Syncsort™ MFX Messages - mfx

COL 1 OR 1-15 NOT BLANK

EXPLANATION: This message is triggered by a character in column 1 of the END control statement or in columns 1-15 of a continuation statement following a statement with a character in column 72, or by a non-blank character in columns 1-15 of a sort control statement in the $ORTPARM data set. These columns must be left blank.

EXCESS CARDS

EXPLANATION: The static internal storage area is inadequate for the quantity and/or complexity of the control statements in this application. Either the minimum storage value set at installation time is too low, or insufficient storage is available in your region.

ACTION: Ask the systems programmer in charge of MFX installation to increase the minimum storage (MINCORE) value unless the storage available in the region is less than the minimum storage value. In that case, increase the storage available in the region or partition so that it at least equals the minimum storage value.

NO FLD DEFINER

EXPLANATION: The FIELDS operand was not specified on the SORT/MERGE control statement.

ERR IN DISP LENGTH VALUE

EXPLANATION: The length and displacement value of a control field is greater than 4092 (4084 for variable-length records), or less than one, or the sum of the lengths of all control fields exceeds 4092 (4084 for variable-length records).

CTL FLD ERR

EXPLANATION: An error was detected in the SORT/MERGE control statement for the data format of a control field. The format was specified for one field but not for another, or bit comparisons were specified and FORMAT=BI was not specified.

L1 NOT GIVEN

EXPLANATION: The LENGTH operand on a RECORD control statement does not contain an l₁ value.

CONTROL FIELD BEYOND RECORD

EXPLANATION: The last byte of a SORT/MERGE or JOINKEYS control field is located beyond the maximum record length specified or column 32750, or a variable-length record is shorter than the ending location of a specified SORT/MERGE or JOINKEYS control field in an execution for which this is defined as cause for MFX termination (see VLTEST). Program HISTOGRM may be used to determine the length of the shortest record in the input file.

IMPROPER EXIT

EXPLANATION: The set of legal exits depends on the sorting technique chosen. A merge or copy may not specify any Phase 1 or Phase 2 exits; a copy may not specify exit E32 or E61; and a sort or merge with data fields of Y2x or PD0 formats may not specify exit E61.

EXIT E61 REQUIRED

EXPLANATION: A SORT control statement specified "E" in the FIELDS parameter but program exit E61 was not specified on a MODS control statement.

CONTROL FIELD COLLATING ORDER E REQUIRED

EXPLANATION: Program exit E61 was specified on the MODS control statement but "E" was not specified in the FIELDS parameter of the SORT control statement.

G=ggg, B=bbb, SEGLEN=sss, BIAS=zz

EXPLANATION: The tuning information displayed is as follows:

G=ggg	ggg is the number of records that can be contained in MFX’s working virtual storage area. For variable-length records, this number is the number of segments.
B=bbb	bbb indicates the physical blocking used for intermediate storage. For fixed-length records, this number represents the blocking factor. For variable-length records, it represents the blocksize. The B value will not appear in the message for incore or turnaround sorts.
SEGLEN=sss	This value appears in the message for variable-length records, when the execution is not an incore or turnaround sort. It reflects the segment length used in MFX’s working storage during Phase 1.
BIAS=zz	zz reflects the degree of prior sequencing in the input data. The number displayed ranges from 00 to 99 indicating random to highly sequenced input. The BIAS value is not included in the message for an incore or turnaround sort, where it is 100 by definition.

REXX ENVIRONMENT UNAVAILABLE

EXPLANATION: One or more REXX exits were specified in a MODS control statement, but the required operating system and/or TSO environment is not available.

INSUFFICIENT VIRTUAL STORAGE

EXPLANATION: The amount of virtual storage available to MFX is not large enough to permit execution.

ACTION: Verify that virtual storage is specified properly. Check that the region size is sufficient for execution.

EXIT Exx INVALID OPTION

EXPLANATION: The exit routine shown in the message specified an invalid option for the modification of a DCB parameter of a sort/merge data set.

SORT CAPACITY EXCEEDED

EXPLANATION: All available intermediate storage is exhausted, including any secondary allocation. Sort processing cannot continue.

ACTION: Supply more intermediate storage (see Disk Sort Intermediate Storage Calculation Formulas) or use the MAXSORT technique.

RCD CNT OFF, IN x, OUT y

EXPLANATION: The actual number of records specified in the SIZE parameter on the SORT control statement (the IN value) was not equal to the number of records read from the input data set (the OUT value). (This comparison is made only when the SIZE parameter specifies an actual number of records.)

The actual number of records (the IN value) for FILSZ=n specified either on the SORT control statement or as a PARM option was not equal to the total number of records (the OUT value) from the input data set after any changes due to the INCLUDE/OMIT control statement, and an E14 or E15 exit routine, and SKIPREC, STOPAFT, or join processing.

E16 EXIT CALLED

EXPLANATION: Program exit E16 was entered after all available SORTWORK space was exhausted.

SUM FIELD OVERFLOW

EXPLANATION: Summing of two equally keyed records could not be done due to a numeric overflow or underflow in a defined SUM field. The WER049A critical message is issued instead of the WER049I warning message if the OVFLO=RC16 PARM or the installation parameter SUMOVFL=RC16 is in effect.

ACTION: If complete summing is desired, use the INREC control statement if possible to pad the fields with leading zeros of the proper numeric format. Adjust the SUM field and other control statement fields accordingly.

SUM FIELD OVERFLOW

EXPLANATION: Summing of two equally keyed records could not be done due to a numeric overflow or underflow in a defined SUM field.

ACTION: If complete summing is desired, use the INREC control statement if possible to pad the fields with leading zeros of the proper numeric format. Adjust the SUM field and other control statement fields accordingly.

SUM CONTROL STATEMENT IGNORED

EXPLANATION: A SUM control statement was specified in a SORT FIELDS=COPY application. Since a COPY operation does not use SORT/MERGE key fields, the specification of SUM, which operates on equally keyed records, is illogical.

ACTION: The SUM statement will be ignored, but the application should be checked for correct specification of control statements.

DIAG=hhhh,hhhh

EXPLANATION: The hexadecimal information following the DIAG keyword is likely to change from execution to execution. It is internal diagnostic information intended for use by Syncsort™ MFX personnel in Product Support.

END SYNCSORT - jobname, stepname, procstepname,DIAG=hhhh,hhhh,...

EXPLANATION: MFX has successfully completed execution. The hexadecimal information following the DIAG keyword is likely to change from execution to execution. It is internal diagnostic information intended for use by Syncsort™ MFX personnel in Precisely Support.

RCD IN x, OUT y

EXPLANATION: For a non-join application, the x represents the number of records read from the input data set(s). For a join application, the x represents the resulting number of records created by the join processing. If OUTFIL statements are not present, the y represents the number of records in the output file. If OUTFIL statements are present, the y represents the number of records available for OUTFIL processing.

INSERT x, DELETE y

EXPLANATION: The x represents the number of records inserted by user exit routines. The y represents the number of records deleted by user exit routines, SUM, and INCLUDE/OMIT control statements.

Note: For MAXSORT, these counts are cumulative for the entire MAXSORT application.

RCD LNG INVALID FOR DEVICE

EXPLANATION: The logical record length specified for a fixed-length input data set plus overhead, if any, is too large to fit on one disk track of the intermediate storage device.

I/O ERR jobname, stepname, unit address, device type, DDname, operation attempted, error description, last seek address or block count, access method.

EXPLANATION: An I/O error has occurred on the device whose address is given. I/O errors are often transient - resubmitting the job may result in a successful run. However, if the I/O error is on an input DD, the following should be checked first:

When the input consists of concatenated data sets, check that the largest blocksize is available at sort initialization. See Concatenating Input Data Sets.
If the data set is on disk and has just been created by another program, check that this program opened the data set even if no data was written to the file. The data set must be opened in order for an end-of-file mark to be written. (In the absence of an end-of-file mark, MFX will tend to read whatever was on the disk as part of the input data set, causing an I/O error.)

xxxxxx OPEN ERR

EXPLANATION: The data set shown cannot be successfully opened.

ACTION: Check for missing DD statements.

DECK STRUCTURE ERROR

EXPLANATION: The end of the SYSIN data set was reached before all user exit routines were read or an object deck was missing its first statement.

APPROX RCD CNT x

EXPLANATION: Sort capacity was exceeded, so the sort terminated. The approximate number of records processed by MFX up to this point is given.

OUT OF SEQ SORTINxx[, BLOCK y]

EXPLANATION: A record in the SORTIN data set indicated by xx is out of sequence according to the FIELDS specification on the MERGE statement. The number y of the block containing the out-of-sequence record is given if an E32 exit was not used.

E39/OUTFIL INCOMPATIBLE

EXPLANATION: The E39 exit facility may not be utilized in sorts/merges which also specify OUTFIL control statements.

ddname {TOTAL,SUBTOTAL,AVG,SUBAVG} FIELD OVERFLOW

EXPLANATION: The ddname will be SORTOUT, SORTOFxx, SORTOFx or the ddname provided by an OUTFIL FNAMES parameter. An overflow condition was generated during the TOTAL, SUBTOTAL, AVG, or SUBAVG OUTFIL function for the specified output file. All fields are totaled internally as 16-byte PD values, allowing for 31 decimal digits. A field that is to be converted to BI or FI format may not have a value greater than 20 decimal digits.

ACTION: This error is usually due to invalid data in the specified fields. Check the fields specified in the indicated parameter and check the actual data in those fields to ensure that no total will exceed 31 decimal digits. In some cases, within TRAILER2 or TRAILER3, you could change SUBTOTAL to TOTAL or SUBAVG to AVG to reduce the possibility of overflow.

MAXIMUM NUMBER OF RECORDS EXCEEDED

EXPLANATION: MFX’s default internal limit on the maximum number of records that can be sorted has been exceeded. By default, the internal limit on the number of records that can be processed for variable-length data or for a sort application that uses the EQUALS option is 4,294,967,295 records. Specify the EXTCOUNT PARM to increase the internal limit to 140,737,488,355,327 records. Fixed-length sorts without EQUALS have automatic support for the maximum number of records allowed by the EXTCOUNT PARM. For additional information, see EXTCOUNT.

{EQUALS, NOEQUALS} [,RESET] {,BALANCE, ELAP, CPU, IO} IN EFFECT

EXPLANATION: This message indicates the status of three MFX options that could affect how your data was processed. The status of the EQUALS option, primarily used to retain the sequence of equally-keyed input records, is given first. “RESET” is indicated if the RESET option was used to prevent VSAM from treating output data sets created with the REUSE option as MOD data sets. The last parameter is the optimization mode in effect, i.e., BALANCE, ELAP, CPU, or IO.

ddname: dsname [(FIRST of n)]

EXPLANATION: The ddname will be SORTIN, SORTJNF1, SORTJNF2 or SORTMInn. This informational message displays the input DD data set name. For concatenated DDs, only the first data set name will be displayed and the number of concatenations will be displayed in “FIRST of n”. For MULTIIN input, WER073I will be displayed for only the first input ddname that is read.

ddname: DSNAME=dsname

EXPLANATION: The ddname will be SORTOUT, SORTOFxx, SORTOFx or the ddname provided by an OUTFIL FNAMES parameter. This informational message displays the output DD data set name. This message will be provided for each output file specified.

INVALID TAPE TYPE IN PARM FIELD

EXPLANATION: An invalid tape type was specified for DEVIN/DEVOUT in the PARM field of the EXEC statement. MFX ignored the invalid parameter.

COBEXIT=COB2 AND COBOL E15 AND E35 EXITS FOUND IN COPY APPLICATION

EXPLANATION: A COBOL E15 and COBOL E35 may not both be specified in a copy application if the COBEXIT=COB2 installation option is in effect. Only one of the exits is permitted.

INVALID MESSAGE TYPE IN PARM FIELD

EXPLANATION: An invalid message code was specified in the PARM field of the EXEC statement or in the invoking program parameter list. MFX ignored the invalid parameter.

REXX E15 AND REXX E35 EXITS FOUND IN A COPY APPLICATION

EXPLANATION: A REXX E15 and a REXX E35 may not both be specified in a copy application. Only one of the exits is permitted.

INCOMPATIBLE LEVELS BETWEEN THE STATIC AND DYNAMIC LIBRARIES OF A COBOL OR C EXIT

EXPLANATION: When using either a C or COBOL exit, insure that the run-time dynamic Language Environment libraries are at the same or higher level than the libraries used for the compile or link-edit of the exit.

ddname INVALID DEVICE TYPE

EXPLANATION: The ddname is SORTIN, SORTINnn, SORTJNF1, SORTJNF2, SORTMInn, SORTOUT, SORTOFxx, SORTOFx or the ddname provided by an OUTFIL FNAMES parameter. This file resides on an invalid device type. Valid device types include the IBM 3380, 3390, and 9345 direct access devices and their equivalents as well as the IBM 3420, 3480, 3490, and 3590 series tape devices and their equivalents.

ddname RECFM INCOMPATIBLE WITH REPORT WRITING

EXPLANATION: The ddname will be SORTOUT, SORTOFxx, SORTOFx or the ddname provided by an OUTFIL FNAMES parameter. The RECFM specified for the file did not include the 'A' (ASA control character) specification that is required when report writing is requested.

ddname: RECFM= ;LRECL= {;BLKSIZE=,CISIZE=} [;CINV ACCESS]

EXPLANATION: The ddname will be SORTIN, SORTMInn, SORTJNF1, or SORTJNF2. This informational message lists the DCB characteristics used by MFX to process the input file. For a non-VSAM data set that is concatenated, the DCB characteristics are for the first of the concatenated data sets, except for BLKSIZE, which is the largest of all data sets in the concatenation examined at sort initialization time. For a VSAM data set, the CISIZE is provided; if control interval access was used, the CINV ACCESS portion of the message will be displayed.

MERGE INPUT: TYPE={F,V};LRECL=

EXPLANATION: This informational message lists the DCB characteristics used by MFX to process the input files for a merge.

ddname RECFM= ;LRECL= {;BLKSIZE=,CISIZE=} [;CINV ACCESS]

EXPLANATION: The ddname will be SORTOUT, SORTOFxx, SORTOFx or the ddname provided by an OUTFIL FNAMES parameter. This informational message lists the DCB characteristics used by MFX to process the indicated output file. This message will be provided for each output file specified. For a VSAM data set, the CISIZE is provided; if control interval access was used, the CINV ACCESS portion of the message will be displayed.

[ddname] {INREC,OUTREC,TOTAL/SUBTOTAL,MIN/SUBMIN, MAX/SUBMAX,AVG/SUBAVG} INVALID DATA CONVERSION REQUESTED

EXPLANATION: The ddname will be SORTOUT, SORTOFxx, SORTOFx or the ddname provided by an OUTFIL FNAMES parameter. Data conversion has been requested for INREC, OUTREC, OUTFIL OUTREC, TOTAL/SUBTOTAL, etc., as indicated, and one of the following error conditions has occurred:

The length of the field to be converted is too large.
Data conversion has been requested for a field that is not specified as BI, CSF/FS, FI, PD, Y2ID, Y2IP or ZD.
Invalid or conflicting EDIT/SIGNS parameters were specified.

INVALID VALUES IN FIELD PARAMETER

EXPLANATION: An invalid value was specified in the FIELDS operand of the SORT/MERGE control statement.

TOO MANY SORT FIELDS

EXPLANATION: The number of sort control fields specified exceeds the internal limits of the product. The absolute upper limit on the number of sort control fields is 128; however, depending on the complexity of an application, the limit may be reduced. When locale processing is used, the number of allowable CH control fields is also limited by the length of those fields.

INVALID MOD NAME

EXPLANATION: An invalid name for a program exit was entered on a MODS control statement.

THE FOLLOWING H/T IS GT LRECL:

EXPLANATION: This message flags any HEADERs, TRAILERs or IFTRAIL TRLUPD records that exceed the LRECL specification. The HEADER or TRAILER in error will be printed on the next line. To correct this problem, see Rules for Specifying HEADER Subparameters or Rules for Specifying TRAILER Subparameters.

INVALID ANSI CONTROL CHARACTER FOUND

