Your Browser is not longer supported

Please use Google Chrome, Mozilla Firefox or Microsoft Edge to view the page correctly
Loading...

{{viewport.spaceProperty.prod}}

Error handling

&pagelevel(3)&pagelevel

ILCS normally reports the occurrence of an error to the calling program via a return code. In the following situations, however, this is not possible since there is no caller:

  • An exception occurs in a contingency routine (e.g. no resources).

  • A return to the co-routine adapter is effected from IT0CREND.

These situation are treated as internal errors in ILCS.

The following error situations are treated by the standard event handler (SEH) as internal errors for which normal SEH error recovery - triggering the error again - is not possible:

  • Data exception. These are SEH exceptions that have changed the data in such a way that the exceptions cannot be triggered again.

  • An SEH error recovery routine reports that an STXIT event is to be treated like a data exception.

In the event of internal errors:

  • an error message is issued (prerequisite for issuing error messages is CRTE-MSG V1.3)

  • debugging information is stored in the Prosys Common Data Area (PCD), and

  • the application is terminated abnormally with the TERM macro.

Values are entered in the fields in the PCD the first time an error occurs which causes abnormal termination. Sequence errors are ignored.
The PCD fields are also supplied with values if abnormal termination is handled by the TERM macro by specifying a user exit.

The possible values of the PCD fields M7TYP, M7DIA and M7ADR are listed below.

The user can also control the TERM macro via the contents of certain PCD fields. You will find a description of how to initialize the corresponding fields in section “Control of the TERM macro by the user”.