Policy XML element name and attribute values

Policy XML element names and attributes are listed, together with valid values. The assigned values for policy XML element names and attributes depends on the policy rule and action types.

XML parameter values

The following table lists policy XML element names and attributes with the possible values that you could select by using the appropriate drop-down list in the CICS Explorer® Policy wizard. The example after the table shows a policy XML skeleton.

Table 1. XML value cross-reference
`rule_type` 1	`condition_type` 2	`rule_item` 3	`unit` 4	`value` 5	`action_type` 6
databaserequest	databaseRequestCondition	sqlcommand	"" (no value) or K	"" 0 - 4294967295 K 0 - 4294967	abend event message
filerequest	fileRequestCondition	delete read readnext readprev readupdate rewrite startbr write	"" (no value) or K	"" 0 - 4294967295 K 0 - 4294967 These value ranges for requests or thousand requests apply to all filerequest policy rule items.	abend event message
programrequest	programRequestCondition	link	"" (no value) or K	"" 0 - 4294967295 K 0 - 4294967	abend event message
startrequest	startRequestCondition	start	"" (no value) or K	"" 0 - 4294967295 K 0 - 4294967	abend event message
storage	storageUsedCondition	task24 shared24 task31 shared31 task64 shared64	B, K, M, or G	24-bit rule items: B 0 - 16777215 K 0 - 16383 M 0 - 15 G 0 31-bit rule items: B 0 - 2147483647 K 0 - 2097151 M 0 - 2047 G 0 - 1 64-bit rule items: B 0 - 4294967295 K 0 - 4294967295 M 0 - 4294967295 G 0 - 4294967295	abend event message
storagerequest	storageRequestCondition	task24request shared24request task31request shared31request task64request shared64request	"" (no value) or K	"" 0 - 4294967295 K 0 - 4294967 These value ranges for requests or thousand requests apply to all storagerequest policy rule items.	abend event message
syncpointrequest	syncpointRequestCondition	syncpoint	"" (no value) or K	"" 0 - 4294967295 K 0 - 4294967	abend event message
tdqrequest	tdqRequestCondition	readq writeq	"" (no value) or K	"" 0 - 4294967295 K 0 - 4294967 These value ranges for requests or thousand requests apply to all tdqrequest policy rule items.	abend event message
time	timeCondition	cpulimit elapsedlimit	O, M, or S	O 0 - 4294967295 M 0 - 86400000 S 0 - 86400 (a value of 86400 equates to 24 hours)	abend event message
tsqbytes	tsqBytesCondition	writeq writeqaux writeqmain	B, K, M, or G	B 0 - 4294967295 K 0 - 4294967295 M 0 - 4294967295 G 0 - 4294967295 All tsqbytes policy rule items have the same value ranges.	abend event message
tsqrequest	tsqRequestCondition	readq writeq writeqaux writeqmain	"" (no value) or K	"" 0 - 4294967295 K 0 - 4294967 These value ranges for requests or thousand requests apply to all tsqrequest policy rule items.	abend event message

XML policy skeleton

This example lists the XML skeleton for a policy. The fields that are listed in the table and notes are indicated.

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<policy:policy xmlns:policy="http://www.ibm.com/xmlns/prod/cics/managedplatform/policy" policySchemaRelease="0" policySchemaVersion="1">
   <description>description_of_policy</description>
   <userTag>tag_1</userTag>
   <rule type="rule_type" 1 > 
      <name>name_of_rule</name> 
      <description>description_of_rule</description>      
      <condition_type 2  item="rule_item" 3  operator="GT" unit="unit" 4  value="value" 5 />      
      <action>
         <action_type 6 />  
      </action> 
   </rule>
</policy:policy>

Note:

The value of condition_type 2 depends on the value of rule_type 1 .
The valid values for rule_item 3 and unit 4 depend on the value of condition_type 2 .
You can specify only one action_type 6 value for each policy rule, but all three action types are valid for all rule types.
If action_type 6 is abend, and you want the policy to issue a custom abend code, the next statement must be as follows, where code is the value of your abend code:
```
<abend abendCode="code"/>
```
If the action_type 6 is event, the next statement must be one of the following, depending on whether you want the event to be issued to an event adapter or an event adapter set, where name is the name of the event adapter or event adapter set, as appropriate:
- ```
<eventAdapterName>name</eventAdapterName>
```
- ```
<eventAdapterSetName>name</eventAdapterSetName>
```