EXPLANATION: An invalid ANSI control character appears in a HEADER or TRAILER. The ANSI Control Character Table lists the valid characters accepted by MFX.

INVALID ANSI CONTROL CHARACTER FOUND

EXPLANATION: An invalid ANSI control character appears in an output data record. The sort will process the record as if a blank control character had been found. This message will be issued only once regardless of how many data records have invalid ANSI characters. The ANSI Control Character Table lists the valid characters accepted by MFX.

ddname INVALID OVERLAPPING FIELDS

EXPLANATION: The ddname will be SORTOUT, SORTOFxx, SORTOFx or the ddname provided by an OUTFIL FNAMES parameter. An OUTFIL control statement contains a HEADER, TRAILER or IFTRAIL TRLUPD parameter which contains overlapping fields. This may be caused, for example, by a positional subparameter specification which overlaps a previously defined field.

NO DD NAME IN MODS FIELD

EXPLANATION: A DD name is missing on the MODS control statement.

SEP. LKED NOT ALLOWED

EXPLANATION: A module for which separate link-editing was specified on a MODS control statement is not allowed to be link-edited separately.

TASK CALL PARAM ERROR

EXPLANATION: If a 24-bit list is being used, either a control statement address is zero, or the length of a control statement is not positive, or the parameter list ends with the first word of a two-word parameter. If a 31-bit list is being used, the last parameter word in the list is not followed by the four byte field X'FFFFFFFF'.

INVALID INTERMEDIATE STORAGE DEVICE

EXPLANATION: An invalid device was assigned as intermediate storage. Valid devices include IBM’s 3380, 3390, and 9345 mass storage system, and equivalent units.

IMPROPER RETURN CODE FROM Exx

EXPLANATION: An invalid return code was passed by the exit that appears in the message. Valid return codes are 0, 4, 8, 12, 16 (and 20, if the exit is a COBOL or C E15 or E35).

[ESTIMATED] PREALLOCATED/USED SORTWORK SPACE USAGE FACTOR {=,<,>}nn.nn

EXPLANATION: nn.nn represents the quotient obtained by dividing the number of tracks assigned within preallocated sortworks (sortworks allocated in the JCL or dynamically allocated by an invoking program) by the number of tracks actually used by MFX. The word ESTIMATED is included when MFX’s derivation of this factor is inexact, for example, when all sortwork data sets are not opened, or when data space or hiperspace is used to contain part or all of the sortwork data.

Note that for MAXSORTs, the factor displayed is at or near "1.00" for all but the last sort. For the last sort, the factor may be anywhere between "0.01" and "1.00" depending on the amount of data sorted.

OUTFIL CONVERT WITHOUT THE OUTREC OR BUILD PARAMETER MAY PRODUCE UNDESIRABLE OUTPUT

EXPLANATION: OUTFIL CONVERT requires the OUTREC or BUILD parameter to produce consistent and blank-padded, if appropriate, output records. If the OUTREC or BUILD parameter is not specified with OUTFIL CONVERT, the sort may still run to completion, but the output record will include the input RDW in the first four bytes, and the record may be padded to the output record length with residual storage contents that are unpredictable in nature.

I/O ERROR ON SYSIN

EXPLANATION: An I/O error occurred on SYSIN or $ORTPARM.

PARM FIELD ERROR - xxxxxxxx

EXPLANATION: An invalid PARM was found in the PARM field string that was passed to MFX. MFX terminated the PARM processing by ignoring the remainder of this PARM string without terminating the MFX application. The invalid PARM is displayed in the message text if the PARM was passed on the EXEC statement. If the invalid PARM was passed through the $ORTPARM DD statement, the entire PARM string is written to the SYSOUT data set, and an asterisk is displayed beneath the invalid PARM.

Exx USER EXIT REQUESTED TERMINATION

EXPLANATION: Return code 16 was passed by the exit routine shown in the message. MFX terminated.

TASK CALL/E35 TERMINATED PREMATURELY

EXPLANATION: An E35 exit routine (COBOL Output Procedure) passed a return code of 8, terminating the sort before the sort was able to pass all of the records. A SORTOUT data set was not present.

TASK CALL/E35 TERMINATED PREMATURELY

EXPLANATION: An E35 exit routine (COBOL Output Procedure) passed a return code of 8, terminating the sort before the sort was able to pass all of the records. A SORTOUT data set was not present.

This message may not indicate an error condition - it depends on what the programmer intended. For example, this message will be generated if a COBOL program using the SORT verb RELEASEs 100 records in the Input Procedure without RETURNing all 100 records in the Output Procedure because the logic dropped to the bottom of the Output Procedure “prematurely.”If this is what the programmer intended, then no data has been lost. If, however, the programmer intended the Output Procedure to write all the records read in the Input Procedure, then this message indicates a logic bug in the COBOL program.

{INREC,OUTREC,ddname OUTREC} HAS OVERLAPPING FIELDS SPECIFIED

EXPLANATION: The column specification of a c: subparameter in the indicated control statement overlaps a field previously defined in the same control statement. Note that the subparameters used to define each field must be coded in the order in which the fields will appear in the reformatted record. The ddname will be SORTOUT, SORTOFxx, SORTOFx or the ddname provided by an OUTFIL FNAMES parameter.

ddname BLKSIZE NOT EVENLY DIVISIBLE BY LRECL

EXPLANATION: The ddname is SORTIN, SORTINnn, SORTJNF1, SORTJNF2, SORTMInn, SORTOUT, SORTOFxx, SORTOFx or the ddname provided by an OUTFIL FNAMES parameter. A block was read from the indicated file whose length was not a multiple of the LRECL value, or the JCL or data set attributes are incorrect.

ddname RECFM IS U

EXPLANATION: The ddname is SORTIN, SORTINnn, SORTJNF1, SORTJNF2, SORTMInn, SORTOUT, SORTOFxx, SORTOFx or the ddname provided by an OUTFIL FNAMES parameter. MFX does not support undefined record format for any of these files.

MIXED FIXED AND VARIABLE SORTxx TYPES NOT SUPPORTED

EXPLANATION: MFX permits only one record format type (fixed or variable) for input files per sort/merge. xx could be ‘IN’ or ‘MI’.

SORTIN LRECLS ARE MIXED

EXPLANATION: The LRECL must be the same for all fixed-length files supplied to a merge.

UNEXPECTED VIRTUAL STORAGE FRAGMENTATION

EXPLANATION: The amount of virtual storage calculated by MFX for Phases 2 or 3 was not available in a contiguous block. Additional virtual storage was obtained to satisfy the sort requirement. This condition was probably caused by virtual storage not released by the user program in the job step (for example, user exit buffer space was not released).

nnn BYTES OF EMERGENCY SPACE

EXPLANATION: The indicated amount of virtual storage has been set aside by MFX for use by other programs (e.g., program invoking the sort, system SVCs, tape management system).

CONTROL FIELD GREATER THAN RECORD LENGTH, POSSIBLE OUT OF SEQUENCE RECORD

EXPLANATION: The sort encountered a variable-length record that was too short to contain all of the control field(s) specified in the SORT statement. VLTEST instructed MFX to pad the record with binary zeros to the length of the sort key and continue processing. The added binary zeros account for the position of this record in the sorted file, which may appear to be out of sequence for this reason. The binary zeros are removed when the record is processed for output. Program HISTOGRM may be used to determine the length of the shortest record in the input file.

OPEN ERR SYSIN

EXPLANATION: SYSIN is either not present or cannot be opened.

FRAGMENTED VIRTUAL STORAGE IN SORT PHASE

EXPLANATION: The virtual storage specified for MFX’s use was not available in a contiguous block for Phase 1. This condition was probably caused by a calling program or user exit routine. MFX obtained its virtual storage in fragments and continued execution. Note that the calling program or user exit routine used virtual storage in such a way as to cause fragmentation, which might another time result in ABEND 80A or S804.

SECONDARY EXTENTS OBTAINED xxx

EXPLANATION: This gives the number of secondary extents obtained for SORTWKxx data sets.

REQUESTED VIRTUAL STORAGE NOT AVAILABLE, nnn BYTES USED

EXPLANATION: The CORE parameter specified a value which was not available when MFX received control. The number of available bytes used by MFX is given.

INSUFFICIENT VIRTUAL STORAGE IN {INT.,FINAL} MERGE PHASE

EXPLANATION: The amount of virtual storage available for the indicated merge phase (the intermediate or final merge phase) was not sufficient to allow execution.

NO MODS DD CARD

EXPLANATION: The DD statement whose name was specified on the MODS control statement was not provided, so the user exit routine cannot be found.

SPANNED RECORD LENGTH LARGER THAN LRECL

EXPLANATION: A record from a VBS input data set contains a record longer than the maximum record length specified by LRECL in the DCB.

ACTION: Execute program HISTOGRM to get the length of the longest record in the data set. Use this length for the LRECL value in the DCB parameter of the input data set.

RECORD LENGTH GREATER THAN L2, CUT TO L2

EXPLANATION: A variable-length input record is longer than the maximum record length specified by either LRECL in the DCB or the l₂ value in the RECORD control statement. (If l₂ was not specified, the variable-length record is longer than the l₁ value.) MFX has truncated the record.

ACTION: For applications where MFX is reading SORTIN, if truncation is not desired, execute program HISTOGRM to get the length of the longest record in the data set. Use this length for the LRECL value in the DCB parameter of the SORTIN data set.

RECORD LENGTH 0, SORTIN RECORD xxx,xxx,xxx,xxx,xxx

EXPLANATION: An invalid variable-length record (length code <4 in its Record Descriptor Word) has been found. If the record was found in the input file, the number of the invalid record is given. If the record was inserted from a user exit routine, the number of the inserted record is given (for example, 45 indicates the forty-fifth record read from the input file or inserted by a user exit.)

RECORD LENGTH GREATER THAN LRECL, TERMINATION REQUESTED

EXPLANATION: VLTEST has requested the sort to abort because of the following condition. A variable-length record read from the input file is longer than the maximum record length specified by LRECL in the DCB or (after E15 processing) is longer than the l₂ value in the RECORD control statement. (If l₂ was not specified, the l₁ value was used as its default.)

ACTION: Change the LRECL or l₂ value to reflect the record length, or specify another value for VLTEST. Program HISTOGRM may be used to determine the length of the longest record in the input file.

ALTERNATE PARM USED

EXPLANATION: The alternate PARM option ($ORTPARM DD, PARMEXIT or PARMTABLE) was used and MFX received the parameters specified.

ppp PREALLOCATED SORTWORK TRACKS, ddd DYNAMICALLY ALLOCATED sss ACQUIRED IN xxx SECONDARY EXTENTS, rrr RELEASED, TOTAL OF uuu TRACKS USED

EXPLANATION: ppp is the number of tracks found available in sortwork data sets which were allocated prior to MFX’s gaining control. (These may have been allocated in the JCL or dynamically allocated by an invoking program.) ddd is the number of tracks dynamically allocated as primary space by MFX. sss is the number of tracks acquired as secondary space, on both preallocated data sets and data sets dynamically allocated by MFX. xxx is the total number of secondary extents acquired. rrr is the total number of unneeded tracks released from both preallocated data sets and data sets dynamically allocated by MFX. uuu is the total number of tracks actually used in sorting.

The following notes apply to the information in this message:

ppp may not represent all of the preallocated tracks available, since not all preallocated sortwork data sets may be opened by MFX.
uuu may be less than the sum of ppp, ddd and sss since it represents the space actually used and not the space available.
For MAXSORTs, all dynamic allocation and secondary space acquisition is done during the first sort. For this reason, the WER162B message for the first sort will indicate the number of tracks dynamically allocated, the number acquired via secondary extents, etc. However, the WER162B message in all subsequent MAXSORT sorts will report these tracks as “preallocated”.

www BYTES OF VIRTUAL STORAGE AVAILABLE, xxx BYTES REQUESTED, yyy BYTES RESERVE REQUESTED, zzz BYTES USED

EXPLANATION: The amount of virtual storage available (free) when MFX received control is represented by w’s. The amount of virtual storage requested for MFX’s use is represented by x’s. The amount of virtual storage that the user requested MFX to reserve below the 16-megabyte line is represented by y’s. The amount of virtual storage used by MFX is represented by z’s. This message reflects the total amount of virtual storage below and above the 16-megabyte line that was available to MFX and used by MFX.

STAT DATA REC NOT WRITTEN

EXPLANATION: The installation default for the MFX SMF record feature is applied, but the sort did not invoke the module that creates the sort statistical record. A possible reason for the sort’s not invoking the module may be that FREE=CLOSE was coded on the SORTOUT (SYSUT2) or SORTWKxx DD statement.

ACTION: Remove the FREE=CLOSE parameter if full SMF statistics are desired.

RECORD LENGTH GREATER THAN L3, CUT TO L3

EXPLANATION: MFX has truncated a variable-length record prior to output processing. If an E35 exit was in use, the truncated record was longer than the LRECL of the output file’s DCB or greater than the l₃ value on the RECORD control statement. If an E35 exit was not in use, the truncated record was longer than the LRECL in the output file’s DCB. If OUTFIL processing is requested additional truncation may occur as a result of the OUTFIL processing regardless of the action requested by the VLTEST PARM.

RECORD LENGTH GREATER THAN OUTPUT LRECL, TERMINATION REQUESTED

EXPLANATION: Prior to output processing MFX has encountered a variable-length record longer than the l3 value on the RECORD control statement (if an E35 exit was in use) or longer than the LRECL in the output file’s DCB. Either the VLTEST PARM requested MFX to terminate or OUTFIL VLTRAIL was used.

ACTION: Change the LRECL in the output file’s DCB or the l3 value on the RECORD control statement (if an E35 exit is used) to reflect the correct record length, or specify another value for the VLTEST PARM.

CONTROL FIELD WITHIN RDW

EXPLANATION: A SORT/MERGE control field for a variable-length file fell within the Record Descriptor Word of each record. This is a critical error whenever the control field is specified with a ZD or PD format code.

CONTROL FIELD WITHIN RDW

EXPLANATION: A SORT/MERGE control field for a variable-length file falls within the Record Descriptor Word of each record. (The first byte of the data portion of a variable-length record is at byte position 5.)

RELEASE r.r BATCH nnnn TPF LEVEL n.n

EXPLANATION: Details on the release level, the batch number from the base installation tape, and the last TPF applied to MFX are given.

CONCATENATED DATA SET, BLKSIZE NOT DIVISIBLE BY LRECL

EXPLANATION: One of the files concatenated to a fixed-length input data set or one of the multiple input files has a BLKSIZE that is not evenly divisible by the original LRECL. Note that ‘CONCATENATED DATA SET’ could be replaced with ‘MULTIPLE INPUT’ in the message.

ACTION: Check the BLKSIZE specified on each of the DD statements concatenated to the first DD statement of the input or SORTMInn DD statements.

CONCATENATED DATA SET, LRECLS NOT EQUAL OR RECFMS DIFFERENT

EXPLANATION: One of the files concatenated to a fixed-length input data set or one of the multiple input files has an LRECL not equal to the original LRECL; or one of the files concatenated to a variable-length data set has an LRECL greater than the original LRECL; or one of the files concatenated to a fixed or variable-length data set has a RECFM not equal to the original RECFM. Note that ‘CONCATENATED DATA SET’ could be replaced with ‘MULTIPLE INPUT’ in the message.

CONCATENATED DATA SET, BLKSIZE GREATER THAN ORIGINAL BLKSIZE

EXPLANATION: One of the files concatenated to an input data set has a BLKSIZE greater than the original BLKSIZE.

BDW INVALID

EXPLANATION: The Block Descriptor Word of a block in the input data set contains a value less than 8; or the Block Descriptor Word contains a value greater than the number of bytes actually read.

ACTION: Check the data set for the invalid block.

RDW INVALID, OVERFLOWS BUFFER

EXPLANATION: The Record Descriptor Word of a record in the input data set is too large. (According to the RDW, the record extends beyond the buffer.)

ACTION: Execute HISTOGRM to check the data set for an invalid record.

INCORE SORT CAPACITY EXCEEDED

EXPLANATION: There are too many input records to fit in virtual storage.

ACTION: Either increase the amount of virtual storage the sort is able to use or supply SORTWKxx DD statements. (The DYNALLOC option may be used instead of SORTWKxx DD statements.)

USER EXIT LKED FAILED

EXPLANATION: Exit routine(s) needing to be link-edited were present, but the linkage editor passed a return code greater than 0.

ACTION: Check that the DD statement specified on the MODS control statement is present in the JCL and contains the modules specified on the MODS statement. Check that all exits (except E11, E21, and E31) to be link-edited together have an external name identical to the exit name. Examine the linkage editor output for other errors.

TURNAROUND SORT PERFORMED

EXPLANATION: MFX was able to sort the input file without using intermediate storage (SORTWKxx’s). All input data was contained in virtual storage.

ddname [nnnnn] MEMBER NOT FOUND

EXPLANATION: An input DD statement specified a member of a partitioned data set that could not be found. If a value nnnnn is provided, it represents the concatenation number of the data set that has the member-not-found condition.

ACTION: Check the DD statement for an error or list the members of the partitioned data set.

ddname INVALID DCB PARAMETERS

EXPLANATION: The ddname is SORTIN, SORTINnn, SORTJNF1, SORTJNF2, SORTMInn, SORTOUT, SORTOFxx, SORTOFx, or the ddname provided by an OUTFIL FNAMES parameter. MFX is unable to derive RECFM, LRECL, and BLKSIZE parameters from the JCL, the DSCB on the disk or the tape label.

ACTION: Check the JCL and the disk or tape labels for the error.

ddname MEMBER NOT SPECIFIED

EXPLANATION: The indicated input or output DD statement defines a partitioned data set, but a member name has not been specified.

ACTION: Specify a member name on the indicated DD statement or change the partitioned data set to a sequential data set.

INVALID RDW ddname BLOCK x

EXPLANATION: An invalid spanned record indicator was detected in an input file whose RECFM=VBS, or an invalid record length was detected in a copy operation. The block number of the file is given.

ACTION: Execute HISTOGRM to check the data set for a record containing invalid span bits. You can also use the VLTEST option to turn off segment sequence checking if so desired.

SORTWORK DATA SET REQUIRED

EXPLANATION: SORTWKxx data set(s) are required for one of the following conditions in this execution of MFX: (1) INCORE=OFF is specified as a PARM, (2) exit E14 or E16 is activated, (3) the SUM control statement is used, (4) the OUTREC control statement is used, (5) the checkpoint-restart facility is used, (6) SORTOUT is a VSAM data set, (7) the OUTFIL control statement is used. (All conditions only apply to sort applications.)

INVALID RETURN CODE FROM E32

EXPLANATION: The return code from merge exit E32 must be 8, 12, or 16.

SORTIN DCB BLKSIZE GREATER THAN ACTUAL BLKSIZE, I/O INEFFICIENT

EXPLANATION: The I/O rate is reduced to an inefficient level because the blocksize specified for the input data set is larger than the actual blocksize, causing excessive error correction.

ACTION: Correct the blocksize specification for future jobs.

SVC {nnn,109-rrr} IS INCORRECT VERSION OR NOT A SYNCSORT SVC - SVC NOT USED - INEFFICIENT SORT

EXPLANATION: The SVC nnn or SVC 109 with router code rrr was specified as the MFX SVC. The SVC did not return a code indicating it was at the correct version level, therefore it was not used. The SVC is either at the wrong MFX release/maintenance level or is not an MFX SVC. The problem could cause less efficient I/O and/or loss of SMF records.

ACTION: Notify your system programmer, who should check that the SVC has been installed in the system libraries, has been IPLed into the system, was specified via SYNCMAC, and was not incorrectly overridden via $ORTPARM or the PARM field.

SORTOF CINV SIZE LESS THAN RECORD LENGTH BUT SPANNING NOT SPECIFIED

EXPLANATION: The ddname will be SORTOUT, SORTOFxx, SORTOFx or the ddname provided by an OUTFIL FNAMES parameter. The record length is greater than the control interval size specified in the definition of the indicated VSAM data set, but the data set definition did not also include a specification for spanned records.

SORTIN IS DIRECT ACCESS/DSCB NOT FOUND/OBTAIN FAILED

EXPLANATION: The ddname is SORTIN, SORTINnn or SORTMInn. MFX was unable to successfully issue an OBTAIN for the specified direct access data set and was therefore unable to determine the DCB characteristics for the file. The OBTAIN failed either because the volume parameter was incorrectly specified for the input file indicated or because the data set was deleted from the volume. (NOTE: the data set may still be in the master catalog even though the data set is no longer on the volume.)

ddname DCB RECFM REQUIRED

EXPLANATION: The RECFM was not specified on the indicated input DD statement, nor was it available in the DSCB on disk nor the tape label, and the TYPE operand was not specified on the RECORD control statement.

ddname DUPLICATE OUTFIL SPECIFICATION

EXPLANATION: The ddname will be SORTOUT, SORTOFxx, SORTOFx or the ddname provided by an OUTFIL FNAMES parameter. The indicated output file is referred to more than once in FILES parameters on the OUTFIL control statement.

ddname BLKSIZE/LRECL INVALID

EXPLANATION: This message is displayed in conjunction with either WER108I or WER109I which will indicate the invalid DCB characteristic specification of the input ddname. BLKSIZE and LRECL must be equal if RECFM=F. BLKSIZE must be evenly divisible by LRECL if RECFM=FB. BLKSIZE must be greater than or equal to LRECL + 4 if RECFM=V.

ddname DCB LRECL MISSING

EXPLANATION: The LRECL was not specified on the indicated input DD statement, in the DSCB on the disk, in the tape label, or on the RECORD control statement.

ddname DCB LRECL AND BLKSIZE MISSING

EXPLANATION: The BLKSIZE or LRECL must be specified either on the indicated input DD statement, in the DSCB on the disk, or in the tape label. Alternatively, an l₁ specification may be included on the RECORD control statement. None of these specifications were made.

SORTOUT DCB REQUIRED/TAPE NOT SL

EXPLANATION: DISP=OLD was specified on the SORTOUT DD statement, the tape label was not specified as SL in the LABEL parameter, and required DCB information (LRECL, RECFM, BLKSIZE) was not specified.

ddname DCB REQUIRED/VSAM INPUT

EXPLANATION: The ddname will be SORTOUT, SORTOFxx, SORTOFx or the ddname provided by an OUTFIL FNAMES parameter. The indicated output file requires additional DCB information (RECFM, LRECL or BLKSIZE) on its DD statement.

SORTIN RECFM=VB, LRECL GREATER THAN BLKSIZE

EXPLANATION: RECFM=VB requires the BLKSIZE of the input ddname to be greater than or equal to LRECL + 4.

ddname RECFM=F/FB, LRECL/BLKSIZE INVALID

EXPLANATION: The ddname will be SORTOUT, SORTOFxx, SORTOFx or the ddname provided by an OUTFIL FNAMES parameter. BLKSIZE and LRECL were not equal on the indicated DD statement for RECFM=F, or BLKSIZE was not a multiple of LRECL for RECFM=FB.

SORTxx VARIABLE LRECL LESS THAN OR EQUAL TO 4

EXPLANATION: The LRECL specification on the indicated input or output DD statement did not allow 4 bytes for the RDW plus 1 byte for data. xx could be ‘IN’ or ‘OF’.

SORTxx RECORD TYPE=V, BLKSIZE LESS THAN OR EQUAL TO 8

EXPLANATION: The BLKSIZE specified for the indicated input or output DD statement did not allow 4 bytes for the BDW, 4 bytes for the RDW plus 1 byte of data. xx could be ‘IN’ or ‘OF’.

ddname RECFM=V/VB LRECL/BLKSIZE INVALID

EXPLANATION: The ddname will be SORTOUT, SORTOFxx, SORTOFx or the ddname provided by an OUTFIL FNAMES parameter. RECFM=V or VB requires the BLKSIZE to be greater than or equal to LRECL + 4.

ddname IS DIRECT ACCESS/DSCB NOT FOUND/OBTAIN FAILED

EXPLANATION: The ddname will be SORTOUT, SORTOFxx, SORTOFx or the ddname provided by an OUTFIL FNAMES parameter. MFX was unable to successfully issue an OBTAIN for the specified direct access data set, and was therefore unable to determine the DCB characteristics of the indicated file. The OBTAIN failed either because the volume parameter was incorrectly specified for the indicated output file, or because the data set was deleted from the volume. (NOTE: the data set name may still be in the master catalog even though the data set is no longer on the volume.)

ddname RECFM INCOMPATIBLE

EXPLANATION: The ddname will be SORTOUT, SORTOFxx, SORTOFx or the ddname provided by an OUTFIL FNAMES parameter. The record format of the output file is not the same as the input file, the record format of a record provided by an E15, or the record format created by a JOIN REFORMAT statement. (Both formats must be either fixed-length or variable-length.) If you want to convert a variable-length input file into a fixed-length output file, use the CONVERT parameter of the OUTFIL or OUTREC control statements. If you want to convert a fixed-length input file into a variable-length output file, use the FTOV parameter of the OUTFIL control statement.

INVALID SVC NUMBER

EXPLANATION: MFX’s processing requires its SVC, but no SVC number was specified at installation time.

ACTION: Inform your systems programmer of this error condition.

SORTCKPT DD STATEMENT MISSING OR INVALID

EXPLANATION: MFX could not take checkpoints because a SORTCKPT DD statement was not supplied or the statement specified an invalid device for a checkpoint data set. Invalid devices include DUMMY data sets or devices other than disk or tape. Processing continued but checkpoints were not taken.

MIXTURE OF SORTWK DEVICES

EXPLANATION: SORTWKxx data sets were assigned to different device types.

xxx PRIMARY AND yyy SECONDARY SORTOUT TRACKS ALLOCATED, zzz USED

EXPLANATION: It was necessary for MFX to request one or more secondary allocations for SORTOUT. xxx is the number of tracks that were initially allocated, yyy is the total number of tracks acquired via secondary allocation, and zzz is the total number of tracks actually required to contain the SORTOUT data set.

E15 RETURN CODE INVALID, IGNORED

EXPLANATION: A return code of 0 or 4 was passed by an E15 exit routine at a time when these return codes are invalid because MFX has not passed the E15 a record address. The invalid return code was ignored by MFX, and a return code of 8 was presumed.

[ ] CALLED BY SYNCSORT; RC=xxxx

EXPLANATION: The sort statistics routine (the name inserted in the message) is called by MFX. RC gives the code returned to MFX by the statistics routine. Note that RC=36 is generally issued when the MFX SVC is not active; the SVC must be installed to create SMF records. If RC does not equal zero or 36, see Before Contacting Precisely Support.

INVALID SUM DATA FIELD

EXPLANATION: A field with an invalid data length was specified on the SUM statement.

ACTION: Correct the field length.

[SORTOFnn] {INREC,OUTREC} ARITHMETIC OVERFLOW

EXPLANATION: When using either INREC, OUTREC or OUTFIL OUTREC, an arithmetic calculation or a data format conversion had an overflow. An arithmetic calculation overflow will occur if any intermediate result exceeds 31 decimal digits or if division by zero is attempted. Overflow may also occur when converting a number with a value of 4G or more to a 4-byte BI format or a number with an absolute value of 2G or more to a 4-byte FI format. An 8-byte BI value is limited to 18446744073709551615. The absolute value of an 8-byte FI or FL number is limited to 9223372036854775807.

ACTION: Review the arithmetic calculations specified in the indicated statement for errors. If they appear to be correct, consider whether the data could possibly cause an overflow or division by zero. If possible, eliminate any data with questionable values via INCLUDE/OMIT. Consider changing the order of the calculations to prevent intermediate calculation overflow.

SUM FIELD OUTSIDE RANGE

EXPLANATION: A sum field on the SUM control statement is located beyond the record length.

DYNALLOC {UNIT,STORCLAS} ASSIGNMENT ERROR

EXPLANATION: Either the unit name or storage class name (DFSMS STORCLAS) is missing or specified incorrectly.

DYNALLOC FAILED RC=(nnnn) - uuuuuuuu [-SMS RC=ssss]

EXPLANATION: The execution of the DYNALLOC macro instruction failed. nnnn represents the error reason code, uuuuuuuu represents either the unit name or storage class name, and ssss represents the SMS return code (only present for certain failures detected by SMS). Two possible reason codes are:

021C - Undefined unit name.

0214 - Unit not available. If all specified units are unavailable when DYNALLOC is issued, the DYNALLOC request fails.

For other reason codes, see IBM publication z/OS MVS Programming: Authorized Assembler Services Guide SA22-7608.

DYNALLOC FAILED RC=(nnnn) - uuuuuuuu [-SMS RC=ssss] SORT PROCESSING CONTINUES

EXPLANATION: Dynamic allocation was unsuccessful. nnnn represents the error reason code, uuuuuuuu represents either the unit name or storage class name, and ssss represents the SMS return code (only present for certain failures detected by SMS). Sort processing continues with previously allocated SORTWKs and JCL-allocated SORTWKs. For an explanation of the error reason code, see IBM publication z/OS MVS Programming: Authorized Assembler Services Guide SA22-7608.

INVALID OVERLAPPING OF SUM FIELDS

EXPLANATION: A SUM field overlaps another SUM field, a SORT/MERGE control field or the Record Descriptor Word of a variable-length record. All of these are invalid.

ddname ASCII XLATION, BUT VOLUME IS NOT ASCII TAPE OR RECFM IS V

EXPLANATION: RECFM=D was specified for the indicated input or output file which is not a tape data set. (RECFM=D is valid for tape data sets only.) Or, RECFM=D was specified for the input data set and no DCB was specified for the output data set.

ACTION: In the first case, code correct RECFM for the data set specified; in the latter case, code DCB characteristics for the output data set, and rerun the job.

ddname NOT DEFINED

EXPLANATION: A required DD statement could not be found.

E35 RC INVALID, IGNORED

EXPLANATION: An invalid return code was received from an E35 exit routine. If an output data set was not present, the invalid code was other than 4 or 8, and MFX assumed return code 4. If end of file was reached, the invalid code was other than 8 or 12, and MFX assumed return code 8.

ddname BLKSIZE GREATER THAN ASCII LIMIT

EXPLANATION: The ddname will be SORTOUT, SORTOFxx, SORTOFx or the ddname provided by an OUTFIL FNAMES parameter. The DD statement for an output data set targeted to an ASCII-labeled tape requested a blocksize greater than 2048 bytes; that violates the standard and cannot be done.

ddname DCB BLKSIZE GREATER THAN TRACK CAPACITY

EXPLANATION: The ddname will be SORTOUT, SORTOFxx, SORTOFx or the ddname provided by an OUTFIL FNAMES parameter. The BLKSIZE for the indicated output file was greater than the track capacity of the output device.

ACTION: Specifying the track-overflow RECFM in the DCB may possibly correct the error condition, or the BLKSIZE should be reduced.

ddname DSORG NOT PS/PO

EXPLANATION: The file defined by ddname must be a sequential data set (PS) or a partitioned data set (PO) member.

[ddname] xxxxxxxx FIELD OUTSIDE RANGE

EXPLANATION: The ddname will be SORTOUT, SORTOFxx, SORTOFx or the ddname provided by an OUTFIL FNAMES parameter. The reason for this may be any of the following:

A field specified in the SORT/MERGE or JOINKEYS statement is not located within the first 32750 bytes of the variable-length record. (This limit is lower if AC, AQ, E, PD0, Y2x or LOCALE CH fields are used.)
A field specified for INREC, OUTREC, OUTFIL OUTREC, REFORMAT, SECTION control, (SUB)TOTAL, (SUB)MIN, (SUB)MAX, (SUB)AVG or HEADER/TRAILER data field is located beyond the maximum record length.
INREC, OUTREC, OUTFIL OUTREC, REFORMAT, OUTFIL IFTRAIL, or HEADER/TRAILER n/col/date/page attempted to build a record larger than the allowable maximum.
A REFORMAT statement referenced a join input file field, but records from that input file were excluded by specifying ONLY on the JOIN statement.

[ddname] {INREC,OUTREC} - INVALID DATA FIELD

EXPLANATION: The ddname will be SORTOUT, SORTOFxx, SORTOFx or the ddname provided by an OUTFIL FNAMES parameter. An error was found in the INREC, OUTREC or OUTFIL OUTREC specification.

ACTION: Check the statement for alphabetic data in a numeric field, for a parameter value of 0, for an omitted value, for a space value greater than 256X, for incorrect boundary alignment, and for inclusion of the "variable portion" of fixed-length input records in the output records. Also, LINES=ANSI or LINES=(ANSI,n) may not be used on the OUTFIL statement when using multiline OUTREC.

ddname RECFM=VBS, LRECL MISSING

EXPLANATION: A RECFM of VBS was specified for the input ddname without an accompanying LRECL specification.

VIO INVALID FOR DYNALLOC

EXPLANATION: VIO is not permitted as a unit device for dynamic allocation. This is due to a possible performance degradation if VIO data sets are used as SORTWK.

[ddname] {INREC,OUTREC,REFORMAT} RDW NOT INCLUDED

EXPLANATION: The ddname will be SORTOUT, SORTOFxx, SORTOFx or the ddname provided by an OUTFIL FNAMES parameter. Four bytes must be provided for the RDW of the variable-length output record in the FIELDS parameter of the INREC, OUTREC, OUTFIL OUTREC, or REFORMAT specification. These bytes must appear at the beginning of the record and must not be edited. For REFORMAT, the RDW must be specified as coming from a variable-length join input data set.

[ddname] {INREC,OUTREC} NULL RECORD

EXPLANATION: The ddname will be SORTOUT, SORTOFxx, SORTOFx or the ddname provided by an OUTFIL FNAMES parameter. A variable-length INREC, OUTREC or OUTFIL OUTREC output record must contain at least one other data field in addition to the RDW. Or if multiline OUTFIL OUTREC is being used, at least one non-blank line must be defined.

OUTREC RECORD LENGTH=xxxx

EXPLANATION: The xxxx represents the length of the record after OUTREC processing. OUTREC occurs prior to E35 and/or SORTOUT/OUTFIL processing. If the data consists of variable-length records, xxxx represents the maximum record length.

POTENTIALLY INEFFICIENT USE OF INREC

EXPLANATION: The INREC control statement has been used to increase the input record length. This can reduce MFX’s performance because a larger volume of data is being processed than if the OUTREC control statement were used to perform the same function. Typically, increasing the record length with INREC is only useful when expanding SUM fields with leading zeros to prevent an overflow condition during SUM.

ACTION: Revise the application so that addition of data is performed in an OUTREC statement. Be sure to adjust the FIELDS of the SORT, MERGE or SUM control statements if necessary.

TYPE PARAMETER REQUIRED

EXPLANATION: There was a VSAM input or output file but the TYPE parameter was not specified. Or, an E15 or E32 exit routine is passing all of the records to the sort/merge (no SORTIN/SORTINnn/SORTMInn), but the TYPE parameter was not specified on the RECORD control statement.

ddname UNSUPPORTED DCB FUNCTION

EXPLANATION: The DD statement specified or implied an attribute which is not supported, e.g., hardware keys for a disk output data set or a block prefix length other than 0, 4 or L for an ASCII tape output data set.

SHORT RECORD FOR SUM

EXPLANATION: One or more variable-length records were too short to contain all the sum fields specified on the SUM control statement. These records were therefore not summed. Program HISTOGRM may be used to determine the length of the shortest record in the input file.

[ddname] {INREC,OUTREC} SHORT RECORD

EXPLANATION: The ddname will be SORTOUT, SORTOFxx, SORTOFx or the ddname provided by an OUTFIL FNAMES parameter. A variable-length record was too short to contain all the fields specified on the control statement. Program HISTOGRM may be used to determine the length of the shortest record in the input file.

FILESIZE x

EXPLANATION: The number of bytes of input data sorted or copied by MFX is given for FILESIZE. This number reflects input data set, E15, JOIN, INCLUDE/OMIT, and INREC processing. Note the following:

For MAXSORT, the FILESIZE is given in kilobytes for each individual sort in a WER351I message; the FILESIZE in the WER246I for the final merge is the sum of the individual sorts’ sizes and, because of truncation in each intermediate sort, may not be exact.
For variable-length record cases, when WER246I is issued and WER054I is also issued, the number of bytes processed includes a single record descriptor word for each record. When WER246I is issued and WER054I is not issued, the number of bytes processed includes the record descriptor words for all segments of any multi-segment records.

ddname HAS INCOMPATIBLE LRECL

EXPLANATION: The ddname will be SORTOUT, SORTOFxx, SORTOFx or the ddname provided by an OUTFIL FNAMES parameter. There is a conflict between the LRECL specification for the indicated output file and either the post-OUTFIL or post-OUTREC record length. Padding of records is not permitted after OUTFIL processing, so the LRECL may not be greater than the post-OUTFIL record length. Alternately, truncation of records is not permitted after the OUTREC statement or the OUTFIL OUTREC processing, so the LRECL may not be less than the post-OUTREC record length.

[ddname] INCLUDE/OMIT FIELD BEYOND RECORD

EXPLANATION: The ddname will be SORTOUT, SORTOFxx, SORTOFx or the ddname provided by an OUTFIL FNAMES parameter. A compare field specified for an INCLUDE/OMIT/WHEN/BEGIN/END/TRLID comparison extended beyond the end of the record. If it is expected that the input record (or for OUTFIL, the record after INREC or OUTREC control statement processing) will not be long enough to contain all the INCLUDE/OMIT fields, refer to VLTESTI for alternate methods of handling this short record condition.

INCLUDE/OMIT INVALID yyyyyyyyyy

EXPLANATION: The invalid relational condition represented by yyyyyyyyyy was found in the INCLUDE/OMIT/WHEN/BEGIN/END/TRLID parameter specification.

INCLUDE/OMIT FORMATS INCOMPATIBLE

EXPLANATION: A relational condition specified in an INCLUDE/OMIT/WHEN/BEGIN/END/TRLID comparison contains an invalid field-to-field, field-to-constant or field-to-mask comparison. Note that if LOCALE processing has been specified, a CH to BI comparison is not supported.

ddname VSAM {OPEN,CLOSE} ERROR - xx

EXPLANATION: An error occurred during an attempt to OPEN or CLOSE a VSAM file defined by ddname. For the definition of the error number, xx, consult the following IBM publication:

DFSMS Macro Instructions for Data Sets

Note: If xx is A0, it is likely that the VSAM data set is empty, and that VSAMEMT=NO is in effect. Pass the parameter VSAMEMT=YES as a possible solution.

VSAM LOGICAL ERROR xx ON {INPUT,OUTPUT}

EXPLANATION: An error occurred while processing a VSAM data set. For the definition of the hexadecimal error number represented by xx, see the following IBM publication:

DFSMS Macro Instructions for Data Sets

Note: If xx is 0C or 08 on output, it is likely that the VSAM output data set was created with REUSE, the VSAM data set is not empty, and RESET is not in effect. Pass the parameter RESET as a possible solution.

Note: A 0C on INPUT generally indicates an issue with duplicate-keyed records in the VSAM input data set.

ddname VSAM file, RECORDS PADDED ON OUTPUT

EXPLANATION: The ddname will be SORTOUT, SORTOFxx, SORTOFx or the ddname provided by an OUTFIL FNAMES parameter. The fixed-length VSAM LRECL for the indicated output file is greater than the length of the records at the end of MFX processing. MFX padded the output records with filler characters on the right.

INREC RECORD LENGTH=xxxxx

EXPLANATION: xxxxx represents the length of the record immediately after INREC processing. If you have variable-length records, xxxxx represents the maximum record length.

DUPLICATE DDNAME: SORTINxx

EXPLANATION: Two input files for a merge have the same number. The file number is given.

DUPLICATE ALTSEQ STATEMENT

EXPLANATION: Two ALTSEQ control statements were found.

RECOVERY FROM B37 SUCCESSFUL. SORT PROCESSING CONTINUES

EXPLANATION: MFX recovered from a B37 abend and continued processing.

REENTRANT SORT NOT RESIDENT - INEFFICIENT SORT

EXPLANATION: The resident MFX load module(s) were loaded into the private area instead of being executed from the Link Pack Area/Extended Link Pack Area. This situation may have occurred because the module(s) were found in a STEPLIB/JOBLIB DD data set. Loading the resident modules into the private area limits the amount of virtual storage available to the sort and may reduce the efficiency of the sort.

ACTION: Contact the systems programmer in charge of MFX installation.

MULTIVOLUME SORTWK DATA SETS ARE NOT SUPPORTED

EXPLANATION: MFX does not support the use of multi-volume disk SORTWK data sets. (However, if MFX only requires the use of the space on the first volume of a multi-volume SORTWK file, this error message will not be issued.)

ACTION: Remove the volume count subparameters of the UNIT parameter on all SORTWK DD statements that specify more than one volume.

UNEQUAL RECORD LENGTHS - VSAM SORTxx - TYPE=F

EXPLANATION: A record in a fixed-length VSAM input data set was encountered whose length was not equal to the length specified in the RECORD statement or VSAM cluster definition. xx could be ‘IN’ or ‘MI’.

ACTION: Use the IDCAMS utility to identify and correct the records in error.

ddname VSAM CONCATENATED INPUT NOT ALLOWED

EXPLANATION: The ddname indicated represents an input file which consists of concatenated VSAM data sets. MFX does not support concatenated VSAM input files.

ACTION: MFX is able to read multiple VSAM and non-VSAM input files through the MULTIIN facility. See Multiple Input Files for information on how to use MULTIIN.

ALTPARM - PARM LENGTH GT MAX SUPPORTED

EXPLANATION: The length of the parameter list passed through the alternate parameter data set exceeded the 256 byte limitation.

statement STATEMENT: STATEMENT NOT FOUND

EXPLANATION: A required SORT/MERGE or RECORD statement (as indicated in the message text) is missing.

statement STATEMENT: SYNTAX ERROR

EXPLANATION: An MFX control statement, as indicated in the message text, contains a syntax error. The next line will contain an '*' indicating the approximate location of the syntax error.

statement STATEMENT: DUPLICATE STATEMENT FOUND

EXPLANATION: More than one ALTSEQ, DUPKEYS, END, JOIN, JOINKEYS, INCLUDE/OMIT, INREC, MODS, OUTREC, RECORD, REFORMAT, SORT/MERGE, or SUM statement was found, as indicated.

statement STATEMENT: DUPLICATE PARM FOUND

EXPLANATION: A single parameter was multiply specified on the indicated MFX control statement; or a single parameter was specified both in the invoking parameter list and in the control statements.

statement STATEMENT: NUMERIC FIELD ERROR

EXPLANATION: A numeric field has been improperly specified on the indicated MFX control statement.

statement STATEMENT: PARMS NOT FOUND

EXPLANATION: Required parameters have not been included on the indicated MFX control statement.

BLANK STATEMENT FOUND

EXPLANATION: A blank statement has been encountered.

CONTINUATION STATEMENT ERROR FOUND

EXPLANATION: MFX has encountered a statement containing a continuation indicator, but cannot locate a continuation statement which should follow.

NO KEYWORDS FOUND ON CONTROL STATEMENT

EXPLANATION: A required keyword has not been specified on an MFX control statement.

SYSDIAG=nnnnnnnn,nnnnnnnn,nnnnnnnn,nnnnnnnn

EXPLANATION: This message contains internal diagnostic information intended for use by Precisely Support.

[ddname] {INREC,OUTREC} - INVALID USE OF VL (VARIABLELENGTH OUTPUT)

EXPLANATION: The ddname will be SORTOUT, SORTOFxx, SORTOFx or the ddname provided by an OUTFIL FNAMES parameter. The VL subparameter was used within JFY/SQZ and is invalid for one of the following reasons:

JFY/SQZ is used within the OVERLAY parameter.
An output record field with a starting column is specified after JFY/SQZ.
The LENGTH subparameter is used within the JFY/SQZ.
The input record to INREC/OUTREC is fixed-length (unless used on an OUTFIL statement where the FTOV parameter is specified).
JFY/SQZ is used within an OUTFIL IFTHEN clause with either WHEN=INIT or HIT=NEXT, and the FTOV parameter is specified.

BLOCK E15/E35 ERROR, REASON CODE nn

EXPLANATION: A Block Exit error was found in the E15 or E35 routine module, where nn represents the error reason code.

01 Block List Parameter Area or Block List address Invalid
02 Block List type Invalid
03 Block List boundaries Invalid
04 Block address (Type 2) or Record address (Type 1) Invalid
05 Block Exit Return Code Invalid
06 Record Length Invalid (Variable length Record)

SORTBKPT DD STATEMENT REQUIRED

EXPLANATION: The SORTBKPT DD statement was not included in the job stream. This is a required data set for all MAXSORTs.

SORTBKPT DATA MUST RESIDE ON DISK

EXPLANATION: The SORTBKPT data set must be allocated to a disk device.

SORTBKPT TRACK CAPACITY TOO SMALL

EXPLANATION: Direct access devices with a track capacity smaller than 3600 bytes cannot be used for the SORTBKPT data set.

SORTBKPT SYSTEM OPEN FAILURE

EXPLANATION: The operating system could not open the SORTBKPT data set.

ACTION: Check to see that the DD statement is correct. Determine if operating system is at proper maintenance level.

SORTBKPT RECORD FORMAT ERROR

EXPLANATION: There is a record format error in the SORTBKPT data set.

ACTION: Check that the SORTBKPT DD statement points to the correct DSNAME. Check that the data set has not been inadvertently written into and modified. Use the HEX function on the OUTREC statement or OUTREC parameter on the OUTFIL statement to get a hex format listing of the data.

SORTBKPT RECORD EXCEEDS BLKSIZE

EXPLANATION: The use of an excessive number of parameters in a control statement has caused the SORTBKPT data set to overflow the maximum blocksize limit of 32760.

ACTION: Reduce the size of the control statement specification if possible, or convert the application from a MAXSORT to a conventional sort.

RESTART FROM BREAKPOINT PROHIBITED

EXPLANATION: The SORTBKPT data set indicates that a program-initiated sort or a sort with exit programs tried to restart from a breakpoint.

ACTION: Use z/OS checkpoint facilities since only these will save your work areas and the program memory for restart.

SORTBKPT RECORD SEQUENCE ERROR

EXPLANATION: An out-of-sequence record was read from the SORTBKPT data set.

ACTION: Use the HEX function on the OUTREC statement or OUTREC parameter on the OUTFIL statement to get a hexadecimal listing of the data set for analysis. See if the data set was damaged by another program. Check system for hardware error.

BREAKPOINT ID NOT FOUND ON SORTBKPT

EXPLANATION: The parameter RESTART=id was specified but id could not be found.

ACTION: Check spelling, correct, and return.

SORTOUXX DATA MUST BE ON DISK OR TAPE

EXPLANATION: Intermediate sort output data was allocated to an unsupported device. Only disk or tape is allowed.

ACTION: Allocate SORTOUxx data to either disk or tape.

SORTOUXX DEVICE MIXING PROHIBITED

EXPLANATION: Intermediate sort output was allocated to both tape and disk in the same job or to a mixture of disk device types.

ACTION: Allocate all intermediate sort data to the same device type.

DISK SORTOUXX REQUIRES SORTOUXX DD

EXPLANATION: No SORTOUxx DD statements were found so there was no place to store intermediate sort output.

ACTION: Supply one or more SORTOUxx DD statements with xx represented by 01 to 99.

TAPE SORTOUXX REQUIRES SORTOU00 DD

EXPLANATION: One or more SORTOUxx DD statements were allocated to tape but the SORTOU00 statement was not present.

ACTION: Allocate a tape unit using the SORTOU00 DD statement.

SORTOUXX DEVICE NOT SUPPORTED

EXPLANATION: The SORTOUxx DD statements specify an unsupported device type.

ACTION: Change the device allocation of the SORTOUxx data set.

INSUFFICIENT VIRTUAL STORAGE FOR MAXSORT

EXPLANATION: MAXSORT cannot run efficiently in the amount of virtual storage provided.

ACTION: Increase virtual storage or decrease the number of tape units requested by MINMERGE.

