![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |
The following data sets must be allocated on every z/OS image where Service Gateway for DB2 will generate or use static SQL to access the DB2. The ALLOCDB2 member in the JCL data set distributed with TIBCO Object Service Broker provides sample JCL to allocate these data sets.
Allocated by... Allocated in the Images Occupied by ... TIBCO Object Service Broker and DB2 An assembler source data set for the static SQL handlers generated by the @STATICSQL tool, specified in the File field for the @DB2SERVERASM export table definition. An object code data set for assembled static SQL handlers. A DBRM library to hold DBRMs generated when the static SQL handlers are assembled. A load library for static SQL handlers (does not have to be authorized); use the //HDB2SSQL DD statement to point to this library. TIBCO Object Service Broker and DB2 A data set for JCL generated by the @STATICSQL tool, which assists in assembling and linking the SQL handlers, and binding the Gateway. This data set is specified in the File field for the @DB2SERVERJCL export table definition. TIBCO Object Service Broker and DB2 A source listing data set for the static SQL handler assembler listings.Before you run @STATICSQL for the first time, the @DB2SERVERJCLMDL, @DB2SERVERJCL, and @DB2SERVERASM import and export tables must be modified.To generate static SQL, collect your TIBCO Object Service Broker DB2 access statements by running your applications in an Execution Environment with the DB2LOG Execution Environment parameter set to Y. The @STATICSQL tool can then be run to generate the static SQL handlers and the JCL to assemble and link the handlers.Refer to Chapter 3, Using Static SQL for more information.TIBCO Object Service Broker Parameters for further information on parameters.
![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |