Strange SQLSTATE 51002

Georg Peter

Strange SQLSTATE 51002
Environment: DB2 for z/OS V7

Collegues,

we are dealing with a strange SQLSTATE 51002:

SQLABC = 136
SQLCODE = -805
SQLERRML = 045
SQLERRMC = 'A03DB2..DTBIN2DC.consistencytoken.PLDACIC9'
SQLERRP = 'DSNXEPM'
SQLERRD(1-6)= -250, 000, 00000, -1, 00000, 000
SQLWARN(0-A)='_ _ _ _ _ _ _ _ _ _ _ '
SQLSTATE = 51002

But: The mentioned plan PLDACIC9 is still there/valid/operative, also the
program DTBIN2DC (bound into a collection). And this collection is really
associated with the plan PLDACIC9.

We saw that in SQLERRML are two points after the location name - normally
here the collection id has to be - or not ? Any ideas what is going wrong
here ?

Thanks in advance.

With kind regards - mit freundlichen Gruessen,
G e o r g H . P e t e r

---------------------------------------------------------------------------------
Welcome to the IDUG DB2-L list. To unsubscribe, go to the archives and home page at http://www.idugdb2-l.org/archives/db2-l.html. From that page select "Join or Leave the list". The IDUG DB2-L FAQ is at http://www.idugdb2-l.org. The IDUG List Admins can be reached at [login to unmask email] Find out the latest on IDUG conferences at http://conferences.idug.org/index.cfm

Agus Kwee

Re: Strange SQLSTATE 51002
(in response to Georg Peter)
Peter,

I did a test to produce sqlcode = -805
I received similar sqlerrmc text that exclude the collection-id.
The sqlerrml contained 40 which is 5 less than the one you
received because my location-d is 2 bytes shorter than your
location-id and my dbrm-name is 3 bytes shorter than your
dbrm-name.
The difference is the last 2 bytes returned in my sqlerrmc contains
'03' the 'REASON' that further explained the -805 sqlcode.
How long is the consistency-token in your sqlerrmc?
If you add all the returned text in sqlerrmc does it add up to
the 45 value in sqlerrml?

Regards,
Agus Kwee
Themis Training
http://www.themisinc.com

----- Original Message -----
From: "Peter, Georg" <[login to unmask email]>
Newsgroups: bit.listserv.db2-l
To: <[login to unmask email]>
Sent: Tuesday, January 03, 2006 7:00 AM
Subject: [DB2-L] Strange SQLSTATE 51002


> Environment: DB2 for z/OS V7
>
> Collegues,
>
> we are dealing with a strange SQLSTATE 51002:
>
> SQLABC = 136
> SQLCODE = -805
> SQLERRML = 045
> SQLERRMC = 'A03DB2..DTBIN2DC.consistencytoken.PLDACIC9'
> SQLERRP = 'DSNXEPM'
> SQLERRD(1-6)= -250, 000, 00000, -1, 00000, 000
> SQLWARN(0-A)='_ _ _ _ _ _ _ _ _ _ _ '
> SQLSTATE = 51002
>
> But: The mentioned plan PLDACIC9 is still there/valid/operative, also the
> program DTBIN2DC (bound into a collection). And this collection is really
> associated with the plan PLDACIC9.
>
> We saw that in SQLERRML are two points after the location name - normally
> here the collection id has to be - or not ? Any ideas what is going wrong
> here ?
>
> Thanks in advance.
>
> With kind regards - mit freundlichen Gruessen,
> G e o r g H . P e t e r
>
> --------------------------------------------------------------------------
-------
> Welcome to the IDUG DB2-L list. To unsubscribe, go to the archives and
home page at http://www.idugdb2-l.org/archives/db2-l.html. From that page
select "Join or Leave the list". The IDUG DB2-L FAQ is at
http://www.idugdb2-l.org. The IDUG List Admins can be reached at
[login to unmask email] Find out the latest on IDUG conferences at
http://conferences.idug.org/index.cfm
>

---------------------------------------------------------------------------------
Welcome to the IDUG DB2-L list. To unsubscribe, go to the archives and home page at http://www.idugdb2-l.org/archives/db2-l.html. From that page select "Join or Leave the list". The IDUG DB2-L FAQ is at http://www.idugdb2-l.org. The IDUG List Admins can be reached at [login to unmask email] Find out the latest on IDUG conferences at http://conferences.idug.org/index.cfm