×
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.
On 3/16/11 5:22 AM, rob@xxxxxxxxx wrote:
Your first problem is that you are using a command (WRKJOB), telling
it OUTPUT(*PRINT), and trying to analyze that output.
<<SNIP>>
Not necessarily. For the subject "duplicate jobs" case, that
condition causes the CL WRKJOB request to fail with the escape message
CPF1069 "End of duplicate names." while having produced _no output_
except possibly the "Select Job" panel presented in an interactive job;
but even that can be avoided by specifying DUPJOBOPT(*MSG) on the Work
with Job request. Thus for that case, WRKJOB OUTPUT(*NULL) /* if it
were supported */ might suffice for what is intended\analyzed.
The messaging can be used as a means to infer something about the
specified generic JOB() without having to use any spooled output or an
API; just limited in the capabilities that method provides, and CHGJOB
of a mundane attribute might be a better choice since no output is
produced when only one job [i.e. no duplicate job name] exists. Little
different than a coded wait and looping on ENDSBS requests versus a
coded wait and looping on job status inquiries of the subsystem monitor
after just one ENDSBS request, awaiting completion of the CL ENDSBS request.
Regards, Chuck
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
