I will assume for the purpose of answering your question that you are sure
that the DB2 subsystem (on OS/390) is TCP/IP-enabled. There is some
"magic" that the systems programs have to work to accomplish this.
They usually register the two ports for the DB2 subsystem to
prevent others from using those ports for other subsystems.
You will need to know the TCP/IP number for the LPAR, in either number
format (172.99.99.99 etc) or the DNS name, i.e. prod1.customs.gov.au. If
your systems programmers were really kind, then they will have set up a
DB2 subsystems-specific name in DNS so that your DB2 subsystems is
not tied to a particular LPAR. This will help you out if they ever move the
DB2 subsystem from one LPAR to another one. The name might look like
db2z.customs.gov.au.
If you do know not the TCP/IP number or DNS name for where your DB2
is running there is a sneaky way to find it. Go into the running task for the
SSAS address space (DSNMSTR), which there will be for each DB2 subsystem.
Once in here, go to the log dataset and do a find for 'TCP'. Once you find this
section, you will see the TCP/IP number (and I believe DNS name for the
LPAR), as well as the port that DB2 is using to communicate. Choose the
port that is NOT the resync port.
If you already know the LPAR's TCP/IP number or name, the fast way to
find the port is by typing 'tso netstat' at the ISPF command line or typing
'netstat' at ISPF option 6. You MUST be logged on the LPAR where the
DB2 subsystem exists to get the correct information. Netstat will give you a
list of all the ports that are listening on that LPAR. You should be able to
find your DB2 port pretty easily this way; just pick the port that is NOT
the resync port. I can't remember the description for the correct port and
I'm not logged onto OS/390 right now.
I'm assuming from your question that you know the secrets of getting the CCA
to connect to and OS/390 DB2 once you have the IP and port. In case, you
don't know the host it is looking for is the IP number or DNS name that I
mentioned above. Under Version 6.1 of the client, I had problems when I tried
to set up communication to an OS/390 DB2 when I had the "register for
ODBC" box checked. Under Version 7.1 I haven't had that problem.
[EMAIL PROTECTED] wrote:
> DB 7.1 NT -> DB2v5 os390
>
> Ok basic question time. I've tried to find out via the quick beginnings,
> the list archives and book mangler but I think I need a pointer in
> the right direction.
>
> If I want to a) 'See' my db2 os390 catalog and b)'See' data
> in databases from the workstation how
> do I know what port number to use? I have the ip address but
> cannot find a port number. I should point out that the m/f
> is very vanilla at the moment and it is quite possible that I
> need to do work on that end too. Do I need to get DDF up and
> running to do this or is there some magic via tcp/ip which lets
> me see things. I have been using the CCA but I suspect I need
> to do more on the m/f end first.
>
> Perhaps I should be more basic and not assume that I am going
> in the right direction and simply ask...What are the basic steps
> I need to perform at each end to achieve the link between the two?
> An RTFM message telling me the manual/chapter would be fine.
>
> TIA
>
> Steve T
>
> =====
> To unsubscribe, send 'unsubscribe' to [EMAIL PROTECTED]
> For other info (and scripts), see http://people.mn.mediaone.net/scottrmcleod
=====
To unsubscribe, send 'unsubscribe' to [EMAIL PROTECTED]
For other info (and scripts), see http://people.mn.mediaone.net/scottrmcleod
