NTS Storage Estimates › Active Session Data

Active Session Data

All active session data which has been captured by NTS is kept in main memory. This storage is above the 16 MB line. The actual amount of storage required for any given network configuration varies depending upon the NTS processing options. As a guide, the following scenario may be useful.

Example

Consider an NTS region operating in a single VTAM domain that contains 500 terminals, of which 400 are continually in session with one of several applications.

• If all active sessions (that is the 400 LU-LU sessions, 500 SSCP-LU sessions, plus a handful of SSCP-PU sessions) are to be kept by NTS, the storage requirement would be approximately 350K.
• By keeping LU-LU sessions only, this is reduced to about 180K.
• Gathering accounting data takes no extra storage.
• To collect RTM data for all 400 LU-LU sessions would require an extra 40K.
• If the default trace queue limits were used, and trace data collected for every LU-LU session, then this could reach a requirement of up to an extra 700K. However, it is not usual for all sessions to be concurrently holding the maximum number of trace PIUs in storage. New sessions take some time to reach this wrap level, while for ended sessions, the trace data is logged then purged from storage.

When Using NTS-SI

If your NTS region is configured to receive session awareness data through NTS Single Image, this must be considered when calculating the storage requirements of NTS. The local NTS receives session awareness from the remote NTS and maintain this data in storage. This data includes SSCP-SSCP, SSCP-PU, SSCP-LU and LU-LU session data. Session data (trace, RTM, and accounting) is solicited from the remote NTS when requested and is discarded when the data is not being viewed.