Policy schema versions

Policy schema versions are used to provide the greatest compatibility with your systems.

The policy schema version is identified by a version and release number shown in the schema. For example, a policy schema version of 1.0 is expressed in the schema as:

policySchemaVersion="1" policySchemaRelease="0"

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. For example, a new policy schema is provided for existing CICS releases so that a policy can define static data capture items or an event name for rules that specify the event action. The schema release number becomes 1, so the policy schema version becomes 1.1 and is expressed in the schema as:

policySchemaVersion="1" policySchemaRelease="1"

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 on the 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.3 or later. Any attempt to install a policy into a CICS region at an earlier CICS release than the aggregate CICS release for the policy displayed in the Overview tab will fail with the message DFHMP2004.

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 export the CICS bundle to zFS.

Listing of rule conditions, policy schema version and minimum CICS release

Task rules	System rules
Listing by task rule type and item Listing by policy schema version	Listing by system rule type

Reference for task rules

Table 1 shows the minimum CICS release for each task rule, ordered by task rule type and item.

Table 1. Task rule conditions, policy schema version and minimum CICS release
Task rule type	Item	Policy schema version	Minimum CICS release
All	Set Transaction ID and User ID conditions	5.2	6.1 5.4 through 5.6 with APAR ¹
Async requests	RUN TRANSID commands	5.0	5.4
Async requests	RUN TRANSID commands	5.1 ²	5.4 with APAR ³
Container storage	64-bit storage allocated to containers for a user task	7.1	6.1 5.6 with APAR PH29187
Database requests	DLI commands	3.0	5.3
Database requests	DLI commands	3.1 ²	5.3 with APAR ³
Database requests	SQL commands	1.0	5.3
Database requests	SQL commands	1.1 ²	5.3 with APAR ³
EXEC CICS requests	EXEC CICS commands	3.0	5.3
EXEC CICS requests	EXEC CICS commands	3.1 ²	5.3 with APAR ³
File requests	DELETE commands READ commands READNEXT commands READPREV commands READ UPDATE commands REWRITE commands STARTBR commands WRITE commands	1.0	5.3
File requests		1.1 ²	5.3 with APAR ³
File requests	ALL option	8.0	6.1
IBM MQ requests	MQ commands	3.0	5.3
IBM MQ requests	MQ commands	3.1 ²	5.3 with APAR ³
Named counter requests	GET COUNTER commands	3.0	5.3
Named counter requests	GET COUNTER commands	3.1 ²	5.3 with APAR ³
Program requests	LINK commands	1.0	5.3
Program requests	LINK commands	1.1 ²	5.3 with APAR ³
Start requests	START commands	2.0	5.3
Start requests	START commands	2.1 ²	5.3 with APAR ³
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	1.0	5.3
Storage allocation		1.1 ²	5.3 with APAR ³
Storage allocation	All option	8.0	6.1
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	1.0	5.3
Storage requests		1.1 ²	5.3 with APAR ³
Storage requests	All option	8.0	6.1
Syncpoint requests	SYNCPOINT commands	2.0	5.3
Syncpoint requests	SYNCPOINT commands	2.1 ²	5.3 with APAR ³
TD queue requests	READQ TD commands WRITEQ TD commands	2.0	5.3
TD queue requests	READQ TD commands WRITEQ TD commands	2.1 ²	5.3 with APAR ³
TD queue requests	All option	8.0	6.1
Time	CPU time	1.0	5.3
Time	CPU time	1.1 ²	5.3 with APAR ³
Time	Elapsed time	2.0	5.3
Time	Elapsed time	2.1 ²	5.3 with APAR ³
TS queue bytes	All TS written Auxiliary TS written Main TS written	2.0	5.3
TS queue bytes	All TS written Auxiliary TS written Main TS written	2.1 ²	5.3 with APAR ³
TS queue bytes	Shared TS written	3.0	5.3
TS queue bytes	Shared TS written	3.1 ²	5.3 with APAR ³
TS queue requests	ALL WRITEQ TS commands READQ TS commands WRITEQ TS commands to auxiliary WRITEQ TS commands to main	2.0	5.3
TS queue requests		2.1 ²	5.3 with APAR ³
TS queue requests	WRITEQ TS commands to shared	3.0	5.3
TS queue requests	WRITEQ TS commands to shared	3.1 ²	5.3 with APAR ³
TS queue requests	All option	8.0	6.1

