ISFC is a CP feature that allows APPC and IUCV traffic to flow from one VM into another. You need a CTC as Shimon said. But, once you have such an ISFC link, the SFSes available on one VM system are visible in the other coupled systems, on condition that A. your SFS is not named VMSYSxxx B. you add REMOTE in the SFS' DMSPARMS file
Note too that the "Global" APPC resources (that you can see with CP Q RESOURCE, "type Global") need to have a unique name in the ISFC collection. Otherwise, the APPC server that starts first is the one everyone will connect to. A remote SFS setup like this works perfectly well and is very fast (much better than is using a SNA connection over AVS). An alternative to make SFSes remotely available without AVS, nor CTC, but based on TCP/IP is installing IPGATE (from VM's download library). Works great too and fast too. To have a guest VM grab files from a host VM (or the other way around), there are multiple methods too that don't involve a SENDFILE. But, in these cases, much care must be taken: A. use CPHOST, and have the guest VM LINK to a minidisk of the host VM followed by an ATTACH in the guest. B. use DEFINE MDISK in the guest VM to define an overlay on a minidisk on a disk. BEWARE: DEFINE MDISK yields a R/W minidisk, be sure the use "ACCESS vdev fm/fm" so avoid CMS writing to it. We have some execs that use this technique in a relatively safe way. 2007/5/4, James M <[EMAIL PROTECTED]>:
q 741 CTCA 0741 ATTACHED TO RSCS 0741 Not sure what ISFC is. I'll have to check it out. But does it work with minidisks and spool files? Thanks again! -James
-- Kris Buelens, IBM Belgium, VM customer support
