Your Browser is not longer supported

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

{{viewport.spaceProperty.prod}}

BCAM exit (036)

&pagelevel(3)&pagelevel

This exit permits a check to be kept on requests for connections to system applications (e.g. $DIALOG). The exit routine is called when BCAM recognizes that a local or remote partner wishes to set up a connection to a system application.

The following information is passed to the exit routine:

R1 = A($SYSX parameter area)
R12 = A(TPR program manager)
R13 = A(save area of calling component)
R14 = A(indirect return)
R15 = A(exit routine)

The parameter area has the following format:

fun

typ1

id1

typ2

id2

0

1

2



fun =

Function of the exit routine (field contents: X’01’).

typ =

Function type; initially only one type exists, with the code X’01’.
X’01’ means monitoring the connections to system applications.

id =

Application ID.
id1 is the called application, id2 the calling application.

The application name/processor name are supplied, resulting in the following structure:


01

01

called appl

own proc

01

calling appl

partner proc

00

01

02

0A

12

13

1B        22



called appl:

Name of the system application called.

own proc:

Name of the local processor.

calling appl:

Name of the calling application.

partner proc:

Name of the partner processor containing the calling application.

Warning

Only a comparison of names should be performed in the exit routine. Before the names (IDs) are accessed, the type must be checked because this can change the format (in particular the length) of the ID. An errored exit routine can cause the communication system (DCM) to crash.

Return code for the calling system component in the $SYSX parameter area.