If the Extend Report Recovery Segment configuration property under the Runtime Behavior category is set to True, Report recovery information is retained after the failure of the automatic recovery attempts. You can use this information to manually initiate Report recovery.

Before manually initiating Report recovery, ensure that you have corrected the problem that caused the failure of the automatic recovery. This might mean such things as increasing the DMS limits on an Ispec through the Population Change facility of the Database Management Utility (DMU). Refer to Diagnostic and Management Utilities for more information on DMU.

You can manually initiate Report recovery in one of the following ways:

These ways are discussed in the following subsections.

You should use the same method you initially used to run the Report. In the case of Reports initiated from Ispecs, these might be resubmitted by using the :RUN Administration command.

Manually Initiating Online Report Recovery

To manually initiate Report recovery, you require the key under which the recovery information is retained. This can be accessed by using the following Administration command:

:REP RECOVER

This lists Reports that have recovery information stored, along with their key values and other information. If necessary, further screens of Report details can be displayed by entering:

:REP RECOVER key

The key value gives the starting point for the next screen display.

Then restart the Report, using the following Administration command:

:RUN report RECOVER key device

The Report restarts from the last Sleep or CriticalPoint command prior to its abnormal termination.

If the key given is not for the Report name specified, then the following error message is returned:

INVALID REPORT IDENTIFICATION

Recovery information is stored by key, and can only be deleted by using the following Administration command:

:DEL key

Refer to Administration Commands for more information on Administration commands used with Report recovery.

Manually Initiating RIP Report Recovery

To manually initiate Report recovery under the batch Report Initiation Program (RIP), first obtain the recovery information key by using the following Administration command:

:REP RECOVER

This lists Reports that have recovery information stored, along with their keys and other information.

Then restart the Report under RIP, by entering:

RUN $NGEN28/RIP ("system/report");TARGET = key

When you are using extended Report Recovery, do not include a parameter or file equates when you attempt to recover a Report if you want your original parameter and file equates to be used automatically.

In all other respects, the procedure is the same as for Online Report Recovery.

Manually Initiating Recovery of Standalone Reports

Because a Standalone Report's recovery record is not removed from GLB-CRITIC unless the Report is manually restarted and successfully completes, recovery of a failed Standalone Report should be initiated manually.

To manually initiate recovery of a Standalone Report, make the following settings (where mix is the mix number of original task):

SW7=TRUE;TASKVALUE=0 mix 0;

For example, if the original mix number of the Report is 53967, then you would make the following settings:

SW7=TRUE;TASKVALUE=539670;

In all other respects, the procedure is the same as for Online Report Recovery.