SQL CODE -30000 when 2 DB2s are connected via batch

Max Scarpa

SQL CODE -30000 when 2 DB2s are connected via batch
Estemeed listers

We have 2 DB2s connected by some batch jobs that update some tables in the
local and remote DB2s. They are in different version (V6 & V7) and from
time to time we meet the following error in MVS log:

DSNL031I -D20P DSNLCMSR DRDA EXCEPTION CONDITION IN 698
RESPONSE FROM SERVER LOCATION=DB2P FOR THREAD WITH
LUWID=ITFCTN00.D20PFCT.BDFE5B34E76B
REASON=00D31018
ERROR ID=DSNLCMSR0001
CORRELATION ID=SIRJP113
CONNECTION ID=BATCH
IFCID=0192
SEE TRACE RECORD WITH IFCID SEQUENCE NUMBER=00000000

In the batch job we have:

DSNT408I SQLCODE = -30000, ERROR: EXECUTION FAILED DUE TO A
DISTRIBUTION PROTOCOL ERROR THAT WILL NOT AFFECT THE
SUCCESSFUL EXECUTION OF SUBSEQUENT COMMANDS OR SQL STATEMENTS:
REASON 124C (0118)
DSNT418I SQLSTATE = 58008 SQLSTATE RETURN CODE
DSNT415I SQLERRP = DSNLCMSR SQL PROCEDURE DETECTING ERROR
DSNT416I SQLERRD = 0 0 0 -1 0 0 SQL DIAGNOSTIC INFORMATION
DSNT416I SQLERRD = X'00000000' X'00000000' X'00000000'
X'FFFFFFFF' X'00000000' X'00000000' SQL DIAGNOSTIC
INFORMATION

Reason 124C says it's a syntax error in DRDA but I'm not able to know more
about it.

After this erron in batch job we have a -918 error:

DSNT408I SQLCODE = -918, ERROR: THE SQL STATEMENT CANNOT BE EXECUTED
BECAUSE A CONNECTION HAS BEEN LOST
DSNT418I SQLSTATE = 51021 SQLSTATE RETURN CODE
DSNT415I SQLERRP = DSNLXRUW SQL PROCEDURE DETECTING ERROR
DSNT416I SQLERRD = 0 0 0 -1 0 0 SQL DIAGNOSTIC INFORMATION
DSNT416I SQLERRD = X'00000000' X'00000000' X'00000000'
X'FFFFFFFF' X'00000000' X'00000000' SQL DIAGNOSTIC
INFORMATION


Had anyone meet these errors before ? Any help/hint ? After the error if we
rerun the job it ends OK.

Thank you in advance

Max Scarpa

---------------------------------------------------------------------------------
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: SQL CODE -30000 when 2 DB2s are connected via batch
(in response to Max Scarpa)
If my memory serves me correctly, our shop experienced a VTAM related
problem while on V6. We had two V6 DB2s connected and were using stored procedures
when this happened, and would receive a similar error.(-30018, I believe)
An IBM VTAM fix resolved our issue.

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

Chris Tee

Re: SQL CODE -30000 when 2 DB2s are connected via batch
(in response to Ava Collins)
Max

Have a look at PQ37315, it's quite old but it sounds like your symptoms.

Chris

Chris Tee
DB2 DBA
Infrastructure Services & SAP Solutions (iS3)
Information Systems Europe
SONY Europe
Tel: +44 (0) 1256 82 8342


-----Original Message-----
From: DB2 Data Base Discussion List [mailto:[login to unmask email]
Sent: 01 December 2005 12:04
To: [login to unmask email]
Subject: [DB2-L] SQL CODE -30000 when 2 DB2s are connected via batch


Estemeed listers

We have 2 DB2s connected by some batch jobs that update some tables in the
local and remote DB2s. They are in different version (V6 & V7) and from
time to time we meet the following error in MVS log:

DSNL031I -D20P DSNLCMSR DRDA EXCEPTION CONDITION IN 698
RESPONSE FROM SERVER LOCATION=DB2P FOR THREAD WITH
LUWID=ITFCTN00.D20PFCT.BDFE5B34E76B
REASON=00D31018
ERROR ID=DSNLCMSR0001
CORRELATION ID=SIRJP113
CONNECTION ID=BATCH
IFCID=0192
SEE TRACE RECORD WITH IFCID SEQUENCE NUMBER=00000000

In the batch job we have:

DSNT408I SQLCODE = -30000, ERROR: EXECUTION FAILED DUE TO A
DISTRIBUTION PROTOCOL ERROR THAT WILL NOT AFFECT THE
SUCCESSFUL EXECUTION OF SUBSEQUENT COMMANDS OR SQL STATEMENTS:
REASON 124C (0118)
DSNT418I SQLSTATE = 58008 SQLSTATE RETURN CODE
DSNT415I SQLERRP = DSNLCMSR SQL PROCEDURE DETECTING ERROR
DSNT416I SQLERRD = 0 0 0 -1 0 0 SQL DIAGNOSTIC INFORMATION
DSNT416I SQLERRD = X'00000000' X'00000000' X'00000000'
X'FFFFFFFF' X'00000000' X'00000000' SQL DIAGNOSTIC
INFORMATION

Reason 124C says it's a syntax error in DRDA but I'm not able to know more
about it.

After this erron in batch job we have a -918 error:

DSNT408I SQLCODE = -918, ERROR: THE SQL STATEMENT CANNOT BE EXECUTED
BECAUSE A CONNECTION HAS BEEN LOST
DSNT418I SQLSTATE = 51021 SQLSTATE RETURN CODE
DSNT415I SQLERRP = DSNLXRUW SQL PROCEDURE DETECTING ERROR
DSNT416I SQLERRD = 0 0 0 -1 0 0 SQL DIAGNOSTIC INFORMATION
DSNT416I SQLERRD = X'00000000' X'00000000' X'00000000'
X'FFFFFFFF' X'00000000' X'00000000' SQL DIAGNOSTIC
INFORMATION


Had anyone meet these errors before ? Any help/hint ? After the error if we
rerun the job it ends OK.

Thank you in advance

Max Scarpa

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

************************************************************************
The information contained in this message or any of its attachments may be confidential and is intended for the exclusive use of the addressee(s). Any disclosure, reproduction, distribution or other dissemination or use of this communication is strictly prohibited without the express permission of the sender. The views expressed in this email are those of the individual and not necessarily those of Sony or Sony affiliated companies. Sony email is for business use only.

This email and any response may be monitored by Sony to be in compliance with Sony’s global policies and standards

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