Just a shot in the dark.  DB2 personal edition does it support a DB2 Connect
to DRDBA.  I seem to remember reading that to connect a PC to AS/400 DRDA
you had to use an upgraded version, don't remember the name but something
like DB2 enterprise edition.

Mike Jeu Devine
Insulectro
Programmer/Analyst
949-587-3356


                -----Original Message-----
                From:   Wayne Capwell [mailto:wayne@redoaktech.com]
                Sent:   Wednesday, July 21, 1999 1:12 PM
                To:     MIDRANGE-L@midrange.com
                Subject:        Re: DB2 Connect error

                Thank you, but...
                The DRDA clue seemed to help but I'm not home yet.
                The only host server not started is the IPX, which doesn't
suprise me
                since we have an NT network.

                I have re-configured the client as stated and got the signon
prompt,
                (though I did get that before).
                Now I receive the following error,
                _____________________________
                The connection test failed.

                [IBM][CLI Driver] SQL30020N  Execution failed because of a
Distributed
                Protocol Error that will affect the successful execution of
subsequent
                commands and SQL statements:  Reason Code "1254".
SQLSTATE=58009
                __________________________

                Of course the help text does not define the "Reason Code". 

                What else needs to be set up?

                Thanks in advance
                Wayne




                "R. Bruce Hoffman, Jr." wrote:
                > 
                > Sorry I couldn't look at this earlier, but...
                > 
                > Wayne Capwell wrote:
                > >
                > > Hello again,
                > > I tried this post on Friday and got no response.  Am I
the only one
                > > attempting to use DB2 Connect?  I'll try this again and
hope for some
                > > help.
                > 
                > No, you are not alone, but I am using DB2 UDB 5.2
Enterprise Developer
                > Edition. It comes with ALL of the parts.
                > 
                > >
                > > I am attempting to connect a Win95 workstation to our
AS/400 running
                > > V4R2 using IBM's DB2 Connect Personnel Edition over
TCP/IP.  I can ping
                > > the AS/400 and have network access to the AS/400 from
other Win95 PC's
                > > on the same network using Client Access.  I get the
following error
                > > message when I try to search of a database on the
AS/400.
                > 
                > Don't search. Configure the connection. First, are you
using the control
                > center to set this up? If so, under systems, add the
AS/400 name and
                > select OS/400 as the operating system. An instance folder
appears. Add a
                > new instance name, remote instance should specify the 400
RDB name (that
                > is the name you give to the *LOCAL in the WRKRDBDIRE
command on the 400,
                > should be a re-req) and the protocol is TCP/IP.
                > 
                > Now the important step. For the host name, specify the IP
address or use
                > a hosts file. If you are using a DNS, *verify* the name to
the address.
                > In the service name, put 446. This is the DRDA port on the
400 that is
                > listening for connections.
                > 
                > Database folder appears, add a new database. Put in the
database name
                > that (again) is the same as the *LOCAL in the WRKRDBDIRE
command.
                > 
                > Now you should be able to right click on the database and
select connect
                > from the pop up menu. User profile and password.  ta-da.
                > 
                > > _________________________________________________
                > > The connection test failed.
                > >
                > > [IBM][CLI Driver] 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:
"gethostbyname".  Protocol
                > > specific error code(s): "*", "11002", "*".
SQLSTATE=08001
                > > ____________________________________________________
                > >
                > 
                > This message is basically telling you that it can not find
an IP address
                > for the name of the machine that you entered. If you
specify the IP
                > address instead of the name, this message should go away.
                > 
                > Also, I have not connected to an AS/400 that *didn't* have
the IP
                > address of itself in the hosts file on itself with it's
own name
                > attached. This entry will not hurt anything, just make
sure that the
                > hosts file on the AS/400 contains itself and it's IP
address.
                > 
                > Lastly, double check the drda service port. Use WRKTCPSTS
option 3 and
                > look for the drda service port to be in listen status. If
you then look
                > at the port number (F14) you should see the 446.
                > 
                > If this is not running, make sure that the STRTCPSVR *DDM
and STRHOSTSVR
                > *ALL commands have been run and look for it again. In V4R2
the start of
                > the host servers happens automatically.
                > 
                > Good luck.
                > --
                >
===========================================================
                > R. Bruce Hoffman, Jr.
                >  -- IBM Certified AS/400 Professional System Administrator
                >  -- IBM Certified AS/400 Professional Network
Administrator
                > 
                > "The sum of all human knowledge is a fixed constant.
                >     It's the population that keeps growing!"
                > +---
                > | This is the Midrange System Mailing List!
                > | To submit a new message, send your mail to
MIDRANGE-L@midrange.com.
                > | To subscribe to this list send email to
MIDRANGE-L-SUB@midrange.com.
                > | To unsubscribe from this list send email to
MIDRANGE-L-UNSUB@midrange.com.
                > | Questions should be directed to the list owner/operator:
david@midrange.com
                > +---

                -- 
                ______________________________________
                Wayne W. Capwell
                Red Oak Technologies, Inc.
                11301 Carmel Commons Blvd., Suite 114   
                Charlotte, NC  28226
                704-945-1067

                Manufacturing...Production...Solutions
                     http://www.redoaktech.com/
                +---
                | This is the Midrange System Mailing List!
                | To submit a new message, send your mail to
MIDRANGE-L@midrange.com.
                | To subscribe to this list send email to
MIDRANGE-L-SUB@midrange.com.
                | To unsubscribe from this list send email to
MIDRANGE-L-UNSUB@midrange.com.
                | Questions should be directed to the list owner/operator:
david@midrange.com
                +---

+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---


This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2019 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].