The space requirements of the NTS database vary according to the amount of data collected and logged. To store a single session incidence for a session name pair requires approximately 800 bytes. Each additional session incidence requires an extra amount of approximately 350 bytes. Further requirements are an extra 128 bytes for each record of session accounting or RTM data, and around 1200 bytes if trace data is logged (assuming the default trace queue depths are used).
Hence, for the default session keep count of 10 session incidence records per session name pair, the total database space requirement per session name pair is as follows (approximately):
Extrapolating further, with a 500-terminal network in which up to six different applications can be used by all terminals, this translates to an overall database storage requirement of the following (approximately):
Follow the sizing formula and calculate a primary space allocation. Allow an additional 25% primary allocation for growth, and provide a 5% secondary allocation and index allocation. For example, if the calculation indicates that the data requires 80 cylinders, use CYLS(100 5) for the data allocation and CYLS(5 1) for the index allocation.
Note: These figures are intended as a guide only for the initial implementation, as in operation many changing factors can affect the amount of data stored in the NTS database.