For DB2: If the RepoOnly = TRUE option is turned on in the ini file, why is a # character generated instead of the default ; character after each SQL statement?

For DB2: If the RepoOnly = TRUE option is turned on in the ini file, why is a # character generated instead of the default ; character after each SQL statement?

book

Article ID: KB0085331

calendar_today

Updated On:

Products Versions
TIBCO ActiveMatrix BusinessWorks Plug-in for Database -
Not Applicable -

Description

Resolution:
It is because trigger statements use semicolons to delimit multiple SQL statements within it.  We arbitrary chose the # character as the SQL statement terminator. In this situation, you must set the SQL terminator to the # character before you run the scripts.  In SPUFI, you can set it in one of the panels. In DSNTEP2 or DSNTIAD utilities, you can code PARMS (‘SQLTERM(#)’) in the RUN command. For other venue, consult the respective manuals.

Issue/Introduction

For DB2: If the RepoOnly = TRUE option is turned on in the ini file, why is a # character generated instead of the default ; character after each SQL statement?
Powered by Wolken Software