This chapter explains the User and System abends.
This section contains the following topics:
This topic covers some of the user abends associated with CA View.
Reason:
A permanent archival control statement is invalid. The backup cycle of the CA View started task terminates. The abend is accompanied by messages beginning with SARPAR
xx,
and message text identifying the type of error that occurred:SARPARxx (CARD xxxx) INVALID xxxxxxxxxxxxxxxxxxx
Action:
To complete the backup cycle or SARVERO utility correct the control statement, and then restart the started task.
Reason:
This abend is issued by EBCTMR12, EBCTMRR, EBCTMRS, EBCTMRT, and EBCTMRX when a screen service could not be performed successfully. This abend occurs if the address space with which XMS is communicating has abended or been canceled.
Action:
If the associated address space being canceled or abended causes the abend, then restart the abended task to stop the abends. The XMS address spaces must continue to process other requests. For assistance, contact Technical Support at http://ca.com/support.
Reason:
Copying a tape using the ADDHDR parameter but the input tape has a CA View Header (SARHDR).
Action:
Remove the ADDHDR parameter and rerun the tape copy.
Reason:
The XMS logon request queue storage was overlaid. The XMS region abends when this occurs.
Action:
Restart your XMS region. Save the dump that is created by the U0005 abend and For assistance, contact Technical Support at http://ca.com/support.
Reason:
Copying full tapes using the Tape Copy Utility SARTCP to output tapes which are not long enough to hold all of the input tape data and results in the message SARTCP11.The job step also terminates with a user abend U0011.
Action:
Rerun the step with a new scratch tape. The differences in physical tape lengths cause this problem and several attempts are required to obtain a tape which is long enough to hold the input data. SARPAC can also be used to create a tape rather than copying the tape.
Reason:
The database has no more space to hold direct-to-CA View archival reports from CA Deliver, and the operator responded T(Terminate) to the following message:
SARPAM24 DATABASE database-name FULL - REPLY R (RETRY) OR T (TERMINATE)
Action:
Either create more space in the database by deleting SYSOUTS or add more space to the database by either ADDDS or SARDBASE.
Reason:
The EMC Centera API modules (FPAPIDLL, FPMDZDLL, FPPOSDLL, FPPAIDLL, and/or XERCES26) were not found. This message occurs if a release 3.0 or prior EMC Centera load library is referenced.
Action:
Add the EMC Centera load library to JOBLIB, STEPLIB, or the link list. The EMC Centera load library can also be copied to CVDELOAD.
Reason:
An unsupported version of the EMC Centera API modules is found in JOBLIB, STEPLIB, or the link list.
Action:
Add the EMC Centera load library distribute with CA View to JOBLIB, STEPLIB, or the link list. The EMC Centera load library can also be copied to CVDELOAD.
Reason:
The direct-to-CA View archival feature is attempting to write report data to an encrypted database but the external key manager product (ICSF) is not active, not installed, or has rejected the service request to obtain the encryption key. The operator responded T(Terminate) to the following message:
SARPAM30 External key manager error obtaining key for
database-name
- Reply R (retry) or T (terminate).Action:
See the ‘ACTION’ section under the SARPAM30 message for instructions.
Reason:
If DFSORT ABEND or ABSTP is in effect, and DFSORT terminates with an error message, you receive a user abend. If the DFSORT installation option is set to the default value (ABCODE=MSG), the user abend code is equal to the error message (for example, U0046 for message ICE046A). For user abend codes that are error message numbers (ABCODE=MSG), see the explanation for the corresponding message (for example, the ICE046A Explanation for U0046).
Action:
Correct the sort error and restart the function.
CA View is modified to prevent a loop in IOCS when I/O errors occur on 'fenced' tape devices. The modification causes SARTPO (CA View Tape Output Processor) to abend when an unrecoverable tape I/O error occurs.
A user abend 0049 can occur during a backup cycle or a tape consolidation (SARPAC) run.
A U0049 abend during a backup cycle terminates the archival task (SARSTC). The task must be restarted with the execution parameter STOPBU to reset backup cycle processing, and start a new backup cycle using the modify command.
Example:
F SARSTC,NEW
A U0049 abend during a tape consolidation run terminates the job. Until a new backup cycle has completed the run must not restart. Start a new backup cycle using the modify command as described previously.
The tape that caused the U0049 abend contains valid reports and is usable. Customer tape library systems must be set up to keep tapes created by CA View tasks that abend.
The tape that caused the U0049 abend produces block ID errors when used. When MVS closes some high‑density tapes from tasks that are terminated abnormally , the tape's Record 0 is set to 'corrupted'. Record 0 is a hardware control record on a high‑density tape which is used with block ID processing. If Record 0 is corrupt, you can see an I/O error when CA View is positioning the tape. This caused a tape rewind and multiple 'forward space files' to reposition the tape.
A tape consolidation run against this tape copies all active reports to new tape media that restores the block ID processing.
Reason:
The DSK2PARM specifies a unit that is not a tape device. The following message displays along with the abend:
SARTPO55 SECONDARY DISK DOES NOT EMULATE 3480 TAPES
Action:
Correct the DSK2DRVR name to use the correct driver if it is in error, correct the DSK2PARM to use a tape device, or correct the tape unit's system definition.
Reason:
The TAPEOPT parameter specifies EAST, but the tape unit does not support block ID processing. The abend is accompanied by the following message:
SARTPO56 IMMEDIATE TAPE ACCESS REQUIRES 3480 TAPES
Action:
Correct the tape unit name in the STORGRPx definition, correct the tape unit's system definition, or change TAPEOPT to use 3420 processing.
Reason:
CA View has to create a tape volume, but the specified range has been exhausted. The following message displays with the abend:
SARTPO57 VOLSER RANGE xxxxxx-xxxxxx EXCEEDED (VOLSER RANGE MUST BE EXTENDED OR CHANGED), PROCESSING TERMINATED
Action:
Define new volumes and modify the range in the STORGRPx or STORGRXx parameter.
Reason:
CA View writes several blocks to a tape volume simultaneously. The maxblks specification in the STORGRXx parameter is below this number (currently 10). The following message displays with the abend:
SARTPO58 MAXBLKS FOR STORAGE GROUP SET TOO LOW
Action:
Correct the maxblks specification in the STORGRXx parameter.
Reason:
An attempt is made to add or update a SYSOUT group index record with an invalid generation and sequence number. Processing is terminated. The following message displays along with the abend:
SARIFP01 INVALID GROUP CONTROL RECORD ID=xxxxxxxxxxxx, GEN=nnnn, AND SEQ=nnnn ENCOUNTERED, PROGRAM TERMINATED.
Action:
If this occurs during a SARDBASE REORG, the program automatically corrects the error, and you can ignore this message. If bad records reside in the database from earlier releases of the product, the database needs correction with the VERIFY control statement from the SARDBASE utility. Otherwise, the processing can be resumed. For assistance, contact Technical Support at http://ca.com/support.
Reason:
ERO processing is selected (EROOPT=YES initialization parameter) with the ERO table being the single source of retention information (PRETAIN=TABLE initialization parameter), but the ERO table that is referenced by the SARPATAB DD statement is not specified in the archival task (SARSTC) job stream. This following message displays along with the abend:
SARPAR09 SARPATAB DD STATEMENT MISSING
Action:
Add the SARPATAB DD statement to the archival task job stream referencing a sequential file or a member of a PDS that containing the ERO table entries or change PRETAIN to INIT if there is no ERO Table.
Reason:
ERO processing was selected (EROOPT=YES initialization parameter) with the ERO table being the single source of retention information (PRETAIN=TABLE initialization parameter), but the data set referenced by the SARPATAB DD statement in the archival task (SARSTC) job stream does not contain any ERO table entries. This following message displays along with the abend:
SARPAR10 SARPATAB DATA SET EMPTY
Action:
Point the SARPATAB DD statement to a sequential file or member of a PDS that contains the table entries or change PRETAIN to INIT if there is no ERO Table.
Reason:
The logical record length (LRECL) of data set pointed to by the SARPATAB DD Statement in the Archival Task (SARSTC) procedure exceeds 256 characters. The following message displays along with the abend:
SARPAR12 SARPATAB data set LRECL greater than 256.
Action:
Reallocate the data set with a logical record length (LRECL) of 256 characters or less and restart the Archival Task.
Reason:
CA View is attempting to allocate dynamically a SYSOUT data set to print a SYSOUT group, and an internal program logic error occurred. The online print or batch print terminates. The following message displays along with the abend:
SARPRT99 Unexpected return code - xxxx
Action:
For assistance, contact Technical Support at http://ca.com/support.
Reason:
CA View is attempting to allocate dynamically a SYSOUT data set to print a SYSOUTgroup, and an internal program logic error occurred. The online print or batch print terminates. The following message displays along with the abend:
SARBCP44 Unexpected return code – xxxx
Action:
For assistance, contact Technical Support at http://ca.com/support.
Reason:
CA View is attempting to dynamically allocate a SYSOUT data set to print a SYSOUT group, and an internal program logic error occurred. The online print or batch print terminates. The abend is accompanied by the following message:
SARBPT99 Unexpected return code - xxxx
Action:
For assistance, contact Technical Support at http://ca.com/support.
Reason:
An internal processing error occurred while performing I/O on a database sub‑file.
Action:
Secure all system and job logs and dumps. For assistance, contact Technical Support at http://ca.com/support.
Reason:
The ACIF compression dictionary (SARCED01) is incorrectly linked (not on the page boundary). This error must never occur, but if it does, the cause is either an internal or packaging error. Specifying ACIFCOMP=NO in your SARINIT parameters allows the FSS collectors to process, but you are not able to access any compressed ACIF reports until this is corrected.
Action:
Do not modify the compression dictionary in any way. For assistance, contact Technical Support at http://ca.com/support.
Reason:
The ACIF compression dictionary (SARCED01) is corrupted (size is not a multiple of 4 KB). This error must never occur, but if it does, the cause is either an internal or packaging error. Specifying ACIFCOMP=NO in your SARINIT parameters allows the FSS collectors to process, but you are not able to access any compressed ACIF reports until the error is solved.
Action:
Do not modify the compression dictionary in any way. For assistance, contact Technical Support at http://ca.com/support.
Reason:
This indicates MVS Compression Services returned a non‑zero return code. Specifying ACIFCOMP=NO in your SARINIT parameters allows the FSS collectors to process, but you are not able to access any compressed ACIF reports until this is corrected.
Action:
This is a problem with the MVS Compression Services themselves, not with the interface supplied with CA View. The return code from MVS Compression Services is in R7.
Note: For more information about the return codes, see the chapter "CSRCMPSC – Compress and Expand Data" in the MVS Assembler Services Reference Manual.
This section provides some of the system abends associated with CA View.
|
Copyright © 2013 CA.
All rights reserved.
|
|