FastSort Manual

FastSort Error Messages
FastSort Manual—429834-003
B-10
Numeric List of Programmatic Messages
Cause. A key field does not lie entirely within the record.
Recovery. Correct either the key-field offset or the record length.
Cause. The specified output file exists but is too small or has a wrong type.
SORTPROG cannot purge the file and create a new one because of the file's security,
current usage, or some other condition in the system.
Recovery. Use the NOPURGE option of the TO command or flags<14>.1 in
SORTMERGESTART. If this strategy fails to resolve the problem, follow recovery
recommendations in the Guardian Procedure Errors and Messages Manual for the
operating system error code returned with this FastSort error code. If the problem is
security or current usage, you can change the security for the file or prevent concurrent
access to it.
Cause. SORTPROG could not open a scratch file.
Recovery. Follow recovery recommendations in the Guardian Procedure Errors and
Messages Manual for the file-system error number returned with this FastSort error
code.
Cause. SORTPROG could not write to the output file, probably because you or
FastSort underestimated the number of input records.
Recovery. If FastSort underestimated the number of input records, you can specify
the number of records or name an existing file large enough to hold the output records.
Follow recovery recommendations in the Guardian Procedure Errors and Messages
Manual for the operating system error code returned with this FastSort error code.
Cause. SORTPROG could not write to a scratch file, either because you
underestimated the number of input records or because of a disk process or data flow
problem.
Recovery. Ensure that sufficient scratch space exists for the sort. SORTPROG might
require more overflow scratch space. For more informatio about scratch files, see
Managing Sort Workspace on page 9-1.
26 A KEY FIELD LOCATION EXCEEDS THE RECORD SIZE.
27 THE TO FILE ALREADY EXISTS AND CANNOT BE PURGED.
28 A SCRATCH FILE CANNOT BE OPENED.
29 A WRITE HAS FAILED TO THE TO FILE.
30 A WRITE HAS FAILED TO A SCRATCH FILE.