CONFDATA
The CONFDATA parameter specifies whether CICS® is to suppress user data that might otherwise appear in CICS trace entries or in dumps.
- CONFDATA={SHOW|HIDETC}
- This option applies to initial input data received on:
- A z/OS® Communications Server RECEIVE ANY operation
- An MRO connection
- An IPIC connection
- FEPI screens and RPLAREAs
This option also applies to the CICS client use of a Virtual Terminal. Data is traced before and after codepage conversion and is suppressed if HIDETC is used in combination with CONFDATA YES in the transaction.- SHOW
- Data suppression is not in effect. User data is traced regardless of the CONFDATA option specified in transaction resource definitions. This option overrides the CONFDATA option in transaction resource definitions.
- HIDETC
- CICS is to 'hide' user
transport data from CICS trace
entries. The action taken by CICS is
subject to the individual CONFDATA attribute on the transaction resource
definition (see Table 1). If you specify CONFDATA=HIDETC, CICS processes z/OS Communications Server, MRO, IS, and FEPI user data as follows:
- z/OS Communications
Server: CICS clears the z/OS Communications Server RAIA
containing initial input as soon as it has been processed, and before
the target transaction has been identified.
The normal trace entries (FC90 and FC91) are created on completion of the RECEIVE ANY operation with the text
SUPPRESSED DUE TO CONFDATA=HIDETC IN SIT
replacing all the user data except the first 4 bytes of normal data, or the first 8 bytes of function management headers (FMHs).CICS then identifies the target transaction for the data. If the transaction definition specifies CONFDATA(NO), CICS traces the user data that it suppressed from the FC90 trace in the trace entry AP FC92. This trace entry is not created if the transaction is defined with CONFDATA(YES).
- MRO: CICS does not
trace the initial input received on an MRO link.
The normal trace entries (DD16, DD23, and DD25) are created with the text
SUPPRESSED DUE TO CONFDATA=HIDETC IN SIT
replacing all the user data.CICS then identifies the target transaction for the data. If the transaction definition specifies CONFDATA(NO), CICS traces the user data that it suppressed from DD16 in the trace entry AP FC92. This special trace entry is not created if the transaction is defined with CONFDATA(YES).
- IPIC:
Trace points SO 0201 and SO 0202 suppress buffer data with the message
Trace data suppressed because it may contain sensitive data
. Subsequent trace point SO 029D (buffer continuation) and buffer data from trace points WB 0700 and WB 0701 is suppressed.If the transaction definition specifies CONFDATA(NO), IS trace entries are created with the user data, as normal.
If the transaction definition specifies CONFDATA(YES), user data from IS trace points IS 0602, IS 0702, and IS 0906 is replaced with
SUPPRESSED DUE TO CONFDATA=HIDETC IN SIT
. Data from IS trace points IS 0603 and IS 0703 is not shown. - FEPI: FEPI screens and RPL data areas (RPLAREAs) areas
are suppressed from all FEPI trace points if CONFDATA(YES) is specified
in the transaction resource definition. The user data in the FEPI
trace points AP 1243, AP 1244, AP 145E, AP 145F, AP 1460, AP 1461,
AP 1595, AP 1596, AP 1597, AP 1598, and AP 1599 is replaced with the
message
SUPPRESSED DUE TO CONFDATA=HIDETC IN SIT
. If the transaction definition specifies CONFDATA(NO), the FEPI trace entries are created with the user data as normal.
- z/OS Communications
Server: CICS clears the z/OS Communications Server RAIA
containing initial input as soon as it has been processed, and before
the target transaction has been identified.
Mirror transactions: The CICS-supplied mirror transaction definitions are specified with CONFDATA(YES). This ensures that, when you specify CONFDATA=HIDETC as a system initialization parameter, CICS regions running mirror transactions suppress user data as described for z/OS Communications Server, MRO, and IS data.
Modified data: By waiting until the transaction has been identified to determine the CONFDATA option, z/OS Communications Server, MRO, or IS data may have been modified (for example, it may have been translated to uppercase).
The interaction between the CONFDATA system initialization parameter and the CONFDATA attribute on the transaction resource definition is shown in Table 1.Table 1. Effect of CONFDATA system initialization and transaction definition parameters CONFDATA on transaction CONFDATA system initialization parameter SHOW HIDETC NO Data not suppressed Data not suppressed YES Data not suppressed Data suppressed You cannot modify the CONFDATA option while CICS is running. You must restart CICS to apply a change.
Restriction: You can specify the CONFDATA parameter in the SIT, PARM, and SYSIN only.