> Would IPGATE be an option? I did try to get it running on 
> some other systems. I could see a resource in the remote VM 
> but I was not successfull in accessing it. If someone would 
> have an example config for this I'd be very happy.

For IPGATE to work for this purpose, you need to do the following: 

1) Make sure that you can reach each of the systems via TCPIP. Use the
fastest IP pipe you can find between the systems -- SFS generates a enormous
amount of traffic. 

2) Set up a IPGATE virtual machine on each system. 

3) Customize IPGATE RESOURCE to look something like this:

*resource target   scope    target port and address
*2345678  12345678 12345678 1234 123......
* following line is for FCONX remote access AKA Perfkit
FCXRES0B  FCXRES0A SYSTEM   4567 aaa.bbb.ccc.ddd
* SFS file pool running on remote system 1 at IP address xx.yy.zz.aa
* 1st arg is resource name, 2nd arg is filepool name globally visible
SNA1POOL  SNA1     SYSTEM   4567 xxx.yyy.zzz.aaa
* Another pool to be visible elsewhere 
VSFSPOOL  SFSPOOL2 SYSTEM   4567 ddd.eee.fff.ggg
*

Substitute your resource names, pool names and IP addresses appropriately. 

4) Customize IPGATE USERMAP to look something like this (note, we coordinate
userids on all systems, so this may not be appropriate for your setup):

;origin_system  origuser resource locuser
;23456789012345 12345678 12345678 12345678
Aaa.bbb.ccc.ddd *        *        =
Xxx.yyy.zzz.aaa *        *        =
Ddd.eee.fff.ggg *        *        =
*               *        *        not_auth

Again, substitute your IP addresses appropriately. 

5) Start IPGATE on each system.  After a few minutes, QUERY RESOURCE should
show the resouces from the other systems.

You should see something like this in the Q RESOURCE output:

Resource: SNA1POOL  Type: System  Owning Userid: IPGATE
Resource: VSFSPOOL  Type: System  Owning Userid: IPGATE

At that point, assuming that your userid is authorized in the remote
filepools, you should be able to access SFS files over the IP connection. 

All the CRR requirements and remote authorization stuff like that still
apply, but you're free of the CTC requirement. 
If you have a really fast network connection (a real hipersocket screams for
this application), this works well. If you can,  support the largest frame
size and MTU size you can configure that won't result in fragmentation of
packets in transit. 

Works like a charm for us. 

-- db

Reply via email to