![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |
• Placing data into the arguments of the rule to be called. Refer to Calling a Rule – CALLRULE for more information.
• Placing data into a block of storage pointed at by the DATA-IN area when a rule is called. Refer to Calling a Rule – CALLRULE for more information.
• Placing data in a table occurrence mapped by the Host Language Interface (HLI) and performing an INSERT or REPLACE. Refer to Using the Host Languages Interface for more information.Under normal circumstances, the batch client sets a return code of zero. You can use the $SETSESSIONEND tool to set the return code to a value between zero and 3999:You can subsequently use JES2 or JES3 condition processing to control the execution of subsequent job steps based on return or abend codes. For example:
• Using MAP tables to REPLACE table occurrences in blocks of storage pointed at by the DATA-OUT area. Refer to Calling a Rule – CALLRULE for more information.
• Populating a temporary table and using the Host Language Interface to perform a FORALL or GET to the table containing the required data. Refer to Using the Host Languages Interface for more information.Your session can invoke external routines defined using the ROUTINES and ARGUMENTS tables to manipulate data. Refer to Chapter 10, Accessing External Routines for more information.TIBCO Object Service Broker Managing Data about MAP tables.TIBCO Object Service Broker Programming in Rules about the rules language statements and writing rules.TIBCO Object Service Broker Shareable Tools about the use of the tools.
![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |