Preparing CSV files

Before you can update a CICS® IA UDB database with new data, you need to convert the VSAM files that are created by the Collector to the QSAM flat files or, in other words, comma-separated values (CSV) files.

CICS® IA provides the following batch jobs that you can use for managing tables:

hlq.SCIUSAMP.UDB(CIUUDB): Prepares QSAM CSV files for all Dependency tables, including the DETAILED tables.
Note:

If you are not collecting Db2® data, you can remove step STEP050 through STEP074.

If you are not collecting MQ data, you can remove step STEP075 through STEP094.

If you are not collecting IMS™ data, you can remove step STEP095 through STEP112.
hlq.SCIUSAMP.UDB(CIUUDB4): Prepares QSAM CSV files for the CIU_CMDFLOW_DATA and CIU_CMDFLOW_INDEX tables.
hlq.SCIUSAMP.UDB(CIUUDBAF): Prepares QSAM CSV files for the CIU_REGION_INFO and CIU_AFF_EVENTS tables.
hlq.SCIUSAMP.UDB(CIUUDBAP): Prepares QSAM CSV files for the CIU_APPLS_RESOURCE and CIU_APPLS_DESC tables.
hlq.SCIUSAMP.UDB(CIUUDBCS): Prepares QSAM CSV files for the CIU_CSECT_INFO and CIU_PROGRAM_INFO tables.
hlq.SCIUSAMP.UDB(CIUUDBSD): Prepares QSAM CSV file for the CIU_SCAN_DETAIL table.
hlq.SCIUSAMP.UDB(CIUUDBSS): Prepares QSAM CSV file for the CIU_SCAN_SUMMARY table.

When you create CSV files using the CIUUDB, CIUUDB4 and CIUUDBAF jobs, you should set the variable UDBPARM before the jobs start. The possible values are:

NOCONV (default). CSV files are created in readable form and can NOT be used for loading into the CICS IA UDB.
CONV. CSV files are encoded for loading into the CICS IA UDB.

When you create CSV files using the CIUUDB4 job, you should set the variable UDBPARM before the job starts. The possible values are:

Header variable ‘0’ (default) - generates the .CSV file without the header.
Set the header variable as ‘1’-generates the .CSV file with the header fields.

When you create a new CSV file for the Dependency tables, you can associate the collection by using the COLLECTION_ID column in the tables. You can use the same COLLECTION_ID for each load or select a new one, which is recommended in case of major changes in your application or environment. The CICS® IA Explorer plug-in allows you to compare resources across COLLECTION_IDs. You can also manage your CICS® IA data by COLLECTION_ID: for example, delete it from a table.

Note:

Do not change the length of the collection ID in these samples. It must be 16 characters long.

Table 1. Relationships between the CSV files and the corresponding Db2® tables and the sample jobs that create the CSV files.
Sample Job	CSV file	Db2® table
CIUUDB	CICS®.CSV	CIU_CICS_DATA
	IBM® Db2®.CSV	CIU_DB2_DATA
	MQ.CSV	CIU_MQ_DATA
	IMS®.CSV	CIU_IMS_DATA
	WEBSERV.CSV	CIU_WEBSERV_DETAIL
	FILE.CSV	CIU_FILE_DETAIL
	PROGRAM.CSV	CIU_PROGRAM_DETAIL
	TRANSID.CSV	CIU_TRANSID_DETAIL
	TDQUEUE.CSV	CIU_TDQUEUE_DETAIL
	TSQUEUE.CSV	CIU_TSQUEUE_DETAIL
	EXIT.CSV	CIU_EXIT_INFO
	EVENT.CSV	CIU_EVENT_DETAIL
	NATURAL.CSV	CIU_NATURAL_DATA
	REGION.CSV	CIU_REGION_INFO
	CONN.CSV	CIU_CONNECTIONS

CIUUDBAF	REGION.CSV	CIU_REGION_INFO
	AFFINITY.CSV	CIU_AFF_EVENTS

CIUUDBAP	APPL1.CSV	CIU_APPLS_DESC
	APPL2.CSV	CIU_APPLS_RESOURCE

CIUUDB4	CMDFLOW.CSV	CIU_CMDFLOW_DATA
	CMDINDEX.CSV	CIU_CMDFLOW_INDEX

CIUUDBCS	CSPROG.CSV	CIU_PROGRAM_INFO
	CSECT.CSV	CIU_CSECT_INFO

CIUUDBSD	SCANDET.CSV	CIU_SCAN_DETAIL

CIUUDBSS	SCANSUM.CSV	CIU_SCAN_SUMMARY