EXIT - define event exits

The EXIT control statement allows you to define event exits which are used in the application, except for the event exits VORGANG and HTTP.

For the event exits FORMAT and INPUT, you may only specify a single EXIT statement for each KDCDEF run.
For the event exits START and SHUT, you may specify up to eight EXIT statements. However, the specifications for the PROGRAM= operand must differ for the EXIT statements.

When starting or terminating a UTM process, all of the programs defined as START or SHUT exits are called one after the other. The sequence of the EXIT statements in the KDCDEF run determines the sequence in which openUTM activates the START or SHUT exit program.

Further information on event exits can be found in the openUTM manual „Programming Applications with KDCS”.

Event exits on BS2000 systems:
The event exits START, SHUT, INPUT and FORMAT must not be assigned to a load module generated with LOAD-MODULE LOAD-MODE=ONCALL.

The event services MSGTAC, BADTACS and SIGNON must be defined using the TAC statement.

EXIT	PROGRAM=objectname ,USAGE={ START |          SHUT |          ( INPUT, { ALL | FORMMODE | LINEMODE | USERFORM1 } ) |           FORMAT1 }

¹FORMAT and USERFORM are only permitted on BS2000 systems

PROGRAM=	name Name of the program containing the functions to be executed for the event exit. A PROGRAM statement with this name (objectname) must be issued.
USAGE=	Type of event exit
START	Used as event exit START
SHUT	Used as event exit SHUT
INPUT	Used as event exit INPUT Additionally you must specify the type of INPUT exit:
ALL	Event exit INPUT, which handles messages of all format control characters as well as LINEMODE messages. If you specify ALL here, this is the only event exit INPUT of the application. Further INPUT event exits cannot be defined.
FORMMODE	Event exit INPUT for +, *, and #formats
LINEMODE	Event exit INPUT for LINEMODE messages
USERFORM	Event exit INPUT for -formats
FORMAT	Used as event exit FORMAT