• The data control block (DCB) for SORTIN contained incorrect LRECL or BLKSIZE data set attributes. Check the SORTIN DD statement to ensure that the LRECL and BLKSIZE parameters are correct.
• When a COBOL program invoked DFSORT:
  • The SELECT or ASSIGN statement specified an incorrect file name or DDNAME parameter.
  • The SORTIN or SORTOUT files specified DCB attributes different from those defined for the data set.
  • The FD file description for SORTIN or SORTOUT files contained inaccurate specifications (such as RECORD CONTAINS, BLOCK CONTAINS, RECORDING MODE, and so on).

• For variable-length record SORTOUT or OUTFIL data sets, the record descriptor word was invalid (less than 4 bytes or greater than 32 KB) or, for nonspanned records, was greater than the specified block size.
• For fixed-length record SORTOUT or OUTFIL data sets, the LRECL parameter was greater than the BLKSIZE parameter.

• Was greater than 32760 for a disk data set, or was greater than the maximum block size supported by the access method for a tape data set.
• Was not an integer multiple of the LRECL parameter for fixed-length records, or was not at least four bytes longer than the LRECL for variable-length records.

• Locale processing with a run-time library that contains down-level dynamically loadable routines.
• An invalid PD or ZD sign (0-9) or digit (A-F) can result in a data exception (0C7 ABEND) for SUM processing. An invalid PD or ZD digit can result in a data exception for OUTFIL edit or statistics processing. ICETOOL's DISPLAY or VERIFY operators can be used to identify decimal values with invalid digits. ICETOOL's VERIFY operator can be used to identify decimal values with invalid signs.
• A user exit passed back a variable-length record that was shorter than the record descriptor word indicated.
• A user exit passed back a fixed-length record that was shorter than the length specified in the RECORD statement (L2 for E15 and E32, or L3 for E35).
• The contents of register 1 (and possibly other registers) used by DFSORT were altered before returning to DFSORT. Ensure the registers are restored before returning to DFSORT.
• The SORTLIB DD statement specified an incorrect library.
• The DEBUG CTRx option was in effect and the criteria were met.
• For COBOL:
  • DISPLAY was used for COBOL messages, but the message data set was missing. Supply a message data set DD statement. (See the discussion of MSGDDN in z/OS DFSORT Application Programming Guide for an alternative solution.)
  • An attempt was made to reopen an open data set, or a data set was already open prior to executing the SORT USING statement.
  • A STOP RUN or GOBACK statement was required but not supplied; therefore, the COBOL program did not exit as intended but processed the next instruction.
  • Invalid logic was used in a sort I/O procedure (possibly using the STOP RUN, GOBACK, CALL, or GO TO statements), or PERFORM referred to a paragraph outside the section.
  • The file name or DDNAME parameter of the SELECT/ASSIGN statement was incorrect.
  • The LINKAGE SECTION was specified incorrectly or misplaced.
  • The PROCEDURE DIVISION USING statement gave an invalid parameter list.
  • An attempt was made to move data from the COBOL SD area prior to execution of the SORT verb.
  • The FD entry RECORD CONTAINS clause (LRECL) for the USING data set is different than the SD entry RECORD CONTAINS clause for the SORTWK data set.

• A specified data set was not found.
• Space for the SORTOUT or OUTFIL data set was not allocated.
• For COBOL:
  • The file name or DDNAME parameter of the SELECT or ASSIGN statement was incorrect.
  • The SORT verb required the SORTLIB DD statement.

ABEND 806, along with message “CSV003I REQUESTED MODULE CEEBINIT NOT FOUND”, may occur if during locale processing DFSORT does not have access to the library containing the dynamically loadable routines. For example, the data set containing these routines might be called SYS1.SCEERUN. If you are unsure of the name of the data set, contact your system administrator.