JCL and Sample JCL/Control Statement Streams - mfx

JCL and Sample JCL/Control Statement Streams - mfx - 3.1

Syncsort™ MFX Programmers Guide

Product type

Software

Portfolio

Integrate

Product family

Syncsort™ Software

Product

Syncsort™ MFX > MFX

Version

3.1

Language

English

Content type

Programmer’s Guide

Product name

Syncsort™ MFX

Title

Syncsort™ MFX Programmers Guide

2024

First publish date

2010

Last updated

2024-08-27

Published on

2024-08-27T08:14:56.318001

MFX’s job control statements follow the standard operating system conventions described in the z/OS job control language manuals. Each program application therefore requires a JOB statement, an EXEC statement, and a DD (data definition) statement for every data set used. (The single exception to this is the dynamic allocation of work files via DYNALLOC or DYNATAPE.) The inclusion and coding requirements of particular job control statements depend on such factors as whether MFX is program-invoked or initiated directly, whether any exits are coded, and, of course, whether the sorting technique requested is Disk Sort, MAXSORT, or PARASORT.

All aspects of program initiation which are specific to the sort/merge (such as the dedicated DD names SORTIN and SORTOUT) are documented in this section. For complete coding instructions, refer to a z/OS MVS JCL reference manual. Product is compatible with data sets allocated on Extended Address Volumes (EAV), where a volume has more than 65,520 cylinders.

The following table summarizes MFX’s DD statement requirements.

Table 1. MFX DD Statements
//STEPLIB DD //JOBLIB DD	Instructs operating system to look for the sort program in a specified data set.
//SYSOUT DD	Message data set. Required unless all messages are routed to console.
//SORTIN DD	Defines the input data set for a SORT or COPY application. Required unless it is a join application or there is an E15 exit routine. Ignored if the invoking program supplies an inline E15 exit routine; optional if the MODS statement activates an E15 exit routine.
//SORTINnn DD //SORTINn DD	MERGE input data set. Required unless there is an E32. SORTINnn DD statements are not processed when FIELDS=COPY is specified.
//SORTJNF1 DD //SORTJNF2 DD	Join application input data sets. Required for join application.
//SORTOUT DD	Output data set. Required unless there is an E35. Ignored if the invoking program supplies an inline E35 exit routine; optional if the MODS statement activates an E35 exit routine.
//SORTOFxx DD //SORTOFx DD //fname DD	OUTFIL output data sets. One required for each FILES or FNAMES specification.
//SORTXDUP DD	Output data set of records eliminated by the DUPKEYS control statement. Required when the XDUP parameter is specified.
//SORTXSUM DD	Output data set of records eliminated by the SUM control statement. Required when the XSUM parameter is specified.
//SORTWKxx DD //SORTWKn DD	Disk work area definition. Required unless incore sort, DYNALLOC, MERGE, COPY or restarting at a MAXSORT merge breakpoint.
//SYSIN DD	Control statement data set. Used unless control statements are supplied via an invoking program parameter list.
//$ORTPARM DD	Used to override PARM or control statement information.
//SORTCKPT DD	Checkpoint data set. Required for Checkpoint-Restart.
//SORTMODS DD	Required if user exits are in SYSIN.
//SYSLIN DD //SYSLMOD DD //SYSPRINT DD	Required if user exits are to be linkage-edited at execution time.
//ddname DD	Required for exits unless the exit is inline in LINKLIB/JOBLIB/STEPLIB or in SYSIN.
//STDOUT DD //STDERR DD	Data sets for informational and error messages issued by Java during creation of PDF, HTML and RTF files via the OUTFIL OUTPUT facility.