Parameters created by the DISCOVER action

The DISCOVER action creates parameters for each subsystem it discovers.

Overview of output

The output of the DISCOVER action depends on the subsystem:

Table 1. Output of the DISCOVER action
Subsystem Output
Db2®, IMS, TCP/IP Parameters that configure the runtime environment to monitor these subsystems.

For Db2, you need to complete the discovered details.

CICS® Parameters that specify an historical datastore allocation table for task history file disposition.
MQ Statements using embed overrides that you can place in the KMQ$CUSR embed override member:
SET MANAGER NAME(queue-manager)

In addition to the subsystem discovery, a member is created that contains the System symbols that can be used by the GENERATE action along with the respective KCIPARSE extracted variables. For more information, see RTEDEF(SYS@lpar).

Parameters

The following table lists the parameters created by the DISCOVER action.

The parameters created depend on which program performs the action: KCIOMEGA or KCIALPHA.

In general, KCIOMEGA discovers only the subsystem identifier. For detailed discovery, use KCIALPHA.

Table 2. Parameters created by the DISCOVER action
Subsystem Parameter
(nn is the 2-digit table row number)
KCIOMEGA KCIALPHA
CICS KC2_HSnn_CLASSIC_CICS_REGION No Yes
Db2 KD2_DBnn_DB2_SSID Yes Yes
Db2 KD2_DBnn_DB2_VER No Yes
Db2 KD2_DBnn_DB2_DS_GROUP No Yes
Db2 KD2_DBnn_DB2_LOADLIB No Yes
IMS KI2_I1nn_CLASSIC_IMSID Yes Yes
IMS KI2_I1nn_CLASSIC_IMS_RESLIB No Yes
MQ For MQ subsystems, DISCOVER generates SET MANAGER statements, not parameters. Yes Yes
TCP/IP KN3_TCPXnn_TCP_STC Yes Yes
TCP/IP KN3_TCPXnn_TCPIP_PROFILES_DSN No Yes
TCP/IP KN3_TCPXnn_TCPIP_PROFILES_MBR No Yes