|
|
|
The following messages are produced by the CA SRAM Common Service.
Reason:
The parameter table or return table is not aligned on a fullword boundary.
Action:
Ensure that the definition of the table includes the keyword ALIGNED or SYNCHRONIZED, respectively, when using PL/I or COBOL. See the CA SRAM User Guide for specifying sort parameter tables.
Reason:
The record length has not been specified.
Action:
Specify a valid record length in the sort parameter table.
Reason:
A syntax error has been detected in the key definition vector. Possible causes include:
Action:
See the CA SRAM User Guide for the key definition vector specification.
Reason:
The CA SRAM work file has not been assigned to a DASD device, the open for the work file was unsuccessful, or a nonzero return code was obtained when issuing SVC 24 to obtain the device characteristics of the work file. This can also occur if the DDname specified in the parameter table is an invalid z/OS DDname or if the DDname specified in the JCL does not match the value in the table.
Action:
Ensure that there is a corresponding DD statement for the DDname specified in the sort parameter table and that it is assigned to a valid DASD device supported by CA SRAM.
Reason:
An error return code has been returned by the DYNALLOC system function.
Action:
See the IBM manual SPL: Job Management for an explanation of the various return, error, and information codes.
Reason:
The maximum number of 15 secondary extents on the CA SRAM work file has been exceeded.
Action:
Assign more work file space. Increase amount of space for primary or secondary allocation. Ensure that the amount of space specified for the primary allocation is sufficient, and that there is enough contiguous space on the assigned work volume to prevent an excessive number of secondary allocations. In general, the work file allocations should be sufficient to hold all input records plus a reserve of about 10% to 25%. More work file space may be required for the sort task whose control fields are in reverse sequence.
Reason:
An attempt has been made to open or reopen the same work file more than once without first closing it.
Action:
Check for the wrong parameter table name on two CA SRAM sorts or another user logic error.
Reason:
The storage value specified in the parameter table is below the absolute minimum. Each sort must have at least 4 KB of storage to operate. Performance will probably improve if more storage than the minimum is specified.
Action:
Correct the program to specify a larger storage value.
Reason:
An application program logic error has caused a FILL call to be issued either before the OPEN, or after a call to SRTCLSE, SRTGETR, or SRTOPN.
Action:
Check the user program for logic and coding errors.
Reason:
An application program logic error has caused a call to SRTGETR to be issued before the OPEN or FILL call, or after the close has been issued.
Action:
Check the user program for logic and coding errors.
Reason:
A call to SRTGETR has been issued after CA SRAM presented an end-of-file condition.
Action:
Check the EOF indicator after every retrieve call for the value '99' after each SRTGETR call.
Reason:
Occurs if a return code table has been provided and another CA SRAM call has been made after an error occurred on a previous call. It is important to check for a nonzero value in the return code halfword of the table after every CA SRAM call. If return codes are requested, it is the responsibility of the user program to take appropriate action to handle the error condition.
Action:
Correct the user program to check for nonzero return codes after each CA SRAM call and take the appropriate action.
Reason:
An I/O error has occurred during an open or reopen of the CA SRAM work file. The standard SYNAD information that describes the nature of the I/O error is displayed in the message. The value xxxxxxxx will show the DDname from the parameter table.
Action:
Ensure that the work file DD statement in the error message is specified correctly. Check for possible hardware-related errors on the device in the error message. Resubmit the job using an alternative unit or volume. Ensure that the work file has remained unchanged from the last SRTCLSE call, if a reopen of the CA SRAM work file is requested.
Reason:
An I/O error has occurred during a FILL operation to the CA SRAM work file. The standard SYNAD information that describes the nature of the I/O error is displayed in the message. The value xxxxxxxx will show the DDname from the parameter table.
Action:
Ensure that the work file DD statement in the error message is specified correctly. Check for possible hardware-related errors on the device in the error message. Resubmit the job using an alternative unit or volume.
Reason:
An I/O error has occurred during a GETR operation from the CA SRAM work file. The standard SYNAD information describing the nature of the I/O error is displayed in the message. The value xxxxxxxx will show the DDname from the parameter table.
Action:
Ensure that the work file DD statement in the error message is specified correctly. Check for possible hardware-related errors on the device in the error message. Resubmit the job using an alternative unit or volume.
Reason:
The expected return address in hexadecimal notation within the user program is represented by xxxxxx.
Action:
For assistance, contact CA Support at http://ca.com/support.
Reason:
An internal error of undetermined origin has been detected by CA SRAM.
Action:
Save all of the documentation produced. For assistance, contact CA Support at http://ca.com/support.
| Copyright © 2011 CA. All rights reserved. | Tell Technical Publications how we can improve this information |