Starting Sysview there are a lot of Threshold messages with the Warning and problem limits with a value of 0
For example:
12.01.00 STC01234 GSVX321W (MVSDATA) Threshold SYSTEM ASIACT * PROBLEM 500
500 V=159 W=0 P=0 UPPER 0.000000 * *
500 Desc='Address spaces active '
500 Policy=000506C0
12.01.00 STC01234 GSVX321W (MVSDATA) Threshold SYSTEM ASIAPPC * PROBLEM 501
501 V=0 W=0 P=0 UPPER 0.000000 * *
501 Desc='Address spaces APPC transactions '
501 Policy=00050880
and finally an error message GSVX998E with the GSS_SCHED_IMOD failing with rc 20 rs 31
12.02.00 STC01234 GSVX998E (MVSDATA) ISER008E GSS_SCHED_IMOD failed, rc 20 rs 31
12.02.00 STC01234 GSVX321W (MVSDATA) Threshold JOB JOBCLOCK HIS PROBLEM 601
601 V=32.1DAYS W=0.000000 P=0.000000 UPPER 0.000000 0053
601 STC02000
601 Desc='Wall clock time '
601 Policy=0005EC00
The System - Address Space Activity Thresholds (ASIACT,ASIAPPC...) are defined in the member MVSTHRSH of *.CNM4BPRM
Normally these definitions are after the )EOF sentence so are inactive .
For example:
)EOF Logical end of file
*==================================================
* List of all thresholds
*==================================================
*. . . . . . . . . . . . . . . . . . . . . . . . .
* System - Address Space Activity Thresholds
* Resource = not applicable
* The RSCE keyword is not required
*. . . . . . . . . . . . . . . . . . . . . . . . .
DEFINE ASIACT RSCE none LIMIT 0
DEFINE ASIAPPC RSCE none LIMIT 0
...
When these definitions are before the )EOF the Thresholds are enabled with a value of 0 for the PROBLEM definition.
Code )EOF before the System - Address Space Activity Thresholds