Troubleshooting Best Practices › Not Tracking

Not Tracking

What do I check if no jobs are tracking?

CA WA CA 7 Edition tracks work that it submits using SMF feedback.

The failure to track work in CA7ONL is reported in many ways. Jobs that complete do not trigger their follow-up work, jobs hang in the ready queue, and so forth, but these are symptoms of CA WA CA 7 Edition not tracking the work it is submitting.

If some jobs track and others do not, verify that security is not causing the problem. Look for a JOB FLUSHED message on OS console. The message probably has no job name.

Jobs in the ready queue are either ready to submit or have already been submitted and moved to the active queue when a job initiation record is received. To verify whether a job is already submitted, look at the output from an LQ command (LQ, LRDY, and so on). The output has a SUB/START DATE/TIME heading. For a job in the ready queue, a value in the SUB/START DATE/TIME field of *NONE* means that the job is not submitted. If a date and time are in this field, that time is the time that the JCL was written to internal reader or submit data set. LRDYP,JOB=,LIST=STATUS show a nonsubmittal reason if *NONE* is in this field.

If using submit data sets and a date/time is in the SUB/START DATE/TIME field, check to see whether the submit data sets are used correctly between CA7ONL and ICOM.

If a date/time is in the SUB/START DATE/TIME field on the LRDY output, and the job has run, check to be sure that ICOM is active on the LPAR where the job is running. Check the communications data set name in the CA7ONL and ICOM procedures to verify that they are the same file. When both programs start, a CA-7.INCD message states the volume where the communications data set resides and whether it is shared.

Check the SVCNO statement in the initialization file for SASSVC=NO. For job tracking, set this keyword as SASSSVC=YES.

If the CA WA CA 7 Edition environment was reinitialized with CAIRIM, consider recycling CA7ONL and ICOM.

You can issue CAISMFU as a command from ISPF option 6 or TSO.

The output should show SASSUJV, SASSU83 and SASSU84 active:

   CAS9001I    Interface Summary: 
   CAS9002I 
   CAS9003I    Name      Vers  Description           Status 
   CAS9004I    CAS9U83   S910  CAIRIM INTERCEPT      Active 
   CAS9004I    CAS9U84   S910  CAIRIM INTERCEPT      Active 
   CAS9004I    CAS9ATRT  S910  CAIRIM INTERCEPT      Active 
   CAS9004I    SMFISDMP  SF15  JARS/SMF INITIATOR    Active 
   CAS9004I    $IXRUJSI  L141  IXR JOB INIT EXIT     Active 
   CAS9004I    TLMSSMFE  TL55  TLMS SMF EXIT         Active 
   CAS9004I    SASSUJV   L2B0   CA-7 JOB VAL EXIT    Active 
   CAS9004I    SASSU83   L2B0   CA-7 SVC 83  EXIT    Active 
   CAS9004I    SASSU84   L2B0   CA-7 SVC 84  EXIT    Active 
   CAS9004I    JR51SMFE  7.1   JARS ONLINE CHARGES   Active 
   CAS9004I    CASEJOB   W110  CA-ENF Job Init       Active 
   CAS9004I    CASESM83  W110  CA-ENF Intercept      Active 
   CAS9004I    CASESM84  W110  CA-ENF Intercept      Active 
   CAS9002I 
   CAS9005I    Number of interfaces 13  Number of calls processed 684533 

Run the U7TESTSV program. Issue a DEMAND,JOB=CA07SVCT command, and check the JES output of this job (you may have to do a DEMANDH and then edit the QJCL to route the job to various LPARS if you have more than one). The messages produced by this job are documented in the Message Reference Guide.

Run the CAL2OPTN member AL2ENVR (if you use release 11.1, the member name is CAL2ENVR in SAMPJCL) to get an environmental report.

Business Value:

Understanding how work is tracked helps when troubleshooting an issue with task tracking.