Dependency base tables

The Dependency base tables are defined in the database objects. You can write your own SQL applications to query the tables; these applications must use native SQL queries.

CIU_CICS_DATA
This table stores information about every unique combination of CICS® region, transaction, program, function, and CICS or CICSPlex® SM resource recorded by the Collector. With this table, you can answer questions such as:
  • Which CICS resources are used by this transaction?
  • If I change this CICS resource, which programs and transactions are affected?
Table 1. The CIU_CICS_DATA table
Column Type Description
COLLECTION_ID CHAR(16) Collection ID.
ARCHIVE_DATE TIMESTAMP Time of archiving.
APPLID CHAR(8) CICS region APPLID.
HOMESYSID CHAR(4) SYSID of local region.
Start of change PLATFORM End of change Start of change CHAR(64) End of change Start of change Platform name End of change
APP_NAME CHAR(64) Application name
APP_VER1 INTEGER Major version number
APP_VER2 INTEGER Minor version number
APP_VER3 INTEGER Micro version number
APP_OPER CHAR(64) The operation associated with the task
TRANSID CHAR(4) CICS transaction ID
PROGRAM CHAR(8) Currently active CICS program.
FUNCTION CHAR(24) EXEC CICS command name, such as READ, WRITEQ,1 4 or EXEC CPSM command name.
TYPE CHAR(16) Resource type, such as TS, program. 1 4
OBJECT CHAR(255) Resource name. 2
OBJLENGTH INTEGER Length of resource name in OBJECT field.
RMTSYSID CHAR(4) Remote SYSID, if relevant. 3
RMTNAME CHAR(8) Name by which the resource is known in the remote region.
TERMTRAN CHAR(1) Whether a terminal is associated with the transaction:
Y
Terminal transaction
N
Non terminal transaction
TCBMODE CHAR(2) CICS TCB in which the application is running; for example, QR or L8.
AFFINITY CHAR(1) Whether the EXEC CICS command might cause an affinity:
Y
Yes
N
No
OFFSET CHAR(8) The offset of the command from the start of the program.
PROGLEN CHAR(8) Length of CICS program. Used for program versioning.
COMMAREA CHAR(1) Whether a commarea is associated with the transaction:
Y
Yes
N
No
CHANNEL CHAR(1) Whether a channel is associated with the transaction:
Y
Yes
N
No
USECOUNT INTEGER Number of occurrences.
FIRST_RUN TIMESTAMP Time of first occurrence, in the local time format.
LAST_RUN TIMESTAMP Time of latest observation, in the local time format.
USER_DATA1 CHAR(48) Reserved.
USER_DATA2 CHAR(48) Reserved.
USER_DATA3 CHAR(48) Reserved.
Note:
  1. If the EIBCODE in the dependency data is not recognized by the database update program, both the FUNCTION and TYPE columns contain ????????.
  2. The resource name is the name of the object of the function. This column is 50 bytes to accommodate the names of objects such as programs and files, but the data, the 4-byte name of a TD queue, might occupy less space.
  3. If the command is shipped or routed to a remote region, these characters represent the system identifier (SYSID) of the remote region.
  4. For information about Function and Type values, see Type and Function mapping for monitored commands.
CIU_DB2_DATA
This table stores information about every unique combination of CICS region, transaction, program, function, and DB2® resource recorded by the Collector. With this table, you can answer questions such as:
  • Which DB2 resources are used by this transaction?
  • If I change this DB2 resource, which programs and transactions are affected?
