The primary command APPEND appends a rule onto the rule currently being edited. The
APPEND command appends the actions at the end of the action part and the exception handlers at the end of the exception handler part of the rule being edited. The rule is checked for syntax before it can be saved.
APPEND does not append local variables and conditions, and it does not add action sequence numbers for the appended action part. You must supply these as required.
Issue the APPEND command as shown:
If you decide not to save changes to a rule, you can cancel the changes by typing the primary command
CANCEL in the primary command field and pressing Enter, or by pressing PF12. When you issue the command, the Rule Editor cancels editing changes and returns you to your previous screen.
The CHANGE command has an optional argument,
ALL. This argument changes the scope of the
CHANGE command from the next occurrence of the search token to all the occurrences of the search token in the rule. Specify the
ALL argument as follows:
If a CHANGE … ALL command makes changes, the message line tells how many occurrences of the search token are replaced. If the search token does not occur in the rule, the message line informs you of this.
The COPY primary command causes the current rule to be replaced, except its name, with a copy of the rule specified. The
COPY command provides a convenient way to replace one rule with another or to fill in an empty template.
Issue the COPY command as shown:
If you change the name of the rule that you are editing (without making other changes) and if there is no rule with the new name in your local library, the Rule Editor creates a copy of the original rule under the new name. If a rule with the new name already exists, you are prompted to overwrite it.
The primary command DELETE deletes a rule from your local library. To issue the command, type
DELETE in the primary command field, or display the rule and press PF22.
The Rule Editor does not delete a rule without first prompting you to type the command
CONFIRM or press PF22 to confirm the deletion. To cancel the deletion, press Enter or any other function key.
The primary command DOCUMENT causes a screen to appear where you document the description and usage of your rule. To issue the command, type
DOCUMENT in the primary command field, or display the rule and then press PF2.
TIBCO Object Service Broker Getting Started about documenting rules and other TIBCO Object Service Broker objects.
You can use the primary command EDIT to edit a different rule or to create a new rule from within an editing session. The rule being edited is checked for syntax errors, and when it can be saved the new editing session begins.
To edit a different rule from within an editing session, type the EDIT command and the name of the required rule in the primary command field, and press Enter. For example, if you are editing the EMPLOYEES_RAISE rule and you want to edit the DEPARTMENTS rule, type the
EDIT command as shown:
If there are no syntax errors, the Rule Editor saves the EMPLOYEES_RAISE rule before it displays the DEPARTMENTS rule. If there are syntax errors, you must correct them before the Rule Editor can begin the editing session for the DEPARTMENTS rule.
To create a new rule from within an editing session, type the EDIT command and the name of the new rule in the primary command field and press Enter.
You can end the editing session and save the changes by typing END in the primary command field and pressing Enter, or by pressing PF3. If there are no syntax errors, when you issue the
END command the Rule Editor saves the rule in the local library you are using, not in the library of origin, and returns you to the workbench. You must correct your syntax errors before the rule can be saved. Refer to
Syntax Checking Performed on a Rule for more information.
You can display online help by typing HELP in the primary command field or by pressing PF1. The online help contains a description of the Rule Editor and a list of the Rule Editor commands and their syntax. To return to the rule, press PF3 or PF12.
You can use the primary command LOWER to type string literals in mixed case (that is, text within single quotation marks). If you are editing an existing rule, you must issue the primary command
LOWER and press Enter before the lowercase text is typed in. Existing lowercase text remains in lowercase when it is edited.
To print the current rule, press PF13 or type PRINT in the primary command field and press Enter. The hardcopy output includes some of the documentation for the rule. The documentation that is included appears between the rule definition and the conditions.
Rules are not actually updated in your local library until you save your changes. You can save changes by typing
SAVE in the primary command field and pressing Enter. The Rule Editor saves the rule in the local library you are using, not in the library of origin, and continues the editing session.
If the Rule Editor cannot save a rule, it gives a reason for the failure on the message line and positions the cursor where the first correction is required. You must correct the rule before you can save the changes. Refer to
Syntax Checking Performed on a Rule for more information.
If you issue the primary command LOWER and you want to revert back to using uppercase for your string literals, type
UPPER in the primary command field and press Enter.
You use the XEDIT command to edit an existing or new rule within an editing session. The difference between
EDIT and
XEDIT is that
XEDIT cancels changes made to the rule currently being edited.
The Rule Editor stores a command until it is replaced with another command. PF9 redisplays the most recent command, which you can edit if necessary. For example, suppose that the previous command was the following:
You now want to change the token DEPT to the token DEPARTMENT#. Re-display the previous command by pressing PF9. Place the cursor where editing is required (on the token REGION) and alter the command by overtyping, as follows: