Activating BetterGener provides additional “IEBGENER” editing capability by permitting the inclusion of the $ORTPARM DD statement in IEBGENER job streams. In order for the contents of the $ORTPARM data set to affect the copy execution, the copy must be done through MFX; if SYNCGENR transfers control to IEBGENER, the $ORTPARM DD statement is ignored. Therefore, whenever MFX file editing is crucial to a copy application, explicit FIELDS=COPY MFX coding should be used. Here is an example of such a jobstream:
Sample Job Where MFX Must Be Used
In this example, $ORTPARM acts to right-pad the first (8-byte) field of the record with 10 blanks, truncating the final 10 bytes, if MFX is executed. If, however, BetterGener routes the job back to IEBGENER, no padding or truncation is done.