z/OS MVS Planning: APPC/MVS Management
Previous topic | Next topic | Contents | Contact z/OS | Library | PDF


Example of Using TP Message Log Parameters

z/OS MVS Planning: APPC/MVS Management
SA23-1388-00

To use a cumulative log for all messages with a limit of 10,000 messages, code the values for the highlighted parameters as shown in the following examples of a TP profile and an ASCHPMxx parmlib member.

Figure 1. TP Profile Parameters
          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)
     //TEST1    JOB  ,IBMUSER
     //STEP     EXEC PGM=TESTRUN
     END_OF_JCL
       KEEP_MESSAGE_LOG(ALWAYS)
       MESSAGE_DATA_SET(TEST1.TESTLOG)
       DATASET_STATUS(MOD)
     ##
Figure 2. ASCHPMxx Parameters
  CLASSADD
    CLASSNAME(A),
    MAX(10),
    MIN(2),
    RESPGOAL(.01),
    MSGLIMIT(10000)

  TPDEFAULT
    REGION(256),
    TIME(1,30),
    MSGLEVEL(1,1),
    OUTCLASS(J)

This example is for a test TP that creates a TP message log that contains all runtime messages. After a TP is successfully tested, an installation might change the KEEP_MESSAGE_LOG value to ERROR or NEVER to enhance TP runtime performance. Writing messages to the TP message log will affect CPU time and the response time of the TP.

Go to the previous page Go to the next page




Copyright IBM Corporation 1990, 2014