Sharing rule definitions between instances

In most situations, sharing rule definitions between instances of Advanced Allocation Management that run on separate systems and that use different load libraries is not problematic. Every effort is made to ensure that RULEDEF syntax is upwardly compatible but downward compatibility is not guaranteed. If you plan to share rule definitions between instances of Advanced Allocation Management that run on separate systems and that use different load libraries, and you want to check for unidentified keywords, complete the following steps for each load library each version and level of Advanced Allocation Management with which you plan to use the rule definitions.

About this task

Complete the following steps:

Procedure

  1. Modify the GLOCLIST JCL by replacing &HILEVEL on the first statement in the CLIST.
  2. Run Advanced Allocation Management. When you run Advanced Allocation Management, it fills in the subsequent references to the &HILEVEL variable automatically.
  3. Run the syntax-check as described in Syntax-checking control data set members.

What to do next

If the Advanced Allocation Management started task encounters an unidentified keyword, the rule definition activation fails and the message: GLO1176E RULEDEFS MEMBER membername ACTIVATION FAILED - SEE JESYSMSG FOR DETAILS is generated. In this situation, review the Advanced Allocation Management started task JESYSMSG.

If you see the message: GLO4030E INVALID KEYWORD-keyword, remove the invalid keyword from the rule definitions and activate the rule definitions again. For more information, see Activating rule definitions.