SQLCODE: -904 00D3002D 00001006

Darren Kilpatrick

SQLCODE: -904 00D3002D 00001006
Hello,
I am trying to connect from one mainframe to another. I have set up the communication database entries (for our shop, we needed LOCATIONS, USERNAMES, IPNAMES) on the source mainframe, yet I am still getting this error: SQLCODE: -904 00D3002D 00001006. I have connected to another LPAR (the IP address is slightly different) on the target mainframe successfully. Is there anything else, system-wise, that would need to be done so the mainframes can talk to each other? I have not been able to find much on this error message anywhere. Thanks,

_____________________________________________________________________
* IDUG EMEA * Prague, Czech Republic * 14-18 November 2011 * http://IDUG.ORG/EMEA *
* If you are going to attend only one conference this year, this is it! *
_____________________________________________________________________
http://www.IDUG.org/mentor
How can you expand your staff or do succession planning in this economy?
Mentoring is a proven, economical, way to train the next generation of DB2 Users!
_____________________________________________________________________

If you need to change settings, http://www.idug.org/cgi-bin/wa?A0=DB2-L is the home of IDUG's Listserv

Robert Hall

Re: SQLCODE: -904 00D3002D 00001006
(in response to Darren Kilpatrick)
Darren,

I pasted the error message text below of 00D3002D. You didn't mention which version(s) of DB2 you are running.

Maybe you have a typo in one of the tables such as the outbound USERNAMES entry? Maybe the DB2 Authorization IDs are different between the source and target mainframes, causing a mismatch? Have you tried using "A" for SECURITY_OUT (Already verified?)

As I'm sure you know, the columns for these tables are defined in an appendix in the SQL Guide, but the descriptions are a bit cryptic.



Good luck,

Robert




00D3002D
Explanation: The remote server was not successfully connected. The
SYSIBM.USERNAMES table did not contain an outbound row, the TYPE column
specified as an 'O' describing the remote authorization identifier to be
used for the plan owner DB2 authorization ID. When the USERNAMES column in
SYSIBM.LUNAMES specifies 'O' or 'B' requiring outbound name translation,
the SYSIBM.USERNAMES table must contain entries describing the remote
authorization IDs to be used for each DB2 authorization ID communicating
with the LU.

This abend reason code is issued by the following CSECTs: DSNLTXAC
DSNLTMIG

System Action: A resource unavailable is returned to the application. The
request is not sent to the remote site.

Operator Response: Notify the communications database administrator.

System Programmer Response: Make sure the USERNAMES column in
SYSIBM.LUNAMES has been specified correctly for the indicated LUNAME. If
you intend to use remote authorization IDs that differ from DB2
authorization IDs, verify that the SYSIBM.USERNAMES table has rows that
correctly specify the remote authorization ID to be used for each possible
DB2 authorization ID.

Problem Determination: Analyze the SYSIBM.USERNAMES table for an incorrect or missing entry.





-----Original Message-----
From: IDUG DB2-L [mailto:[login to unmask email] On Behalf Of Darren Kilpatrick
Sent: Friday, December 10, 2010 2:00 PM
To: [login to unmask email]
Subject: [DB2-L] SQLCODE: -904 00D3002D 00001006

Hello,
I am trying to connect from one mainframe to another. I have set up the communication database entries (for our shop, we needed LOCATIONS, USERNAMES, IPNAMES) on the source mainframe, yet I am still getting this error: SQLCODE: -904 00D3002D 00001006. I have connected to another LPAR (the IP address is slightly different) on the target mainframe successfully. Is there anything else, system-wise, that would need to be done so the mainframes can talk to each other? I have not been able to find much on this error message anywhere. Thanks,

_____________________________________________________________________
* IDUG EMEA * Prague, Czech Republic * 14-18 November 2011 * http://IDUG.ORG/EMEA *
* If you are going to attend only one conference this year, this is it! *
_____________________________________________________________________
http://www.IDUG.org/mentor
How can you expand your staff or do succession planning in this economy?
Mentoring is a proven, economical, way to train the next generation of DB2 Users!
_____________________________________________________________________

If you need to change settings, http://www.idug.org/cgi-bin/wa?A0=DB2-L is the home of IDUG's Listserv

_____________________________________________________________________
* IDUG EMEA * Prague, Czech Republic * 14-18 November 2011 * http://IDUG.ORG/EMEA *
* If you are going to attend only one conference this year, this is it! *
_____________________________________________________________________
http://www.IDUG.org/mentor
How can you expand your staff or do succession planning in this economy?
Mentoring is a proven, economical, way to train the next generation of DB2 Users!
_____________________________________________________________________

If you need to change settings, http://www.idug.org/cgi-bin/wa?A0=DB2-L is the home of IDUG's Listserv

Chris Tee

Re: SQLCODE: -904 00D3002D 00001006
(in response to Robert Hall)
Did you read the Codes manual for 00D3002D, it explains what's required
fairly well. If you are doing outbound translation, you need an entry for
the plan owner as well as for the id doing the connect. What USERNAMES
entries have been set up for the location that works?

-----Original Message-----
From: Darren Kilpatrick
Sent: Friday, December 10, 2010 7:00 PM Newsgroups: bit.listserv.db2-l
To: [login to unmask email]
Subject: [DB2-L] SQLCODE: -904 00D3002D 00001006

Hello,
I am trying to connect from one mainframe to another. I have set up the
communication database entries (for our shop, we needed LOCATIONS,
USERNAMES, IPNAMES) on the source mainframe, yet I am still getting this
error: SQLCODE: -904 00D3002D 00001006. I have connected to another LPAR
(the IP address is slightly different) on the target mainframe successfully.
Is there anything else, system-wise, that would need to be done so the
mainframes can talk to each other? I have not been able to find much on
this error message anywhere. Thanks,

_____________________________________________________________________
* IDUG EMEA * Prague, Czech Republic * 14-18 November 2011 *
http://IDUG.ORG/EMEA *
* If you are going to attend only one conference this year, this is it!
*
_____________________________________________________________________
http://www.IDUG.org/mentor
How can you expand your staff or do succession planning in this economy?
Mentoring is a proven, economical, way to train the next generation of DB2
Users!
_____________________________________________________________________

If you need to change settings, http://www.idug.org/cgi-bin/wa?A0=DB2-L is
the home of IDUG's Listserv

_____________________________________________________________________
* IDUG EMEA * Prague, Czech Republic * 14-18 November 2011 * http://IDUG.ORG/EMEA *
* If you are going to attend only one conference this year, this is it! *
_____________________________________________________________________
http://www.IDUG.org/mentor
How can you expand your staff or do succession planning in this economy?
Mentoring is a proven, economical, way to train the next generation of DB2 Users!
_____________________________________________________________________

If you need to change settings, http://www.idug.org/cgi-bin/wa?A0=DB2-L is the home of IDUG's Listserv

James Campbell

Re: SQLCODE: -904 00D3002D 00001006
(in response to Chris Tee)
We had a similar thing happening at our installation. As it turned out the fields that were supposed to be Varchar got padded out with blank characters so we got a mismatch when db2 tried to compare the locations.

Check the length of the fields (location and linkname) to be sure that you do not have extra spaces in them.

Jim Campbell
Sr. Database Administrator
360-704-4015
[login to unmask email]

-----Original Message-----
From: IDUG DB2-L [mailto:[login to unmask email] On Behalf Of Darren Kilpatrick
Sent: Friday, December 10, 2010 11:00 AM
To: [login to unmask email]
Subject: [DB2-L] SQLCODE: -904 00D3002D 00001006

Hello,
I am trying to connect from one mainframe to another. I have set up the communication database entries (for our shop, we needed LOCATIONS, USERNAMES, IPNAMES) on the source mainframe, yet I am still getting this error: SQLCODE: -904 00D3002D 00001006. I have connected to another LPAR (the IP address is slightly different) on the target mainframe successfully. Is there anything else, system-wise, that would need to be done so the mainframes can talk to each other? I have not been able to find much on this error message anywhere. Thanks,

_____________________________________________________________________
* IDUG EMEA * Prague, Czech Republic * 14-18 November 2011 * http://IDUG.ORG/EMEA *
* If you are going to attend only one conference this year, this is it! *
_____________________________________________________________________
http://www.IDUG.org/mentor
How can you expand your staff or do succession planning in this economy?
Mentoring is a proven, economical, way to train the next generation of DB2 Users!
_____________________________________________________________________

If you need to change settings, http://www.idug.org/cgi-bin/wa?A0=DB2-L is the home of IDUG's Listserv

_____________________________________________________________________
* IDUG EMEA * Prague, Czech Republic * 14-18 November 2011 * http://IDUG.ORG/EMEA *
* If you are going to attend only one conference this year, this is it! *
_____________________________________________________________________
http://www.IDUG.org/mentor
How can you expand your staff or do succession planning in this economy?
Mentoring is a proven, economical, way to train the next generation of DB2 Users!
_____________________________________________________________________

If you need to change settings, http://www.idug.org/cgi-bin/wa?A0=DB2-L is the home of IDUG's Listserv