Policy rule conditions
Conditions defined in the rule trigger the requested action when they are met. Different rule types support different conditions. Task rules and system rules share some condition filters such as the Transaction ID and User ID. For task rules, you can also specify thresholds for supported attributes as filters.
For available policy rule types, see Policy system rules and Policy task rules.
The minimum CICS® release that is required for each rule type can vary. The required CICS release for each rule can be found in Policy schema versions or in the policy definition editor.
Task rule conditions
The following two tables include the attribute thresholds and filters you can specify as task rule conditions in the Policy Definition editor.
Specify thresholds for the following attributes as filters. 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 |
Container storage |
Container storage used Note: This container storage rule tracks
both explicitly occurred storage on CHANNEL containers such as PUT CONTAINER
(CHANNEL), PUT64 CONTAINER, DELETE CONTAINER
(CHANNEL), and FETCH CHILD CHANNEL, and implicitly occurred storage for
CHANNEL containers, for example, START TRANSID CHANNEL, RUN TRANSID
CHANNEL CHILD and so on.
|
Bytes |
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: |
31-bit shared storage allocated |
|
31-bit rule items: |
|
64-bit shared storage allocated |
|
64-bit rule items: |
|
All storage allocated |
Bytes |
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:
|
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.
The following filters are provided to restrict the effect of the rules to specific user tasks:
Task rule type | Condition | Condition value | Condition operator |
---|---|---|---|
All task rule types |
Transaction ID |
1-4 characters Acceptable characters:
|
|
All task rule types |
User ID |
1-8 characters Acceptable characters:
|
|
System rule conditions
The following table lists the condition filters that you can specify in the Policy Definition editor when you define a system rule. You can use them to restrict the rule to certain status changes or user tasks.
System rule type | Filter | Filter value | Filter operator |
---|---|---|---|
AID threshold |
AID threshold |
0-65535 |
|
Bundle available status |
Bundle ID |
1-64 characters Acceptable characters:
|
|
Bundle available status |
Bundle name |
1-8 characters Acceptable characters:
|
|
Bundle available status |
From available status |
AVAILABLE |
|
Bundle enable status |
From enable status |
ANY |
|
Bundle enable status |
To enable status |
ANY |
|
Compound condition | See Table 4. | ||
DBCTL connection status |
From connection status |
|
|
DBCTL connection status |
To connection status |
|
|
DB2® connection status |
From connection status |
CONNECTING |
|
File enable status |
File name |
1-8 characters Acceptable characters:
|
|
File enable status |
From enable status |
DISABLED |
|
File enable status |
Open status |
CLOSED |
|
File open status |
From open status |
CLOSED |
|
IBM MQ connection status |
From connection status |
|
|
IPIC connection status |
Connection name |
1-8 characters Acceptable characters:
|
|
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:
|
|
MRO connection status |
From connection status |
ACQUIRED |
|
Message |
Message insert |
0-255 characters Acceptable characters: All characters, including white space. 1 |
|
Pipeline enable status |
Pipeline name |
1-8 characters Acceptable characters:
|
|
Pipeline enable status |
|
|
|
Pipeline enable status |
To enable status |
DISABLED |
|
Program enable status |
Program name |
1-8 characters Acceptable characters:
|
|
Program enable status |
From enable status |
DISABLED |
|
User tasks |
Percentage of MXT |
|
|
Tranclass tasks |
Transaction class |
1-8 characters Acceptable characters:
|
|
Tranclass tasks |
Percentage of MAXACTIVE |
|
|
Transaction abend |
Abend code |
1-4 characters Acceptable characters:
|
|
Bundle enable status |
Transaction ID |
1-4 characters Acceptable characters:
|
|
Bundle enable status |
User ID |
1-8 characters Acceptable characters:
|
|
Condition type | Filter | Filter value | Filter operator |
---|---|---|---|
Bundle available status |
Bundle ID |
1-64 characters Acceptable characters:
|
|
Bundle available status |
Bundle name |
1-8 characters Acceptable characters:
|
|
Bundle available status |
To available status |
AVAILABLE |
|
Bundle enable status |
To enable status |
ANY |
|
DB2 connection status |
To connection status |
CONNECTING |
|
DBCTL connection status |
To connection status |
CONNECTED |
|
File enable status |
File name |
1-8 characters Acceptable characters:
|
|
File enable status |
To enable status |
DISABLED |
|
File open status |
To open status |
CLOSED |
|
IBM MQ connection status |
To connection status |
CONNECTING |
|
IPIC connection status |
Connection name |
1-8 characters Acceptable characters:
|
|
IPIC connection status |
To connection status |
ACQUIRED |
|
MRO connection status |
Connection name |
1-4 characters Acceptable characters:
|
|
MRO connection status |
To connection status |
ACQUIRED |
|
Pipeline enable status |
Pipeline name |
1-8 characters Acceptable characters:
|
|
Pipeline enable status |
To enable status |
DISABLED |
|
Program enable status |
Program name |
1-8 characters Acceptable characters:
|
|
Program enable status |
To enable status |
DISABLED |
|
- 1 When the "does not start with" or "starts with" condition operator is specified, at least one character must be specified.
- 2 A User ID condition cannot be defined for a DBCTL connection status rule that specifies either "From connection status equals CONNECTING or DISCONNING", or "To connection status equals CONNECTED, NOTCONNECTED or UNUSABLE".
- 3 A Transaction ID condition cannot be defined for an IBM MQ connection status rule that specifies either "From connection status equals DISCONNING" or "To connection status equals NOTCONNECTED".
- 4 A Transaction ID condition cannot be defined for a Pipeline enable status rule that specifies "From enable status equals INITIAL".
- 5 A User ID condition cannot be defined for a Pipeline enable status rule that specifies "From enable status equals INITIAL".
- 6 This condition is not checked at the time the rule becomes enabled.