Load Module Scanner base tables

This section describes the Load Module Scanner base tables defined in the database. You can write your own SQL applications to query the tables; these applications must use native SQL queries to do this.

CIU_SCAN_SUMMARY
This table stores summary information about every module in the load libraries that have been scanned.
Table 1. The CIU_SCAN_SUMMARY table
Column Type Description
DSNAME CHAR(44) Data set name
PROGRAM CHAR(8) Module name
LANGUAGE CHAR(10) Programming language detected
LE CHAR(7) Language Environment (LE) detected
CICS_OR_BATCH CHAR(5) CICS® transaction or batch
AFFINITY_COUNT INTEGER Number of commands with potential to create affinities
MVS_POST_COUNT INTEGER Number of MVS™ POST commands
DEPENDENCY_COUNT INTEGER Number of commands with potential to create dependencies
CIU_SCAN_DETAIL
This table records detailed information about every command, in specified modules of the load libraries that have been scanned, that has the potential to create a resource dependency or a transaction affinity.
Table 2. The CIU_SCAN_DETAIL table
Column Type Description
DSNAME CHAR(44) Data set name
PROGRAM CHAR(8) Module name
OFFSET INTEGER Offset, from the start of the program, at which this command occurs
COMMAND CHAR(24) EXEC CICS command or MVS POST
RESOURCE_TYPE CHAR(16) Resource type; for example, program
AFFINITY CHAR(1) Whether this command has the potential to create an affinity:
Y
Yes
N
No
AFFINITY_TYPE CHAR(2) The type of affinity:
IT
Inter-transaction
TS
Transaction-system
DEPENDENCY CHAR(1) Whether this command has the potential to create a dependency:
Y
Yes
N
No
MVS_POST CHAR(1) Whether this command is a possible MVS POST:
Y
Yes
N
No
COMMAND_HEX CHAR(50) Data at the command offset, shown in hexadecimal
V_CIU_SCAN_TRDSAFE
This view is a simple join between the CIU_SCAN_DETAIL table and the CIU_THREADSAFE_CMD table using the COMMAND and RESOURCE_TYPE fields from each table. This table is used to query, by CICS TS release, which commands in the CIU_SCAN_DETAIL table are threadsafe, non-threadsafe, or indeterminate-threadsafe.
Table 3. The V_CIU_SCAN_TRDSAFE table
Column Type Description
DSNAME CHAR(44) Data set name
PROGRAM CHAR(8) Module name
LANGUAGE CHAR(10) Programming language detected
LE CHAR(7) Language Environment (LE) detected
CICS_OR_BATCH CHAR(5) CICS transaction or batch
AFFINITY_COUNT INTEGER Resource type; for example, program
MVS_POST_COUNT INTEGER Number of MVS POST commands
DEPENDENCY_COUNT INTEGER Number of commands with potential to create dependencies
CICS_TS22 CHAR(1) Indicates the threadsafe status if the command is for CICS TS V2.2. Values are:
Y
command is threadsafe
N
command is not threadsafe
I
command is indeterminate threadsafe
CICS_TS23 CHAR(1) Indicates the threadsafe status if the command is for CICS TS V2.3. Values are:
Y
command is threadsafe
N
command is not threadsafe
I
command is indeterminate threadsafe
CICS_TS31 CHAR(1) Indicates the threadsafe status if the command is for CICS TS V3.1. Values are:
Y
command is threadsafe
N
command is not threadsafe
I
command is indeterminate threadsafe
CICS_TS32 CHAR(1) Indicates the threadsafe status if the command is for CICS TS V3.2. Values are:
Y
command is threadsafe
N
command is not threadsafe
I
command is indeterminate threadsafe