Help with Stored Procedure execution ....

Raquel Rodriguez

Help with Stored Procedure execution ....
This is a stored procedure that resides on Mainframe
and gets executed on the client by connecting to the
mainframe through DB2 connect. It was executing fine
till yesterday when I executed a table change and
successfully Rebound the package associated with the
stored procedure. Since then, it is giving a strange
problem. When the client executes the program that
calls the stored procedure SP1, the stored procedure
does not get executed *at all* and the control just
returns back to the calling program..no error
message..nothing. The monitor on the mainframe (TMON),
for that execution just shows that a package SYSSTAT
is being executed (which I believe is a DB2 connect
package); however SP1 (which should also have been
executed along with SYSSTAT package) is not shown to
be executed at all. There are no error messages in
SPAS (we are not using WLM) or MSTR. DB2DIAG.LOG on
DB2 connect server shows the following error (which we
are not even sure is related to this instance of
stored procedure execution):

2004-12-11-17.14.32.047372 Instance:db2cm Node:000
PID:17544(db2agentg ()) TID:1 Appid:none
common communication sqlcctcpconnr Probe:110

DIA3202C The TCP/IP call "connect" returned an
errno="146".

2004-12-17-08.22.27.096147 Instance:db2cm Node:000
PID:14519(db2agentg (DSNP )) TID:1
Appid:B49B0BDF.EE06.013846201710
DRDA Application Server sqljsTermAgentReply Probe:10

DIA5000C A DRDA AS token "AGENT TERMINATING" was
detected. The diagnostic data
returned is (SRVDGN): "SQLERRP:SQLJCMN
SQLCODE:-30081".
ALERT :26

PID:14519 TID:1 Node:000 Title: SQLCA
sqlcaid : SQLCA sqlcabc: 136 sqlcode: -30081
sqlerrml: 43
sqlerrmc: 32 * 0 TCP/IP SOCKETS 180.155.203.254 send
sqlerrp : SQLJCMN \2016
sqlerrd : (1) 0x81360012 (2) 0x00000012 (3)
0x00000000
(4) 0x00000000 (5) 0x00000000 (6)
0x00000000
sqlwarn : (1) (2) (3) (4) (5)
(6)
(7) (8) (9) (10) (11)
sqlstate:


Any pointers would be greatly appreciated. This is
Production.

TIA
Raquel.



__________________________________
Do you Yahoo!?
Jazz up your holiday email with celebrity designs. Learn more.
http://celebrity.mail.yahoo.com

---------------------------------------------------------------------------------
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

Ava Collins

Re: Help with Stored Procedure execution ....
(in response to Raquel Rodriguez)

:-30081


Looks like you are receiving a connection error. We experienced this error
when there was a problem with VTAM on the mainframe. That was over a year
ago, but IBM had a fix for it.

Which version of DB2 are you using?

Is your stored procedure "stay resident" yes? Have you stopped and started
the stored procedure? Is it started?.

I'm not experienced with non-WLM stored procedures. We've also had issues
when our load library on the mainframe went into an extra extent and our newly
changed program was in that extent. The environment didn't recognized that
the new extent existed until it was refreshed.

Hope this helps.

Jacquie



---------------------------------------------------------------------------------
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