![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |
Before you execute @STATICSQL for the first time, you must edit the definitions for the @DB2SERVERJCLMDL, @DB2SERVERASM, and @DB2SERVERJCL import and export tables. Initially, only level‑7 TIBCO Object Service Broker users can edit these tables; if a level‑1 user needs to customize these tables, you must update the security.
In the File field on the Table Definition screen, specify the name of the JCL data set containing members ASMDB2MD and LINKD2MD. These are models to generate JCL. You must customize these members to specify the required DB2 data sets. Export table @DB2SERVERASM In the File field of the Table Definition screen, specify the name of the data set that holds the Static SQL handlers generated by @STATICSQL. Export table @DB2SERVERJCL In the File field of the Table Definition screen, specify the name of the data set that holds the JCL, link control cards, and bind control cards generated by @STATICSQL.
Ensure these data sets are allocated as part of the installation procedure. Also ensure that @SCHEDULEMODEL(‘MVS’, ‘*DEFAULT*’), used to generate Static SQL in batch, and the BINDDB2S member in the JCL data set are customized. Refer to Requirements for Accessing DB2 Using Static SQL for more information.
• TIBCO Object Service Broker Managing Security for more information on updating Security accesses.
• TIBCO Service Gateway for Files Installing and Operating about modifying import and export tables.
![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |