Tags

, , , , ,

DFSORT – Informational and Error Messages

DFSORT messages can appear within your printed output or on the master console. The formats are:

ICE000I

– CONTROL STATEMENTS FOR 5694-A01, Z/OS DFSORT VvRrr – hh:mm ON day mmm dd, yyyy

Explanation:

Identifies the following for this DFSORT run:

  • DFSORT version level (v) and release level (rr)
  • Time as hours (hh) and minutes (mm)
  • Day of the week (day)
  • Date as month (mmm), day of the month (dd) and year (yyyy)

System action:

None.

Programmer response:

None.

ICE001A

TEXT BEGINS IN WRONG COLUMN

Explanation:

Critical. A continuation line started in column 1.

System action:

The program terminates.

Programmer response:

Use one of the following recommended valid methods for continuing a statement:

  • Break the previous line at a comma-blank or semicolon-blank or colon-blank before column 72 and start the continuation line in column 2-71
  • Break the previous line at column 71, put a nonblank in column 72 and start the continuation line in column 16.

See z/OS DFSORT Application Programming Guide for other valid methods of continuing a statement.

ICE002I

DUPLICATE OR CONFLICTING xxxxxxxx STATEMENT

Explanation:

The same operation definer, or mutually exclusive operation definers (SORT and MERGE, or INCLUDE and OMIT), appeared more than once in the same source (for example, SORTCNTL).

System action:

DFSORT does not analyze duplicate or conflicting statements. The first one encountered is used.

Programmer response:

No action is necessary, if the parameters on the duplicate (second and subsequent) control statements are not needed. Otherwise, consolidate the parameters from the duplicate control statements into a single control statement.

ICE003A

CONTINUATION LINE MISSING

Explanation:

Critical. A continuation line was indicated by the previous line ending with a comma, or with a nonblank entry in column 72, but no line followed.

System action:

The program terminates.

Programmer response:

Check for an overflow of parameters into column 72 or a missing continuation line.

ICE005A

BLANK NEEDED IN COLUMN 1 OR OPERATION NOT DEFINED CORRECTLY

Explanation:

Critical. One of the following errors was found:

  • An operation definer, that is, ALTSEQ, DEBUG, END, INCLUDE, INREC, |JOINKEYS, JOIN, MERGE, MODS, OMIT, OPTION, OUTFIL, OUTREC, RECORD, |REFORMAT, SORT or SUM,, started in column 1 instead of column 2. An operation definer must be preceded by at least one blank in column 1.
  • A control statement did not contain one of the valid operation definers.
  • A control statement did not contain an operation definer followed by a blank on the first line.
  • A DFSPARM PARM was continued using the continuation column.
  • A continuation line followed a line with an error.
  • A control statement passed by a parameter list contained a label.

System action:

The program terminates.

Programmer response:

Check that each control statement contains a valid operation definer and follows the syntax rules for the source of the control statements (DFSPARM, SYSIN, SORTCNTL, parameter list) including:

  • An operation definer in a control statement in SYSIN or SORTCNTL must be preceded by at least one blank or by a label and at least one blank.
  • A control statement in DFSPARM or a parameter list must not start with a label.
  • An operation definer in a control statement in DFSPARM must be preceded by at least one blank.
  • A DFSPARM PARM parameter must appear on one line.
  • A control statement must contain an operation definer followed by a blank on the first line.

ICE006A

OPERAND DEFINER ERROR

Explanation:

Critical. The first operand of a control statement did not begin on the same line as the operation definer, or an operand or operand value was not valid, or a required operand was not specified.

System action:

The program terminates.

Programmer response:

Check for statements with invalid operands, invalid operand values, missing operands, or no operands.

ICE007A

SYNTAX ERROR

Explanation:

Critical. A control statement contained an error in syntax.

System action:

The program terminates.

Programmer response:

Check the control statements for syntax errors. Some of the more common syntax errors are:

  • Unbalanced parenthesis
  • Missing comma
  • Embedded blank
  • Invalid format type
  • Invalid operator
  • Invalid constant
  • Continuation of DFSPARM PARM options using the continuation column.
  • Symbol used where it is not allowed
  • Parsed field (%nn) used where it is not allowed.

ICE008A

FIELD VALUE EXCEEDS MAXIMUM ALLOWABLE CHARACTERS

Explanation:

Critical. A specified parameter value was too long. Most parameter values have a maximum length of eight characters, but some can have longer or shorter maximum lengths.

System action:

The program terminates.

Programmer response:

Check control statements for parameter values that are too long. Refer to the description of each parameter to verify the maximum length for its values.

ICE010A

NO SORT OR MERGE CONTROL STATEMENT

Explanation:

Critical. All control statements have been processed and either:

  • No SORT or MERGE control statement or OPTION COPY statement was found, or
  • A 24-bit parameter list did not contain a SORT or MERGE control statement.

System action:

The program terminates.

Programmer response:

Make sure that the 24-bit parameter list contains a SORT or MERGE control statement. If you are not using a 24-bit parameter list, make sure you have supplied a SORT or MERGE control statement or an OPTION COPY statement.

ICE011A

DUPLICATE OR CONFLICTING OPERANDS ON THE OPTION STATEMENT

Explanation:

Critical. On an OPTION control statement, one of the following errors was found:

  • A keyword was specified twice.
  • A keyword and a variation of it were both specified. CKPT and CHKPT are variations, as are FILSZ and SIZE.
  • A keyword and its opposite were both specified. EQUALS and NOEQUALS are examples of this.

System action:

The program terminates.

Programmer response:

Check the OPTION control statement for the errors indicated in the explanation and correct the errors.

ICE012A

MISSING FIELDS OPERAND DEFINER

Explanation:

Critical. A SORT, MERGE, or SUM control statement did not contain the FIELDS operand.

System action:

The program terminates.

Programmer response:

Check for a SORT, MERGE, or SUM control statement that does not have the FIELDS operand.

ICE013A

INVALID SORT OR MERGE STATEMENT OPERAND

Explanation:

Critical. An invalid keyword operand was detected on a SORT or MERGE control statement.

System action:

The program terminates.

Programmer response:

Make sure the SORT or MERGE control statement does not contain an invalid keyword operand.

ICE014A

DUPLICATE SORT OR MERGE STATEMENT OPERAND

Explanation:

Critical. On a SORT or MERGE control statement, one of the following errors was found:

  • A keyword was specified twice.
  • A keyword and a variation of it were both specified. CKPT and CHKPT are variations, as are FILSZ and SIZE.
  • A keyword and its opposite were both specified. EQUALS and NOEQUALS are examples of this.

System action:

The program terminates.

Programmer response:

Check the SORT or MERGE control statement for the errors indicated in the explanation and correct the errors.

ICE015A

VARIABLE RECORD TOO SHORT

Explanation:

Critical. This message was issued for one of the following reasons:

  • An input data set contained an invalid RDW or BDW.
  • A record passed to DFSORT from user exit E15 or E35 contained an invalid RDW.
  • A variable-length record was too short to contain all fields or, if Blockset was not selected, shorter than L4.
  • A record did not contain the first byte of the first control field when VLSHRT was in effect and Blockset was not selected.

System action:

The program terminates.

Programmer response:

If the records are valid but too short to contain all fields, use the VLSCMP option (INCLUDE, OMIT) or VLSHRT option (INCLUDE, OMIT, SORT, MERGE) to prevent DFSORT from terminating. Otherwise, take one or more of the following actions:

  • Check that the input data set contains valid BDWs.
  • Check that the input data set and all records passed from exits contain variable-length records with valid RDWs.
  • Decrease L4 if it is too large.
  • Check the input data set and all records inserted at user exits E15 and E35 to see that all records contain all fields.
  • Remove any records that are too short.
  • Check your E15 and E35 routines and correct any errors.

If ICETOOL was used, check each ON field of the failing operator for incorrectly specified displacement (position) or length.

You can use the ICETOOL STATS operator with ON(VLEN) to show the length of the shortest variable length record. You can use the ICETOOL DISPLAY operator with ON(VLEN) to show the length of each variable length record.

ICE016A

INVALID FIELDS OPERAND VALUE

Explanation:

Critical. The FIELDS operand of a SORT or MERGE statement contained an invalid f or s value in a p,m,s or p,m,f,s field.

System action:

The program terminates.

Programmer response:

Check for invalid f and s values in the control fields.

ICE017A

INVALID POSITION OR LENGTH IN CONTROL FIELD – REASON CODE IS rsn

Explanation:

Critical. A position (p) or length (m) in a SORT or MERGE control field is invalid. rsn is the reason code associated with the error. The reason code helps you determine the specific cause of the error. Reason code values (rsn) are as follows:

  1. A length (m) was less than the minimum allowed for the specified format (f). For example:
  2. SORT FIELDS=(11,1,PD0,A)
  3. * 1 IS LESS THAN THE MINIMUM LENGTH OF 2

    * FOR A PD0 FIELD

  4. A length (m) was greater than the maximum allowed for the specified format (f). For example:
  5. MERGE FIELDS=(21,33,FS,D)
  6. * 33 IS GREATER THAN THE MAXIMUM LENGTH OF 32

    * FOR AN FS FIELD

  7. A bytes.bit position (p.x) or length (m.y) was specified but the format (f) was not BI. For example:
  8. SORT FIELDS=(7.2,3,CH,A)

    * BI MUST BE USED WITH A POSITION OF 7.2

  9. A position (p) was 0, or a bytes.bit position (p.x) was 0.x. For example:
  10. SORT FORMAT=CH,FIELDS=(21,3,D,0,5,A)
  11. * 0 IS LESS THAN THE THE MINIMUM OF 1

    * FOR A POSITION

  12. A bit position (.x) or bit length (.y) was greater than 7. For example:
  13. MERGE FIELDS=(11,5.8,BI,A)
  14. * .8 IS GREATER THAN THE MAXIMUM OF .7

    * FOR A BIT LENGTH

  15. A length (m) was 0, or a bytes.bit length (m.y) was 0.0. For example:
  16. SORT FIELDS=(11,0.0,BI,D)
  17. * 0.0 IS LESS THAN THE MINIMUM OF 0.1

    * FOR A BYTES.BIT LENGTH

  18. A position (p) plus length (m) was greater than 32753. For example:
  19. SORT FIELDS=(32751,3,CH,A)
  20. * 32751 + 3 = 32754 IS GREATER THAN

    * THE MAXIMUM OF 32753 FOR POSITION+LENGTH

  21. VLSHRT was in effect and control fields were too complex.
  22. The total length of the control fields was greater than the maximum allowed.

System action:

The program terminates.

Programmer response:

Take the action for the indicated reason code value (rsn) as follows:

  1. Ensure that each length is valid for its specified format.
  2. Ensure that each length is valid for its specified format.
  3. Ensure that BI format is used with each bytes.bit position or length.
  4. Ensure that each position is equal to or greater than 1.
  5. Ensure that each bit position and bit length is between .0 and .7.
  6. Ensure that each bytes.bit length is equal to or greater than 0.1.
  7. Ensure that the position plus length is less than or equal to 32753.
  8. Specify NOVLSHRT or reduce the complexity of the control fields.
  9. Reduce the total length of the control fields.

ICE018A

INVALID OR MISSING FIELD FORMAT – REASON CODE IS rsn

Explanation:

Critical. A field in a SORT, MERGE, INCLUDE, OMIT, |JOINKEYS, SUM, INREC, OUTREC or OUTFIL statement has an invalid format or no format. rsn is the reason code associated with the error. The reason code helps you determine the specific cause of the error. Reason code values (rsn) are as follows:

  1. A SORT, MERGE, SUM, INCLUDE, or OMIT statement has a field with an invalid format. For example:
  2. SORT FIELDS=(5,4,NG,A)
  3. * NG IS AN INVALID FORMAT
  4. SUM FIELDS=(12,2),FORMAT=CH

    * CH IS AN INVALID FORMAT FOR SUM

  5. An INCLUDE or OMIT operand of an OUTFIL statement |or |JOINKEYS statement, or an IFTHEN WHEN, BEGIN or END operand of an INREC, OUTREC, or OUTFIL statement, has a field with an invalid format or has a field without a format. For example:
  6. OUTFIL FNAMES=OUT1,
  7. INCLUDE=(5,2,NG,EQ,C’AB’)
  8. * NG IS AN INVALID FORMAT
  9. OUTFIL FNAMES=OUT2,
  10. IFTHEN=(WHEN=(21,2,EQ,35,2),
  11. OVERLAY=(21:C’OK’))

    * FORMATS ARE MISSING IN WHEN CONDITION

  12. A SORT, MERGE, SUM, INCLUDE, or OMIT statement without a FORMAT=f operand, or with an invalid FORMAT=f operand, has a field without a format (that is, p,m instead of p,m,f). For example:
  13. SORT FIELDS=(5,4,BI,A,21,2,D)
  14. * FORMAT IS MISSING FOR SECOND FIELD
  15. SUM FIELDS=(12,2)

    * FORMAT IS MISSING FOR SUM FIELD

  16. D2 format was specified in the INCLUDE or OMIT operand of an OUTFIL statement |or JOINKEYS statement, or in the IFTHEN WHEN, BEGIN or END operand of an INREC, OUTREC, or OUTFIL statement. For example:
  17. INREC IFTHEN=(WHEN=(21,2,D2,EQ,C’AB’),
  18. OVERLAY=(21:C’OK’))
  19. * D2 IS INVALD FOR WHEN
  20. OUTFIL FNAMES=OUT1,
  21. INCLUDE=(5,2,D2,EQ,C’AB’)

    * D2 IS INVALID FOR OUTFIL INCLUDE

  22. More than 112 SORT or MERGE fields were specified, and Blockset was not selected.
  23. CSF, FS, UFF, SFF, Y2x or PD0 format was specified for SORT, MERGE or SUM and Blockset was not selected. For example:
  24. OPTION NOBLKSET
  25. SORT FORMAT=PD0,FIELDS=(5,3,ZD,A)

    * PD0 AND NOBLKSET SPECIFIED

System action:

The program terminates.

Programmer response:

Take the action for the indicated reason code value (rsn) as follows:

  1. Ensure that the format for each field in the SORT, MERGE, SUM, INCLUDE, and OMIT statements is valid.
  2. Specify p,m,f for each field in the INCLUDE, OMIT, WHEN, BEGIN and END operands, and ensure that the format for each field is valid.
  3. Ensure that each field in the SORT, MERGE, SUM, INCLUDE and OMIT statements has a format by specifying p,m,f or FORMAT=f with p,m, as appropriate.
  4. Use the D2 format in an INCLUDE or OMIT statement rather than in an INCLUDE or OMIT operand, or replace the D2 format with a valid format in the INCLUDE, OMIT, WHEN, BEGIN or END operand.
  5. Rerun the job with a SORTDIAG DD statement to get message ICE800I, which indicates the reason Blockset could not be used. If possible, remove the condition preventing the use of Blockset. Alternatively, reduce the number of SORT or MERGE fields to 112 or less.
  6. Rerun the job with a SORTDIAG DD statement to get message ICE800I, which indicates the reason Blockset could not be used. If possible, remove the condition preventing the use of Blockset. Alternatively, do not use a CSF, FS, UFF, SFF, Y2x or PD0 format.

ICE019A

MEMBER NAME NOT SPECIFIED FOR ddname

Explanation:

Critical. A data set indicated by the specified ddname is partitioned, but the member name was missing.

System action:

The program terminates.

Programmer response:

Ensure that a member name is specified for each partitioned data set or PDSE defined for the indicated ddname. If the ddname is a concatenation of data sets, then ensure that each partitioned data set or PDSE in the concatenation has a member name specified with it.

ICE020A

INVALID RECORD STATEMENT OPERAND

Explanation:

Critical. An invalid keyword was found in a RECORD control statement.

System action:

The program terminates.

Programmer response:

Check for invalid keywords.

ICE021A

NO TYPE OPERAND

Explanation:

Critical. RECORD TYPE was not specified for a tape work data set sort or Conventional merge application that uses one of the following:

  • VSAM input
  • an E15 exit that supplies all of the input records
  • an E32 exit that supplies all of the input records.

System action:

The program terminates.

Programmer response:

Specify RECORD TYPE=F or RECORD TYPE=V as appropriate.

ICE022A

RECORD FORMAT NOT F, V OR D

Explanation:

Critical. The TYPE operand of a RECORD control statement |or JOINKEYS control statement contained an invalid value.

System action:

The program terminates.

Programmer response:

Check that the TYPE operand value on the RECORD statement |or JOINKEYS statement is F, FB, V, VB, D, or DB. Check also for a conflict between the SORTIN/SORTOUT DCB RECFM parameter and the RECORD control statement.

ICE023A

NO LENGTH OPERAND

Explanation:

Critical. The input record length was not available. A RECORD statement with an L1 or L2 value is required when an E15 or E32 user exit supplies all of the input records, or when a temporary empty VSAM data set defined without a RECSZ value is used for input.

This message can also be issued if input processing is bypassed because of a previous error.

System action:

The program terminates.

Programmer response:

Check for:

  • A missing RECORD statement
  • A RECORD statement without a LENGTH operand or without an L1 value
  • A missing SORTIN DD statement or SORTINnn DD statement
  • A temporary empty input VSAM data set defined without a RECSZ value

ICE024A

MAXIMUM RECORD LENGTH EXCEEDED – REASON CODE IS rsn

Explanation:

Critical. A specified or calculated record length was greater than the maximum length DFSORT could process. The record length can be one of the following:

  • Input record length: Can be obtained from the L1 or L2 value of the RECORD LENGTH operand, from the RECORDSIZE value for a VSAM input data set, or from the LRECL of a non-VSAM input data set.
  • Reformatted record length: Can be obtained from the INREC statement or OUTREC statement.
  • Output record length: Can be obtained from the L3 value of the RECORD LENGTH operand, from the RECORDSIZE value for a VSAM output data set, or from the LRECL of a non-VSAM output data set.

Note that for VSAM data sets processed as variable-length, the record length is increased by 4 bytes since DFSORT prepends an RDW to each record.

rsn is the reason code associated with the error. The reason code helps you determine the specific cause of the error. Reason code values (rsn) are as follows:

  1. An input record length was greater than 32767.
  2. An input record length for fixed-length records was greater than 32760.
  3. An input record length for variable-length unspanned records was greater than 32756.
  4. An output record length was greater than 32767.
  5. An output record length for fixed-length records was greater than 32760.
  6. An output record length for variable-length unspanned records was greater than 32756.
  7. A reformatted record length was greater than 32767.
  8. A reformatted record length for fixed-length records was greater than 32760.
  9. A reformatted record length for variable-length unspanned records was greater than 32756.
  10. Blockset was not selected and the specified or calculated minimum record length (L4) was greater than the specified or calculated maximum record length (L2).
  11. Blockset was not selected and the specified or calculated minimum record length (L4) was greater than the specified or calculated average record length (L5).
  12. Blockset was not selected and the specified or calculated average record length (L5) was greater than the specified or calculated maximum record length (L2).

System action:

The program terminates.

Programmer response:

Ensure that specified and calculated record lengths are not greater than the maximum length DFSORT can process. If Blockset was not selected, rerun the job with a SORTDIAG DD statement to get message ICE800I, which indicates the reason Blockset could not be used. If possible, remove the condition preventing the use of Blockset.

ICE025A

RECORD COUNT OFF

Explanation:

Critical. The program has compared the count of input records and output records (shown in message ICE054I), taken into account the number of records inserted or deleted (shown in message ICE055I), if any, and found a discrepancy.

The message is issued when the entire output data set has been written. The message is suppressed if NOCHECK was in effect and you had an E35 user exit and no SORTOUT or OUTFIL data set.

System action:

The program terminates.

Programmer response:

The most probable cause is that you have not specified a SORTOUT or OUTFIL data set, have specified E35, and from your E35 routine have passed a return code of 8 (do not return) too early, when there are still output records remaining. If this is the case, you can avoid receiving this message by specifying OPTION NOCHECK. If this is not the case, examine any user exit routines (especially E15 and E35) for possible return code or other errors.

If a COBOL-invoking program contains an output procedure, make sure the RETURN statement is iterated until the AT END condition is executed. This occurs the next time the RETURN statement is executed after the last record was returned to you.

If the iteration of the RETURN is controlled by a PERFORM statement, the PERFORM logic should be controlled by the execution of the AT END clause of the RETURN statement.

It is possible but less likely that the error was caused by an internal sort problem.

ICE026I

SMF RECORD NOT WRITTEN TO THE SMF DATA SET (RC=nn)

Explanation:

A nonzero return code was returned from system management facilities (SMF). nn is the return code from the SMFWTM macro, in decimal.

System action:

The SMF type 16 record is not successfully written.

Programmer response:

Have your system programmer determine whether SMF is properly initialized on your system by referring to z/OS MVS System Management Facilities (SMF) for the meaning of the return code from SMFWTM.

ICE027A

END OF [ddname] FIELD BEYOND MAXIMUM RECORD LENGTH

Explanation:

Critical. If ddname is blank, then:

  • The OUTREC or INREC length exceeded 32767 bytes, or
  • if INREC was specified, a SORT, MERGE, OUTREC, or SUM field was defined as extending beyond the maximum reformatted record length.
  • otherwise, a SORT, MERGE, INREC, OUTREC, SUM, INCLUDE, or OMIT field was defined as extending beyond the maximum input record length

Otherwise, ddname indicates the first data set in the OUTFIL group for which either:

  • an OUTFIL field was defined as extending beyond the maximum OUTFIL input record length, or
  • the OUTFIL output record length exceeded 32767 bytes

System action:

The program terminates.

Programmer response:

Check all relevant control statements for incorrectly specified field position or length values. Check the record statement for incorrectly specified length values.

If an EFS field is specified in the SORT or MERGE control statement, make sure the position begins within the record.

If ICETOOL is used, check each ON field of the failing operator for incorrectly specified position or length values, and for a DISPLAY, OCCUR, RANGE, STATS, UNIQUE, or VERIFY operator, check that the LRECL of the FROM data set is at least 4.

ICE028A

TOO MANY EXITS

Explanation:

Critical. A MODS statement specified more than the maximum number of user exits.

System action:

The program terminates.

Programmer response:

Make sure that routines are specified for valid user exits only, and that each exit is associated with only one routine. Exits that can be specified in the MODS statement are E11, E15, E16, E17, E18, E19, E31, E35, E37, E38, E39, and E61.

Restriction:

For a merge-only application you can only specify exits E31, E35, E37, E38, E39, and E61.

ICE029A

IMPROPER EXIT

Explanation:

Critical. This message was issued for one of the following reasons:

  • An incorrect user exit was specified on a MODS control statement.
  • A user exit in the sort or intermediate merge phase of the program was specified for a merge application.

System action:

The program terminates.

Programmer response:

Make sure that the MODS control statement does not contain errors that resulted in the specification of an invalid program user exit number. Numbers that can be specified are E11, E15, E16, E17, E18, E19, E31, E35, E37, E38, E39, and E61.

Restriction:

For a merge-only application, you can only specify exits E31, E35, E37, E38, E39, and E61.

ICE030A

MULTIPLY DEFINED EXITS

Explanation:

Critical. This message was issued for one of the following reasons:

  • A user exit was defined twice in a MODS control statement.
  • An E15, E18, E35, or E39 user exit was specified both in the invoking program parameter list and in a MODS statement.

System action:

The program terminates.

Programmer response:

Check MODS statement for multiply defined user exits.

ICE031A

INVALID MODS OP CHAR

Explanation:

Critical. A parameter of a MODS control statement contained an invalid character.

System action:

The program terminates.

Programmer response:

Check the parameters of the MODS control statement for a length field containing something other than numeric data, a source or name field beginning with something other than an alphabetic character, or containing a special character other than $, @, or #.

ICE032A

EXIT E61 REQUIRED

Explanation:

Critical. A SORT or MERGE control statement defined a control field to be modified by a user-written routine (this was done by specifying E for the control field sequence indicator), and user exit E61 was not activated by a MODS control statement.

System action:

The program terminates.

Programmer response:

Check for conflicts in the SORT or MERGE and MODS statements with respect to E and E61.

ICE033A

CONTROL FIELD SEQUENCE INDICATOR E REQUIRED

Explanation:

Critical. User exit E61 was activated and no control fields were specified for user modification (an E control field sequence parameter was missing on a SORT or MERGE control statement).

System action:

The program terminates.

Programmer response:

Check for conflicts in the SORT or MERGE and MODS statements with respect to E and E61.

ICE034A

MODS STATEMENT OPERAND ERROR

Explanation:

Critical. This message was issued for one of the following reasons:

  • An incorrect number of parameters followed an operand defined on a MODS control statement.
  • SYSIN was specified as the third parameter for a user exit whose fourth parameter was N or C.
  • For those user exits pre-link-edited by the user (fourth parameter was N or C, or null), the third parameter (library ddname) was different for two or more exits.
  • An invalid value was specified for the fourth parameter of the statement.
  • E15=COB or HILEVEL=YES was specified and E15 was specified with T as the fourth parameter.
  • E35=COB or HILEVEL=YES was specified and E35 was specified with T as the fourth parameter.
  • S was specified for the fourth parameter, but the user exit was not E11 or E31.

System action:

The program terminates.

Programmer response:

Make sure that:

  • Each exit operand of the MODS statement is specified using correct syntax.
  • SYSIN is not specified for any user exit with the fourth parameter as N or C.
  • T has not been specified as the fourth parameter for an E15 or E35 user exit along with E15=COB or E35=COB, respectively, or HILEVEL=YES.
  • S has not been specified for the fourth parameter for an user exit other than E11 or E31.
  • The dynamic link-edit parameters (SYSIN, T, and S) have not been specified for a copy application.
  • The third parameter is specified if S or T is used for the fourth parameter.
  • The third parameter is specified for a conventional merge or tape work data set sort.

ICE035A

DUPLICATE MODS ROUTINE OPERAND

Explanation:

Critical. The same user-written routine was used for more than one user exit in a DFSORT program phase, or two or more routines had the same name.

System action:

The program terminates.

Programmer response:

Make sure that the MODS control statement does not use duplicate names.

ICE036I

B = a

Explanation:

DFSORT diagnostic message for use by IBM software support personnel.

ICE0371

G = a

Explanation:

DFSORT diagnostic message for use by IBM software support personnel.

ICE038I

NMAX APPROXIMATELY = n

Explanation:

This message gives an estimate of the maximum number of records that can be sorted using the intermediate storage and main storage available to DFSORT for the current application. The number replaces n in the text of the message as shown above. Nmax is calculated assuming that 2400-foot tapes are used. For variable-length records, the value is based on maximum record length.

System action:

None.

Programmer response:

None.

ICE039A

INSUFFICIENT MAIN STORAGE – ADD AT LEAST nK BYTES

Explanation:

Critical. There was not enough main storage available for DFSORT to run, or main storage was fragmented.

System action:

The program terminates.

Programmer response:

The message gives an estimate of how much more main storage is needed. Add at least that amount to the main storage already allocated to the program by recoding the REGION parameter or the MAINSIZE/SIZE value (see z/OS DFSORT Application Programming Guide for ways to specify this).

|For a JOINKEYS application, you may need to use REGION=0M.

This message may sometimes be issued again even after you have provided more storage because DFSORT re-estimates the amount of storage it needs at several points in the program.

Storage requirements can be reduced by decreasing either the input block size or the number of intermediate storage areas. See also messages ICE092I, ICE093I, ICE156I and ICE231I.

Make sure that storage allocation is permitted above 16 MB virtual and enough storage is available above 16 MB virtual to load the DFSORT modules.

If you are using OUTFIL processing, increase the REGION value or decrease the number of OUTFIL data sets or their block sizes; do not increase the MAINSIZE/SIZE value.

ICE040A

INSUFFICIENT WORK UNITS

Explanation:

Critical. There were not enough work data sets to allow your application to run. This can occur when work data sets are on tape. In a merge-only application, this message can result from incorrectly specifying one or more input data sets (SORTIN01, and so forth) or from using an E32 user exit without specifying the number of data sets.

System action:

The program terminates.

Programmer response:

Make sure that the DD statements do not contain errors. For a sort using tape work files, the SORTWKdd numbers must be in sequence, starting with SORTWK01, and at least three work data sets must be assigned to the program. For a Conventional merge application, make sure that the numbers for the SORTINnn DD statements are in sequence, starting with SORTIN01.

ICE041A

N GT NMAX

Explanation:

Critical. The exact number of records specified in a FILSZ or SIZE operand was greater than the maximum sort capacity calculated by the program.

System action:

The program terminates.

Programmer response:

Check all FILSZ or SIZE operands for errors. If all operands are correct, check DD statements for an error in assigning work data sets. If DD statements are correct, assign more work data sets to the program.

ICE042A

UNIT ASSIGNMENT ERROR: ddname – REASON CODE IS rsn

Explanation:

Critical. An error was detected for the data set associated with the indicated ddname. The following information is displayed in the message:

  • ddname: The input, output or work ddname (for example, SORTIN, SORTOUT or SORTWK01).
  • rsn: The reason code associated with the error. The reason code (listed below) helps you determine the specific cause of the error.

Note:

The ddname and reason code are not displayed for a tape work data set sort or conventional merge application. In this case, the message will appear as:

ICE042A UNIT ASSIGNMENT ERROR

These techniques should be avoided by not using tape work data sets for a sort or by removing the condition preventing the use of Blockset indicated by the reason code displayed in message ICE800I when a SORTDIAG DD statement is specified.

Reason code values (rsn) are as follows:

  1. VSAM and non-VSAM input data sets were specified for a merge application. Example: SORTIN01 is a VSAM data set and SORTIN02 is a non-VSAM data set. SORTIN01 and SORTIN02 are non-VSAM data sets and SORTIN03 is a VSAM data set.
  2. Concatenated VSAM and non-VSAM input data sets were specified. Example: SORTIN has a non-VSAM data set followed by a VSAM data set. SORTIN has two VSAM data sets followed by a non-VSAM data set.
  3. A DUMMY, NULLFILE, spool, pipe, or HFS data set, an HFS file or an invalid device type was specified for a work data set, or both tape and disk work data sets were specified. Example: SORTWK01 is an HFS data set.
  4. Blockset was not selected and a pipe data set was specified for input or output. Example: SORTIN is a pipe data set but Blockset could not be used.
  5. DFSORT was invoked by the ICEGENER facility, but SYSIN (or the alternate ddname for SYSIN) was not DUMMY. Control was automatically transferred to the IEBGENER system utility. Example: ICEGENER with //SYSIN DD *.
  6. The QNAME parameter was specified on an output DD statement. Example: SORTOUT with QNAME=NAME1.
  7. An HFS data set (not an HFS file) was specified for input or output. Example: SORTIN is an HFS data set.

System action:

The program terminates.

Programmer response:

For the data set associated with the indicated ddname, take the action for the indicated reason code value (rsn) as follows:

  1. Use only VSAM data sets, or only non-VSAM data sets, but not both.
  2. Use only a single VSAM data set, or concatenated non-VSAM data sets.
  3. Remove the work data sets or use only valid work data sets.
  4. Rerun the job with a SORTDIAG DD statement to get message ICE800I, which indicates the reason Blockset could not be used. If possible, remove the condition preventing the use of Blockset. Alternatively, do not use a pipe data set for input or output.
  5. If you do not need to use any IEBGENER control statements, use DUMMY for SYSIN (or the alternate ddname for SYSIN). If you do need to use IEBGENER control statements, no action is necessary.
  6. Do not use the QNAME parameter on the output DD statement.
  7. Do not use an HFS data set for input or output; you can use an HFS file for input or output.

ICE043A

INVALID DATA SET ATTRIBUTES: ddname
attribute – REASON CODE IS rsn

Explanation:

Critical. An error associated with a record format, record length or block size was detected, or a conflict between these attributes was detected. The following information is displayed in the message:

  • ddname: The input or output ddname for the associated data set (for example, SORTIN for a single or concatenated input data set used for a copy or sort application, SORTIN01 or SORTIN02 for an input data set used for a merge application, SORTOUT for an output data set, OUT1 for an OUTFIL output data set, and so on).
  • attribute=RECFM: The error is associated with a record format. The record format can be set or derived from a RECFM value or a RECORD TYPE value, or defaulted based on other attributes. The record format can be fixed length (for example, RECFM=F, RECFM=FB or TYPE=F) or variable length (for example, RECFM=V, RECFM=VB, RECFM=VS, RECFM=VBS or TYPE=V).
  • attribute=LRECL: The error is associated with a record length. The record length can be set or derived from an LRECL value, a RECORD LENGTH value, a VSAM RECORDSIZE value or the reformatted record length, or defaulted based on other attributes.
  • attribute=BLKSIZE: The error is associated with a block size. The block size can be set or derived from a BLKSIZE value, or defaulted based on other attributes.
  • rsn: The reason code associated with the error. The reason code (listed below) helps you determine the specific cause of the error.

Note:

The ddname, attribute, and reason code are not displayed for a tape work data set sort or conventional merge application. In this case, the message will appear as:

ICE043A INVALID DATA SET ATTRIBUTES

These techniques should be avoided by not using tape work data sets for a sort or by removing the condition preventing the use of Blockset indicated by the reason code displayed in message ICE800I when a SORTDIAG DD statement is specified.

Reason code values (rsn) are as follows:

  1. A fixed length output data set has a block size smaller than the record length, or a variable length output data set has a block size smaller than the record length plus four. Example: The record length is 1000 and BLKSIZE=800 is specified on the SORTOUT DD statement.
  2. The record length cannot be determined, LRECL=X was specified, or the record length is larger than the maximum allowed. Example: The SORTIN data set was created with LRECL=X.
  3. Input data sets have mixed fixed length and variable length record formats, or mixed valid and invalid record formats. Examples: Concatenated SORTIN data sets have RECFM=FB and RECFM=VB. The SORTIN01 data set has RECFM=V and the SORTIN02 data set has RECFM=FB. Concatenated SORTIN data sets have RECFM=VB and RECFM=U.
  4. A variable length spanned input data set was found after a variable length unspanned input data set. Example: Concatenated SORTIN tape data sets have RECFM=VB and RECFM=VBS.
  5. Fixed length input data sets have different record lengths. Examples: Concatenated SORTIN data sets have RECFM=FB with LRECL=100 and RECFM=FB with LRECL=80. The SORTIN01 data set has RECFM=FB with LRECL=100 and the SORTIN02 data set has RECFM=FB with LRECL=135.
  6. The record format is fixed length and the block size is smaller than the record length or is not a multiple of the record length. Example: The reformatted fixed record length is 1200 from OUTREC BUILD=(11,1200) and the SORTOUT data set has BLKSIZE=25000.
  7. An input tape data set with the largest block size was not the first data set, and the block size for that data set was not available in the DD statement, from DFSMSrmm, or from a tape management system using ICETPEX. Example: Concatenated SORTIN tape data sets are unmanaged: the first data set was created with RECFM=FB, LRECL=80 and BLKSIZE=32720 and the second data set was created with RECFM=FB, LRECL=80 and BLKSIZE=262080.
  8. Input and output data sets have mixed fixed length and variable length record formats, or mixed valid and invalid record formats. Examples: The SORTIN data set has RECFM=FB and the SORTOUT data set has RECFM=VB. The SORTIN01 data set has RECFM=VB and the SORTOUT data set has RECFM=F or RECFM=U.
  9. The record format is fixed length and the output record length is larger than the input record length or reformatted record length. Examples: The SORTIN01 data set has RECFM=FB and LRECL=80 and the SORTOUT data set has LRECL=100. The SORTIN01 data set has RECFM=FB and LRECL=80, the reformatted record length is 60 from OUTREC BUILD=(1,60) and the SORTOUT data set has LRECL=80.
  10. The record format cannot be determined or is not valid for DFSORT processing. Examples: The SORTIN data set has DUMMY or NULLFILE but does not have RECFM=value. The SORTOUT data set has RECFM=U.
  11. The track capacity of the device for the output data set was smaller than the block size for the output data set. Example: The SORTOUT data set is allocated on a 3350 and has BLKSIZE=32000.
  12. The block size cannot be determined or is not valid for DFSORT processing. Examples: The SORTIN DD statement has DUMMY or NULLFILE but does not have BLKSIZE=value. The block size of the first SORTIN data set cannot be determined
  13. The record format is variable length and the OUTFIL output data set has a fixed length record format, or OUTFIL parameter FTOV or VLFILL is specified and the OUTFIL output data set has a fixed length record format. Examples: SORTIN has RECFM=VB, OUTFIL FNAMES=OUT1 is specified, and OUT1 has RECFM=FB. SORTIN has RECFM=FB, OUTFIL FNAMES=OUT2,FTOV is specified and OUT2 has RECFM=F. SORTIN has RECFM=VB, OUTFIL FNAMES=OUT3, VLFILL=C’*’,BUILD=(70) is specified and OUT3 has RECFM=FB.
  14. The record format is fixed length and the OUTFIL output data set has a variable length record format, or OUTFIL parameter VTOF or CONVERT is specified and the OUTFIL output data set has a variable length record format. Examples: SORTIN has RECFM=FB, OUTFIL FNAMES=OUT1 is specified, and OUT1 has RECFM=VBS. SORTIN has RECFM=VB, OUTFIL FNAMES=OUT2,VTOF,BUILD=(5,60) is specified and OUT2 has RECFM=VB.
  15. The input data set with the largest block size was not the first input data set. Example: SORTIN01 has BLKSIZE=15000 and SORTIN02 has BLKSIZE=20000 and Blockset could not be used.
  16. A data set with RECFM=F has a block size that is not equal to the record length, or the first input data set has RECFM=F and is followed by a data set with a different block size. Example: SORTOUT has RECFM=F, LRECL=80 and BLKSIZE=160.

System action:

The program terminates.

Programmer response:

