is it possible to connect to db2/390 without having db2 connect?

[aka]

Hi

I have a DB2 v8.1 on AIX and DB2 Connect EE on Solaris wich is connected to
OS/390 DB2 subsystems via APPC / SNA. I have cataloged the DB2 Connect
instance as tcpip node and then the Host DB cataloged on that node...this
works from v7.2 Fixpack 11 clients and servers, but with v8.1 server I get
SQL1334N.
Does anyone has an idea?

Thanks
aka

[Blair Adamache]

SNA / APPC support is extremely limited inb Version 8.

Recommendations :

1. drop SNA and try TCP/IP only
or
2. upgrade to the latest fixpak of DB2 v8, and try CPIC support (v8
equivalent of APPC / SNA)

aka wrote:

Hi

I have a DB2 v8.1 on AIX and DB2 Connect EE on Solaris wich is connected to
OS/390 DB2 subsystems via APPC / SNA. I have cataloged the DB2 Connect
instance as tcpip node and then the Host DB cataloged on that node...this
works from v7.2 Fixpack 11 clients and servers, but with v8.1 server I get
SQL1334N.
Does anyone has an idea?

Thanks
aka

[Blair Adamache]

SNA / APPC support is extremely limited inb Version 8.

Recommendations :

1. drop SNA and try TCP/IP only
or
2. upgrade to the latest fixpak of DB2 v8, and try CPIC support (v8
equivalent of APPC / SNA)

aka wrote:

Hi

I have a DB2 v8.1 on AIX and DB2 Connect EE on Solaris wich is connected to
OS/390 DB2 subsystems via APPC / SNA. I have cataloged the DB2 Connect
instance as tcpip node and then the Host DB cataloged on that node...this
works from v7.2 Fixpack 11 clients and servers, but with v8.1 server I get
SQL1334N.
Does anyone has an idea?

Thanks
aka

[Sundeep Narravula]

Hi,

I am trying to setup DB2 in a multi-partition setup. But due to some
local configuration problems, We are not in a position to use an NFS.

Is there some way to install the multi-partition setup without having to
use the NFS?

--Sundeep Narravula.

[Sundeep Narravula]

Hi,

I am trying to setup DB2 in a multi-partition setup. But due to some
local configuration problems, We are not in a position to use an NFS.

Is there some way to install the multi-partition setup without having to
use the NFS?

--Sundeep Narravula.

[aka]

Hi Blair,

thanks for your answer...I'm DBA in a big health isurance company and it
takes me about a week or so to get a new fixpack or db2 instance
installed...
we have DB2/390 v6.1.2 on MVS Host
DB2/SUN v7.2.9 on SunFire Cluster, there is also DB2 Connect EE and SNA is
installed
and we use Solaris and AIX as DB2 Servers from v6.1 to v7.2.9 and also EEE
v7.2.9 on 8 AIX SP2 nodes for data warehouse...
now I have my first v8.1 FP 5 instance on AIX maschine and try to get a
connection to the Host System...

you say SNA/APPC support is limited, so i will first try to get the setup
for v8.1 FP5 on the connect instance
it will then be a second task to follow your tip to exchange APPC with
CPIC...I will let you know

in the above configuration we make connections to MVS host via Solaris
gateway (with DB2 connect EE) and I don't know how long it takes to upgrade
the host system with tcp/ip

in the meantime I read the manuals and wonder about the SQL1334N message I
get, when I try to connect in the same environment to host from v8.1

I thougt I need a DB2 Connect as gateway to access Host DB2 but from the SQL
message it is said that DRDA databases can only connect directly, so another
question is: can I connect to Host system without using the connect gateway?
Thanks
aka

SNA / APPC support is extremely limited inb Version 8.

Recommendations :

1. drop SNA and try TCP/IP only
or
2. upgrade to the latest fixpak of DB2 v8, and try CPIC support (v8
equivalent of APPC / SNA)

[aka]

Hi Blair,

thanks for your answer...I'm DBA in a big health isurance company and it
takes me about a week or so to get a new fixpack or db2 instance
installed...
we have DB2/390 v6.1.2 on MVS Host
DB2/SUN v7.2.9 on SunFire Cluster, there is also DB2 Connect EE and SNA is
installed
and we use Solaris and AIX as DB2 Servers from v6.1 to v7.2.9 and also EEE
v7.2.9 on 8 AIX SP2 nodes for data warehouse...
now I have my first v8.1 FP 5 instance on AIX maschine and try to get a
connection to the Host System...

you say SNA/APPC support is limited, so i will first try to get the setup
for v8.1 FP5 on the connect instance
it will then be a second task to follow your tip to exchange APPC with
CPIC...I will let you know

in the above configuration we make connections to MVS host via Solaris
gateway (with DB2 connect EE) and I don't know how long it takes to upgrade
the host system with tcp/ip

in the meantime I read the manuals and wonder about the SQL1334N message I
get, when I try to connect in the same environment to host from v8.1

I thougt I need a DB2 Connect as gateway to access Host DB2 but from the SQL
message it is said that DRDA databases can only connect directly, so another
question is: can I connect to Host system without using the connect gateway?
Thanks
aka

SNA / APPC support is extremely limited inb Version 8.

Recommendations :

1. drop SNA and try TCP/IP only
or
2. upgrade to the latest fixpak of DB2 v8, and try CPIC support (v8
equivalent of APPC / SNA)

[Larry]

I think the explanation for error msg SQL1334N isn't exactly clear, but
take my word for it, if you want to connect to a DB2 V6 database on
OS/390 ... you need either a DRDA gateway (DB2 COnnect EE), a DRDA
client (DB2 Connect Personal Edition), or the new type 4 JDBC driver in
DB2 Connect V8 (which will allow direct connections from a type 4 JDBC
client, but still requires a DB2 Connect license) ... and I'm not
entirely sure whether the type 4 JDBC driver in V8 will support either
DB2/390 V6 or SNA.

The description of your environment is not exactly clear to me. Where do
you receive this error msg? On the client? Gateway Server? What exactly
is the client configuration, and the gateway server configuration?

My advice is get off SNA asap.

Larry Edelstein

aka wrote:

Hi Blair,

thanks for your answer...I'm DBA in a big health isurance company and it
takes me about a week or so to get a new fixpack or db2 instance
installed...
we have DB2/390 v6.1.2 on MVS Host
DB2/SUN v7.2.9 on SunFire Cluster, there is also DB2 Connect EE and SNA is
installed
and we use Solaris and AIX as DB2 Servers from v6.1 to v7.2.9 and also EEE
v7.2.9 on 8 AIX SP2 nodes for data warehouse...
now I have my first v8.1 FP 5 instance on AIX maschine and try to get a
connection to the Host System...

you say SNA/APPC support is limited, so i will first try to get the setup
for v8.1 FP5 on the connect instance
it will then be a second task to follow your tip to exchange APPC with
CPIC...I will let you know

in the above configuration we make connections to MVS host via Solaris
gateway (with DB2 connect EE) and I don't know how long it takes to upgrade
the host system with tcp/ip

in the meantime I read the manuals and wonder about the SQL1334N message I
get, when I try to connect in the same environment to host from v8.1

I thougt I need a DB2 Connect as gateway to access Host DB2 but from the SQL
message it is said that DRDA databases can only connect directly, so another
question is: can I connect to Host system without using the connect gateway?
Thanks
aka

SNA / APPC support is extremely limited inb Version 8.

Recommendatio ns:

1. drop SNA and try TCP/IP only
or
2. upgrade to the latest fixpak of DB2 v8, and try CPIC support (v8
equivalent of APPC / SNA)

[Larry]

I think the explanation for error msg SQL1334N isn't exactly clear, but
take my word for it, if you want to connect to a DB2 V6 database on
OS/390 ... you need either a DRDA gateway (DB2 COnnect EE), a DRDA
client (DB2 Connect Personal Edition), or the new type 4 JDBC driver in
DB2 Connect V8 (which will allow direct connections from a type 4 JDBC
client, but still requires a DB2 Connect license) ... and I'm not
entirely sure whether the type 4 JDBC driver in V8 will support either
DB2/390 V6 or SNA.

The description of your environment is not exactly clear to me. Where do
you receive this error msg? On the client? Gateway Server? What exactly
is the client configuration, and the gateway server configuration?

My advice is get off SNA asap.

Larry Edelstein

aka wrote:

Hi Blair,

