Date:         Fri, 22 Feb 2002 12:20:52 -0800
Reply-To:     "William W. Viergever" <wwvierg@ATTGLOBAL.NET>
Sender:       "SAS(r) Discussion" <SAS-L@LISTSERV.UGA.EDU>
From:         "William W. Viergever" <wwvierg@ATTGLOBAL.NET>
Subject:      Re: MVS Question
Comments: To: Puddin' Man <pudding_man@POSTMARK.NET>
In-Reply-To:  <20020222211748.26658.qmail@venus.postmark.net>
Content-Type: text/plain; charset="us-ascii"; format=flowed

Hi Puddin'

Being rusty on MVS I didn't respond to this when I read it .. but was
thinking the same thing.

More in particular, however, at the various shops on whose big iron I've
played, they all had pretty much different default TIME limits; sometimes
w/ different amounts allowed on the JOB vs. the EXEC cards, so......

if Paul wants to sleep <g>, she best check out those or it'll bomb anyway.

Out



At 09:17 PM 2/22/2002 +0000, Puddin' Man wrote:
>bracyr wrote:
>
> > > MVS SAS 8.2
> > > Does anyone currently schedule SAS jobs to run on an automatic recurring
> > > basis? For example, tomorrow I'm out but after 6AM, I want a SAS job to
> > > run. Would my JCL code need updated? Any help would be appreciated!
> >
> > Quick and dirty way would be to use the CALL SLEEP function.
>
>Well, it might not be so bad to make it SLEEP for an
>hour or so.
>
>But while it's SLEEPing, the batch job will be
>sitting on an important and unused resource: internal
>storage (aka memory).
>
>So Paula maybe submits her job at 5 PM with a SLEEP
>parameter that keeps it inactive for 11 hours?
>
>Imagine the MVS operator shift change. Operator T tells
>operator T+1 that job XXXX has done no i/o, used no
>cpu cycles for hours. Then T+1 watches the job do
>nothing for additional hours. Operators have been
>known to cancel such jobs ("Damned thang's hung!
>Shoot it down!!").
>
>If practical, I'd dial-in after breakfast and submit
>it my po' self. :-)
>
>   Puddin'
>
>*******************************************************
>*** Puddin' Man     *** Pudding_Man@postmark.net  *****
>*******************************************************;
>
>
> > Excerpt from Online SAS document
> > CALL SLEEP puts the DATA step in which it is invoked into a nonactive
> > wait state, using no CPU time and performing no input or output. If
> > you are running multiple SAS processes, each process can execute CALL
> > SLEEP independently without affecting the other processes.
> >
> > In this example, the DATA step invokes CALL REPORT every hour:
> >
> > data _null_;
> >    while (1);
> >       call report(a,b,c,d);
> >       call sleep(3600000);
> >    end;
> > run;

------------------------------------------------------------
William W. Viergever          Voice  : (916) 483-8398
Viergever & Associates        Fax    : (916) 486-1488
Sacramento, CA 95825          E-mail : wwvierg@attglobal.net
------------------------------------------------------------