SORTOUXX BLKSIZE GT TRACK CAPACITY

EXPLANATION: Intermediate sort output is on disk, but the input data set requires too large a blocksize for a disk device.

ACTION: Allocate intermediate sort output to tape and rerun.

INSUFFICIENT SORTOUXX DD STATEMENTS

EXPLANATION: The data to be sorted requires one or more additional data sets.

ACTION: Recalculate and restart the job including additional SORTOUxx DD statements. (Make sure each statement’s number is greater than the last one you put in.)

MAXSORT OPTION SELECTED

EXPLANATION: A MAXSORT was requested.

INPUT CARDS IGNORED - SORTBKPT USED

EXPLANATION: The control statement just listed on SYSOUT for a breakpoint/restart were not used to control sorting. Whatever control statements were specified when the job was started were used. (They may be the same as the statements just listed, however.)

SORT RESTARTED AT BKPT xxxxxxxxxxxx

EXPLANATION: This message identifies the breakpoint id from which MAXSORT resumes execution on a breakpoint/restart.

INEFFICIENT SORTOUXX BLKSIZE FORCED

EXPLANATION: Due to the constraints between the amount of memory and the value specified for MAXMERGE, MAXSORT was forced to compromise and choose a smaller blocksize than would permit efficient buffering in sorts and merges.

ACTION: If you wish a more efficient MAXSORT, either increase the amount of memory or reduce the number specified for MAXMERGE. This will permit a larger blocksize to be chosen which will allow multiple buffering of all the intermediate sort output data.

SORTOUXX BLKSIZE=xxxxx

EXPLANATION: This gives the blocksize that MAXSORT has chosen for intermediate sort output.

TAPE DYNALLOC FAILURE - CODE=xxxx

EXPLANATION: Attempts to dynamically allocate tape units for a merge phase met with unexpected failure. Code xxxx gives the hexadecimal return code from the dynamic allocation request. For an explanation of this code, see IBM publication z/OS MVS Programming: Authorized Assembler Services Guide SA22-7608.

BKPT DATA AT DIFFERENT RELEASE LEVEL

EXPLANATION: The SORTBKPT data was created by a different MFX release than the MFX program reading it. Because of this, the breakpoint data cannot be processed.

ACTION: Restart this job and run under the same MFX release that you started with.

TAPENAME CLASS NOT FOUND ON SYSTEM

EXPLANATION: The tapes could not be dynamically allocated because a TAPENAME was specified that was not generated into the operating system.

ACTION: Check with the systems programmer for acceptable unit names.

MAXSORT STOPPED BY OPERATOR

EXPLANATION: The operator responded to a message by stopping the sort. The sort may be restarted from the last breakpoint or checkpoint.

DYNALLOC UNALLOC FAILURE - CODE=xxxx

EXPLANATION: Attempts to dynamically deallocate tape units met with unexpected failure. Code xxxx gives the hexadecimal return code from the dynamic deallocation request. For an explanation of this code, see IBM publication z/OS MVS Programming: Authorized Assembler Services Guide SA22-7608.

INSUFFICIENT UNITS FOR MINIMAL MERGE

EXPLANATION: Too few tape units were allocated to meet the number specified in MINMERGE. Either too few SORTOUxx DD were supplied or the z/OS system was unable to dynamically allocate enough units.

ACTION: Restart the job with additional SORTOUxx DD statements.

SORTOUXX SYSTEM OPEN FAILURE

EXPLANATION: The operating system could not open the SORTOUxx data sets.

ACTION: Check to see that SORTOUxx DD statements are correct. Determine if operating system is at a proper maintenance level.

SORTOU00 SYSTEM RDJFCB FAILURE

EXPLANATION: The operating system could not read the Job File Control Block for MFX analysis.

ACTION: Determine if operating system is at a proper maintenance level.

SPECIFIED SORTING TIME HAS EXPIRED

EXPLANATION: The time limit specified in the SORTTIME parameter has expired. The job may be restarted from the last breakpoint or checkpoint.

SYSTEM CHECKPOINT FAILURE

EXPLANATION: Request for z/OS checkpoint facilities failed.

ACTION: Ascertain that the SORTCKPT DD statement was correctly specified. Check that rules for the use of checkpoint were not violated.

TOO MANY INTERMEDIATE SORTS - INCREASE SORTWORK SPACE

EXPLANATION: Only 99 intermediate sorts are allowed in a MAXSORT application.

ACTION: Increase the SORTWORK space available to MAXSORT so that each intermediate sort will process more data, reducing the number of intermediate sorts required. Ensure that the MINWKSP and MAXWKSP values are sufficient to allow additional space to be acquired. The application does not have to be restarted from the beginning. If a MAXSORT breakpoint/restart is allowed in the application, restart from an earlier breakpoint with a sufficient amount of SORTWORK space available to process the file within the 99 intermediate sort limit

zHPF USED FOR {INPUT, OUTPUT}

EXPLANATION: MFX used zHPF channel programs to improve the performance of the input and/or output phase.

{SORT/MERGE} # XX COMPLETE {AT BREAKPOINT/AT CHECKPOINT} bbbbbbbbbbbb, DIAG=hhhh,hhhh...

EXPLANATION: This message tells which individual sort or merge has completed. Restart can be performed from the breakpoint or checkpoint id given in bbbbbbbbbbbb. If restart is not possible the above message will read:SORT/MERGE # XX COMPLETE. The hexadecimal information following the DIAG keyword is likely to change from execution to execution. It is internal diagnostic information intended for use by Precisely Support.

DATA SIZE xxxx KB [FROM yy WAY MERGE]

EXPLANATION: The amount of data that was processed for the current MFX individual sort/merge is given in kilobytes. When a merge is processed yy gives the number of tape units used.

DYNAMICALLY ALLOCATED TAPE UNITS - XX

EXPLANATION: The number of tapes drives that were dynamically allocated for the current merge pass is given.

STARTING TIME hh.mm.ss - ENDING TIME hh.mm.ss

EXPLANATION: The starting and ending times in hours, minutes, and seconds of the individual sort or merge just completed are given.

----------------------DATA SET STATUS----------------------

EXPLANATION: This is a header. Messages relating to data sets will follow.

{DSN=dsname/VOL SERS = vvvvvv...}

EXPLANATION: The data set names of the tapes for intermediate sort output are given. The tape volumes are listed for tape intermediate sort output. Retain these reels for input to a later merge.

SORTOUXX DD STATEMENT IS ACTIVE

EXPLANATION: The disk data set allocated to the SORTOUxx DD statement is needed as input to a subsequent merge. Be sure to keep it in case restart is necessary.

jobname.stepname - MAXSORT BKPT idTIME ESTIMATE: XXX MINUTES UNTIL NEXT NOTIFICATION.REPLY 'GO' TO CONTINUE, 'STOP' TO TERMINATE

EXPLANATION: A long-running MAXSORT has exhausted its assigned block of computer time.

ACTION: The operator’s decision should be based on scheduling priorities and the estimated time of the sort. A 'GO' reply will permit sort execution to proceed in stages. This message is generated at discrete intervals so that the operator can again opt to continue or terminate its execution.

jobname.stepname - MAXSORT BKPT idaaa TAPE UNITS ALLOCATED TO jobnamebbb TAPE UNITS NEEDED FOR BEST PERFORMANCETIME ESTIMATE USING aaa TAPE UNITS -xxxx MINUTES TO {NEXT BREAKPOINT | END OF JOB}REPLY 'GO' TO CONTINUE, 'STOP' TO TERMINATE, 'NN' # UNITS

EXPLANATION: The first time this message is generated, it indicates that MAXSORT has dynamically allocated the optimum number aaa of tape drives up to MAXMERGE. Reissued, this message documents MAXSORT’s response to the operator’s previous reply of 'NN' tape units. 'NN' represents the total number of tapes that will be allocated.

ACTION: Given a reply of 'NN' tape drives, MAXSORT will attempt to satisfy the operator’s request. For 'NN' larger than aaa, MAXSORT will try to raise its allocation to 'NN'. (The operator can delay the request for more tape units in order to give other jobs time to free any tape drives they are using.) The above message is reissued and the operator can see how the decision will affect sort execution.

As soon as allocations and time estimates are satisfactory, the reply 'GO' will cause continued execution using the allocated tape units. If allocation or time estimates are not satisfactory, the job may be terminated (reply 'STOP') or a new number 'NN' of units may be requested.

jobname.stepname - MAXSORT BKPT idINSUFFICIENT TAPE UNITS AVAILABLEaaa TAPE UNITS ALLOCATED TO jobnamebbb TAPE UNITS NEEDED TO CONTINUE EXECUTIONREPLY 'RETRY' TO GET UNITS, 'STOP' TO TERMINATE

EXPLANATION: MAXSORT cannot immediately acquire enough tape drives to make continued processing worthwhile.

ACTION: The operator can wait until other tape drives have been released, then reply 'RETRY'. If enough drives are now available, execution continues. Otherwise the above message is repeated. Eventually enough tape drives become available or the operator terminates the job with a 'STOP' response.

NO ADDITIONAL TAPE UNITS EXIST FOR GENERIC CLASS tapename

EXPLANATION: All tape units on the system within the TAPENAME class have been allocated. Further DYNALLOC attempts will fail to acquire more tape units. Message WER376D or WER377D will follow.

MINIMUM SORTWK SPACE NOT AVAILABLE

EXPLANATION: MAXSORT could not obtain enough SORTWK disk space to run. When MAXSORT is executing with larger storage values, MFX may need to automatically raise MINWKSP, overriding the specified MINWKSP value. Therefore, it may erroneously appear that JCL SORTWKs provided enough space to satisfy MINWKSP when this message was posted.

ACTION: Correct SORTWK volume, primary, and secondary allocations. Restart the job.

INSUFFICIENT VIRTUAL STORAGE FOR SORTBKPT BUFFER

EXPLANATION: MAXSORT was unable to obtain the necessary 3600-byte buffer space from the operating system.

ACTION: Check to see that sufficient virtual storage was allocated to the sort.

SORTBKPT FORMAT ERR - VBS PROCESSING

EXPLANATION: MAXSORT attempted to read back control information associated with VBS input data and found a format error in the SORTBKPT data set.

ACTION: Contact Precisely Support or call your MFX support representative.

TURNAROUND MAXSORT SORT PERFORMED

EXPLANATION: The amount of input data was small enough to fit entirely on SORTWK disk space, so sorted data was produced in one MFX pass.

SORTOUXX DD STMT REQUIRED FOR MERGE

EXPLANATION: The above DD statement was required for disk intermediate sort output as input to a merge but could not be found.

ACTION: Supply the missing DD statement.

INVALID SORTOU00 OR SORTOUxx DSN PREFIX

EXPLANATION: The BKPTDSN parameter was used, but the required trailing period was not specified as part of the DSN prefix.

ACTION: Add a trailing period to the parameter specification.

LKED DD STATEMENT MISSING OR INVALID

EXPLANATION: A MODS statement specified at least one exit to be link-edited by MFX, but a SYSPRINT and/or SYSLIN and/or SYSLMOD DD statement is missing. All of these statements are required for link-editing. Or, the SYSLMOD DD statement does not refer to a data set on a direct access device.

ACTION: Supply the missing DD statement(s) or adjust the SYSLMOD DD statement as appropriate.

ddname IS AN UNINITIALIZED SEQUENTIAL DISK DATA SET

EXPLANATION: The input data set was allocated but never opened for output. Therefore, there is no valid data or end-of-file mark in the data set. This condition usually occurs when a program abends and the steps to create the data are bypassed.

ACTION: Write the appropriate data or end-of-file mark in the data set, or see UNINTDS.

CSECT NAME DIFFERENT THAN MEMBER NAME

EXPLANATION: The MODS statement specified an exit routine module in SYSIN that was not found.

ACTION: Either change the member name in the MODS statement to match the module name or reassemble the exit module with a name to match the member name on the MODS statement.

SORTMODS STOW FAILURE

EXPLANATION: While copying an exit routine from SYSIN to SORTMODS, MFX attempted unsuccessfully to store (STOW) the exit routine in the SORTMODS directory. This condition is caused either by specifying insufficient directory blocks when creating the SORTMODS data set or by the presence of a member or alias with the same name as the exit routine in the SORTMODS data set, or by a hardware failure.

ACTION: Check the SORTMODS directory names for a member-name conflict and rerun the job step.

xxxxxxxx NOT VALID FOR MAXSORT

EXPLANATION: xxxxxxxx denotes the feature that is not supported when using MAXSORT.

ACTION: Either remove the feature specification or convert the application not to invoke MAXSORT.

{SORTXSUM,SORTXDUP}: RECFM= ;LRECL= ;{BLKSIZE=,CISIZE=} [;CINV ACCESS]; RCD OUT n

EXPLANATION: This informational message lists the DCB characteristics used by MFX to process the SORTXSUM/SORTXDUP file, as well as the number of records (n) that were written to the data set. For a VSAM data set, the CISIZE is provided; if control interval access was used, the CINV ACCESS portion of the message will be displayed.

ddname DATA RECORDS OUT n, TOTAL RECORDS OUT y

EXPLANATION: The ddname will be SORTOUT, SORTOFxx, SORTOFx or the ddname provided by an OUTFIL FNAMES parameter. The n represents the number of data records (exclusive of HEADERS/TRAILERS and multi-record OUTREC) in each output data set. The y represents the total number of records in each output data set (data records, HEADERS/TRAILERS and multi-record OUTREC records). Note that the total number of lines written to the line printer may be greater than the actual record count since multiple lines can be generated from one data record using ANSI control characters.

ddname HEADER/TRAILER/DATA LINES EXCEED PAGE SIZE

EXPLANATION: The ddname will be SORTOUT, SORTOFxx, SORTOFx or the ddname provided by an OUTFIL FNAMES parameter. The number of lines generated by some HEADER and/or TRAILER and/or multiline OUTREC parameters is greater than or equal to the number of lines to be written per logical page as specified by the LINES parameter. If LINES has not been coded, this number defaults to 60.

ACTION: Reduce the number of HEADER/TRAILER lines generated or increase the number of lines in the LINES parameter so that a minimum of all output lines from 1 data record can be written per logical page.

UNUSABLE SORTWK DEVICE ALLOCATED, UNIT=VIO

EXPLANATION: A VIO data set was allocated during dynamic allocation. The device was held for the duration of the sort; however, the device was not used for SORTWK storage.

ACTION: For future executions, ensure that the DYNALLOC runtime parameter specifies a unit name that does not cause a VIO data set to be allocated.

MOD ON SYSIN NOT FLAGGED AS SYSIN MODULE

EXPLANATION: An object deck was found in the SYSIN data set that, according to the MODS statement, was not specified as belonging in SYSIN.

xxx BYTES OF VIRTUAL STORAGE AVAILABLE ABOVE THE 16-MEGABYTE LINE, yyy BYTES RESERVE REQUESTED, zzz BYTES USED

EXPLANATION: The amount of virtual storage above the 16-megabyte line available (free) when MFX received control is represented by x’s. The amount of virtual storage that the user requested MFX to reserve above the 16-megabyte line is represented by y’s. The amount of virtual storage used by MFX above the 16-megabyte line is represented by z’s.

nnn BYTES OF EMERGENCY SPACE ALLOCATED ABOVE THE 16-MEGABYTE LINE

EXPLANATION: The indicated amount of virtual storage above the 16-megabyte line has been set aside by MFX for use by other programs (e.g., program invoking the sort, system SVCs, tape management system.)

ERROR TAKING SYSTEM CHECKPOINT. PROCESSING CONTINUES

EXPLANATION: An error occurred when MFX attempted to take a user-requested checkpoint. Sort/merge processing continued; however, a usable checkpoint may not exist. Refer to the IHJxxxx message in the job log to determine the cause of the error.

ddname OPEN ERROR ON AN UNINITIALIZED SEQUENTIAL DISK DATA SET

EXPLANATION: An error occurred during an OPEN of a multi-volume uninitialized sequential disk data set being used for ddname. When the UNINTDS=YES option has been selected, either by default or parameter override, MFX will need to open for output a multi-volume uninitialized disk data set in order to set the DS1IND80 flag in the format-1 DSCB of the first volume. Typically this error will occur if the MFX step does not have the authority to open the data set for output processing.

