Kris, I actualy use the spool method in the very real present if I have to transfer a handful of small files - simply because I think the method is less error prone.
I use the minidisk method for large transfers. And then, before copying from the 1st level I make sure I do DEFINE MDISK on the basis of an _up to date_ info, whichever way I get that info. If I am on the 2nd level, I make sure that I _RELEASE/DETACH_ any 1st level minidisks that I linked to avoid unintentionally using backlevel or wrong-level files later on. Using spool is at least three times slower (punch, read to 2nd level spool, read to disk), but you have less to worry about. You can surely use RDEVICE if you are not eager enough to find out wether that SYSTEM CONFIG change actually worked. :-) Cheers, Ivica Brodaric Tabcorp, Australia -----Original Message----- From: VM/ESA and z/VM Discussions [mailto:[EMAIL PROTECTED] On Behalf Of Kris Buelens Sent: Saturday, 10 December 2005 2:46 AM To: [email protected] Subject: Re: 2nd-Level VM Install Question - Side question The technique below does indeed work, I used it too in ancient history. But, given that VM no longer needs an assembled, rigid, HCPRIO, you can access each and every minidisk of your first level system in your secondlevel (as Alan already pointed out). - Often secondlevel users have their secondlevel console on the same 3270 session as the first level VM. So, a PA1 brings you to first level where you can enter #CP LINK lvl1user vdev vdev2 RR - Otherwise, on a firstlevel user issue CP SEND CP LVL2VM LINK lvl1user vdev vdev2 RR - And, if you plan to use secondlevel system regulary, get the CP1STLVL package from the download lib and every authorised user on the secondlevel system can issue commands like CP1ST LINK lvl1user vdev vdev2 RR Once you have the LINK, an ATTACH vdev2 xxxx vdev3 R/O and an ACCESS is all you need. To work the other way around: I use DEFINE MDISK indeed, but, with an EXEC that gets the MDISK addresses directly from a CMS file that contains the secondlevel directory. This exec also takes care of ATTACH to SYSTEM of the dasd hosting the minidisk, at the end the dasd is DETACHED again. And, a last remark: in the pedestrian method below, it is suggested to re-IPL. No need for that, everything can be done dynamically. Simply issue SET RDEVICE 000C TYPE READER etc. Updatin the SYSTEM CONFIG file makes that you don't need to repeat the SET REDVICE comman(s) after each IPL. Kris, IBM Belgium, VM customer support *********************************************************************************** The information in this e-mail message and any files transmitted with it are intended to be confidential and for the use of only the individual or entity to whom they are addressed. The message and files may be protected by legal professional privilege, or other legal rules. The confidentiality of and privilege applying to this message and files is not waived if this message or files has been sent to you by mistake. If the reader of this message or files is not the intended recipient, you are notified that retention, distribution or copying of this message and files are strictly prohibited. If you receive this message or files in error, please notify us immediately by telephone or return e-mail and delete all copies from your computer system. It is the recipient's responsibility to check this message and files for viruses. Thank you. ***********************************************************************************
