SEO

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.

TIA
Raquel.

Are you running DB2 Connect on Solaris by chance? According to the DB2
Messages and Codes manual, errno 146 occurs on Solaris and means
"Connection Refused". And SQLCODE -30081 indicates a comm error somewhere.

Check you TCP/IP and DB2 Comm-related settings on the DB2 Connect Server.

Larry Edelstein

Raquel wrote:
> 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.
>
> TIA
> Raquel.
>