ACTION: In a separate step prior to the MFX invocation, write the appropriate end-of-file mark in the first volume of the multi-volume data set.

DSM FACILITY DISABLED

EXPLANATION: MFX’s dynamic storage management feature was not active for this sort execution.

EXPLANATION: This message provides summary I/O tuning information for files processed by MFX. The first form is used when an access method other than EXCP is used for a file. It uses a generic term for the access method (BSAM, HIPERBATCH, etc.) and the file for which it was used. When EXCP is used, the message takes on the second form which has the component parts listed below. Some of these components may or may not be included in the message depending on the level of the operating system and the availability of the information within MFX.

EXCP'S=eee	"eee" identifies the number of EXCPs issued for the file. For input files such as SORTIN, this is the total EXCPs issued for all concatenated input sets.
UNIT=vuuuu	"uuuu" is the unit type on which the data set resides. For files that can consist of concatenations or multi-volume data sets, the unit type displayed is for the first volume of the first data set.
DEV=dddd	"dddd" is the device name for the first or only device for the file.
CHP=cccccccc,n	This field identifies the channel paths available to the first or only device. ''n'' is the number of PAV aliases available.
VOL=vvvvvv	This field is displayed for only DASD devices and identifies the volume serial number of the first or only volume for the file.

For certain types of sorts, MFX may dynamically allocate data sets other than SORTWKxx data sets for use in the sorting process, and this can occur whether or not normal dynamic allocation of sortwork data sets is enabled. When used, such data sets are collectively represented in a single WER416B message using a ddname of "SORTWK&&" for the purpose of reporting EXCPs issued against them.In the third form of the message, xxx provides a total of the EXCPs issued for SORTWORKS, SORTING, COPYING, or MERGING, as identified by "totalid."

UNEQUAL MAINTENANCE LEVELS: x,y,z

EXPLANATION: The module x and MFX maintenance levels do not correspond. y represents the maintenance level of the x module; z represents the PTF number recorded in the MFX maintenance record.

ACTION: Contact the systems programmer in charge of MFX maintenance. This problem is most likely caused by a lack of synchronization between maintenance levels of modules in the SYNCLINK, SYNCRENT, and SYNCLPA libraries. Note that the MFX maintenance record is in the SYNCLINK library.

DATASPACE(S) AND/OR ZSPACE USED

EXPLANATION: MFX has dynamically chosen to use data space or ZSPACE during the execution of the sort. ZSPACE is a technique within MFX created as a replacement for hiperspace. It allows native use of the central storage resources which are available. This technique eliminates the additional overhead produced when hiperspace is simulated by the operating system in a z/Architecture environment. It provides superior CPU performance and reduced system overhead compared to a conventional hiperspace application.

COBOL ACCELERATOR ACTIVE

EXPLANATION: MFX’s high performance access method was used for accessing a COBOL file.

SORTOUT STOW FAILURE

EXPLANATION: When writing to SORTOUT, MFX attempted unsuccessfully to store (STOW) the SORTOUT PDS member in the SORTOUT directory. This condition is caused by specifying insufficient directory blocks when creating the SORTOUT data set.

ACTION: Recreate the SORTOUT data set with more directory blocks and rerun the job step.

DYNAMIC ALLOCATION RETRY - WAITING FOR SPACE

EXPLANATION: The DYNALLOC facility is being used to acquire sortwork space, but there is currently insufficient disk space on the system to satisfy the request. MFX will wait the prescribed number of minutes as specified by the DYNALLOC option and then retry the request.

DYNAMIC ALLOCATION RETRY SUCCESSFUL

EXPLANATION: The dynamic allocation of sortwork space after a DYNALLOC RETRY attempt was successful. Sort processing continues.

CONVERT FEATURE CANNOT BE USED WITH OVERLAY OR IFTHEN; OUTFIL CONVERT REQUIRES OUTREC

EXPLANATION: The OUTREC CONVERT feature cannot be used with OVERLAY or IFTHEN parameters. It also must be used together with the OUTREC parameter.

SORT INTERNAL ERROR - RECOVERY ATTEMPT IN PROGRESS

EXPLANATION: The presence of this message indicates that an automatic retry of the MFX execution has been initiated. If the error recovery is successful, the MFX SYSOUT listing will contain a subsequent set of messages representing the complete information about the execution. The subsequent set of messages may be separated from the initial set of listings by a diagnostic output of significant size. The new listing will contain the message WER427I.

RECOVERY ATTEMPT IN PROGRESS

EXPLANATION: The set of SYSOUT messages containing the WER427I will be from the automatic retry execution. Examine these messages to insure that it also contains a WER052I message indicating a successful completion of the MFX execution. In addition, a successful MFX recovery will complete with a return code of zero. Even if the WER426I and WER427I messages are present, this in itself does not constitute a successful recovery unless zero is returned for the step completion code.

If an execution of MFX does utilize the recovery facility, whether successfully or not, the Precisely Support should be contacted so that the underlying error can be investigated and resolved.

CALLER-PROVIDED IDENTIFIER IS "xxxx"

EXPLANATION: MFX was invoked by another program, and that program used a 31-bit or 64-bit parameter list where the "call identifier" parameter was specified. xxxx is the identifier specified by the calling program.

COPY SUBSTITUTED FOR MULTIPLE OUTFILS

EXPLANATION: The SORT or COPY multiple output application (multiple OUTFILs) has been automatically converted by MFX to a single SORT or COPY operation followed by one or more COPY operations.

If system resources are available and the output files of a multiple output application have identical specifications, MFX will make this type of change to take advantage of system resources to improve the application’s performance.

{SORT,MERGE} FORMAT OPERAND IGNORED

EXPLANATION: On either a SORT or MERGE control statement, the format of the keys was specified in both the FIELDS and FORMAT parameters. MFX ignores the FORMAT parameter and uses the individual format specifications within the FIELD parameter.

SUM FORMAT OPERAND IGNORED

EXPLANATION: On a SUM control statement, the sum field format was specified in both the FIELDS and FORMAT parameters. MFX ignores the FORMAT parameter and uses the individual format specifications within the FIELD parameter.

JOINKEYS FORMAT OPERAND IGNORED

EXPLANATION: On the JOINKEYS control statement, the format of the keys was specified in both the FIELDS and FORMAT parameters. MFX ignores the FORMAT parameter and uses the individual format specifications within the FIELDS parameter.

ddname ALLOCATION ERROR ON AN UNINITIALIZED SEQUENTIAL DISK DATA SET

EXPLANATION: An error occurred during the dynamic allocation of a multi-volume uninitialized sequential disk data set being used for an input data set. When the UNINTDS=YES option has been selected, either by default or parameter override, MFX will need to dynamically allocate and open for output a multi-volume uninitialized disk data set in order to set the DS1IND80 flag in the format-1 DSCB of the first volume.

ACTION: In a separate step prior to the MFX invocation, write the appropriate end-of-file mark in the first volume of the multi-volume data set.

UNEQUAL MAINTENANCE APPLIED TO GLOBAL DSM AND SYNCSORT LIBRARIES

EXPLANATION: The maintenance level of the MFX product is in conflict with the maintenance level of the global DSM (GDSM) subcomponent due to the incomplete application of one or more maintenance levels.

[ddname] SPLIT, SPLITBY, SPLIT1R OR REPEATINCOMPATIBLE WITH REPORT WRITING

EXPLANATION: The ddname will be SORTOUT, SORTOFxx, SORTOFx or the ddname provided by an OUTFIL FNAMES parameter. The SPLIT, SPLITBY, SPLIT1R, or REPEAT parameter and one or more report writing parameters have been specified for an OUTFIL group. The specified ddname is the first ddname of the OUTFIL group. SPLIT, SPLITBY, SPLIT1R, or REPEAT and report writing parameters are incompatible on the same OUTFIL control statement. Specifically, SPLIT, SPLITBY, SPLIT1R, or REPEAT cannot be specified on the same OUTFIL statement with HEADERn, TRAILERn, LINES, NODETAIL, and SECTIONS.

[ddname] {INREC,OUTREC} - NONE OF THE FIND-CONSTANTS WAS MATCHED WITH THE CHANGE FIELD (p,l), CONTENTS OF INPUT FIELD IN HEX: xxxxxxxx

EXPLANATION: The ddname will be SORTOUT, SORTOFxx, SORTOFx or the ddname provided by an OUTFIL FNAMES parameter. A CHANGE subparameter on an INREC, OUTREC or OUTFIL OUTREC control statement was specified without a NOMATCH option and the input field did not match any of the specified find-constants. p,l represents the position and length of the input field. xxxxxxxx is the hexadecimal representation of the input field.

{INREC, OUTREC, ddname} FIND/REPLACE OVERRUN OF nnnnn BYTE RECORD LENGTH

EXPLANATION: FINDREP was used on either an INREC, OUTREC, or OUTFIL ddname statement. The substitution of an output constant during a FINDREP operation caused a non-blank character to be pushed beyond the maximum record length. By default only trailing blanks can be deleted during a FINDREP operation. nnnnn represents the maximum record length for the FINDREP operation.

ACTION: Either specify a MAXLEN value on the FINDREP parameter to increase the maximum length of the record or specify the OVERRUN=TRUNC FINDREP subparameter to allow deletion of non-blank characters.

UNSUPPORTED OPERATING ENVIRONMENT

EXPLANATION: The operating system on which MFX executes must be z/OS Release 1.4 or later. In addition, MFX requires a zSeries processor running z/OS in ESAME mode.

ERROR IN CALLING LANGUAGE ENVIRONMENT SERVICE, RC = nnnn

EXPLANATION: A Language Environment service used to support LOCALE processing indicated a critical error in its feedback code. nnnn is the error message number representing the feedback code. For an explanation of this code, see the IBM publication Debugging Guide and Run-Time Messages, SC26-4829.

INVALID CHARACTER IN COMPARE FIELD FOR ACTIVE LOCALE

EXPLANATION: INCLUDE/OMIT processing with the LOCALE function active detected a character that is not defined in the current locale. The invalid character could be in a CH field or in a character or hexadecimal constant compared to a CH field.

INVALID CHARACTER IN CONTROL FIELD FOR ACTIVE LOCALE

EXPLANATION: Sort or merge processing with the LOCALE function active detected a character that is not defined in the current locale. The invalid character is in a CH sort or merge field.

LOCALE PROCESSING USED FOR LOCALE nnnnnn

EXPLANATION: Indicates that LOCALE processing was in effect. nnnnnn (up to 32 characters) represents the name of the locale used.

LOCALE PROCESSING CONFLICT

EXPLANATION: LOCALE processing has been used invalidly. LOCALE processing cannot be used with an E61 exit. The LOCALE specification cannot be changed on a MAXSORT breakpoint/restart.

[ddname] INCLUDE/OMIT FORMATS INCOMPATIBLE FOR LOCALE PROCESSING

EXPLANATION: The ddname will be SORTOUT, SORTOFxx, SORTOFx or the ddname provided by an OUTFIL FNAMES parameter. LOCALE processing has been requested and a character (CH) to binary (BI) comparison was specified in an INCLUDE/OMIT or WHEN comparison. CH to BI comparisons are not supported when using LOCALE processing.

PHASE 3 VIRTUAL STORAGE REDUCED TO nnn BYTES FOR OPTIMAL PERFORMANCE

EXPLANATION: Phase 3 optimization has determined that a reduction in virtual storage is appropriate for an efficient execution. nnn is the amount of virtual storage used during phase 3. The total bytes used value in message WER164B indicates the virtual storage used during earlier phases of the sort execution.

Y2 FORMAT CENTURY WINDOW IS FROM xxxx TO yyyy

EXPLANATION: One of the Y2x data formats has been used for a SORT/MERGE field, an INCLUDE/OMIT/WHEN/BEGIN/END field or an INREC/OUTREC edit field. The starting year is xxxx and the ending year is yyyy for the century window used to process the fields.

SYNCSORT GLOBAL DSM SUBSYSTEM ACTIVE

EXPLANATION: The MFX Global DSM (GDSM) subsystem was active during the execution of this MFX application.

PARASORT USED

EXPLANATION: The PARASORT technique has been used for this execution.

PARASORT TAPE LABEL ERROR VOL(vvvvvv) [CONCATENATION+0nnn]

EXPLANATION: The tape label on volume vvvvvv does not match the DCB characteristics of the input data set. This could happen because of changed record length, BLKSIZE or record format. This situation is normally caused by overwriting some of the data in a multi-volume data set. The concatenation number indicates where in the input concatenation the volume in error may be found.

PARASORT NOT USED: reason

EXPLANATION: The PARASORT feature has been disabled and the sort was performed using conventional input processing. The message indicates the reason for this action, which may be any of the following:

AUTOMATIC RETRY DISABLED Automatic sort retry must be enabled for PARASORT to be used. It is required in the event that the condition identified in WER454A is encountered.
CONCATENATED SORTIN DEVICES DIFFER Concatenated SORTIN devices must be the same device; that is, unit affinity must be specified.
DUPLICATE VOLUMES ON SORTIN DD NOT ALLOWED
INCOMPATIBLE CONDITIONS The application may specify elements that cannot be used together. This problem can be caused by unusual sort key types, some feature combinations, or very long sort keys.
INPUT IS NOT TAPE PARASORT requires input from tape devices. Input from any other source is not permitted.
INSUFFICIENT TAPE CHANNELS At least two channel paths must be available to the tape drives being used to read the SORTPARn DDs. For a description of a technique to help insure that this requirement is satisfied, see the description of esoteric unit names in the PARASORT chapters of this manual and the MFX for z/OS Installation Guide.
NO SORTWORKS AVAILABLE PARASORT requires sortwork space, which must be specified in the JCL or provided dynamically by DYNALLOC.
RETRY IN PROGRESS PARASORT failed, but a retry is being attempted.
SORTIN IS A NULLFILE
SORTIN IS ONLY A SINGLE VOLUME DATA SET The SORTIN DD statement for PARASORT must define either a single multi-volume SORTIN data set or several concatenated tape data sets, which can be single or multi-volume. One single-volume data set is not permitted.
V(B)S DATA SETS NOT ALLOWED VS and VBS data sets are not compatible with PARASORT.

FOR PARASORT text

EXPLANATION: PARASORT failed and the sort application will not execute. The message text indicates the condition that caused the failure or the PARASORT requirement that was violated:

A SORTPAR2 DD STATEMENT IS REQUIRED
EQUALS MAY NOT BE SPECIFIED If EQUALS is not specified on the SORT control statement or as a PARM, ensure it is not enabled by default. Pass NOEQUALS to disable EQUALS.
E15 EXITS MAY NOT BE SPECIFIED
IFTHEN WHEN=GROUP MAY NOT BE SPECIFIED ON INREC
MAXSORT MAY NOT BE SPECIFIED
PASSED SORTIN IS INVALID
SEQNUM MAY NOT BE SPECIFIED ON INREC
SKIPREC MAY NOT BE SPECIFIED
SORTIN AND SORTOUT MUST BE DIFFERENT DATA SETS
SORTIN GDG NOT ALLOWED
SORTIN VOLUME SEQUENCE MAY NOT BE SPECIFIED The volume sequence number must be 1, the first volume. The number cannot be greater than 1.
SORTPAR DD STATEMENTS ARE REQUIRED
SORTPAR(N)S MUST BE SEQUENTIALLY NUMBERED
SORTPAR1 AND SORTIN DATA SET NAMES MUST BE THE SAME
SORTPAR1 DISPOSITION MUST BE OLD
SORTPAR1 UNIT MUST BE THE SAME AS THE SORTIN UNIT
SORTPAR1-4 DEVICE TYPES MUST BE THE SAME AS THE SORTIN DEVICE TYPE
SORTPAR2-4 CANNOT BE THE SAME AS THE SORTIN UNIT
SORTPAR2-4 and SORTIN DATA SET NAMES MUST BE THE SAME
SORTPAR2-4 DISPOSITION MUST BE (NEW,KEEP,KEEP)
SORTPAR2-4 MUST SPECIFY DEFER ON THE UNIT PARAMETER
SORTPAR2-4 MUST SPECIFY VOL=PRIVATE
STOPAFT MAY NOT BE SPECIFIED
THE DISPOSITION OF SORTIN IS INVALID SORTIN data sets may not be temporary data sets. They also may not be NEW, passed or have PASS on their JCL definition.
DB2 MAY NOT BE SPECIFIED The DB2 query function is not supported with a PARASORT.

