z/OS DFSMSrmm Implementation and Customization Guide
Previous topic | Next topic | Contents | Contact z/OS | Library | PDF


JCL for EDGINERS

z/OS DFSMSrmm Implementation and Customization Guide
SC23-6874-00

Figure 1 shows sample JCL for automatic processing.

Figure 1. JCL for EDGINERS automatic processing
//INIT     EXEC PGM=EDGINERS,
//              PARM='MEDIANAME(3480),VERIFY'
//SYSPRINT DD   program message data set
//TAPE     DD   UNIT=(TAPE,,DEFER)

Figure 2 shows sample JCL for manual processing.

Figure 2. JCL for EDGINERS manual processing
//INIT     EXEC PGM=EDGINERS
//SYSPRINT DD   program message data set
//TAPE     DD   UNIT=(TAPE,,DEFER)
//SYSIN    DD   optional control command input

The SYSPRINT DD statement is always required. It contains all the messages issued by EDGINERS processing, even when processing uses the operator console for input. The messages issued by EDGINERS are normally written both to SYSPRINT and as a WTO message to the job log, console, and syslog. Some messages issued as WTO are truncated because of the message length limits, but the complete message text is available in the SYSPRINT file.

The TAPE DD statement is only required if any of the volumes to be processed are not in a system-managed tape library.

Figure 3 shows sample JCL for initializing volumes with ISO/ANSI version 4 tape labels. The EXEC JCL statement can be overridden by control information from SYSIN, operator replies to messages, or information from the DFSMSrmm control data set.

Figure 3. JCL for initializing volumes with ISO/ANSI Version 4 VOL1 and HDR1 labels
//INIT     EXEC PGM=EDGINERS,PARM='..,ALVER4,...'
//SYSPRINT DD   SYSOUT=A
//SYSIN    DD   DUMMY

Go to the previous page Go to the next page




Copyright IBM Corporation 1990, 2014