Apart from the new features available in later versions of MPE/iX, I am
aware of two additional ways for checking if a job is running or not,
both of which should work on older versions of MPE/iX as well.
First, MPEX has a function called JSCOUNT. It can be used thus...
!MPEX
%!WHILE JSCOUNT("jobname,user.acct&EXEC")>0 DO
%! PAUSE 10
%!ENDWHILE
%!END
...this MPEX functionality has been around a long time, I remember using
it on CLASSIC boxes back in 1989.
Alternatively, you can use a command file / UDC such as the following.
:print isjob
anyparm !JOBNAME
showjob job=!JOBNAME;EXEC>tempfile
if finfo("tempfile",19) < 6 then
setvar job_running false
else
setvar job_running true
endif
This works by doing a SHOWJOB into a file and checking the EOF of that
file. If at least one occurrence of this job is EXECuting, the EOF will
be at least 6. Now within your jobstream, you can say the following...
!isjob JOBNAME,USER.ACCT
!while job_running DO
! pause 10
! isjob JOBNAME,USER.ACCT
!endwhile
...this will loop performing the ISJOB command every 10 seconds. As soon
as no jobs with that name are executing, JOB_RUNNING will be set to
false, and the loop will end.
Many thanks
David
(ex 4321)
-----Original Message-----
From: Simonsen, Larry [SMTP:[log in to unmask]]
Sent: 20 October 1998 02:17
To: [log in to unmask]
Subject: pause while job executing
* Please Note : This message was received from the Internet *
_____________________________________________________________
I seem to remember a command which would allow one job to wait
for
another job to complete. I thought that it was the pause
command but, I
cannot find the syntax for this.
can some one point me into the right cave for this?
------------------------------------------------------------------------
Larry Simonsen Phone: 801-489-2450
Flowserve Corporation Fax: 801-491-1750
PO Box 2200 http://www.flowserve.com
Springville, UT 84663 e-mail: [log in to unmask]
------------------------------------------------------------------------
__________________________________________________________________
Confidentiality Notice
This message may contain privileged and confidential information. If you think, for any reason, that this message may have been addressed to you in error, you must not disseminate, copy or take any action in reliance on it, and we would ask you to notify us immediately by return email to "[log in to unmask]".
|