CICS VT supports a subset of IDCAMS PRINT and REPRO functions. There is no support for other IDCAMS functions.
You can use PRINT with a CICS® VT migrated data set. The following PRINT options are supported:
Using a CICS VT migrated file as INFILE, the following REPRO options are supported:
Using a CICS VT migrated file as OUTFILE requires an additional DD statement if either REPLACE or REUSE is specified. In addition, the LRECL parameter must be added to the output DD statement. Figure 1 shows sample JCL for IDCAMS with REPRO REPLACE.
//REPLT EXEC PGM=IDCAMS,REGION=0M
//STEPLIB DD DISP=SHR,DSN=CICSVT.TEST.DRIVERS
// DD DISP=SHR,DSN=CICSVT.TEST.EXIT.LOAD
// DD DISP=SHR,DSN=VID.VIDLOAD
// DD DSN=SYS1.LINKLIB,DISP=SHR
//SYSPRINT DD SYSOUT=*
//IDCIN DD DISP=SHR,DSN=CICSVT.TEST.DIMREPL.INPUT
//IDCOUT@ DD DISP=SHR,DSN=CICSVT.TEST.DIMREPL.DUMMY
//IDCOUT DD DISP=SHR,SUBSYS=(VIDZ,DB2B,DIMREPL),LRECL=llll
//
//SYSIN DD *
REPRO INFILE(IDCIN) OUTFILE(IDCOUT) REPLACE SKIP(2) COUNT(4)
//VIDIDCIN DD *
DIMREPL REPLACE
The additional DD statement required for REPRO REPLACE or REUSE is VIDIDCIN. The format of the input is:
dim-name REPLACE or
dim-name REUSE
The LRECL value llll must be the length of the longest record in the input file + 4.
You can specify multiple VIDIDCIN input statements, but you can only specify a dim-name once. For example, assume that you are using IDCAMS to copy two input sequential data sets to the same output VSAM file as follows:
REPRO INFILE(IDCIN1) OUTFILE(IDCOUT) REUSE
REPRO INFILE(IDCIN2) OUTFILE(IDCOUT) REPLACE
Without CICS VT, the VSAM file contains only those records from IDCIN1 after the first REPRO statement is processed. After the second REPRO statement is processed, the VSAM file contains a combination of updated and new records from IDCIN2. With CICS VT, you must split this into separate job steps. The first job step will have the first REPRO statement and the VIDIDCIN statement will be:
dim-name REUSE
VIDIDCIN for the second job step will be:
dim-name REPLACE
Multiple REPRO statements in the same job step but for different VSAM files is supported.