EXIT13 Socket Monitoring
Purpose
EXIT13 can be used to prevent the STOP and ACTIVATE commands from being issued against a socket. You can also use it to override the STOP or ACTIVATE commands.
EXIT13 is called for both STOP and ACTIVATE processing.
Format
Usage
You can use Exit13 to prevent the STOP and ACTIVATE commands from being issued against a socket, or to override the STOP or ACTIVATE commands. Exit13 be called for both STOP and ACTIVATE processing. The input that is available to this exit includes the following task global variables:
- FKX_Command
- STOP or ACTIVATE command as coded in the socket policy
- FKX_Delay
- Delay time between STOP and ACTIVATE commands
- FKX_Action
- Identifies type of action, STOP or ACTIVATE
- FKX_CmdType
- Identifies the type of command z/OS®, NETV, TSO, or UNIX
You can choose the following task global variables with this exit:
- FKX_Command
- Modifies the STOP or ACTIVATE command
- FKX_Delay
- Modifies the delay time between the STOP and ACTIVATE commands
- FKX_CmdType
- Modifies the type of command, z/OS , NETV, TSO, or UNIX
When zero (0) is the return code either the STOP or ACTIVATE command runs.
When a nonzero return code is received from the user exit, the STOP command not be issued, a DELAY is not valid, and the user exit attempt to process the ACTIVATE command. If the nonzero return code is for an ACTIVATE command, ACTIVATE is not attempted. AON recovery monitoring still occurs.