Table 2 shows the minimum CICS release for each task rule condition, ordered by policy schema version.

Table 2. Task rule conditions and minimum CICS release
Policy schema version	Minimum CICS release	Task rule type	Item
1.0	5.3	Database requests	SQL commands
1.1 ²	5.3 with APAR ³	Database requests	SQL commands
1.0	5.3	File requests	DELETE commands READ commands READNEXT commands READPREV commands READ UPDATE commands REWRITE commands STARTBR commands WRITE commands
1.1 ²	5.3 with APAR ³	File requests
1.0	5.3	Program requests	LINK commands
1.1 ²	5.3 with APAR ³	Program requests	LINK commands
1.0	5.3	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
1.1 ²	5.3 with APAR ³	Storage allocation
1.0	5.3	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
1.1 ²	5.3 with APAR ³	Storage requests
1.0	5.3	Time	CPU time
1.1 ²	5.3 with APAR ³	Time	CPU time
2.0	5.3	Start requests	START commands
2.1 ²	5.3 with APAR ³	Start requests	START commands
2.0	5.3	Syncpoint requests	SYNCPOINT commands
2.1 ²	5.3 with APAR ³	Syncpoint requests	SYNCPOINT commands
2.0	5.3	TD queue requests	READQ TD commands WRITEQ TD commands
2.1 ²	5.3 with APAR ³	TD queue requests	READQ TD commands WRITEQ TD commands
2.0	5.3	Time	Elapsed time
2.1 ²	5.3 with APAR ³	Time	Elapsed time
2.0	5.3	TS queue bytes	All TS written Auxiliary TS written Main TS written
2.1 ²	5.3 with APAR ³	TS queue bytes	All TS written Auxiliary TS written Main TS written
2.0	5.3	TS queue requests	ALL WRITEQ TS commands READQ TS commands WRITEQ TS commands to auxiliary WRITEQ TS commands to main
2.1 ²	5.3 with APAR ³	TS queue requests
3.0	5.3	Database requests	DLI commands
3.1 ²	5.3 with APAR ³	Database requests	DLI commands
3.0	5.3	EXEC CICS requests	EXEC CICS commands
3.1 ²	5.3 with APAR ³	EXEC CICS requests	EXEC CICS commands
3.0	5.3	IBM MQ requests	MQ commands
3.1 ²	5.3 with APAR ³	IBM MQ requests	MQ commands
3.0	5.3	Named counter requests	GET COUNTER commands
3.1 ²	5.3 with APAR ³	Named counter requests	GET COUNTER commands
3.0	5.3	TS queue bytes	Shared TS written
3.1 ²	5.3 with APAR ³	TS queue bytes	Shared TS written
3.0	5.3	TS queue requests	WRITEQ TS commands to shared
3.1 ²	5.3 with APAR ³	TS queue requests	WRITEQ TS commands to shared
5.0	5.4	Async requests	RUN TRANSID commands
5.1 ²	5.4 with APAR ³	Async requests	RUN TRANSID commands
5.2	6.1 5.4 through 5.6 with APAR ¹	All	Set Transaction ID and User ID conditions
7.1	6.1 5.6 with APAR PH29187	Container storage	64-bit storage allocated to containers for a user task
8.0	6.1	File requests Storage allocation Storage requests TD queue requests TS queue requests	All option

Note:

Available when the PTF for APAR PH26145 is applied to CICS TS 5.4, 5.5, or 5.6.
The schema release number is 1 if a task rule defines a static data item or an event name. That is, the required policy schema version is 1.1, 2.1, 3.1, or 5.1, depending on the task rule type.
Available when the PTF for APAR PI88500 is applied to CICS TS 5.3 or 5.4.

Reference for system rules

Table 3 shows the schema version and minimum CICS release for each system rule condition, ordered by system rule type.

