Copyright © TIBCO Software Inc. All Rights Reserved
Copyright © TIBCO Software Inc. All Rights Reserved


Chapter 3 Using Static SQL : Task D: Manage Warning and Error Messages from @STATICSQL

Task D: Manage Warning and Error Messages from @STATICSQL
@SS_SELECTION Table
The screen below shows a sample TIBCO Object Service Broker @SS_SELECTION table that is used to generate Static SQL.

 
BROWSING TABLE : @SS_SELECTION(U40_DB2_EMP)
COMMAND ==>
SCROLL: P
KEY ACCESS INCLUDE CURSORID
_ ----------- - - -
_ 1 N .
_ 4 N .
_ 5 N .
_ 6 N .
_ 7 N .
_ 8 G .
_ 9 N .
_ 10 N .
_ 11 N .
PFKEYS: 1=HELP 5=FIND NEXT 9=RECALL 18=EXCLUDE 13=PRINT 3=END 14=EXPAND

 
Field Values
 
G – GET
N – FORALL
blank – Include.
N – Ignore, do not include.
Displays a period, representing the encoded data that is your TIBCO Object Service Broker DB2 access statement. This data cannot be read or modified.
Cursor Names
@STATICSQL generates cursor names. Each cursor name contains the following information:
A letter corresponding to the ACCESS field in the @SS_SELECTION table (N or G)
A number corresponding to the KEY field in the @SS_SELECTION table
Sample Warning Messages Generated By @STATICSQL
When you encounter warning messages in the message log similar to those shown in the example below, Static SQL is not generated for the lines named in the warning message, for example, LS9 and LS10. If you delete the entry from @SS_SELECTION, it reappears the next time you log your accesses for Static SQL. Therefore, you should set the INCLUDE flag for the corresponding numbered entry in the @SS_SELECTION table to N so that you do not see this warning message again, for example KEY=9 and KEY=10.

 
Unsupported selection: Table U40_DB2_EMP, cursor type "N", abbrev "LS9"
UNSUPPORTED OPERATOR
Unsupported selection: Table U40_DB2_EMP, cursor type "N", abbrev "LS10"
UNSUPPORTED OPERATOR
Generate/Remove Static SQL: 0 errors. CHECK LOG for warnings

 
Sample Error Messages Generated By @STATICSQL
When you encounter error messages in the message log similar to the example below, no Static SQL is generated for the line named in the error message, for example, LS11. The first line displays the source of the problem (LS11). The second line of the message explains that the field accessed in the WHERE clause of the access logged (LS11) is not a field in the named TIBCO Object Service Broker DB2 table. Therefore, you should delete the corresponding numbered entry in the @SS_SELECTION table or set the INCLUDE flag for this entry to N.

 
Unsupported selection: Table U40_DB2_EMP, cursor type "N", abbrev "LS11"
Field referenced in the selection is not part of table’s defn
Generate/Remove Static SQL: 0 errors. CHECK LOG for warnings

 
When you generate Static SQL, the log tables @SS_SELECTION and @SS_ACCESSES are not cleared. When you modify an application, you must rerun only the modified portion of the application to collect the new accesses to TIBCO Object Service Broker DB2 tables. If you want to regenerate all accesses, you must clear the accesses logged in @SS_SELECTION for the TIBCO Object Service Broker DB2 table and delete the corresponding table name from @SS_ACCESSES. If you choose to remove the accesses, you must rerun all applications that access this table.

Copyright © TIBCO Software Inc. All Rights Reserved
Copyright © TIBCO Software Inc. All Rights Reserved