Viewing the TP Message Log During TP Run Time

When you set up the TP message log with the parameters described in the previous sections, you can access the log only after a TP stops running. If you need to access the TP message log between job steps, you can invoke program ASBSCHWL (write log routine) after a job step in the TP profile JCL. This routine enables you to view messages for the previous job step.

The following example invokes program ASBSCHWL in STEP2 and specifies that error messages, if any, go to data set IBMUSER.JOBLOG.DATASET.

Figure 1. Invoking the Write Log Routine

          TPNAME(RUN_TEST)
          USERID(IBMUSER)
          ACTIVE(YES)
          TPSCHED_DELIMITER(##)
             TAILOR_SYSOUT(YES)
             TAILOR_ACCOUNT(YES)
             CLASS(A)
             TPSCHED_TYPE(STANDARD)
             JCL_DELIMITER(END_OF_JCL)
     //TEST     JOB  ,IBMUSER
     //STEP1    EXEC PGM=TEST1
     //STEP2    EXEC PGM=ASBSCHWL,PARM='JOBLOG'
     //JOBLOG   DD   DSN=IBMUSER.JOBLOG.DATASET,DISP=SHR...
     //STEP3    EXEC PGM=TEST2
     END_OF_JCL
     ##

Note: If the PARM parameter is omitted in STEP2, JOBLGDCB is the default joblog DD name.

Write log routines can write messages only if the TP profile parameter KEEP_MESSAGE_LOG has a value of ALWAYS or ERROR. When KEEP_MESSAGE_LOG has a value of NEVER, no messages are written to any TP message log.

In the previous example, the write log routine controls only the TP messages written in STEP1. Otherwise, the following TP profile defaults apply:

  KEEP_MESSAGE_LOG(ERROR)
  MESSAGE_DATA_SET(&SYSUID;&SYSWUID;&TPDATE;&TPTIME;JOBLOG)
  DATASET_STATUS(NEW)

Assuming that the ASCHPMxx parmlib member also uses defaults, the following parmlib member defaults apply:

  MSGLIMIT(500)
  MSGLEVEL(1,0)

Given these defaults, if the TP abnormally ended in STEP3, messages would be written to the default TP message log data set (&SYSUID.&SYSWUID.&TPDATE.&TPTIME.JOBLOG), which can be accessed when the TP stops running. &SYSUID resolves to the user ID that invoked the TP, &SYSWUID resolves to the work unit identifier for the TP, and &TPDATE and &TPTIME resolve to the date and time the TP ran. For a multitrans TP, &SYSUID resolves to the generic userid. For a standard TP, &SYSUID resolves to the userid passed in with the inbound allocate request, unless security_none is used (no userid passed), and then &SYSUID resolves to SYSUID.