CICS VSAM Transparency for z/OS, Version 1.2


Mapping a VSAM file to CICS VT manually

This section explains how to manually map a VSAM file to CICS® VT.

You can map many files using the automated mapper, but in certain circumstances it may be necessary to modify generated mapping. For example, if you encounter inconsistent numeric data during the data migration phase, one solution is to change the field type to character and make the DB2 column type CHAR. Another solution is to correct the inconsistent data in VSAM. You must use the manual mapping dialogs if you need to make changes to the generated mapping.

Because of the potential need to change mapping, it is important to understand the manual mapping process. (For details of the automated mapping method, see The automated mapping facility ).

There are some slight differences in the way that a KSDS data set is mapped compared to an RRDS data set. The screens and explanation that follow apply to a KSDS data set. The differences when mapping an RRDS data set are detailed in Mapping an RRDS data set . The automated mapping facility handles the differences for you.

Alternate index paths must be mapped, although the mapping process is different from mapping base cluster data sets. Alternate index mapping is covered in Mapping alternate indexes .





Last updated: December 6, 2013 20:43:13

Information Information

Feedback


Timestamp icon Last updated: Friday, 6 December 2013


http://pic.dhe.ibm.com/infocenter/cicsts/v5r1/topic///topics/cvtug_mapping_manual.html