Reason:
The function you are attempting against the CXX is not allowed for the release of the CXX. Here are possible causes:
Action:
Determine the reason and either perform the function on a current CXX, use the current release of code, or convert your CXX to the current release level.
Reason:
The DBUTLTY RECOVERY function with TSN= is processing and one or more informational messages are provided to show conditions that replace the variable x.
TSN TASK FOUND, RECOVER AS SAME TSN – occurs if the original task with the TSN has been found and the transaction is in a wait state waiting for the backward recovery to execute. This recovery execution executes as the same transaction in a different task area. It depends on the original task area to remain in its wait until the successful completion of this recovery. This message is normal and expected to acknowledge the proper environment for a TSN recovery from a forced spill.
TSN TASK NOT FOUND, RECOVER AS NEW TSN – occurs if the original task with the TSN has not been found. It must have completed normally or in error including being subject to REQABORT. With the task not waiting on this backward recovery, all row locks for maintenance transactions were fully released and are available to all other tasks areas for more maintenance. This function cannot use the same TSN but executes as a normal (new) transaction and has no relationship to the original transaction sequence number. With no row lock protection, this function maintenance succeeds or fails based on the rows being in the same state as they were when the original task completed.
Action:
None. This message is for information only.
Reason:
The DBUTLTY function RECOVERY with TSN= cannot be successfully completed because of one of the following specific conditions that replace the variable 'x'.
RXX EXCLUDES FIRST TSN LOG RECORD - occurs if the first log record for the TSN is missing from the provided RXX input files. This record and every record are critical to the success and must be provided.
RXX EXCLUDES LAST TSN LOG RECORD - occurs if the last log record for the TSN is missing from the provided RXX input files.
TSN TASK INVALID STATUS - occurs if the task containing the TSN is found but not currently displaying the status of waiting and having a DB00109 message. The transaction may still be running and, as such, is not subject to backward recovery.
PREVIOUS TSN RECOVERY TASK STATUS - occurs if a previous backward recovery for the TSN is found but not currently displaying the status of waiting and having a DB00109 message.
TSN IS NOT FULLY SPILLED - occurs if the original task has not had all its log records spilled to a Recovery File (RXX) or if a previous backward recovery for the TSN and running as the TSN has not had all its log records spilled.
Action:
For the first two conditions, research the needed RXX files including any required additional SPILL functions and provide all that are needed for successful completion.
For the other conditions, research the status of executing tasks and execute the function again when there is no conflict.
|
Copyright © 2014 CA.
All rights reserved.
|
|