For the data set associated with the indicated ddname, and the indicated attribute, take the action for the indicated reason code value (rsn) as follows:

  1. Let DFSORT set the output data set block size, specify BLKSIZE=value with a value that is valid for the record length, or use an existing data set with a block size that is valid for the record length, as appropriate.
  2. Do not use a data set with LRECL=X. Ensure that the record length is available, and is not larger than 32767 or the maximum allowed for the record format. Specify LRECL=value on the DD statement, if appropriate, and especially for a DUMMY or NULLFILE data set.
  3. Ensure that all of the input data sets have fixed length record formats (for example, RECFM=FB), or that all of the input data sets have variable length record formats (for example, RECFM=VB and RECFM=VBS). Do not use a data set with RECFM=U.
  4. Ensure that a variable length spanned input data set (for example RECFM=VBS) is not preceded by a variable length unspanned input data set (for example, RECFM=VB).
  5. Ensure that all of the fixed length input data sets have the same record length. If appropriate, use fixed input data sets padded to the largest record length.
  6. Let DFSORT set the output data set block size, specify BLKSIZE=value with a value equal to or larger than the record length and a multiple of the record length, or use an existing data set with a block size that is valid for the record length, as appropriate.
  7. Use managed tapes, or specify BLKSIZE=value, with a value equal to the largest block size, in the first input DD statement.
  8. Ensure that all of the input data and output data sets have fixed length record formats (for example, RECFM=FB), or that all of the input and output data sets have variable length record formats (for example, RECFM=VB and RECFM=VBS). If you want to convert from fixed length input records to variable length output records, use an OUTFIL statement with FTOV. If you want to convert from variable length input records to fixed length output records, use an OUTFIL statement with VTOF and BUILD.
  9. Ensure that the SOLRF parameter is in effect. Use INREC or OUTREC to pad the output records to the needed length. Let DFSORT set the output record length, specify LRECL=value with a value equal to the reformatted record length, or use an existing data set with a record length equal to the reformatted record length, as appropriate.
  10. Ensure that the record format is available and is valid for DFSORT processing (for example, RECFM=F, RECFM=FB, RECFM=VB, RECFM=VBS). Do not use RECFM=U. Specify RECFM=value on the DD statement, if appropriate, and especially for a DUMMY or NULLFILE data set. Specify RECORD TYPE=value, if appropriate, and especially for a VSAM input data set.
  11. Ensure that the output data set block size is equal to or smaller than the track capacity for the device on which the output data set resides.
  12. Ensure that the block size is available and is valid for DFSORT processing. Specify BLKSIZE=value on the DD statement, if appropriate, and especially for a DUMMY or NULLFILE data set.
  13. If you want to use FTOV or VLFILL, ensure that the OUTFIL output data set has a variable length record format or no record format. If you want to convert from variable length input records to fixed length output records, use VTOF and BUILD and ensure that the OUTFIL output data set has a fixed length record format or no record format.
  14. If you want to use VTOF or CONVERT, ensure that the OUTFIL output data set has a fixed length record format or no record format. If you want to convert from from fixed length input records to variable length output records, use FTOV and ensure that the OUTFIL output data set has a variable length record format or no record format.
  15. Rerun the job with a SORTDIAG DD statement to get message ICE800I, which indicates the reason Blockset could not be used. If possible, remove the condition preventing the use of Blockset. Alternatively, specify BLKSIZE=value, with a value equal to the largest block size, in the first input DD statement.
  16. Ensure that data sets with RECFM=F have a block size equal to the record length, or specify RECFM=FB in the first input DD statement.

ICE044I

EXIT Enn INVALID OPTION

Explanation:

An invalid input/output option was passed to DFSORT at user exit E18, E19, E38, or E39. The nn value in the above message text is replaced by the number of the user exit at which the error occurred.

System action:

The invalid option is ignored.

Programmer response:

Check the parameter list passed by the user-written routine against the table in Appendix A. Valid Input/Output Options at User Exits—ICE044I before rerunning the application. An x in the table indicates an option that is allowed with the user exit in question.

ICE045I

END SORT PH

Explanation:

The sort (input) phase completed successfully. This message appears only when the BALN or POLY tape technique was used.

ICE046A

SORT CAPACITY EXCEEDED – RECORD COUNT: n

Explanation:

Critical. DFSORT was not able to complete processing with the intermediate storage available (Hiperspace or disk work data sets). For work data sets with secondary allocation allowed, DFSORT overrides system B37 abends and continues processing; this message is issued only when no more space is available in Hiperspace or on any allocated work data set.

Note:

DFSORT uses only the first volume of multi-volume work data sets.

The count n is either an approximation of the number of records or is the total number of records that DFSORT was able to read in before it used all of the available intermediate storage.

The amount of intermediate storage required can vary depending on many factors including:

  • The amount of Hiperspace DFSORT is able to use at the time the sort is run
  • The amount of main storage available
  • The degree of randomness of the records to be sorted
  • The values specified (or defaulted) for options such as DYNALOC, DYNAUTO, DYNSPC, FILSZ/SIZE, AVGRLEN, or DYNALLOC
  • The amount of padding required for short records when VLSHRT is in effect.

System action:

The program terminates.

Programmer response:

Take one or more of the following actions:

  • If dynamic allocation was used, refer to message ICE254I (if issued) for more information.
  • If JCL work data sets were used, increase the amount of work space available to DFSORT.
  • If message ICE118I was received, refer to message ICE253I for more information
  • If you are sorting variable length records, refer to message ICE098I for more information.
  • If appropriate, increase the amount of main storage available to DFSORT using the options MAINSIZE/SIZE or the JCL option REGION. Increasing the amount of main storage available to DFSORT can help DFSORT use less intermediate storage. Avoid running a large sort in a small amount of main storage as this can degrade performance and increase intermediate storage requirements. In some cases, a small amount of main storage can force DFSORT to perform an intermediate merge as indicated by message ICE247I; refer to ICE247I for more information on the consequences of an intermediate merge and how to avoid it.
  • If VLSHRT was in effect and the total size of all control fields was significantly larger than the average LRECL for the data set, you may be able to reduce the amount of work space required by reducing the total size of the control fields.

ICE047A

RECORD COUNT OFF, SPECIFIED n, RECEIVED n

RCD COUNT OFF

Explanation:

Critical. Installation option FSZEST=NO was specified or defaulted, and the number of records received was NOT equal to the value specified in the FILSZ=x or SIZE=y option in effect.

The SPECIFIED field contains the value specified in the FILSZ=x or SIZE=y option. The RECEIVED field contains the actual number of records in the input data sets (for SIZE=y) or the actual number of records to be sorted or merged (for FILSZ=x). See the explanation of SIZE=y or FILSZ=x on the OPTION statement in the z/OS DFSORT Application Programming Guide for details.

System action:

The program terminates.

Programmer response:

Make sure that the FILSZ=x or SIZE=y value is accurate. Message ICE047A can be suppressed by specifying installation option FSZEST=YES, or by using FILSZ=Ex, SIZE=Ey, FILSZ=Ux, or SIZE=Uy, thus ensuring that the value will be treated as an estimate.

If an E15 or E32 exit passes all of the records (no SORTIN or SORTINxx), use FILSZ=x rather than SIZE=y.

ICE048I

NMAX EXCEEDED

Explanation:

DFSORT exceeded the calculated sort capacity while processing the input data set, and user exit E16 was specified.

System action:

The user-written routine at E16 is entered.

Programmer response:

No response necessary. (The number of records sorted is equal to the NMAX calculated by DFSORT. See message ICE038I.)

ICE049I

SKIP MERGE PH

Explanation:

DFSORT diagnostic message for use by IBM software support personnel.

ICE050I

END MERGE PH

Explanation:

DFSORT diagnostic message for use by IBM software support personnel.

ICE051A

UNENDING MERGE

Explanation:

Critical. There was not enough main storage or work data set space available for DFSORT to run with.

System action:

The program terminates.

Programmer response:

Assign more intermediate storage or main storage and rerun the job. Reverse sequence files can require more space.

ICE052I

END OF DFSORT

Explanation:

The program completed.

System action:

Returns control to the operating system or invoking program.

Programmer response:

None.

ICE053A

OUT OF SEQUENCE

Explanation:

Critical. The current record leaving the intermediate or output phase was not in collating sequence with the last record blocked for output.

System action:

The program terminates.

Programmer response:

Contact IBM for programming support. If message ICE143I indicates the Blockset technique was selected, specifying OPTION NOBLKSET temporarily may allow you to bypass the DFSORT error.

ICE054I

RECORDS-IN: n, OUT: n

RCD IN n,OUT n

Explanation:

This message lists the number of records read by DFSORT from the input data sets, and the number of records written to SORTOUT or used as input for OUTFIL processing. The numbers replace n in the text of the message as shown above. |For a JOINKEYS subtask, |the OUT field is zero; the number of joined records is displayed |in message ICE421I for the main task. For a Conventional merge application, if an exact file size was not specified, the IN field is zero; if an exact file size was specified, it appears in the IN field.

If DEBUG CTRx was used and Blockset was not selected, the n values could be meaningless.

For a tape work data set sort or Conventional merge application, record counts that exceed 4294967295 will be displayed as asterisks.

System action:

None.

Programmer response:

If you are using user exit E15 or E35 and have any reason to suspect that you are “losing” or “gaining” records, check message ICE055I. The sum of RECORDS IN plus INSERT should always be equal to the sum of RECORDS OUT plus DELETE. If it is not, you should also receive message ICE025A.

ICE055I

INSERT n, DELETE n

Explanation:

The number of records inserted or deleted (prior to OUTFIL processing, if used) replaces the values shown as n in the above format.

If DEBUG CTRx was used and Blockset was not selected, the n values could be meaningless.

For a tape work data set sort or Conventional merge application, record counts that exceed 4294967295 will be displayed as asterisks.

System action:

None.

Programmer response:

See message ICE054I.

ICE056A

ddname NOT DEFINED

Explanation:

Critical. A required DD statement was not supplied. This message appears for:

  • Sort or copy applications without a SORTIN DD statement or E15 user exit
  • Merge applications without a SORTINnn DD statement or E32 user exit
  • |Merge applications without a specified OPTION MERGEIN |ddname or with an OPTION MERGEIN ddname also used for SORTOUT.
  • Sort, merge, or copy applications without an E35 user exit, a SORTOUT DD statement or an OUTFIL data set.
  • Tape work data set sort applications without a SORTIN DD statement or a SORTOUT DD statement
  • |The same OPTION SORTIN and OPTION SORTOUT ddname |or a missing OPTION SORTIN or OPTION SORTOUT ddname.
  • CKPT in effect with no work data set specified
  • Conventional merge applications without a SORTIN01 DD statement (Conventional merge ignores SORTIN1) or a SORTOUT DD statement.
  • A DD statement for a specified or defaulted OUTFIL ddname was not present.
  • |A DD statement for a specified JOINKEYS F1 or F2 |ddname was not present. The F1 ddname is SORTJNF1 (or ccccJNF1 if |SORTDD=cccc is in effect) if FILE=F1 or FILES=F1 is specified. The |F2 ddname is SORTJNF2 (or ccccJNF2 if SORTDD=cccc is in effect) if |FILE=F2 or FILES=F2 is specified.

System action:

The program terminates.

Programmer response:

Check the DD statements for errors.

If you are using an ICETOOL operator (for example, COPY) with a USING(xxxx) operand, be sure to use FNAMES=ddname for any OUTFIL statements you specify in xxxxCNTL.

ICE057A

SORTIN NOT SORTWK01

Explanation:

Critical. A work data set other than SORTWK01 was assigned to the same tape drive as SORTIN.

System action:

The program terminates.

Programmer response:

Check the DD statements for errors.

ICE058A

SORTOUT A WORK UNIT

Explanation:

Critical. SORTOUT was specified on the same tape drive as a work data set.

System action:

The program terminates.

Programmer response:

Check the DD statements for errors.

ICE059A

RECORD LENGTH INVALID FOR {DEVICE|ddname}

Explanation:

Critical. The intermediate record created by DFSORT from the input record was either less than 18 bytes or more than 32756 bytes when work units were tape (indicated by DEVICE) or was too large for the assigned work data set device with the indicated ddname. The error can exist for other devices in addition to the one indicated.

System action:

The program terminates.

Programmer response:

If the intermediate record is too small, redefine input record length to at least 18 bytes. If the length is too large, assign work data set devices with larger track capacity.

If EQUALS is in effect, the maximum record length is reduced by 4 bytes.

ICE060I

INVALID ddname PARAMETER

Explanation:

A PARM parameter specified in the ddname data set contained an error. If a parameter was specified more than once, the first entry was used (if valid).

System action:

Processing continues. Invalid and duplicate parameters are ignored.

Programmer response:

No action is necessary. For later runs, be sure that the optional parameters are valid. Valid PARM parameters are described in z/OS DFSORT Application Programming Guide.

ICE061A

I/O ERROR, DD ddname, DEV address, ECB completion code, CSW status bytes, SENSE sense bytes

Explanation:

Critical. This message was issued for one of the following reasons:

  • The job control statements incorrectly specified record length or blocking information for the data set located on the device indicated by the DEV field in the message.
  • A permanent error occurred during an I/O operation on the indicated device.

The most likely causes include:

  • The output data set of a merge, copy, or ICEGENER application is the same as one of the input data sets.
  • An output data set is the same as another output data set.
  • Hardware-related error.

System action:

If no user options are specified, the program terminates.

Programmer response:

Make sure that the DD statement for the data set assigned to this device contains the correct DCB information. In a merge application, if the device in error holds an input data set, make sure that the DCB information (except for BLKSIZE) specified in the SORTIN01 DD statement correctly describes the data in this device.

If ICE061A contains ECB=41 and CSW=0006, and you receive an accompanying IOS000I simulated I/O error message, you could be experiencing a missing interrupt time-out on the corresponding channel due to a large data transfer. If this is the case, either reduce the value set for the IOMAXBF installation option or raise the missing interrupt handler (MIH) value for the device associated with the error.

If the error persists, you can bypass it, in some cases, by specifying the NOBLKSET option temporarily to force DFSORT to use a different sorting technique.

ICE062A

LINK-EDIT ERROR

Explanation:

Critical. The linkage editor found a serious error.

System action:

The program terminates.

Programmer response:

Check that all the DD statements used by the linkage editor are included (SYSPRINT, SYSLIN, SYSUT1, and SYSLMOD), and that they are correct.

If the DD statements are correct, make sure that:

  • All user routines in libraries are valid object decks or load modules.
  • All user routines in the system input stream (SYSIN) are valid object decks.
  • Modules to be link-edited together do not contain duplicate entry point names.
  • A SORTLIB DD statement is specified if a tape work data set or conventional merge is used and the SORTLIB=SYSTEM installation option is specified.

ICE063A

OPEN ERROR ddname

Explanation:

Critical. An error occurred while trying to open the data set with the indicated ddname.

System action:

The program terminates.

Programmer response:

Check for any of the following:

  • A missing or invalid DD statement
  • Conflicting DCB information; for example, the records are fixed-blocked, but the block size is not a multiple of the record length
  • Concatenated mixed disk/tape or tape-only input without a DCB BLKSIZE parameter for the tape data set containing the largest block size
  • Concatenated, fixed-length input with different LRECL specifications
  • Data sets required for dynamic link-editing cannot be opened.

ICE064A

DELETE ERR

Explanation:

Critical. DFSORT was unable to delete either itself or a user exit routine. This message appears only when user exit routines are used.

System action:

The program terminates.

Programmer response:

Make sure that the user exit routines are not modifying the DFSORT code and information areas, and rerun the job.

ICE065A

PROBABLE DECK STRUCTURE ERROR

Explanation:

Critical. The end of the SYSIN data set was found before all needed user exit modules were read or the end of the SYSIN data set was not found after all specified modules were read.

System action:

The program terminates.

Programmer response:

  • Check that the MODS statement specifies the correct routines.
  • Make sure the SYSIN data set contains all user exit routines specified by the MODS statement, and no others.
  • Check for misplaced job control language statements, especially preceding a user exit routine on SYSIN.
  • Make sure nothing follows the last object deck in SYSIN.

ICE066I

APROX RCD CNT n

Explanation:

Sort capacity was reached. The count n is an approximation of the number of records DFSORT can handle with the available work data sets.

System action:

The program terminates.

Programmer response:

Respond as indicated in the accompanying message, ICE046A.

ICE067I

INVALID PARAMETER IN JCL EXEC PARM OR INVOKED PARMLIST

Explanation:

An error was found in the PARM field parameters of the EXEC statement, or in the optional parameters of the parameter list passed to DFSORT using ATTACH, LINK, or XCTL. If a parameter was specified more than once, the first entry was used (if valid).

System action:

Processing continues. Invalid and duplicate parameters are ignored.

Programmer response:

No action is necessary. For later runs, be sure that the optional parameters are valid. Valid parameters are described in z/OS DFSORT Application Programming Guide.

ICE068A

OUT OF SEQUENCE SORTINnn

OUT OF SEQ SORTINnn

Explanation:

Critical. During a merge, a data set was found to be out of sequence.

If Blockset was selected:

  • |If input was not supplied through exit E32, ddname |is the ddname associated with the data set which was found to be out |of sequence.
  • |If input was supplied through user exit E32, SORTINnn |identifies the file which was found to be out of sequence. 00 signifies |the first input file, 01 the second, and so on.

If Blockset was not selected:

  • |If input was not supplied through exit E32, SORTINnn |is the ddname associated with the data set which was found to be out |of sequence.
  • |If input was supplied through exit E32, SORTINnn |identifies the file which was found to be out of sequence. 01 signifies |the first input file, 02 the second, and so on.

System action:

The program terminates.

Programmer response:

If a user-written routine was modifying the records, check the routine thoroughly. It should not modify control fields at user exit E35. If a user-written routine is not being used, make sure that all input data sets have been sorted on the same control fields, in the same order, and that they all have a similar format. Check whether you have also received message ICE072I.

If input was supplied through user exit E32, check your routine to make sure records are passed to the merge from the correct file.

If you were reading in variable-length VSAM records through user exit E32, check the format and accuracy of the record descriptor word (RDW) you built at the beginning of each record.

If Blockset was not selected, rerun the job with a SORTDIAG DD statement to get message ICE800I, which indicates the reason Blockset could not be used. If possible, remove the condition preventing the use of Blockset.

ICE069A

INVALID SIGN

Explanation:

Critical. For a tape work data set sort or conventional merge, the first byte of signed numeric data with leading separate sign (that is, CSL or ASL data), or the last byte of signed numeric data with trailing separate sign (that is, CST or AST), did not contain a valid sign character of ‘+’ (plus) or ‘-‘ (minus).

System action:

The program terminates.

Programmer response:

Rerun the job with a SORTDIAG DD statement to get message ICE800I, which indicates the reason Blockset could not be used. If possible, remove the condition preventing the use of Blockset. Blockset treats a ‘-‘ (minus) sign as negative and any other sign (for example, ‘+’ (plus) or blank) as positive. If you must use tape work data sets or conventional merge, use ‘+’ for all of the positive signs in your CSL, CST, ASL and AST data.

ICE070A

EXIT xxxxxxxx NOT FOUND

Explanation:

Critical. This message was issued for one of the following reasons:

  1. If xxxxxxxx is CSECT, the CSECT name of the user exit specified for a dynamically linkedited user exit was incorrect.
  2. If xxxxxxxx is not CSECT, it is a member name specified in the MODS statement that could not be found in the appropriate library data set.

System action:

The program terminates.

Programmer response:

For case 1, change the CSECT name to be the same as the member name specified in the MODS statement.

For case 2:

  • If you specified an exit ddname for the member, make sure the member is present in the library data set with that ddname.
  • If you did not specify an exit ddname for the member, make sure the member is present in a library identified by the STEPLIB/JOBLIB or link library.

ICE071A

INVALID RETURN CODE FROM EXIT Enn [RC=x, CASE=id]

Explanation:

Critical. An E15, E16, E32, or E35 user exit passed back an invalid return code to DFSORT. The user exit can be part of an invoking program, such as a COBOL input or output procedure.

nn is the number of the user exit that passed back return code x.

x is the return code passed to DFSORT from the user exit; it prints as the decimal equivalent of the 32-bit value in register 15.

id is an identifier that helps you determine why return code x is invalid and what the valid return codes are for the situation.

System action:

The program terminates.

Programmer response:

Check the exit number (nn), return code (x), and case identification (nn) against the table in Appendix B. User Exit Return Codes—ICE071A. Change your user exit to pass an appropriate valid return code (that is, one marked with an x in the table) for the identified situation. As shown in the table, installation option EXITCK=WEAK can be used to avoid this message and continue processing for certain invalid return codes from the E15 and E35 user exits.

In a COBOL-invoking program containing an input or output procedure, check that control passes through the end of the input procedure before the output procedure is entered, and through the output procedure before the sort is ended.

Also check that the user exit did not overlay register 15, for example, by inadvertently including the register in a load multiple (LM) instruction.

For complete details of how return codes are interpreted in various situations for the E15, E16, E32, and E35 user exits, see the chapter on using your own user exit routines in the z/OS DFSORT Application Programming Guide. In particular, see the detailed tables in the section on the E15/E35 return codes and EXITCK.

ICE072I

FIELD NOT WITHIN MINIMUM RECORD LENGTH

Explanation:

A RECORD statement specified a minimum record length (L4) that cannot contain all fields specified in the SORT, MERGE, INCLUDE, OMIT, INREC, OUTREC, or SUM statements.

System action:

The L4 value is adjusted. Processing continues.

Programmer response:

None.

ICE073A

VARIABLE RECORD TOO LONG

Explanation:

Critical. This message was issued for one of the following reasons:

  1. A variable length record was larger than the maximum length specified or defaulted.
  2. The sum of the record length and the control field lengths was larger than 32767 bytes.
  3. For a tape work data set sort, a variable length record was larger than 32752 bytes (or 32748 with EQUALS in effect).
  4. OPTCD=Q was not specified on the DD statement for an ASCII tape input data set.
  5. An invalid RDW or BDW was found.

System action:

The program terminates.

Programmer response:

For case 1, check the input both at E15 and E35, if used, and in SORTIN. Then delete the extra long records or increase the SORTIN or SORTOUT DD statement DCB LRECL value or the RECORD statement L1, L2, or L3 value, as appropriate.

If you are using INREC or OUTREC, check that a SORTOUT DD LRECL value or L3 value is at least as large as the reformatted output record length.

If you have VSAM records, remember that they are increased in length by the 4-byte record descriptor word (RDW) added when they enter DFSORT. If you are inserting or modifying records through E15, check the format of the RDW you are building at the beginning of each record.

For case 2, if the Blockset technique was selected, you may be able to run the application by specifying OPTION NOBLKSET.

You can use the ICETOOL STATS operator with ON(VLEN) to show the length of the longest variable length record. You can use the ICETOOL DISPLAY operator with ON(VLEN) to show the length of each variable length record.

For case 3, either reduce the record lengths, or replace the tape work data sets with disk work data sets so the Blockset technique can be used.

For case 4, ensure that OPTCD=Q is specified on all ASCII tape input DD statements.

For case 5, ensure that all RDWs and BDWs are valid.

ICE074I

RECORD LENGTH L1 OR L3 OVERRIDDEN

Explanation:

The L1 value for the LENGTH parameter of the RECORD statement was not the same as the LRECL value for SORTIN or SORTIN01, or the L3 value was not the same as the SORTOUT LRECL value. For VSAM, the equivalent of LRECL is maximum RECSZ.

System action:

Processing continues with the L values overridden.

Programmer response:

For subsequent runs, check all the record lengths. Take special note of the L2 value. If you did not specify one, it defaulted to the value you specified for L1 (and was not overridden by the LRECL value). If the L2 value was too small, it could have caused your application to terminate at any of a number of points, and the error can be difficult to detect.

The input record type and maximum record length is shown in message ICE088I or ICE089I. If you have variable-length input records, check that the L1 value specified is actually a maximum.

The output record type and maximum record length is shown in message ICE090I or ICE091I. If you have variable-length output records, check that the L3 value specified is actually a maximum.

ICE075A

VSAM CB ERROR (nn) AT aaaaaa

Explanation:

Critical. aaaaaa represents the storage address of the control block at which the error was detected. nn is the VSAM return code, in decimal, from a VSAM macro.

System action:

The program terminates, unless the error is detected during close, when the program tries to close all remaining VSAM data sets before terminating.

Programmer response:

Refer to z/OS DFSMS Macro Instructions for Data Sets for the meaning of the error code and, if possible, take appropriate action.

ICE076A

VSAM INPUT ERROR i (nnn) ddname

Explanation:

Critical. i is either P (physical) or L (logical), describing the type of error encountered for the data set with the indicated ddname. nnn is the VSAM feedback code (RPLERRCD) from a GET macro, in decimal.

System action:

The program terminates.

Programmer response:

Refer to z/OS DFSMS Using Data Sets or z/OS DFSMS Macro Instructions for Data Sets for the meaning of the error code and, if possible, take appropriate action.

ICE077A

VSAM OUTPUT ERROR i (nnn) [ddname]

Explanation:

Critical. i is either P (physical) or L (logical), describing the type of error encountered. nnn is the VSAM feedback code (RPLERRCD) from a PUT macro, in decimal. The ddname of the data set in error is given, if available.

System action:

The program terminates.

Programmer response:

Refer to z/OS DFSMS Using Data Sets or z/OS DFSMS Macro Instructions for Data Sets for the meaning of the error code and, if possible, take appropriate action.

A VSAM logical error, reason code 8, can occur for a non-empty KSDS, RRDS, or VRRDS output data set if NORESET is in effect, or if the data set is defined without the REUSE option.

A VSAM logical error, reason code 12, can occur if the output data set is a KSDS and either the VSAM keys are not in ascending binary sequence or there are duplicate keys. If so, ensure that the keys are in ascending binary sequence and that there are no duplicate keys.

Refer to z/OS DFSORT Application Programming Guide for more information about VSAM data sets.

ICE078A

VSAM OPEN ERROR (nnn) ddname

Explanation:

Critical. nnn is the VSAM OPEN ERROR return code (ACBERFLG) in decimal, for the data set with the indicated ddname.

System action:

The program terminates.

Programmer response:

Refer to z/OS DFSMS Macro Instructions for Data Sets for the meaning of the error code and, if possible, take appropriate action.

Some of the more common reasons for a VSAM OPEN error are as follows:

  • An empty data set is used for input, but NVSAMEMT is in effect.
  • Concatenated VSAM data sets are used.
  • The same VSAM data set defined without REUSE is used for both input and output, but RESET is in effect.

ICE079A

VSAM CLOSE ERROR (nnn) ddname

Explanation:

Critical. nnn is the VSAM CLOSE ERROR return code (ACBERFLG), in decimal, for the data set with the indicated ddname.

System action:

The program terminates.

Programmer response:

Refer to z/OS DFSMS Using Data Sets or z/OS DFSMS Macro Instructions for Data Sets for the meaning of the error code and, if possible, take appropriate action.

ICE080I

IN MAIN STORAGE SORT

Explanation:

All records were sorted in main storage or data space. Work data sets were not used. Hiperspace was not used.

System action:

None.

Programmer response:

None.

ICE081A

FIRST COMMUNICATION AREA SPACE EXCEEDED

Explanation:

Critical. The complexity of the application caused dynamic areas and routines to exceed the total fixed amount of storage allowed for them in the first communication area. This situation normally occurs due to specification of one or more of the following (in approximate order of importance):

  • A large number of SORT, MERGE, INREC, or OUTREC fields
  • Use of an E61 user exit
  • Use of the VLSHRT option
  • Use of the NOSZERO option
  • Use of an ICETEXIT routine
  • Very large records.
  • An EFS program requesting statements with a large number of fields.

System action:

The program terminates.

Programmer response:

Reduce the complexity of the application. For example, reduce the number of SORT fields or specify OPTION NOVLSHRT, if possible.

ICE082I

CHECKPOINT CANCELLED

Explanation:

No more work data set tracks were available; therefore, the tracks allocated for CKPT were given back to the sort work data sets.

System action:

The program continues, but no checkpoints are taken.

Programmer response:

Increase the work space allocation for the next run.

ICE083A

RESOURCES WERE UNAVAILABLE FOR DYNAMIC ALLOCATION OF WORK DATA SETS (xxxx)

Explanation:

Critical.

  • If xxxx is 064K:

    The work space needed for each work data set exceeds the limit of 64K tracks for a single, physical data set. Dynamic allocation could not be attempted.

  • If xxxx is not 064K:

    DFSORT attempted to dynamically allocate work data sets using the DYNALOC, DYNSPC, and DYNALLOC values in effect. Dynamic allocation failed; xxxx indicates the failure code returned by the system’s dynamic allocation facility. See z/OS MVS Programming: Authorized Assembler Services Guide for an explanation of the failure code.

Two commonly received return codes are:

0218

The device type is defined to the system, but the requested device has insufficient space available. For example, the device type is defined to the system but no devices of that type have been installed, or all devices of that type are mounted as private.

021C

The device type is not defined to the system. For example, SYSDX was specified instead of SYSDA.

However, in a DFSMS environment, the return code is usually 970C regardless of the specific error encountered.

System action:

The program terminates.

Programmer response:

  • If xxxx is 064K:

    Use the DYNALLOC=(,n) parameter to increase the maximum number of work data sets (n) such that the work space needed for each work data set does not exceed 64K tracks.

  • If xxxx is not 064K:

    Ensure that work data sets can be dynamically allocated.

If message ICE118I was received, specify FILSZ=En with a reasonably accurate estimate of the number of records to be sorted. If you cannot specify FILSZ=En, use DYNSPC=n to decrease the primary space allocated.

|For a JOINKEYS operation, you can supply any needed |parameters as follows:

|

|

  • In DFSPARM for the JOINKEYS main task. |
  • In JNF1CNTL for the JOINKEYS F1 subtask. |
  • In JNF2CNTL for the JOINKEYS F2 subtask.

ICE084I

{BSAM|EXCP|VSAM} ACCESS METHOD USED FOR ddname

Explanation:

This message identifies the access method used for the identified data set.

System action:

None.

Programmer response:

None, unless you have any problems reading or writing the data set. If EXCP was used, you can force DFSORT not to use EXCP by specifying BSAM on the DEBUG control statement or as an EXEC PARM.

ICE085A

SECOND COMMUNICATION AREA SPACE EXCEEDED – ADD AT LEAST nK BYTES TO REGION

Explanation:

Critical. The complexity of the application caused dynamic areas and routines to exceed the total fixed amount of storage allowed for them in the second communication area. This situation normally occurs due to specification of one or more of the following (in approximate order of importance):

  • A large number of SORT, MERGE, INREC, or OUTREC fields
  • Use of an E61 user exit
  • Use of the VLSHRT option
  • Use of the NOSZERO option
  • Use of an ICETEXIT routine
  • A large number of SUM fields.
  • A large number of OUTFIL fields.

System action:

The program terminates.

Programmer response:

  • If n is not zero, increase the REGION value by at least n KB, and ensure that the MAINSIZE value in effect is at least 200 KB.
  • If n is zero and the MAINSIZE value in effect is less than 200 KB, increase the MAINSIZE value to at least 200 KB.
  • If n is zero and the MAINSIZE value in effect is at least 200 KB, reduce the complexity of the application. For example, reduce the number of sort fields or specify OPTION NOVLSHRT, if possible.

ICE088I

jobname.stepname.procstepname, INPUT LRECL = n, BLKSIZE = n, TYPE = t

Explanation:

Gives current job name, step name, procedure step name, and information related to the input records when SORTIN or SORTINnn is present:

  • LRECL is the largest logical record length of the input data sets.
  • BLKSIZE is the largest block size (non-VSAM) or largest control interval size (VSAM) used by DFSORT.
  • TYPE is the record format of one of the input data sets, and can be one or more of the following:
    • F – fixed-length input records
    • V – EBCDIC or ASCII variable-length input records
    • B – blocked records
    • S – standard for fixed-length records or spanned for variable-length records
    • A – ANSI control characters.

System action:

None.

Programmer response:

None.

ICE089I

jobname.stepname.procstepname, INPUT LRECL = n, TYPE = t

Explanation:

Gives the current job name, step name, procedure step name, and information related to the input records when all input is supplied by user exit E15 or E35 or when input is VSAM and DFSORT cannot obtain the control interval size:

  • LRECL is the logical record length of the input records.
  • TYPE is F for fixed-length input records, or V for EBCDIC or ASCII variable-length input records.

System action:

None.

Programmer response:

None.

ICE090I

OUTPUT LRECL = n, BLKSIZE = n, TYPE = t [(SDB)]

Explanation:

Gives information related to the output records when SORTOUT is present:

  • LRECL is the logical record length of the output records.
  • BLKSIZE is the block size (non-VSAM) or control interval size (VSAM) of the output data set.
  • TYPE is the record format of the output data set and can be one or more of the following:
    • F – fixed-length output records
    • V – EBCDIC or ASCII variable-length output records
    • B – blocked records
    • S – standard for fixed-length records or spanned for variable-length records
    • A – ANSI control characters.
  • (SDB) indicates that the system-determined optimum block size was used.

System action:

None.

Programmer response:

None.

ICE091I

OUTPUT LRECL = n, TYPE = t

Explanation:

Gives information related to the output records when neither SORTOUT nor an OUTFIL data set is present (that is, when all output records are deleted by user exit E35):

  • LRECL is the logical record length of the output records.
  • TYPE is F for fixed-length output records or V for EBCDIC or ASCII variable-length output records.

System action:

None.

Programmer response:

None.

ICE092I

MAIN STORAGE = (x,y,z)

Explanation:

Gives information related to the use of main storage for this DFSORT application:

x

The main storage value specified (subject to the SIZE/MAINSIZE limit), or supplied by default.

y

The main storage theoretically available to DFSORT, considering the MINLIM value specified when the program was installed.

z

The main storage actually available to DFSORT, after any other program took what it needed from the region (invoking program or exit routines).

The value for z is not meaningful if the storage taken by the invoking program or user exit is greater than REGION or SIZE/MAINSIZE.

The x, y, and z references to main storage apply to the total storage above and below 16 MB virtual.

System action:

None.

Programmer response:

None, unless DFSORT subsequently terminated abnormally. In that case, check the z value to see how much storage was really available to DFSORT. If space was the problem, you have probably also received message ICE039A. If storage was heavily fragmented, the result might instead be a system 80A abend in either DFSORT or one of your own routines.

You can need considerably more than the normal minimum if the region is fragmented.

ICE093I

MAIN STORAGE = (MAX,y,z)

Explanation:

Gives information related to the use of main storage for this DFSORT application:

MAX

The value MAX was in effect.

y

The main storage theoretically available to DFSORT, considering the TMAXLIM or MAXLIM values specified when the program was installed.

z

The main storage actually available to DFSORT, after any other program took what it needed from the region (invoking program or user exit routines). RESALL and RESINV are not considered.

The value for z is not meaningful if the storage taken by the invoking program or user exit is greater than REGION or SIZE/MAINSIZE.

The y and z references to main storage apply to the total storage above and below 16 MB virtual.

System action:

None.

Programmer response:

None, unless DFSORT subsequently terminated abnormally. In that case, check the z value to see how much storage was really available to DFSORT. If space was the problem, you probably also received message ICE039A. If storage was heavily fragmented, the result might instead be a system 80A abend in either DFSORT or one of your own routines.

You can need considerably more than the normal minimum if the region is fragmented.

ICE094I

SMF RECORD NOT WRITTEN

Explanation:

A DFSORT SMF record was requested, but system management facilities (SMF) was not active in the system.

System action:

Writing of the SMF record to the DFSORT SMF data set is bypassed.

Programmer response:

Have your system programmer determine if SMF is properly initialized on your system.

ICE095A

INVALID OPTION STATEMENT OPERAND

Explanation:

Critical. An OPTION control statement contained an invalid keyword operand.

System action:

The program terminates.

Programmer response:

Make sure that the OPTION control statement does not contain an invalid keyword operand. For valid keywords, refer to z/OS DFSORT Application Programming Guide.

ICE096I

SUCCESSFUL RECOVERY FROM B37 ABEND(S) FOR WORK DATA SET(S)

Explanation:

DFSORT successfully recovered from one or more system B37 abends. These abends occurred when DFSORT attempted to allocate more disk space than was available on one or more work data sets.

System action:

Processing continues.

Programmer response:

None.

ICE097I

SORT RECOVERING FROM B37 ABEND ON SORTWK DATASET

Explanation:

A system B37 abend occurred when DFSORT attempted to allocate more disk space than was available on a work data set. This message is issued only to the master console.

System action:

Processing continues.

Programmer response:

None.

ICE098I

AVERAGE RECORD LENGTH – PROCESSED: p, EXPECTED: e

Explanation:

Indicates the processed (p) and expected (e) average record length in bytes for the variable-length records processed by sort, that is, the number of bytes in the variable-length records (including the record descriptor word) divided by the number of records. The number of records includes all records received, added and not deleted during DFSORT input processing.

p is based on the number of bytes and records actually processed. e is based on DFSORT’s determination of the average record length it expected taking into account various factors such as the AVGRLEN value, the estimated input file size, the FILSZ value, and so on.

If DFSORT terminated before completing the input phase, p is based on the number of bytes and records processed up to the point of failure.

System action:

None.

Programmer response:

Take appropriate action depending on whether or not DFSORT issued message ICE046A:

  • ICE046A: If p is greater than e, specify AVGRLEN=n, where n is greater than or equal to p and is a reasonably accurate estimate of the average record length.
  • No ICE046A: If p is significantly different from e, specifying AVGRLEN=n with a reasonably accurate estimate of the average record length can prevent DFSORT from overallocating or underallocating dynamic work space. p was the actual average record length for this run. If future runs will process approximately the same amount of data and number of records, consider specifying AVGRLEN=p.

See z/OS DFSORT Application Programming Guide for additional information about parameters you can use to provide accurate information to DFSORT that can prevent overallocation or underallocation of dynamic work space (FILSZ, AVGRLEN, DYNSPC, and so on). Also, see the following messages, if issued: ICE253I, ICE254I, and ICE258I.

|For a JOINKEYS operation, you can supply any needed |parameters as follows:

|

|

  • In DFSPARM for the JOINKEYS main task. |
  • In JNF1CNTL for the JOINKEYS F1 subtask. |
  • In JNF2CNTL for the JOINKEYS F2 subtask.

ICE099A

BLDL FAILED FOR ddname DATA SET

Explanation:

Critical. An error was detected during member verification when the identified data set was defined as a member of a partitioned data set or a PDSE. The BLDL system function was used for verification. The most likely cause is that the member was not found in the data set.

System action:

The program terminates.

Programmer response:

Ensure that the specified partitioned data set or PDSE member exists.

ICE101A

xxxxxxxxxxxx STATEMENT NOT SUPPORTED FOR TECHNIQUE USED

