Understanding XBM options

The period of time (in seconds) over which statistical data is gathered for interval (short-term) statistics

While XBM is running, it gathers statistics constantly and resets statistics at the beginning of each interval. The default value is 3600 seconds. When XBM is idle after processing large numbers of snapshot data sets, maximizing the statistics interval might result in reduced CPU consumption.

The record type to use for writing XBM data to SMF

SMF reserves record types 200 through 255 for user-written records. Choose a record type that is not in use, and have your system programmer activate the user type. The default value is type 245.

The MVS console route codes that XBM uses to send messages to the consoles for display

For more information, see the IBM MVS/ESA Routing and Descriptor Codes document. The default values are codes 02 and 11.

Whether to prevent storage allocations for the extended buffer that exceed the system’s available resources

The default value is Yes, which limits excessive cache. With this setting, XBM deactivates an active configuration that contains a cache specification exceeding available resources. XBM does not fall back to the previously active configuration. You must change the configuration or activate another configuration.

The following rules apply to Limit excessive cache:

• XBM does not check ESO hiperspace caches.
• XBM checks fixed virtual storage caches against the available real storage frames. If the cache is larger than the available amount, XBM does not create the cache and deactivates the configuration.
• XBM checks pageable virtual storage and data space caches against the frames available in auxiliary storage. If the cache is larger than the available amount, XBM does not create the cache and deactivates the configuration.

Whether to enable XBM to convert messages that are issued in the XBM address space, such as SYSPRINT and trace messages to uppercase

The default value is No.