DASD Calculation Chart › Providing Global Variable Database Control (Optional) › Usage Warning Messages

Usage Warning Messages

CA OPS/MVS also issues warning messages each time database usage increases by 5 percent above the threshold (for instance, at 85 percent, 90 percent, and 95 percent of capacity), even between GLOBALWARNINTVAL intervals. The usage levels triggering the warning messages are not reset in a CA OPS/MVS life cycle unless you change the GLOBALWARNTHRESH parameter to a different value. In this case, the high-usage level is reset to the threshold value.

The warning message OPS4290O, which can apply to either the permanent global variable database or the temporary global variable database, contains the following information:

• Whether the warning is for the temporary or the permanent global variable database
• Current percentage of the database that is full
• Number of blocks currently in use
• Total number of blocks in the database (determined by the value of the GLOBALMAX or GLOBALTEMPMAX parameter)
• Name of the program or rule, once executed, that caused the threshold to be met or exceeded. This program or rule may or may not be responsible for filling the database.

Note: CA OPS/MVS checks for the threshold being exceeded only when a new global variable is allocated or an existing global variable is extended. Therefore, the interval between the messages may be greater than the defined interval.

For an explanation of DASD allocation requirements for global variables see the chapter “Preparing Your System” in the Getting Started.

If either the permanent or the temporary global variable database fills completely, CA OPS/MVS issues the OPS1093I message. If this occurs, your automated operations will probably cease to function properly. Because of this, you should make use of the CA OPS/MVS threshold warning message that can alert you to the imminence of such a situation before a failure.