thanks for your answer...I'm DBA in a big health isurance company and it
takes me about a week or so to get a new fixpack or db2 instance
installed...
we have DB2/390 v6.1.2 on MVS Host
DB2/SUN v7.2.9 on SunFire Cluster, there is also DB2 Connect EE and SNA is
installed
and we use Solaris and AIX as DB2 Servers from v6.1 to v7.2.9 and also EEE
v7.2.9 on 8 AIX SP2 nodes for data warehouse...
now I have my first v8.1 FP 5 instance on AIX maschine and try to get a
connection to the Host System...

you say SNA/APPC support is limited, so i will first try to get the setup
for v8.1 FP5 on the connect instance
it will then be a second task to follow your tip to exchange APPC with
CPIC...I will let you know

in the above configuration we make connections to MVS host via Solaris
gateway (with DB2 connect EE) and I don't know how long it takes to upgrade
the host system with tcp/ip

in the meantime I read the manuals and wonder about the SQL1334N message I
get, when I try to connect in the same environment to host from v8.1

I thougt I need a DB2 Connect as gateway to access Host DB2 but from the SQL
message it is said that DRDA databases can only connect directly, so another
question is: can I connect to Host system without using the connect gateway?
Thanks
aka

SNA / APPC support is extremely limited inb Version 8.

Recommendatio ns:

1. drop SNA and try TCP/IP only
or
2. upgrade to the latest fixpak of DB2 v8, and try CPIC support (v8
equivalent of APPC / SNA)

[aka]

Larry thank you for answering

I think the explanation for error msg SQL1334N isn't exactly clear, but
take my word for it, if you want to connect to a DB2 V6 database on
OS/390 ... you need either a DRDA gateway (DB2 COnnect EE), a DRDA
client (DB2 Connect Personal Edition), or the new type 4 JDBC driver in
DB2 Connect V8 (which will allow direct connections from a type 4 JDBC
client, but still requires a DB2 Connect license) ... and I'm not
entirely sure whether the type 4 JDBC driver in V8 will support either
DB2/390 V6 or SNA.
yes that's my option also. I have a piece of java code to test the type 4
connect:

/*+----------------------------------+*/
/*! initialize JDBC/ODBC environment !*/
/*+----------------------------------+*/
try
{
// choose driver...
if (in_host_name.l ength() > 0 && in_port_number. length() > 0)
{ // use NET driver
db2_class = "COM.ibm.db2.jd bc.net.DB2Drive r";
db2_url = "jdbc:db2://" + in_host_name + ":" + in_port_number + "/"
+ in_source_db_na me;
}
else
{ // use APPlication driver
db2_class = "COM.ibm.db2.jd bc.app.DB2Drive r";
db2_url = "jdbc:db2:" + in_source_db_na me;
}
Driver myDBDriver = (Driver)Class.f orName (db2_class).new Instance();

// get db connection
System.out.prin tln ("DB2_Class= " + db2_class);
System.out.prin tln ("Connect_UR L=" + db2_url);
if (in_usr_name.eq uals("")) db_conn = DriverManager.g etConnection
(db2_url, "", "");
else db_conn = DriverManager.g etConnection (db2_url, in_usr_name,
in_usr_pw);
The description of your environment is not exactly clear to me. Where do
you receive this error msg? On the client? Gateway Server? What exactly
is the client configuration, and the gateway server configuration?
The sql message is kind of misleading, eh? Ok I try to describe the
environment more exactly...

(I) Host with MVS and DB2 v6.1.2
Subsystem called DB2T
I call this a server

(II) Solaris machine with DB2 Connect EE v7.2.9
Instance: GWMVS
Host DB cataloged at APPN node as DB2T
I call this gateway

(III) AIX machines with DB2 EEE v7.2.9
Instance: DB2TEST
cataloged GWMVS as TCPIP node
cataloged Host DB at TCPIP node GWMVS as DB2T
this is DB2 server but acts as client against host DB2

In this environment the connection to DB2T from machine (III), instance
DB2TEST works just fine. Now I got another instance V8TEST installed on
machine (III) with DB2 v8.1.5. With the same cataloging I get SQL1334N when
connecting to DB2T. I thought that DB2 v8 already has DRDA included, so the
only thing that is missing would be perhaps SNA...or that the gateway isn't
needed anymore when the host gets TCP/IP? This is primarily not a question
of licenses.
My advice is get off SNA asap.
yep. I told that since two years or so...
Larry Edelstein

Regards
aka