Policy conditions

Conditions defined in the rule trigger the requested action when they are met. A task rule defines only one condition (a threshold), which triggers the requested action when it is met. A system rule can define multiple conditions, all of which must be met to trigger the requested action.

Task rule conditions

The following table includes the attributes that you can specify in the policy definition editor when you define a task rule condition. You can define multiple task rules of the same rule type with the same or different threshold values. When multiple task rules with the same threshold are deployed, the rules are processed in the following order: message action rules, event action rules, and then abend action rules.

Table 1. Supported task rule attributes
Task rule type	Subtype	Unit	Value
Async requests	RUN TRANSID commands	No unit Thousands	0 - 4294967295 0 - 4294967
Database requests	SQL commands DLI commands (EXEC DLI or CALLDLI)	No unit Thousands	0 - 4294967295 0 - 4294967
EXEC CICS® requests	All EXEC CICS commands	No unit Thousands	0 - 4294967295 0 - 4294967
File requests	DELETE commands READ commands READNEXT commands READPREV commands READ UPDATE commands REWRITE commands STARTBR commands WRITE commands	No unit Thousands	0 - 4294967295 0 - 4294967 These value ranges for requests or thousand requests apply to all subtypes of file request task rules.
IBM® MQ requests	MQ commands	No unit Thousands	0 - 4294967295 0 - 4294967
Named counter requests	GET COUNTER commands GET DCOUNTER commands	No unit Thousands	0 - 4294967295 0 - 4294967
Program requests	LINK commands Note: As well as LINK commands, INVOKE APPLICATION commands are also included in the count for program request, but are not a separate subtype.	No unit Thousands	0 - 4294967295 0 - 4294967
Start requests	START commands	No unit Thousands	0 - 4294967295 0 - 4294967
Storage allocation	24-bit shared storage allocated 24-bit task storage allocated 31-bit shared storage allocated 31-bit task storage allocated 64-bit shared storage allocated 64-bit task storage allocated	Bytes Kilobytes Megabytes Gigabytes Bytes Kilobytes Megabytes Gigabytes Bytes Kilobytes Megabytes Gigabytes	24-bit rule items: 0 - 16777215 0 - 16383 0 - 15 0 31-bit rule items: 0 - 2147483647 0 - 2097151 0 - 2047 0 - 1 64-bit rule items: 0 - 4294967295 0 - 4294967295 0 - 4294967295 0 - 4294967295
Storage requests	24-bit shared storage requests 24-bit task storage requests 31-bit shared storage requests 31-bit task storage requests 64-bit shared storage requests 64-bit task storage requests	No unit Thousands	0 - 4294967295 0 - 4294967 These value ranges for requests or thousand requests apply to all subtypes of storage request task rules.
Syncpoint requests	SYNCPOINT commands	No unit Thousands	0 - 4294967295 0 - 4294967
TD queue requests	READQ TD commands WRITEQ TD commands	No unit Thousands	0 - 4294967295 0 - 4294967 These value ranges for requests or thousand requests apply to all subtypes of TD queue request task rules.
Time	CPU time Elapsed time	Microseconds Milliseconds Seconds	0 - 4294967295 0 - 86400000 0 - 86400 A value of 86400 seconds equates to 24 hours.
TS queue bytes	All TS bytes written Auxiliary TS bytes written Main TS bytes written Shared TS bytes written Note: The WRITEQ subtype is used to set a threshold for the amount of data that is written to all TSQs combined. The other subtypes are used to set a threshold for a specific type of TSQ. Data that is written by both WRITE and REWRITE requests count towards the total, and REWRITE requests are treated as WRITE operations, in that the count is incremented by the total size of the REWRITE, and not the delta between the original WRITE and REWRITE. Data is counted only if the WRITEQ is performed successfully.	Bytes Kilobytes Megabytes Gigabytes	0 - 4294967295 0 - 4194303 0 - 4095 0 - 3 All subtypes of the TS queue byte task rule have the same value ranges.
TS queue requests	All WRITEQ TS commands READQ TS commands WRITEQ TS commands to auxiliary WRITEQ TS commands to main WRITEQ TS commands to shared Note: The READQ and WRITEQ subtypes are used to set a threshold for the total number READ or WRITE requests to the auxiliary, main, and shared TSQs combined. The other WRITEQ subtypes are used to set a threshold for the number of WRITE requests to a specific type of TSQ.	No unit Thousands	0 - 4294967295 0 - 4294967 These value ranges for requests or thousand requests apply to all subtypes of TS queue request task rules.

Note: When you select a unit and specify a value for the threshold in your policy task rule, be aware that the granularity decreases as the size of the unit increases. However, if you cannot specify a high enough value with a smaller unit, you might be able to specify an appropriate value by using a larger unit. For example, if you create a storage request task rule, and want to set a threshold for 64-bit shared storage requests greater than 4294967295 bytes, you cannot use bytes as the unit, but you might be able to set your threshold by using kilobytes and entering an appropriate kilobyte value in the Value field in the policy definition editor.

