Standalone Reports

Your Reports might be initiated in a standalone mode; that is, they might be initiated without your application being active.

Initiating Standalone Reports

Standalone Reports can be initiated by using:

Note: If you initiate reports using WFL, EPILOG_TIDYUP runs at the completion of every report as well as at the closure of every update for an online application.Refer to Initiating RIP from a WFL for more information on task EPILOG_TIDYUP.

Recovery of Standalone Reports

Standalone Reports might be run in recovery with the following settings, where mix is the mix number of the original task:

SW7=TRUE; TASKVALUE=0 mix 0 ;

Standalone Reports are seen by :REP RECOVER and deleted by :DEL. However, it is not possible for Reports to be rerun in recovery by the System Supervisor program (LSS). They must be rerun as Standalone Reports. They are distinguished in the :REP RECOVER output by five pound signs (#####) before the Report name.

Standalone Reports that abort do not remove their recovery record from GLB-CRITIC unless they are restarted manually in recovery mode and successfully complete.

Capabilities and Restrictions

Standalone Reports: