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.
Task rule type | Subtype | Unit | Value |
---|---|---|---|
Async requests |
RUN TRANSID commands |
No unit |
0 - 4294967295 |
Database requests |
SQL commands |
No unit |
0 - 4294967295 |
EXEC CICS® requests |
All EXEC CICS commands |
No unit |
0 - 4294967295 |
File requests |
DELETE commands |
No unit |
0 - 4294967295 These value ranges for requests or thousand requests apply to all subtypes of file request task rules. |
IBM® MQ requests |
MQ commands |
No unit |
0 - 4294967295 |
Named counter requests |
GET COUNTER commands |
No unit |
0 - 4294967295 |
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 |
0 - 4294967295 |
Start requests |
START commands |
No unit |
0 - 4294967295 |
Storage allocation |
24-bit shared storage allocated |
|
24-bit rule items: 0 - 16777215 31-bit rule items: 0 - 2147483647 64-bit rule items: 0 - 4294967295 |
Storage requests |
24-bit shared storage requests |
No unit |
0 - 4294967295 These value ranges for requests or thousand requests apply to all subtypes of storage request task rules. |
Syncpoint requests |
SYNCPOINT commands |
No unit |
0 - 4294967295 |
TD queue requests |
READQ TD commands |
No unit |
0 - 4294967295 These value ranges for requests or thousand requests apply to all subtypes of TD queue request task rules. |
Time |
CPU time |
Microseconds |
0 - 4294967295 A value of 86400 seconds equates to 24 hours. |
TS queue bytes |
All TS bytes written Note:
|
Bytes |
0 - 4294967295 All subtypes of the TS queue byte task rule have the same value ranges. |
TS queue requests |
All WRITEQ TS commands 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 |
0 - 4294967295 These value ranges for requests or thousand requests apply to all subtypes of TS queue request task rules. |
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.
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 @ # . / - _ |
|
Bundle available status Bundle enable status |
Bundle name |
1-8 characters Acceptable characters: A-Z a-z 0-9 $ @ # . / - _ % & ? ! : | " = ¬ , ; < > |
|
Bundle available status |
From available status |
AVAILABLE |
|
Bundle enable status |
From enable status |
DISABLED |
|
Bundle enable status |
To enable status |
DISABLED |
|
DB2® connection status |
From connection status |
CONNECTING |
|
File enable status |
File name |
1-8 characters Acceptable characters: A-Z 0-9 $ @ # |
|
File enable status |
From enable status |
DISABLED |
|
File enable status |
Open status |
CLOSED |
|
File open status |
From open status |
CLOSED |
|
IPIC connection status |
Connection name |
1-8 characters Acceptable characters: A-Z 0-9 $ @ # |
|
IPIC connection status |
From connection status |
ACQUIRED |
|
Message |
Message ID |
9 characters Format: DFHXXnnnn or EYUXXnnnn Where:
|
|
MRO connection status |
Connection name |
1-4 characters Acceptable characters: A-Z 0-9 $ @ # |
|
MRO connection status |
From connection status |
ACQUIRED |
|
Message |
Message insert |
0-255 characters Acceptable characters: All characters, including white space. 1 |
|
Program enable status |
Program name |
1-8 characters Acceptable characters: A-Z 0-9 $ @ # |
|
Program enable status |
From enable status |
DISABLED |
|
User tasks |
Percentage of MXT |
|
|
Tranclass tasks |
Transaction class |
1-8 characters Acceptable characters: A-Z 0-9 $ @ # |
|
Tranclass tasks |
Percentage of MAXACTIVE |
|
|
Transaction abend |
Abend code |
1-4 characters Acceptable characters: A-Z a-z 0-9 $ @ # . / - _ % & ? ! : | " = ¬ , ; < > |
|
Bundle enable status |
Transaction ID |
1-4 characters Acceptable characters: A-Z a-z 0-9 $ @ # . / - _ % & ? ! : | " = ¬ , ; < > |
|
Bundle enable status |
User ID |
1-8 characters Acceptable characters: A-Z 0-9 $ @ # |
|