The problem determination parameters

You might be asked for certain CICSPlex SM system parameters to help with problem determination.

As indicated in Table 1, 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 1. System parameters for problem determination
Name Description Values Default  1  Used by
BASTRACE Business Application Services trace settings 1–32 None Both
CHETRACE Data Cache Manager trace settings 1–32 None Both
CICSDUMPS CICS® system dumping active NO | YES NO CMAS
COMTRACE Communications trace settings 1–32 None Both
DATTRACE Data Repository trace settings 1–32 None Both
ESDUMP Take SDUMP on all CMAS and MAS failures YES | NO | NEVER NO Both1
ESDUMPCOM Suppress communication task dumps YES | NO NO CMAS
ESDUMPLIMIT Controls the number of dumps collected for a given failure. 0–999 1 CMAS2
KNLTRACE Kernel Linkage trace settings 1–32 None Both
MASTRACE Managed Application System trace settings 1–32 None MAS
MONTRACE Monitor Services trace settings 1–32 None CMAS
MSGTRACE Message Services trace settings 1–32 None Both
QUETRACE Queue Manager trace settings 1–32 None Both
RTATRACE real-time analysis trace settings 1–32 None Both3
SRVTRACE Common Services trace settings 1–32 None Both
TOPTRACE Topology Services trace settings 1–32 None Both
TRCTRACE Trace Services trace settings 1–32 None Both
WLMTRACE Workload Manager trace settings 1–32 None Both4
Notes:

 1  You should only modify the default values at the request of your IBM® Service Representative.

  1. ESDUMP - SVC dumps are issued by CICSPlex SM 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 may 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 are suppressed. SVC dump requests made through EYU0XZSD from the COD0 transaction continue to be honored.
    It is strongly recommended that ESDUMP(NEVER) not be used, because it might affect the ability to debug problems. If a problem occurs with SVC dump suppression active, you might 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 using one of the following methods:
    • Using the COD0 SET command.
    • For a CMAS only, by updating the CMAS resource table SDUMP field using the API or WUI
  2. If the ESDUMP system parameter is set to NO, the SVC dump suppression is controlled by the ESDUMPLIMIT CICSPlex SM system parameter. You can use it in the startup job for the CMAS. This parameter controls the number of dumps collected for a given failure. The default is 1.
    For example, if you want to capture dump diagnostic information for the first 3 instances of an error, add the following to the CMAS's EYUPARM DD statement:
    ESDUMP(NO)
    ESDUMPLIMIT(3)
    An abend control block of entries is created whenever a CICSPlex SM dump is requested. Each entry contains information about the number of different abends that have occurred. Separate entries are maintained for CMASes and MASes.

    The instances of an abend are determined by a combination of abending program name, abend codes, abend offset and region type (CMAS or MAS).

    For dumps requested by a MAS, the ESDUMPLIMIT of the CMAS that the MAS connects to is used. For a MAS, the dump limit is shared among all the MASes that connect to the CMAS. For example, if ESDUMPLIMIT(5) is set in a CMAS, and 10 different MASes all receive the same abend, dumps are requested only by the first 5 MASes.

    The number of abends that have occurred is reset to 0 for MAS-related abend entries when the last MAS disconnects from a CMAS.

    The number of abends that have occurred is reset to 0 for CMAS related abend entries during CMAS initialization.

    All abend entries are reset for both MASes and CMASes if a CMAS and all the MASes that connect to it are shut down at the same time.

  3. RTATRACE is valid in a MAS only if status definitions are installed and being used by a user-written status program.
  4. WLMTRACE is valid in a MAS only if it is a local MAS acting as a TOR in a CICSPlex® SM workload.


eyus1hk.html | Timestamp icon Last updated: Monday, 5 June 2017