PARASORT SORTIN END OF FILE ENCOUNTERED BEFORE THE VOLUME LIST EXHAUSTED

EXPLANATION: The SORTIN volume list is supplied from either the catalog or specific list of volume serial numbers. The volume serial list must accurately reflect the volumes in the data set. If extra volumes are specified (as may happen if an old data set is rewritten with less data) this error message will be generated. A volume sequence number may not be specified.

PARASORT CHANNEL CONTENTION - SORTPARn NOT USED

EXPLANATION: SORTPAR2-4 has no available channel path to send data other than a path that would conflict with a previously defined SORTPARn definition. This SORTPARn will not be used during the PARASORT execution. This message may occur more than once if there are multiple conflicting SORTPARn DD’s.

VISUAL SYNCSORT APPLICATION SUCCESSFULLY EXPORTED

EXPLANATION: A file that describes your application has been created and written to the VISUALEX DD statement for export to Visual SyncSort. The operations defined by the control statements have not been performed.

VISUALEX NOT SPECIFIED OR INVALID

EXPLANATION: The VISUALEX DD statement for export to Visual SyncSort is either missing or its data set has been incorrectly defined. The file must have physical sequential or extended sequential organization or be a member of a partitioned data set or PDSE. The record format must be undefined (RECFM=U) or unspecified.

MAINTENANCE LEVEL INSUFFICIENT TO PROCESS VISUAL SYNCSORT SYSIN DATA SET

EXPLANATION: The SYSIN data set created by Visual SyncSort cannot be processed by MFX. This is due to an insufficient level of maintenance on the MFX library. A newer level of MFX may be required to process the SYSIN data set.

A VISUAL SYNCSORT APPLICATION MAY NOT text

EXPLANATION: Only qualified MFX applications may be exported to Visual SyncSort. The reason this application is ineligible is supplied in the message text.

ddname DATA TRUNCATED DUE TO DCB BLKSIZE OVERRIDE

EXPLANATION: An extended sequential data set used as input to a sort, merge or copy has had its DCB BLKSIZE overridden to a smaller value via a JCL specification. A physical block exceeding this overridden BLKSIZE specification was truncated to the smaller size during input processing.

ACTION: Confirm that this truncation is desired. If not, remove the BLKSIZE specification from the JCL.

SORTOUT/OUTFIL DATA SET CONTAINS NO DATA RECORDS

EXPLANATION: If the NULLOUT=RC16 parameter is in effect and the SORTOUT data set had no data records written to it during processing, WER461A will be posted. (HEADER/TRAILER records are not considered to be data records.) If one or more non-SORTOUT OUTFIL specifications had the NULLOFL=RC16 parameter in effect and they had no records written to them, WER461A will be posted. The WER405I message, which details the records written to each OUTFIL, will provide information on the OUTFIL(s) that caused the message to be generated. Note that an OUTFIL FILES=OUT, or FNAMES SORTOUT is controlled by NULLOUT only, and not by NULLOFL.

SORTOUT/OUTFIL DATA SET CONTAINS NO DATA RECORDS

EXPLANATION: If the NULLOUT=RC4 parameter is in effect and the SORTOUT data set had no data records written to it during processing, WER461I will be posted. (HEADER/TRAILER records are not considered to be data records.) If one or more non-SORTOUT OUTFIL specifications had the NULLOFL=RC4 parameter in effect and they had no records written to them, WER461I will be posted. The WER405I message, which details the records written to each OUTFIL, will provide information on the OUTFIL(s) that caused the message to be generated. Note that an OUTFIL FILES=OUT, or FNAMES SORTOUT is controlled by NULLOUT only, and not by NULLOFL.

OUTPUT LRECL DIFFERS FROM SORTOUT LRECL

EXPLANATION: If the application is a sort, merge, or copy, the LRECL defined in the JCL for a non-OUTFIL SORTOUT differs from the SORTIN/SORTINnn/SORTMInn LRECL or the internally processed record length when the SORTIN/SORTINnn/SORTMInn LRECL is modified by features and the PAD and/or TRUNC parameters have been set to RC=16 to disallow this. For a variable-length MULTIIN application, the maximum of all of the SORTMInn LRECLs is used. In a BetterGener application, the LRECL defined in the JCL for SYSUT2 differs from the SYSUT1 LRECL or the internally modified record length when the SYSUT1 LRECL is modified by features and the SOPADGN and/or SOTRNGN installation options have been set to RC=16 to disallow this.

ACTION: Remove the SORTOUT LRECL specification, allowing MFX to calculate the appropriate SORTOUT LRECL or modify the MFX control statements to build a record of the desired length as specified by the SORTOUT LRECL.

OUTPUT LRECL DIFFERS FROM SORTOUT LRECL

EXPLANATION: If the application is a sort, merge, or copy, the LRECL defined in the JCL for a non-OUTFIL SORTOUT differs from the SORTIN/SORTINnn/SORTMInn LRECL or the internally processed record length when the SORTIN/SORTINnn/SORTMInn LRECL is modified by features and the PAD and/or TRUNC parameters have been set to RC0 or RC4. For a variable-length MULTIIN application, the maximum of all of the SORTMInn LRECLs is used. In a BetterGener application, the LRECL defined in the JCL for SYSUT2 differs from the SYSUT1 LRECL or the internally modified record length when the SYSUT1 LRECL is modified by features and the SOPADGN and/or SOTRNGN installation options have been set to RC=0 or RC=4.

Fixed-length records will be padded to the SORTOUT LRECL (SYSUT2 LRECL in a SYNCGENR application) when the SORTOUT LRECL is greater than the SORTIN or internally processed record length.

Records will be truncated to the SORTOUT LRECL (SYSUT2 LRECL in a SYNCGENR application) when the SORTOUT LRECL is less than the SORTIN or internally processed record length.

ACTION: Verify that the padding or truncation that will be performed is desired for this application. Refer to the provided WER108I and WER110I messages that detail the input and output record lengths.

ddname IS A LINEAR VSAM DATA SET

EXPLANATION: MFX does not support an input or output file that is a linear VSAM data set.

INVALID SPANNED RECORD FOUND

EXPLANATION: An invalid spanned record segment has been found while processing the input records in a sort or merge application, and VLTEST=(,{OFF,OFF4}) has been specified to produce a warning. When OFF4 has been specified, a return code of 4 will be issued if not overridden by a higher return code issued for another reason.

OPEN ERROR SYMNAMES

EXPLANATION: The OPEN for the SYMNAMES DD has failed. Check the DD statement for any errors.

SYMNAMES ERRORS FOUND

EXPLANATION: One or more errors were found in the data dictionary definitions in the SYMNAMES data set or JPn PARMs. See the description of each error that appears after each erroneous SYMNAMES statement.

DB2 QUERY TRIAL MODE SUCCESSFULLY EXECUTED

EXPLANATION: A report of the record layout produced by the DB2 query contained in the SORTDBIN data set has been successfully produced. No other processing has occurred.

DB2 QUERY SUPPORT ERROR: text

EXPLANATION: The DB2 query operation failed and the sort or copy application will not execute. The message text indicates the condition that caused the failure or the DB2 query requirement that was violated.

MAXSORT MAY NOT BE SPECIFIED
AN E15 EXIT MAY NOT BE SPECIFIED
MERGE OPERATION MAY NOT BE SPECIFIED
SKIPREC MAY NOT BE SPECIFIED
SORTDBIN OPEN ERROR
SORTDBIN CANNOT BE FOUND The DB2 parameter has been specified, but the required SORTDBIN DD has not been provided.
NO SQL SELECT STATEMENT FOUND IN SORTDBIN
INVALID COMMAND, ONLY SQL SELECT STATEMENT SUPPORTED Only a SELECT or $ELECT statement is valid in SORTDBIN. No other SQL operations are supported.
QUERY STATEMENT TOO LONG (MAX 32765 BYTES)
CANNOT CONNECT TO DB2 DB2 is not started or the subsystem name specified on the DB2 EXEC parameter is incorrect.
CANNOT BIND PLAN The user ID from which the job was submitted has insufficient authority to bind the plan with the MFX module. Submit the application from an ID that is allowed the BIND privilege.
BIND/OPN PLAN ER The user ID from which the job was submitted has insufficient authority to bind the plan with the MFX module or insufficient resources were available for DB2 to process the open request.
UNSUPPORTED DATA TYPE FOUND
UNKNOWN DATA TYPE FOUND
SQL ERROR: SQLCODE=xxxx,SQLSTATE=yyyy Where xxxx is the SQLCODE and yyyy is the SQLSTATE returned. Refer to IBM publication DB2 Universal Database for z/OS Messages and Codes (GC18-9602) for details on these return codes.
DB2 MODULES ARE NOT LINKED The DB2 query facility of MFX has not been installed during MFX installation. Contact your systems programmer for assistance.

BOTH JOINKEYS STATEMENTS MUST HAVE THE SAME NUMBER OF JOINKEYS

EXPLANATION: A join application requires two JOINKEYS statements that define the same number of JOINKEYS FIELDS, with each corresponding field having the same order specified.

TWO JOINKEYS STATEMENTS ARE REQUIRED TO USE THE JOIN FEATURE

EXPLANATION: A join application requires two JOINKEYS statements that define the same number of JOINKEYS FIELDS, with each corresponding field having the same order specified.

A REFORMAT STATEMENT IS REQUIRED TO USE THE JOIN FEATURE

EXPLANATION: A join application requires two JOINKEYS control statements and a REFORMAT control statement, unless a JOIN UNPAIRED control statement is present with the ONLY parameter specified.

THE NUMBER OF JOIN FIELDS EXCEEDS THE MAXIMUM OF 64

EXPLANATION: The maximum number of JOINKEYS FIELDS that may be specified is 64.

INVALID JOINKEYS STATEMENT FIELD LENGTH

EXPLANATION: A JOINKEYS statement field length exceeds the allowable length for its format. 4080 is the maximum for BI, CH and AQ fields, and 256 is the maximum for FI, PD, and ZD fields.

TOTAL LENGTH OF JOIN KEYS IN JOINKEYS STATEMENTS EXCEEDS 4080

EXPLANATION: The maximum total length of all JOINKEYS FIELDS is 4080 bytes.

BOTH JOINKEYS STATEMENTS MUST HAVE CORRESPONDING KEY FIELDS WITH COMPATIBLE FORMATS

EXPLANATION: Corresponding JOINKEYS fields do not have formats that are compatible with each other. CH and BI are compatible formats, and PD and ZD are compatible formats. AQ and FI formats are not compatible with any other format type.

FIRST 4 BYTES OF A VARIABLE-LENGTH REFORMAT DEFINITION MUST BE FROM A VL JOIN FILE

EXPLANATION: When defining a variable-length record as the output of the join feature, the first four bytes defined must be for an RDW. This must be specified on the REFORMAT statement as FIELDS=(Fn:1,4,…). This field may be taken from either of the SORTJNFn files if both are variable-length, but if only one file is variable-length, the field must come from the variable-length file.

BOTH JOINKEYS STATEMENTS MUST HAVE CORRESPONDING KEY FIELDS WITH THE SAME ORDER

EXPLANATION: A join application requires two JOINKEYS statements that define the same number of JOINKEYS FIELDS, with each corresponding field having the same order specified.

A SORTJNF1 OR SORTJNF2 DD STATEMENT IS MISSING; BOTH ARE REQUIRED

EXPLANATION: A join application requires the presence of SORTJNF1 and SORTJNF2 DD definitions in the JCL.

xxxxxxxx MAY NOT BE USED IN A JOIN APPLICATION

EXPLANATION: A join application may not be specified with any of the following parameters: MAXSORT, PARASORT, Syncsort PipeSort, SKIPREC, MERGE function, user exits (except E35), CHECKPOINT, or DB2.

A REFORMAT FIELD WITH ONLY A POSITION VALUE MUST REFERENCE A VARIABLE-LENGTH JOIN FILE

EXPLANATION: A REFORMAT FIELD may only be specified as a position without a length value if it refers to a file defined as variable-length. This type of field definition may be specified once for each join file if they are both variable-length. These specifications must be the last fields defined on a REFORMAT statement.

JOINKEYS REFORMAT RECORD LENGTH = nnnnn,TYPE = {F,V}

EXPLANATION: nnnnn represents the length of the record produced by JOINKEYS REFORMAT processing. The TYPE represents the record format produced, either fixed (F) or variable (V). If you have variable-length records, nnnnn represents the maximum record length.

JNFn STATISTICS

EXPLANATION: JNFn is either JNF1 or JNF2 representing information on SORTJNF1 or SORTJNF2 processing that was performed during a join application. This message will be followed by other informational messages that apply to the SORT or COPY processing for that DD.

JNF1 or JNF2 processing information …

EXPLANATION: This message follows the WER482I message that defines which of the two join input files this message contains information about. The information details characteristics of the sort processing performed for SORTJNF1 or SORTJNF2 to prepare them for the join operation. Further information can be found in the explanations of the WER164B, WER410B, WER036B, WER158I, WER460I, WER464I, and WER162B messages.

ddname: RCD IN=aaaaaaaa, OMITTED=bbbbbbbb, PAIRED=cccccccc, UNPAIRED=dddddddd

EXPLANATION: The ddname will be either SORTJNF1 or SORTJNF2. aaaaaaaa represents the number of records read from the particular join input file. bbbbbbbb indicates the number of records deleted by the JOINKEYS INCLUDE/OMIT parameter. cccccccc is the number of records matched from this file during join processing. dddddddd is the number of records from this file that were unpaired during join processing.

SORTJNFn OUT OF SEQUENCE, RECORD NUMBER=aaaaaaaa

EXPLANATION: When the SORTED parameter is specified on the JOINKEYS statement, MFX will sequence check the input file according to its JOINKEYS fields. This message indicates that a sequence error was detected in either SORTJNF1 or SORTJNF2. aaaaaaaa is the record number within the file that caused the error. The record number is not provided if the INCLUDE/OMIT parameter of the JOINKEYS statement is specified.

ERROR IN JNFn PROCESSING

EXPLANATION: The n value is either 1 or 2 and indicates that an error has occurred while processing the SORTJNF1 or SORTJNF2 data sets. Examine the application’s SYSOUT message data set for additional WERnnnA messages that will indicate the exact nature of the error.

FILESIZE aaaaaaaa BYTES

EXPLANATION: The aaaaaaaa represents the number of bytes of SORTJNF1 or SORTJNF2 input data sorted by MFX to prepare the file for join match field processing. This number reflects deletions made by JOINKEYS INCLUDE/OMIT processing. See the prior WER482I message to determine if FILESIZE is for SORTJNF1 or SORTJNF2.

JOIN CAPACITY EXCEEDED

EXPLANATION: MFX is unable to complete the join application because of insufficient memory. This may be due to a user error in specifying the JOINKEYS fields, or the application may be very large relative to the amount of available memory.

In order to join all records with equal JOINKEYS in SORTJNF1 with all records with matching JOINKEYS in SORTJNF2, MFX retains all the equally keyed SORTJNF2 records in memory to join with the next equally keyed record from SORTJNF1. The available amount of memory is determined by the available system resources and the region size and may not be sufficient if there are very many equally keyed records in SORTJNF2.

ACTION: First examine the fields specified for the JOINKEYS FILE=F2 statement and correct any errors. If the fields were incorrectly specified, then many records may have been incorrectly determined to be equally keyed.

If the JOINKEYS statement for F2 is correct, and if you believe that SORTJNF1 does not contain many equally keyed records that match the large number of equally keyed records in SORTJNF2, then this problem may be easily corrected by reversing the F1 and F2 definitions such that SORTJNF1 has many equally keyed records, but SORTJNF2 does not. To do this, reverse the DDNAMEs of the two files and change the JOINKEYS, REFORMAT, and JOIN UNPAIRED statements accordingly.

