DSNREXX - failure in EXECSQL

[Steve Coalbran]

Hi Pete,
No, I did a LOGON SE1661 and retried and I get the same
Steve

[petwir]

RonB has a VERY GOOD POINT. I don't see the CONNECT statement in your posted code either?

[Steve Coalbran]

Hi Pete, (I don't see an append from RonB?)
I added the CONNECT...
CALL SQL "CONNECT" ssid
I get this now ...different

*************** SQLCA INFORMATION *********************************************
*                                                                             *
* SQLCODE     = -805                                                          *
* SQLSTATE    = 51002                                                         *
* SQLERRMC    = MOPDB40..DSNREXX.179B1B7F010832EC:DSNREXX:03                  *
* SQLERRP     = DSNXEPM                                                       *
* SQLERRD(1)  = -251                                                          *
*        (4)  = -1                                                            *

Steve

[don.leahy]

Originally Posted by petwir

RonB has a VERY GOOD POINT. I don't see the CONNECT statement in your posted code either?

That was my first thought too. I tested the theory by disabling the CONNECT statement in one of my own DSNREXX programs. Much to my surprise, it worked anyway.

[don.leahy]

Originally Posted by Steve Coalbran

Hi Pete, (I don't see an append from RonB?)
I added the CONNECT...
CALL SQL "CONNECT" ssid
I get this now ...different

*************** SQLCA INFORMATION *********************************************
*                                                                             *
* SQLCODE     = -805                                                          *
* SQLSTATE    = 51002                                                         *
* SQLERRMC    = MOPDB40..DSNREXX.179B1B7F010832EC:DSNREXX:03                  *
* SQLERRP     = DSNXEPM                                                       *
* SQLERRD(1)  = -251                                                          *
*        (4)  = -1                                                            *

Steve

I have seen this before. It may be that DSNREXX is not installed properly in your shop. Time to talk to your DBA and/or DB2 sysprog.

[Steve Coalbran]

Originally Posted by RonB

Don't see it, but did you issue a "CONNECT" to the DB2 Subsystem before trying to run SQL?

AHA! Now I see it!
Steve

[Steve Coalbran]

Hi Don,
OK, sounds like a job for next week!
As it's MOP (IBM DEMO m/c in Montpellier) j'ai peut-être besoin de rafraîchir mon Français ?!...
...Nah! zTec speak better English than I do!
Steve