Text |
Unexpected error during execution of SORT statement. |
Explanation |
This is an internal error. |
Action |
Contact Software AG support. |
Text |
External sort control fields total exceeds 256 bytes. |
Explanation |
The external sort used via the SORT statement supports a maximum of 256 bytes for the sort fields. |
Action |
Reduce the number or length of sort fields specified in the SORT statement. |
Text |
Error in external sort; core/disk space insufficient. |
Explanation |
For the external sort function, either a system sort program is invoked (in batch mode) or an incore sort is invoked (in online mode). In batch mode, the reason for the error message is either insufficient disk space or a missing DD card. In online mode, the reason for the message is insufficient memory in the file buffer which is used for intermediate storage in the sort process. |
Action |
Contact your Natural administrator. |
Text |
External sort cannot be used in this environment. |
Explanation |
The SORT/NTSORT option EXT=ON has been specified, but the requested external sort cannot be used for the execution of the Natural SORT statement in the current environment. An external sort can only be used if Natural is running in a batch- oriented environment (batch mode, TSO, VM/CMS, TIAM). If Natural is running in a TP environment (Com-plete, CICS, IMS TM, UTM) or as an NDV server, the Natural internal sort has to be used. |
Action |
Use the SORT/NTSORT option EXT=OFF. |
Text |
External sort module not found. |
Explanation |
The system sort program to be used for the external sort function could not be found in any of the libraries defined for the Natural run. |
Action |
Check if the NTSORT parameter EXTNAME contains a valid name for the sort program and that the load libraries defined for the Natural run contain that module. |
Text |
No more sort work space. |
Explanation |
There is no more space in the core; or the work files cannot be accessed, are full, or cannot be supported; or the record size is greater than the maximum buffer size. |
Action |
Decrease the number of records to be sorted, or the number of fields per sort record; or enlarge the incore sort work area or sort work files (if present). |
Text |
No more internal work space for buffer pool sort. |
Explanation |
The internal work space required for a buffer pool sort is full. |
Action |
Increase the NTSORT parameter WRKSIZE. |
Text |
Sort buffer pool is full. |
Explanation |
The sort buffer pool used as a temporary storage for intermediate results during the sort function is full. The problem may also be caused by too many parallel sort runs. |
Action |
Increase the size of the sort buffer pool or decrease the number of parallel sorts. |
Text |
The buffer pool sort module could not be found. |
Explanation |
The buffer pool sort module is not linked to NAT2SORT. This is an internal error. |
Action |
Contact Software AG support. |
Text |
Internal error during buffer pool sort. |
Explanation |
Internal control blocks are destroyed. |
Action |
Contact Software AG support. |
Text |
Sort buffer pool lost during open processing. |
Explanation |
The sort buffer pool is lost during execution of the sort function. Possible reasons: - The sort buffer pool was shut down while sort was active. - The Natural session was switched to another address space and no global sort buffer pool was used. - The Natural session was switched to another operating system image (SYSPLEX only). This is not supported. |
Action |
Ensure that the same sort buffer pool is available to the Natural session while a sort function is active. |
Text |
Sort buffer pool lost during read/write processing. |
Explanation |
The sort buffer pool is lost during execution of the sort function. Possible reasons: - The sort buffer pool was shut down while sort was active. - The Natural session was switched to another address space and no global sort buffer pool was used. - The Natural session was switched to another operating system image (SYSPLEX only). This is not supported. |
Action |
Ensure that the same sort buffer pool is available to the Natural session while a sort function is active. |
Text |
Internal error - no more space in quicksort work area. |
Action |
Contact your Natural administrator. |
Text |
Sort buffer pool lost during purge processing. |
Explanation |
The sort buffer pool is lost during execution of the sort function. Possible reasons: - The sort buffer pool was shut down while sort was active. - The Natural session was switched to another address space and no global sort buffer was used. - The Natural session was switched to another operating system image (SYSPLEX only). This is not supported. |
Action |
Ensure that the same sort buffer pool is available to the Natural session while a sort function is active. |
Text |
SORT/NTSORT option STORAGE=SD only allowed under Com-plete. |
Explanation |
The SORT/NTSORT option STORAGE=SD can only be used for the Natural internal sort if the Natural session is running under Com-plete. |
Action |
Use STORAGE=MAIN or STORAGE=BP. |
Text |
Multiple active SORTs are not allowed. |
Explanation |
No more than one SORT loop may be active at a time. This error occurs if within an active processing loop initiated with a SORT statement another program, subprogram or subroutine is invoked, and within this invoked object another SORT statement is executed. |
Action |
Correct error in application. |
Text |
Memory required for statement execution not available. |
Explanation |
The memory required to execute the statement is not available. Possible reasons are: - The amount of memory allocated to a dynamic variable or an X-array had to be increased, but this caused the total memory available to the Natural session to be exceeded. - The amount of work memory required to execute the statement caused the total memory available to the Natural session to be exceeded. - Natural environment constraints (e.g. the settings of profile parameters) limit the total amount of memory available to the Natural session. - Operating or TP system restrictions (e.g. the total memory available) limit the amount of memory that is available to the Natural session. |
Action |
Use the system command LASTMSG * to find out what exactly caused the memory request to fail. Check program and correct error, or contact your Natural administrator. |
Text |
A numeric field contains a non-numeric digit. |
Explanation |
At least one of the digits in a numeric field is not a numeric digit and cannot be processed in a numeric context. |
Action |
Check if the numeric field in question is redefined as alphanumeric or binary. If so, make sure it contains only numeric digits. Otherwise, input data (from the database) could be erroneous. |