![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |
User COBOL source programs can use the Call Level Interface together with either embedded TIBCO Object Service Broker access statements or embedded SQL statements. After establishing a transaction environment using the Call Level Interface STARTTR function, you can issue embedded TIBCO Object Service Broker or SQL statements to access TIBCO Object Service Broker tables.Writing a COBOL Program Using a Combination of the Call Level Interface, TIBCO Object Service Broker Access Statements, and SQL StatementsThe procedure for writing a COBOL program that uses the Call Level Interface and TIBCO Object Service Broker access or embedded SQL statements is:
1. In the WORKING-STORAGE section, establish the access environment for embedded access statements.Refer to Chapter 21, Coding TIBCO Object Service Broker Access Statements or Chapter 22, Coding SQL Access Statements, depending on whether you intend to use TIBCO Object Service Broker access statements or SQL access statements. In either case, the HRNHLLWA, which is shared between the Call Level Interface and the access statements, is automatically generated for you.
2. In the WORKING-STORAGE section, copy in the copybook HRNHLIST provided in the distribution MACRO data set.
3. In the PROCEDURE DIVISION, create a transactional environment as described in the previous sections before coding data access statements.Refer to Chapter 21, Coding TIBCO Object Service Broker Access Statements or Chapter 22, Coding SQL Access Statements. During program execution, these access statements can be preceded or followed by the Call Level Interface CALLRULE function.When you end a first-stream-level transaction using the STOPTR function, you can no longer execute TIBCO Object Service Broker access statements or SQL access statements. You can, however, resume coding these statements after a STOPTR function, if this returns you to a lower transaction nesting level.Precompile third-party programs with embedded data access calls through the TIBCO Object Service Broker preprocessor, to allow for the TIBCO Object Service Broker or SQL data access statements.Convert the TIBCO Object Service Broker or SQL statements to COBOL using the HLIPREPROCESSOR tool. Refer to Chapter 23, Processing COBOL Programs for information on how to use this tool.Refer to the member COBCOLNK in the JCL data set distributed with TIBCO Object Service Broker, for an example of this step.Refer to the member COBBATCH in the JCL data set distributed with TIBCO Object Service Broker, for an example of this invocation.
The STEPLIB DD must have the TIBCO Object Service Broker Load Library concatenated to it. Since such a concatenation normally causes de-authorization of the STEPLIB, you should also provide a HRNLIB DD pointing to the TIBCO Object Service Broker Load Library.
![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |