Updating Policy Objects Using Text Files
Each policy object in the
text file is represented by the following structure:
UPD <Entry Type> - <Entry Name>
<Policy Item> ( field|block|policy replacement )
<Field> : <Value>
<Field> : <Value>
...
<Policy Item> ( field|block|policy replacement )
<Field> : <Value>
<Field> : <Value>
...
...The actual values for the Entry Type, Entry Name, Policy Item, and Field variables depend on the
selections that you made when the file was created and what data is in your policy database, for example:
UPD APL - AM
RELATIONSHIPS ( policy replacement )
Relationship Type : MAKEUNAVAILABLE
Supporting Resource : AM2/APL/=
Description : Prevents takeover at system shutdown
Sequence Number :
Automation : PASSIVE
Chaining : WEAK
Condition : WhenDown
* MESSAGES/USER DATA no data available
WHERE_USED APG : AM_X The <Policy Item> lines must be indented by 1 or 2 characters, and the <Field> lines must be indented by 3 or more characters.
Do not modify the <Policy Item> or <Field> segments because the syntax of the file will be invalid and the file will fail syntax checking.
If the file does fail the syntax check, you can view the update report and fix any errors that are reported before trying the update again.
The text after each policy item indicates which type of data replacement is possible:
- Field replacement: the data that you specify in the text file replaces only the corresponding data in the policy database.
- Block replacement: the row and all data that is nested underneath it is treated as one block of data, and each such block replaces the corresponding data in the policy database.
- Policy replacement: the policy definition in the text file replaces the whole policy definition in the policy database.