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 > Another (pedestrian) way of sending file(s) from a first level VM to the > second and back is by using the spool. Although limited because of the > initial size of the spool, this is handy in the initial stages of the > installation while you still don't have any other products installed on > the 2nd level. Also useful if you don't want to think where your > minidisks are :-) > 1. Make sure you have a virtual reader and punch defined in a 1st > level's userid for the 2nd level VM (e.g. SPOOL 000C 3505 X and SPOOL > 000D 3525 X). Those will be 2nd level's "real" reader and punch. > 2. Add the following in the SYSTEM CONFIG on the 2nd level VM and then > re-IPL 2nd level: > Rdevice 000C Type Reader Class X > Rdevice 000D Type Punch Classes X > 3. On the 2nd level's user with privilege class D enter the following to > start the real reader and punch (this step may have to be repeated after > the first file comes in/out): > cp sta c > cp sta d > 4. Now you can use DISK DUMP command and RECEIVE to send the files both > ways.