Explanation:

Critical. The control statement indicated by xxxxxxxxxxxx is not supported for the technique used (tape work data set sort or Conventional merge). xxxxxxxxxxxx is replaced by INCLUDE/OMIT, SUM, INREC, or OUTREC.

System action:

The program terminates.

Programmer response:

Rerun the job with a SORTDIAG DD statement to get message ICE800I. ICE800I indicates the reason Blockset could not be used. If possible, remove the condition preventing the use of Blockset. Alternatively, remove the indicated statement.

ICE102A

MISSING COND OPERAND DEFINER

Explanation:

Critical. An INCLUDE or OMIT control statement did not contain a logical expression definition.

System action:

The program terminates.

Programmer response:

Check the INCLUDE or OMIT control statement for lack of a logical expression definition (COND operand).

ICE103A

INVALID INCLUDE OR OMIT STATEMENT OPERAND

Explanation:

Critical. An INCLUDE or OMIT control statement contained an invalid keyword operand.

System action:

The program terminates.

Programmer response:

  • Make sure that the INCLUDE or OMIT control statement does not contain an invalid keyword operand.
  • Make sure that the D2 format is not specified in the FORMAT=f operand.

ICE104A

INVALID INREC OR OUTREC STATEMENT OPERAND

Explanation:

Critical. An INREC or OUTREC control statement contained an invalid keyword operand.

System action:

The program terminates.

Programmer response:

Make sure that the INREC or OUTREC control statement does not contain an invalid keyword operand.

ICE105A

INVALID SORT, MERGE, OR SUM STATEMENT OPERAND

Explanation:

Critical. A SORT, MERGE, or SUM control statement contained an invalid keyword operand.

System action:

The program terminates.

Programmer response:

  • Make sure that the SORT, MERGE, or SUM control statement does not contain an invalid keyword operand.
  • Make sure that FIELDS=COPY and FORMAT=f are not both specified for the SORT or MERGE control statement.
  • Make sure that FIELDS=NONE and FORMAT=f are not both specified for the SUM control statement.
  • Make sure that the D1 format is not specified in the FORMAT=f operand.

ICE106A

DUPLICATE INCLUDE OR OMIT STATEMENT OPERAND

Explanation:

Critical. An INCLUDE or OMIT control statement contained a duplicate keyword operand.

System action:

The program terminates.

Programmer response:

Check the INCLUDE or OMIT control statement for a duplicate keyword operand.

ICE107A

DUPLICATE, CONFLICTING, OR MISSING INREC OR OUTREC STATEMENT OPERAND

Explanation:

Critical. One of the following errors was found in an INREC or OUTREC statement:

  • An operand, other than IFTHEN, was specified twice. Example:

    INREC BUILD=(5,4,C’***’,40:X),BUILD=(1,60)

  • PARSE, FIELDS, BUILD, OVERLAY or FINDREP was specified with IFTHEN or IFOUTLEN. Example:
  • OUTREC FINDREP=(IN=C’ONE’,OUT=C’TWO’),

    IFTHEN=(WHEN=INIT,OVERLAY=(25:C’YES’))

  • FIELDS and BUILD, FIELDS and OVERLAY, FIELDS and FINDREP, BUILD and OVERLAY, BUILD and FINDREP, or OVERLAY and FINDREP were specified. Example:

    OUTREC BUILD=(1,20),OVERLAY=(10:C’A’)

  • For an IFTHEN clause, WHEN was not specified. Example:

    OUTREC IFTHEN=(OVERLAY=(10:C’A’))

  • For an IFTHEN clause, WHEN=INIT, WHEN=(logexp), or WHEN=NONE was specified without PARSE, BUILD, OVERLAY, or FINDREP. Example:

    INREC IFTHEN=(WHEN=(5,1,CH,EQ,C’1′),HIT=NEXT)

  • For an IFTHEN clause, WHEN=GROUP was specified without BEGIN, END or RECORDS, or without PUSH. Example:

    INREC IFTHEN=(WHEN=GROUP,BEGIN=(9,2,CH,EQ,C’NO’))

  • For an IFTHEN clause, WHEN=(logexp), WHEN=ANY, or WHEN=NONE was specified with PARSE, but without BUILD, OVERLAY, or FINDREP. Example:
  • INREC IFTHEN=(WHEN=NONE,

    PARSE=(%01=(FIXLEN=5,ENDBEFR=BLANKS)))

  • For an IFTHEN clause, WHEN=INIT, WHEN=(logexp), WHEN=ANY, or WHEN=NONE was specified with BEGIN, END, RECORDS or PUSH. Example:

    OUTREC IFTHEN=(WHEN=INIT,PUSH=(9:5,8))

  • For an IFTHEN clause, WHEN=GROUP was specified with PARSE, BUILD, OVERLAY or FINDREP. Example:

    OUTREC IFTHEN=(WHEN=GROUP,BUILD=(9:5,8))

  • An IFTHEN clause with WHEN=INIT was preceded by an IFTHEN clause with WHEN=(logexp), WHEN=ANY or WHEN=NONE. Example:
  • OUTREC IFTHEN=(WHEN=(5,2,CH,EQ,C’AA’),
  • OVERLAY=(10:C’A’)),

    IFTHEN=(WHEN=INIT,BUILD=(1,80))

  • An IFTHEN clause with WHEN=GROUP was preceded by an IFTHEN clause with WHEN=(logexp), WHEN=ANY or WHEN=NONE. Example:
  • OUTREC IFTHEN=(WHEN=(5,2,CH,EQ,C’AA’),
  • OVERLAY=(10:C’A’)),
  • IFTHEN=(WHEN=GROUP,RECORDS=3,

    PUSH=(8:SEQ=2)))

  • An IFTHEN clause with WHEN=NONE was followed by an IFTHEN clause with WHEN=INIT, WHEN=(logexp), or WHEN=ANY. Example:
  • INREC IFTHEN=(WHEN=NONE,OVERLAY=(10:C’A’)),

    IFTHEN=(WHEN=ANY,BUILD=(1,80))

  • The first IFTHEN clause with WHEN=ANY was not preceded by an IFTHEN clause with WHEN=(logexp). Example:
  • OUTREC IFTHEN=(WHEN=INIT,OVERLAY=(10:C’A’)),

    IFTHEN=(WHEN=ANY,BUILD=(1,80))

  • An IFTHEN clause with WHEN=ANY and without HIT=NEXT was followed by an IFTHEN clause with WHEN=ANY. Example:
  • OUTREC IFTHEN=(WHEN=(5,1,CH,EQ,C’1′),
  • OVERLAY=(10:C’A’),HIT=NEXT),
  • IFTHEN=(WHEN=(5,1,CH,EQ,C’2′),
  • OVERLAY=(10:C’B’),HIT=NEXT),
  • IFTHEN=(WHEN=ANY,
  • OVERLAY=(28:C’ABC’)),

    IFTHEN=(WHEN=ANY,BUILD=(1,80))

System action:

The program terminates.

Programmer response:

Check the INREC or OUTREC control statement for the errors indicated in the explanation and correct the errors.

ICE108A

DUPLICATE SUM STATEMENT OPERAND

Explanation:

Critical. A SUM control statement contained a duplicate keyword operand.

System action:

The program terminates.

Programmer response:

Check the SUM control statement for a duplicate keyword operand.

ICE109A

INVALID POSITION OR LENGTH IN SUM FIELD – REASON CODE IS rsn

Explanation:

Critical. A position (p) or length (m) in a SUM field is invalid. rsn is the reason code associated with the error. The reason code helps you determine the specific cause of the error. Reason code values (rsn) are as follows:

  1. The length (m) was invalid for the specified format (f). For example:
  2. SUM FIELDS=(21,3,FI)
  3. * A LENGTH OF 3 IS NOT ALLOWED FOR AN FI FIELD.

    * THE LENGTH MUST BE 2, 4 OR 8.

  4. A position (p) plus length (m) was greater than 32753. For example:
  5. SUM FIELDS=(32751,3,ZD)
  6. * 32751 + 3 = 32754 IS GREATER THAN

    * THE MAXIMUM OF 32753 FOR POSITION+LENGTH

  7. A position (p) was 0 or a length (m) was 0. For example:
  8. SUM FORMAT=PD,FIELDS=(0,3)
  9. * 0 IS LESS THAN THE MINIMUM OF 1

    * FOR A POSITION

  10. A position (p) plus length (m) was greater than 4093 and Blockset was not selected. For example:
  11. OPTION NOBLKSET
  12. SUM FIELDS=(4092,2,BI)
  13. * 4092+2 = 4094 IS GREATER THAN THE MAXIMUM

    * OF 4093 FOR POSITION+LENGTH WITH NOBLKSET

System action:

The program terminates.

Programmer response:

Take the action for the indicated reason code value (rsn) as follows:

  1. Ensure that each length is valid for its specified format. For BI and FI, length must be 2, 4, or 8 bytes; for PD, length must be 1 through 16 bytes; for ZD, length must be 1 through 31 bytes; for FL, length must be 4, 8 or 16 bytes.
  2. Ensure that the position plus length is less than or equal to 32753.
  3. Ensure that each position and each length is equal to or greater than 1.
  4. Rerun the job with a SORTDIAG DD statement to get message ICE800I, which indicates the reason Blockset could not be used. If possible, remove the condition preventing the use of Blockset. Alternatively, ensure that the position plus length is less than or equal to 4093.

ICE110I

VERIFY NOT USED WITH SUM

Explanation:

A SUM control statement was specified and VERIFY was in effect, but the Blockset technique was not selected. VERIFY with SUM is not supported by the other techniques.

System action:

Processing continues with NOVERIFY in effect.

Programmer response:

Rerun the job with a SORTDIAG DD statement to get message ICE800I. ICE800I indicates the reason Blockset could not be used. If possible, remove the condition preventing the use of Blockset.

ICE111A

REFORMATTING FIELD ERROR

Explanation:

Critical. The FIELDS, BUILD, OVERLAY, IFTHEN BUILD or IFTHEN OVERLAY operand of an INREC or OUTREC statement, or the OUTREC, BUILD, OVERLAY, IFTHEN BUILD or IFTHEN OVERLAY operand of an OUTFIL statement, contained an invalid column, separator, position, length, keyword, pattern, sign, constant or value. Some common errors are:

  • A 0 value was used.
  • A null value was used where it was not permitted.
  • A null string, pattern, or sign was used.
  • A column was greater than 32752, or was followed by another column.
  • A position plus length was greater than 32753.
  • DATE=(abcd) or DATENS(abc) was specified with a, b or c not M, D, Y or 4, with M, D, Y or 4 specified more than once, or with Y and 4 both specified.
  • YDDD=(abc) or YDDDNS=(ab) was specified with a or b not D, Y or 4, with D, Y or 4 specified more than once, or with Y and 4 both specified.
  • TIME=(abc) or TIMENS=(ab) was specified with ab not 12 or 24.
  • |DT=(abcd) or DTNS=(abc) was specified with a, b |or c not M, D, Y or 4, with M, D, Y or 4 specified more than once, |or with Y and 4 both specified.
  • The length (m for p,m or FIXLEN=m for %nn) for a hexadecimal field was greater than 16376.
  • A repetition factor was greater than 4095 for a separator, or a character or hex constant was longer than 256 bytes.
  • An invalid digit or an odd number of digits was specified for a hexadecimal constant.
  • The length (m for p,m or FIXLEN=m for %nn) for a Y2 format field was not 2 for Y2C, Y2Z, Y2P, Y2S or Y2PP, or 1 for Y2D, Y2B or Y2DP, or 3–6 for Y2T, Y2W, Y2TP or Y2WP, or 2–3 for Y2U, Y2X, Y2UP or Y2XP, or 3–4 for Y2V, Y2Y, Y2VP or Y2YP.
  • |The length (m for p,m or FIXLEN=m for %nn) for a |Y4 format field was not 7-8 for Y4T or Y4W, 4 for Y4U or Y4X, or 5 |for Y4V or Y4Y.
  • The length (m for p,m or FIXLEN=m for %nn) for an edit field was less than 2 or greater than 8 for PD0.
  • The length (m for p,m or FIXLEN=m for %nn) for an edit field was greater than 8 for BI or FI, 16 for PD, 31 for ZD, 32 for CSF/FS or 44 for UFF or SFF.
  • The length (m for p,m or FIXLEN=m for %nn) for an edit field was not 4 for DT1, DT2, DT3, TM1, TM2, TM3, or TM4.
  • The length (m for p,m or FIXLEN=m for %nn) for an edit field was not 8 for DC1, DC2, DC3, TC1, TC2, TC3, TC4. DE1, DE2, DE3, TE1, TE2, TE3, or TE4.
  • The length (m for p,m or FIXLEN=m for %nn) for an edit field was not 4 or 8 for FL.
  • %nn,H or %nn,F or %nn,D was specified.
  • More than 31 digits or 44 characters were specified in an edit pattern.
  • SIGNz (where z is not S) was specified with Mn or without EDIT or EDxy.
  • x, y, or z in EDxy or SIGNz were the same character.
  • The value for LENGTH was greater than 44.
  • NOMATCH was specified after p,m or %nn rather than after CHANGE.
  • The length for a lookup input field was greater than 64 with character or hexadecimal find constants, or greater than 1 with find bit constants.
  • The length for a lookup output field was greater than 64.
  • The length for a find constant was greater than the lookup input field length.
  • A find constant was not a character, hexadecimal, or bit constant.
  • The length for a set constant or set field (m for p,m or FIXLEN=m for %nn) was greater than the lookup output field length.
  • An invalid character was specified in a find bit constant, or the number of bits for a find bit constant was not 8.
  • A set constant was not a character or hexadecimal constant.
  • The length for a sequence number was greater than 16.
  • The value for START was greater than 100000000000.
  • The value for INCR was greater than 10000000.
  • The length (m for p,m or FIXLEN=m for %nn) for a RESTART field was greater than 256 bytes.
  • A position without length (p without m) was specified for OVERLAY or IFTHEN OVERLAY.
  • A / was specified for OVERLAY or IFTHEN OVERLAY.

System action:

The program terminates.

Programmer response:

Correct the invalid value.

ICE112I

EQUALS NOT USED WITH SUM

Explanation:

A SUM control statement was specified and EQUALS was in effect, but the Blockset technique was not selected. EQUALS with SUM is not supported by the other techniques.

System action:

Processing continues with NOEQUALS in effect.

Programmer response:

Rerun the job with a SORTDIAG DD statement to get message ICE800I. ICE800I indicates the reason Blockset could not be used. If possible, remove the condition preventing the use of Blockset.

ICE113A

COMPARISON FIELD ERROR

Explanation:

Critical. The COND operand of an INCLUDE or OMIT statement, or the INCLUDE or OMIT operand of an OUTFIL statement |or |JOINKEYS statement, or the IFTHEN WHEN, BEGIN or END operand of an INREC, OUTREC, or OUTFIL statement, contained an invalid position, length, format, constant, or mask.

System action:

The program terminates.

Programmer response:

Make sure that all fields and constants are specified correctly. Make sure that the position plus the length of each field does not exceed 32753. Make sure that a shift-out (X’0E’) is not embedded within double-byte data in a character constant.

ICE114A

INVALID COMPARISON

Explanation:

Critical. One of the following situations exists:

  • The COND operand of an INCLUDE or OMIT statement, or the INCLUDE or OMIT operand of an OUTFIL statement |or JOINKEYS |statement, or the IFTHEN WHEN, BEGIN or END operand of an INREC, OUTREC, or OUTFIL statement, contained an invalid field-to-field, field-to-mask, or field-to-constant comparison, or used a field with NUM that was not FS, CSF, PD, or ZD.
  • FORMAT=SS was specified after COND in an INCLUDE or OMIT statement.
  • Locale processing was required, but a character (CH) field to binary (BI) field comparison was specified. Locale processing does not support the comparison of a CH to BI field.

System action:

The program terminates.

Programmer response:

Make sure that all of the comparisons are valid. If you specified FORMAT=SS after COND in an INCLUDE or OMIT statement, respecify it before COND. DFSORT’s locale processing might eliminate the need for CH to BI comparisons. See z/OS DFSORT Application Programming Guide for information relating to locale processing. If a CH to BI comparison is needed, specify run time option LOCALE=NONE.

ICE115A

INSUFFICIENT MAIN STORAGE

Explanation:

Critical. Storage was fragmented, the reserved storage value was too large, or the sizes of the user exits were too large compared to the total storage available to DFSORT.

Main storage refers to the storage below 16 MB virtual.

System action:

The program terminates.

Programmer response:

Add more main storage in 32 KB increments by recoding the REGION parameter or the MAINSIZE/SIZE value. See z/OS DFSORT Application Programming Guide for ways to specify MAINSIZE/SIZE.

If routines are used at user exits, their size should be added to this minimum value. For efficient sorting, allow at least 50 percent more storage than the minimum required.

This message can be issued again even after you have provided more storage because DFSORT re-estimates the amount of storage it needs at several points in the program.

Storage requirements can be reduced by decreasing either the input block size or the number of work data sets. See also message ICE092I or ICE093I.

ICE116A

SORT CAPACITY EXCEEDED

Explanation:

Critical. DFSORT was not able to complete processing with the available disk or tape work data sets. For disk work data sets with secondary allocation allowed, DFSORT overrode system B37 abends and continued processing; this message was issued only when no space was available on any allocated work data set.

Note:

DFSORT uses only the first volume of multi-volume work data sets.

The amount of work data set space required can vary depending on many factors, including:

  • The amount of main storage available
  • The degree of randomness of the records to be sorted
  • The values specified (or defaulted) for options such as FILSZ/SIZE and DYNALLOC.

System action:

The program terminates.

Programmer response:

Take one or more of the following actions:

  • If appropriate, increase the amount of main storage available to DFSORT by using the options MAINSIZE/SIZE or the JCL option REGION. Increasing the amount of main storage available to DFSORT can help DFSORT use less work data set space. Avoid running a large sort in a small amount of main storage.
  • If dynamic allocation was used, check that the values for options DYNALLOC and FILSZ/SIZE were appropriate. If necessary, specify these options.
  • If JCL disk work data sets were used, increase the amount of disk work space available to DFSORT.
  • If tape work data sets were used, check that all reels contained full-length tapes. (A bad tape may appear short because of many write errors.) If all reels contained full-length tapes, rerun the application and specify more work data sets.

ICE117A

I/O ERROR, jobname, stepname, unit address, device type, ddname, operation attempted, error description, last seek address or block count, access method. (SYNADAF)

Explanation:

Critical. This message was issued for one of the following reasons:

  • The job control statements incorrectly specified record length or blocking information for the data set located on the device indicated by the “unit address” field in the message.
  • A permanent error occurred during an I/O operation on the indicated device.

The most probable cause is a hardware-related error.

System action:

If no user options are specified, the program terminates.

Operator response:

If the “error description” field in the message does not contain

“WRNG. LEN. RECORD”

run the job again with the indicated unit offline, using an alternative unit or volume in its place at run time.

Programmer response:

Make sure that the DD statement for the data set assigned to this device contains the correct DCB information. In a merge application, if the device in error holds an input data set, make sure that the DCB information (except for BLKSIZE) specified in the SORTIN01 DD statement correctly describes the data in this device.

ICE118I

UNKNOWN FILE SIZE – FILSZ=EN MAY IMPROVE RESOURCE USAGE AND PERFORMANCE

Explanation:

DFSORT could not determine the input file size, and the number of records was not supplied by a FILSZ or SIZE value, that is, the input file size is unknown. Generally, DFSORT can automatically determine the input file size. However, in a few cases, such as when an E15 supplies all of the input records or when information about a tape data set is not available from a tape management system, DFSORT cannot determine an accurate file size.

If dynamic allocation of work space is used, DFSORT allocates the primary space according to the DYNSPC value in effect. This can result in an underallocation or overallocation, possibly leading to wasted space or an out-of-space condition, respectively. Performance may also be degraded.

System action:

None.

Programmer response:

None required, unless you receive message ICE046A or ICE083A, in which case you should specify FILSZ=En with a reasonably accurate estimate of the number of records to be sorted. If you receive message ICE046A with dynamically allocated work space and you cannot specify FILSZ=En, use DYNSPC=n to increase the primary space allocated. If you receive message ICE083A and you cannot specify FILSZ=En, use DYNSPC=n to decrease the primary space allocated.

You may want to specify FILSZ=En even if you don’t receive message ICE046A or ICE083A, because doing so may improve resource usage and performance.

|For a JOINKEYS operation, you can supply any needed |parameters as follows:

|

|

  • In DFSPARM for the JOINKEYS main task. |
  • In JNF1CNTL for the JOINKEYS F1 subtask. |
  • In JNF2CNTL for the JOINKEYS F2 subtask.

Note:

FILSZ=E0 is ignored.

ICE119A

SUM FIELD OVERLAPS CONTROL FIELD

Explanation:

Critical. A sum field in a SUM control statement overlapped a control field in a SORT or MERGE control statement.

System action:

The program terminates.

Programmer response:

Make sure that the sum fields in the FIELDS operand of the SUM control statement do not overlap control fields in the FIELDS operand of the SORT or MERGE control statement.

ICE120I

EXIT Enn IGNORED

Explanation:

User exit E14 or E2n was specified in the MODS statement, as identified in the message by Enn. Exit Enn is not supported and cannot be entered.

System action:

The Enn operand is checked for correct syntax, but the user exit is not used.

Programmer response:

Optional. Correct the MODS statement by removing the identified Enn operand.

ICE121A

FILE SIZE IS TOO LARGE

Explanation:

Critical. The amount of data to be sorted exceeded a DFSORT implementation limit for the maximum number of records that can be sorted. DFSORT cannot handle the amount of data regardless of environmental factors, such as the amount of work data set space provided. Specific implementation limits include:

  1. Variable-length records – 4294967295 records
  2. EQUALS in effect – 4294967295 records
  3. VLSHRT in effect – 2147483647 records
  4. Blockset technique not selected – 2147483647 records

System action:

The program terminates.

Programmer response:

For cases 1 through 3, perform the sort on subsets of the data set containing less than the indicated maximum number of records. Then merge the sorted subsets into a single data set.

For case 4, rerun the job with a SORTDIAG DD statement to get message ICE800I, which indicates the reason Blockset could not be used. If possible, remove the condition preventing the use of Blockset. Alternatively, perform the sort on subsets of the data set containing less than the indicated maximum number of records. Then merge the sorted subsets into a single data set.

ICE122A

keyword VALUE INVALID

Explanation:

Critical. The numeric value specified for the indicated keyword exceeded the DFSORT processing limit of 562949953421311 records (Blockset selected) or 2147483647 records (Blockset could not be used).

System action:

The program terminates.

Programmer response:

Specify a numeric value for the indicated keyword that is less than the processing limit.

ICE123I

CKPT OR CHKPT OPTION IGNORED

Explanation:

CKPT or CHKPT was specified in the SORT or OPTION control statement for a sort application, IGNCKPT=YES was specified during installation, and the Blockset technique was selected. The Blockset technique does not support the automatic checkpoint/restart facility, so the CKPT or CHKPT option was ignored.

System action:

The program continues, but no checkpoints are taken.

Programmer response:

Specifying NOBLKSET on the OPTION control statement will allow you to take checkpoints, except in cases where only the Blockset technique can be used (for example, when an OUTFIL control statement is specified).

ICE124A

SUM FIELD OVERLAPS RECORD DESCRIPTOR WORD

Explanation:

Critical. A sum field in a SUM control statement overlapped the record descriptor word (RDW) for variable-length record processing.

System action:

The program terminates.

Programmer response:

Make sure that the sum fields in the FIELDS operand of the SUM control statement do not overlap the RDW.

ICE125A

SUM FIELD OVERLAPS SUM FIELD

Explanation:

Critical. A sum field in a SUM control statement overlapped another sum field.

System action:

The program terminates.

Programmer response:

Make sure that the sum fields in the FIELDS operand of the SUM control statement do not overlap.

ICE126A

INCONSISTENT REFORMATTING FOR {*INREC|*OUTREC|ddname}: REASON CODE rsn, IFTHEN n

Explanation:

Critical. The FIELDS, BUILD, or IFTHEN BUILD operand of an INREC or OUTREC statement, or the OUTREC, BUILD or IFTHEN BUILD operand of an OUTFIL statement, contained a field that was inconsistent with the format (fixed or variable) of the input or output records, or with other fields.

OUTFIL data sets for which VTOF or CONVERT is used have variable-length input records and fixed length output records. OUTFIL data sets for which FTOV is used have fixed-length input records and variable-length output records.

The following information is displayed in the message:

  • *INREC if the error is associated with an INREC statement. *OUTREC if the error is associated with an OUTREC statement. ddname if the error is associated with an OUTFIL statement.
  • rsn: The reason code associated with the error. The reason code (listed below) helps you determine the specific cause of the error.
  • n: 0 if the error is not associated with an IFTHEN clause. Otherwise, n identifies the number of the IFTHEN clause associated with the error (starting at 1 for the first IFTHEN clause).

The statement and operand associated with the error are identified as follows:

  • *INREC and n=0 indicates that the FIELDS or BUILD operand of the INREC statement caused the error.
  • *OUTREC and n=0 indicates that the FIELDS or BUILD operand of the OUTREC statement caused the error.
  • ddname and n=0 indicates that the OUTREC or BUILD operand of an OUTFIL statement caused the error. ddname identifies the first data set in the associated OUTFIL group.
  • *INREC and n>0 indicates that an IFTHEN BUILD operand of the INREC statement caused the error. n identifies the number of the associated IFTHEN clause (starting at 1 for the first IFTHEN clause in the INREC statement).
  • *OUTREC and n>0 indicates that an IFTHEN BUILD operand of the OUTREC statement caused the error. n identifies the number of the associated IFTHEN clause (starting at 1 for the first IFTHEN clause in the OUTREC statement).
  • ddname and n>0 indicates that an IFTHEN BUILD operand of an OUTFIL statement caused the error. ddname identifies the first data set in the associated OUTFIL group. n identifies the number of the associated IFTHEN clause (starting at 1 for the first IFTHEN clause in the OUTFIL statement).

