Network Tracking System › Output Processing

Output Processing

Session records can be queued for output processing by NTS for any of the following reasons:

• Session start notification—applies only to sessions for which accounting information has been requested
• Forced logging by an operator through an NTSMOD command
• Session awareness close processing when CLOSE=ALL is specified on SAW STOP
• Normal end-of-session processing

For sessions placed on the output queue, logging commences immediately after one of the following:

• Session start notification (accounting information is logged)
• Being force-logged by an operator
• Being closed by session awareness close processing when WAIT=NO is specified on SAW STOP

How Session End Processing Works

All data associated with an active session is kept in storage until the session ends. When termination notification for a session is received from VTAM, NTS queues the session for output processing, which occurs as follows:

1. Firstly, NTS correlates all session data, such as session awareness data and any other statistical or problem-determination data, waiting for the correlation interval if necessary.
2. This final session data is then passed to a user exit, if one is active, and logged in the NTS database (unless the user exit suppresses logging).
3. When output processing is complete, the session data is purged from storage and is subsequently available (in the NTS database) as historical data only.

NTS User Exit Processing

If an exit is defined, all session records scheduled for logging (this is determined by the record type) are first passed to this exit. The exit can perform additional record processing, and can set a flag to indicate that the record be ignored by the subsequent NTS logging function.