Table 2. The CIU_DB2_DATA table
Column Type Description
COLLECTION_ID CHAR(16) Collection ID.
ARCHIVE_DATE TIMESTAMP Time of archiving.
APPLID CHAR(8) CICS region APPLID.
HOMESYSID CHAR(4) SYSID of local region.
Start of change PLATFORM End of change Start of change CHAR(64) End of change Start of change Platform name End of change
APPL_NAME CHAR(64) Application name
APPL_VER1 INTEGER Major version number
APPL_VER2 INTEGER Minor version number
APPL_VER3 INTEGER Micro version number
APPL_OPER CHAR(64) The operation associated with the task
DB2ID CHAR(4) DB2 subsystem ID.
TRANSID CHAR(4) CICS transaction ID.
PROGRAM CHAR(8) CICS program name.
PLAN CHAR(8) DB2 plan ID.
RESTYPE CHAR(16) DB2 resource type. 1
RESNAME CHAR(40) DB2 resource name.
FUNCTION CHAR(24) EXEC SQL command name, such as CREATE, UPDATE. 1 2
SECTION SMALL INT The section number, in the source code of the CICS program, at which the DB2 command is issued.
STATEMENT SMALL INT The precompiler statement number, in the source code of the CICS program, at which the DB2 command is issued.
TERMTRAN CHAR(1) Whether a terminal is associated with the transaction:
Y
Terminal transaction.
N
Nonterminal transaction.
TCBMODE CHAR(2) CICS TCB in which the application is running; for example, QR or L8.
OFFSET CHAR(8) The offset of the command from the start of the program.
PROGLEN CHAR(8) Length of CICS program. Used for program versioning.
USECOUNT INTEGER Number of occurrences.
FIRST_RUN TIMESTAMP Time of first occurrence, in the local time format.
LAST_RUN TIMESTAMP Time of latest observation, in the local time format.
USER_DATA1 CHAR(48) Reserved.
USER_DATA2 CHAR(48) Reserved.
USER_DATA3 CHAR(48) Reserved.
Note:
  1. For more information about RESTYPE and FUNCTION, see Table 43 in Type and Function mapping for monitored commands.
  2. If the command in the dependency data is not recognized by the database update program, the FUNCTION column contains ????????.
  3. The RESOURCE column might not contain the actual name of the DB2 resource that is used. It might, for example, contain the name of a variable. In this case, use the values of the PROGRAM, SECTION, and STATEMENT columns to look up, in the DB2 SYSIBM.SYSPACKSTMT or SYSIBM.SYSSTMT table, the DB2 resource name. The views V_CIU_DB2_RES for SYSIBM.SYSPACKSTMT and V_CIU_DB2_RES2, for SYSIBM.SYSSTMT are provided to help you.
CIU_IMS_DATA
This table stores information about every unique combination of CICS region, transaction, program, function, and IMS™ resource recorded by the Collector. With this table, you can answer questions such as:
  • Which IMS resources are used by this transaction?
  • If I change this IMS resource, which programs and transactions are affected?
Table 3. The CIU_IMS_DATA table
Column Type Description
COLLECTION_ID CHAR(16) Collection ID.
ARCHIVE_DATE TIMESTAMP Time of archiving.
APPLID CHAR(8) CICS region APPLID.
HOMESYSID CHAR(4) SYSID of local region.
Start of change PLATFORM End of change Start of change CHAR(64) End of change Start of change Platform name End of change
APPL_NAME CHAR(64) Application name
APPL_VER1 INTEGER Major version number
APPL_VER2 INTEGER Minor version number
APPL_VER3 INTEGER Micro version number
APPL_OPER CHAR(64) The operation associated with the task
TRANSID CHAR(4) CICS transaction ID.
PROGRAM CHAR(8) Currently active CICS program.
CALLTYPE CHAR(4)

EXEC for EXEC DLI calls.
CBLT for CBLTDLI calls.
ASMT for ASMTDLI calls.
PLIT for PLITDLI calls.
FUNCTION CHAR(24) DLI command. 1
TYPE CHAR(16) PSB or PCB. 1
OBJECT CHAR(8) PSB name or PCB name.
TERMTRAN CHAR(1) Whether a terminal is associated with the transaction:
Y
Terminal transaction.
N
Nonterminal transaction.
TCBMODE CHAR(2) CICS TCB in which the application is running; for example, QR or L8.
OFFSET CHAR(8) The offset of the command from the start of the program.
PROGLEN CHAR(8) Length of CICS program. Used for program versioning.
USECOUNT INTEGER Number of occurrences.
FIRST_RUN TIMESTAMP Time of first occurrence, in the local time format.
LAST_RUN TIMESTAMP Time of last occurrence, in the local time format.
USER_DATA1 CHAR(48) Reserved.
USER_DATA2 CHAR(48) Reserved.
USER_DATA3 CHAR(48) Reserved.
Note:
  1. For more information about Function and Type, see Table 44 in Type and Function mapping for monitored commands.
CIU_MQ_DATA
This table stores information about every unique combination of CICS region, transaction, program, function, and WebSphere® MQ resource recorded by the Collector. With this table, you can answer questions such as:
  • Which WebSphere MQ resources are used by this transaction?
  • If I change this WebSphere MQ resource, which programs and transactions are affected?
