DD statements for the Image Copy function (DFSUDMP0 JCL)
DD statements are used to identify the source of input and the placement of output information. The following DD statements are supported for the Image Copy function that is called from IMS compatible JCL.
DDNAME | Use | Format | Required or optional |
---|---|---|---|
STEPLIB | Input | PDS | Optional |
DFSRESLB | Input | PDS | Optional |
IMS | Input | PDS | Required (See Note 1) |
SYSPRINT | Output | SYSOUT | Required |
SYSIN | Input | LRECL=80 | Required |
datain | Input | Required | |
dataout1 | Output | VBS (See Note 2) | Required |
dataout2 | Output | VBS (See Note 2) | Optional |
SYSABEND or SYSUDUMP | Output | N/A | Optional |
RECON1 | Input/output | KSDS | Optional |
RECON2 | Input/output | KSDS | Optional |
RECON3 | Input/output | KSDS | Optional |
Notes:
|
- STEPLIB DD
- This statement points to two load module library data sets. The data sets must be in the
following sequence:
//STEPLIB DD DISP=SHR,DSN=HPS.SHPSLMD0 // DD DISP=SHR,DSN=IMS.SDFSRESL
where:
- HPS.SHPSLMD0
- The name of the library that contains the load modules of IMS HP Image Copy.
- IMS.SDFSRESL
- The name of the library that contains the IMS nucleus and required action modules.
To enable IMS-managed ACBs, you must include the IMS Tools Generic Exits library in the STEPLIB concatenation.
To use IMS HP Image Copy site default table, you must specify the library that contains the IMS HP Image Copy site default table.
If STEPLIB is unauthorized because it specifies libraries concatenated to IMS.SDFSRESL, you must specify a DFSRESLB DD statement.
- DFSRESLB DD
- This statement points to an authorized library that contains the IMS SVC modules.
- IMS DD
- This statement defines the library that contains the DBD describing the database to dump,
generally DSNAME=IMS.DBDLIB. The data set must reside on a direct-access volume.
This statement is not required when the IMS management ACBs is enabled.
- SYSPRINT DD
- This statement defines the output messages data set. The data set can reside on a tape, a direct-access volume, or a printer, or it can be routed through the output stream (SYSOUT). SYSPRINT can be blocked but must be a multiple of 121.
- SYSIN DD
- This statement defines the input control statement data set. The data set can reside on a tape or a direct-access volume, or it can be routed through the input steam (DD * or DD DATA).
- datain DD
- This statement defines the input data set to be dumped. The ddname on this statement must be the
same as the one in the DBD that describes this data set. The ddname must also appear in the utility
control statement. One DD statement of this type must be present for each data set that is dumped.
The data set must reside on a direct-access volume.
If the buffer size specifications are omitted, the Image Copy function allocates the optimized data buffer for VSAM or OSAM data sets. You can modify the buffer size by specifying:
- The data set's BUFFERSPACE
- The BUFSP/BUFND in the AMP parameter on the DD statement for OSAM
- The BUFNO in the DCB parameter on the DD statement
The Image Copy function requests that VSAM data buffers and VSAM control blocks reside in virtual storage above 16 MB. OSAM data buffers are obtained above 16 MB in the DFSMS/MVS environment, and below 16 MB in the DFP environment.
The minimum block size for the data set is 69; smaller data sets are padded with blanks.
- dataout1 DD
- This statement defines the first copy of the dumped output data set. One DD statement is
required for each data set to be dumped. The ddname can be any 1- to 8-character string, but the
ddname must appear in the associated utility control statement. The output device must be either
direct access or tape. Standard labels must be used. If the track size of the output direct-access
device exceeds 32 KB and no DCB is explicitly specified, the BLKSIZE where multiple blocks can
reside in a track is used as the default value, unless the database record length is larger than the
capacity of a half track. If BLKSIZE is specified in the JCL, that BLKSIZE is used.
The Image Copy function allocates the optimized data buffer for OSAM data sets, if the buffer size parameter is omitted. You can modify the buffer size by specifying:
- The BUFNO in the DCB parameter of the DD statement
OSAM data buffers are obtained above 16 MB in the DFSMS environment, and below 16 MB in the DFP environment.
- dataout2 DD
- This statement is required only if the associated utility control statement requests two copies
of the dump. The name must appear in the control statement. The name must be either that of the tape
or the direct-access device. Standard labels must be used. If the track size of the output
direct-access device exceeds 32 KB and no DCB is explicitly specified, the BLKSIZE where multiple
blocks can reside in a track is used as the default value, unless the database record length is
larger than the capacity of a half track. If BLKSIZE is specified in the JCL, that BLKSIZE is used.
The Image Copy function calculates the optimized data buffer for OSAM data sets, if the buffer size parameter is omitted. You can modify the buffer size by specifying:
- The BUFNO in the DCB parameter of the DD statement
OSAM data buffers are obtained above 16 MB in the DFSMS environment, and below 16 MB in the DFP environment.
If either of the two output copies has an "open" problem (message DFS301A) or fails the first PUT operation to either output data set (message DFS319A), the current control statement is terminated and the next control statement is processed.
Once the utility processes the first PUT, all I/O errors to either output data set return a code of 08, and the utility continues to copy to the remaining output data set. Each image copy control statement is treated as an independent copy, with the final return code being the highest received for the job.
- SYSABEND DD
- SYSUDUMP DD
- These statements define a dump data set. If both statements are present, the last occurrence is used for the dump.
- RECON1 DD
- RECON2 DD
- RECON3 DD
- These statements define the DBRC RECON data sets. These RECON data sets must be the RECON data sets used by the control region. Do not specify these RECON data set DD statements if you want RECON data sets allocated dynamically using the DFSMDA macro.