IEBGENER

IEBGENER is basically a copy utility which copies records from a sequential dataset, or creates a partitioned dataset

you can use IEBGENER to

  • Create a backup copy of a sequential data set or a member of a PDS.
  • Produce a PDS, or a member of a partitioned data set, from a sequential data set or an HFS file.
  • Expand an existing partitioned data set by creating partitioned members and merging them into the existing data set.
  • Produce an edited sequential or partitioned data set or PDSE.
  • Manipulate data sets containing double-byte character set data.
  • Print sequential data sets, members of partitioned data sets or PDSEs or HFS files.
  • Reblock or change the logical record length of a data set.
  • Copy user labels on sequential output data sets.
  • Supply editing facilities and exits for your routines that process labels, manipulate input data, create keys, and handle permanent input/output errors.

If you have the DFSORT product installed, you should be using ICEGENER as an alternative to IEBGENER.It generally gives better performance



Sample JCL

			
		//IEBGENER JOB  ACCT,'IEBGENER',MSGCLASS=X,CLASS=D
		//STEP001  EXEC PGM=IEBGENER                   
		//SYSUT1   DD DSN=XXXX.XXXX.XXXX.XXXX,
		//            DISP=SHR 
		//SYSUT2   DD DSN=YYYY.YYYY.YYYY.YYYY,
		//            DISP=(NEW,CATLG,DELETE), 
		//            UNIT=SYSDA,SPACE=(TRK,(5,5),RLSE),
		//            DCB=(RECFM=FB,LRECL=1440) 
		//SYSPRINT  DD SYSOUT=*                        
		//SYSIN      DD DUMMY 
		


JCL Control Statements

SYSPRINT DD Statement

  • The SYSPRINT DD statement is required for each use of IEBGENER.
  • The block size for the SYSPRINT data set must be a multiple of 121.
  • Any blocking factor can be specified for this record size, but the maximum value for the block size is 32670 bytes.

SYSUT1 DD Statement

  • The input data set for IEBGENER, as specified in SYSUT1, can contain fixed,variable, undefined, or variable spanned records.
  • The default record format is undefined (U) for the input data set. Record format must be specified if the data set is new, undefined, or a dummy data set.

SYSUT2 DD Statement

  • The output data set for IEBGENER, as specified in SYSUT2, can contain fixed, variable, undefined, or variable spanned records

SYSIN DD Statement

  • The SYSIN DD statement is required for each use of IEBGENER.
  • The block size for the SYSIN data set must be a multiple of 80.
  • Any blocking factor can be specified for this block size.
  • If SYSIN is dummy, IEBGENER copies the input data set sequentually.


Utility Control Statements

  • GENERATE
  • EXITS
  • LABELS
  • MEMBER
  • RECORD

Return Codes

00

Successful completion

04

Probable successful completion. A warning message is written

08

Either processing was ended after you requested processing of user header labels only, or a DBCS error was encountered

12

Either an unrecoverable error exists and the job step is stopped, or a DBCS error was encountered

16

A user routine passed a return code of 16 to IEBGENER. The utility ends


Error Codes:

IEB311I - CONFLICTING DCB PARAMETERS

The DCB parameters in the SYSUT2 DD statement are not compatible with those specified in the SYSUT1 DD statement. The reason for incompatibility could be one of the following:

  • The I/O blocksize is inconsistent with the I/O logical record length when the record format is FB or F
  • The I/O blocksize is not at least 4 bytes larger than the I/O logical record length when the record format is VB or V
  • The output logical record length is different from the input logic record length or the input record format is variable and the output record format is fixed when editing is not specified.
  • The output blocksize is not equal to the input blocksize when the input record format is undefined.

Examples

suggestion / complaint / feedback Web Statistics