| View previous topic :: View next topic |
| Author |
Message |
vmbigot
Beginner
Joined: 17 Jun 2004
Posts: 36
Topics: 14
Location: westminster, california
|
 Posted: Tue Jan 03, 2006 5:09 pm Post subject: db2 subsystem access from two seperate IP networks |
 |
|
We have a test version 8 DB2 subsystem running on z/OS 1.4 using port number(s) 5100/5101 on our production LAN. Our production LAN is connected to an OSA adapter defined as IP address 172.16.1.170. Another OSA adapter is defined as 172.16.1.171 in the same TCP/IP stack and is connected to our test LAN. For security purposes our two LANs cannot be connected except through the common IP stack on the mainframe. Is there a way for clients on the test LAN to be able to access the test DB2 subsystem connected to the production LAN? Any help would be appreciated!
Thanks,
vmbigot
_________________
Inside every older man is a young boy asking this question. What the heck happened?!? |
|
| Back to top |
|
 |
kolusu
Site Admin
Joined: 26 Nov 2002
Posts: 12376
Topics: 75
Location: San Jose
|
|
| Back to top |
|
|
vmbigot
Beginner
Joined: 17 Jun 2004
Posts: 36
Topics: 14
Location: westminster, california
|
| Posted: Thu Jan 05, 2006 2:00 pm Post subject: |
|
|
Thanks Kolusu.
I checked out the link you supplied and found some good stuff in it that I can use later. However, it explains how to make tables in one susbsystem available to another subsystem, but not how to make one or more tables in one DB2 subsystem to be available to multiple but completely seperate LANs and clients. As much as I hate to do it, I'm going to crack open the manuals. 
I am also starting to think that this might be more of a TCPIP issue than a DB2 one.
Thanks,
vmbigot
_________________
Inside every older man is a young boy asking this question. What the heck happened?!? |
|
| Back to top |
|
|
|
|
|
FAQ
Search
Quick Manuals
Register
Profile
Log in to check your private messages
Log in
