First guess is that you have different fixpak levels between DB2 client (WAS Server) and DB2 server and need to rebind the client packages.
Use the db2cli.lst in SQLLIB/bnd for that.
> db2 connect to <your_db_name>
> db2 bind @db2cli.lst blocking all grant public
CLI driver is more or less the underlying client software.
for the sql code enter (works for any sqlcode):
> db2 ? sql0805
I dont want to print the output here, it is rather long, but it also states the following:
> If the DB2 utility programs need to be rebound to the database,
> the database administrator can accomplish this by issuing one of
> the following CLP command from the bnd subdirectory of the
> instance, while connected to the database:
>
> o "db2 bind @db2ubind.lst blocking all grant public" for the
> DB2 utilities.
>
> o "db2 bind @db2cli.lst blocking all grant public" for CLI.
Message Codes and Reference gives you the same:
http://publib.boulder.ibm.com/infoce...e/rsql0800.htm
NULLID are usually some of those packages. Only with the full name this can be checked finally, also where the package belongs to.