Similarly one can find the meaning of other DB2 to Vendor API return codes, in this way.

Note, however, that this return code is not the return code from the Vendor API. To find this out we must at the very first instance of the db2diag.log message, in the above group of diagnostic messages:

sqlint32 takes up 4 bytes, so the return code from the vendor function is to be found in the first 4 bytes of the above diagnotics data entry. This is hexadecimal dump (hexdump).

So, in the above case we see that the value is hex 0000 01AA which is corresponds to decimal 426. Note: the value for the description array is 3432 3520 3432 3600 0000 00000000 0000 0000 0000 0000 0000 0000 0000 0000 which happens to contain the return code value. We should not rely soley on the description array though.

Now that we have the Vendor's return code one can find out what that means by simply looking up the Vendor API documentation. In the case of TSM one can find this here:

Now, if the above DATA component contains all zeros and the db2diag.log contains a number of signal handler diagnostic entries, then it is likely that an abnormal termination has occurred in the vendor's library.

In this case you would see a rc = 30 in the sqlpgArchiveLogFile function.