Reason code values (rsn) are as follows:

  1. An IFOUTLEN=n operand was specified without an IFTHEN operand.

    Example:

    OUTREC IFOUTLEN=50

  2. The last position was specified without a corresponding length for fixed-length input records.

    Examples (fixed-length input):

    INREC BUILD=(1,5,6X,8)

    or

    OUTFIL FNAMES=O1,

    OUTREC=(1,20,28),FTOV

  3. For variable-length input records, the last position was specified without a corresponding length for one, but not all, of the FIELDS or BUILD operand of the INREC statement, the FIELDS or BUILD operand of the OUTREC statement, or the OUTREC or BUILD operand of an OUTFIL statement (without a VTOF or CONVERT operand):

    Examples (variable-length input):

    INREC FIELDS=(1,20,31)

    OUTREC FIELDS=(1,25)

    or

    OUTREC BUILD=(1,20,31,10)

    OUTFIL BUILD=(1,25,27)

  4. A column overlapped the previous output field in the reformatted record.

    Example (fixed-length input):

    INREC IFTHEN=(WHEN=INIT,

    BUILD=(81:SEQNUM,8,ZD)),

    IFTHEN=(WHEN=(81,8,ZD,EQ,+1),

    BUILD=(3,20,20:C’ABC’))

  5. A VTOF or CONVERT operand was specified without an OUTREC or BUILD operand for variable-length input record to fixed-length output record conversion in an OUTFIL statement.

    Example (variable-length input):

    OUTFIL VTOF

    Note:

    VTOF cannot be used with an IFTHEN or OVERLAY operand.

  6. A VLFILL=C’x’ or VLFILL=X’yy’ operand was specified without an OUTREC or BUILD operand for variable-length input records in an OUTFIL statement.

    Example (variable-length input):

    OUTFIL VLFILL=C’*’

    Note:

    VLFILL cannot be used with an IFTHEN or OVERLAY operand.

  7. An OUTREC or BUILD operand did not specify any input or separation fields.

    Example (fixed-length input):

    OUTFIL OUTREC=(//)

System action:

The program terminates.

Programmer response:

Take the action for the indicated reason code value (rsn) as follows:

  1. Specify an IFTHEN operand with an IFOUTLEN=n operand.

    Example:

    OUTREC IFOUTLEN=50,

    IFTHEN=(WHEN=(5,1,CH,EQ,C’A’),

    OVERLAY=(21:C’N’)),

    IFTHEN=(WHEN=NONE,OVERLAY=(21:C’Y’))

  2. Specify the last position with a corresponding length.

    Example (fixed-length input):

    INREC BUILD=(1,5,6X,8,25)

    OUTFIL FNAMES=O1,

    OUTREC=(1,20,28,40),FTOV

  3. Specify the last position without a corresponding length for the INREC, OUTREC and OUTFIL statements, or specify the last position with a corresponding length for the INREC, OUTREC, and OUTFIL statements, as appropriate.

    Examples (variable-length input):

    INREC FIELDS=(1,20,31)

    OUTREC FIELDS=(1,20,5X,21)

    or

    OUTREC BUILD=(1,20,31,10)

    OUTFIL BUILD=(1,20,5X,21,10)

  4. Ensure that columns do not overlap previous fields in the reformatted record.

    Example (fixed-length input):

    INREC IFTHEN=(WHEN=INIT,

    BUILD=(81:SEQNUM,8,ZD)),

    IFTHEN=(WHEN=(81,8,ZD,EQ,+1),

    BUILD=(3,20,25:C’ABC’))

  5. Specify an OUTREC or BUILD operand with the VTOF or CONVERT operand.

    Example (variable-length input):

    OUTFIL VTOF,BUILD=(5,60)

  6. Specify an OUTREC or BUILD operand with the VLFILL=C’x’ or VLFILL=X yy operand.

    Example (variable-length input):

    OUTFIL VLFILL=C’*’,BUILD=(1,4,8,45)

  7. Specify an input or separation field.

    Example (fixed-length input):

    OUTFIL OUTREC=(//,X)

ICE127I

OPTIONS: OVFLO=s,PAD=s,TRUNC=s, SPANINC=s,VLSCMP=x,SZERO=x, RESET=x,VSAMEMT=x,DYNSPC=t

Explanation:

See ICE133I.

ICE128I

OPTIONS: SIZE=n,MAXLIM=n,MINLIM=n, EQUALS=x,LIST=x,ERET=a, MSGDDN=b

Explanation:

See ICE133I.

ICE129I

OPTIONS: VIO=x,RESDNT=c, SMF=e,WRKSEC=x,OUTSEC=x, VERIFY=x,CHALT=x,DYNALOC=d, ABCODE=j

Explanation:

See ICE133I.

ICE130I

OPTIONS: RESALL=n,RESINV=n,SVC=g, CHECK=x,WRKREL=x,OUTREL=x, CKPT=x,COBEXIT=f

Explanation:

See ICE133I.

ICE131I

OPTIONS: TMAXLIM=n,ARESALL=n, ARESINV=n,OVERRGN=n,CINV=x, CFW=x, DSA=t

Explanation:

See ICE133I.

ICE132I

OPTIONS: VLSHRT=x,ZDPRINT=x,
IEXIT=x,TEXIT=x,LISTX=x,
EFS=h,EXITCK=k,PARMDDN=q,
FSZEST=x

Explanation:

See ICE133I.

ICE133I

OPTIONS: HIPRMAX=p, DSPSIZE=r,ODMAXBF=n,SOLRF=x, VLLONG=x, VSAMIO=x,MOSIZE=r

Explanation:

|Messages ICE127I through ICE133I, ICE235I and |ICE236I indicate the options in effect for a Blockset sort, copy, or merge application or a Peerage/Vale sort application.

When DFSORT is invoked by JCL, these options can come from the EXEC PARM field, the SYSIN data set, the DFSPARM data set, or the installation defaults. When DFSORT is invoked dynamically, these options can come from the SORTCNTL data set, the DFSPARM data set, the invocation parameter list, or the installation defaults.

DFSORT can change the options due to conflicting specifications or for performance reasons. Some options are not meaningful for all applications (for example, HIPRMAX applies to a sort application, but not to a copy or merge application.)

For information on where the options can be specified and on the order of override, see z/OS DFSORT Application Programming Guide. Message values |for ICE127I through ICE133I are as follows:

x

‘Y’ for YES; ‘N’ for NO

n

A decimal value representing bytes

a

‘RC16’ or ‘ABEND’

b

‘SYSOUT’, or the alternate ddname for the message data set

c

‘ALL’ for eligible DFSORT modules loaded into LPA; ‘NONE’ for eligible DFSORT modules not loaded into LPA. DFSORT automatically determines the RESDNT status; you cannot override this status nor specify it as an option.

d

‘N’ for NO, or (y,n) where y is the dynamic allocation device name and n is a decimal value for the number of data sets

e

‘SHORT’ , ‘FULL’ , or ‘NO’

f

‘COB1’ or ‘COB2’

g

A decimal value representing the SVC number, or ‘109A’ for SVC 109 using the alternate SVC module

h

EFS program name, or ‘NONE’

j

‘MSG’, or a decimal value representing the ABCODE number

k

‘S’ for STRONG; ‘W’ for WEAK

p

A decimal value representing megabytes, or ‘OPTIMAL’

q

‘DFSPARM’, or the alternate ddname for the DFSPARM data set

r

A decimal value representing megabytes, or ‘MAX’

s

‘RC0’, ‘RC4’, or ‘RC16’

t

A decimal value representing megabytes

System action:

None.

Programmer response:

None.

Notes:

  1. |Do not expect the values in ICE127I through |ICE133I, ICE235I and ICE236I to be identical to the installation-option values selected at your site. You can use the ICETOOL DEFAULTS operator to show all the installation option values.
  2. Messages ICE131I, ICE133I |and ICE236I are printed only for Blockset.

ICE134I

NUMBER OF BYTES SORTED: n

Explanation:

n is the total number of bytes “sorted”; that is, the number of bytes in records for which control field processing was performed. The following insert/delete/alter processing is performed before control field processing and is taken into account when determining n: SORTIN, SKIPREC, STOPAFT, E15, and INCLUDE/OMIT. Other processing that can affect the number of bytes actually manipulated by DFSORT (for example, INREC) is done after control field processing, and is not taken into account when determining n.

If the input data includes incomplete spanned segments, they will be eliminated before “sorting”. However, these incomplete spanned segments may be taken into account when determining n, in order to avoid impacting performance. If you want to ensure that n does not reflect incomplete spanned segments, you can eliminate them with copy, and sort the resulting data.

System action:

None.

Programmer response:

None.

ICE135A

[SORTIN=ddname|SORTOUT=ddname] MATCHES POSSIBLE WORK DDNAME

Explanation:

Critical. The ddname specified for OPTION statement operand SORTIN or SORTOUT in DFSPARM or in the extended parameter list was ccccWKdd, ccccWKdd, ccccDKd, or ccccDKdd. cccc is the specified or defaulted value for the SORTDD operand and d is any character. These ddnames can be used for work data sets and thus cannot be used as input or output ddnames. For example, each of the following OPTION statements in DFSPARM will result in this error message:

OPTION SORTOUT=SORTWK02

OPTION SORTIN=SORTDKA

OPTION SORTDD=ABCD,SORTIN=ABCDWK2

OPTION SORTDD=ABCD,SORTOUT=ABCDDKW1

System action:

The program terminates.

Programmer response:

Specify a ddname for SORTIN or SORTOUT that cannot be used for a work data set. For example, none of the following OPTION statements in DFSPARM will result in this error message:

OPTION SORTOUT=MYOUT

OPTION SORTIN=SORTWR01

OPTION SORTDD=ABCD,SORTIN=MYIN

OPTION SORTDD=ABCD,SORTOUT=SORTWK1

ICE136I

SPACE FOR ddname WAS READJUSTED TO CYLINDERS

Explanation:

The indicated work data set was not allocated in cylinders. DFSORT adjusted its usage of the allocated space to cylinders and could have skipped several tracks in the primary extents of the data set.

System action:

None.

Programmer response:

To optimize performance and minimize wasted disk space for future runs, change your JCL to use cylinder allocation for the indicated work data set.

ICE137A

VSAM INPUT ERROR i (nnn) text from VSAM SYNAD

Explanation:

Critical. i is either P (physical) or L (logical), describing the type of error encountered. nnn is the VSAM feedback code from a GET macro, in decimal, and is followed by the VSAM SYNAD message.

System action:

The program terminates.

Programmer response:

Refer to z/OS DFSMS Using Data Sets or z/OS DFSMS Macro Instructions for Data Sets for the meaning of the error code and, if possible, take appropriate action.

ICE138A

VSAM OUTPUT ERROR i (nnn) text from VSAM SYNAD

Explanation:

Critical. i is either P (physical) or L (logical), describing the type of error encountered. nnn is the VSAM feedback code from a PUT macro, in decimal, and is followed by the VSAM SYNAD message.

System action:

The program terminates.

Programmer response:

Refer to z/OS DFSMS Using Data Sets or z/OS DFSMS Macro Instructions for Data Sets for the meaning of the error code and, if possible, take appropriate action.

ICE139A

UNSUPPORTED VSAM DATA SET ATTRIBUTE FOR ddname

Explanation:

Critical. An attribute specified for the VSAM data set with the indicated ddname is not supported by DFSORT. DFSORT supports the following attributes:

  • If Blockset is selected: SPAN, KSDS, ESDS, RRDS, and VRRDS
  • If Blockset is not selected: SPAN, KSDS, ESDS, and RRDS

System action:

The program terminates.

Programmer response:

Remove any unsupported attributes, other than VRRDS, from the indicated VSAM data set. To use the VRRDS attribute, you must remove any condition preventing the use of Blockset. Rerun the job with a SORTDIAG DD statement to get message ICE800I, which indicates the reason why Blockset could not be used.

ICE140I

END OF PARAMETERS FROM ddname – SYSIN OR xxxxCNTL/PARAMETER LIST CONTROL STATEMENTS FOLLOW

Explanation:

An alternate parameter data set was specified with the indicated ddname. This message separates the listing of its parameters (control statements or PARM parameters) from the listing of control statements specified from other sources:

  • The SYSIN DD statement
  • The SORTCNTL DD statement
  • The invoking parameter list.

The data set’s parameters are listed only if LIST is in effect (see message ICE128I).

A parameter in a statement other than the OPTION or DEBUG control statement completely overrides the same or corresponding control statement in other sources.

A DEBUG control statement in the alternate parameter data set overrides only the same or corresponding parameters in a DEBUG control statement in the other sources. This selective override does not affect the other parameters in a DEBUG control statement in the alternate parameter data set or the other sources.

An OPTION control statement in the alternate parameter data set overrides only the same or corresponding parameters in an OPTION, SORT, or MERGE control statement in the other sources. This selective override does not affect the other parameters in an OPTION, SORT, or MERGE control statement in the alternate parameter data set or the other sources.

See z/OS DFSORT Application Programming Guide for complete details on the order of override.

System action:

None.

Programmer response:

None.

ICE141A

SPANNED RECORD ON ddname COULD NOT BE ASSEMBLED

Explanation:

Critical. A spanned record on the indicated data set could not be properly assembled. This message was issued for one of the following reasons:

  • A segment length was greater than the LRECL.
  • A segment length was less than 4 bytes.
  • The total length of segments was greater than the LRECL.
  • Segments are blocked incorrectly for VBS data sets (that is, a first and a last segment are in the same block).

System action:

The program terminates.

Programmer response:

Check the indicated data set for incorrect spanned records.

ICE142I

ddname NOT FOUND – SYSOUT USED

Explanation:

A DD statement for ddname (the specified alternate message data set) was not found. SYSOUT was used instead.

System action:

Processing continues; messages are written to SYSOUT.

Programmer response:

If you want to use an alternate message data set, provide a DD statement for ddname.

ICE143I

t
a TECHNIQUE SELECTED

Explanation:

t indicates the DFSORT technique chosen for the run, and a indicates the application chosen for the DFSORT technique. Message values are as follows:

t     BLOCKSET – disk work data set sort,
standard merge or copy
PEERAGE — disk work data set sort
VALE — disk work data set sort
CONVENTIONAL — tape work data set sort
or nonstandard merge

a     SORT
MERGE
COPY

System action:

None.

Programmer response:

None required. However, if Blockset was not selected, you may want to remove the condition preventing the use of Blockset. Rerun the job with a SORTDIAG DD statement to get message ICE800I, which indicates the reason Blockset could not be used.

ICE144A

TOO MANY SUM FIELDS

Explanation:

Critical. The complexity of the application caused dynamic areas to exceed the storage allowed for them.

System action:

The program terminates.

Programmer response:

Reduce the number of summary fields.

ICE145A

SVC nnn IS AN INVALID USER SVC

Explanation:

Critical. The DFSORT installation defaults for your site indicate that SVC nnn is the DFSORT SVC. SVC nnn is not compatible with the DFSORT release currently running. Either SVC nnn is for a release of DFSORT other than this one, or SVC nnn is a non-DFSORT SVC.

System action:

The program terminates.

Programmer response:

Report this message to your system programmer. It indicates that the DFSORT SVC was incorrectly installed.

ICE146I

END OF STATEMENTS FROM xxxxCNTL – PARAMETER LIST STATEMENTS FOLLOW

Explanation:

When a data set specified with a DD statement for xxxxCNTL is present, this message separates the listing of its statements from the listing of the statements specified in the parameter list. The statements for xxxxCNTL (if any) and the parameter list (if any) are listed only if LIST is in effect (see message ICE128I).

A statement other than OPTION or DEBUG in the xxxxCNTL data set completely overrides the same or corresponding statement in the parameter list.

A DEBUG statement in the xxxxCNTL data set overrides only the same or corresponding operands in a DEBUG statement in the parameter list. This selective override does not affect the other operands in a DEBUG statement in the xxxxCNTL data set or parameter list.

An OPTION statement in the xxxxCNTL data set overrides only the same or corresponding operands in an OPTION, SORT, or MERGE statement in the parameter list. This selective override does not affect the other operands in an OPTION, SORT, or MERGE statement in the xxxxCNTL data set or parameter list. (OPTION statement operands LIST, NOLIST, LISTX, NOLISTX, EFS, MSGDDN, MSGPRT, SORTDD, SORTIN, and SORTOUT are not used if specified in the xxxxCNTL data set.)

For complete details on the order of override, see z/OS DFSORT Application Programming Guide.

System action:

None.

Programmer response:

None.

ICE147A

OPTION STATEMENT OPERAND SORTIN OR SORTOUT NOT ALLOWED

Explanation:

Critical. The OPTION statement operand SORTOUT was specified for a Conventional merge, or the operand SORTIN or SORTOUT was specified for a tape work data set sort, or ICETOOL was used for a tape work data set sort.

System action:

The program terminates.

Programmer response:

Remove the SORTIN or SORTOUT operand. You can use the SORTDD operand of the OPTION statement to provide alternate ddnames for SORTIN and SORTOUT.

If ICETOOL was used, do not use tape work data sets.

ICE148A

ddname CONCATENATION NOT ALLOWED

Explanation:

Critical. SORTINnn or SORTWKdd data sets were concatenated.

System action:

The program terminates.

Programmer response:

Use separate DD statements for SORTINnn or SORTWKdd data sets.

ICE149A

DFSORT IS NOT LICENSED FOR USE ON THIS SYSTEM – RETURN CODE x AND REASON CODE y

Explanation:

SYS1.PARMLIB member IFAPRDxx does not define DFSORT as a feature licensed for use on this system, or an error was encountered while registering DFSORT for use on this system.

System action:

The program terminates.

Programmer response:

If the return code (x) is 12, the reason code (y) is 4, and you are licensed to use DFSORT, then you need to update the IFAPRDxx member of parmlib. See z/OS Planning for Installation for information about adding the appropriate entry to IFAPRDxx.

After you have added the appropriate entry to IFAPRDxx, you must activate it by using a SET PROD command or by IPLing the system.

For any other return and reason codes, contact the IBM Support Center.

ICE150I

VLSHRT NOT USED FOR SORT, MERGE, INCLUDE, OMIT OR SUM STATEMENT FIELDS

Explanation:

The VLSHRT option was in effect, and one or more of the following situations exists:

  • An INREC or OUTREC statement was specified.
  • A copy application was specified without an INCLUDE or OMIT statement.
  • More than one control field was specified, and Blockset was not selected.
  • The application had EFS processing in effect, and an EFS01 or EFS02 user exit routine was supplied by the EFS program.
  • Locale processing was required for sort or merge fields.

System action:

Processing continues; VLSHRT is not used for SORT, MERGE, INCLUDE, OMIT or SUM statement fields, but is used for OUTFIL INCLUDE or OMIT parameter fields, if specified.

Programmer response:

None, unless message ICE015A or ICE218A was received, in which case you can either respecify your fields to be within the shortest record in the input data set, or use equivalent OUTFIL parameters (for example, the INCLUDE and OUTREC parameters of OUTFIL instead of the INCLUDE and OUTREC statements) for the application.

If Blockset was not selected, rerun the job with a SORTDIAG DD statement to get message ICE800I, which indicates the reason Blockset could not be used. If possible, remove the condition preventing the use of Blockset.

ICE151A

TOO MANY {*INCLUDE|*OMIT| *INREC|*OUTREC|ddname} IFTHEN n CONDITIONS

Explanation:

Critical. The complexity of the conditions in a COND, INCLUDE, OMIT or IFTHEN WHEN, BEGIN or END operand caused dynamic areas to exceed the storage allowed for them. The specific cause of the error is identified as follows:

  • *INCLUDE indicates that the COND operand of the INCLUDE statement, |or the INCLUDE operand of a JOINKEYS statement, caused the error. n is 0.
  • *OMIT indicates that the COND operand of the OMIT statement, |or the OMIT operand of a JOINKEYS statement, caused the error. n is 0.
  • ddname and n=0 indicates that the INCLUDE or OMIT operand of an OUTFIL statement caused the error. ddname identifies the first data set in the associated OUTFIL group.
  • *INREC indicates that an IFTHEN WHEN, BEGIN or END operand of the INREC statement caused the error. n identifies the number of the associated IFTHEN clause (starting at 1 for the first IFTHEN clause in the INREC statement).
  • *OUTREC indicates that an IFTHEN WHEN, BEGIN or END operand of the OUTREC statement caused the error. n identifies the number of the associated IFTHEN clause (starting at 1 for the first IFTHEN clause in the OUTREC statement).
  • ddname and n>0 indicates that an IFTHEN WHEN, BEGIN or END operand of an OUTFIL statement caused the error. ddname identifies the first data set in the associated OUTFIL group. n identifies the number of the associated IFTHEN clause (starting at 1 for the first IFTHEN clause in the OUTFIL statement).

System action:

The program terminates.

Programmer response:

Reduce the number of conditions, or the size of the constants, in the COND, INCLUDE, OMIT or IFTHEN WHEN, BEGIN or END operand that caused the problem. Alternatively, you may be able to avoid reducing the number of conditions, or the size of the constants, by using one of the following techniques:

  • If NOSZERO is in effect and you can treat numeric –0 and +0 values as signed (that is, different) for this application, use the SZERO option.
  • If possible, rewrite the conditions to use substring comparison tests (see z/OS DFSORT Application Programming Guide for details)
  • Use an INREC or OUTREC statement with multiple IFTHEN clauses to “OR” sets of conditions together, and set a “flag” after the end of each record that satisfies a condition. Use an OUTFIL statement to keep (INCLUDE) or delete (OMIT) the records which have the flag on, and then remove the flag.

    In the following example, the input data set has RECFM=FB and LRECL=80. a1 to an and b1 to bn represent relational conditions. We use an INREC statement to set a ‘Y’ flag in position 81 after the end of each record for which any specified condition is true. We use an OUTFIL statement to INCLUDE the records with a ‘Y’ in position 81, and then we remove the flag so the output records have the same length as the input records.

    //MULT EXEC PGM=ICEMAN

    //SYSOUT DD SYSOUT=*

    //SORTIN DD DSN=…

    //SORTOUT DD DSN=…

    //SYSIN DD *

    OPTION COPY

    * If a1,OR,a2,OR,…,an is true,

    * set flag in 81 to ‘Y’.

    INREC IFTHEN=(WHEN=(a1,OR,a2,OR,…,an),

    OVERLAY=(81:C’Y’)),

    * If b1,OR,b2,OR,…,bn is true,

    * set flag in 81 to ‘Y’.

    IFTHEN=(WHEN=(b1,OR,b2,OR,…,bn),

    OVERLAY=(81:C’Y’)),

    * If none of the conditions is true,

    * set flag in 81 to ‘N’.

    IFTHEN=(WHEN=NONE,OVERLAY=(81:C’N’))

    * If the flag in 81 is ‘Y’, include the

    * records.

    OUTFIL INCLUDE=(81,1,CH,EQ,C’Y’),

    * Remove the flag byte.

    OUTREC=(1,80)

    /*

ICE152I

OVERFLOW DURING SUMMATION – RC=n

Explanation:

The application was successfully processed, but overflow occurred for one or more pairs of summary fields. DFSORT set a return code of 0 or 4 as indicated by n. DFSORT only set a return code of 4 if OVFLO=RC4 was in effect and summary fields overflowed.

System action:

Summation continues for pairs of records for which overflow does not occur. Summation is not performed for pairs of records for which overflow would occur; the original records are left unchanged. DFSORT passes back a return code of n unless it sets a higher return code for some other reason.

Programmer response:

If appropriate, redesign the records so that summary fields do not overflow, or, if possible, use INREC to increase the size of the summary fields (see z/OS DFSORT Application Programming Guide ), or specify the OVFLO=RC0, OVFLO=RC4, or OVFLO=RC16 run-time option to provide a different return code for this situation.

ICE153A

COBOL EXIT NOT SUPPORTED FOR TECHNIQUE USED

Explanation:

Critical. An E15 or E35 user exit written in COBOL was specified, but is not supported for the technique used (tape work data set sort or Conventional merge).

System action:

The program terminates.

Programmer response:

Rerun the job with a SORTDIAG DD statement to get message ICE800I. ICE800I indicates the reason Blockset could not be used. If possible, remove the condition preventing the use of Blockset. Alternatively, remove the COBOL user exit.

ICE154A

STOPAFT NOT SUPPORTED FOR TECHNIQUE USED

Explanation:

Critical. STOPAFT was in effect but is not supported for the technique used (tape work data set sort).

System action:

The program terminates.

Programmer response:

Use disk work data sets, if possible, or remove the STOPAFT option.

ICE155I

STOPAFT OR SKIPREC NOT APPLICABLE TO MERGE

Explanation:

A MERGE control statement was specified and STOPAFT or SKIPREC was in effect. Neither STOPAFT nor SKIPREC can be used with MERGE.

System action:

Processing continues; STOPAFT or SKIPREC is ignored.

Programmer response:

None.

ICE156I

MAIN STORAGE ABOVE 16-MEGABYTE = (y,z)

Explanation:

Supplies information on the amount of storage available above 16 MB virtual:

y

The maximum amount of main storage available to DFSORT above 16 MB virtual.

z

The actual amount of main storage available to DFSORT above 16 MB virtual, after DFSORT has released the ARESALL and ARESINV space.

This message is only printed when Blockset is selected.

System action:

None.

Programmer response:

None.

ICE157I

EXEC PARM E15=COB OR E35=COB AND NO MODS EXIT

Explanation:

A MODS statement contained one of the following:

  • E15=COB without a corresponding E15 operand
  • E35=COB without a corresponding E35 operand.

System action:

Processing continues. The EXEC parameter E15=COB or E35=COB is ignored.

Programmer response:

Specify an E15 or E35 operand on a MODS statement or remove the EXEC parameter.

ICE158A

SYSOUT DD STATEMENT MISSING

Explanation:

Critical. Issued only to the master console to indicate that installation option NOMSGDD=QUIT was used and a message data set was required, but not specified. Corresponds to DFSORT return code 20.

System action:

The program terminates.

Programmer response:

Specify a DD statement for the message data set, using the ddname specified by MSGDDN (if any) or SYSOUT.

ICE159A

MODULE ICECOB2 NOT FOUND

Explanation:

Critical. Module ICECOB2 was not installed as part of DFSORT. An E15 or E35 user exit routine written in COBOL was to be used and COBEXIT=COB2 was in effect. Module ICECOB2 is required for COBEXIT=COB2.

System action:

The program terminates.

Programmer response:

Ask your system programmer to ensure that module ICECOB2 is available.

ICE160A

COPY FUNCTION COULD NOT BE USED – REASON CODE IS rsn

Explanation:

Critical. The COPY function was specified but could not be processed. rsn is the reason code associated with the error. The reason code helps you determine the specific cause of the error. Reason code values (rsn) are as follows:

1

The SORTIN or SORTOUT data set was BDAM.

2

FREE=CLOSE was specified (ICEGENER).

3

An attempt to open a data set caused a system error.

4

The SORTIN or SORTOUT data set resided on an unsupported device.

5

ASCII tapes had the following parameters:

(LABEL=AL or OPTCD=Q) and RECFM=D and BUFOFF¬=L

or

(LABEL=AL or OPTCD=Q) and RECFM¬=D and BUFOFF¬=0

6

An attempt to read the DSCB for the SORTIN data set caused an error.

7

An attempt to read the DSCB for the SORTOUT data set caused an error.

8

The SORTIN data set had keyed records (ICEGENER).

9

User labels were present (ICEGENER).

10

A MODS statement Exx operand had SYSIN in the third parameter or T or S in the fourth parameter (that is, dynamic link-editing was requested.)

Note:

For ICEGENER, SYSUT1 is equivalent to SORTIN and SYSUT2 is equivalent to SORTOUT.

System action:

The program terminates.

Programmer response:

Correct the situation indicated by the reason code (rsn).

ICE161A

COBEXIT=COB2 AND COBOL E15 AND E35 EXITS WERE FOUND

Explanation:

Critical. COBEXIT=COB2 was in effect; therefore, separately compiled COBOL E15 and E35 user exits were not allowed together for COPY processing.

System action:

The program terminates.

Programmer response:

When COBEXIT=COB2 is in effect, use either a COBOL E15 user exit or a COBOL E35 user exit for copy applications, but not both.

ICE162I

ICEIEXIT CHANGED ONE OR MORE OPTIONS IN EFFECT

Explanation:

The initialization exit (ICEIEXIT) was used to change one or more of the options that apply to your application. DFSORT used the changed options where appropriate. Messages ICE127I through ICE133I|, ICE235I and ICE236I indicate which options DFSORT used.

System action:

None.

Programmer response:

No action is necessary. If appropriate, see your system programmer for an explanation of the changes made with the ICEIEXIT routine.

ICE163A

DFSORT CANNOT FIND THE IEBGENER MODULE

Explanation:

Critical. This message, issued only to the master console, indicates the DFSORT ICEGENER facility attempted to transfer control to the IEBGENER module, but the DFSORT installation option for that name was the same as the name for the ICEGENER module, thus resulting in a loop.

System action:

The program terminates with user abend 163.

Programmer response:

Ensure that the name being used for the GENER installation option is an alias of the IEBGENER module and not an alias of the ICEGENER module.

ICE164A

xnnnn ABEND OCCURRED DURING EXECUTION OF ICETEXIT

Explanation:

Critical. ESTAE was in effect and an abend occurred after the installation exit ICETEXIT was called but before control was returned to DFSORT.

x

The abend type, either S for system or U for user

nnnn

The abend code

System action:

None.

Programmer response:

Notify your system programmer that the installation exit, ICETEXIT, has abended so that they can determine the cause of the abend and correct the error. You might need to rerun the job with a SYSUDUMP DD statement to get an abend dump. With ESTAE in effect, DFSORT tries to call ICETEXIT (if it has not been called already) after an earlier abend. In this case, only the information about the first abend appears in the dump. Rerun the job with DEBUG ABSTP to get the dump for the secondary abend.

ICE165I

TOTAL DATA SET TRACKS ALLOCATED: a, TRACKS USED: b

Explanation:

This message gives work data set space usage information for the sort run. Message values are as follows:

a

Total primary and secondary disk work space allocated and available throughout sort processing (in tracks). This space is not available for use by other applications.

b

Total primary and secondary disk work space actually used during sort processing (in tracks).

Note:

In some cases, DFSORT may free up JCL-specified work space if it is determined that the space is not needed for the sort.

System action:

None.

Programmer response:

None.

ICE168I

CENTURY WINDOW FOR Y2 FORMAT FIELDS IS FROM ssss TO eeee

Explanation:

Indicates the starting year (ssss) and ending year (eeee) for the century window to be used in conjunction with the specified Y2 format fields.

System action:

None

Programmer response:

None

ICE170I

FORMAT OPERAND IGNORED

Explanation:

A FORMAT=f operand was specified on a SORT, MERGE, SUM, INCLUDE or OMIT statement in which p,m,f was used for all of the fields. For example:

SORT FORMAT=BI,FIELDS=(5,4,CH,A,12,2,PD,A,21,8,BI,D)

System action:

f from p,m,f is used for each field. f from FORMAT=f is not used for any of the fields.

Programmer response:

Optional. Remove FORMAT=f, or remove any or all f values in FIELDS that match the f value in FORMAT=f. For example, the SORT statement above could be changed to either of the following SORT statements to eliminate the ICE170I message:

SORT FIELDS=(5,4,CH,A,12,2,PD,A,21,8,BI,D)

SORT FORMAT=BI,FIELDS=(5,4,CH,A,12,2,PD,A,21,8,D)

ICE171I

SORTOUT LRECL OF x IS DIFFERENT FROM SORTIN(NN) LRECL OF y – RC=n

Explanation:

The application was successfully processed, but the SORTOUT LRECL (x) and SORTIN/SORTINnn LRECL (y) were not equal. DFSORT set a return code of 0 or 4 as indicated by n. DFSORT only sets a return code of 4 if:

  • PAD=RC4 was in effect and x was larger than y (LRECL padding), or
  • TRUNC=RC4 was in effect and x was smaller than y (LRECL truncation).

System action:

Processing continues and DFSORT passes back a return code of n, unless it sets a higher return code for some other reason.

Programmer response:

If appropriate, change the LRECL of SORTOUT or SORTIN/SORTINnn so that the LRECLs are equal, or specify the PAD=RC0, PAD=RC4, or PAD=RC16 run-time option to provide a different return code for this situation.

ICE172A

XSUM IS NOT SUPPORTED – USE ICETOOL SELECT IF APPROPRIATE

Explanation:

Critical. XSUM was specified on the SUM statement. DFSORT does not support the XSUM parameter provided by a competitive sort product to write records deleted by SUM processing to a SORTXSUM DD data set.

System action:

The program terminates.

Programmer response:

If you are using SUM FIELDS=NONE with XSUM, you can perform the same function with ICETOOL’s SELECT operator. For example, if you are using XSUM as follows:

//S1 EXEC PGM= ICEMAN

//SYSOUT DD SYSOUT=*

//SORTIN DD DSN=…

//SORTOUT DD DSN=…

//SORTXSUM DD DSN=…

//SYSIN DD *

SORT FIELDS=(5,4,CH,A)

SUM FIELDS=NONE,XSUM

/*

You can use this ICETOOL job instead:

//S1 EXEC PGM=ICETOOL

//TOOLMSG DD SYSOUT=*

//DFSMSG DD SYSOUT=*

//SORTIN DD DSN=…

//SORTOUT DD DSN=…

//SORTXSUM DD DSN=…

//TOOLIN DD *

SELECT FROM(SORTIN) TO(SORTOUT)-

ON(5,4,CH) FIRST DISCARD(SORTXSUM)

/*

Related reading:

You can also perform additional functions with ICETOOL’s SELECT operator that are not available with XSUM. See z/OS DFSORT Application Programming Guide for complete details of ICETOOL’s SELECT operator.

ICE173I

NO RECORDS FOR THE SORTOUT DATA SET – RC=n

Explanation:

The application was successfully processed, but there were no records for the SORTOUT data set, as indicated by an OUT count of 0 in message ICE054I. DFSORT set a return code of 0 or 4 as indicated by n. DFSORT only sets a return code of 4 if NULLOUT=RC4 was in effect, but there were no records for the SORTOUT data set.

System action:

Processing continues and DFSORT passes back a return code of n, unless it sets a higher return code for some other reason.

Programmer response:

If appropriate, change the application to produce records for the SORTOUT data set. Alternatively, specify the NULLOUT=RC0, NULLOUT=RC4, or NULLOUT=RC16 run-time option to provide a different return code for this situation.

ICE174I

NO DATA RECORDS FOR AN OUTFIL DATA SET – RC=n

Explanation:

The application was successfully processed, but there were no data records for one or more OUTFIL data sets, as indicated by a DATA count of 0 in message ICE227I. DFSORT set a return code of 0 or 4 as indicated by n. DFSORT only sets a return code of 4 if NULLOFL=RC4 was in effect for an OUTFIL data set, but there were no data records for that OUTFIL data set.

System action:

Processing continues and DFSORT passes back a return code of n unless it sets a higher return code for some other reason.

Programmer response:

If appropriate, change the application to produce records for the relevant OUTFIL data sets (which you can identify by a DATA count of 0 in message ICE227I). Alternatively, specify the NULLOFL=RC0, NULLOFL=RC4, or NULLOFL=RC16 run-time option on the relevant OUTFIL statements to provide a different return code for this situation.

ICE175I

ATTEMPT TO REALLOCATE VIO WORK DATA SETS TO REAL RESULTED IN VIO

Explanation:

Since VIO=NO was in effect, DFSORT attempted to reallocate work data sets to real (non-VIO) devices, but could not. Since the reallocated data sets were directed to VIO again, DFSORT continued processing with the VIO work data sets, and issued this warning message. The use of VIO for work data sets is not recommended because:

  • It prevents the use of large format data sets
  • Performance might be degraded since DFSORT’s Memory Object, Hiperspace, and Dataspace functions already exploit processor storage to avoid DASD I/O to work datasets.

System action:

Processing continues using the VIO work data sets. Large format data sets are not used.

Programmer response:

No action is necessary. If appropriate, verify that the DFSMS Automatic Class Selection (ACS) routines do not force DFSORT work data sets to VIO.

ICE176A

service SERVICE ERROR (xy)

Explanation:

Critical. The indicated system service failed when DFSORT called it. Message values are as follows:

x

The return code from the service, in decimal.

y

The reason code from the service, in decimal, or zero if unavailable.

System action:

The program terminates.

Programmer response:

Contact IBM for programming support.

ICE177A

DASD CALCULATION SERVICES ERROR (xy)

Explanation:

Critical. DASD Calculation Services returned an unexpected return or reason code when DFSORT called it to determine the optimum block size for an output data set.

System action:

The program terminates.

Programmer response:

Contact IBM for programming support. You can bypass the use of system-determined block size for this application by specifying either SDB=NO or a BLKSIZE value on the DD statement for the output data set.

ICE178I

REALLOCATING VIO SORTWK DATA SETS TO REAL SORTDK DATA SETS USING UNIT=device

Explanation:

SORTWKdd data sets specified in the JCL were allocated on virtual devices (VIO). Because the VIO=NO installation option was specified or defaulted, DFSORT will attempt to reallocate the SORTWKdd data sets as SORTDKdd data sets using devices of the type indicated by device.

System action:

Processing continues; DFSORT attempts to reallocate the data sets.

Programmer response:

If appropriate, allocate the SORTWKdd data sets on real devices to avoid reallocation.

ICE179A

RESOURCES WERE UNAVAILABLE FOR VIO REALLOCATION OF WORK DATA SETS (xxxx)

Explanation:

Critical. SORTWKdd data sets specified in the JCL were allocated on virtual devices (VIO). Because the VIO=NO installation option was specified or defaulted, DFSORT attempted to reallocate the SORTWKdd data sets as SORTDKdd data sets using a real device of the type indicated in message ICE178I. The reallocation failed; xxxx indicates the failure code returned by the system’s dynamic allocation facility. See z/OS MVS Programming: Authorized Assembler Services Guide for an explanation of the failure code.

Two commonly received return codes are:

0218

The real device type is defined to the system, but the requested device has insufficient space available. For example, the real device type is defined to the system but no devices of that type have been installed, or all devices of that type are mounted as private.

021C

The real device type is not defined to the system. For example, 3380 was specified instead of 3390.

However, in a DFSMS environment, the return code is usually 970C regardless of the specific error encountered.

System action:

The program terminates.

Programmer response:

Ensure that the VIO SORTWKdd data sets can be reallocated on the real device indicated in message ICE178I, or if appropriate, allocate the SORTWKdd data sets on real devices to avoid reallocation.

Alternatively, specify installation option VIO=YES (can degrade performance). See z/OS DFSORT Installation and Customization for details on the VIO installation option.

ICE180I

HIPERSPACE STORAGE USED = nK BYTES

Explanation:

n is the number of Kilobytes of Hiperspace storage used during this sort. If n is zero, Hiperspace storage was not used.

System action:

None.

Programmer response:

None.

ICE181A

HIPERSPACE READ ERROR (xx) [yyyyyyyy]

Explanation:

Critical. The HSPSERV SREAD service request for a Hiperspace read failed. xx is the HSPSERV return code (in decimal). yyyyyyyy is the reason code (set only when the return code is 8).

System action:

The program terminates.

Programmer response:

Refer to the HSPSERV service documentation in the z/OS MVS Programming: Authorized Assembler Services Reference EDT-IXG for a description of HSPSERV return codes and reason codes. If possible, take appropriate action.

The use of Hiperspace can be bypassed by specifying HIPRMAX=0 on the OPTION control statement.

ICE182A

HIPERSPACE WRITE ERROR (xx) [yyyyyyyy]

Explanation:

Critical. The HSPSERV SWRITE service request for a Hiperspace write failed. xx is the HSPSERV return code (in decimal). yyyyyyyy is the reason code (set only when the return code is 8).

System action:

The program terminates.

Programmer response:

Refer to the HSPSERV service documentation in the z/OS MVS Programming: Authorized Assembler Services Reference EDT-IXG for a description of HSPSERV SWRITE return codes and reason codes. If possible, take appropriate action.

The use of Hiperspace can be bypassed by specifying HIPRMAX=0 on the OPTION control statement.

ICE183A

CONDITIONS NOT MET TO USE THE SAME VSAM DATA SET FOR indd AND outdd

Explanation:

Critical. The indd DD statement and outdd DD statement both specified the same VSAM data set, but one of the following conditions prevented DFSORT from using the same VSAM data set for input and output:

  • The application is a copy or merge
  • NOVSAMIO is in effect
  • NORESET is in effect
  • The VSAM data set is not defined with REUSE

System action:

The program terminates.

Programmer response:

If you want to sort the VSAM data set in-place, ensure that VSAMIO and RESET are in effect, and that the VSAM data set is defined with REUSE. Otherwise, ensure that the indd DD and outdd DD statements do not specify the same VSAM data set.

ICE184I

THE NUMBER OF RECORDS SORTED WITH EQUAL KEYS IS n

Explanation:

n is the number of records sorted having equal control keys.

System action:

None.

Programmer response:

None.

ICE185A

AN xnnnn ABEND WAS ISSUED BY DFSORT, ANOTHER PROGRAM OR AN EXIT (PHASE m y)

Explanation:

Critical. DFSORT detected a system or user abend while it’s ESTAE routine was in effect. The abend may have been issued by DFSORT, another program that called DFSORT, or a user exit called by DFSORT. Although DFSORT detected the abend, DFSORT is not necessarily the cause of the abend.

This message gives details about the abend as follows:

x

The abend type, either S for system or U for user

nnnn

The abend code

This message gives details about DFSORT’s application mode (if known at the time of the error) and phase at the time DFSORT detected the abend.

m

S, M, or C for a Blockset sort, merge, or copy, respectively. m is P when the Peerage/Vale technique was used. m can also be blank if the abend occurred before DFSORT determined the application type.

y

Phase number 0, 1, 2, 3, or 4.

System action:

The program terminates.

Programmer response:

Use the information in the abend dump to determine if DFSORT, a calling program, or a user exit caused the abend, and take appropriate action.

For system abends, see the appropriate systems codes document.

User abends are program specific. If Unnnn is reported in the message, nnnn in the range 1000-1675 or 2222 may or may not have been issued by DFSORT. nnnn outside that range was not issued by DFSORT.

ICE186A

DFSORT CONTINUED AFTER ERROR AND OUTPUT IS USABLE

Explanation:

Critical. An error was detected or an abend occurred; however, the sort, copy, or merge was completed successfully. The SORTOUT data was written successfully or an E35 user exit disposed of all of the output records. The SORTOUT data set written by DFSORT was closed successfully.

System action:

The program terminates with the abend code.

Programmer response:

The SORTOUT data set can be used (provided the system did not delete it) even though the program terminated abnormally. Because of the error, one of the following DFSORT functions below was not completed successfully:

  • The writing of final and statistical messages
  • The writing of an SMF record, if appropriate
  • The calling of a termination exit, if present
  • The closing of data sets, releasing of space, and other cleanup functions.

ICE187I

DFSORT SVC LEVEL INCOMPATIBLE WITH DFSORT PROGRAM LEVEL

Explanation:

The running level of DFSORT did not match the installed level of the DFSORT SVC. This incompatibility had no effect on the DFSORT run if the SVC was not needed. If the SVC was needed, the run could have terminated with a system abend code of 56D or other failure. DFSORT uses the SVC with certain disk devices and to write the SMF record. See z/OS DFSORT Installation and Customization for more information about installing the SVC. Message ICE816I was also printed if DFSORT abended trying to call the SVC.

System action:

Processing continues.

Programmer response:

Ask your system programmer to check that the DFSORT SVC is installed properly for this level of DFSORT and that the correct routing code for the SVC is selected. If necessary, rerun the job with a SORTDIAG DD dummy statement to get message ICE816I.

ICE188I

DATA SPACE STORAGE USED = nK BYTES

Explanation:

n is the number of Kilobytes of data space storage used during this sort. If n is zero, data space storage was not used.

System action:

None.

Programmer response:

None.

ICE189A

BLOCKSET REQUIRED BUT COULD NOT BE USED – REASON CODE IS rsn

Explanation:

Critical. DFSORT’s primary technique, Blockset, could not be used due to the reason indicated by reason code rsn, the meaning of which is documented in message ICE800I.

Blockset was required to handle one of the following situations which cannot be handled by DFSORT’s secondary techniques:

  • LOCALE processing
  • OUTFIL processing
  • |JOINKEYS processing
  • |MERGEIN processing
  • Y2x, Y2xx, |Y4x, PD0, FS, CSF, UFF, or SFF format
  • PARSE, OVERLAY, FINDREP, IFTHEN, or IFOUTLEN processing
  • INREC or OUTREC processing with one of the following:
    • p,m,HEX
    • p,HEX
    • p,m,TRAN=LTOU
    • p,TRAN=LTOU
    • p,m,TRAN =UTOL
    • p,TRAN=UTOL
    • p,m,TRAN=ALTSEQ
    • p,TRAN=ALTSEQ
    • p,m,f
    • p,m,lookup
    • p,m,JFY=(…)
    • p,m,SQZ=(…)
    • %nn or %n
    • SEQNUM
    • DATE1, DATE1(c), DATE1P, DATE2, DATE2(c), DATE2P, DATE3, DATE3(c), DATE3P, or +n and -n variations (for example, DATE1-20 or DATE3P+20)
    • DATE4, DATE, DATE=(abcd), DATENS=(abc), YDDD=(abc) or YDDDNS=(ab),
    • TIME1, TIME1(c), TIME1P, TIME2, TIME2(c), TIME2P, TIME3, TIME3P, TIME, TIME=(abc), or TIMENS=(ab)
    • +n
    • –n
    • (…)
  • A VSAM extended addressability data set
  • To set the SORTOUT LRECL from the L3 length (without E35, INREC or OUTREC), the OUTREC length or the INREC length, with SOLRF in effect
  • an FL format sort field with NOSZERO in effect
  • VLLONG in effect and SORTOUT present
  • VSAMEMT in effect for a sort or merge with VSAM input
  • The same VSAM data set was specified for both input and output
  • An HFS file was specified for input or output
  • A tape data set with a block size greater than 32760 bytes was specified for input or output
  • SDB=LARGE or SDB=INPUT was in effect and DFSORT selected a block size greater than 32760 bytes for a tape output data set
  • VLSHRT in effect with a SUM statement
  • Position plus length for a control field exceeded 4093
  • Position plus length for a summary field exceeded 4093
  • ICETOOL called DFSORT for DATASORT or SUBSET processing
  • ICETOOL called DFSORT for an operation involving SORTOUT, and NULLOUT=RC16 is in effect
  • DB2 Utilities called DFSORT.
  • INCLUDE or OMIT processing with NUM
  • A 33 to 256 byte PD, ZD, CSL, CST, CLO, CTO, ASL or AST format merge field
  • A 256 byte PD format sort field with NOSZERO in effect
  • |A program dynamically allocated DFSORT input, output |or work data sets using the options for XTIOT, uncaptured UCBs, or |DSAB above 16 megabyte virtual.

System action:

The program terminates.

Programmer response:

Correct the situation indicated by the reason code (rsn) so Blockset can be used. Alternatively, you can remove the source of the requirement to use Blockset. However, this will result in the use of a less efficient technique.

ICE190A

ddname DYNALLOC CALL FAILED – RETURN CODE x AND REASON CODE y

Explanation:

Critical. For the data set with the associated ddname, the DYNALLOC SVC failed while attempting to obtain the pathname for an HFS file, or while attempting to determine if the data set was an HFS data set. x and y are the return code and reason code, respectively, from the DYNALLOC SVC.

System action:

The program terminates.

Programmer response:

Refer to the explanation for DYNALLOC Return Codes in z/OS MVS Programming: Authorized Assembler Services Guide for more information about the indicated return code and reason code. If possible, take appropriate action.

ICE191I

DFSORT SVC NOT AVAILABLE – PERFORMANCE MAY BE DEGRADED

Explanation:

An input, output, or work data set was on a cached disk control unit, but the DFSORT SVC was either not installed on the system or installed incorrectly. DFSORT did not use its SVC to set the optimal caching mode for the data set, which could have lengthened DFSORT’s elapsed time. Message ICE816I was also printed if DFSORT abended while trying to call the SVC.

System action:

Processing continues.

Programmer response:

Have your system programmer check to see that the DFSORT SVC has been installed properly for this level of the DFSORT program and that the correct routing code for the SVC has been selected. If necessary, rerun the job with a SORTDIAG DD dummy statement to get message ICE816I.

ICE192I

INVALID RETURN CODE FROM EXIT Enn WAS ACCEPTED

Explanation:

User exit Enn (E15 or E35) inappropriately passed DFSORT a return code of 0, 4, 12 or 20. Because EXITCK=WEAK was in effect, the invalid return code was accepted and interpreted as a valid return code. See z/OS DFSORT Application Programming Guide for an explanation of how DFSORT interprets E15 and E35 return codes when EXITCK=WEAK is in effect.

This message is issued once for E15 if it passes one or more inappropriate return codes to DFSORT or once for E35 if it passes one or more inappropriate return codes to DFSORT.

System action:

Processing continues.

Programmer response:

None.

ICE193I

ICEAMx INVOCATION ENVIRONMENT IN EFFECT – ICEyyy ENVIRONMENT SELECTED

Explanation:

ICEAMx indicates the invocation installation environment in effect for this run as follows:

  • ICEAM1 – batch JCL directly invoked environment
  • ICEAM2 – batch program invoked environment
  • ICEAM3 – TSO directly invoked environment
  • ICEAM4 – TSO program invoked environment

ICEyyy indicates the time-of-day installation environment (ICETDx) or invocation installation environment (ICEAMx) selected for this run. The set of installation defaults for the selected installation environment are used for the run.

An ICETDx installation environment can be selected only if:

  • It is specified by the ENABLE parameter of the ICEAMx installation environment in effect for the run-time environment, and
  • It specifies a day and time range that includes the day and time of the run (as listed in DFSORT’s ICE000I message)

If an ICETDx installation environment is not selected, the ICEAMx installation environment in effect for the run-time environment is selected.

Note:

You can use ICETOOL’s DEFAULTS operator to list merged PARMLIB/ICEMAC defaults in effect for each installation environment.

System action:

None.

Programmer response:

None.

ICE195A

OVERFLOW DURING SUMMATION – RC=16

Explanation:

Critical. OVFLO=RC16 was in effect and a pair of summary fields overflowed.

System action:

The program terminates.

Programmer response:

Redesign the records so that summary fields do not overflow, or if possible, use INREC to increase the size of the summary fields (see z/OS DFSORT Application Programming Guide). Alternatively, specify the OVFLO=RC0 or OVFLO=RC4 run-time option to override OVFLO=RC16 so summary overflow will be allowed for this application.

ICE196A

SORTOUT LRECL OF x IS DIFFERENT FROM SORTIN(NN) LRECL OF y – RC=16

Explanation:

Critical. One of the following errors occurred:

  • PAD=RC16 was in effect and the SORTOUT LRECL (x) was larger than the SORTIN/SORTINnn LRECL (y)
  • TRUNC=RC16 was in effect and the SORTOUT LRECL (x) was smaller than the SORTIN/SORTINnn LRECL (y).

System action:

The program terminates.

Programmer response:

Change the LRECL of SORTOUT or SORTIN/SORTINnn so that the LRECLs are equal. Alternatively, specify the PAD=RC0, PAD=RC4, TRUNC=RC0, or TRUNC=RC4 run-time option to override PAD=RC16 or TRUNC=RC16.

ICE197I

ONE OR MORE INCOMPLETE SPANNED RECORDS DETECTED AND ELIMINATED – RC=n

Explanation:

The application was successfully processed, but one or more incomplete spanned records was detected. DFSORT set a return code or 0 or 4, as indicated by n, according to whether SPANINC=RC0 or SPANINC=RC4 was in effect.

System action:

Processing continues and DFSORT passes back a return code of n unless it sets a higher return code for some other reason. Incomplete spanned records are eliminated and valid records are recovered.

Programmer response:

If appropriate, specify the SPANINC=RC0, SPANINC=RC4, or SPANINC=RC16 run-time option to provide a different return code for this situation.

ICE198I

DEBUG EQUCOUNT CANNOT BE USED WITHOUT WORK DATA SET

Explanation:

DEBUG EQUCOUNT was not used for this variable-length-record Blockset sort because no work data set was supplied.

System action:

Processing continues. DEBUG EQUCOUNT is not used.

Programmer response:

To use EQUCOUNT for this application, at least one work data set must be supplied.

ICE199I

|MEMORY OBJECT STORAGE USED AS MAIN STORAGE |= nM BYTES

Explanation:

|n is the number of megabytes of memory object |storage DFSORT used as main storage during this sort. If n is |zero, DFSORT did not use memory object storage as main storage during |this sort.

System action:

None.

Programmer response:

None.

ICE200I

IDENTIFIER FROM CALLING PROGRAM IS cccc

Explanation:

cccc is the identifier passed by the calling program for this invocation of DFSORT.

System action:

None.

Programmer response:

If appropriate, use cccc to relate this set of DFSORT messages to the call to DFSORT that passed this identifier.

ICE201I

RECORD TYPE IS x – DATA STARTS IN POSITION y

Explanation:

Indicates whether DFSORT processes the input records as fixed-length (without an RDW) or variable-length (with an RDW).

  • For fixed-length record processing, x is F and y is 1. Because the input records are processed without an RDW, the data starts in position 1. Positions in your control statements should be specified accordingly.
  • For variable-length record processing, x is V and y is 5. Because the input records are processed with an RDW in positions 1-4, the data starts in position 5. Positions in your control statements should be specified accordingly.

System action:

None.

Programmer response:

None, unless you are using VSAM input, or supplying all input with an E15 or E32 exit, and the selected record type is not what you want DFSORT to use. In that case, specify RECORD TYPE=F or RECORD TYPE=V as appropriate.

ICE202I

SYSUT2 LRECL OF x IS DIFFERENT FROM SYSUT1 LRECL OF y – RC=n

Explanation:

The ICEGENER application was successfully processed, but the SYSUT2 LRECL (x) and SYSUT1 LRECL (y) were not equal. ICEGENER set a return code of 0 or 4 as indicated by n. ICEGENER only set a return code of 4 if:

  • Installation option GNPAD=RC4 was specified and x was larger than y (LRECL padding), or
  • Installation option GNTRUNC=RC4 was specified and x was smaller than y (LRECL truncation).

System action:

Processing continues and ICEGENER passes back a return code of n unless it sets a higher return code for some other reason.

Programmer response:

If appropriate, change the LRECL of SYSUT1 or SYSUT2 so that the LRECLs are equal.

ICE203I

ONE OR MORE RECORDS HAD SHORT SUM FIELDS

Explanation:

The application was successfully processed, but one or more records had short SUM summary fields, that is, a summary field extended beyond the end of the variable-length record.

System action:

Records with short summary fields are excluded from summation, that is, if either one of a pair of records being summed has a short SUM field, the records are left unsummed and neither record is deleted.

Programmer response:

If records with short summary fields have equal control fields and summation of these records is required, redesign the records to eliminate short summary fields.

ICE204A

INCOMPLETE SPANNED RECORD DETECTED ON ddname – RC=16

Explanation:

Critical. SPANINC=RC16 was in effect and a spanned record in the indicated data set was incomplete.

System action:

The program terminates.

Programmer response:

Delete all incomplete spanned records from the indicated data set. Alternatively, specify the SPANINC=RC0 or SPANINC=RC4 run-time option to override SPANINC=RC16; DFSORT can then eliminate incomplete spanned records and recover valid records for this application.

ICE205A

CONTROL WAS NOT PASSED TO ICETEXIT

Explanation:

Critical. Control was not passed to ICETEXIT because an error occurred while collecting statistical information for the termination installation exit (ICETEXIT).

System action:

The program terminates.

Programmer response:

Notify your system programmer of the problem.

ICE206A

NO RECORDS FOR THE SORTOUT DATA SET – RC=16

Explanation:

Critical. NULLOUT=RC16 was in effect, but there were no records for the SORTOUT data set, as indicated by an OUT count of 0 in message ICE054I.

System action:

The program terminates.

Programmer response:

Change the application to produce records for the SORTOUT data set. Alternatively, specify the NULLOUT=RC0 or NULLOUT=RC4 run-time option to override NULLOUT=RC16.

ICE209A

NO DATA RECORDS FOR AN OUTFIL DATA SET – RC=16

Explanation:

Critical. NULLOFL=RC16 was in effect for one or more OUTFIL data sets for which there were no data records, as indicated by a DATA count of 0 in message ICE227I for those OUTFIL data sets.

System action:

The program terminates.

Programmer response:

Change the application to produce records for the relevant OUTFIL data sets (which you can identify by a DATA count of 0 in message ICE227I). Alternatively, specify the NULLOFL=RC0 or NULLOFL=RC4 run-time option on the relevant OUTFIL statements to override NULLOFL=RC16.

ICE210I

xxxx USED, LRECL = n, BLKSIZE = n, TYPE = t [(SDB)]

Explanation:

Gives attribute and access method information for the OUTFIL data set with the indicated ddname, as follows:

  • xxxx shows the access method used: EXCP, BSAM, or VSAM.
  • LRECL=n shows the logical record length.
  • BLKSIZE=n shows the block size (non-VSAM) or control interval size (VSAM).
  • TYPE=t shows the record format where t is one or more of the following format indicators:
    • F – fixed-length records
    • V – EBCDIC or ASCII variable-length records
    • B – blocked records
    • S – standard for fixed-length records or spanned for variable-length records
    • A – ANSI control characters
  • (SDB) shows that the system-determined optimum block size was used.

System action:

None.

Programmer response:

None.

ICE211I

OLD OUTFIL STATEMENT PROCESSING USED

Explanation:

This OUTFIL statement did not have any of the following operands: FNAMES, FILES, STARTREC, ENDREC, SAMPLE, INCLUDE, OMIT, SAVE, PARSE, OUTREC, BUILD, VTOF, CONVERT, VLFILL, OVERLAY, IFTHEN, FTOV, VLTRIM, REPEAT, SPLIT, SPLITBY, SPLIT1R, NULLOFL, LINES, HEADER1, TRAILER1, HEADER2, TRAILER2, SECTIONS, NODETAIL, BLKCCH1, BLKCCH2, BLKCCT1 or REMOVECC. For compatibility, this OUTFIL statement was treated as an “old” OUTFIL statement and all of its operands were ignored.

System action:

Processing continues, but OUTFIL data sets are not associated with this OUTFIL statement. If the Blockset technique is not selected, control statement errors could result from continuation of this OUTFIL statement.

Programmer response:

None, unless this is not an old OUTFIL statement, in which case valid operands from the list above should be specified.

ICE212A

MATCH NOT FOUND FOR {*INREC|*OUTREC|ddname} IFTHEN n CHANGE FIELD: {POSITION p|PARSE x}

Explanation:

Critical. In the FIELDS, BUILD, OVERLAY, IFTHEN BUILD or IFTHEN OVERLAY operand of an INREC or OUTREC statement, or the OUTREC, BUILD, OVERLAY, IFTHEN BUILD or IFTHEN OVERLAY operand of an OUTFIL statement, a CHANGE parameter was specified without a NOMATCH parameter and a fixed field (p,m) value or parsed field (%x) value did not match any of the find constants.

POSITION p indicates that a fixed field (p,m) did not match any of the find constants. p is the starting position of the input field. PARSE x indicates that a parsed field (%x) did not match any of the find constants.

The specific cause of the error is identified as follows:

  • *INREC and n=0 indicates that a change field in the FIELDS, BUILD or OVERLAY operand of the INREC statement caused the error.
  • *OUTREC and n=0 indicates that a change field in the FIELDS, BUILD or OVERLAY operand of the OUTREC statement caused the error.
  • ddname and n=0 indicates that a change field in the OUTREC, BUILD or OVERLAY operand of an OUTFIL statement caused the error. ddname identifies the first data set in the associated OUTFIL group.
  • *INREC and n>0 indicates that a change field in an IFTHEN BUILD or IFTHEN OVERLAY operand of the INREC statement caused the error. n identifies the number of the associated IFTHEN clause (starting at 1 for the first IFTHEN clause in the INREC statement).
  • *OUTREC and n>0 indicates that a change field in an IFTHEN BUILD or IFTHEN OVERLAY operand of the OUTREC statement caused the error. n identifies the number of the associated IFTHEN clause (starting at 1 for the first IFTHEN clause in the OUTREC statement).
  • ddname and n>0 indicates that a change field in an IFTHEN BUILD or IFTHEN OVERLAY operand of an OUTFIL statement caused the error. ddname identifies the first data set in the associated OUTFIL group. n identifies the number of the associated IFTHEN clause (starting at 1 for the first IFTHEN clause in the OUTFIL statement).

System action:

The program terminates when the first change field is encountered for which a match is not found.

Programmer response:

Correct the lookup table specified with the CHANGE parameter, or use the NOMATCH parameter to specify a constant, input field, or parsed field to be used as the output field if a match is not found. The use of a constant such as NOMATCH=(C’**’) can be helpful in identifying all fixed field values or parsed field values for which a match is not found.

ICE213A

INVALID OUTFIL STATEMENT OPERAND

Explanation:

Critical. An OUTFIL control statement contained an invalid keyword operand.

System action:

The program terminates.

Programmer response:

Make sure that the OUTFIL control statement does not contain an invalid keyword operand.

ICE214A

DUPLICATE, CONFLICTING, OR MISSING OUTFIL STATEMENT OPERANDS

Explanation:

Critical. One of the following errors was found in an OUTFIL statement:

  • An operand, other than IFTHEN, was specified twice.

    Example:

    OUTFIL STARTREC=5,STARTREC=10

  • INCLUDE and OMIT, INCLUDE and SAVE, or OMIT and SAVE were specified.

    Example:

    OUTFIL INCLUDE=ALL,SAVE

  • VTOF and CONVERT were specified.

    Example:

    OUTFIL VTOF,CONVERT

  • FTOV and VTOF, FTOV and CONVERT, or FTOV and VLFILL were specified.

    Example:

    OUTFIL FTOV,VLFILL=C’*’

  • PARSE, OUTREC, BUILD, OVERLAY or FINDREP was specified with IFTHEN or IFOUTLEN.

    Example:

    OUTFIL FINDREP=(IN=C’ONE’,OUT=C’TWO’),

    IFTHEN=(WHEN=INIT,OVERLAY=(25:C’YES’))

  • OUTREC and BUILD, OUTREC and OVERLAY, OUTREC and FINDREP, BUILD and OVERLAY, BUILD and FINDREP, or OVERLAY and FINDREP were specified.

    Example:

    OUTFIL BUILD=(1,20),OVERLAY=(10:C’A’)

  • For an IFTHEN clause, WHEN was not specified.

    Example:

    OUTFIL IFTHEN=(OVERLAY=(10:C’A’))

  • For an IFTHEN clause, WHEN=INIT, WHEN=(logexp), or WHEN=NONE was specified without PARSE, BUILD, OVERLAY, or FINDREP.

    Example:

    OUTFIL IFTHEN=(WHEN=(5,1,CH,EQ,C’1′),HIT=NEXT)

  • For an IFTHEN clause, WHEN=GROUP was specified without BEGIN, END or RECORDS, or without PUSH

    Example:

    OUTFIL IFTHEN=(WHEN=GROUP,

    BEGIN=(9,2,CH,EQ,C’NO’))

  • For an IFTHEN clause, WHEN=(logexp), WHEN=ANY, or WHEN=NONE was specified with PARSE, but without BUILD, OVERLAY, or FINDREP.

    Example:

    OUTFIL IFTHEN=(WHEN=NONE,

    PARSE=(%01=(FIXLEN=5,ENDBEFR=BLANKS)))

  • For an IFTHEN clause, WHEN=INIT, WHEN=(logexp), WHEN=ANY, or WHEN=NONE was specified with BEGIN, END, RECORDS or PUSH.

    Example:

    OUTFIL IFTHEN=(WHEN=INIT,PUSH=(9:5,8))

  • For an IFTHEN clause, WHEN=GROUP was specified with PARSE, BUILD, OVERLAY or FINDREP.

    Example:

    OUTFIL IFTHEN=(WHEN=GROUP,BUILD=(9:5,8))

  • For an IFTHEN clause, WHEN=INIT and BUILD with / were specified

    Example:

    OUTFIL IFTHEN=(WHEN=INIT,BUILD=(1,25,/,26,25))

  • For an IFTHEN clause, BUILD with / and HIT=NEXT were specified.

    Example:

    OUTFIL IFTHEN=(WHEN=(21,1,CH,EQ,C’A’),

    BUILD=(1,25,/,26,25),HIT=NEXT)

  • An IFTHEN clause with WHEN=INIT was preceded by an IFTHEN clause with WHEN=(logexp), WHEN=ANY or WHEN=NONE.

    Example:

    OUTFIL IFTHEN=(WHEN=(5,2,CH,EQ,C’AA’),

    OVERLAY=(10:C’A’)),

    IFTHEN=(WHEN=INIT,BUILD=(1,80))

  • An IFTHEN clause with WHEN=GROUP was preceded by an IFTHEN clause with WHEN=(logexp), WHEN=ANY or WHEN=NONE.

    Example:

    OUTFIL IFTHEN=(WHEN=(5,2,CH,EQ,C’AA’),

    OVERLAY=(10:C’A’)),

    IFTHEN=(WHEN=GROUP,RECORDS=3,

    PUSH=(8:SEQ=2))

  • An IFTHEN clause with WHEN=NONE was followed by an IFTHEN clause with WHEN=INIT, WHEN=WHEN=(logexp), or WHEN=ANY.

    Example:

    OUTFIL IFTHEN=(WHEN=NONE,OVERLAY=(10:C’A’)),

    IFTHEN=(WHEN=ANY,BUILD=(1,80))

  • The first IFTHEN clause with WHEN=ANY was not preceded by an IFTHEN clause with WHEN=(logexp).

    Example:

    OUTFIL IFTHEN=(WHEN=INIT,OVERLAY=(10:C’A’)),

    IFTHEN=(WHEN=ANY,BUILD=(1,80))

  • An IFTHEN clause with WHEN=ANY and without HIT=NEXT was followed by an IFTHEN clause with WHEN=ANY.

    Example:

    OUTFIL IFTHEN=(WHEN=(5,1,CH,EQ,C’1′),

    OVERLAY=(10:C’A’),HIT=NEXT),

    IFTHEN=(WHEN=(5,1,CH,EQ,C’2′),

    OVERLAY=(10:C’B’),HIT=NEXT),

    IFTHEN=(WHEN=ANY,OVERLAY=(28:C’ABC’)),

    IFTHEN=(WHEN=ANY,BUILD=(1,80))

System action:

The program terminates.

Programmer response:

Check the OUTFIL control statement for the errors indicated in the explanation and correct the errors.

ICE215A

SPECIFIED FEATURE IS ONLY SUPPORTED BY OUTFIL STATEMENT

Explanation:

Critical. One of the following, which is supported only by the OUTFIL control statement, was specified on an INREC or OUTREC control statement:

  • A / in a FIELDS, BUILD, or IFTHEN BUILD operand
  • A VTOF or CONVERT operand
  • An FTOV operand
  • A VLFILL=byte operand
  • A VLTRIM=byte operand

System action:

The program terminates.

Programmer response:

If a / was specified, use a / in a BUILD or IFTHEN BUILD operand in an OUTFIL statement instead. If a VTOF, CONVERT, or VLFILL=byte operand was specified, use the same operand and BUILD in an OUTFIL statement instead. For example:

OUTFIL BUILD=(1,60),FTOV

If an FTOV or VLTRIM=byte operand was specified, use the same operand and BUILD or IFTHEN BUILD in an OUTFIL statement instead. For example:

OUTFIL VLTRIM=X’40’,

IFTHEN=(WHEN=(5,1,CH,EQ,C’A’),BUILD=(1,40,45))

ICE216A

TOTAL LENGTH OF CONTROL FIELDS AND SUM FIELDS IS TOO LONG

Explanation:

Critical. The total length of the SORT or MERGE control fields and SUM summary fields is too long for DFSORT to process, or the complexity of the application caused dynamic areas to exceed the storage allowed for them. Note that locale processing can significantly decrease the total length of the SORT or MERGE fields DFSORT can process.

System action:

The program terminates.

Programmer response:

Remove one or more control fields or summary fields, or make them shorter.

ICE217A

n BYTE VARIABLE RECORD IS LONGER THAN m BYTE MAXIMUM FOR {ddname|E15|E32|E35}

Explanation:

Critical. A variable-length record was larger than the maximum length specified or defaulted. The values shown in the message are as follows:

  • n is the length of the variable-length record
  • m is the maximum length specified or defaulted
  • ddname indicates that the variable-length record, read from a SORTIN (sort or copy) or SORTINnn (merge) data set or to be written to the SORTOUT or OUTFIL data set, had a length greater than the LRECL specified or defaulted. For |SORTINnn, SORTIN, SORTOUT, or OUTFIL, the actual ddname is shown.
  • E15 indicates that an E15 exit passed a variable-length record with a length greater than the L2 value specified or defaulted
  • E32 indicates that an E32 exit passed a variable-length record with a length greater than the L1 value specified or defaulted
  • E35 indicates that an E35 exit passed a variable-length record with a length greater than the L3 value specified or defaulted

System action:

The program terminates.

Programmer response:

If variable-length records are longer than the LRECL of the SORTOUT or OUTFIL data set and you want to truncate long records to the LRECL, use the VLLONG option. Keep in mind that the use of VLLONG causes data at the end of long records to be lost.

If variable-length output records are longer than 32757 bytes for the SORTOUT or OUTFIL data set, you can specify an LRECL up to 32767 bytes if you also specify RECFM=VBS.

If variable-length records are longer than the LRECL of the OUTFIL data set, you may be able to use the VLTRIM=byte parameter of the OUTFIL statement to shorten them. For example, VLTRIM=C’ ‘ will remove trailing blanks from the records.

If variable-length output records are longer than the LRECL of the SORTIN data set, the first data set in the concatenation does not have the largest LRECL as required. Either specify the data set with the largest LRECL first in the SORTIN concatenation, or specify LRECL=n as a parameter on the SORTIN DD statement where n is equal to or greater than the length of the longest record.

If variable-length records from an E15, E32, or E35 exit are longer than the corresponding Ln value, correct the RDW or Ln value, as appropriate.

You can use the ICETOOL STATS operator with ON(VLEN) to show the length of the longest variable-length record. You can use the ICETOOL DISPLAY operator with ON(VLEN) to show the length of each variable-length record.

ICE218A

n BYTE VARIABLE RECORD IS SHORTER THAN m BYTE MINIMUM FOR [ddname] FIELDS

Explanation:

Critical. A variable-length record was shorter than 4 bytes, or was too short to contain all specified fields. The values shown in the message are as follows:

  • n is the length of the variable-length record
  • m is 4 or the minimum length needed for all fields specified
  • if ddname is blank, the short record was detected during non-OUTFIL processing. Otherwise, the first data set in the OUTFIL group for which the short record was detected is indicated by ddname.

System action:

The program terminates.

Programmer response:

If a variable-length record was too short to contain all INREC, OUTREC, or OUTFIL fields, use an INREC or OUTREC statement with operands OVERLAY or IFTHEN as appropriate, or an OUTFIL statement with operands OVERLAY, IFTHEN, or BUILD and VLFILL=C ‘x’ or VLFILL=X ‘yy’ as appropriate, to prevent DFSORT from terminating.

If the variable-length record was too short to contain all SORT, MERGE, or SUM fields, use the VLSHRT option to prevent DFSORT from terminating.

If a variable-length record was too short to contain all INCLUDE or OMIT fields, use the VLSCMP or VLSHRT option to prevent DFSORT from terminating.

|This message can be issued in the JOINKEYS F1 or |F2 subtask for an INCLUDE or OMIT statement specified in JNFnCNTL |or for an INCLUDE or OMIT operand specified on a JOINKEYS statement. | An INCLUDE or OMIT statement specified in JNFnCNTL will be displayed |in the subtask. An INCLUDE or OMIT operand specified on a JOINKEYS |statement will be displayed in the main task. If you specify an INCLUDE |or OMIT statement in JNFnCNTL, you can also specify VLSCMP in JNFnCNTL |if appropriate. If you specify an INCLUDE or OMIT operand on the JOINKEYS |statement, you can specify VLSCMP in DFSPARM if appropriate.

See the Programmer Response for message ICE015A for additional information.

ICE219I

DUPLICATE DDNAME ddname IGNORED

Explanation:

The indicated ddname was specified previously in an OUTFIL statement in this source. The OUTFIL specifications are not used for this ddname, although they may be used for other ddnames in this OUTFIL statement that have not been previously specified in this source.

This message is only printed for the first 128 duplicate ddnames found.

System action:

Processing continues. The first OUTFIL ddname encountered in a source is used (unless overridden by the use of the same ddname in an OUTFIL statement in a higher source).

Programmer response:

No action is necessary if the OUTFIL processing specified for the duplicate ddname is not needed. Otherwise, correct the ddname conflicts.

ICE220A

ddname COULD NOT BE USED – REASON CODE IS rsn

Explanation:

Critical. The OUTFIL data set associated with the indicated ddname could not be processed. rsn is the reason code associated with the error. The reason code helps you determine the specific cause of the error. Reason code values (rsn) are as follows:

1

An attempt to OPEN the OUTFIL tape data set to retrieve its attributes failed.

2

The OUTFIL data set resided on an unsupported device.

3

An attempt to read the DSCB for the OUTFIL data set failed.

4

The OUTFIL data set was BDAM.

System action:

The program terminates.

Programmer response:

Correct the situation indicated by the reason code (rsn).

ICE221A

INVALID FIELD OR CONSTANT IN {*INCLUDE|*OMIT|*INREC| *OUTREC|ddname} IFTHEN n CONDITION m

Explanation:

Critical. An error was detected in a COND, INCLUDE, OMIT, or IFTHEN WHEN, BEGIN or END operand. The specific cause of the error is identified as follows:

  • *INCLUDE indicates that the COND operand of the INCLUDE statement, |or an INCLUDE operand of a JOINKEYS statement, caused the error. n is 0.
  • *OMIT indicates that the COND operand of the OMIT statement, |or an OMIT operand of a JOINKEYS statement, caused the error. n is 0.
  • ddname and n=0 indicates that the INCLUDE or OMIT operand of an OUTFIL statement caused the error. ddname identifies the first data set in the associated OUTFIL group.
  • *INREC indicates that an IFTHEN WHEN, BEGIN or END operand of the INREC statement caused the error. n identifies the number of the associated IFTHEN clause (starting at 1 for the first IFTHEN clause in the INREC statement).
  • *OUTREC indicates that an IFTHEN WHEN, BEGIN or END operand of the OUTREC statement caused the error. n identifies the number of the associated IFTHEN clause (starting at 1 for the first IFTHEN clause in the OUTREC statement).
  • ddname and n>0 indicates that an IFTHEN WHEN, BEGIN or END operand of an OUTFIL statement caused the error. ddname identifies the first data set in the associated OUTFIL group. n identifies the number of the associated IFTHEN clause (starting at 1 for the first IFTHEN clause in the OUTFIL statement).

One of the following errors was detected:

  • the length for a field with a format other than SS was greater than 256
  • the length for a PD field not used with NUM was 256
  • the length for a PD0 field was less than 2 or greater than 8
  • the length for a CSF or FS field not used with NUM was greater than 32
  • the length for a UFF or SFF field was greater than 44
  • the length for a CSL, CST, ASL, or AST field was 1
  • the decimal constant for an FI field was greater than +9223372036854775807 or less than -9223372036854775808
  • the decimal constant for a BI field was greater than 18446744073709551615 or less than +0
  • the number of digits (including leading zeros) in the decimal constant for an FI or BI field was greater than 31
  • the length for a Y2 field was not 2 for Y2C, Y2Z, Y2P or Y2S, or 1 for Y2D or Y2B, or 3–6 for Y2T or Y2W, or 2–3 for Y2U or Y2X, or 3–4 for Y2V or Y2Y
  • a Y2 field was compared to another Y2 field with a different number of non-year digits
  • a Y2 field was compared to a Y constant with a different number of non-year digits
  • a Y2 field other than Y2S, Y2T or Y2W was compared to Y’LOW’, Y’BLANKS’ or Y’HIGH’
  • a Y2 field was compared to a constant that was not a Y constant.

m indicates the number of the relational condition in which the error was found (starting at 1 for the first relational condition). For example, in

INCLUDE COND=(5,2,CH,EQ,8,2,CH,OR,

11,257,BI,EQ,301,257,BI)

the second relational condition (after the OR) has the error described in the first bullet above, so m is 2.

System action:

The program terminates.

Programmer response:

Correct the field length or constant in error in relational condition m.

ICE222A

n BYTE FIXED RECORD LENGTH IS NOT EQUAL TO m BYTE LRECL FOR ddname

Explanation:

Critical. The LRECL specified or retrieved for the fixed-length OUTFIL data set was not equal to the computed length of the output records for that data set. You cannot use the LRECL value to pad the OUTFIL records or to truncate the records produced by BUILD, OUTREC, OVERLAY, FINDREP, IFTHEN BUILD, IFTHEN OVERLAY, IFTHEN FINDREP or IFTHEN PUSH operand processing. The values shown in the message are as follows:

  • n is the computed length of the output records for the OUTFIL group
  • m is the specified or retrieved LRECL of the OUTFIL data set
  • ddname indicates the OUTFIL data set for which padding or truncation was required

System action:

The program terminates.

Programmer response:

Take one of these actions as appropriate:

  • Do not set the LRECL explicitly. Instead, let DFSORT set the LRECL to the computed record length.
  • If you are using IFTHEN operands, specify IFOUTLEN=m. (Remember to allow an extra byte for OUTFIL report data sets for the ANSI carriage control character unless you specify the REMOVECC operand.)
  • If you are not using IFTHEN operands, ensure that the computed length for the BUILD, OVERLAY, or FINDREP operand, or the specified MAXLEN length for the FINDREP operand, is equal to m. (Remember to allow an extra byte for OUTFIL report data sets for the ANSI carriage control character unless you specify the REMOVECC operand.)

ICE223A

REPORT FIELD ERROR

Explanation:

Critical. The LINES, HEADER1, TRAILER1, HEADER2, TRAILER2, or SECTIONS parameter of an OUTFIL statement contained an invalid column, report element, position, length, format, keyword, pattern, sign, or constant. Some common errors are :

  • A 0 value was used.
  • A null value was used where it was not permitted.
  • A null string, pattern, or sign was used.
  • A column was greater than 32752, preceded / or n/ (new line), or was followed by another column.
  • A column overlapped the previous output field in the report record (a missing new line (/ or n/) to end the current report record and start the next one can cause this error).
  • A position plus length was greater than 32753.
  • DATE=(abcd) or DATENS(abc) was specified with a, b or c not M, D, Y or 4, with M, D, Y or 4 specified more than once, or with Y and 4 both specified.
  • YDDD=(abc) or YDDDNS=(ab) was specified with a or b not D, Y or 4, with D, Y or 4 specified more than once, or with Y and 4 both specified.
  • TIME=(abc) or TIMENS=(ab) was specified with ab not 12 or 24.
  • The length for an input field or section break field was greater than 256 bytes.
  • A repetition factor was greater than 4095 for a blank, character string, or hexadecimal string report element, or greater than 255 for a blank lines report element or a section skip line count.
  • A character or hexadecimal constant was longer than 256 bytes.
  • An invalid digit or an odd number of digits was specified for a hexadecimal string.
  • The length for a statistics field was greater than 8 for BI or FI, 16 for PD, 31 for ZD, 32 for CSF/FS, or 44 for UFF or SFF.
  • The length for a statistics field was not 4 or 8 for FL.
  • More than 31 digits or 44 characters were specified in an edit pattern.
  • SIGNz (where z is not S) was specified with Mn or without EDIT or EDxy.
  • x, y, or z in EDxy or SIGNz were the same character.
  • The value for LENGTH was greater than 44.
  • The value for LINES was greater than 255.
  • A section break field was not followed by SKIP, HEADER3, or TRAILER3.
  • A statistics field was specified in HEADER1, HEADER2, or HEADER3.
  • HEADER3, TRAILER3, SKIP, or PAGEHEAD was specified more than once after a section break field.

System action:

The program terminates.

Programmer response:

Correct the invalid value.

ICE224A

ddname CANNOT BE USED FOR A REPORT – RECFM WITHOUT ‘A’ SPECIFIED, OR VSAM DATA SET

Explanation:

Critical. The OUTFIL report specified for the OUTFIL data set associated with ddname cannot be produced because either:

  • the OUTFIL data set is VSAM, or
  • the record format specified or retrieved for the OUTFIL data set does not contain ‘A’ (ANSI carriage control characters).

System action:

The program terminates.

Programmer response:

If the OUTFIL data set is VSAM, it cannot be used for a report. If the OUTFIL data set is non-VSAM, take one of the following actions:

  • Let DFSORT set the RECFM appropriately.
  • Specify a RECFM that includes ‘A’.
  • Specify the REMOVECC parameter on the OUTFIL statement so ‘A’ is not needed in the RECFM.

ICE225A

ddname : LRECL = n IS INVALID

Explanation:

Critical. The specified or computed LRECL (n), for the OUTFIL data set associated with ddname, is invalid for one of the following reasons:

  • LRECL=X was specified (n will be 32768)
  • n is less than the minimum allowed: 1 (not a report) or 2 (report) for a fixed-length record data set or 5 (not a report) or 6 (report) for a variable-length record data set
  • n is greater than the maximum allowed: 32760 for a fixed-length record data set, 32756 for a variable-length record data set, 32767 for a spanned record data set or 32752 for a VSAM variable-length record data set

System action:

The program terminates.

Programmer response:

If LRECL=X was specified, specify the actual maximum LRECL instead. If the LRECL is less than the minimum allowed, increase it. If the LRECL is greater than the maximum allowed, decrease it.

ICE226A

BLKSIZE = n IS INVALID (LRECL = m)

Explanation:

Critical. The specified or computed block size (n), for the OUTFIL data set associated with ddname, is invalid for one of the following reasons (m is the associated LRECL):

  • n is less than the minimum allowed: 1 (not a report) or 2 (report) for a fixed-length record data set or 9 (not a report) or 10 (report) for a variable-length record data set
  • n is less than m for a fixed-length record data set
  • n is not a multiple of m for a fixed-length record data set
  • n is not equal to m for an unblocked fixed-length record data set
  • n is less than m + 4 for a variable-length record data set
  • n is greater than the track capacity of the device on which the data set resides

System action:

The program terminates.

Programmer response:

Change the block size to a valid value.

ICE227I

ddname : DELETED = n, REPORT = n, DATA = n

Explanation:

For the OUTFIL data set associated with ddname, lists the number of OUTFIL input records deleted (that is, not written to this data set) and the number of report and data records written.

System action:

None.

Programmer response:

None.

ICE228I

ddname : TOTAL IN = n, TOTAL OUT = n

Explanation:

For the OUTFIL data set associated with ddname, lists the number of OUTFIL input records and the number of OUTFIL output records (report plus data) written.

System action:

None.

Programmer response:

None.

ICE229A

ddname : LINES = n IN EFFECT, BUT m LINES REQUIRED

Explanation:

Critical. For the OUTFIL group whose first data set is associated with ddname, the value specified or defaulted for LINES (n) is too low to contain the number of lines (m) required for the maximum of:

  • The HEADER1 lines
  • The TRAILER1 lines
  • The sum of all lines for HEADER2, TRAILER2, HEADER3s, and TRAILER3s, and the data lines and blank lines produced from an input record.

System action:

The program terminates.

Programmer response:

Set LINES=n to a value equal to or greater than m, or reduce the number of lines required.

ICE230A

n BYTE HEADER/TRAILER RECORD LENGTH EXCEEDS m BYTE LRECL FOR ddname

Explanation:

Critical. The specified, retrieved, or computed LRECL for the OUTFIL data set was less than the computed length for the report records for that data set. The values shown in the message are as follows:

  • n is the computed length of the report records for the OUTFIL group
  • m is the specified, retrieved, or computed LRECL of the OUTFIL data set
  • ddname indicated the OUTFIL data set for the report

System action:

The program terminates.

Programmer response:

Use the BUILD, OVERLAY, IFTHEN, or IFOUTLEN operand to force a length for the data records that is longer than any report record, and either let DFSORT compute and set the LRECL, or ensure that the computed LRECL is equal to the existing or specified LRECL. (Remember to allow an extra byte in the LRECL for the ANSI carriage control character, unless you specify the REMOVECC parameter.)

For example, if your data records are 40 bytes, but your longest report record is 60 bytes, you could use an OVERLAY parameter such as:

OUTFIL HEADER1=(51:DATE=(4MD/)),OVERLAY=(80:X)

DFSORT will then set the LRECL to 81 (1 byte for the ANSI carriage control character plus 80 bytes for the length of the data records), and pad the data records with blanks on the right.

ICE231I

STORAGE USED FOR OUTFIL : BELOW 16M = x, ABOVE 16M = y

Explanation:

Gives information related to the main storage used exclusively for OUTFIL processing. x is the storage used below 16 MB virtual and y is the storage used above 16 MB virtual.

System action:

None.

Programmer response:

None.

ICE232A

ddname: SPLIT, SPLITBY, SPLIT1R OR REPEAT CANNOT BE USED FOR A REPORT

Explanation:

Critical. For the OUTFIL group whose first data set is associated with ddname, a SPLIT, SPLITBY, SPLIT1R, or REPEAT parameter was specified along with one or more report parameters (LINES, HEADER1, TRAILER1, HEADER2, TRAILER2, SECTIONS or NODETAIL). The records of a report cannot be repeated, or split among a group of OUTFIL data sets.

System action:

The program terminates.

Programmer response:

Remove either the SPLIT, SPLITBY, SPLIT1R, or REPEAT parameter or the report parameters.

ICE233A

OUTFIL STATEMENTS CANNOT BE PASSED TO OR FROM AN EFS PROGRAM

Explanation:

Critical. An OUTFIL statement was to be passed to an EFS program or an EFS program passed back an OUTFIL statement. DFSORT does not allow OUTFIL statements to be processed by an EFS program that requests them, and does not allow an EFS program to change other statements passed to it into OUTFIL statements.

System action:

The program terminates.

Programmer response:

Change the EFS program such that it does not request OUTFIL statements or change other statements it requests into OUTFIL statements.

ICE234A

STARTREC, ENDREC, SAMPLE OR REPEAT VALUES ARE INCONSISTENT

Explanation:

Critical. Specified values were inconsistent in one of the following ways:

  • The n value of ENDREC=n is less than the n value of STARTREC=n. Example: STARTREC=10,ENDREC=9

    The n value of ENDREC=n must be equal to or greater than the n value of STARTREC=n. Example: STARTREC=10,ENDREC=10 to process record 10, or STARTREC=10,ENDREC=20 to process records 10-20.

  • The n value of SAMPLE=n or SAMPLE=(n,m) is 1, which would result in processing every record instead of a sample of records. Example: SAMPLE=1.

    The n value of SAMPLE=n or SAMPLE=(n,m) must be equal to or greater than 2. Example: SAMPLE=2 to process records 1, 3, and so on, or SAMPLE=(10,2) to process records 1, 2, 11, 12, and so on.

  • The n value of REPEAT=n is 1, which would result in no repetitions. Example: REPEAT=1.

    The n value of REPEAT=n must be equal to or greater than 2. Example: REPEAT=5 to repeat each output record five times.

System action:

The program terminates.

Programmer response:

Specify consistent values for STARTREC, ENDREC, SAMPLE, and REPEAT.

ICE235I

OPTIONS: NULLOUT=a

Explanation:

|Issued in conjunction with messages ICE127I through |ICE133I and ICE236I to indicate the options in effect.

|
|

a |

‘RC0’, ‘RC4’, or ‘RC16’ |

|See ICE133I for more information.

|

ICE236I

OPTIONS: DYNAPCT=a|,MOWRK=b|

|

Explanation:

|

Issued in conjunction with messages ICE127I through ICE133I and |ICE235I to indicate the options in effect.

|
|

a |

A decimal value representing a percentage, or ‘OLD’ |
|

|b|
|

|‘Y’ for YES; ‘N’ for NO|
|
|

|

|See ICE133I for more information.|

ICE241A

{*INREC|*OUTREC|ddname} IFTHEN n COLUMN OVERLAPS RECORD DESCRIPTOR WORD

Explanation:

Critical. For variable-length record processing, the OVERLAY, IFTHEN OVERLAY, or IFTHEN PUSH operand of an INREC, OUTREC or OUTFIL statement specified an item that overlapped the record descriptor word (RDW). Only data bytes, which start at position 5 for variable-length records, can be overlaid. The specific cause of the error is identified as follows:

  • *INREC and n=0 indicates that the OVERLAY operand of the INREC statement caused the error.
  • *OUTREC and n=0 indicates that the OVERLAY operand of the OUTREC statement caused the error.
  • ddname and n=0 indicates that the OVERLAY operand of an OUTFIL statement caused the error. ddname identifies the first data set in the associated OUTFIL group
  • *INREC and n>0 indicates that an IFTHEN OVERLAY or IFTHEN PUSH operand of the INREC statement caused the error. n identifies the number of the associated IFTHEN clause (starting at 1 for the first IFTHEN clause in the INREC statement).
  • *OUTREC and n>0 indicates that an IFTHEN OVERLAY or IFTHEN PUSH operand of the OUTREC statement caused the error. n identifies the number of the associated IFTHEN clause (starting at 1 for the first IFTHEN clause in the OUTREC statement).
  • ddname and n>0 indicates that an IFTHEN OVERLAY or IFTHEN PUSH operand of an OUTFIL statement caused the error. ddname identifies the first data set in the associated OUTFIL group. n identifies the number of the associated IFTHEN clause (starting at 1 for the first IFTHEN clause in the OUTFIL statement).

The error is one of the following:

  • c: was not specified for the first OVERLAY, IFTHEN OVERLAY, or IFTHEN PUSH item so the default of 1: was used for that item. Example:

    OVERLAY=(C’ABC’)

  • c: was specified for an OVERLAY, IFTHEN OVERLAY, or IFTHEN PUSH item with a value for c which was less than 5. Example:

    PUSH=(3:SEQ=5)

System action:

The program terminates.

Programmer response:

Specify c: with a value of 5 or more for the first OVERLAY, IFTHEN OVERLAY, or IFTHEN PUSH item. Ensure that c is 5 or more for any other c: values you specify. Example:

OVERLAY=(8:C’ABC’,1,2,HEX,25:5C’*’)

ICE242A

Z/ARCHITECTURE MODE IS REQUIRED FOR THIS FUNCTION

Explanation:

Critical. The indicated function cannot be used because it requires z/Architecture mode, but you are running in ESA/390 mode. z/Architecture mode is required for the following functions:

  • FL (hexadecimal floating-point) conversion to integer with the INREC, OUTREC or OUTFIL statement.
  • FL (hexadecimal floating-point) conversion to integer with the DISPLAY operator.

System action:

The program terminates.

Programmer response:

A $ marks the point at which the error was detected. Remove the function or switch to z/Architecture mode.

ICE243A

PARSED FIELD DEFINITION ERROR

Explanation:

Critical. The PARSE operand of an INREC, OUTREC or OUTFIL statement contained an invalid or incorrect definition for a parsed field. One of the following errors was found:

  • More than 2 digits was specified for a parsed field definition (for example, %001 instead of %1 or %01). A parsed field must start with % and must have 1 digit, 2 digits or no digits.
  • FIXLEN was not specified for %nn or %n.
  • FIXLEN, ABSPOS, ADDPOS, SUBPOS or PAIR was specified more than once.
  • ABSPOS and ADDPOS, ABSPOS and SUBPOS, or ADDPOS and SUBPOS were specified.
  • FIXLEN, ABSPOS, ADDPOS or SUBPOS was specified with a value of 0 or a value greater than 32752.
  • A null string was used.
  • A character or hexadecimal constant was longer than 256 bytes.
  • An invalid digit or an odd number of digits was specified for a hexadecimal string.
  • An invalid keyword was specified.

System action:

The program terminates.

Programmer response:

Check the PARSE operand for the errors indicated in the explanation and correct the errors.

ICE244A

DUPLICATE PARSED FIELD DEFINITION

Explanation:

Critical. A %nn parsed field was defined previously (for example, %03 was defined twice), a %0n parsed field was defined previously as a %n parsed field (for example, both %3 and %03 were defined), or a %n parsed field was defined previously as a %0n parsed field (for example, both %03 and %3 were defined). Each %nn (including %n and %0n) parsed field must only be defined once in all PARSE operands of the INREC, OUTREC and OUTFIL statements.

System action:

The program terminates.

Programmer response:

A $ marks the duplicate parsed field. Use unique %nn parsed fields (%00-%99).

ICE245A

PARSED FIELD NOT DEFINED FOR USE IN THIS OVERLAY, BUILD, FIELDS OR OUTREC OPERAND

Explanation:

Critical. An OVERLAY, BUILD, FIELDS or OUTREC operand, or an IFTHEN OVERLAY or IFTHEN BUILD suboperand, of an INREC, OUTREC or OUTFIL statement specified a parsed field (%nn) that was not previously defined for use with that operand or suboperand. %nn parsed fields must be defined and used as follows:

  • %nn used in INREC OVERLAY/BUILD/FIELDS: The %nn parsed field must be defined in the INREC statement in a PARSE operand that precedes the OVERLAY, BUILD or FIELDS operand.
  • %nn used in OUTREC OVERLAY/BUILD/FIELDS: The %nn parsed field must be defined in the OUTREC statement in a PARSE operand that precedes the OVERLAY, BUILD or FIELDS operand.
  • %nn used in OUTFIL OVERLAY/BUILD/OUTREC: The %nn parsed field must be defined in the same OUTFIL statement in a PARSE operand that precedes the OVERLAY, BUILD or OUTREC operand.
  • %nn used in INREC IFTHEN OVERLAY/BUILD: The %nn parsed field must be defined in the INREC statement in an IFTHEN PARSE suboperand of a WHEN=INIT clause, or in an IFTHEN PARSE suboperand of the same clause, before the OVERLAY or BUILD suboperand.
  • %nn used in OUTREC IFTHEN OVERLAY/BUILD: The %nn parsed field must be defined in the OUTREC statement in an IFTHEN PARSE suboperand of a WHEN=INIT clause, or in an IFTHEN PARSE suboperand of the same clause, before the OVERLAY or BUILD suboperand.
  • %nn used in OUTFIL IFTHEN OVERLAY/BUILD: The %nn parsed field must be defined in the same OUTFIL statement in an IFTHEN PARSE suboperand of a WHEN=INIT clause, or in an IFTHEN PARSE suboperand of the same clause, before the OVERLAY or BUILD suboperand.

The following are some examples of using %nn parsed fields correctly:

* %00 defined in PARSE and used in BUILD.

INREC PARSE=(%00=(FIXLEN=IO,ENDBEFR=C’,’)),

BUILD=(%00)

* %01 defined in WHEN=INIT clause and used

* in WHEN=(logexp) clause.

* %02 defined in WHEN=(logexp) clause

* and used in that clause.

OUTREC IFTHEN=(WHEN=INIT,

PARSE=(%01=(ENDBEFR=C’,’,

FIXLEN=8))),

IFTHEN=(WHEN=(5,1,CH,EQ,C’A’),

PARSE=(%02=(STARTAFT=C'(‘,

FIXLEN=12)),

BUILD=(%01,%02))

* %03 defined and used for OUTFIL OUT1.

* %04 defined and used for OUTFIL OUT2.

OUTFIL FNAMES=0UT1,INCLUDE=(8,1,CH,EQ,C’A’),

PARSE=(%03=(FIXLEN=IO,ENDBEFR=C’,’)),

OVERLAY=(21:%03)

OUTFIL FNAMES=0UT2,SAVE,

PARSE=(%04=(FIXLEN=8,ENDBEFR=C’:’)),

OVERLAY=(31:%04)

The following are some examples of using %nn parsed fields incorrectly:

* %00 used in BUILD, but defined in PARSE

* after BUILD.

INREC BUILD=(%00),

PARSE=(%00=(FIXLEN=IO,ENDBEFR=C’,’))

* %02 used in WHEN=NONE clause but not defined

* in that clause or in a WHEN=INIT clause

OUTREC IFTHEN=(WHEN=(5,1,CH,EQ,C’A’),

PARSE=(%02=(STARTAFT=C'(‘,

FIXLEN=12)),

BUILD=(%02)),

IFTHEN=(WHEN=NONE,

BUILD=(1,20,%02))

* %03 used in OUTFIL for OUT2, but defined

* in OUTFIL for OUT1.

OUTFIL FNAMES=0UT1,INCLUDE=(8,1,CH,EQ,C’A’),

PARSE=(%03=(FIXLEN=IO,ENDBEFR=C’,’)),

OVERLAY=(21:%03)

OUTFIL FNAMES=0UT2,SAVE,

OVERLAY=(21:%03)

System action:

The program terminates.

Programmer response:

A $ marks the incorrectly used %nn parsed field. Define the %nn parsed field correctly.

ICE246A

SORT CAPACITY EXCEEDED – RECORD COUNT: n

Explanation:

Critical. Blockset was not selected, and DFSORT was not able to complete processing with the intermediate storage available (disk work data sets). For work data sets with secondary allocation allowed, DFSORT overrides system B37 abends and continues processing; this message is issued only when no more space is available on any allocated work data set.

Note:

DFSORT uses only the first volume of multi-volume work data sets.

The amount of intermediate storage required can vary depending on many factors including:

  • The amount of main storage available
  • The degree of randomness of the records to be sorted
  • The values specified (or defaulted) for options such as DYNALOC, DYNAUTO, DYNSPC, FILSZ/SIZE, AVGRLEN, or DYNALLOC
  • The amount of padding required for short records when VLSHRT is in effect.

System action:

The program terminates.

Programmer response:

Take one or more of the following actions:

  • If appropriate, increase the amount of main storage available to DFSORT using the options MAINSIZE/SIZE or the JCL option REGION. Increasing the amount of main storage available to DFSORT can help DFSORT use less intermediate storage. Avoid running a large sort in a small amount of main storage.
  • If dynamic allocation was used, ensure that the values for the options DYNALOC, DYNAUTO, DYNSPC, DYNALLOC, FILSZ/SIZE, and AVGRLEN are appropriate. If necessary, specify these options or change their values.
  • If VLSHRT was in effect and the total size of all control fields was significantly larger than the average LRECL for the data set, you may be able to reduce the amount of work space required by reducing the total size of the control fields.
  • If JCL work data sets were used, increase the amount of work space available to DFSORT.

ICE2471

INTERMEDIATE MERGE ENTERED – PERFORMANCE MAY BE DEGRADED

Explanation:

Because the amount of virtual storage available to DFSORT was a small fraction of the amount of data to be sorted, DFSORT required additional intermediate merge passes over the data to perform the sort. Such intermediate merge passes often result in significant performance degradation with a consequent increase in intermediate storage requirements.

System action:

Processing continues using intermediate merge passes as required.

Programmer response:

Increase the amount of virtual storage available for the sort. For information and guidelines for optimizing virtual storage, refer to “Run-Time Considerations” z/OS DFSORT Tuning Guide.

|

ICE248I

DFSORT ATTEMPTED TO ALLOCATE xMB OF DISK WORK SPACE |ON y WORK DATA SETS

|

Explanation:

|

Provides information on the total disk work space DFSORT attempted |to allocate dynamically when it was unable to allocate all of the |work space it requested. x indicates the total megabytes |of disk work space DFSORT attempted to allocate. y indicates |the total number of work data sets used for the allocations. x/y is |the amount of free space that must be available on at least y volumes |for DFSORT to allocate all of the work space it requested.

|

System action:

|

None.

|

Programmer response:

|

Verify that there are enough candidate volumes with the required |free space to satisfy the work data set space requests. If necessary, |increase the number of work data sets used for dynamic allocation |to reduce the required disk space for each.

|

ICE249I

DFSORT SUCCESSFULLY ALLOCATED xMB OF DISK WORK SPACE |ON y WORK DATA SETS

|

Explanation:

|

Provides information on the total disk work space DFSORT successfully |allocated dynamically when it was unable to allocate all of the work |space it requested. x indicates the total megabytes of disk |work space DFSORT successfully allocated. y indicates the |total number of work data sets used for the allocations.

|

System action:

|

None.

|

Programmer response:

|

Verify that there are enough candidate volumes with the required |free space to satisfy the work data set space requests. If necessary, |increase the number of work data sets used for dynamic allocation |to reduce the required disk space for each.

ICE250I

VISIT http://www.ibm.com/storage/dfsort FOR DFSORT PAPERS, EXAMPLES AND MORE

Explanation:

The DFSORT website at http://www.ibm.com/storage/dfsort is an important source of information about DFSORT. It contains papers, examples, online documents, news, tips, techniques and more that can help you get the most out of DFSORT.

System action:

None.

Programmer response:

Optional. Visit the DFSORT website to see what it has to offer.

ICE251A

MISSING RDW OR DATA FOR {*INREC|*OUTREC|ddname}: REASON CODE rsn, IFTHEN n

Explanation:

Critical. For variable-length records, the FIELDS, BUILD, or IFTHEN BUILD operand of an INREC or OUTREC statement, or the OUTREC, BUILD or IFTHEN BUILD operand of an OUTFIL statement, did not start with positions 1 to 4 for the RDW (record descriptor word) or did not contain any data bytes after the RDW. The operand must start with 1,4 or 1:1,4 or 1,n or 1:1,n (with n greater than 4) and must be followed by an input field (for example, 1,8,11,5) or a separation field (for example, 1:1,8,12:C’A’)

Remember that the first data byte starts in position 5 after the RDW in positions 1-4.

The following information is displayed in the message:

  • *INREC if the error is associated with an INREC statement. *OUTREC if the error is associated with an OUTREC statement. ddname if the error is associated with an OUTFIL statement.
  • rsn: The reason code associated with the error. The reason code (listed below) helps you determine the specific cause of the error.
  • n: 0 if the error is not associated with an IFTHEN clause. Otherwise, n identifies the number of the IFTHEN clause associated with the error (starting at 1 for the first IFTHEN clause).

The statement and operand associated with the error are identified as follows:

  • *INREC and n=0 indicates that the FIELDS or BUILD operand of the INREC statement caused the error.
  • *OUTREC and n=0 indicates that the FIELDS or BUILD operand of the OUTREC statement caused the error.
  • ddname and n=0 indicates that the OUTREC or BUILD operand of an OUTFIL statement caused the error. ddname identifies the first data set in the associated OUTFIL group.
  • *INREC and n>0 indicates that an IFTHEN BUILD operand of the INREC statement caused the error. n identifies the number of the associated IFTHEN clause (starting at 1 for the first IFTHEN clause in the INREC statement).
  • *OUTREC and n>0 indicates that an IFTHEN BUILD operand of the OUTREC statement caused the error. n identifies the number of the associated IFTHEN clause (starting at 1 for the first IFTHEN clause in the OUTREC statement).
  • ddname and n>0 indicates that an IFTHEN BUILD operand of an OUTFIL statement caused the error. ddname identifies the first data set in the associated OUTFIL group. n identifies the number of the associated IFTHEN clause (starting at 1 for the first IFTHEN clause in the OUTFIL statement).

Reason code values (rsn) are as follows:

  1. The first field was a separation field, or the first field was preceded by a column other than 1:. Examples:
  2. INREC FIELDS=(4X)
  3. OUTREC BUILD=(8:1,20)
  4. OUTFIL BUILD=(1:C’ABCD’)

  5. The first field was a position without a length. Examples:
  6. INREC BUILD=(1)
  7. OUTREC BUILD=(5)

  8. The first field did not start with 1. Example:
  9. OUTREC IFTHEN=(WHEN=INIT,

    BUILD=(2,8,3X,21,5,HEX))

  10. The first field has a length less than 4. Example:

    INREC BUILD=(1,3,10:X)

  11. The first field is modified or edited. Examples:
  12. INREC BUILD=(1,4,HEX)
  13. OUTREC BUILD=(1,9,PD,M11)
  14. OUTFIL PARSE=(%01=(ENDBEFR=C’,’,FIXLEN=5)),

    BUILD=(%01)

  15. 1,4 is the only field. Example:

    OUTREC BUILD=(1,4)

System action:

The program terminates.

Programmer response:

Take the action for the indicated reason code value (rsn) as follows:

  1. Specify 1,4 before the separation field. . Examples:
  2. INREC FIELDS=(1,4,4X)
  3. OUTREC BUILD=(1,4,8:5C’*’)
  4. OUTFIL BUILD=(1,4,C’ABCD’)

  5. Specify 1,n with n equal to or greater than 4 as the first field. Examples:
  6. INREC BUILD=(1,4,5)
  7. OUTREC BUILD=(1,8,9,10)

  8. Specify 1,n with n equal to or greater than 4 as the first field. Example:
  9. OUTREC IFTHEN=(WHEN=INIT,

    BUILD=(1,8,3X,21,5,HEX))

  10. Specify 1,n with n equal to or greater than 4 as the first field. Example:

    INREC BUILD=(1,4,10:X)

  11. Specify 1,4 before the modified or edited field. Examples:
  12. INREC BUILD=(1,4,1,4,HEX)
  13. OUTREC BUILD=(1,4,5,9,PD,M11)
  14. OUTFIL PARSE=(%01=(ENDBEFR=C’,’,FIXLEN=5)),

    BUILD=(1,4,%01)

  15. Specify at least one input field or separation field after 1,4. Examples:
  16. INREC BUILD=(1,4,X)
  17. OUTREC FIELDS=(1,5)

ICE252I

PARMLIB OPTIONS WERE MERGED WITH INSTALLATION MODULE DEFAULTS

Explanation:

For this run, installation options from one or more ICEPRMxx members in PARMLIB were merged with the defaults for the selected installation module indicated in message ICE191I. DFSORT used the merged installation defaults where appropriate.

System action:

None.

Programmer response:

No action is necessary. You can use the DEFAULTS operator of ICETOOL to display the merged installation defaults, the ICEPRMxx PARMLIB options, and the ICEMAC defaults.

ICE253I

RECORDS SORTED – PROCESSED: p, EXPECTED: e

Explanation:

Indicates the processed (p) and expected (e) records sorted. The number of records includes all records received, added and not deleted during DFSORT input processing.

p is based on the number of records actually processed. e is based on DFSORT’s determination of the total number of records it expected taking into account various factors such as the estimated input file size, the FILSZ value, and so on.

If DFSORT terminated before completing the input phase, p is based on the number of records processed up to the point of failure.

System action:

None.

Programmer response:

Take appropriate action depending on whether or not DFSORT issued message ICE046A:

  • ICE046A: If p is greater then e, specify FILSZ=En, where n is greater than or equal to p and is a reasonably accurate estimate of the number of records to be processed.
  • No ICE046A: If p is significantly different from e, specifying FILSZ=En with a reasonably accurate estimate of the number of records to be sorted can prevent DFSORT from overallocating or underallocating dynamic work space. p was the actual number of records processed for this run. If future runs will process approximately the same amount of data, consider specifying FILSZ=Ep. See z/OS DFSORT Application Programming Guide for information about the FILSZ parameter and factors that can cause a difference between p and e (E15, INCLUDE/OMIT, unmanaged tape, and so on).

See z/OS DFSORT Application Programming Guide for additional information about parameters you can use to provide accurate information to DFSORT that can prevent overallocation or underallocation of dynamic work space (FILSZ, AVGRLEN, DYNSPC, and so on). Also, see the following messages, if issued: ICE098I, ICE254I and ICE258I.

|For a JOINKEYS operation, you can supply any needed |parameters as follows:

|

|

  • In DFSPARM for the JOINKEYS main task. |
  • In JNF1CNTL for the JOINKEYS F1 subtask. |
  • In JNF2CNTL for the JOINKEYS F2 subtask.

ICE254I

DFSORT FAILED TO DYNAMICALLY ALLOCATE THE REQUIRED WORK DATA SET SPACE

Explanation:

The work data set space DFSORT was able to dynamically allocate for this sort application was not sufficient for the application to complete. DFSORT’s determination of the required space takes into account various factors such as the estimated input file size, the average record length, the FILSZ value, the AVGRLEN value, and so on.

Note:

DFSORT uses only the first volume of multi-volume work data sets.

System action:

None.

Programmer response:

You should investigate why DFSORT could not dynamically allocate all of the space it required. You may need to increase the number of work data sets or the available space in the volume pool for the work data sets. You should ensure that DFSORT is provided accurate file size (FILSZ=En) and average record length (AVGRLEN=n) information.

See z/OS DFSORT Application Programming Guide for additional information about parameters you can use to provide accurate information to DFSORT that can prevent overallocation or underallocation of dynamic work space (FILSZ, AVGRLEN, DYNSPC, and so on). Also, see the following messages, if issued: ICE098I and ICE253I.

|For a JOINKEYS operation, you can supply any needed |parameters as follows:

|

|

  • In DFSPARM for the JOINKEYS main task. |
  • In JNF1CNTL for the JOINKEYS F1 subtask. |
  • In JNF2CNTL for the JOINKEYS F2 subtask.

ICE255I

ddname STATISTICS MAY BE INCORRECT – FILSZ=EN MAY IMPROVE RESOURCE USAGE AND PERFORMANCE

Explanation:

DFSORT could not be certain that the data set information provided by Catalog was correct |for this sort application. The catalog entry for this data set indicated that the component was not closed properly and the statistics for the data set are invalid.

Generally, DFSORT can automatically determine the input file size. However, in a few cases, such as when the catalog statistics are invalid, DFSORT may not be able to determine an accurate file size.

System action:

None.

Programmer response:

None required, unless you receive message ICE046A or ICE083A, in which case you should specify FILSZ=En with a reasonably accurate estimate of the number of records to be sorted.

You may want to specify FILSZ=En even if you don’t receive message ICE046A or ICE083A, because doing so may improve resource usage and performance.

For more information regarding the cause of the invalid statistics, or the steps necessary to correct the statistics, see the “STA: Statistics Group” section of z/OS DFSMS Access Method Services for Catalogs.

|

ICE256I

DFSORT CODE IS ELIGIBLE TO USE ZIIP FOR THIS DB2 UTILITY |RUN

|

Explanation:

|

For this DB2 Utility run, DFSORT will execute code that is eligible |to use the IBM System z Integrated Information Processor (zIIP) subject |to its availability.

|

System action:

|

None.

|

Programmer response:

|

None.

|

ICE257A

CRITICAL ERROR RETURNED FROM SRB – a b c d

|

Explanation:

|

Critical. A system error occurred or an abend was requested while |DFSORT was executing a Service Request Block (SRB) eligible to use |the IBM System z Integrated Information Processor (zIIP). a, b, c |and d provides information to help IBM diagnose the failure.

|

System action:

|

The program terminates.

|

Programmer response:

|

Contact IBM for programming support and provide the values displayed |for fields a, b, c and d.

ICE258I

DFSORT COULD NOT DYNAMICALLY ALLOCATE THE OPTIMAL WORK DATA SET SPACE

Explanation:

The work data set space DFSORT was able to dynamically allocate for this sort application was not the optimal amount. DFSORT’s determination of the optimal space takes into account various factors such as the estimated input file size, the average record length, the FILSZ value, the AVGRLEN value, and so on.

Note:

DFSORT uses only the first volume of multi-volume work data sets.

System action:

None.

Programmer response:

You should consider investigating why DFSORT could not dynamically allocate all of the space it requested. Although DFSORT can often complete successfully with less than the optimal work data set space, a failure is more likely if the work space requirements are greater than expected. You may want to increase the number of work data sets or the available space in the volume pool for the work data sets. You should ensure that DFSORT is provided accurate file size (FILSZ=En) and average record length (AVGRLEN=n) information.

See z/OS DFSORT Application Programming Guide for additional information about parameters you can use to provide accurate information to DFSORT that can prevent overallocation or underallocation of dynamic work space (FILSZ, AVGRLEN, DYNSPC, and so on). Also, see the following messages, if issued: ICE098I and ICE253I.

|For a JOINKEYS operation, you can supply any needed |parameters as follows:

|

|

  • In DFSPARM for the JOINKEYS main task. |
  • In JNF1CNTL for the JOINKEYS F1 subtask. |
  • In JNF2CNTL for the JOINKEYS F2 subtask.

ICE259A

PUSH FIELD ERROR

Explanation:

Critical. The PUSH operand of an INREC, OUTREC or OUTFIL statement contained an invalid column, position or length, as follows:

  • A 0 value was used.
  • A column was greater than 32752, or was followed by another column.
  • An input position plus length was greater than 32753.
  • The length for a SEQ or ID field was greater than 15.
  • An output field was beyond position 32767.

System action:

The program terminates.

Programmer response:

Correct the invalid column, position or length.

ICE260A

FIND/REPLACE FIELD ERROR

Explanation:

Critical. One of the following errors was found in the FINDREP operand of an INREC, OUTREC or OUTFIL statement:

  • A 0 value was used.
  • A null value was used where it was not permitted.
  • IN or INOUT was not specified.
  • INOUT, IN, OUT, STARTPOS, ENDPOS, DO, MAXLEN, OVERRUN or SHIFT was specified more than once.
  • INOUT was specified with IN or OUT.
  • IN was specified without OUT, or OUT was specified without IN.
  • An input constant was specified without a matching output constant in INOUT.
  • A repetition factor was 0 or greater than 256 for a character string or hexadecimal string.
  • The total length of a single or repeated character or hexadecimal constant was greater than 256 bytes.
  • An invalid digit or an odd number of digits was specified for a hexadecimal string.
  • The value for STARTPOS, ENDPOS or MAXLEN was greater than 32752.
  • The value for DO was greater than 1000.

System action:

The program terminates.

Programmer response:

Check the FINDREP operand for the errors indicated in the explanation and correct the errors.

ICE261A

FIND AND REPLACE CAUSED OVERRUN OF n BYTE {*INREC/*OUTREC/ddname} OUTPUT RECORD END

Explanation:

Critical. OVERRUN=ERROR was specified or defaulted for the FINDREP operand of an INREC, OUTREC or OUTFIL statement, and processing of the find/replace constants caused nonblank characters to overrun the end of the maximum of n bytes allowed for the output record. This can occur when an output constant is longer than an input constant (for example, INOUT=(C’A’,C’XYZ’)), or when the length of the record to be created by FINDREP is less than the length of the original record (for example, when the input record is 80 bytes and MAXLEN=50 is used to decrease the length of the record).

The specific source of the error is identified as follows:

  • *INREC indicates that a FINDREP operand in the INREC statement caused the error.
  • *OUTREC indicates that a FINDREP operand in the OUTREC statement caused the error.
  • ddname indicates that a FINDREP operand in an OUTFIL statement caused the error; ddname identifies the first data set in the associated OUTFIL group.

System action:

The program terminates.

Programmer response:

If you want to truncate nonblank characters that overrun the end of the record, specify OVERRUN=TRUNC. If you do not want to truncate nonblank characters that overrun the end of the record, increase the length of the record using MAXLEN=m with a value for m equal to or greater than the maximum length record to be created by FINDREP.

|

ICE264I

ddname STATISTICS MAY be INCORRECT

|

Explanation:

|

DFSORT could not be certain that the data set information provided |by Catalog was correct for this copy application. The catalog entry |for this data set indicated that the component was not closed properly |and the statistics for the data set are invalid.

|

System action:

|

None.

|

Programmer response:

|

None required. For more information regarding the cause of the |invalid statistics, or the steps necessary to correct the statistics, |see the “STA: Statistics Group” section of z/OS DFSMS Access Method Services for Catalogs.

ICE271I

SYMNAMES IS EMPTY – SYMBOL SUBSTITUTION WILL NOT BE PERFORMED

Explanation:

A SYMNAMES data set was specified, but was empty (that is, it contained no statements). Symbol substitution will not be performed.

System action:

Processing continues without symbol substitution.

Programmer response:

If symbol substitution is needed, add appropriate SYMNAMES statements to the specified SYMNAMES data set or specify a non-empty SYMNAMES data set.

ICE272A

SYMBOL, VALUE OR SYNTAX IS INVALID

Explanation:

Critical. The SYMNAMES statement has one of the following errors:

  • The symbol starts with a number (0-9) or a hyphen (-).
  • The value contains an invalid parsed field. A valid parsed field must be %nn (nn is 00 to 99) or %n (n is 0 to 9).
  • The symbol or value contains an invalid character. The valid characters are uppercase letters (A-Z), lowercase letters (a-z), numbers (0-9), the number sign (#), the dollar sign ($), the commercial at sign (@), the underscore(_), and the hyphen (-).
  • The symbol, keyword or value is null (for example, symbol,,5,CH).
  • The symbol, keyword or value is followed by or contains an invalid delimiter.
  • p or m in p,m or p,m,f is 0 or greater than 32752 or contains a non-numeric character.
  • q in POSITION,q is 0 or greater than 32752 or contains a non-numeric character.
  • symbol in POSITION,symbol references a symbol that was not previously defined or which was previously defined without a valid position (for example, a symbol for a constant).
  • n in SKIP,n is 0 or greater than 32752 or contains a non-numeric character.
  • The decimal constant contains a non-numeric character other than a leading plus sign (+) or minus sign (-).
  • An equal sign (=) is specified for p, m or f, but the previous position, previous length or previous format, respectively, was not established.
  • f in p,m,f is not a valid format. The valid formats are AC, AQ, ASL, AST, BI, CH, CLO, CSF, CSL, CST, CTO, DC1, DC2, DC3, DE1, DE2, DE3, DT1, DT2, DT3, D1, D2, FI, FL FS, LS, OL, OT, PD, PD0, SFF, SS, TC1, TC2, TC3, TC4, TE1, TE2, TE3, TE4, TM1, TM2, TM3, TM4, TS, UFF, Y2B, Y2C, Y2D, Y2DP, Y2P, Y2PP, Y2S, Y2T, Y2TP, Y2U, Y2UP, Y2V, Y2VP, Y2W, Y2WP, Y2X, Y2XP, Y2Y, Y2YP, Y2Z|, Y4T, Y4U, |Y4V, Y4W, Y4X, Y4Y and ZD, and lowercase or mixed case variations
  • x in ALIGN,x is not a valid alignment. The valid alignments are H, F, D, h, f and d.
  • The character constant, system symbol constant, hexadecimal constant, or bit constant does not have an ending apostrophe after the string.
  • The hexadecimal constant is null (X”) or contains an odd number of digits (for example, X’123′).
  • The hexadecimal constant contains an invalid character. The valid characters are 0-9, A-F and a-f.
  • The bit constant is null (B”) or contains a number of bits that is not a multiple of 8 (for example, B’1010′).
  • The bit constant contains an invalid character. The valid characters are . (period), 0 and 1.

System action:

The program terminates.

Programmer response:

Correct the symbol, value or syntax error.

ICE273A

SYMBOL OR VALUE IS TOO LONG

Explanation:

Critical. The SYMNAMES statement has one of the following errors:

  • The symbol is longer than 50 characters.
  • The value contains a number longer than 31 significant digits.
  • The constant contains a string longer than 64 characters.

System action:

The program terminates.

Programmer response:

Specify a symbol, value or string that is less than or equal to the allowed limit.

ICE274A

NEXT POSITION TO BE USED FOR * IS LARGER THAN 32752

Explanation:

Critical. The SYMNAMES statement specifies an asterisk (*) for p requesting that the next position be used for p. However, the next position is greater than the limit for p of 32752.

Calculation of the next position will be discontinued once a SYMNAMES statement error has been detected. Therefore, ICE274A is only issued once and only if a previous SYMNAMES processing error was not detected.

System action:

The program terminates.

Programmer response:

Specify a value for p that is less than or equal to 32752. You can do this directly by specifying a number for p or indirectly by specifying * for p and ensuring that the next position is less than or equal to 32752. See z/OS DFSORT Application Programming Guide for an explanation of how the next position is set.

ICE275A

DUPLICATE SYMBOL

Explanation:

Critical. The symbol was used in a previous SYMNAMES statement. A symbol can only be used once in SYMNAMES.

System action:

The program terminates.

Programmer response:

Remove or rename one of the duplicate symbols.

ICE276A

RESERVED WORD – NOT ALLOWED FOR SYMBOL

Explanation:

Critical. The SYMNAMES statement specifies a DFSORT/ICETOOL reserved word for the symbol. Reserved words cannot be used for symbols. The reserved words are as follows (uppercase only as shown): A, AC, ADD, ALL, AND, AQ, ASL, AST, BI, CH, CLO, COPY, COUNT, COUNT15, CSF, CSL, CST, CTO, D, DATE, DATE1, DATE1…, DATE2, DATE2…, DATE3, DATE3…, DATE4, DC1, DC2, DC3, DE1, DE2, DE3, DIV, DT1, DT2, DT3, D1, D2, E, F, FI, FL, FS, H, HEX, LS, MAX, MIN, MOD, MUL, Mn, Mnn, NONE, NUM, OL, OR, OT, PAGE, PAGEHEAD, PD, PDC, PDF, PD0, SEQNUM, SFF, SS, SUB, SUBCOUNT, SUBCOUNT15, TC1, TC2, TC3, TC4, TE1, TE2, TE3, TE4, TIME, TIME1, TIME1P, TIME2, TIME2P, TIME3, TIME3P, TM1, TM2, TM3, TM4, TS, UFF, VALCNT, VLEN, X, Y2x, Y2xx, |Y4x, Z, ZD, ZDC, and ZDF, where n is 0-9 and x is any character.

System action:

The program terminates.

Programmer response:

Use a symbol that is not one of the reserved words, such as a lowercase or mixed case version of the word being used. For example, you could use Valcnt (which is not a reserved word) instead of VALCNT (which is).

|

ICE278I

x WORK DATA SETS WERE INSUFFICIENT TO COMPLETE THIS SORT |SO y ADDITIONAL WORK DATA SETS WERE USED

|

Explanation:

|

DFSORT initially intended to use only x work data sets for this |sort application. However, the work space requirements for the sort |were unexpectedly larger than anticipated, so DFSORT used y additional |work data sets.

|

System action:

|

None.

|

Programmer response:

|

Verify that DFSORT has the correct file size information to allow |it to accurately calculate the initial amount of work space needed. | See messages ICE098I and ICE253I for additional information.

ICE279A

ONE OR MORE ERRORS ENCOUNTERED DURING SYMNAMES PROCESSING

Explanation:

Critical. DFSORT or ICETOOL detected one or more errors while processing SYMNAMES statements.

System action:

The program terminates.

Programmer response:

Correct each error indicated by a previous error message (ICE272A through ICE276A).

ICE280I

ORIGINAL STATEMENTS FROM source FOLLOW

Explanation:

This message is issued for each source specified. It is followed by a listing of the original DFSORT control statements before they are transformed by symbol processing. Source can be one of the following:

  • DFSPARM or the ddname specified by the PARMDDN installation option
  • SYSIN
  • xxxxCNTL
  • PARMLIST

System action:

None.

Programmer response:

None.

ICE281I

ORIGINAL OPERATOR STATEMENTS FOLLOW

Explanation:

This message is followed by a listing of the original ICETOOL operator statements before they are transformed by symbol processing. The operator statements listed are from TOOLIN or the calling program’s parameter list as indicated by message ICE632I.

System action:

None.

Programmer response:

None.

ICE282I

PERFORMING SYMBOL SUBSTITUTION AS NEEDED

Explanation:

DFSORT or ICETOOL successfully processed the SYMNAMES statements. ICETOOL will transform operators as necessary using symbol substitution. DFSORT will transform control statements as necessary using symbol substitution. Any operators or control statements with substitution errors will be shown after ICE282I.

System action:

None.

Programmer response:

None.

ICE283A

SYMBOL, SYNTAX OR DELIMITER ERROR

Explanation:

Critical. During symbol substitution processing, one of the following errors was found in a control statement or operator:

  • A specified symbol was not defined in SYMNAMES.

    Note:

    Symbols are treated as case-sensitive: Frank, FRANK, and frank are three different symbols. Be careful to use symbols in control statements and operators exactly as they are defined in SYMNAMES.

  • A specified symbol was longer than 50 characters.
  • A specified symbol started with an invalid character or with a delimiter. Examples:
  • SORT FIELDS=(.Sym1,A)
  • * .Sym1 is invalid. FIELDS=(Sym1,A) is valid.
  • INREC FIELDS=((Sym1)

    * ((Sym1) is invalid. FIELDS=(Sym1) is valid.

  • A specified symbol contained an invalid character. Examples:
  • SUM FIELDS=(New-Field)
  • * New*Field is invalid. New_Field is valid.
  • * New-Field is valid.
  • OUTREC FIELDS=(A%B)

    * A%B is invalid.

    Note:

    A symbol with an invalid character cannot be defined in SYMNAMES.

  • A specified symbol was followed by an invalid delimiter. Examples:
  • SUM FIELDS=(Sym1 )
  • * (Sym1 ) is invalid. FIELDS=(Sym1) is valid.
  • OUTFIL OUTREC=(Sym1/)

    * Sym1/ is invalid. OUTREC=(Sym1,/) is valid.

  • A delimiter was misplaced. Examples:
  • VERIFY ON(,Sym1)
  • * (,Sym1) is invalid. ON(Sym1) is valid.
  • VERIFY ON((5,4,PD)
  • * ((5,4,PD) is invalid. ON(5,4,PD) is valid.
  • VERIFY ON(5,4,PD))

    * (5,4,PD)) is invalid. ON(5,4,PD) is valid.

  • A syntax error caused a value to be misinterpreted as an undefined symbol. Example:

    OUTREC FIELDS=(1,4,ZD,EDIT(IIIT))

    EDIT is misinterpreted as an undefined symbol because an equal sign is missing. The following is valid:

    OUTFIL OUTREC=(1,4,ZD,EDIT=(IIIT))

System action:

The program terminates.

Programmer response:

Correct the symbol, syntax or delimiter error.

ICE284A

SYMBOL SUBSTITUTION CAUSES OPERAND TO OVERFLOW COLUMN 72

Explanation:

Critical. The operand contained a symbol. Substitution of the value for the symbol caused the operand to exceed 72 characters if the line was not continued or 71 characters if the line was continued. ICETOOL operators must be contained in columns 1-72, so the transformed operand cannot be processed by ICETOOL.

System action:

The program terminates.

Programmer response:

Use a symbol or value that will not cause the operand to overflow column 72. If necessary, change the value in the SYMNAMES statement for the symbol.

ICE285A

BLOCKSET IS REQUIRED FOR WORK DATA SETS ON VOLUMES WITH MORE THAN 17476 CYLINDERS

Explanation:

Critical. One or more JCL or dynamically allocated work data sets was allocated on a device with more than 17476 cylinders. Blockset is the only DFSORT technique that supports the use of such devices for work data sets, but Blockset was not selected.

System action:

The program terminates.

Programmer response:

Rerun the job with a SORTDIAG DD statement to get message ICE800I, which indicates the reason Blockset could not be used. If possible, remove the condition preventing the use of Blockset. Alternatively, ensure that work data sets are not allocated on devices with more than 17476 cylinders for this application.

ICE287A

ONE OR MORE ERRORS ENCOUNTERED DURING SYMBOL SUBSTITUTION

Explanation:

Critical. DFSORT or ICETOOL detected one or more errors during symbol substitution processing.

System action:

The program terminates.

Programmer response:

Correct each error indicated by a previous error message (ICE283A or ICE284A).

|

ICE288I

INPUT OR OUTPUT DATE VALUE OUT OF RANGE FOR DATE CONVERSION

|

Explanation:

|

For a date conversion operation using TOJUL, TOGREG, WEEKDAY, DT |or DTNS, an invalid input date was used.

|

A date value is considered invalid if any of the following range |conditions are not met:

|

|

  • yy must be between 00 and 99 |
  • ccyy must be between 0001 and 9999 |
  • mm must be between 01 and 12 |
  • dd must be between 01 and 31, and must be valid for the year and |month |
  • ddd must be 001 to 366 for a leap year, or between 001 and 365 |for a non-leap year.

|

A date is also considered invalid if the input field is a CH/ZD |special indicator of binary zeros, blanks or binary ones, and the |output field is PD.

|

System action:

|

Asterisks are printed for each invalid output value. The message |is only issued once. Processing continues.

|

Programmer response:

|

Check for output values containing asterisks and ensure that the |input date value is valid and that you are not converting a CH/ZD |special indicator of binary zeros, blanks or binary ones to a PD value.

|

ICE289A

UNSUPPORTED EXTENDED ATTRIBUTES FOR ddname

|

Explanation:

|

Critical. Extended attributes for the data set associated with |the indicated ddname are not supported by the system on which DFSORT |is running. A data set with extended attributes is described with |format 8 and 9 DSCBs (Data Set Control Blocks) in the VTOC and may |contain extents that are allocated in the Extended Addressing Space |(EAS) where tracks are described by 28-bit cylinder numbers.

|

System action:

|

The program terminates.

|

Programmer response:

|

Use this data set with DFSORT on a system that supports the data |set’s extended attributes.

ICE298I

AVERAGE RECORD LENGTH = n BYTES

Explanation:

Indicates the average record length (n) in bytes for the variable-length records processed by sort when Blockset was not selected, that is, the number of bytes in the variable-length records (including the record descriptor word) divided by the number of records. The number of records includes all records received, added and not deleted during DFSORT input processing.

n is based on the number of bytes and records actually processed.

If DFSORT terminated before completing the input phase, p is based on the number of bytes and records processed up to the point of failure.

System action:

None.

Programmer response:

None. However, specifying AVGRLEN=n with a reasonably accurate estimate of the average record length can prevent DFSORT from overallocating or underallocating dynamic work space.

|For a JOINKEYS operation, you can supply AVGRLEN=n, |if needed, as follows:

|

|

  • In DFSPARM for the JOINKEYS main task. |
  • In JNF1CNTL for the JOINKEYS F1 subtask. |
  • In JNF2CNTL for the JOINKEYS F2 subtask.

|

ICE299I

MEMORY OBJECT USED AS WORK STORAGE = nM BYTES

|

Explanation:

|

n is the number of megabytes of memory object storage |DFSORT used as intermediate work space during this sort. If n is |zero, DFSORT did not use memory object storage as intermediate work |space during this sort.

|

System action:

|

None.

|

Programmer response:

|

None.

|

ICE400A

INVALID JOINKEYS, JOIN OR REFORMAT STATEMENT OPERAND

|

Explanation:

|

Critical. An invalid keyword operand was detected on a JOINKEYS, |JOIN or REFORMAT control statement.

|

System action:

|

The program terminates.

|

Programmer response:

|

Make sure the JOINKEYS, JOIN or REFORMAT control statement contains |only valid keyword operands.

|

ICE401A

DUPLICATE JOINKEYS, JOIN OR REFORMAT STATEMENT OPERAND

|

Explanation:

|

Critical. One of the following errors was found:

|

|

  • On a JOINKEYS, JOIN or REFORMAT statement, a keyword was specified |twice. |
  • On a JOINKEYS statement, more than one of FILE=F1, FILES=F1, F1=ddname, |FILE=F2, FILES=F2 or F2=ddname was specified. |
  • On a JOINKEYS statement, INCLUDE and OMIT were both specified.

|

System action:

|

The program terminates.

|

Programmer response:

|

Check the JOINKEYS, JOIN or REFORMAT control statement for the |errors indicated in the explanation and correct the error.

|

ICE402A

JOINKEYS STATEMENT FOR Fn WAS REQUIRED, BUT NOT FOUND

|

Explanation:

|

Critical. A JOINKEYS application was requested by a JOINKEYS, |JOIN or REFORMAT statement, or a JKFROM operand (ICETOOL COPY or SORT), |but a JOINKEYS statement for file F1 or file F2, as indicated, was |not found.

|

System action:

|

The program terminates.

|

Programmer response:

|

Supply two JOINKEYS statements; one for F1 (with FILE=F1, FILES=F1 |or F1=ddname) and another for F2 (with FILE=F2, FILES=F2 or F2=ddname).

|

ICE403A

OPERAND keyword WAS REQUIRED FOR verb STATEMENT, BUT NOT |FOUND

|

Explanation:

|

Critical. The indicated required keyword was missing for the indicated |control statement as follows:

|

|

  • For a JOINKEYS statement, FILE=F1, FILES=F1, FILE=F2, FILES=F2, |F1=ddname or F2=ddname must be specified. |
  • For a JOINKEYS statement, FIELDS must be specified. |
  • For a JOIN statement, UNPAIRED must be specified. |
  • For a REFORMAT statement, FIELDS must be specified.

|

System action:

|

The program terminates.

|

Programmer response:

|

Specify the indicated keyword for the indicated control statement.

|

ICE404A

REFORMAT STATEMENT WAS REQUIRED, BUT NOT FOUND

|

Explanation:

|

Critical. A JOIN statement with an ONLY operand was not specified, |so a REFORMAT statement is required. However, a REFORMAT statement |was not found.

|

System action:

|

The program terminates.

|

Programmer response:

|

Either specify a JOIN statement with the ONLY operand, or specify |a REFORMAT statement, as appropriate.

|

ICE405A

JOINKEYS STATEMENTS HAD MISMATCH IN NUMBER, LENGTH OR ORDER |OF KEYS

|

Explanation:

|

Critical. The keys (p,m,s) specified in the FIELDS operands of |the JOINKEYS statements for F1 and F2 did not match in one or more |of the following ways:

|

|

  • The two FIELDS operands have different numbers of keys. For example, |FIELDS for F1 has two keys and FIELDS for F2 has three keys. |
  • Corresponding keys in the two FIELDS operands have different lengths. | For example, the second key for F1 has a length of 5 and the second |key for F2 has a length of 6. |
  • Corresponding keys in the two FIELDS operands have different orders. | For example, the third key for F1 has ascending order (A) and the |third key for F2 has descending order (D).

|

System action:

|

The program terminates.

|

Programmer response:

|

Ensure that the FIELDS operands of the JOINKEYS statements for |F1 and F2 have the same number of keys, and that corresponding keys |have the same length and order.

|

ICE406A

JOINKEYS STATEMENT FIELD ENDS AFTER POSITION 32752

|

Explanation:

|

Critical. The last byte of the key (p,m,s) in a JOINKEYS FIELDS |operand ended beyond position 32752. Each key must end at or before |position 32752 (position plus length must not be greater than 32753). | For example, 32752,1,A is valid because it ends at position 32752, |but 32752,2,A is invalid because it ends at position 32753.

|

System action:

|

The program terminates.

|

Programmer response:

|

Ensure that each key in the JOINKEYS FIELDS operand ends at or |before position 32752.

|

ICE407A

JOINKEYS STATEMENT HAD TOTAL KEY LENGTH GREATER THAN 4080 |BYTES

|

Explanation:

|

Critical. The total length of all of the keys (p,m,s) in a JOINKEYS |FIELDS operand exceeded the limit of 4080 bytes.

|

System action:

|

The program terminates.

|

Programmer response:

|

Ensure that the total length of all of the keys in the JOINKEYS |FIELDS operand is less than or equal to 4080 bytes.

|

ICE408A

MERGE FUNCTION CANNOT BE USED WITH JOINKEYS MAIN TASK

|

Explanation:

|

Critical. A MERGE FIELDS=(p,m,s,…) statement was found for the |main task of a JOINKEYS application in SYSIN, SORTCNTL, DFSPARM or |a parameter list. A MERGE function cannot be used with JOINKEYS.

|

System action:

|

The program terminates.

|

Programmer response:

|

Replace the MERGE FIELDS=(p,m,s,…) statement with a MERGE FIELDS=COPY, |SORT FIELDS=COPY, OPTION COPY or SORT FIELDS=(p,m,s,…) statement, |as appropriate.

|

ICE409A

INSUFFICIENT STORAGE FOR JOINKEYS APPLICATION – ADD AT LEAST |nMB

|

Explanation:

|

Critical. DFSORT could not get the additional nMB of storage needed |for this JOINKEYS application.

|

System action:

|

The program terminates.

|

Programmer response:

|

Add at least nMB to the storage available to DFSORT (for example, |increase the REGION size).

|

ICE410A

JOINKEYS APPLICATION TERMINATED – SEE ddname MESSAGES

|

Explanation:

|

Critical. This message is issued by subtask1 (for file F1) or |subtask2 (for file F2) of a JOINKEYS application to indicate that |the main task terminated. ddname is the ddname associated with the |message data set for the main task.

|

System action:

|

The program terminates.

|

Programmer response:

|

See the messages in the indicated ddname data set for information |about the main task. Correct the error that caused the main task |to terminate.

|

ICE411I

THIS IS THE JOINKEYS MAIN TASK FOR JOINING F1 AND F2

|

Explanation:

|

Indicates this is the main task for a JOINKEYS application. The |main task processes the joined records from input files F1 and F2 |and writes the output.

|

System action:

|

None.

|

Programmer response:

|

None.

|

ICE412A

REFORMAT REQUIRES RDW IN FIRST FIELD

|

Explanation:

|

The FIELDS operand of the REFORMAT statement has a position without |a length (p without m) as its last field, but the first field does |not include the RDW (1,n with n equal to or greater than 4). For |example, the REFORMAT statement is:

|

REFORMAT FIELDS=(F1:5,8,F2:1,20,F1:15)

|

instead of:

|

REFORMAT FIELDS=(F1:1,8,F2:1,20,F1:15)

|

or the REFORMAT statement is:

|

REFORMAT FIELDS=(?,F1:1,4,5)

|

instead of:

|

REFORMAT FIELDS=(F1:1,4,?,F1:5)

|

System action:

|

The program terminates.

|

Programmer response:

|

Include the RDW (1,n with n equal to or greater than 4) in the |first field, or do not use a position without a length, as appropriate.

|

ICE413A

REFORMAT REQUIRES TYPE=V FILE FOR RDW AND VARIABLE FIELDS

|

Explanation:

|

Critical. The FIELDS operand of the REFORMAT statement has a position |without a length (p without m) as its last field, but has one of the |following errors:

|

|

  • F1: is used for the first field (which includes the RDW), but |F1 does not refer to a TYPE=V file. |
  • F2: is used for the first field (which includes the RDW), but |F2 does not refer to a TYPE=V file. |
  • F1: is used for a position without length field, but F1 does |not refer to a TYPE=V file. |
  • F2: is used for a position without length field, but F2 does |not refer to a TYPE=V file.

|

For example, SORTJNF1 for F1 has RECFM=FB and SORTJNF2 for F2 has |RECFM=VB and the REFORMAT statement is:

|

REFORMAT FIELDS=(F1:1,20,F2:5,6,15)

|

instead of:

|

REFORMAT FIELDS=(F2:1,4,F1:1,20,F2:5,6,15)

|

System action:

|

The program terminates.

|

Programmer response:

|

Ensure that the file (F1 or F2) used for the first field, and for |each position without length field, is a TYPE=V file.

|

ICE414A

ddname (Fn) type FIELD END AT p IS BEYOND LENGTH OF n

|

Explanation:

|

Critical. A JOINKEYS or REFORMAT statement specifies a field which |ends beyond the maximum record length. The information displayed |in the message is as follows:

|

|

  • the ddname of the input file with the field in error. |
  • the file (F1 or F2) with the field in error. |
  • the type of field in error as follows: |

    |

    • KEY to indicate a field in the FIELDS operand of a JOINKEYS statement. |
    • INCLUDE to indicate a field in the INCLUDE operand of a JOINKEYS |statement. |
    • OMIT to indicate a field in the OMIT operand of a JOINKEYS statement. |
    • REFORMAT to indicate a field in the FIELDS operand of a REFORMAT |statement.

    |

  • the position (p) at which the field ends. |
  • the maximum record length (n) which the ending position exceeded

|

System action:

|

The program terminates.

|

Programmer response:

|

Ensure that all fields specified in JOINKEYS and REFORMAT statements |are contained within the maximum record length indicated.

|

ICE415A

TYPE=x JOINED RECORD LENGTH OF n EXCEEDS MAXIMUM OF m

|

Explanation:

|

Critical. The maximum length (n) of the joined records for a JOINKEYS |application, as defined by the REFORMAT statement or by default if |a REFORMAT statement was not specified, exceeds the maximum length |(m) of 32760 for TYPE=F records or 32767 for TYPE=V records.

|

System action:

|

The program terminates.

|

Programmer response:

|

Reduce the maximum length of the joined records so it does not |exceed the maximum length of 32760 for TYPE=F records or 32767 for |TYPE=V records.

|

Note that the maximum LRECL for RECFM=VB records is 32756 and the |maximum LRECL for RECFM=VBS records is 32767; if you want RECFM=VBS |records, ensure that RECFM is specified appropriately for the output |data set.

|

ICE416I

JOINKEYS IS USING THE Fn SUBTASK FOR ddname1 – SEE ddname2 |MESSAGES

|

Explanation:

|

Indicates DFSORT is using a subtask to process the Fn (F1 or F2) |file for a JOINKEYS application. ddname1 is the ddname associated |with the input file for the subtask. ddname2 is the ddname associated |with the message data set for the subtask.

|

System action:

|

None.

|

Programmer response:

|

See the messages in the indicated ddname2 data set for information |about the subtask.

|

ICE417I

THIS IS THE JOINKEYS Fn SUBTASK FOR ddname

|

Explanation:

|

Indicates this is a subtask used to process the Fn (F1 or F2) |file for a JOINKEYS application. The subtask passes the needed Fn |fields to the main task. ddname is the ddname for the input file associated |with the subtask.

|

System action:

|

None.

|

Programmer response:

|

None.

|

ICE418A

JOINKEYS Fn SUBTASK FOR ddname1 TERMINATED – SEE ddname2 |MESSAGES

|

Explanation:

|

Critical. This message is issued by the main task of a JOINKEYS |application to indicate that the subtask used to process file Fn (F1 |or F2) terminated. ddname1 is the ddname associated with the input |file for the subtask. ddname2 is the ddname associated with the message |data set for the subtask.

|

System action:

|

The program terminates.

|

Programmer response:

|

See the messages in the ddname2 data set for information about |the subtask. Correct the error that caused the subtask to terminate.

|

ICE419I

JOINED RECORDS: TYPE=x, LENGTH=n

|

Explanation:

|

Indicates the record type (F or V) and maximum record length (n) |of the joined records passed as input to the main task of a JOINKEYS |application.

|

System action:

|

None.

|

Programmer response:

|

None.

|

ICE420A

COULD NOT ALLOCATE ddname FOR Fn MESSAGES – SUPPLY DD STATEMENT

|

Explanation:

|

Critical. For a JOINKEYS application, a required message data |set was not found and could not be dynamically allocated. A DD statement |for the indicated ddname was required for the messages associated |with the subtask for the F1 or F2 file. A DD statement for that ddname |was not found, so DFSORT attempted to dynamically allocate a SYSOUT=* |message data set. However, the message data set could not be allocated.

|

System action:

|

The program terminates.

|

Programmer response:

|

Supply a message data set using a DD statement for the indicated |ddname.

|

ICE421I

JOINED RECORDS: COUNT=n

|

Explanation:

|

Indicates the number (n) of joined records passed as input to the |main task of a JOINKEYS application.

|

System action:

|

None.

|

Programmer response:

|

None.

|

ICE422I

JOINKEYS STATEMENT FOR Fn FOUND PREVIOUSLY – THIS STATEMENT |IGNORED

|

Explanation:

|

A JOINKEYS statement for the indicated file (F1 or F2) was found |previously in this source (for example, SYSIN) or in a higher source |(for example, DFSPARM is higher than SYSIN). The second and subsequent |JOINKEYS statement for F1 or F2 in the same source or in a lower source |is ignored.

|

System action:

|

None.

|

Programmer response:

|

Correct the conflicting JOINKEYS statements, if appropriate.

|

ICE423A

REFORMAT STATEMENT FIELD ENDS AFTER POSITION 32767

|

Explanation:

|

Critical. The last byte of a field (p,m) in a REFORMAT FIELDS |operand ended beyond position 32767. Each field must end at or before |position 32767 (position plus length must not be greater than 32768). | For example, 32767,1 is valid because it ends at position 32767, |but 32767,2 is invalid because it ends at position 32768.

|

System action:

|

The program terminates.

|

Programmer response:

|

Ensure that each field in the REFORMAT FIELDS operand ends at or |before position 32767.

|

ICE424A

ddname (Fn) KEY IS OUT OF SEQUENCE

|

Explanation:

|

Critical. The SORTED operand was specified without the NOSEQCK |operand on the JOINKEYS statement associated with the indicated ddname |for file F1 or F2. DFSORT checked the records of the indicated file |and found a record out of sequence for the keys specified in the FIELDS |operand of the JOINKEYS statement.

|

System action:

|

The program terminates.

|

Programmer response:

|

Remove the SORTED operand from the JOINKEYS statement for the indicated |file (F1 or F2) to force DFSORT to sort that file by the specified |keys.

|

ICE425A

ddname CANNOT BE USED AS DDNAME FOR BOTH F1 AND F2

|

Explanation:

|

Critical. The indicated ddname was used on the JOINKEYS statements |for both file F1 and F2 (for example, one JOINKEYS statement has F1=IN1 |and the other JOINKEYS statement has F2=IN1). Different ddnames must |be used for the two files.

|

System action:

|

The program terminates.

|

Programmer response:

|

Change the F1, F2 or FILE operand in one or both of the JOINKEYS |statements to use different ddnames for the two files.

|

ICE426A

cccc CANNOT BE USED AS PREFIX FOR JOINKEYS MAIN TASK AND |SUBTASK

|

Explanation:

|

Critical. For a JOINKEYS application, the SORTDD value for the |main task and the TASKID value for a subtask resulted in the same |four character prefix indicated by cccc (for example, SORTDD=MYF1 |and TASKID=MY both result in a prefix of MYF1). Different prefixes |must be used for the main task and the subtasks.

|

System action:

|

The program terminates.

|

Programmer response:

|

Change the SORTDD operand for the main task, or the TASKID operand |for the subtask, to use different prefixes.

|

ICE427A

verb STATEMENT CANNOT BE USED WITH JOINKEYS SUBTASK

|

Explanation:

|

Critical. For a JOINKEYS application, a JOINKEYS, JOIN, MERGE, |OUTFIL, OUTFILE, OUTREC, REFORMAT or SORT statement was found in JNF1CNTL |for subtask1 or in JNF2CNTL for subtask2. These statements cannot |be used for a JOINKEYS subtask.

|

System action:

|

The program terminates.

|

Programmer response:

|

Remove all statements that cannot be used for a JOINKEYS subtask |from JNF1CNTL or JNF2CNTL.

|

ICE428A

TOO MANY DUPLICATES OF ONE KEY IN ddname (F2)

|

Explanation:

|

Critical. The F2 file associated with the indicated ddname contained |more duplicates for a single key than DFSORT could process with the |storage available.

|

System action:

|

The program terminates.

|

Programmer response:

|

If possible, increase the storage available to DFSORT (for example, |try specifying REGION=0M). Alternatively, if the maximum duplicates |for a single key in file F1 is less than the maximum duplicates for |a single key in file F2, reverse F1 and F2. For example, if you received |this error with these control statements:

|

JOINKEYS F1=IN1,FIELDS=(11,4,A)

| JOINKEYS F2=IN2,FIELDS=(21,4,A)

| REFORMAT FIELDS=(F1:1,20,F2:5,30)

|

and the maximum duplicates for a single F1 key is less than the |maximum duplicates for a single F2 key, use these control statements |instead:

|

JOINKEYS F1=IN2,FIELDS=(21,4,A)

| JOINKEYS F2=IN1,FIELDS=(11,4,A)

| REFORMAT FIELDS=(F2:1,20,F1:5,30)

|

ICE429A

JOINKEYS APPLICATION IS ONLY ALLOWED WITH SORT OR COPY OPERATOR

|

Explanation:

|

Critical. A JOINKEYS, JOIN or REFORMAT statement was specified |for an ICETOOL operator other than SORT or COPY. A JOINKEYS application |is only allowed for a SORT or COPY operator, not for any of the other |operators.

|

System action:

|

The program terminates.

|

Programmer response:

|

Redesign the application to not use JOINKEYS, JOIN or REFORMAT |with ICETOOL operators other than SORT or COPY.

ICE600I

DFSORT ICETOOL UTILITY RUN STARTED

Explanation:

Indicates the start of the ICETOOL run.

System action:

None.

Programmer response:

None.

ICE601I

DFSORT ICETOOL UTILITY RUN ENDED – RETURN CODE: nn

Explanation:

Indicates the end of the ICETOOL run and the highest return code encountered. Message ICE602I gives the return code for each operation.

System action:

None.

Programmer response:

None if nn is 00. Otherwise, check the ICE602I messages for non-zero return codes and take the action indicated.

ICE602I

OPERATION RETURN CODE: nn

Explanation:

Indicates the return code for this operation.

System action:

If nn is greater than 04, this operation was terminated due to an error.

Programmer response:

None if nn is 00, or if nn is 04 and message ICE651I was issued. Otherwise:

  • If nn is 04, match the identifier in message ICE606I or ICE627I for this operation to the same identifier in DFSORT message ICE200I (in the DFSMSG data set) to find the set of DFSORT messages for this operation. If appropriate, correct the condition that caused the return code of 4 indicated in the relevant DFSORT informational message.
  • If nn is 12, check the error messages for this operation in the TOOLMSG data set and correct the indicated errors.
  • If nn is 16, match the identifier in message ICE606I or ICE627I for this operation to the same identifier in DFSORT message ICE200I (in the DFSMSG data set) to find the set of DFSORT messages for this operation. Correct the error indicated in the DFSORT error message.

ICE603I

INFORMATION PRINTED IN ddname DATA SET

Explanation:

The information requested for this operator was printed in the list data set with the indicated ddname. If the operation was terminated, the list data set can be incomplete.

System action:

None.

Programmer response:

None.

ICE604A

ERROR IN KEYWORD, PARAMETER, OR DELIMITER

Explanation:

Critical. The statement contained an error in an operand (keyword, parameter) or a delimiter was incorrect or missing. Some common errors are:

  • A keyword or parameter was misspelled. Example: ALLDUP instead of ALLDUPS
  • A keyword was used with an operator for which it is not valid. Example: NOSIGN was used with an operator other than VERIFY.
  • A parameter or value was used with a keyword for which it is not valid. Example: VSAMTYPE(U) instead of VSAMTYPE(F) or VSAMTYPE(V).
  • The cccc value for USING(cccc) was SYSc or was not four characters. Example: USING(ABC) instead of USING(ABCD) or USING(SYS1) instead of USING(SYX1).
  • A left or right parenthesis was missing. Example: FROM IN instead of FROM(IN)
  • A blank was used inside a parentheses. Example:

    FROM( IN) instead of FROM(IN)

  • A continuation indicator (-) was used incorrectly. Example: TO(OUT1,- instead of TO(OUT1,OUT2) –
  • Parameters were not separated by a comma or semicolon. Example: ON(3:5:ZD) instead of ON(3,5,ZD) or ON(3;5;ZD)
  • A numeric value was specified incorrectly. Example: ON(0,3,ZD) instead of ON(1,3,ZD) or LIMIT(+1) instead of LIMIT(1)
  • An operand that can be specified only once per operator was specified more than once. Example: COPY TO(OUT1) TO(OUT2) instead of COPY TO(OUT1,OUT2)
  • Mutually exclusive operands were used. Example: BLANK and PLUS for DISPLAY or WITHEACH and VLENOVLY for SPLICE.
  • A numeric value was too low or too high. Example: LINES(9) or LINES(1000)
  • A string was not enclosed in apostrophes. Example: HEADER(Revenue), HEADER(‘Revenue), HEADER(‘Revenue”), or HEADER(“Revenue”)instead of HEADER(‘Revenue’)
  • A string exceeded the character limit allowed. Example:

    TITLE(‘This string is longer
    than the limit of 50 characters
    for TITLE’)

    Note:

    In your ICETOOL statement, the entire operand must be on one line.

  • A parameter was specified incorrectly. Example: DATE(DMY) instead of DATE(DMY.)
  • NOHEADER was used when HEADER(NONE) was required. Example: HEADER(‘Name’) NOHEADER instead of HEADER(‘Name’) HEADER(NONE)
  • Mutually exclusive items were specified within an operand. Example: DATE(YM4/) instead of DATE(YMD/) or DATE(DM4/)
  • A formatting item was specified for an operator other than DISPLAY or OCCUR. Example:

    SELECT ON(1,5,ZD,A1) instead of
    SELECT ON(1,5,ZD)

  • A symbol was specified where it is not allowed. Example: LINES(Max_Lines) instead of LINES(50)
  • Too many 9’s were specified in the pattern for E’pattern’. Example:

    ON(VALCNT,E’999-999-999-999-999-9′) instead of ON(VALCNT,E’99-999-999-999-999-9′)

  • Too many characters were specified in the pattern for E’pattern’. Example:

    ON(VALCNT,E’*999**999**999**999**999*’) instead of ON(VALCNT,E’999**999**999**999**999*’)

  • A required parameter was missing. Example: ON(25,5) instead of ON(25,5,ZD)
  • A parameter was specified where it isn’t allowed. Example: WITH(25,5,ZD) instead of WITH(25,5)

System action:

This operation is terminated.

Programmer response:

A $ marks the point at which the error was detected. Correct the error.

ICE605A

REQUIRED DD STATEMENT NOT FOUND: ddname

Explanation:

Critical. A DD statement for the indicated ddname was not present. The ddname was required because:

  • It was DFSMSG.
  • It was TOOLIN and the ICETOOL Parameter List Interface was not used.
  • It was specified in the FROM, TO, LIST, or DISCARD operand for this operator.
  • USING(xxxx) was specified for this operator.

System action:

If the ddname was TOOLIN or DFSMSG, ICETOOL terminates without performing any operations. Otherwise, this operation is terminated.

Programmer response:

Supply a DD statement for the indicated ddname.

ICE606I

|DFSORT CALL nnnn FOR {COPY|SORT|MERGE} |FROM {ddname1|JKFROM|MERGEIN} TO {ddname2|E35 |EXIT|OUTFIL} USING xxxxCNTL {COMPLETED|TERMINATED}

Explanation:

Supplies information about a specific call to DFSORT for this operation as follows:

nnnn

The call identifier for this call to DFSORT. You can match nnnn to the same nnnn in DFSORT message ICE200I in the DFSMSG data set to find the set of DFSORT messages for this call to DFSORT.

COPY

The DFSORT copy function was used.

SORT

The DFSORT sort function was used.

|MERGE

|The DFSORT merge function was used.

ddname1

The ddname of the data set that was copied or sorted.

|JKFROM

|A JOINKEYS application was used.

|MERGEIN

|A MERGE operator was used

ddname2

|The ddname of the data set resulting from the |copy, sort or merge.

E35 EXIT

ICETOOL’s E35 user exit was used.

OUTFIL

Either OUTFIL data sets were produced or an E35 user exit routine was used to dispose of all the output records

xxxxCNTL

|The ddname of the DFSORT control data set used |for the copy, sort or merge.

COMPLETED

DFSORT did not detect any errors preventing completion of this ICETOOL operation.

TERMINATED

DFSORT detected an error which prevented completion of this ICETOOL operation.

System action:

None.

Programmer response:

You can use the information in this message to determine the result of this call to DFSORT. If DFSORT terminated, use the call identifier to find the set of DFSORT messages for this call (in the DFSMSG data set), and correct the error indicated in the DFSORT error message.

ICE607I

STATISTICS FOR {(p,m,f)|(VLEN)}:

Explanation:

Indicates the field to which the statistics in subsequent messages ICE608I, ICE609I, and ICE648I apply. (p,m,f) or (VLEN) is a field you specified for this STATS operator.

System action:

None.

Programmer response:

None.

ICE608I

MINIMUM: snnnnnnnnnnnnnnn, MAXIMUM: snnnnnnnnnnnnnnn

Explanation:

Indicates the minimum and maximum for the field indicated in the ICE607I message preceding this message. Each value consists of a + or – sign and 15 decimal digits (padded with zeros on the left as needed). If the values could not be determined due to an error (as indicated in a previous message), asterisks were printed for the values.

Note:

ICE648I messages are printed for the minimum and maximum values (instead of ICE608I) if either value contains more than 15 significant digits, or if LMSG is specified.

System action:

None.

Programmer response:

None unless asterisks were printed for the values, in which case you should correct the error indicated by the previous error message for this operation.

If you want all of the minimum and maximum values displayed with 31 digits, specify the LMSG keyword for this STATS operator.

ICE609I

AVERAGE: snnnnnnnnnnnnnnn, TOTAL:  snnnnnnnnnnnnnnn

Explanation:

Indicates the average and total for the field indicated in the ICE607I message preceding this message. Each value consists of a + or – sign and 15 decimal digits (padded with zeros on the left as needed). If a value could not be determined due to an error (as indicated in a previous message), asterisks were printed for the value.

Note:

ICE648I messages are printed for the average and total values (instead of ICE609I) if either value contains more than 15 significant digits, or if LMSG is specified.

System action:

None.

Programmer response:

None unless asterisks were printed for a value, in which case you should correct the error indicated by the previous error message for this operation.

If you want all of the average and total values displayed with 31 digits, specify the LMSG keyword for this STATS operator.

ICE610I

NUMBER OF UNIQUE VALUES FOR (p,m,f)|(VLEN)}: nnnnnnnnnnnnnnn

Explanation:

Indicates the count of unique values for this field, printed as 15 decimal digits (padded with zeros on the left as needed). (p,m,f) or (VLEN) is the field you specified for this UNIQUE operator.

System action:

None.

Programmer response:

None.

ICE611A

TOTAL FOR {(p,m,f)|(VLEN)} OVERFLOWED nn DECIMAL DIGITS

Explanation:

Critical. The total for the indicated ON(p,m,f) or ON(VLEN) field (STATS or DISPLAY) exceeded the number of digits (nn) allowed for it. nn is 31 for STATS, or 15 or 31 for DISPLAY, depending on the number of digits allowed for the total.

System action:

This operation is terminated.

For a STATS operator, asterisks are printed in ICE648I messages for the average and total for this field.

For a DISPLAY operator, asterisks are printed for this field in any BAVERAGE, BTOTAL, AVERAGE, or TOTAL lines requested.

Programmer response:

If nn is 15, specify an Ndd or Udd formatting item large enough to prevent overflow of the total (that is, use an appropriate Ndd or Udd value between 16 and 31).

If nn is 31 and you need the average or total for this field, use the STATS or DISPLAY operator for subsets of the data set that do not cause the total to overflow. Use the statistics for the subsets to determine the needed statistics for the field.

ICE612I

NO ERRORS FOUND IN STATEMENT

Explanation:

Printed in SCAN mode to indicate that no errors were found in the statement.

System action:

DFSORT is not called in SCAN mode.

Programmer response:

If SCAN mode was entered due to an error while in STOP mode, correct the error. If SCAN mode was entered due to a MODE SCAN statement, replace it with a MODE STOP or MODE CONTINUE statement.

ICE613A

REQUIRED KEYWORD MISSING: keyword

Explanation:

Critical. The indicated keyword was required for this operator, but was not specified. The required keywords and their operands for each operator are:

  • COPY
    • |FROM, or JKFROM and USING
    • TO or USING
  • COUNT
    • FROM
    • EMPTY, NOTEMPTY, HIGHER, LOWER, EQUAL, or NOTEQUAL if RC4 is specified
    • WRITE if TEXT, DIGITS, EDCOUNT, or WIDTH is specified
  • DATASORT
    • FROM, TO, and USING
    • HEADER or TRAILER
  • DEFAULTS
    • LIST
  • DISPLAY
    • FROM, ON, and LIST
    • BREAK if BTITLE, BTOTAL, BMAXIMUM, BMINIMUM, BAVERAGE, or BCOUNT is specified
    • COUNT if EDCOUNT is specified
    • BCOUNT if EDBCOUNT is specified
  • |MERGE |

    |

    • FROM and USING
  • MODE
    • STOP, CONTINUE, or SCAN
  • OCCUR
    • FROM and LIST
    • ON(p,m,f), ON(p,m,HEX), or ON(VLEN)
  • RANGE
    • FROM and ON
    • HIGHER, LOWER, EQUAL, or NOTEQUAL
  • SELECT
    • FROM and ON
    • TO or DISCARD
    • ALLDUPS, NODUPS, HIGHER, LOWER, EQUAL, FIRST, LAST, FIRSTDUP or LASTDUP
  • SORT
    • |FROM or JKFROM
    • |USING
  • SPLICE
    • FROM, TO, ON, and WITH
  • STATS
    • FROM and ON
  • SUBSET
    • FROM
    • TO or DISCARD
    • KEEP or REMOVE
    • INPUT or OUTPUT
  • UNIQUE
    • FROM and ON
  • VERIFY
    • FROM and ON

System action:

This operation is terminated.

Programmer response:

Supply the indicated keyword or operand.

ICE614A

INVALID OPERATOR

Explanation:

Critical. The first keyword in the statement was not a valid operator. The valid operators are: COPY, COUNT, DATASORT, DEFAULTS, DISPLAY, |MERGE, MODE, OCCUR (or OCCURS), RANGE, SELECT, SORT, SPLICE, STATS, SUBSET, UNIQUE, and VERIFY.

A common cause of this error is a missing hyphen (-) on the previous line to indicate continuation.

System action:

This operation is terminated.

Programmer response:

A $ marks the point at which the error was detected. If an invalid operator was used, replace it with a valid operator. If this is a continuation line, use a hyphen after the last operand on the previous line.

ICE615A

DDNAME USED MORE THAN ONCE: ddname

Explanation:

Critical. This message was issued for one of the following reasons:

  • TOOLIN, TOOLMSG, DFSMSG, or SSMSG was used as a ddname in a FROM, TO, LIST, or DISCARD operand for this operator.
  • The indicated ddname was found more than once in a FROM, TO, LIST, or DISCARD operand for this operator.
  • USING(xxxx) was specified and xxxxCNTL was used in a FROM or TO operand for this operator.

System action:

This operation is terminated.

Programmer response:

A $ marks the duplicate ddname. Replace it with a ddname that is unique for this operation and that is not TOOLIN, TOOLMSG, DFSMSG, or SSMSG.

ICE616A

STATEMENT DOES NOT END AT OR BEFORE COLUMN 72

Explanation:

Critical. The statement overran column 72, or a string contained unmatched quotes.

System action:

This operation is terminated.

Programmer response:

Recode the statement to end at or before column 72. Continuation can be indicated by a hyphen (-) after the operator or any operand. For example:

SORT FROM(INDD) –

USING(ABCD) –

TO(OUTPUT1,OUTPUT2,OUTPUT3)

Ensure that all quotes are matched as this message can also result from unmatched quotes in a string, for example, TITLE(‘Status Report).

ICE617A

RECORD COUNT OVERFLOWED 15 DECIMAL DIGITS

Explanation:

Critical. The number of records processed by ICETOOL for this operation was greater than 999999999999999.

System action:

This operation is terminated.

Programmer response:

Perform the operation on subsets of the data set containing less than 999999999999999 records.

ICE618A

INVALID (p,m,f) VALUE – RECORD: nnnnnnnnnnnnnnn

Explanation:

Critical. ICE618A and ICE649A identify an invalid decimal value in a specified field. One of the following was found:

  • An invalid digit (A-F) in a field specified for a DISPLAY, OCCUR, RANGE, STATS, or VERIFY operator.
  • An invalid sign (0-9) in a field specified for a VERIFY operator (NOSIGN was not specified).

(p,m,f) is a field you specified for this operator.

The invalid value was found in record number nnnnnnnnnnnnnnn (prints as 15 decimal digits padded with zeros on the left as needed). For a DISPLAY, RANGE, STATS, or VERIFY operator, nnnnnnnnnnnnnnn is the input record number (that is, the relative record number). For an OCCUR operator, nnnnnnnnnnnnnnn is the sorted record number, and thus may not be useful.

h…h in the ICE649A message that follows this ICE618A message is the invalid value in hexadecimal.

System action:

  • For a DISPLAY operator with an invalid BREAK value, this operation is terminated.
  • For a DISPLAY operator with an invalid ON value, asterisks are printed for this value in the data line and in any statistics lines requested. If this incorrect value causes the limit for decimal values to be reached, this operation is terminated after the current record is printed in the list data set. Otherwise, processing continues.
  • For an OCCUR or RANGE operator, this operation is terminated.
  • For a STATS operator, asterisks were printed in messages ICE608I, ICE609I or ICE648I for minimum, maximum, average, and total for this field.
  • For a VERIFY operator, if this bad value caused the limit for invalid decimal values to be reached, this operation is terminated. Otherwise, processing continues.

Programmer response:

Correct the invalid digit or sign in the identified field. The VERIFY or DISPLAY operator can be used to print all the invalid values and their relative record numbers.

ICE619A

INVALID LENGTH, FORMAT, OR COMBINATION FOR operator OPERATION

Explanation:

Critical. One of the following conditions was detected in the parameters of an ON or BREAK operand:

  • The format was invalid. Example: ON(10,2,CST) or BREAK(10,2,FL)
  • The format was not allowed for this operator. Example: VERIFY ON(10,2,BI)
  • The length was not within the range allowed for the format and operator. Example: STATS ON(10,9,BI)
  • ON(VLEN) was specified for a VERIFY operator. Example: VERIFY ON(VLEN)
  • ON(NUM) was specified for an operator other than DISPLAY. Example: STATS ON(NUM)
  • ON(VALCNT) was specified for an operator other than OCCUR. Example: DISPLAY ON(VALCNT)
  • ON(p,m,HEX) was specified for an operator other than DISPLAY or OCCUR. Example: UNIQUE ON(5,4,HEX)
  • The length was not within the range allowed for ON(p,m,HEX). Example: ON(5,1001,HEX)
  • BREAK(p,m,HEX) was specified. Example: BREAK(5,4,HEX)

System action:

This operation is terminated.

Programmer response:

A $ marks the point at which the error was detected. Correct the error.

ICE620A

SUM OF POSITION AND LENGTH GREATER THAN max

Explanation:

Critical. A specified field extended beyond the maximum position (max – 1) allowed for this operation.

System action:

This operation is terminated.

Programmer response:

A $ marks the point at which the error was detected. Change the position or length so that the field ends at or before position max – 1.

ICE621I

DFSORT DETECTED AN ERROR AFTER E35 EXIT PROCESSING COMPLETED

Explanation:

A call to DFSORT for this operation resulted in a return code of 16. However, because the error was detected by DFSORT after ICETOOL’s E35 user exit completed its processing, the error did not prevent the completion of this ICETOOL operation.

System action:

None.

Programmer response:

None required, but you can examine the DFSORT messages in DFSMSG to determine the error detected by DFSORT and correct it if appropriate.

ICE622A

EXPECTED CONTINUATION LINE NOT FOUND

Explanation:

Critical. This message was issued for one of the following reasons:

  • Continuation was indicated by a hyphen (-) after the last operand in the last line of the TOOLIN data set, but the continuation line was not found.
  • A parameter list statement area did not contain an operator statement.
  • Continuation was indicated by a hyphen (-) in the last line of a parameter list statement area, but the continuation line was not found.

System action:

This operation is terminated.

Programmer response:

Supply the continuation line.

ICE623A

MAXIMUM NUMBER OF keyword KEYWORDS EXCEEDED

Explanation:

Critical. Too many keywords of the indicated type were specified for this operator.

The maximum number of HEADER fields is 20 for a DISPLAY operator or 10 for an OCCUR operator.

The maximum number of WITH operands is 50 for a SPLICE operator.

The maximum number of TITLE operands is 3 for a DISPLAY or OCCUR operator.

The maximum number of RRN operands is 300 for a SUBSET operator.

|The maximum number of FROM operands is 10 for a MERGE |operator

The maximum number of ON fields for each operator is:

  • DISPLAY – 20
  • OCCUR – 10
  • RANGE – 1
  • SELECT – 10
  • SPLICE – 10
  • STATS – 10
  • UNIQUE – 1
  • VERIFY – 10

System action:

This operation is terminated.

Programmer response:

A $ marks the point at which the error was detected. Reduce the number of indicated keywords for this operator to the maximum allowed. If necessary, use additional operators to handle all the required fields.

ICE624A

MAXIMUM NUMBER OF TO DDNAMES EXCEEDED

Explanation:

Critical. Too many TO ddnames were specified for this operator. The maximum number of TO ddnames for each operator is:

  • COPY – 10
  • DATASORT – 1
  • |MERGE – 10
  • SELECT – 1
  • SORT – 10
  • SPLICE – 1
  • SUBSET – 1

System action:

This operation is terminated.

Programmer response:

A $ marks the point at which the error was detected. Reduce the number of TO ddnames for this operator to the maximum allowed. Use additional operators to handle all the data sets required.

ICE625A

OPEN FAILED FOR ddname DATA SET

Explanation:

Critical. The data set with the indicated ddname could not be opened. This occurred either for the data set specified for TOOLIN, SYMNAMES or SYMNOUT, or for the data set whose ddname was specified in the LIST operand for this operator.

System action:

If the ddname is TOOLIN, SYMNAMES, or SYMNOUT, ICETOOL terminates without performing any operations. Otherwise, this operation is terminated.

Programmer response:

Ensure that the attributes of the data set (record format, record length, block size) conform to the rules for that type of data set. See the ICETOOL chapter (TOOLIN or LIST operand data set) or Symbols chapter (SYMNAMES or SYMNOUT) in z/OS DFSORT Application Programming Guide for information on the rules.

ICE626A

LIMIT FOR INVALID VALUES REACHED

Explanation:

Critical. The limit for the number of invalid decimal values specified by the LIMIT operand (or defaulted to 200) was reached for this DISPLAY or VERIFY operator.

System action:

This operation is terminated.

Programmer response:

Correct the invalid decimal values indicated in the ICE618A and ICE649A messages, or set a higher LIMIT value.

ICE627I

DFSORT CALL nnnn FOR {COPY|SORT} FROM ddname1 TO {ddname2|E35 EXIT|OUTFIL} {COMPLETED|TERMINATED}

Explanation:

Supplies information about a specific call to DFSORT for this operation as follows:

nnnn

The call identifier for this call to DFSORT. You can match nnnn to the same nnnn in DFSORT message ICE200I in the DFSMSG data set to find the set of DFSORT messages for this call to DFSORT.

COPY

The DFSORT copy function was used.

SORT

The DFSORT sort function was used.

ddname1

The ddname of the data set that was copied or sorted.

ddname2

The ddname of the data set resulting from the copy or sort.

E35 EXIT

ICETOOL’s E35 user exit was used.

OUTFIL

OUTFIL data sets were produced

COMPLETED

DFSORT did not detect any errors preventing completion of this ICETOOL operation.

TERMINATED

DFSORT detected an error which prevented completion of this ICETOOL operation.

System action:

None.

Programmer response:

You can use the information in this message to determine the result of this call to DFSORT. If DFSORT terminated, use the call identifier to find the set of DFSORT messages for this call (in the DFSMSG data set), and correct the error indicated in the DFSORT error message.

ICE628I

RECORD COUNT: nnnnnnnnnnnnnnn

Explanation:

Indicates the number of records processed by ICETOOL (prints as 15 decimal digits padded with zeros on the left as needed).

If ICETOOL completed the operation successfully, this count reflects the number of records in the input data set or in the subset of the input data set selected by DFSORT statements (for example, INCLUDE). If an ADD operand was specified for a COUNT operator, the count will reflect addition of the specified value. If a SUB operand was specified for a COUNT operator, the count will reflect subtraction of the specified value, but will not be reduced below 0.

If ICETOOL did not complete the operation successfully, this count reflects the number of records processed before an error was detected that caused ICETOOL to terminate processing of this operation.

System action:

None.

Programmer response:

None.

ICE629A

HIGHER AND LOWER VALUES EXCLUDE ALL RECORDS

Explanation:

Critical. The values specified for HIGHER and LOWER excluded all records from the range. For example, HIGHER(5) and LOWER(6) define a range of 5 < value < 6, which excludes every value.

System action:

This operation is terminated.

Programmer response:

A $ marks the point at which the error was detected. Specify values for HIGHER and LOWER that define a valid range.

ICE630I

MODE IN EFFECT: mode

Explanation:

Indicates the processing mode to be used for subsequent operators as follows:

  • STOP mode – set at the beginning of the run and when a MODE STOP statement is processed. Stops subsequent operations if an error is detected (by entering SCAN mode).
  • CONTINUE mode – set when a MODE CONTINUE statement is processed. Continues with subsequent operations if an error is detected.
  • SCAN mode – set when an error is encountered in STOP mode and when a MODE SCAN statement is processed. ICETOOL statements are checked for errors, but DFSORT is not called to perform the operations.

System action:

None.

Programmer response:

If SCAN mode was set due to an error while in STOP mode, correct the error.

ICE631I

NUMBER OF VALUES IN RANGE FOR {(p,m,f)|(VLEN)}: nnnnnnnnnnnnnnn

Explanation:

Indicates the count of values within the specified range for this field (prints as 15 decimal digits padded with zeros on the left as needed). (p,m,f) or (VLEN) is the field you specified for this RANGE operator.

System action:

None.

Programmer response:

None.

ICE632I

SOURCE FOR ICETOOL STATEMENTS: source

Explanation:

Indicates whether ICETOOL statements were processed from TOOLIN or from the calling program’s PARMLIST (parameter list). Statements are processed from TOOLIN unless the ICETOOL Parameter List Interface is used.

System action:

None.

Programmer response:

None.

ICE633A

RETURN AREA IS n BYTES, BUT m BYTES ARE REQUIRED

Explanation:

The length of the return area (in bytes) as indicated in the calling program’s parameter list was too small to contain all of the information to be returned for this operation. A return area of m bytes is needed.

System action:

This operation is terminated.

Programmer response:

Provide a return area of m bytes (or more) for this operation and set the return area length appropriately.

ICE634A

VALUE FOR (p,m,f) EXCEEDS 31 DIGITS

Explanation:

Critical. A value for the indicated FS or CSF field had 32 digits, or a value for the indicated UFF or SFF field had 32 or more digits, exceeding the limit of 31 digits.

System action:

This operation is terminated.

Programmer response:

Limit all FS, CSF, UFF, and SFF data values for this operation to 31 digits. The DISPLAY operator with CH format can be used to visually identify the values with 32 digits.

ICE635A

NUMBER OF HEADER KEYWORDS DOES NOT MATCH NUMBER OF ON KEYWORDS

Explanation:

Critical. There was not a one-to-one correspondence between the HEADER keywords and the ON keywords. For example, two HEADER keywords were specified with three ON keywords.

System action:

This operation is terminated.

Programmer response:

Specify one HEADER(‘string’) or HEADER(NONE) keyword for each ON keyword.

ICE636A

INVALID VALUE IN DFSORT ICEyyy INSTALLATION ENVIRONMENT

Explanation:

Critical. A value in the indicated DFSORT installation environment (ICEyyy) could not be interpreted by ICETOOL. This indicates an installation problem. Any or all of the values printed can be incorrect.

Note:

ICETOOL cannot detect all possible invalid values in the ICEyyy environment; it only prints this message for the first invalid value it detects.

System action:

‘> > INVALID < <‘ is printed in the list data set for the invalid value, and all subsequent processing for this operator is terminated.

Programmer response:

Have your system programmer check that the ICEMAC macro and the DFSORT modules (especially ICEPRML, ICETOOL and ICEMCDU) were installed correctly and that the ICEMAC installation modules (ICEAM1, ICEAM2, ICEAM3, ICEAM4, ICETD1, ICDTD2, ICETD3, and ICETD4) were generated correctly and are at the same level as the DFSORT modules.

ICE637A

ddname RECORD LENGTH OF n BYTES EXCEEDS MAXIMUM WIDTH OF m BYTES

Explanation:

Critical.

  • For a DISPLAY or OCCUR operator without NOCC:

    The calculated record length for the indicated list data set was greater than 2048 or the maximum width specified. n is the total bytes required in the list data set record for the carriage control character, the title lines (resulting from specified title elements), column widths (resulting from specified ON, HEADER, PLUS, BLANK, TOTAL, BREAK, BTITLE, and BTOTAL operands), and blanks before and between title elements and columns (resulting from specified INDENT, TBETWEEN, BETWEEN, and STATLEFT operands). m is the value specified for the WIDTH operand, or 2048 if WIDTH was not specified.

  • For a DISPLAY or OCCUR operator with NOCC:

    The calculated record length for the indicated list data set was greater than 2047 or the maximum width specified. n is the total bytes required in the list data set record for the title lines (resulting from specified title elements), column widths (resulting from specified ON, HEADER, PLUS, BLANK, TOTAL, BREAK, BTITLE, and BTOTAL operands), and blanks before and between title elements and columns (resulting from specified INDENT, TBETWEEN, BETWEEN, and STATLEFT operands). m is the value specified for the WIDTH operand, or 2047 if WIDTH was not specified.

  • For a COUNT operator with WRITE:

    The calculated record length for the indicated output data set was greater than the maximum width specified. n is the total bytes required in the output data set record for the count line (resulting from specified TEXT, DIGITS and EDCOUNT operands). m is the value specified for the WIDTH operand.

System action:

This operation is terminated.

Programmer response:

  • For a DISPLAY or OCCUR operator:

    If m is less than 2048 without NOCC or less than 2047 with NOCC, either remove the WIDTH operand and let ICETOOL set the width, or if you need to set the WIDTH explicitly, increase its value to n or greater.

    If m is 2048 without NOCC or 2047 with NOCC, take one or more of the following actions:

    • Use formatting items or the PLUS or BLANK operand. For example, use ON(21,18,ZD,U19) instead of ON(21,18,ZD) with TOTAL to change the column width from 32 bytes to 20 bytes.
    • Reduce the length of one or more HEADER strings.
    • Reduce the length of one or more ON fields. For example, if an ON(1,8,PD) field always has zeros in bytes 1 through 3, use instead (1,8,PD,U09), or ON(4,5,PD) with BLANK, to reduce the column width from 16 bytes to 10 bytes.
    • Reduce the number of ON fields, especially if the BTOTAL or TOTAL operand is used.
    • Reduce BETWEEN(n).
    • Reduce INDENT(n).
    • Remove STATLEFT.
    • Reduce TBETWEEN(n).
  • For a COUNT operator, remove the WIDTH operand and let ICETOOL set the width, or if you need to set the WIDTH explicitly, increase its value to n or greater.

ICE638I

NUMBER OF RECORDS RESULTING FROM CRITERIA: nnnnnnnnnnnnnnn

Explanation:

Indicates the count of records produced as a result of the specified criteria, for example, ALLDUPS (prints as 15 decimal digits padded with zeros on the left as needed).

  • For an OCCUR operator, the count indicates the total number of records in the list data set.
  • For a SELECT or SPLICE operator, the count indicates the total number of records in the outdd data set.

System action:

None.

Programmer response:

None.

ICE639A

INSUFFICIENT MAIN STORAGE – ADD AT LEAST nK BYTES TO REGION

Explanation:

Critical. ICETOOL could not get the additional n KB of storage needed for this operation.

System action:

This operation is terminated.

Programmer response:

Increase the REGION by at least n KB. In some cases, more than n KB are required to meet all the storage requirements for ICETOOL and DFSORT for this operation.

ICE640A

INVALID FORMATTING ITEM

Explanation:

Critical. An ON(p,m,f,formatting), ON(VLEN,formatting), ON(NUM,formatting), EDCOUNT(formatting), or EDBCOUNT(formatting) operand for this DISPLAY operator, or an ON(p,m,f,formatting), ON(VLEN,formatting) or ON(VALCNT,formatting) operand for this OCCUR operator, or an EDCOUNT(formatting) operand for this COUNT operator, contained an invalid formatting item as follows:

  • The formatting item was not /x (/x can be /D, /C, /K, /DK, /CK, /M, /G, /KB, /MB, or /GB), L’string’, F’string’, T’string’, E’pattern’, NOST, LZ, Ndd, Udd, or a valid mask (mask can be A0-A5, B1-B6, C1-C6, D1-D6, E1-E4, F1-F5, or G1-G6).
  • /x, F’string’, E’pattern’, LZ, NOST, Ndd, Udd, or a mask was specified for a character field.
  • /x or NOST was specified for ON(NUM,formatting) or for OCCUR.
  • /x, NOST or Ndd was specified for BREAK(p,m,f,formatting), EDCOUNT(formatting), or EDBCOUNT(formatting).
  • More than one /x was specified, more than one mask was specified, Ndd and Udd were both specified, or L’string’, F’string’, T’string’, E’pattern’, Udd, or Ndd was specified more than once.
  • L”, F”, T” or E” was specified.
  • F’string’ or a mask was specified with E’pattern’.
  • dd for Ndd or Udd was not two digits from 01 to 31.
  • dd for Ndd or Udd was greater than 15 for ON(NUM,formatting) or ON(VALCNT,formatting).
  • dd for Udd was greater than 15 for EDCOUNT(formatting) or EDBCOUNT(formatting).

System action:

This operation is terminated.

Programmer response:

A $ marks the point at which the error was detected. Correct the error.

ICE641A

service SERVICE ERROR (xy)

Explanation:

Critical. The indicated system service failed when ICETOOL called it. Message values are as follows:

x

The return code from the service, in decimal.

y

The reason code from the service, in decimal, or zero if unavailable.

System action:

This operation is terminated.

Programmer response:

Contact IBM for programming support.

ICE642A

DFSORT RELEASE xxxx AND module RELEASE yyyy DO NOT MATCH

Explanation:

Critical. The release level (xxxx) of DFSORT does not match the release level (yyyy) of the indicated module. If the module is ‘ICEPRML’ , that module, which is used to process ICEPRMxx members in PARMLIB was not at the same release level as the DFSORT modules being used for the run. If the module is ‘ICEAM1’ , ‘ICEAM2’ , ‘ICEAM3’ , ‘ICEAM4’ , ‘ICETD1’ , ‘ICETD2’ , ‘ICETD3’ or ‘ICETD4’, the ICEMAC macro used to compile that installation module was not at the same release level as the DFSORT modules being used for the run.

Note:

This message is only printed for ICEPRML or for the first installation module with a release level that does not match the DFSORT release level.

System action:

This operation is terminated.

Programmer response:

Have your System Programmer ensure that the release level of the DFSORT modules matches the release level of the indicated ICEPRML or installation module.

ICE643I

WIDTH OF REPORT IS n BYTES

Explanation:

n indicates the line length and the LRECL for this DISPLAY or OCCUR list data set, determined as follows:

  • n if WIDTH(n) was specified
  • 121 if NOCC and WIDTH(n) were not specified and the calculated line length was less than or equal to 121
  • the calculated line length if NOCC and WIDTH(n) were not specified and the calculated line length was greater than 121
  • 120 if NOCC was specified, WIDTH(n) was not specified, and the calculated line length was less than or equal to 120
  • the calculated line length if NOCC was specified, WIDTH(n) was not specified, and the calculated line length was greater than 120.

System action:

None.

Programmer response:

None.

ICE644A

{VALUE|TOTAL} FOR {(p,m,f)|(VLEN)} OVERFLOWED n DECIMAL DIGITS

Explanation:

Critical. A value for the indicated ON(p,m,f) or ON(VLEN) field (DISPLAY or OCCUR) or BREAK(p,m,f) field (DISPLAY), or the total for the indicated ON(p,m,f) field, exceeded the number of digits (n) you allowed for it. n is the number of digits allowed for the value or total as determined from the length and format of the field, or the Ndd or Udd formatting item you specified.

System action:

  • For a DISPLAY operator with an overflowing BREAK value, this operation is terminated.
  • For a DISPLAY operator with an overflowing ON value, asterisks are printed for this value in the data line and in any statistics lines requested. Processing continues.
  • For a DISPLAY operator with an overflowing total, asterisks are printed for the total. Processing continues.
  • For an OCCUR operator with an overflowing ON value, this operation is terminated.

Programmer response:

Specify an Ndd or Udd formatting item large enough to prevent overflow of the value or total (that is, use an appropriate Ndd or Udd value between n+1 and 31).

ICE645A

{(NUM)|(VALCNT)|COUNT} OVERFLOWED n DECIMAL DIGITS

Explanation:

Critical. The number of digits (n) allowed from the Ndd, Udd , or DIGITS(n) item you specified was too small, as follows:

  • (NUM) indicates a record number for this DISPLAY operator exceeded the number of digits you allowed for it.
  • (VALCNT) indicates a value count for this OCCUR operator exceeded the number of digits you allowed for it.
  • COUNT indicates a count for this COUNT operator, or an overall count or break count for this DISPLAY operator, exceeded the number of digits you allowed for it.

System action:

This operation is terminated.

Programmer response:

Specify an Ndd or Udd formatting item, or a DIGITS(n) operand, large enough to prevent overflow of the record number, value count, overall count or break count (that is, use an appropriate Ndd, Udd, or DIGITS value between n+1 and 15).

ICE646A

RECORD COUNT MEETS CRITERIA – RC=12 SET

Explanation:

Critical. EMPTY, NOTEMPTY, HIGHER(n), LOWER(n), EQUAL(n), or NOTEQUAL(n) was specified for this COUNT operator. Because the record count met the specified criteria, RC=12 was set for this COUNT operation.

System action:

The operation is terminated.

Programmer response:

None.

ICE647I

RECORD COUNT DOES NOT MEET CRITERIA – RC=0 SET

Explanation:

EMPTY, NOTEMPTY, HIGHER(n), LOWER(n), EQUAL(n), or NOTEQUAL(n) was specified for this COUNT operator. Because the record count did not meet the specified criteria, RC=0 was set for this COUNT operation.

System action:

None.

Programmer response:

None.

ICE648I

statistic: snnnnnnnnnnnnnnnnnnnnnnnnnnnnnnn

Explanation:

Indicates the minimum, maximum, average or total for the field indicated in the ICE607I message preceding this message. statistic is MINIMUM, MAXIMUM, AVERAGE or TOTAL. Each value consists of a + or – sign and 31 decimal digits (padded with zeros on the left as needed).

Note:

An ICE608I message is printed for the minimum and maximum values (instead of ICE648I messages) if both values contain less than 16 significant digits, unless LMSG is specified. An ICE609I message is printed for the average and total values (instead of ICE648I messages) if both values contain less than 16 significant digits, unless LMSG is specified.

System action:

None.

Programmer response:

None unless asterisks were printed for the AVERAGE and TOTAL values, in which case you should correct the error indicated by the previous error message for this operation.

If you want all of the minimum, maximum, average and total values displayed with 31 digits, specify the LMSG keyword for this STATS operator.

ICE649A

HEX VALUE: h…h

Explanation:

Critical. Displays the invalid value associated with preceding message ICE618A. h…h is the invalid value in hexadecimal. See the Explanation of message ICE618A for details

System action:

See the System Action of message ICE618A for details.

Programmer response:

See the Programmer Response of message ICE618A for details.

ICE650I

VISIT http://www.ibm.com/storage/dfsort FOR ICETOOL PAPERS, EXAMPLES AND MORE

Explanation:

The DFSORT website at http://www.ibm.com/storage/dfsort is an important source of information about DFSORT’s ICETOOL utility. It contains papers, examples, online documents, news, tips, techniques and more that can help you get the most out of ICETOOL.

System action:

None.

Programmer response:

Optional. Visit the DFSORT website to see what it has to offer.

ICE651I

RECORD COUNT MEETS CRITERIA – RC=4 SET

Explanation:

RC4 and EMPTY, NOTEMPTY, HIGHER(n), LOWER(n), EQUAL(n), or NOTEQUAL(n) was specified for this COUNT operator. Because the record count met the specified criteria, RC=4 was set for this COUNT operation.

System action:

Processing continues and ICETOOL passes back a return code of 4 unless it sets a higher return code for some other reason.

Programmer response:

None.

ICE652A

OUTREC STATEMENT FOUND BUT NOT ALLOWED – USE OUTFIL STATEMENT INSTEAD

Explanation:

Critical. A DFSORT OUTREC statement was specified for this DATASORT, SELECT, SPLICE, or SUBSET operator, but you cannot use an OUTREC statement with DATASORT, SELECT, SPLICE, or SUBSET.

System action:

The operation is terminated.

Programmer response:

If you want to reformat the output records produced by this DATASORT, SELECT, SPLICE, or SUBSET operator, use one or more OUTFIL statements as explained in z/OS DFSORT Application Programming Guide, instead of an OUTREC statement.

ICE653A

STOPAFT, SKIPREC OR COND (SUBSET) OR STOPAFT (DATASORT) NOT ALLOWED

Explanation:

Critical. Either:

  • a SUBSET operator was used and a DFSORT SKIPREC, STOPAFT or COND operand was specified, or
  • a DATASORT operator was used and a DFSORT STOPAFT operand was specified.

You cannot use STOPAFT with SUBSET or DATASORT. You cannot use SKIPREC or COND with SUBSET.

System action:

The operation is terminated.

Programmer response:

If appropriate, use an OUTFIL statement with INCLUDE, OMIT, STARTREC, ENDREC or other operands to remove unwanted records after they are processed by SUBSET or DATASORT.

ICE654A

SORT FUNCTION IS REQUIRED FOR DATASORT OPERATION

Explanation:

Critical. A DFSORT SORT statement was not found for this DATASORT operator, but you must supply a SORT statement with DATASORT.

System action:

The operation is terminated.

Programmer response:

Specify a SORT statement in the xxxxCNTL data set corresponding to the USING(xxxx) operand for this DATASORT operator. Ensure that the SORT statement is not overridden by an OPTION COPY statement.

ICE655I

COUNT RECORD WRITTEN IN ddname DATA SET – LENGTH IS n BYTES

Explanation:

The record containing the count was written in the output data set with the indicated ddname. n indicates the record length and the LRECL for the output data set, determined as follows:

  • n if WIDTH(n) was specified
  • the calculated length of the count record if WIDTH(n) was not specified.

System action:

None.

Programmer response:

None.

ICE656A

DISCARD AND INPUT CANNOT BE USED WITH SORT FUNCTION FOR SUBSET OPERATION

Explanation:

Critical. A DFSORT SORT statement was found for a SUBSET operator with DISCARD(savedd) and INPUT operands, but you cannot use a SORT statement with these SUBSET operands.

System action:

This operation is terminated.

Programmer response:

Remove the SORT statement or DISCARD(savedd) operand, or change the INPUT operand to an OUTPUT operand, as appropriate. Alternatively, use two SUBSET operators, one with REMOVE and INPUT operands, a SORT statement, and no DISCARD(savedd) operand, and the other with KEEP and INPUT operands, a SORT statement, and no DISCARD(savedd) operand.

|

ICE657A

TOO MANY FROM DDNAMES FOR MERGE

|

Explanation:

|

Critical. The maximum of 50 FROM ddnames was exceeded for this |MERGE operation.

|

System action:

|

This operation is terminated.

|

Programmer response:

|

A $ marks the point at which the error was detected. Reduce the |number of FROM ddnames for this MERGE operator to 50 or less. Use |additional MERGE operators to handle all of the data sets required.

|

ICE658A

MERGE FUNCTION IS REQUIRED FOR MERGE OPERATION

|

Explanation:

|

Critical. A DFSORT MERGE statement was not found for this MERGE |operator, but you must supply a MERGE statement with a MERGE operator

|

System action:

|

This operation is terminated.

|

Programmer response:

|

Specify a MERGE statement in the xxxxCNTL data set corresponding |to the USING(xxxx) operand for this MERGE operator. Ensure that the |MERGE statement is not overridden by a SORT statement, an OPTION COPY |statement, or a MERGE FIELDS=COPY statement.

ICE700A

EFS PROCESSING IS NOT SUPPORTED FOR THE TECHNIQUE SELECTED

Explanation:

Critical. EFS processing is not supported for the technique selected (tape work data set sort or Conventional merge).

System action:

The program terminates.

Programmer response:

Rerun the job with SORTDIAG DD statement to get the reason for the revert from message ICE800I. Remove the cause of the revert or do not use EFS processing by specifying EFS=NONE.

ICE701A

EFS PROCESSING WAS TERMINATED BY pppppppp AT MAJOR CALL n

Explanation:

Critical. Termination of the DFSORT run was requested by EFS program pppppppp at Major Call 1, 2, 3, 4, or 5.

System action:

If the termination was requested at Major Call 1, the program terminates. If the termination was requested at Major Call 2 through 5, DFSORT scans all remaining control statements and then the program terminates.

Programmer response:

Refer to the message issued by EFS program pppppppp for the error description.

ICE702A

INVALID RETURN CODE FROM EFS PROGRAM pppppppp AT MAJOR CALL n

Explanation:

Critical. EFS program pppppppp returned an invalid return code to DFSORT at Major Call 1, 2, 3, 4, or 5.

System action:

If the invalid return code was returned at Major Call 1, the program terminates. If the invalid return code was returned at Major Call 2 through 5, DFSORT scans all remaining control statements and then the program terminates.

Programmer response:

Check the EFS program thoroughly and ensure that the return code is either 0 or 16.

ICE703A

INVALID RETURN CODE FROM ppppp OF EFS PROGRAM pppppppp

Explanation:

Critical. The ppppp-generated user exit routine, EFS01 or EFS02, of EFS program pppppppp returned an invalid return code to DFSORT.

System action:

The program terminates.

Programmer response:

Check the EFS-generated user exit routines thoroughly and ensure that the return code returned by EFS01 is either 0 or 16 and that the return code returned by EFS02 is 0, 4, or 16.

ICE704A

LOAD FAILED FOR EFS PROGRAM pppppppp

Explanation:

Critical. EFS program pppppppp could not be loaded.

System action:

The program terminates.

Programmer response:

Check that EFS program pppppppp is installed.

ICE705A

EFS PROCESSING WAS TERMINATED BY ppppp OF EFS PROGRAM pppppppp

Explanation:

Critical. Termination of the DFSORT run was requested by a user exit routine generated by EFS program pppppppp.

ppppp is one of the following names:

EFS01

The SORT/MERGE user exit routine.

EFS02

The INCLUDE/OMIT user exit routine.

System action:

The program terminates.

Programmer response:

Refer to the message issued by the user exit routine generated by EFS program pppppppp.

ICE706I

END OF SUPPLIED CONTROL STATEMENTS – EFS RETURNED CONTROL STATEMENTS FOLLOW

Explanation:

When control statements are specified in the invoking parameter list or control statements are specified with the DD statement for SYSIN or xxxxCNTL, this message separates the listing of those control statements from the listing of the control statements returned by an EFS program.

A control statement returned by an EFS program completely overrides the corresponding control statement in the parameter list, or in SYSIN or xxxxCNTL. (OPTION control statement operands EFS, LIST, NOLIST, LISTX, NOLISTX, MSGDDN, MSGPRT, SORTDD, SORTIN, SORTOUT, and USEWKDD are ignored if returned by an EFS program.)

For complete details on the order of override, see z/OS DFSORT Application Programming Guide.

System action:

None.

Programmer response:

None.

ICE707A

EXIT E61 IS NOT SUPPORTED FOR EFS FIELDS

Explanation:

Critical. The SORT or MERGE control statement defined a control field to be processed both by an EFS program and an E61 user exit routine.

System action:

The program terminates.

Programmer response:

Check the SORT or MERGE control statement for errors resulting in the specification of a D1 field format type with an E field sequence type.

ICE708A

AN EFS PROGRAM IS REQUIRED

Explanation:

Critical. A SORT/MERGE control field or an INCLUDE/OMIT compare field was to be processed by an EFS program, but the EFS program was not activated by the EFS option, nor was a verb request list returned at Major Call 1.

System action:

The program terminates.

Programmer response:

Check the SORT/MERGE or INCLUDE/OMIT control statements for errors resulting in the specification of a D1 or D2 field format type. Check that the EFS option has been specified.

ICE709A

ppppp EXIT ROUTINE IS REQUIRED

Explanation:

Critical. A SORT/MERGE control field or an INCLUDE/OMIT compare field was to be processed by an EFS program, but the EFS program did not return an address to EFS01 or EFS02.

ppppp is one of the following names:

EFS01

The SORT/MERGE user exit routine.

EFS02

The INCLUDE/OMIT user exit routine.

System action:

The program terminates.

Programmer response:

Check the SORT/MERGE and INCLUDE/OMIT control statements for errors resulting in the specification of a D1 or D2 field format type. Check the EFS program and ensure that it returns an address to EFS01 or EFS02.

ICE710A

THE aaaaaaaa CONTROL STATEMENT WAS NOT SENT TO EFS PROGRAM pppppppp

Explanation:

Critical. The control statement aaaaaaaa requested by EFS program pppppppp contained a syntax error. DFSORT could not determine the true length of the requested control statement or option.

System action:

The program terminates.

Programmer response:

Respond as indicated in the accompanying message ICE007A.

ICE711I

END OF EFS RETURNED CONTROL STATEMENTS FROM xxxxCNTL – PARAMETER LIST CONTROL STATEMENTS FOLLOW

Explanation:

When returned control statements are specified in the invoking parameter list and with the DD statement for xxxxCNTL, this message separates the listing of requested control statements from both sources.

If all returned control statements came from either SORTCNTL or the parameter list, message ICE711I was not printed; only ICE706I was printed.

For complete details on the order of override, see z/OS DFSORT Application Programming Guide.

System action:

None.

Programmer response:

None.

ICE712I

END OF EFS RETURNED PARAMETERS FROM ddname – SYSIN OR xxxxCNTL/PARAMETER LIST CONTROL STATEMENTS FOLLOW

Explanation:

When returned parameters are specified with:

  • The SYSIN DD statement
  • The SORTCNTL DD statement, or
  • The invoking parameter list

and are specified with the DD statement indicated by ddname, this message separates the listing of the requested data set’s parameters from the former sources.

See z/OS DFSORT Application Programming Guide for details on the order of override.

System action:

None.

Programmer response:

None.

ICE713A

LANGUAGE ENVIRONMENT INITIALIZATION FAILED

Explanation:

Critical. Language Environment initialization failed.

System action:

The program terminates.

Programmer response:

Contact IBM for programming support.

ICE714A

LOAD FAILED FOR ACTIVE LOCALE name

Explanation:

Critical. Indicates that the designated active locale could not be loaded and gives its name.

System action:

The program terminates.

Programmer response:

If the indicated locale name is that of an IBM supplied locale, DFSORT must have access to the run-time library containing the dynamically loadable routines. For example, the data set containing them might be called SYS1.SCEERUN. If you are unsure of the name of the data set where the compiled locale load modules are installed at your location, contact your system administrator.

If the indicated name is that of a user defined locale, DFSORT must have access to the load library containing it.

ICE715A

LOCALE PROCESSING CONFLICTS WITH keyword

Explanation:

Critical. Locale processing cannot be used with the function or feature indicated by the keyword shown. See z/OS DFSORT Application Programming Guide for details on locale processing and the function or feature indicated.

System action:

The program terminates.

Programmer response:

If D1, D2, or EFS is the indicated keyword, take one of the following actions:

  • Specify run-time option EFS=NONE to use locale processing without EFS processing. (Locale processing might eliminate the need for an EFS program.)
  • Specify run-time option LOCALE=NONE to use EFS processing without locale processing.

If CHALT is the indicated keyword, take one of the following actions:

  • Specify run-time option NOCHALT to use locale processing without alternate sequence processing for CH fields. (Locale processing might eliminate the need for alternate sequence processing.) If alternate sequence processing is needed for a particular field, specify AQ for that field instead of CH.
  • Specify run-time option LOCALE=NONE to use alternate sequence processing for CH fields without locale processing.

If INREC is the indicated keyword, take one of the following actions:

  • Use the OUTREC statement or the OUTREC operand of the OUTFIL statement instead of the INREC statement to allow locale processing.
  • Specify run-time option LOCALE=NONE to use the INREC statement without locale processing.

If E61 is the indicated keyword, take one of the following actions:

  • Eliminate the E61 exit, and change E to A or D for each field, to use locale processing without E61 processing. (Locale processing might eliminate the need for an EFS program.)
  • Specify run-time option LOCALE=NONE to use E61 processing without locale processing.

ICE716A

A CONTROL FIELD CONTAINS AN INVALID CHARACTER

Explanation:

Critical. Locale processing of a control field detected that a character in the control field is not defined in the active locale.

System action:

The program terminates.

Programmer response:

Ensure that the correct locale is the active locale in effect or correct the invalid character.

ICE717A

CONTROL FIELDS FOR LOCALE PROCESSING ARE TOO COMPLEX

Explanation:

Critical. For a SORT or MERGE statement with control fields that require locale processing, the complexity of the application caused dynamic areas to exceed the storage allowed for them.

System action:

The program terminates.

Programmer response:

Reduce the number or length of SORT or MERGE control fields that require locale processing.

ICE721A

A COMPARE FIELD CONTAINS AN INVALID CHARACTER

Explanation:

Critical. Locale processing of a compare field detected that a character in the compare field is not defined in the active locale.

System action:

The program terminates.

Programmer response:

Ensure that the correct locale is the active locale in effect or correct the invalid character.

ICE722I

ACTIVE LOCALE name WAS USED FOR LOCALE PROCESSING

Explanation:

Indicates that DFSORT used locale processing and gives the name of the active locale. Locale processing is used for:

  • SORT or MERGE character (CH) control fields
  • INCLUDE or OMIT character (CH) compare fields
  • INCLUDE or OMIT character or hexadecimal constant to character (CH) compare field comparisons.

Note:

Locale processing is not used for IFTHEN WHEN constants or compare fields.

System action:

None

Programmer response:

None

ICE725A

LANGUAGE ENVIRONMENT SERVICE ERROR (nnnn)

Explanation:

Critical. Language Environment services returned an unexpected feedback code for a service call used by DFSORT. nnnn is the error message number of the feedback code.

System action:

The program terminates.

Programmer response:

Take one or more of the following actions, as appropriate:

  • Check that all SORT, MERGE, INCLUDE, or OMIT CH fields contain valid character data values.
  • Contact IBM for programming support. The error message number can be used to reference Language Environment Run-Time Messages in Locale Processing.

ICE726A

LOAD FAILED FOR LOCALE PROCESSING

Explanation:

Critical. DFSORT’s locale processing routine could not be loaded.

System action:

The program terminates.

Programmer response:

Contact your system programmer to ensure that DFSORT’s locale processing support has been installed.

ICE727A

EFS PROCESSING CANNOT BE USED WITH SYMBOL PROCESSING

Explanation:

Critical. A SYMNAMES data set was specified indicating that symbol processing is to be performed. However, an EFS program was also specified. EFS processing and symbol processing cannot both be used.

System action:

The program terminates.

Programmer response:

Use EFS processing or symbol processing, but not both.

URL:  http://publib.boulder.ibm.com/infocenter/zos/v1r12/index.jsp?topic=%2Fcom.ibm.zos.r12.icem100%2Fdfsor.htm

Advertisements