Deleting old CICS VR V2R3 entries from RCDS

When you migrate from CICS® VR V2R3 to CICS VR V4Rx, the CICS VR program might run out of space the first time a log-of-logs scan is run with automatic deregistration turned on.

Automatic deregistration in CICS VR V2R3 did not delete a few entries that are now deleted by CICS VR V4R2 automatic deregistration. Many entries might require deletion as part of the first log-of-logs scan. The normal deletion module DWWARDJO allocates space for all entries before deleting them, and also does some checks before deleting the entries. If the RCDS has too many entries the program can run out of space or run for a long time. The solution is to use the DWWDEL program.

You can prevent the problem by performing the following steps after migration:
  1. If LOGCOPY was used in CICS VR V2R3, set the retention period for log stream copies as described in Understanding CICS VR automatic deregistration.
  2. Set DWWCON1, DWWCON2, and DWWCON3 to point to the new RCDS data sets allocated for CICS VR V4R3.
  3. Run the DWWDEL program.

Running the DWWDEL program after migration removes any data that is older than any retention period set in the RCDS.

You run the DWWDEL program only once after migration.

After running the DWWDEL program, the DWWMSG data set has the following messages:
CICSVR - CICS VSAM RECOVERY
DWW1801I RCDS Delete is started at 2004/03/17 14:21:28.
DWW1802I RCDS Delete is terminated. The number of deleted entries are cccc
Start of change
Figure 1. JCL to run the DWWDEL program
//IBMUSER  JOB. Modify the job card to fit your environment.
//DEL EXEC PGM=DWWDEL
//STEPLIB DD DISP=SHR,DSN=DWW.SDWWLOAD ! CICSVR 4.3 LIB
// DD DISP=SHR,DSN=DWW.SDWWLENU
//DWWMSG   DD SYSOUT=*
//*You need to point to your V4R3 RCDS data set names
//DWWCON1  DD DSN=CICSMVS.DWWCON1,DISP=SHR
//DWWCON2  DD DSN=CICSMVS.DWWCON2,DISP=SHR
//DWWCON3  DD DSN=CICSMVS.DWWCON3,DISP=SHR
End of change