Using Execute Rule

This chapter describes how to perform various tasks in TIBCO Object Service Broker using the text-based workbench. You can also perform these tasks using the TIBCO Object Service Broker UI, which provides a graphical environment for TIBCO Object Service Broker development. For information about using the TIBCO Object Service Broker UI, refer to the TIBCO Object Service Broker UI online help.

Available Methods

You can invoke the Rule Executor, by using the Execute Rule option from one of the following places:

•

The workbench. For example:

EX execute rule ==> EMPLOYEES_RAISE<Enter>

•

The primary command field. For example:

COMMAND ==> EX EMPLOYEES_RAISE<Enter>

•

The line command X within the Object Manager screen of the Rule Editor

You can also execute a rule asynchronously or in debug mode. For more information about these methods, refer to Chapter 17, Processing Asynchronously in Batch Mode and Chapter 18, Processing in Debug Mode.

Supplying Argument Names

You can provide the arguments within parentheses after the rule name in the command itself. For example:

COMMAND ===> EX EMPLOYEES_RAISE('ANALYST','MIDWEST')<Enter>

or through the arguments screen presented if you do not supply argument values.


	The mode of your 3270 terminal session determines the maximum number of arguments that you can enter through the arguments screen. For example, you can enter a maximum of twelve arguments in a Model 5 3270 terminal session.

Using the Arguments Screen

If the rule has arguments defined and you do not specify values when you invoke the Rule Executor, you are prompted to supply them. For example, because the EMPLOYEES_RAISE rule has two argument, JOBTITLE and REGION, the following screen prompts for two argument values.

---------------------------- RULE EXECUTION --------------------------

ENTER ARGUMENTS FOR RULE EMPLOYEES_RAISE

JOBTITLE ===>

REGION ===>

Library Search Order

If the specified rule exists in your local library, installation library, or system library, the rule is executed. The rules libraries are searched in the order: local library, installation library, system library. This is the default order; you or your system administrator can modify this search order through your user profile or session options.

If the rule is executed from a menu or object list, the search order for the rule can also be set by the tool used to create the menu, such as DEFINE_MENU and DEFINE_OBJLIST.

Results After Execution

After the rule has executed, one of the following types of messages appears across the bottom of the workbench:

•

The ENDMSG, if there is one, for example:

POSITION IS INVALID

•

The message OK, if the rule executes successfully, for example:

11:02:18 OK

If a message is sent to the Message Log, press PF2 to access the message.

•

A reason for execution failure, if the rule does not execute successfully, for example:

ACCESS ERROR ON TABLE "EMPLOYEES"

Press PF2 for more information about the error. Information about the failure is sent to one of the logs maintained by TIBCO Object Service Broker. Refer to Logging of Output.