Messages PM0700 through PM0799 (MainView AutoOPERATOR)

PM0721I

RULES PROCESSOR CONTROL STATEMENT ERROR

Explanation: Displays the card in error in AAORULxx member of parmlib. PM0721I flagged the card in error and the message PM0722I contains a more detailed description of the error. The rule will be skipped and initialization will continue.

User response: Correct the rule and issue the .RESET RULES command to pick up the changes.

PM0724I

RULEID rrrrrrrr IN RULESET ssssssss CHANGED TO RULnnnnn

Explanation: A Rule's identification was changed because another Rule with the same Rule Id, in an enabled (or test mode) Ruleset already exists. rrrrrrrr is the id specified in the Rule, and it resides in Ruleset ssssssss. The new and temporary name is RULnnnnn, where nnnnn is a number which is automatically assigned. This message is followed by PM0725I, which identifies the enabled Ruleset which contains the duplicate id. The rule will be created, but under the generated id.

User response: Change to Id of the Rule to be unique.

PM0725I

RULEID rrrrrrrr ALREADY EXISTS IN RULESET ssssssss

Explanation: This message is preceded by PM0724I when a duplicate Rule ID is encountered. This message specifies where the duplicate id was found for Rule rrrrrrrr. ssssssss is the Enabled (or Test mode) Ruleset containing the duplicate. The rule will be created, but under the generated id.

User response: See PM0724I.

PM0726W

TIME-INIT RULE rrrrrrrr IN RULESET ssssssss HAS AN INVALID ID

Explanation: A Time-init Rule (rrrrrrrr) in Ruleset ssssssss has an invalid id and MAY not fire. A valid Time-init Rule-id must only contain alphanumeric characters (A-Z, 0-9), or special characters '$', '@' or '#'. The rule will be created, and will be enabled, but MAY not fire.

User response: Correct the Rule-id to be a valid name.

PM0727W 

Rule rrrrrrrr in Rule Set ssssssss may be from incompatible release

Explanation: A syntax error was detected in rule rrrrrrrr that is part of rule set ssssssss during the ENABLE of the rule set and MIGRULES=YES was specified in AAOPRMxx. One possible cause for the syntax error is the use of a higher release Rules application to update and SAVE a rule set, and then attempting to use a lower level PAS to process that rule set. The rule will be retained in the rule set but it will have a status of INV and will not be modifiable and will not fire in this PAS.

User response: Determine the cause of the syntax by reviewing the contents of message PM0723I which shows the rule that is in error. Make any necessary corrections and then re-enable the rule set to activate the rule. If it is determined that the syntax error is caused by an option that has been put in the rule by a newer release of the product and that the rule does not need to fire in this PAS then no further action is needed.