I have a question concerning the various script centers on the iSeries. When I use iSeries Navigator to run a script on the iSeries to create a table, the default authority is the *CHANGE (via CRTPF AUT(*LIBCRTAUT), CRTLIB CRTAUT(*SYSVAL) and system value QCRTAUT). When I use the script center from DB2 UDB for Windows and use the Client Configuration Assistant to attach to the iSeries, the default authority is *EXCLUDE. How is this possible? Can this authority match the system values?
The behavior is different because the SQL script centers are using a different SQL naming convention. If the naming convention is *SYS, DB2 UDB would use the QCRTAUT system value. When the naming convention is *SQL, then public authority is set to *EXCLUDE. This behavior is documented in the iSeries SQL Reference Manual.
MORE INFORMATION ON THIS TOPIC
Search400.com's targeted search engine: Get relevant information on DB2/400.
The Best Web Links: tips, tutorials and more.
Check out this Search400.com Featured Topic: Database issues resolved
Dig Deeper on DB2 UDB (universal databases)
Related Q&A from Kent Milligan
Create a host variable of the where in statement on the fly with dynamic SQL. Continue Reading
To solve the SQL error -321 on IBM i6.1, use the new values statement to overcome the error. If you are using an older release, declare a cursor ... Continue Reading
When working with DB2 files with columns that have both short and long names, there is no option choose which column names are returned via ODBC ... Continue Reading