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 rejected the service request to obtain the encryption key. The write to operator message is preceded by a SARICF message that identifies the specific error.
Action:
The SARICF message specifically identifies the nature of the error. If the SARICF error message identifies a return and reason code, a description of the code can be found in Appendix A of the IBM z/OS Cryptographic Service Application Programmer’s Guide.
After the problem is resolved and the external key manager product is active, reply "R" to the SARPAM30 to resume direct to CA View archival for the job. The direct to CA View archival interface attempts to reestablish communication with the external key manager product every minute. If connection is reestablished, the SARICF and SARPAM30 messages are deleted. If the external key manager product error cannot be resolved in the near term, the job can be terminated by replying "T" to the SARPAM30 message. If so, it is also desirable to turn off direct to CA View archival or turn off encryption to the affected database(s).
Reason:
A permanent archival control statement is invalid. The backup cycle of the CA View started task terminates with a U0001 user abend.
Action:
Correct the control statement, and then restart the started task to complete the backup cycle.
Reason:
The SYSOUT identifier on a permanent archival control record is too long. The backup cycle of the CA View started task terminates with a U0001 user abend.
Action:
Correct the control statement, and then restart the started task to complete the backup cycle.
Reason:
The keyword on a permanent archival control record is too long. The backup cycle of the CA View started task terminates with a U0001 user abend.
Action:
Correct the control statement, and then restart the started task to complete the backup cycle.
Reason:
A duplicate keyword is found for the specified ID. The backup cycle of the CA view started task terminates with a U0001 user abend.
Action:
Correct the control card, then restart the started task to complete the backup cycle.
Reason:
The value for the keyword on a permanent archival control record is invalid. The backup cycle of the CA View started task terminates with a U0001 user abend.
Action:
Correct the control statement, and then restart the started task to complete the backup cycle.
Reason:
The keyword on a permanent archival control record contains too many operands. The backup cycle of the CA View started task terminates with a U0001 user abend.
Action:
Correct the control statement, and then restart the started task to complete the backup cycle.
Reason:
The specified keywords cannot be specified on the same control statement and are mutually exclusive. The message is issued with the specification of the Expanded Retention option ALL, LAST, and MARK parameters.
Action:
Execution continues with the assumed specification. Change the Expanded Retention Option control statement to specify either ALL, LAST, or MARK.
Reason:
The ERO table contains report ID statements that are out of order. Since this table is searched sequentially, the most specific entries must precede generic entries. This error occurs when the SARSTC task is started, and the task immediately abends if this error is found.
Action:
Correct the order of the ERO table entries so that the more specific entries precede the more generic entries.
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 ERO table that is referenced by the SARPATAB DD statement is not specified in the archival task (SARSTC) job stream. The backup cycle of the CA View started task terminates with a U1009 user abend.
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.
Note: Processing continues without the ERO table data.
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 that is referenced by the SARPATAB DD statement in the archival task (SARSTC) job stream does not contain any ERO table entries. The backup cycle of the CA View started task terminates with a U1010 user abend.
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:
DRETPD is not coded or is coded with a value less than DSK2DAYS, DRETPR is set to the same value as DSK2DAYS to allow for migration.
Action:
Add DRETPD or extend its value to keep the Sysout on primary disk until it is migrated (DSK2DAYS). Or, remove the DSK2DAYS parameter if it must not be migrated to the secondary disk.
|
Copyright © 2013 CA.
All rights reserved.
|
|