× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



A Google search on SBMKEYJOB reveals.

Michael Price11-16-2000, 07:59 AM
I came across a set of utilities in NEWS/400 February 1997 that allows
one to run batch jobs in parallel. I would like to get feedback on the
best way to use these utilities.

The article suggests if you have an application where ProgA and ProgB
can run parallel to be followed by ProgC that you should create :
PGM
SBMKEYJOB CMD( CALL ProgA ) .......
SBMKEYJOB CMD( CALL ProgB ) .......
WATKEYJOB JOBKEY ( ProgA ProgB )
RCLJOBKEY JOBKEY ( ProgA ProgB )
CALL ProgC
ENDPGM

Can this job be submitted to a jobq and if so would the not require 3
jobs to active on that jobq???

Would it not be better to code the job as:
PGM
SBMKEYJOB CMD ( CALL ProgA ) .....
CALL ProgB
WATKEYJOB JOBKEY ( ProgA )
RCLJOBKEY JOBKEY ( ProgA )
CALL ProgC
ENDPGM


-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Booth Martin
Sent: Wednesday, August 20, 2008 6:25 PM
To: Midrange Systems Technical Discussion
Subject: A CL program that runs several batch jobs, one after the other

A CL program that runs several batch jobs, one after the other

A CL program is calling several other CLs, many of which have SBMJOB
commands in them. The next CL can not be run until the previous CL is
completed.

It is entirely possible that I am making too big a deal out of this. Is
there an easy way to make it run one step at a time?



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.