Report Termination

Reports can be terminated programmatically or through operator intervention.

Abnormal Programmatic Termination

A Report might programmatically terminate abnormally if certain errors occur; for example, a DMS II error or a severe arithmetic error.

When a Report encounters an unexpected DMS II error (for example, a LIMITERROR or a VERSIONERROR), the following process occurs:

  1. The Report terminates.

  2. If the logging option is set, the DMS II error is written into the log as a comment record.

  3. If the error is a DMS II Version Error, the Report is automatically flagged as No Recovery. The Report is not restarted if recovery is invoked.

  4. If there is an initiating station, it is notified of the abnormal termination of the Report, and the DMS II error message is shown on Page 2.

  5. A message is displayed on the ODT (Operator Display Terminal).

Operator Intervention

When you have signed on to the application you might terminate an associated Report, by using one of the Administration commands specified in the following table.

Command

Result

:TER

Terminates the Report unconditionally

:STR

Report sent to orderly End-of-Job:

  • Immediately, if still initializing

  • Immediately, if video browsing (non-ROC Reports only)

  • Immediately, if in Accept state

  • Otherwise, at the next Sleep CriticalPoint AUTO; or Accept logic command

:STO

Terminates the application and Reports:

  • Immediately, if still initializing

  • Immediately, if video browsing (non-ROC Reports only)

  • Otherwise, at the next Sleep CriticalPoint AUTO; or Accept logic command

>STOP

Terminates Video Reports if video browsing and non-ROC

Termination is unconditional

Refer to Administration Commands for more information on these commands.