Policy schema versioning
Policy schema versions are used to provide the greatest compatibility with your systems.
policySchemaRelease="0" policySchemaVersion="1"
If a CICS® release includes a new policy schema, the schema version number is incremented at that release. If the IBM® service organization introduces a new policy schema, the schema release number is incremented.
When you use the policy definition editor to create a policy in a CICS Bundle project, the policy schema version is set to the minimum level for the rules that you define in that policy. This provides the greatest compatibility with systems that might not support later schema versions. The required CICS release for each rule is displayed in the Overview tab of the policy definition editor together with an aggregate CICS release for the policy. The required CICS release for each rule is also displayed Rules tab of the policy definition editor for the rule being edited. For example, if you select a Database request rule with the DLI command subtype, the following information is displayed: Requires CICS TS 5.3 or later. If you select a Database request rule with the SQL command subtype, the following information is displayed: Requires CICS TS 5.1 or later.
If you use a text editor with a policy file to add or remove rules, be aware that this might affect the required policy schema version. You must ensure that the schema version expressed in the <policy:policy tag is at the lowest level that supports all the policy rules. When you save your changes, the policy is validated. If the schema version is not correct, error messages that help you determine the correct schema version are displayed in the Problems view of CICS Explorer®. You must correct any errors before you can deploy the CICS bundle.
The following table shows the minimum CICS release for each task rule, ordered by task rule type and item.
| Task rule type | Item | Policy schema version | CICS release |
|---|---|---|---|
Async requests![]() |
RUN TRANSID commands![]() |
5.0![]() |
5.4![]() |
| Database requests | DLI commands | 3.0 | 5.3 |
| Database requests | SQL commands | 1.0 | 5.1 |
| EXEC CICS requests | EXEC CICS commands | 3.0 | 5.3 |
| File requests | DELETE commands |
1.0 | 5.1 |
| IBM MQ requests | MQ commands | 3.0 | 5.3 |
| Named counter requests | GET COUNTER commands | 3.0 | 5.3 |
| Program requests | LINK commands | 1.0 | 5.1 |
| Start requests | START commands | 2.0 | 5.2 |
| Storage allocation | 24-bit shared storage allocated |
1.0 | 5.1 |
| Storage requests | 24-bit shared storage requests |
1.0 | 5.1 |
| Syncpoint requests | SYNCPOINT commands | 2.0 | 5.2 |
| TD queue requests | READQ TD commands |
2.0 | 5.2 |
| Time | CPU time | 1.0 | 5.1 |
| Time | Elapsed time | 2.0 | 5.2 |
| TS queue bytes | All TS written |
2.0 | 5.2 |
| TS queue bytes | Shared TS written | 3.0 | 5.3 |
| TS queue requests | ALL WRITEQ TS commands |
2.0 | 5.2 |
| TS queue requests | WRITEQ TS commands to shared | 3.0 | 5.3 |
The following table shows the minimum CICS release for each task rule condition, ordered by policy schema version.
| Policy schema version | Task rule type | Item | CICS release |
|---|---|---|---|
| 1.0 | Database requests | SQL commands | 5.1 |
| 1.0 | File requests | DELETE commands |
5.1 |
| 1.0 | Program requests | LINK commands | 5.1 |
| 1.0 | Storage allocation | 24-bit shared storage allocated |
5.1 |
| 1.0 | Storage requests | 24-bit shared storage requests |
5.1 |
| 1.0 | Time | CPU time | 5.1 |
| 2.0 | Start requests | START commands | 5.2 |
| 2.0 | Syncpoint requests | SYNCPOINT commands | 5.2 |
| 2.0 | TD queue requests | READQ TD commands |
5.2 |
| 2.0 | Time | Elapsed time | 5.2 |
| 2.0 | TS queue bytes | All TS written |
5.2 |
| 2.0 | TS queue requests | ALL WRITEQ TS commands |
5.2 |
| 3.0 | Database requests | DLI commands | 5.3 |
| 3.0 | EXEC CICS requests | EXEC CICS commands | 5.3 |
| 3.0 | IBM MQ requests | MQ commands | 5.3 |
| 3.0 | Named counter requests | GET COUNTER commands | 5.3 |
| 3.0 | TS queue bytes | Shared TS written | 5.3 |
| 3.0 | TS queue requests | WRITEQ TS commands to shared | 5.3 |
5.0![]() |
Async requests![]() |
RUN TRANSID commands![]() |
5.4![]() |
The following table shows the schema version and minimum CICS release for each system rule condition, ordered by system rule type.

| System rule type | Policy schema version | CICS release |
|---|---|---|
| DB2® connection status | 4.0 | 5.4 |
| File enable status | 4.0 | 5.4 |
| File open status | 4.0 | 5.4 |
| Message | 4.0 | 5.4 |
| Transaction class tasks | 4.0 | 5.4 |
| Transaction abend | 4.0 | 5.4 |
| User tasks | 4.0 | 5.4 |