Important:

You can use CICS monitoring data to determine an appropriate threshold to set for a task rule, but be aware that the number of requests that are counted by CICS monitoring and the requests that are counted by CICS policy might differ. This is because policy counts only EXEC CICS API requests, but monitoring also includes internal requests. Therefore, requests that do not go through the EXEC CICS layer are counted by CICS monitoring, but are not included in the policy count. To use the policy to count WRITEQ TD requests as an example, if a user task issues an EXEC CICS SPI request to change the status of a CICS resource, message DFHAP1900 is written to the transient data queue CADS; this request is counted in CICS monitoring data but is not included in the policy count.

For information about CICS monitoring data that you can use to determine an appropriate threshold to set for a CICS task rule , see CICS monitoring data for determining task rule thresholds.

System rule conditions

The following table includes the conditions that you can specify in the policy definition editor when you define a system rule condition.

Table 2. Supported system rule conditions
System rule type	Condition	Condition value	Condition operator
Bundle available status Bundle enable status	Bundle id	1-64 characters Acceptable characters: `A-Z a-z 0-9 @ # . / - _`	all does not equal does not start with equals starts with
Bundle available status Bundle enable status	Bundle name	1-8 characters Acceptable characters: `A-Z a-z 0-9 $ @ # . / - _ % & ? ! : \| " = ¬ , ; < >`	all does not equal does not start with equals starts with
Bundle available status	From available status To available status	AVAILABLE SOMEAVAIL UNAVAILABLE	does not equal equals
Bundle enable status	From enable status	DISABLED DISABLING ENABLED ENABLING INITIAL	does not equal equals
Bundle enable status	To enable status	DISABLED DISABLING DISCARDING ENABLED ENABLING	does not equal equals
DB2® connection status	From connection status To connection status	CONNECTING CONNECTED DISCONNING NOTCONNECTED	does not equal equals
File enable status File open status	File name	1-8 characters Acceptable characters: `A-Z 0-9 $ @ #`	all does not equal does not start with equals starts with
File enable status	From enable status To enable status	DISABLED DISABLING ENABLED UNENABLED UNENABLING	does not equal equals
File enable status	Open status	CLOSED CLOSEREQUEST OPEN	all does not equal equals
File open status	From open status To open status	CLOSED CLOSEREQUEST OPEN	does not equal equals
IPIC connection status	Connection name	1-8 characters Acceptable characters: `A-Z 0-9 $ @ #`	all does not equal does not start with equals starts with
IPIC connection status	From connection status To connection status	ACQUIRED FREEING OBTAINING RELEASED	does not equal equals
Message	Message ID	9 characters Format: DFH`XXnnnn` or EYU`XXnnnn` Where: `X` is any uppercase character A-Z. `n` is any digit 0-9. `XX` is not EC, EP or MP for a DFH message.	all equals starts with
MRO connection status	Connection name	1-4 characters Acceptable characters: `A-Z 0-9 $ @ #`	all does not equal does not start with equals starts with
MRO connection status	From connection status To connection status	ACQUIRED RELEASED	does not equal equals
Message	Message insert	0-255 characters Acceptable characters: All characters, including white space. 1	does not equal does not start with equals starts with
Program enable status	Program name	1-8 characters Acceptable characters: `A-Z 0-9 $ @ #`	all does not equal does not start with equals starts with
Program enable status	From enable status To enable status	DISABLED ENABLED	does not equal equals
User tasks	Percentage of MXT	Valid values for goes higher than: 60, 70, 80, 90, 100 Valid values for goes lower than: 50, 60, 70, 80, 90	all goes higher than goes lower than
Tranclass tasks	Transaction class	1-8 characters Acceptable characters: `A-Z 0-9 $ @ #`	all does not equal does not start with equals starts with
Tranclass tasks	Percentage of MAXACTIVE	Valid values for GHT: 60, 70, 80, 90, 100 Valid values for GLT: 50, 60, 70, 80, 90	all goes higher than goes lower than
Transaction abend	Abend code	1-4 characters Acceptable characters: `A-Z a-z 0-9 $ @ # . / - _ % & ? ! : \| " = ¬ , ; < >`	all does not equal does not start with equals starts with
Bundle enable status Bundle available status DB2 connection status File enable status File open status Message MRO connection status Program status Transaction abend	Transaction ID	1-4 characters Acceptable characters: `A-Z a-z 0-9 $ @ # . / - _ % & ? ! : \| " = ¬ , ; < >`	all does not equal does not start with equals starts with
Bundle enable status Bundle available status DB2 connection status File enable status File open status IPIC connection status Message MRO connection status Program status Transaction abend	User ID	1-8 characters Acceptable characters: `A-Z 0-9 $ @ #`	all does not equal does not start with equals starts with

Note: 1 When the "does not start with" or "starts with" condition operator is specified, at least one character must be specified.