×
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.
What I remember (unless this was specific to our configuration where I
worked at the time):
EVOKE would start a job running immediately. If you did it a second
time, the second job would start immediatelty too and run simultaneous
to the first one,.
JOB would add a job to a queue. If nothing else was running, it'd run
immediately, but if you started a second one, it'd wait for the first
one to complete before starting the second one, so the jobs would wait
in a queue and run one at a time. You'd typically use this when you
needed output from the first job in order for the second one to run
successfully.
-SK
On 6/13/19 4:05 PM, Justin Taylor wrote:
I'm trying to determine the difference between these two OCL36 commands: EVOKE and JOBQ. From what I've found on Google, they both appear to be like SBMJOB. Does anyone know the difference between them?
TIA
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.
midrange.com
