Reports that terminate abnormally is recovered without forcing the entire application into recovery.

The System Supervisor program (LSS) attempts to reinitiate the Report twice. If the Report again terminates abnormally, the Report is terminated with the NO.RECOVERY flag set, and notification is sent to the ODT (and to the attached terminal, if the Report was initiated by using a :RUN command), and the Report is not reinitiated.

If a Report that is reinitiated by LSS processes past the original point of abnormal termination and performs a CriticalPoint command or Sleep and has performed accepts or an auto, the retry count is returned to zero. Therefore, it might reinitiate a further two times.

If the Report fails due to a DMS Limit Error or Version Error, it is terminated NO.RECOVERY immediately, on the first failure.

Reports that terminate abnormally are restarted at the last CriticalPoint logic command or (in its absence), at Beginning-of-Job (BOJ). The database is backed out to the last Sleep command, CriticalPoint command, or BOJ. This means that any Accept input received before that Sleep or CriticalPoint command are not recovered. Accept input is recovered from the last CriticalPoint command, Sleep command, or BOJ, up to the point of failure.

Parameters

Parameters for the Wake logic command is not saved for recovery.

Any parameter information passed to the Report on initiation is automatically saved, and is passed again during recovery.

Extract Files

If a Report P-DSs and is restarted in recovery mode, then after the Report has completed successfully, the temporary extract files from the original Report remain on DISK. These temporary files might be used for debugging purposes. However, if you do not require these files, the use of a CriticalPoint command in your Report ensures that these files are deleted if the Report is restarted in recovery mode.

Recovery of extract files in the online system is more difficult to do. The user cannot use critical points in the online system. The most that is done to support recovery is that extract files are closed at the end of a transaction. The nature of the online architecture is such that there is no guarantee for recovery of extract files in the online system.

ROC

If the Report Output Control system (ROC) was in use by Reports being recovered, it is recovered. Enter ROCI from the Ispec Selection screen (Page 2) of your application to access ROC again. ROC video browsing is not restored, and will have to be reinitiated.

Recovery Information

When a Report is terminated abnormally (excluding a :TER DISCARD Administration command), the recovery information relevant to the Report is deleted or retained depending upon the setting of the Extend Report Recovery Segment configuration property under the Runtime Options under General category.

If this property is set to Y, Report recovery information is retained and can be used for manually initiated Report recovery. Refer to Manually Initiated Report Recovery for more information.

If the Report fails due to a DMS Version Error, Open Error, or a :TER DISCARD command, recovery information will not be retained. Only the Report that fails enters recovery. Any other Reports continues independently. Transaction independence is provided by DMS II.

References

Refer to the Agile Business Suite Programming Reference Manual for more information on the value of built-in attributes in recovery.

Refer to :TER in Administration Commands for more information on the recovery effects of the :TER command options.

Refer to Report Operations for more information on Reports.