Table 3. System rule conditions, policy schema version and minimum CICS release
System rule type	Policy schema version	Minimum CICS release
AID threshold	6.0	5.5
	7.0 ¹	5.6
	9.0 ²	6.2 6.1 with APAR PH58295
6.3 APPC(LU62) connection status	10.0	CICS TS 6.3
Bundle available status	4.2	5.5 5.4 with APAR PI92806
	7.0 ¹	5.6
	9.0 ²	6.2 6.1 with APAR PH58295
Bundle enable status	4.2	5.5 5.4 with APAR PI92806
	7.0 ¹	5.6
	9.0 ²	6.2 6.1 with APAR PH58295
Compound condition	8.0	6.1
Compound condition	9.0 ²	6.2 6.1 with APAR PH58295
DBCTL connection status	6.1	5.6 5.5 with APAR PH07632
	7.0 ¹	5.6
	9.0 ²	6.2 6.1 with APAR PH58295
Db2® connection status	4.0	5.4 5.3 with APAR PI83667
	4.1 ³	5.5 5.3 or 5.4 with APAR ⁴
	7.0 ¹	5.6
	9.0 ²	6.2 6.1 with APAR PH58295
File enable status	4.0	5.4 5.3 with APAR PI83667
	4.1 ³	5.5 5.3 or 5.4 with APAR ⁴
	7.0 ¹	5.6
	9.0 ²	6.2 6.1 with APAR PH58295
File open status	4.0	5.4 5.3 with APAR PI83667
	4.1 ³	5.5 5.3 or 5.4 with APAR ⁴
	7.0 ¹	5.6
	9.0 ²	6.2 6.1 with APAR PH58295
IBM MQ connection status	6.1	5.6 5.5 with APAR PH07632
	7.0 ¹	5.6
	9.0 ²	6.2 6.1 with APAR PH58295
IPIC connection status	4.2	5.5 5.4 with APAR PI92806
	7.0 ¹	5.6
	9.0 ²	6.2 6.1 with APAR PH58295
6.3 JVM server enable status	10.0	CICS TS 6.3
Message	4.0	5.4 5.3 with APAR PI83667
	4.1 ³	5.5 5.3 or 5.4 with APAR ⁴
	7.0 ¹	5.6
	9.0 ²	6.2 6.1 with APAR PH58295
MRO connection status	4.2	5.5 5.4 with APAR PI92806
	7.0 ¹	5.6
	9.0 ²	6.2 6.1 with APAR PH58295
Pipeline enable status	6.1	5.6 5.5 with APAR PH07632
	7.0 ¹	5.6
	9.0 ²	6.2
Program enable status	4.2	5.5 5.4 with APAR PI92806
	7.0 ¹	5.6
	9.0 ²	6.2 6.1 with APAR PH58295
Transaction abend	4.0	5.4 5.3 with APAR PI83667
	4.1 ³	5.5 5.3 or 5.4 with APAR ⁴
	7.0 ¹	5.6
	9.0 ²	6.2 6.1 with APAR PH58295
6.2 and later Transaction class queued tasks	9.0	6.2
Transaction class tasks	4.0	5.4 5.3 with APAR PI83667
	4.1 ³	5.5 5.3 or 5.4 with APAR ⁴
	7.0 ¹	5.6
	9.0 ²	6.2 6.1 with APAR PH58295
Transaction dump threshold	7.2	6.1 5.6 with APAR PH34348
Transaction dump threshold	9.0 ²	6.2 6.1 with APAR PH58295
User tasks	4.0	5.4 5.3 with APAR PI83667
	4.1 ³	5.5 5.3 or 5.4 with APAR ⁴
	7.0 ¹	5.6
	9.0 ²	6.2 6.1 with APAR PH58295

Note:

The schema version is 7.0 if a system rule defines the set z/OS® WLM health open status action.
The schema version is 9.0 if a system rule defines the set WLM health interval option with the set z/OS WLM health open status action.
The schema release number is 1 if a system rule defines a static data capture item or an event name. That is, the required policy schema version is 4.1.
Available when the PTF for APAR PI88500 is applied to CICS TS 5.4, or when the PTFs for APARs PI83667 and PI88500 are applied to CICS TS 5.3.