//CSDJOB JOB accounting info,name,MSGLEVEL=1
//STEP1 EXEC PGM=DFHCSDUP,REGION=0M, 1
// PARM='CSD(READWRITE),PAGESIZE(60),NOCOMPAT'
//STEPLIB DD DSN=CICSTS31.SDFHLOAD,DISP=SHR
//*******************************************************************
//* If you are running DFHCSDUP with the MIGRATE command,
//* and your CICS load tables are not in CICSTS31.SDFHLOAD,
//* concatenate your own private library here:
//*******************************************************************
// DD DSN=CICSTS31.userlib.tables,DISP=SHR
//DFHCSD DD DISP=SHR,DSN=CICSTS31.DFHCSD
//SECNDCSD DD UNIT=SYSDA,DISP=SHR,DSN=CICSTS31.SECNDCSD 2
//indd DD UNIT=SYSDA,DISP=SHR,DSN=extract.input.dataset 3
//outdd DD UNIT=SYSDA,DISP=SHR,DSN=extract.output.dataset 4
5
//* or 4
//outdd DD SYSOUT=A 4
5
//SYSPRINT DD SYSOUT=A
//SYSIN DD *
DFHCSDUP commands 6
/*
//
Notes:
2 You need a DD statement for a secondary CSD if you specify the FROMCSD parameter on an APPEND, COPY, or SERVICE command. The ddname for this DD statement is the name you specify on the FROMCSD parameter. The secondary CSD must be a different data set from the primary; you must not define primary and secondary DD statements that reference the same data set.
PROGRAM
TRANSACTION
TYPETERM
XTPNAME
DSNAME
4 If you specify the EXTRACT command, you need to include the DD statements for any data sets that receive output from your extract program. The ddname is whatever ddname you define in the user program. The CICS-supplied sample programs need DD statements for the following ddnames:
program name | ddname | example DD statement |
---|---|---|
DFH$CRFx or |
CRFOUT | //CRFOUT DD SYSOUT=A |
DFH$FORx or |
FOROUT | //FOROUT DD SYSOUT=output.dataset |
DFH0CBDC | CBDOUT |
//CBDOUT DD SYSOUT=A |
5 The output data sets in these examples are opened and closed for each EXTRACT command specified in SYSIN. If you are writing the output to a sequential disk data set, specify DISP=MOD to ensure that data is not overwritten by successive EXTRACT commands. Alternatively, provided you do not specify SYSOUT on the DD statement, you can change the OPEN statement in the program (for example, in the COBOL versions, to OPEN EXTEND). For programming information about the CICS-supplied user programs, see the CICS Customization Guide.
6 Syntax
You can code commands and keywords using abbreviations and mixed case, as given in the syntax box in the description of each command. If you enter an ambiguous command or keyword, the DFHCSDUP program issues a message indicating the ambiguity.
You can specify keyword values longer than one line, if you use the continuation character (an asterisk) at the end of a line (in column 72). Subsequent lines start in column 1. For example, you can use this facility to specify XTPNAME values of up to 128 hexadecimal characters.
You can use a data set or a partitioned data set member for your commands, rather than coding them in the input stream.