If this does not solve the problem, then the total region size must be raised high enough to contain all of the SORTJNF2 equally keyed records.

Contact Precisely Support for assistance, if necessary.

RECORD STATEMENT LENGTH VALUE EXCEEDS MAXIMUM OF 32767

EXPLANATION: The maximum value that can be specified for an l₁ to l₇ value is 32767.

INVALID DATE ENCOUNTERED IN DATE FORMAT ARITHMETIC OR CONVERSION

EXPLANATION: An INREC/OUTREC field with a Y2x or Y4x full date format or a DATEADD/DATEDIFF date field contains an invalid date. The output will be presented with all 9’s in the digit portion of the specification.

Z/ARCHITECTURE ENVIRONMENT REQUIRED

EXPLANATION: FL format conversion on INREC, OUTREC, or OUTFIL is only supported in z/Architecture mode on zSeries processors.

DUPKEYS: text

EXPLANATION: A DUPKEYS control statement was specified. The message text indicates the reason for the error message.

AVG RECORD COUNT OVERFLOW MFX’s default internal limit on the maximum number of records that can be averaged has been exceeded, or the internal accumulation limit on the summation of the total has been exceeded. By default, the internal limit on the number of records that can be processed for an average application is 2,147,483,647 records containing the same SORT or MERGE control fields.
INVALID xxx DATA FIELD where xxx=SUM, MAX, MIN, or AVG. A field with an invalid data length was specified in the xxx parameter.
INVALID OVERLAPPING OF xxx FIELDS where xxx=SUM, MAX, MIN, or AVG. An xxx field overlaps another xxx field or other field in the DUPKEYS statement, or a SORT/MERGE control field, or the Record Descriptor Word of a variable-length record. All of these are invalid.
INVALID USE FOR SUM/XSUM The SUM control statement and the DUPKEYS control statement cannot both be specified. If you would like to add the MIN, MAX, or AVG functionality to an application with a SUM control statement, then move the SUM specification to the DUPKEYS statement and remove the SUM statement. If XSUM was used, then XDUP should be specified and the JCL changed from using a SORTXSUM DD to a SORTXDUP DD.
INVALID USE FOR XDUP/FORMAT Another parameter in addition to XDUP or FORMAT must be specified on the DUPKEYS statement.
SUM/AVG FIELD OVERFLOW Summing or averaging of two equally keyed records could not be done due to a numeric overflow or underflow in a defined SUM/AVG field. The WER492A critical message is issued instead of the WER492I warning message if the OVFLO=RC16 PARM or installation SUMOVFL=RC16 is in effect.
SUM/MIN/MAX/AVG FIELD OUTSIDE RANGE A field in the SUM/MIN/MAX/AVG parameter is located beyond the record length.

DUPKEYS: text

EXPLANATION: A DUPKEYS control statement was specified. The message text indicates the reason for the informational message.

CONTROL STATEMENT IGNORED The DUPKEYS control statement is ignored in a FIELDS=COPY or BetterGener application because there are no SORT/MERGE control fields.
FORMAT OPERAND IGNORED The FORMAT parameter of DUPKEYS was ignored because all fields had a format specified.
SHORT RECORD FOR SUM/AVG/MIN/MAX One or more variable-length records were too short to contain all the control fields specified on the DUPKEYS statement. No DUPKEYS function will be performed on this record. The HISTOGRM program may be used to determine the length of the shortest record in the input file.
SUM/AVG FIELD OVERFLOW Summing or averaging of two equally keyed records could not be done due to a numeric overflow or underflow in a defined SUM/AVG field. The WER492A critical message is issued instead of the WER492I warning message if the OVFLO=RC16 PARM or installation SUMOVFL=RC16 is in effect.

ZIIP PROCESSOR USED

EXPLANATION: MFX has used the zIIP processor for improved performance.

{INPUT, OUTPUT} PHASE USED MIDAW {;MIXED MODE}

EXPLANATION: MFX’s MIDAW technology optimized the performance of the input and/or output phase. MIXED MODE indicates that some of the devices used are not MIDAW-capable.

SORTOUT/OUTFIL DATA SET CONTAINS DATA RECORDS

EXPLANATION: If the NOTMTOUT=RC16 parameter is in effect and the SORTOUT data set had at least one record written to it during processing, WER461A will be posted. If one or more non-SORTOUT OUTFIL specifications had the NOTMTOFL=RC16 parameter in effect and they had at least one record written to them, the WER495A will be posted. The WER405I message, which details the records written to each OUTFIL, will provide information on the OUTFIL(s) that caused the message to be generated. Note that an OUTFIL FILES=OUT, or FNAMES SORTOUT is controlled by NOTMTOUT only, and not by NOTMTOFL.

SORTOUT/OUTFIL DATA SET CONTAINS DATA RECORDS

EXPLANATION: If the NOTMTOUT=RC4 parameter is in effect and the SORTOUT data set had at least one record written to it during processing, WER495I will be posted. If one or more non-SORTOUT OUTFIL specifications had the NOTMTOFL=RC4 parameter in effect and they had at least one record written to them, WER495I will be posted. The WER405I message, which details the records written to each OUTFIL, will provide information on the OUTFIL(s) that caused the message to be generated. Note that an OUTFIL FILES=OUT, or FNAMES SORTOUT is controlled by NOTMTOUT only, and not by NOTMTOFL.

THE MULTIIN PARAMETER CANNOT BE USED WITH MERGE, PARASORT OR JOIN

EXPLANATION: MERGE, PARASORT and JOIN do not support the multiple input feature. Specify SORTINnn DD statements for a merge application.

statement: {NOT-A-NUMBER, NOT-A-NUMBER OR INFINITY} ENCOUNTERED IN FD FIELD (nnnn,nnnn)

EXPLANATION: For a SORT/MERGE statement, a NOT-A-NUMBER value is detected in a field (nnnn,nnnn); for a DUPKEYS/SUM statement, either a NOT-A-NUMBER or INFINITY value is detected in a field (nnnn,nnnn).

DECIMAL FLOATING POINT FACILITY REQUIRED FOR FD FIELDS

EXPLANATION: For a statement that includes a decimal floating point (DFP) field (FD), the DFP facility is required to be installed in the z/Architecture architectural mode.

PFPO SUPPORT REQUIRED TO CONVERT FROM FL TO FD

EXPLANATION: For an INREC/OUTREC statement that needs to convert an FL field to an FD field, the PFPO instruction is required to be installed.

SYNCSORT STATISTICS DATA SET NOW OVER xx PERCENT FULL

EXPLANATION: xx percent of space currently allocated on the MFX Statistics data set has been used. This message is not controlled by the MSG or FLAG PARM and will appear only on the console.

SYNCSORT STATISTICS DATA SET NOW FULL - NO RECORD WRITTEN

EXPLANATION: The MFX Statistics data set did not have enough space for the SYNCSMF record. This message is not controlled by the MSG or FLAG PARM and will appear only on the console.

COULD NOT FIND OR LOAD ONE OR MORE JAVA CLASSES

EXPLANATION: One or more JAVA classes cannot be found. First, ensure that both the JZOS and MFX libraries have been installed correctly. Then ensure that JZOSHOME and SYNCHOME point to these libraries correctly.

ddname OUTFIL OUTPUT PARAMETER - JAVA EXCEPTIONS DETECTED

EXPLANATION: JAVA exceptions have been detected. See the messages in the STDERR DD or the STDOUT DD for the exception type.

UNABLE TO DYNALLOC WORK DATA SET FOR OUTFIL PROCESSING

EXPLANATION: Dynamic allocation of the work data set STDENV failed.

ACTION: Contact Precisely Support or call your MFX support representative.

PDF/RTF OUTPUT LINES WRAPPED

EXPLANATION: Some output lines are longer than the page width. They are wrapped to the following line.

PDF/RTF/HTML OUTPUT HFS FILES REQUIRED

EXPLANATION: PDF/RTF/HTML output must be HFS.

OUTFIL JAVA FILE SSOUTPUT.JAR LEVEL DOES NOT MATCH SYNCSORT

EXPLANATION: The JAR file ssoutput.jar which is installed on UNIX is not the same level as other MFX modules on the mainframe. Re-install ssoutput.jar or check if SYNCHOME points to the correct file directory.

SORTMInn CANNOT BE CONCATENATED INPUT

EXPLANATION: SORTMInn is a concatenated input data set; use a SORTMInn DD statement for each of the concatenated files.

OUTFIL OUTPUT PARAMETER PROCESSING CONFLICT

EXPLANATION: LOCALE, C exits and COBOL exits are not supported with the OUTFIL OUTPUT feature.

OUTFIL OUTPUT PARAMETER JAVA ENVIRONMENT PROBLEM

EXPLANATION: An unexpected return from the JAVA environment occurred. This can occur if the CPU time limit has expired. Increase the amount of time in the TIME parameter.

ERRORS IN SYMNAMES STATEMENTS

EXPLANATION: Errors have been found in one or more SYMNAMES statements or JPn PARMs. See additional messages for details.

MISSING MATCHING QUOTE

EXPLANATION: The data dictionary statement or JPn PARM contains an open quote that has no matching closing quote.

SYMBOL IS A RESERVED WORD

EXPLANATION: The symbol to be defined is a reserved word.

DUPLICATE SYMBOL DEFINITION

EXPLANATION: The symbol to be defined has been defined previously.

UNKNOWN SYMBOL REFERENCED

EXPLANATION: The POSITION data dictionary statement refers to an undefined symbol.

POSITION/LENGTH VALUE OUT OF RANGE

EXPLANATION: The data dictionary statement contains a position or length field that has an invalid value.

SYMBOL/CONSTANT TOO LONG

EXPLANATION: The symbol is too long or the length of the constant is invalid for that type of constant.

INVALID CHARACTER IN CONSTANT DEFINITION

EXPLANATION: The constant contains a character that is invalid for that type of constant.

INVALID FORMAT CODE

EXPLANATION: The format specified is not one of the valid data formats.

SYNTAX ERROR

EXPLANATION: The data dictionary statement has a syntax error.

OUTFIL OUTPUT PARAMETER REQUIRES SYNCSORT INSTALLATION OPTIONS FOR JAVA ENVIRONMENT

EXPLANATION: The JAVAHOME, JZOSHOME and SYNCHOME installation options have to point to the correct libraries when the OUTFIL OUTPUT feature is used.

MODULE JVMLDM NOT FOUND, JAVA JZOS ENVIRONMENT NOT AVAILABLE

EXPLANATION: Either JZOS LOADLIB was not installed or it was not defined in the JOBLIB/STEPLIB data set.

UNABLE TO SEND EMAIL, SEE JAVA MESSAGES

EXPLANATION: Email cannot be sent. See the messages in the STDERR DD or the STDOUT DD for the reason.

CANNOT BRING UP JAVA ENVIRONMENT WITHOUT SYNCSORT SVC IN EFFECT

EXPLANATION: The MFX SVC number must be defined in your installation default options or passed as a runtime parameter. In addition the SVC module must be in LPA.

INVALID CONTROL STATEMENT FOR JOIN INPUT PROCESSING

EXPLANATION: A control statement in the xxxxCNTL DD file is not permitted in a join application. The JOINKEYS, JOIN, MERGE, OUTFIL, OUTREC, REFORMAT and SORT statements are prohibited because they are inappropriate for the subtask that reads a JOINKEYS input file.

IFTRAIL TRLUPD INVALID COLUMN

EXPLANATION: The TRLUPD subparameter of the OUTFIL IFTRAIL parameter has specified a field in columns 1 through 4 of a variable-length record. This is not permitted because the field would overlay the RDW of the record. The first defined field must start in column 5 or beyond.

IOCB: nnn IOXB: nnn SIOB: nnn CC: nn CSW: nnn SNS: nnn RBC:nnn DCWO:nnn PCRC:nnn PCRQ:nnn LREA:nnnnnnnnn

EXPLANATION: This message is issued as a WTO message by a zHPF subtask upon an unrecoverable I/O error. It contains internal diagnostic information that is intended for use by Precisely Support personnel.

UNRECOVERABLE TRANSPORT-MODE (ZHPF) ERROR ON DEVICE xxxx; REVERTING TO COMMAND-MODE FOR yyyyyyy

EXPLANATION: This message is issued when an unrecoverable zHPF error occurred and I/O processing reverted back to command-mode. xxxx is the device number on which the error occurred, and yyyyyyyy is the DD Name for either SORTIN or SORTOUT.

UNSUPPORTED FUNCTIONS WITH SORTWORK ENCRYPTION

EXPLANATION: SORT is not using encryption mode for SORTWORK because of unsupported functions.

SORTWORK ENCRYPTION USED

EXPLANATION: SORT is using encryption mode for SORTWORK. All data in the SORTWORK data set is encrypted.

IBM CALLABLE SERVICE XXXXXXXX ERROR, RETURN CODE XXXXXXXX, REASON CODE XXXXXXXX

EXPLANATION: A SORTWORK encryption process error occurred during an IBM call statement.

ACTION: For more information about the IBM return and reason codes, refer to the IBM publication z/OS Cryptographic Services Integrated Cryptographic Service Facility Application Programmer’s Guide, SC14-7508-06. Or contact Precisely Support for assistance.

HIGH PERFORMANCE DECRYPTION IS USED FOR SORTIN

EXPLANATION: MFX used the EXCP interface to decrypt the SORTIN data set.

HIGH PERFORMANCE ENCRYPTION IS USED FOR SORTOUT

EXPLANATION: MFX used the EXCP interface to encrypt SORTOUT data set.

SORTL INSTRUCTION USED U=a N=b

EXPLANATION: The values a and b are only for internal diagnostic purposes.

SORTL INSTRUCTION NOT USED; REASON CODE=xx

EXPLANATION: The reason code indicates ineligibility of the ZSORT technology. If the ZSORT accelerator path is not selected, MFX will use the traditional techniques for sorting. The reason codes (xx) are detailed below:

'FF' SORTL was disabled via installation or runtime parameter.
'FE' Traditional MFX algorithm selected for better efficiency.
'FD' No hardware support (No IBM Integrated Accelerator available).
'FC' Traditional MFX algorithm selected for better efficiency.
'FB' SUM FIELDS not supported.
'FA' File size less than 100M.
'F9' MAXSORT not supported.
'F8' PROC SYNCSORT not supported.
'F7' COPY not supported.
'F6' MERGE not supported.
'F5' JOIN not supported.
'F4' JOIN not supported.
'F3' Required memory object space not available.
'F2' PIPESORT not supported.
'F1' Central storage requirements not fully met.
'F0' Central storage requirements not fully met.
'EE' Central storage requirements not fully met.
'ED' Central storage requirements not fully met.
'EB' Exits E10, E11, E14 OR E16-19 EXIST.
'EA' DB2 Query not supported.
'E8' LRECL length greater than max supported.
'E6' Traditional MFX algorithm selected for better efficiency.
'E5' STOPAFT not supported.
'E4' SKIPREC not supported.
'E3' INCLUDE / OMIT not supported.
'E2' Central storage requirements not fully met.
'E1' Traditional MFX algorithm selected for better efficiency.
'E0' ZPSORT may be selected and file size < 2G.
'DF' EQUALS was on and key length was <=2.
'DE' VS or VBS dataset used as input.
'DC' Required MFX SVC not available.
'DD' Central storage requirements not fully met.
‘DB’ SORTIN + E15 used.
'01' Input file in sufficient sequential order for traditional MFX techniques to be more efficient.

SOME OF THE COLUMN NAMES IN ABOVE INPUT RECORD DESCRIPTION MAY BE TRUNCATED

EXPLANATION: One or more DB2 Column Name(s) in INPUT RECORD DESCRIPTION may have been truncated. Refer the corresponding DB2 table for complete Column Name.

AUTHORIZATION TURNED OFF DUE TO UNAUTHORIZED EXIT(S)

EXPLANATION: To provide better security, ZPSaver and APF-Authorization will be turned off if there are any unauthorized MODS EXITs.

Syncsort™ MFX Messages - mfx - 3.1

Syncsort™ MFX Programmers Guide

Example	WER177I TURNAROUND SORT PERFORMED
	WER185I SORTIN DCBBLK GT ACTUAL, I/O INEFF