Why do some jobs not track in CA WA CA 7 Edition (remain in the ready queue) while others are tracking?
In a JES2 shared spool environment, initialize CA WA CA 7 Edition with the CAIRIM procedure on every LPAR in the sysplex even if no CA WA CA 7 Edition submitted jobs run on that LPAR. If no CA WA CA 7 Edition submitted jobs run on that LPAR you do not have to start ICOM, but perform the CAIRIM initialization of the CA WA CA 7 Edition environment.
When CA WA CA 7 Edition submits a job, an indicator is put in the first JOB statement. When the job goes through the converter interpreter and the IEFUJV exit, it is recognized as CA WA CA 7 Edition submitted. An indicator is placed in the SMF common area. When subsequent SMF records are cut for the job (job start, step end, job end, and so forth), our exits can collect this data and feed it back to CA WA CA 7 Edition through ICOM. In a shared JES environment, JES decides where the job goes through the converter interpreter. Usually a job is converted on the LPAR where it is submitted, but during heavy processing JES can pass this process to another LPAR.
If a job converts on an LPAR that does not have the CA WA CA 7 Edition environment initialized, CA7ONL does not track this execution. To see whether the job was converted on an initialized LPAR, look in the JESLOG of the job for the following IBM message:
IEFC025I INSTALLATION MODIFIED JCL
The presence of this message means that when the job converted, the CA WA CA 7 Edition environment was present on that LPAR. The absence of this message means that it was not, and if it is not present, the job does not track in CA7ONL.
Business Value:
Understanding how work is tracked helps when troubleshooting an issue with task tracking.
|
Copyright © 2013 CA Technologies.
All rights reserved.
|
|