Could you explain why some SQL messages do not possess a SQLSTATE ?
Why not transmitting the SQLSTATE of the original <sqlcode>, for example if
you get a -911 on a RUNSTATS ?
SQL2310N The utility could not generate statistics. Error
"<sqlcode>" was returned.
Thanks,
JM
Can you calirify? Do you want
SQL2310N The utility could not generate statistics. Error
"<sqlcode>" _with_SQLSTATE_"<sqlstate>"_ was returned.
or
SQL2310N The utility could not generate statistics. Error
"<sqlcode>" was returned.
_SQLSTATE=xxxxx_
Cheers
Serge
--
Serge Rielau
DB2 SQL Compiler Development
IBM Toronto Lab
It would be more like:
SQL2310N The utility could not generate statistics. Error
"<sqlcode>" was returned.
_SQLSTATE=xxxxx_
The RUNSTATS error seems to be sometimes SQL2310N or another code (without
SQLSTATE), other times you could get a SQLCODE and SQLSTATE (at least in V7
... I was trapping SQLSTATEs in shell scripts and realized I only got
SQLCODEs, so missed some info).
But why such a difference as below - can you give a rule of SQLCODEs with or
without SQLSTATEs ?
* RUNSTATS ON TABLE DB2ADMIN.TITI gives:
SQL2306N The table or index "DB2ADMIN.TITI" does not exist. (no SQLSTATE)
* SELECT * FROM DB2ADMIN.TITI gives:
SQL0204N "DB2ADMIN.TITI" is an undefined name. SQLSTATE=42704
Cheers,
Jean-Marc
"Serge Rielau" <sri...@ca.eye-be-em.com> a écrit dans le message de
news:cangnn$h9g$1...@hanover.torolab.ibm.com...
Visit the DB2 UDB and DB2 Connect Online Support site at:
http://www.ibm.com/software/data/db2/udb/winos2unix/support