Date: Wed, 18 Jun 2003 09:15:34 -0400
Reply-To: "L. Bertolini" <bertolini.1@OSU.EDU>
Sender: "SAS(r) Discussion" <SAS-L@LISTSERV.UGA.EDU>
From: "L. Bertolini" <bertolini.1@OSU.EDU>
Organization: Ohio State University
Subject: Re: JCL and SAS
Content-Type: text/plain; charset=us-ascii; format=flowed
Job classes and initiators are configured by the systems programmers at your
s/390 site; each site tends to be unique. So it's hard for people at
to advise you about class A or class G.
Your site has apparently has a policy that aims to discourage long-running,
CPU-intensive batch programs from monopolizing the processor. That
is not uncommon. You may find a way to temporarily circumvent the
restrictions, but eventually you will be discovered; the loophole will be
closed and you'll alienate the systems programmers in the process.
My advice is to try to exploit the multiplatform support of SAS.
Get your data from the mainframe, crunch it on the PC, and if
necessary, send data back from the PC to the mainframe.
> I am using a s/390 ibm mainframe. To write sas programs and run them,
> we use JCL. We classify the Job to be of class A if it takes less
> than two cpu minutes to complete, and G if it takes longer than that.
> A jobs execute immideatly, G jobs get in queue (which sometimes takes
> an hour or two to start).
> Someone told me that if you use PC sas to connect to the mainframe and
> run your program it will run as a class A no matter how long the job
> takes to execute. (using signon and then rsubmit on PC sas).
> If that is the case, then there is a way (i think) to emulate what PC
> SAS does in its communication with the mainframe to run jobs as class A.
> does anyone know if there is some JCL code or some other setting that
> i can use to emulate what PC SAS does to run long jobs as a class A in
> this case?