@STATICSQL generates cursor names. Each cursor name contains the following information:
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.
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.
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.