HP3000-L Archives

July 1995, Week 4

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
"Paul H. Christidis" <[log in to unmask]>
Reply To:
Date:
Fri, 21 Jul 1995 15:41:13 PST
Content-Type:
text/plain
Parts/Attachments:
text/plain (71 lines)
HOW ABOUT TRYING THIS:
 
:STREAM FOOJOB;AT=23:00
 
 Then within the jobstream say:
 
!JOB FOOJOB,MANAGER.SYS
!STREAM FOOJOB;in=1      <<One day from the current date and time>>
!EOJ
 
Use the 'IN=days,hours,minutes' option. The initial mpe command will schedule it
for the first time and then the 'relative' option 'in' will schedule it for the
next day.  The client should consider what happens to his scheduled jobs in the
event that the system is brought down though!
 
Regards
 
Paul H. Christidis
 
______________________________ Reply Separator _________________________________
Subject: Self streaming job to run once a day.
Author:  [log in to unmask] at CCGATE
Date:    7/21/1995 3:23 PM
 
 
I got a call from a customer today who is having problems setting up
a job which, among other things, :STREAMs another instance of itself
to run the next day. Now you would think that this would be the most
obvious use of the Scheduled Job options of the :STREAM command.
 
Unfortunately, this does not turn out to be the case :-)
 
Let's look at some obvious attempts to make this work...
 
1)
 
!JOB FOOJOB,MANAGER.SYS
!STREAM FOOJOB;AT=23:00
!EOJ
 
Looks simple, no? Unfortunately, the !@#$% ;AT= option says that if the
time you specify is equal to the current time, the job is streamed to
run *right* *now* rather than 24 hours from now. So, when today's job
logs on at 23:00, and says :STREAM itself;AT=23:00, it makes a big
mess.
 
The customer tried to get around the problem this way:
 
!JOB FOOJOB,MANAGER.SYS
!PAUSE 65
!STREAM FOOJOB;AT=23:00
!EOJ
 
But... THIS DOESN'T WORK! A :PAUSE of 65 seconds apparently does not
guarantee that we have gotten to at least 23:01. At least on this
customer's system it frequently fails to do so.
 
HP Supportline includes (at the following URL:
http://support.mayfield.hp.com/kdb-bin/wwwsdoc.pl?DOCID=A1589753
) the rather entertaining suggestion that the way to handle this is:
 
!      setvar nextday !hpday + 1
!      stream job.util;at=8:00;day=!nextday
 
which is so wrong (for at least two reasons) that it's funny.
 
There must be a simple, non-kludge, way of making this work which
people are using. Right?
 
G.

ATOM RSS1 RSS2