![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |
@STATICSQL generates members containing the Static SQL accesses and members used to assemble, link, and assist in binding the Static SQL handlers. This requires access to the DB2 table definition. If you used the extraction method to create the TIBCO Object Service Broker DB2 table definition (refer to Using the Extraction Method), ensure that your DB2 definitions are current. If you used the Gateway method to create the TIBCO Object Service Broker DB2 table definition (refer to Using the Gateway Method) you must have an instance of the Gateway running that has the same server ID as your TIBCO Object Service Broker DB2 table definition.If you modify the TIBCO Object Service Broker DB2 table definition, you have to regenerate only your Static SQL to pick up the changes. You do not have to recollect the TIBCO Object Service Broker DB2 access statements, unless changes were made to your application.To use DB2 LIKE in your static handlers, you must specify USEDB2LIKE=Y in your Execution Environment start up. By default, LIKE statements are not included in the selection logged.To use the DB2 LIKE statement format (not to be confused with TIBCO Object Service Broker LIKE) you must apply both of the following settings:
• For dynamic SQL, to make the DB2 Gateway formulate DB2 LIKE clauses you must specify USEDB2LIKE in the DB2 Gateway start up parameters. Without this specification, the Gateway parses the rows returned.
• When generating Static SQL using the @STATICSQL tool, to have LIKE statements included in the Static handler you must sign on to the Execution Environment using USEDB2LIKE(Y). LIKE statements are generated in the static SQL handler. Without this specification, LIKE statements are not included in the static handlers.To invoke the @STATICSQL tool, execute the @STATICSQL rule from the workbench. A screen similar to the one following displays:
Displays all the TIBCO Object Service Broker DB2 tables to which you have READ_DEFN access. You cannot change this name; it is assigned from the Table Definer. Displays the name of the DB2 table corresponding to the TIBCO Object Service Broker DB2 table name displayed in the MetaStor Table field of the same row. You cannot change this name; it is assigned from the Table Definer. G – Static SQL was generated for the table.I – Static SQL was generated and the definition was changed (invalidated). You must regenerate Static SQL for this table.blank – No Static SQL was generated. Type a three character prefix that is unique within all TIBCO Object Service Broker DB2 tables in your system. This prefix is used in conjunction with the suffix. Type a five character suffix that is unique within all TIBCO Object Service Broker DB2 tables in your system. This suffix is appended to the prefix to create the member names of the Static SQL handlers and link control cards. You can edit this field when you regenerate Static SQL. If you have already generated Static SQL for a table, the suffix you entered when you generated Static SQL for this table appears.
Remove Static SQL for the table (press PF3 to remove it online or PF15 to remove it in batch mode). This command performs the following:
• Removes references to the Static SQL handler in the JCL members ASMDB2SS and LINKDB2S and CNTL bind member XBINDDB6Note You can re-bind the Gateway plan to remove the Static SQL handler; however, the Gateway uses dynamic SQL irrelevant of the plan.
• Delete previously generated code in data set holding the Static SQL handlers generated by @STATICSQL (file specified in @DB2SERVERASM)
• Delete the Static SQL handler member from the object code, DBRM, and LOAD data sets, and the data set containing the link control cards (file specified in @DB2SERVERJCL) Generate Static SQL for the table (press PF3 to generate it online or PF15 to generate in batch mode). This command does the following:
• Creates member prefix/suffix in the file pointed to by the export table @DB2SERVERASM. This member is the assembler code that contains the Static SQL statements.WARNING Do not modify this member.
• Creates JCL members ASMDB2SS and LINKDB2S, link control card member prefix/suffix, and CNTL bind member XBINDDB6 pointed to by the export table @DB2SERVERJCL. Use PF3 to exit, with the following message:Note Always use PF2 to review warning or error messages.Note Always review the message log displayed at the end of the batch job for warning or error messages.
![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |