Re: HELP!! DLYJOB command

Bob,

In a message dated 97-04-22 02:18:45 EDT, you write:

> I recently modified our daily backup CL job to include a DLYJOB with the 
>  RSMTIME parm (as opposed to DLY).  This job is normally run by an operator

>  at 1:30am at the system console, but on this particular night we had no 
>  coverage so I thought I'd give this a try.  Now this job already had a 
>  DLYJOB command with DLY(600) to give the subsystems time to end before 
>  beginning the saves (backup runs in restricted state and backups all
changed 
>  objects - I didn't write it) which works fine, but this is my first 
>  experience using the RSMTIME parm.  I added this in the CL immediately 
>  preceding the ENDSBS statements.
>  
>  So anyway, before I left for the day at 5:00pm, I went up to the console
and 
>  started the CL job which appropriately executed up to the new DLYJOB 
>  statement.  A quick check with wrkactjob indicated that the job was in a 
>  delay status until 1:30am.  Upon arriving at 4:00am, an operator was to 
>  check to make sure that the job was either running or had completed.  At 
>  9:00am the next morning I arrived believing that all had gone well since I

>  had not been called.  Come to find the operator did not check the job at 
>  4:00am.  I then instructed him to do so.  Upon arriving at the console the

>  operator found it to be blank (not unusual as it was in energy saver
mode), 
>  so he hit Enter.  At that point all of the subsystems started ending.  I 
>  don't have to tell you how that went over (hint:  not very well!).  There 
>  were no outstanding message in the QSYSOPR message queue, so I don't 
>  believe there was a legitimate reason for the job not resuming at 1:30 ...
Can 
>  anyone PLEASE point me in the right direction here?  I need to do this
again 
>  very soon and would appreciate any help I can get.  As always, thank you
in 
>  advance!!

How do you KNOW that there was not a message outstanding on QSYSOPR?  Would
it have been possible for the operator to delete it before you looked at the
queue?  It sounds like the QSYSOPR queue was in *BREAK mode on the console,
and the operator took the default when he/she pressed <ENTER> (which is why I
always use the space bar on both the /400 and PC's).  It certainly sounds
like there was a message waiting...

Regards!

Dean Asmussen
Enterprise Systems Consulting, Inc.
Fuquay-Varina, NC  USA
E-Mail:  DAsmussen@AOL.COM

"A fanatic is one who can't change his mind and won't change the subject." --
Sir Winston Churchill
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* This is the Midrange System Mailing List!  To submit a new message,   *
* send your mail to "MIDRANGE-L@midrange.com".  To unsubscribe from     *
* this list send email to MAJORDOMO@midrange.com and specify            *
* 'unsubscribe MIDRANGE-L' in the body of your message.  Questions      *
* should be directed to the list owner / operator: david@midrange.com   *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *