Or use a VCTCA to connect RSCS machines or use a TCPNJE link between the machines and use SENDFILE. Since you can FTP between the machines, the TCPNJE link is a snap, and SENDFILE requires fewer keystrokes than FTP.
Another possibility would be to use a real CTCA between the machines and use a shared SFS. If that is not possible, then TSAF could be used to establish a link using a VCTCA so that SFS could be shared. If you have the VTAPE product from VSSI, you could use a shared VTAPE library to transport the files. You have lots of options. Richard Schuh P.S. I did not even include punching the file to the second-level's virtual reader - there is no sense carrying this too far. :-) -----Original Message----- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of Kris Buelens Sent: Friday, December 22, 2006 9:51 AM To: [email protected] Subject: Re: ftp VM to VM Why make it difficult? Using FTP also makes that the file timestanps get lost (they are set to the time of transmission), so yopu no longer can check what level of files you've got. Make lyour first level mchine LINK to the minidisks you want to get files of. So, for example in user LVL2VM CP LINK 19E 119E RR Then in a user loggoed on in the second level: ATTACH 119E * R/O ACCESS 119E Z COPYFILE * * Z = = x (OLDDATE Done When you get the CPHOST package from the VM download lib and install that on the secondlevelk system, you get a CP command to execute CP commands in the host VM system. I assign the name CP1 to it. Then you could even code a REXX EXEC to get tons of files from first level to secondlevel. Something like this (untested): /* */ address command call copy2lvl2 'MAINT 19E MAINT 219E' call copy2lvl2 'MAINT 191 MAINT 2191' ... COPY2LVL2: parse arg fuser fcuu suser tcuu 'CP CP1 LINK' fuser fcuu '001 RR' /* ask host CP to get this Mdisk */ 'CP ATT 001 * R/O' 'ACCESS 1 Z/Z' 'CP LINK' suser scuu '002 M' 'ACCESS 2 X' 'COPYFILE * * Z = = X(OLDD' 'CP DET 1 2' 'CP CP1 DET 1' return You would obviuosly add some checks for returncodes. Another solution I'm fond off: - send the seondlvel directory to your firstlevel system - shutdown the secondlevel system - attach the disks of the secondlevel systelm to SYSTEM on your firstlevel - use DEFINE MDISK to get access to the minidisks of the secondlevel system We've got two execs that make this even easier. I ask for example MDSK fname.MAINT 19E (Filel where 'fname' is the name of the DIRECT file of the secondlevel system. -The MDSK EXEC then finds the location of the indicated minidisk, -ATTACHes that volume to SYSTEM -DEFINEs the minidisk, ACCESS and FILELIST -DEATCHes everything again One can get these execs on request, we not only use them for secondlevel sytems, but also to get a peek at mindisks on our other VM systems (we've got 16 of them all on a z9). Kris, IBM Belgium, VM customer support