Table 4. The CIU_MQ_DATA table
Column Type Description
COLLECTION_ID CHAR(16) Collection ID.
ARCHIVE_DATE TIMESTAMP Time of archiving.
APPLID CHAR(8) CICS region APPLID.
HOMESYSID CHAR(4) SYSID of local region.
Start of change PLATFORM End of change Start of change CHAR(64) End of change Start of change Platform name End of change
APPL_NAME CHAR(64) Application name
APPL_VER1 INTEGER Major version number
APPL_VER2 INTEGER Minor version number
APPL_VER3 INTEGER Micro version number
APPL_OPER CHAR(64) The operation associated with the task
TRANSID CHAR(4) CICS transaction ID.
PROGRAM CHAR(8) CICS program name.
FUNCTION CHAR(24) MQ command name, such as MQGET, MQPUT. 1 2
TYPE CHAR(16) Resource type. 1 2
OBJECT CHAR(48) Resource name. 3
QMGRNAME CHAR(48) Name of the queue manager.
TERMTRAN CHAR(1) Whether a terminal is associated with the transaction:
Y
Terminal transaction.
N
Nonterminal transaction.
TCBMODE CHAR(2) CICS TCB in which the application is running; for example, QR or L8.
OFFSET CHAR(8) The offset of the command from the start of the program.
PROGLEN CHAR(8) Length of CICS program. Used for program versioning.
MQFIQ CHAR(1) Whether the MQOO_FAIL_IF_QUIESCING option is set for the FUNCTION:
Y
Yes
N
No
MQBOO CHAR(1) Whether the MQOO_BIND_ON_OPEN option is set for the FUNCTION:
Y
Yes
N
No
USECOUNT INTEGER Number of occurrences.
FIRST_RUN TIMESTAMP Time of first occurrence,in the local time format.
LAST_RUN TIMESTAMP Time of latest observation, in the local time format.
USER_DATA1 CHAR(48) Reserved.
USER_DATA2 CHAR(48) Reserved.
USER_DATA3 CHAR(48) Reserved.
Note:
  1. If the command in the dependency data is not recognized by the database update program, both the FUNCTION and TYPE columns contain ????????.
  2. For more information about Function and Type, see Table 45 in Type and Function mapping for monitored commands.
  3. The resource name is the name of the object of the function. This column has a size of 48 bytes to accommodate the names of objects such as programs and files, but the data might occupy less space.
CIU_NATURAL_DATA
This table stores information about every unique combination of CICS region, transaction, program, function, and Natural resource recorded by the Collector.
Table 5. The CIU_NATURAL_DATA table
Column Type Description
COLLECTION_ID CHAR(16) Collection ID.
ARCHIVE_DATE TIMESTAMP Time of archiving.
APPLID CHAR(8) CICS region APPLID.
HOMESYSID CHAR(4) SYSID of local region.
Start of change PLATFORM End of change Start of change CHAR(64) End of change Start of change Platform name End of change
APPL_NAME CHAR(64) Application name
APPL_VER1 INTEGER Major version number
APPL_VER2 INTEGER Minor version number
APPL_VER3 INTEGER Micro version number
APPL_OPER CHAR(64) The operation associated with the task
TRANSID CHAR(4) CICS transaction ID.
PROGRAM CHAR(8) Current program name.
FUNCTION CHAR(8) Natural command name, such as CALL.
TYPE CHAR(8) Natural command type, such as ADABAS, PROGRAM.
OBJECT CHAR(32) Database type code (for CALL ADABAS) or calling program name (for CALL PROGRAM).
COMMAND_CODE CHAR(4) Database command code (for CALL ADABAS), such as OP, L1, CL.
COMMAND_ID CHAR(8) Database command identifier (for CALL ADABAS).
COMMAND_DESC CHAR(36) Database command descriptor (for CALL ADABAS).
PROGRAM_TYPE CHAR(16) Calling program type (for CALL PROGRAM), such as FETCH PROGRAM, MAP, CALLNAT SUBPROG, VIEW.
PROGRAM_MODE CHAR(16) Calling program mode (for CALL PROGRAM), such as STATIC, DYNAMIC.
PROGRAM_CALL CHAR(16) Calling program parameter call type (for CALL PROGRAM), such as BY VALUE, BY REFERENCE.
LOCATION CHAR(8) Calling program location (for CALL PROGRAM), such as a library name, LIBRARY (load program library), NUCLEUS (Natural shared nucleus).
DATABASE_ID INTEGER Database identifier (for CALL ADABAS) or system file database identifier (for CALL PROGRAM).
FILE_NUMBER INTEGER File number (for CALL ADABAS) or system file number (for CALL PROGRAM).
TERMTRAN CHAR(1) Whether a terminal is associated with the transaction:
Y
Terminal transaction.
N
Nonterminal transaction.
TCBMODE CHAR(2) CICS TCB in which the application is running; for example, QR or L8.
LEVEL INTEGER Current program level.
LINE CHAR(4) Current statement number.
OFFSET CHAR(8) The offset of the command from the start of the program.
PROGLEN CHAR(8) Length of the program (Natural nucleus).
USECOUNT INTEGER Number of occurrences.
FIRST_RUN TIMESTAMP Time of first occurrence, in the local time format.
LAST_RUN TIMESTAMP Time of latest observation, in the local time format.
USER_DATA1 CHAR(48) Reserved.
USER_DATA2 CHAR(48) Reserved.
USER_DATA3 CHAR(48) Reserved.
Note: For more information about Function and Type, see Table 46 in Type and Function mapping for monitored commands.
Parent topic: The structure of the Dependency database objects