How do you interpret an SQLCODE and the associated tokens reported in an SQL0969N error message?
The client support used with DB2® for Linux®, UNIX, and Windows returns message SQL0969N when reporting host SQLCODEs and tokens for which it has no equivalent code.
Here is an example of message SQL0969N:
SQL0969N There is no message text corresponding to SQL error
"-7008" in the Database Manager message file on this workstation.
The error was returned from module "QSQOPEN" with original
tokens "TABLE1 PRODLIB1 3".
Use the Display Message Description (DSPMSGD) command to interpret the code and tokens:
DSPMSGD SQL7008 MSGF(QSQLMSG)
Select option 1 (Display message text) and the system presents the Display Formatted Message Text display. The three tokens in the message are represented by &1, &2, and &3 in the display. The reason code in the example message is 3, which points to Code 3 in the list at the bottom of the display.
Display Formatted Message Text
System: RCHASLAI
Message ID . . . . . . . . . : SQL7008
Message file . . . . . . . . : QSQLMSG
Library . . . . . . . . . : QSYS
Message . . . . : &1 in &2 not valid for operation.
Cause . . . . . : The reason code is &3. A list of reason codes follows:
-- Code 1 indicates that the table has no members.
-- Code 2 indicates that the table has been saved with storage free.
-- Code 3 indicates that the table is not journaled, the table is
journaled to a different journal than other tables being processed under
commitment control, or that you do not have authority to the journal.
-- Code 4 indicates that the table is in a production library but the user
is in debug mode with UPDPROD(*NO); therefore, production tables may not be
updated.
-- Code 5 indicates that a table, view, or index is being created into a
production library but the user is in debug mode with UPDPROD(*NO);
therefore, tables, views, or indexes may not be created.
More...
Press Enter to Continue.
F3=Exit F11=Display unformatted message text F12=Cancel