This section details messages generated in the course of PITR processing, along with possible causes and corrective actions to take in error situations.
Reason:
The field and date/time values are invalid.
Action:
Correct the parameter specification and resubmit the request.
Reason:
The recovery utility has detected an error in an MCF time stamp record. The record key is provided.
Action:
Contact your administrator.
Reason:
An error has occurred when sorting journal data set input for the recovery utility.
Action:
Contact your administrator.
Reason:
The named Stage occurs in records recovered from a journal data set, but is not defined in the current C1DEFLTS table.
Action:
Contact your administrator.
Reason:
The named Environment occurs in records recovered from a journal data set, but is not defined in the current C1DEFLTS table.
Action:
Contact your administrator.
Reason:
The recovery utility is trying to recover an Element from a journal tape, but cannot find the type for the Element defined in the current MCF.
Action:
Define the type, and resubmit the job.
Reason:
The recovery utility has detected an unrecognizable MCF.
Action:
Contact your administrator.
Reason:
The Environment or System specification in the recovery utility syntax contains an asterisk. These parameters must be specified explicitly.
Action:
Respecify the parameter and resubmit the request.
Reason:
Internal error.
Action:
Contact your administrator.
Reason:
Informational message. The recovery utility is skipping the current journal transaction.
Action:
None.
Reason:
The time stamp on a journal record has changed before the recovery utility reached the number of records in the transaction record count. This often happens because a journal file is missing.
Action:
Make sure that all appropriate journal files have been supplied as input to the recovery utility.
Reason:
The time stamp on a journal record has changed before the recovery utility reached the number of records in the transaction record count. This often happens because a journal file is missing.
Action:
Make sure that all appropriate journal files have been supplied as input to the recovery utility.
Reason:
The number of records in the recovered journal transaction does not correspond to the record count for that transaction. This often happens because a journal file is missing.
Action:
Make sure that all appropriate journal files have been supplied as input to the recovery utility.
Reason:
The recovery utility has encountered a processor group record on a journal tape that is out of sequence.
Action:
Contact your administrator.
Reason:
The recovery utility has found the member in a current base or delta library, but there is no footprint associated with the member.
Action:
Research the problem carefully, but it is likely that the member can be deleted.
Reason:
Informational message. This is the first message in the log portion of the Journal Recovery Execution report for each recovered base or delta journal record.
Action:
None.
Reason:
Informational message. This is the second message in the log portion of the Journal Recovery Execution report for each recovered base or delta journal record.
Action:
None.
Reason:
You have submitted a recovery utility job that requests both a LIST action and a RECOVER action. Each request can specify one or the other, but not both.
Action:
Respecify the job and resubmit the request.
Reason:
Informational message. While processing a delete transaction from a journal tape, the recovery utility checked a base or delta library for the member and did not find it. This indicates that the member has already been deleted.
Action:
None.
Reason:
Informational message. The current member/record update date and time stamp is more recent than the journal transaction. The recovery utility has therefore ignored the journal transaction.
Action:
None.
Reason:
This is the last message written for each successful recovery transaction in the log portion of the Journal Recovery Execution report.
Action:
None.
Reason:
Informational message. This is the first message in the log portion of the Journal Recovery Execution report for each recovered MCF or PCF transaction.
Action:
None.
Reason:
Informational message. This is the second message in the log portion of the Journal Recovery Execution report for each recovered MCF or PCF transaction. It specifies the CA Endevor SCM location associated with the transaction, and includes the number of the record type.
Action:
None.
Reason:
Informational message. The recovery utility has scheduled a batch job to build GENERATE SCL for the Element named earlier in this recovery record.
Action:
None.
Reason:
This is the last message in the Journal Recovery Execution Log. It indicates whether this run of the report was for a RECOVER or a LIST job, and the job return code.
Action:
None.
Reason:
If an Environment name appears in this message, the C1DEFLTS table does not reference a journal group ID in the ENVIRONMENT section for that Environment. If a Package name appears in the message, the C1DEFLTS table does not reference a journal group ID in the MAIN section.
Action:
Contact your administrator.
Reason:
The user who submitted the recovery request is not authorized to access the named Environment. The recovery utility will therefore ignore all journaled transactions pertaining to that Environment.
Action:
If you need to recover transactions related to the named Environment, a user with authority to access that Environment should resubmit the job.
Reason:
The recovery utility found no journal records that met the specified selection criteria.
Action:
Make sure the criteria was specified correctly.
Reason:
Informational message. This message indicates either the date and time of the last update of the named member, or that the recovery utility did not find the member.
Action:
None.
Reason:
Informational message. The first message for each recovery transaction. The message contains the number of the transaction, the date and time stamp from the journal data set, and the number of records in the transaction.
Action:
None.
Reason:
Informational message. This is the first message for each data set reported on in the data set activity portion of the Journal Recovery Execution Summary report.
Action:
None.
Reason:
Informational message. This message indicates the number of members or records created in the data set identified in the preceding JRCV100I message.
Action:
None.
Reason:
Informational message. This message indicates the number of members or records updated in the data set identified in the preceding JRCV100I message.
Action:
None.
Reason:
Informational message. This message indicates the number of members or records deleted in the data set identified in the preceding JRCV100I message.
Action:
None.
Reason:
Informational message. This message serves as the header for the
SCL statement portion of the Journal Recovery Execution Summary report. It
is followed by one or more JRCV106I messages.
Action:
None.
Reason:
Informational message. This message identifies the number of GENERATE SCL statements written for the named CA Endevor SCM location and classification.
Action:
None.
Reason:
Informational message. This message follows message JRCV105I if no SCL statements were written during the run of the recovery utility.
Action:
None.
Reason:
Informational message. This message follows message JRCV113I if no recovery activity occurred for a named data set during a run of the recovery utility.
Action:
None.
Reason:
Informational message. This message indicates the number of generate or delete processors executed for the specified location during a run of the recovery utility.
Action:
None.
Reason:
Informational message. This message indicates the number of transactions for a specific record type during a run of the recovery utility.
Action:
None.
Reason:
Informational message. This message indicates the CA Endevor SCM location associated with a data set named in message JRCV100I.
Action:
None.
|
Copyright © 2015 CA Technologies.
All rights reserved.
|
|