CICS VSAM Transparency for z/OS, Version 1.2


What do I code first?

FBEs and IRDs are used in the initial data migration process. There is no stand-alone exit testing facility with CICS® VT so the first time your exits are used is during the initial data migration.

For files that you are migrating to a single DB2® table, code any FBEs and add them to the mapping, as shown in Figure 1. Generate the CICS VT drivers and then perform the data migration process.

For files that you are migrating to multiple tables, the following approach is recommended:

  1. Write the FBEs that operate at an individual field level.
  2. Write the IRD to handle the initial load process only.
  3. Migrate the data to DB2. Note that there is a special DD statement required for the VIDLOAD utility when a file is mapped to multiple DB2 tables.
  4. Write the FBE that processes the additional tables.
  5. Using the dual mode facility (DMF), test data retrieval.
  6. Add code to the IRD exit to support update calls.
  7. Test update calls.

You should use the VIDUNLOD utility to test data retrieval. Sample JCL is shown in Figure 1.

Figure 1. Sample JCL for VIDUNLOD CICS
//VIDREAD  JOB CLASS=A,MSGCLASS=X,NOTIFY=&SYSUID 
//* 
//CHECKIT EXEC PGM=VIDUNLOD,REGION=8M 
//STEPLIB  DD DSN=appl.EXIT.LOAD,DISP=SHR 
//         DD DSN=appl.DRIVERS.LOAD,DISP=SHR 
//         DD DSN=VID.SVIDLODE,DISP=SHR 
//FILEIN@  DD DISP=SHR,DSN=vsam.DUMMY.APPLCTL 
//FILEIN   DD SUBSYS=(vids,db2x,APPLCTL) 
//FILEOUT  DD DUMMY,LRECL=271,RECFM=FB 
//VIDTRCE  DD SYSOUT=* 
//VIDTRCEP DD * 
TRACE P01,P03,P04,P05,P06,P08,DIM=APPLCTL 
TRACSET CALLS=50

Consider coding a simple program to test update calls for files that use FBE and IRD exits.



Concept topic


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