Copyright © Cloud Software Group, Inc. All Rights Reserved
Copyright © Cloud Software Group, Inc. All Rights Reserved


Chapter 5 The Action Statements : CALL Statement

CALL Statement
The CALL statement invokes a rule within the scope of the current transaction. Upon completion, control passes to the next action in the calling rule. Arguments in CALL statements are passed by an argument list. All arguments must be specified when a rule is called.
Usage Notes
The called rule can be a rule in the installation library, the system library, or the local library that you use for your session when you execute the rule, or it can be a shareable tool. Refer to Chapter 13, Using Rules Libraries for more information about rules libraries. Refer to Chapter 16, Processing in Standard Execution Mode for more information about rules execution.
You can invoke the rule directly or indirectly. Refer to Indirect Referencing for additional information about indirect referencing.
You cannot trap for the following: a non-existent rule, whether the rule name is not semantic data type I (for identifier) or typeless, or an incorrect number of arguments.
Exceptions
 
Signaled if the called routine fails and the cause of the error cannot be signaled by other system exceptions
Examples
1.
2.
3.
About the Examples
Example 2 invokes the shareable tool ENDMSG, which contains one argument, message. The value for message is a concatenation of the value for the local variable COUNT, the text string ‘EMPLOYEES IN DEPARTMENT#’, and the value for the argument DEPT passed in from a higher-level calling rule.
Example 3 indirectly invokes a rule. In this example the value of the field ROUTINE, in the table FCNKEYS, is the name of the rule to be called. For more information, refer to Indirect Referencing.
See Also
TIBCO Object Service Broker Shareable Tools about the use of shareable tools.

Copyright © Cloud Software Group, Inc. All Rights Reserved
Copyright © Cloud Software Group, Inc. All Rights Reserved