About IBM Connect:Direct CICS Data
This section lists files and other data used by IBM® Connect:Direct® DTF and CICS®.
IBM Connect:Direct DTF and CICS Data
The following data, accessed in read-only mode under CICS, is used by IBM Connect:Direct DTF and the CICS Interface:
Data | Description |
---|---|
NETMAP (DDN=NETFINP) |
At least one netmap file exists for each CICS region. The file is defined as a CICS file. It is updated in batch and contains all IBM Connect:Direct nodes available to this CICS environment. Some of the information for the network IBM Connect:Direct nodes is also contained in the Configuration File along with additional fields that you can update. |
PROCESS (DDN=DMPUBLIB) |
One DD name exists for each CICS region. Several files can be concatenated. It is not defined as a CICS file. It is allocated by CICS and used at the subtask level by the IBM Connect:Direct API only. If necessary, you can dynamically allocate and deallocate it using CICS transaction DGAN. |
MESSAGE (DDN=NDMMSG) |
One file exists for each system. It is defined as a CICS file and is allocated and opened by CICS. It is updated in batch using the IBM Connect:Direct message load utility. |
TCQ | One Transmission Control Queue (TCQ) file exists for each IBM Connect:Direct node. It is not defined as a CICS file. It holds submit (ESF) requests when IBM Connect:Direct DTF is down. It is used at the subtask level by the IBM Connect:Direct API only. It is allocated by CICS and opened by a subtask. If necessary, you can dynamically allocate and deallocate it using the CICS transaction DGAN. |
RPLERRCK
(DDNAME) |
It is not defined as a CICS file nor is it in the RDO. It contains VTAM® errors written to a sequential file by the IBM Connect:Direct interface and is defined as SYSOUT. |
EVENT RESTART (DDN=NDMEVNT) |
One file exists for each CICS region. It is defined as a CICS file, and is allocated and opened by CICS. It is updated by the Event Services Support, and is used for restarting ESS. |
Trace Files | Several files within the IBM Connect:Direct API
are dedicated to system trace functions, but are not explicitly used
by the CICS Interface. The IBM Connect:Direct API
design enables trace data to be written when they are available. To
capture trace data, add the appropriate DD name statements to the CICS startup JCL. The files must
be present at CICS initialization. Note: Do
not dynamically allocate trace files after CICS initializes. Each IBM Connect:Direct API
(one per WST) writes trace data to these files when present. An example
is NDMCMDS, which you can use to view all commands submitted to the
API.
|
IBM Connect:Direct CICS Data Sets
The following data sets, used only by Connect:Direct for z/OS®, are for the CICS Interface environment and are updated under CICS:
Data Set | Description |
---|---|
CONFIGURATION | One file exists for each CICS region. It is defined as a CICS file. You can update it online through administrator functions. It is a VSAM KSDS file. It contains all IBM Connect:Direct nodes available to this Connect:Direct for z/OS environment as does NETMAP, but CONFIGURATION contains system parameters that control the IBM Connect:Direct CICS API environment. |
USER PROFILE (SIGNON DEFAULTS) | One file exists for each CICS region. It is defined as a CICS file that is a VSAM KSDS file with the CICS userid as key. Update it using the signon defaults function and use it to set up auto-signon to IBM Connect:Direct. |
Temporary Data Set
The IBM Connect:Direct API TDEXIT parameter configures the routing of IBM Connect:Direct statistics records to CICS Temporary Storage. CICS Temporary Storage, containing the data, is retained until the user exits the SELECT STATISTICS screen. CICS Temporary Storage containing the data is then deleted.