CICS VSAM Transparency for z/OS, Version 1.2


Testing exits like MULTIRD and MULTFBE

There is no CICS® VT stand-alone test facility for an IRD or FBE.

The initial testing occurs during data migration. The migration steps are as follows:

Unload the VSAM file

Use the standard VIDUNLOD utility to unload your VSAM file to a sequential data set. The exits are not executed during this process.

Run the VIDLOAD utility

The VIDLOAD utility creates the file for loading to DB2®. The IRD is invoked to build the records to be loaded to the secondary tables. If you have field level FBEs, these will be tested as well.

You can use CICS VT tracing to help to debug field level FBEs, but the trace will not show any of the data built by an IRD like MULTIRD. You can browse the LOADOUTM data set to review the effects of the IRD.

If you save the VIDLOAD input file, you can rerun it multiple times to help with debugging. You can also use COBOL DISPLAYs or PL/I PUTs.

Run the DB2 load utility

This is the biggest test for an IRD like MULTIRD. If the exit is not building the data correctly, packed decimal and date fields may be in error. The DB2 load utility abends in this case.
Below are the typical error messages you will see if you have invalid packed decimal or date data:
  • DSNU334I with error code = 04 indicates an invalid packed decimal value
  • DSNU334I with error code = 14 indicates an invalid date or time value

Run the VIDREAD utility with DMF

When the data is loaded to DB2, run the VIDREAD utility with dual mode facility (DMF) active. This tests exits like MULTFBE. It also tests any field level FBEs.

You can use CICS VT tracing to help with debugging.

If you are dealing with large data volumes, limit the volume of tracing with the TRACSET trace parameter.

Verify DB2 access paths

When you have successfully migrated the data to DB2, and successfully read it with VIDREAD, check that the SQL in your exits is efficient. REBIND the DB2 packages for exits that contain SQL and specify EXPLAIN(YES).

Review the output that is generated to the PLAN_TABLE. A tablespace scan or any form of sorting indicates an issue with either your SQL or a DB2 table or index definition. You should also check that the attributes of host variable fields are consistent with the associated DB2 column data type.



Concept topic


Last updated: May 25, 2012 20:46:3