CA NetMaster uses the NTSLOG database in a slot-managed fashion. This means that as session instances are logged, space is reserved for the records for that session combination. The data set grows as CI/CA splits occur. Eventually, as all combinations to be recorded occur for the site, the database stabilizes. When this occurs, the NTSLOG mirrors the needs of the NTS session logging options in terms of session pairs and number of session instances.
When the NTSLOG data set has grown and stabilized, perform a reorganization. This once only cleanup removes all of the splits and reclaims any split CAs not used. The new define can have a more exact space allocation (reducing multiple extents). It must retain the minimal free space specifications. Also, if a VSAM analyser is available, analyse the data set (particularly the index) and determine an optimal index CI size based on data CI/CA size, average record length, and key compression statistics. CI size changes must be reflected in the region's LSR pool definitions.
Ensure that you avoid the following: