Jerry,
Just out of curiosity, does the password contain any
non-alpha/non-numeric characters that might be causing the issue?
Shouldn't be a problem but weirder things have happened.
Thanks,
Matthew Stokes
Software Engineer
Internet Technologies
IBM Server Group
Certified: RHCE, MCSE,CLPD(R5), IBM Specialist
Hi,
I've recently installed DB2 Connect EE V7.1 on Solaris 5.6, connecting to
DB2 for OS/390 V5.1. The node, database and DCS directory entries at the
Connect gateway instance were all correctly catalogued, and I could access
the mainframe databases from the Connect gateway server. On a unix db2
client, the node and database directories were also correctly catalogued,
pointing at the gateway server. I don't like typing passwords visibly on
the screen if I can avoid it, so I entered from the client command line:
db2 connect to <mfdb> user <userid>
I was prompted for my mainframe password, which I entered. I then got:
SQL30081N A communication error has been detected. Communication
protocol
being used: "TCP/IP". Communication API being used: "SOCKETS".
Location
where the error was detected: "". Communication function detecting
the error:
"connect". Protocol specific error code(s): "146", "*", "*".
SQLSTATE=08001
No amount of attempts and identical uncatalog/catalog activity could get
around this. All TCP/IP components were in place and functioning correctly
according to the unix bods.
The same command from a Win/NT client, again prompting for a mainframe
password, connected successfully to the mainframe and I could retrieve
data.
At IBM's suggestion, I extended the command on the unix client to
db2 connect to <mfdb> user <userid> using <password>
This time it connected successfully and I could retrieve data. No changes
to the catalogs had been made since the previous failure. Since that first
successful connection, I am able to issue the original command:
db2 connect to <mfdb> user <userid>
prompting for a password and now connecting successfully.
Has anyone seen this before? Can anyone suggest why a unix client (and not
an NT client) was unable to attach through a DB2 Connect gateway (which
was itself working correctly) until a RACF password had been appended to
the CONNECT command, after which this was not required? Not a big deal in
retrospect, but weird!
Regards,
Jerry Long
MBL DBA
NOTICE
This e-mail and any attachments are confidential and may contain copyright
material of Macquarie Bank or third parties. If you are not the intended
recipient of this email you should not read, print, re-transmit, store or
act in reliance on this e-mail or any attachments, and should destroy all
copies of them. Macquarie Bank does not guarantee the integrity of any
emails or any attached files. The views or opinions expressed are the
author's own and may not reflect the views or opinions of Macquarie Bank.
=====
To unsubscribe, send 'unsubscribe' to [EMAIL PROTECTED]
For other info (and scripts), see http://people.mn.mediaone.net/scottrmcleod
