Re: DB2 Connect Userid Problem

Philip Gunning

Re: DB2 Connect Userid Problem
(in response to Michael Dempsey)
Micahel, What error message are you seeing in the mstr log? This will help
to pinpoint the problem and ensure that you are getting to the subsystem.
Is this a new subsystem? Are you using RACF? Is a new subsystem, then you
need to activate the RACF Dist class and be attached to it to connect to
DB2. HTH Phil

-----Original Message-----
From: Dempsey, Michael
To: [login to unmask email]
Sent: 1/5/01 8:35 AM
Subject: DB2 Connect Userid Problem

We're using DB2 Connect 5.2 & DB2 UDB OS/390 V6. I'm trying to add a
new
database via CCA. Here's what I'm using to create it..

Protocol TCP/IP
Target Operating System OS/390
Hostname XXXXXX.XXX.XXX.XX (our mainframe address)
Port 446
Location Name MVS2DB2
Database Alias PEA0NPA

When I try to test the connection, I'm using a userid of an sqlid I
granted
sysadm auth to in our MVS2DB2 location (subsystem). I then receive the
following:

The connection test failed.

[IBM][CLI Driver] SQL30082N Attempt to establish connection failed with
security reason "0" ("NOT SPECIFIED"). SQLSTATE=08001

Which is equivalent to a -808, which still doesn't help this feeble
mind! I
have created other database's, but always with the same userid/password.
Is
there somewhere I need to put the new userid (sqlid) besides granting it
auth in DB2 mainframe? Thanks...



Michael Dempsey
UNC Health Care System



the DB2-L webpage at http://www.ryci.com/db2-l. The owners of the list
can

Michael Dempsey

DB2 Connect Userid Problem
We're using DB2 Connect 5.2 & DB2 UDB OS/390 V6. I'm trying to add a new
database via CCA. Here's what I'm using to create it..

Protocol TCP/IP
Target Operating System OS/390
Hostname XXXXXX.XXX.XXX.XX (our mainframe address)
Port 446
Location Name MVS2DB2
Database Alias PEA0NPA

When I try to test the connection, I'm using a userid of an sqlid I granted
sysadm auth to in our MVS2DB2 location (subsystem). I then receive the
following:

The connection test failed.

[IBM][CLI Driver] SQL30082N Attempt to establish connection failed with
security reason "0" ("NOT SPECIFIED"). SQLSTATE=08001

Which is equivalent to a -808, which still doesn't help this feeble mind! I
have created other database's, but always with the same userid/password. Is
there somewhere I need to put the new userid (sqlid) besides granting it
auth in DB2 mainframe? Thanks...



Michael Dempsey
UNC Health Care System



Harvey Puckett

Re: DB2 Connect Userid Problem
(in response to Philip Gunning)
Michael, I had this problem once, on an NT workstation and found that I had not catalogued my newly created (via CCA) database as a DCS Database. The "security" message threw me off. Seems that CCA does not issue the CATALOG DCS DB correctly, so do a LIST DCS and see if it looks good ... or if it is there at all.

...just a thought

//harve



Jose' Gomez

Re: DB2 Connect Userid Problem
(in response to Harvey Puckett)
Hello Michael:

1- In looking at your e-mail the 446 port number is the DB2 Connect
default port number when adding a new database/alias. Unless you are
using the same port # on the MVS side ???

Protocol TCP/IP
Target Operating System OS/390
Hostname XXXXXX.XXX.XXX.XX (our mainframe address)
Port 446
Location Name MVS2DB2
Database Alias PEA0NPA

2- Make sure the ID you are using is defined to RACF or Top Secret or the
security package your shop uses. You can grant any access to an ID, but
if you SYSADM person has not defined it to MVS, TSO or CMS etc... Your
connection will fail every time...

3- Make sure you password on MVS is not expired....

Mike Waters

Re: DB2 Connect Userid Problem
(in response to Mike Waters)
We had the same problem. We are using CA-TOP SECRET for security. To correct the problem, we had to permit the FACILITY associated with the DDF address space to the USERID.

>>> "Dempsey, Michael" <[login to unmask email]> 01/05/01 10:35AM >>>
We're using DB2 Connect 5.2 & DB2 UDB OS/390 V6. I'm trying to add a new
database via CCA. Here's what I'm using to create it..

Protocol TCP/IP
Target Operating System OS/390
Hostname XXXXXX.XXX.XXX.XX (our mainframe address)
Port 446
Location Name MVS2DB2
Database Alias PEA0NPA

When I try to test the connection, I'm using a userid of an sqlid I granted
sysadm auth to in our MVS2DB2 location (subsystem). I then receive the
following:

The connection test failed.

[IBM][CLI Driver] SQL30082N Attempt to establish connection failed with
security reason "0" ("NOT SPECIFIED"). SQLSTATE=08001

Which is equivalent to a -808, which still doesn't help this feeble mind! I
have created other database's, but always with the same userid/password. Is
there somewhere I need to put the new userid (sqlid) besides granting it
auth in DB2 mainframe? Thanks...



Michael Dempsey
UNC Health Care System






Mike Waters

Re: DB2 Connect Userid Problem
(in response to Jose' Gomez)
test

>>> "Dempsey, Michael" <[login to unmask email]> 01/05/01 10:35AM >>>
We're using DB2 Connect 5.2 & DB2 UDB OS/390 V6. I'm trying to add a new
database via CCA. Here's what I'm using to create it..

Protocol TCP/IP
Target Operating System OS/390
Hostname XXXXXX.XXX.XXX.XX (our mainframe address)
Port 446
Location Name MVS2DB2
Database Alias PEA0NPA

When I try to test the connection, I'm using a userid of an sqlid I granted
sysadm auth to in our MVS2DB2 location (subsystem). I then receive the
following:

The connection test failed.

[IBM][CLI Driver] SQL30082N Attempt to establish connection failed with
security reason "0" ("NOT SPECIFIED"). SQLSTATE=08001

Which is equivalent to a -808, which still doesn't help this feeble mind! I
have created other database's, but always with the same userid/password. Is
there somewhere I need to put the new userid (sqlid) besides granting it
auth in DB2 mainframe? Thanks...



Michael Dempsey
UNC Health Care System






Jose' Gomez

Re: DB2 Connect Userid Problem
(in response to Mike Waters)
Hello Michael:

In looking at your e-mail the 446 port number is the DB2 Connect default
port number when adding a new database/alias. Unless you are using the
same port # on the MVS side ???

Protocol TCP/IP
Target Operating System OS/390
Hostname XXXXXX.XXX.XXX.XX (our mainframe address)
Port 446
Location Name MVS2DB2
Database Alias PEA0NPA

Make sure the ID you are using is defined to RACF or Top Secret or the
security package your shop uses. You can grant any access to an ID, but
if you SYSADM person has not defined it to MVS, TSO or CMS etc... Your
connection will fail every time...

Make sure you password on MVS is not expired...

Check your DCS database catalog on the Gateway of the PC you configuring.
Make sure you Athentication is DCS also and the database is catalog
correctly.