Policy XML element name and attribute 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 would be selected from the appropriate drop-down list in the CICS Explorer® Policy wizard. The example shows a policy XML skeleton.
Table 1. XML value cross-reference
rule_type 1  condition_type 2  rule_item 3  unit 4  action_type 5 

databaserequest

databaseRequestCondition

sqlcommand

"" (no value) or K

abend
event
message

filerequest

fileRequestCondition

delete
read
readnext
readprev
readupdate
rewrite
startbr
write

"" (no value) or K

programrequest

programRequestCondition

link

"" (no value) or K

storage

storageUsedCondition

task24
task31
task64
shared24
shared31
shared64

"" (no value), B, K, M, or G

storagerequest

storageRequestCondition

task24request
task31request
task64request
shared24request
shared31request
shared64request

"" (no value) or K

time

timeCondition

cpulimit

"" (no value), O, M, or S

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="0"/>      
      <action>
         <action_type 5 />  
      </action> 
   </rule>
</policy:policy>
Note:
  • The value of condition_type 2  is dependent 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 .
  • Only one action_type 5  value can be specified per policy rule, but for all rule types any of the three action types is valid.
  • If action_type 5  is "abend", and you want the policy to issue a custom abend code, the next statement must be:
    <abend abendCode="code"/>
    where code is the value of your abend code.
  • If the action_type 5  is "event", the next statement must be either
    <eventAdapterName>name</eventAdapterName>
    or
    <eventAdapterSetName>name</eventAdapterSetName>
    depending on whether you want the event to be issued to an event adapter or an event adapter set, and where name is the name of the event adapter or event adapter set, as appropriate.