You can use the Call Level Interface to write a client program that provides features of the batch client and the rules language, but with a much finer line of granularity. For economy of representation, only the OPERATION, OPERAND, and PARM (if required) are explicitly stated. The COBOL or assembler call, null parameters and RETURN-DATA and RETURN-MESSAGE processing should be viewed as implicit.
In this example, the functionality of a simple invocation of the z/OS batch client is translated into a series of Call Level Interface calls. Assume that we invoked the batch client as follows (the session parameter NOBROWSE means UPDATE):
This example shows how to create a nested transaction. Based on the Batch Client Example, assume that we invoke a BROWSE transaction and call the EMP_B rule before terminating the initial transaction. This functionality could be implemented by a client program as follows:
This example shows how to obtain the rules-based functionality of a TRANSFERCALL using the Call Level Interface. Based on the
Batch Client Example, assume that we invoke a BROWSE transaction and call the EMP_B rule after terminating the initial transaction. This functionality could be implemented by a client program as follows: