Implementing the NTS User Exit › How the NTS Exit Is Called

How the NTS Exit Is Called

NTS is initialized when your region starts and a subtask that acts as the driver for the exit is attached. The subtask mainline routines handle communications between the subtask and the NTS components in the main task.

When the subtask is attached, subtask mainline routines do the following:

1. Load the load module specified as the installation-supplied user exit.
2. Call the exit using conventional branching and linking.
3. Pass an initialization parameter list to the exit.

Note: To implement an NTS exit, you must define the exit name in the SAW parameter group. For more information, see the Installation Guide.

NTS Exit Execution

Because the user exit executes as part of a subtask, no restrictions are placed on the functions that the exit can perform. This is because the activities of the subtask do not impact the performance of the main task, and the exit subtask runs at a lower dispatching priority than the main task.

However, all processing of NTS session records on the output queue by the main task is delayed by processing occurring in the NTS user exit.