Triton Db2 Geek

Confessions of a DB2 geek

IBM Gold Consultant Program and IBM Premier business Partner

DSNWMSGS and IFCID 376

February 19th, 2014 - by

IFCID 376 is new with DB2 V11, and provides a way for DB2 to tell us about SQL statement compatibility issues with applications running in V11 but in V10 compatibility mode (BIND with APPLCOMPAT(V10R1)). The first field of the returned IFCID data element – QW0376FN – is a full word reason ID, i.e. why the record was cut. In common with other IFCIDs, xxx.SDSNIVPD(DSNWMSGS) contains explanations for each of the fields in the returned IFCID – in this case, the reason codes are interpreted in the section about IFCID 366 reason code (QW0366FN).

 

A few of the reason codes have been mislabelled – possibly due to the way that they have been documented in the assembler macro (cf xxx.SDSNMACS(DSNDQW05)). Following a little testing, we’re happy to report that the correct interpretations for values 1104 thru 1107 should be:

 

 

1104: THE CLIENT_ACCTNG SPECIAL REGISTER WAS SET TO        

      A VALUE THAT IS LONGER THAN THE SUPPORTED LENGTH     

      PRIOR TO V11. THE VALUE WAS TRUNCATED.               

1105: THE CLIENT_APPLNAME SPECIAL REGISTER WAS SET TO      

      A VALUE THAT IS LONGER THAN THE SUPPORTED LENGTH     

      PRIOR TO V11. THE VALUE WAS TRUNCATED.              

1106: THE CLIENT_USERID SPECIAL REGISTER WAS SET TO A      

      VALUE THAT IS LONGER THAN THE SUPPORTED LENGTH       

      PRIOR TO V11. THE VALUE WAS TRUNCATED.              

1107: THE CLIENT_WRKSTNNAME SPECIAL REGISTER WAS SET TO    

      A VALUE THAT IS LONGER THAN THE SUPPORTED LENGTH     

      PRIOR TO V11. THE VALUE WAS TRUNCATED.              

 

Note that this is not fixed in UI14462…

 

Comments

« »

Tag Archives