Utilities: IEBGENER Cataloged Procedure

To simplify using the IEBGENER program for basic copy jobs, there is a local cataloged procedure also named IEBGENER. Using this procedure, the basic IEBGENER job consists of the JCL shown in Figure 1. You must supply the information for the DD statements.

//GENERJOB JOB (,,time,lines),'your name',CLASS=class
/*ROUTE  PRINT node.location
...setup statement(s) if needed...
//  EXEC  IEBGENER
//SYSUT1   DD  input data set
//SYSUT2   DD  output data set

In all IEBGENER jobs,

If the output data set is being created (DISP=NEW) and you do not specify DCB attributes, the input data set's DCB attributes are used by default. For this reason, if the output is to a printer you should always code the DCB attributes on the SYSUT2 statement since these require unblocked records.

In all examples shown in this document, the logical record lengths (LRECL) of the input and output data sets must be the same. (If you want to use IEBGENER's editing features to change the LRECL, refer to IBM's documentation.)

You can use the IEBGENER cataloged procedure to re-block a data set. You can specify a different block size (BLKSIZE) on the SYSUT2 DD statement from that on the SYSUT1 statement. This is useful when copying from one type of device to another (e.g., from tape to disk) to make the blocking factor more efficient for the output data set. For fixed-length records, the output BLKSIZE must be a multiple of the logical record length (LRECL).

When copying to a printer, the output BLKSIZE should always equal the LRECL (that is, unblocked records). If the BLKSIZE is greater than the LRECL, only the first record of each block will be copied.

Remember to include the appropriate SETUP statement(s) when you are using cartridge or reel tapes.

All tape and disk data sets are assumed to be fixed (RECFM=F) or fixed blocked (RECFM=FB).

On standard-labeled tapes, if you catalog the data set name it must conform to CNS's data set naming conventions.

As a general rule, the SYSUT1 and SYSUT2 DD statements can be in any order.

This job copies a cataloged OS disk data set named UF.userid.DISKDATA to the first file on tape MYTAPE and names it TAPEFILE. MYTAPE is a standard-labeled, cartridge tape. Since no DCB attributes appear on SYSUT2, the tape file will have the same DCB attributes as the disk data set. This job creates a new first file on the tape, so if any other files previously existed on the tape, they will be lost.

//TOTAPE JOB (,,time,lines),'your name',CLASS=class
/*ROUTE  PRINT node.location
/*SETUP TAPEC,1
// EXEC IEBGENER
//SYSUT1  DD DSN=UF.userid.DISKDATA,DISP=SHR
//SYSUT2  DD DSN=TAPEFILE,UNIT=TAPEC,
//           DISP=(NEW,KEEP),
//           VOL=SER=MYTAPE,LABEL=(1,SL)

This job copies the third file on the standard-labeled tape, TAPEA, to the first file on the non-labeled tape, TAPEB. The DCB attributes for the output tape file are the same as those of the input tape file. The input tape file and the output tape file may never reside on the same tape.

//SLTONL JOB (,,time,lines),'your name',CLASS=class
/*ROUTE  PRINT node.location
/*SETUP TAPEC,1
/*SETUP TAPE9,1
//  EXEC IEBGENER
//SYSUT1 DD DSN=ACCTS,DISP=SHR,UNIT=TAPEC,LABEL=(3,SL),
//       VOL=SER=TAPEA
//SYSUT2 DD UNIT=TAPE9,DISP=(NEW,KEEP),VOL=SER=TAPEB,
//       LABEL=(1,NL)

This job copies file 4 of the non-labeled tape, TAPENL, to file 2 of standard-labeled tape, TAPESL, and names it NEW.FILE. The DCB attributes must be specified for the input tape because the attributes are not stored with the data set as they are on SL tapes. The new output data set is reblocked to a block size (BLKSIZE) of 6160. Both 6400 and 6160 are multiples of the logical record length of 80.

//REBLK JOB (,,time,lines),'your name',CLASS=class
/*ROUTE  PRINT node.location
/*SETUP TAPEC,2
// EXEC IEBGENER
//SYSUT1 DD VOL=SER=TAPENL,UNIT=TAPEC,DISP=OLD,LABEL=(4,NL),
//       DCB=(RECFM=FB,LRECL=80,BLKSIZE=6400)
//SYSUT2 DD DSN=NEW.FILE,UNIT=TAPEC,DISP=(NEW,KEEP),
//       LABEL=(2,SL),VOL=SER=TAPESL,
//       DCB=(RECFM=FB,LRECL=80,BLKSIZE=6160)

In this job, file 2 (MYPROG) of 9-track, standard-labeled tape TAPOLD is copied to a new member of an existing PDS. The new member is named NEWMEM. Because the PDS already exists, the DISP parameter is DISP=OLD, even though the member is new. DCB attributes are not specified for the output data set. Because it is an existing data set, it already has attributes associated with it, and these are used. If the pre-existing DCB attributes are not the same as the input data set's, they must conform to reblocking restrictions; that is, the BLKSIZE must be a multiple of the LRECL.

//SLTOPDS JOB (,,time,lines),'your name',CLASS=class
/*ROUTE  PRINT node.location
/*SETUP TAPE9,1
// EXEC IEBGENER
//SYSUT2  DD  DSN=UF.userid.PDS(NEWMEM),DISP=OLD
//SYSUT1  DD  DSN=MYPROG,UNIT=TAPE9,VOL=SER=TAPOLD,
//        DISP=OLD,LABEL=(2,SL)

Member MYPROG of the partitioned data set UF.userid.PROGRAMS.SOURCE is sent to a line printer. The LRECL of the input data set and the output data set must be the same. When a line printer is used as the output device, DCB attributes should always be specified and the LRECL cannot be greater than 133. In this example, it is assumed that the input data set does not have carriage control characters. For an example with carriage control, see below.

//TOPRT JOB (,,time,lines),'your name',CLASS=class
/*ROUTE  PRINT node.location
// EXEC IEBGENER
//SYSUT2  DD SYSOUT=A,DCB=(RECFM=F,LRECL=80,BLKSIZE=80)
//SYSUT1  DD DSN=UF.userid.PROGRAMS.SOURCE(MYPROG),DISP=SHR

Assume that disk data set UF.userid.RESEARCH.TEXT is a text file that contains carriage control characters in column 1 for printing to a line printer. The output RECFM should be FA, which means that the character in column 1 of each record (line) is interpreted as a carriage control character. Carriage control characters are used to control line skips and top-of-form in printing text and other readable documents. You should specify carriage control ONLY when you know that carriage control characters are included in the file you are copying. If the data set or file which you have copied to a printer does not contain readable data or carriage control characters in column 1, IEBGENER will attempt to print it anyway, producing a lot of garbage and wasted paper.

//TOPRTCC JOB (,,time,lines),'your name',CLASS=class 
/*ROUTE  PRINT node.location
// EXEC  IEBGENER
//SYSUT1 DD DSN=UF.userid.RESEARCH.TEXT,DISP=SHR
//SYSUT2 DD SYSOUT=A,DCB=(RECFM=FA,LRECL=133,BLKSIZE=133)

This job concatenates the disk data set UF.userid.FILE6 with disk data set UF.userid.FILE2 and copies the result to file 1 of the standard-labeled tape TAPEC, naming it UF.userid.NEWFILE. The input disk data sets must have the same RECFM and LRECL and reside on the same type devices. The output data set that is being created has no DCB attributes specified, so the attributes of the input data sets are used.

//CATCPY JOB (,,time,lines),'your name',CLASS=class
/*ROUTE  PRINT node.location
/*SETUP TAPEC,1
// EXEC IEBGENER
//SYSUT2  DD  DSN=UF.userid.NEWFILE,
//            UNIT=TAPEC,DISP=(NEW,CATLG),
//            LABEL=(1,SL),VOL=SER=MYTAPE
//SYSUT1  DD  DSN=UF.userid.FILE6,DISP=SHR
//        DD  DSN=UF.userid.FILE2,DISP=SHR

If you have questions about the IEBGENER program or the local IEBGENER cataloged procedure, please call the CNS Support Desk at (352) 392-2061, or send e-mail to consult@lists.ufl.edu.

See the CNS General Information: CNS Software and Software References document (D0009) for a list of recommended references on IBM utilities, JCL, and z/OS (OS/390) batch jobs.

For information about using OS data sets, see CNS DOCWEB document D0045, z/OS (OS/390) Disk Data Sets at CNS: Utilities for z/OS (OS/390) Disk Data Sets.

For information about using magnetic tapes, see CNS DOCWEB document D0017, Using Magnetic Tapes at CNS: Utilities for Magnetic Tapes.

There are also DOCWEB documents for various other local utilities and procedures.