The problem determination parameters

Table 9 lists the CICSPlex® SM system parameters that you may be asked to use for problem determination. As indicated in the table, some of the parameters can be used in the startup job for both CMASs and MASs; other parameters are specific to either a CMAS or a MAS.

Table 9. System parameters for problem determination
Name Description Values Used by
BASTRACE Business Application Services trace settings 1-32 Both
BASCONMSG Business Application Services console message flags 1-32 CMAS
CHETRACE Data Cache Manager trace settings 1-32 Both
CHECONMSG Data Cache Manager console message flags 1-32 Both
CICSDUMPS CICS® system dumping active NO | YES CMAS
COMTRACE Communications trace settings 1-32 Both
COMCONMSG Communications console message flags 1-32 Both
DATTRACE Data Repository trace settings 1-32 Both
DATCONMSG Data Repository console message flags 1-32 Both
Start of changeESDUMPEnd of change Start of changeControls SVC dump suppression.End of change Start of changeYES | NO | NEVEREnd of change Start of changeBoth3End of change
ESDUMPCOM Suppress communication task dumps YES | NO CMAS
ESDUMPLIMIT Controls the number of dumps collected for a given failure. 0| 999 CMAS
KNLTRACE Kernel Linkage trace settings 1-32 Both
KNLCONMSG Kernel Linkage console message flags 1-32 Both
MASTRACE Managed Application System trace settings 1-32 MAS
MASCONMSG Managed Application System console message flags 1-32 MAS
MONTRACE Monitor Services trace settings 1-32 CMAS
MONCONMSG Monitor Services console message flags 1-32 CMAS
MSGTRACE Message Services trace settings 1-32 Both
MSGCONMSG Message Services console message flags 1-32 Both
QUETRACE Queue Manager trace settings 1-32 Both
QUECONMSG Queue Manager console message flags 1-32 Both
RTATRACE real-time analysis trace settings 1-32 Both1
RTACONMSG real-time analysis console message flags 1-32 Both
SRVTRACE Common Services trace settings 1-32 Both
SRVCONMSG Common Services console message flags 1-32 Both
TOPTRACE Topology Services trace settings 1-32 Both
TOPCONMSG Topology Services console message flags 1-32 Both
TRCTRACE Trace Services trace settings 1-32 Both
TRCCONMSG Trace Services console message flags 1-32 Both
WLMTRACE Workload Manager trace settings 1-32 Both2
WLMCONMSG Workload Manager console message flags 1-32 Both
Notes:
  1. RTATRACE is valid in a MAS only if status definitions are installed and being used by a user-written status program.
  2. WLMTRACE is valid in a MAS only if it is a local MAS acting as a TOR in a CICSPlex SM workload.
  3. Start of changeSVC dumps are issued by CPSM through EYU9XLRV during abend recovery or on demand through EYU0XZPT and EYU0XZSD.
    • When ESDUMP(YES) is specified, no SVC dumps are suppressed.
    • When ESDUMP(NO) is specified, duplicate dumps taken by EYU9XLRV, EYU0XZPT and internally by EYU0XZSD might be suppressed, depending upon the value of the ESDUMPLIMIT EYUPARM. SVC dump requests made through EYU0XZSD from the COD0 transaction continue to be honored.
    • When ESDUMP(NEVER) is specified all SVC dumps taken by EYU9XLRV, EYU0XZPT, and internally by EYU0XZSD will be suppressed. SVC dump requests made through EYU0XZSD from the COD0 transaction will continue to be honored.
    It is strongly recommended by CPSM service that ESDUMP(NEVER) not be used, as it may affect the ability to debug problems. If a problem occurs with SVC dump suppression active, users may be required to reproduce the problem without SVC dump suppression active before debugging can be performed for the problem.

    To deactivate SVC dump suppression without restarting the CMAS or MAS, the ESDUMP value can also be updated as follows:

    • Through the COD0 SET command.
    • For a CMAS only, by updating the CMAS resource table SDUMP field through the EUI ( CMASD view SDUMP always field), or through the API or WUI
    End of change
[[ Contents Previous Page | Next Page Index ]]