Hi
I have a question. What I have been doing up to this point for a new z/Linux guest build is, not necessarily in this order and does not necessarily include all steps but, Crave out the DASD for the z/Linux guest Init the DASD using CPFMTXA putting a label on the disk Setting up the Directory entry for the new guest, which includes specifying the MDISK for all of the DASD for the guest. We back up our z/Linux guests on the z/OS side with DFDSS. My question is since when we Kick Start the new z/Linux guest and it initializes the DASD during this process is there any compelling reason for me to initialize the DASD up front before the guest is Kick Started for the first time basically doing a double INIT? If not I assume then I would replace the MDISK statements in the Directory entry with DEDICATE statements for each one of the DISKS. We do not share DASD between guests here so what is defined to the guest belongs to that guest only. Is there anything to be aware of by changing to DEDICATE statements from MDISK statements? My only concern is with the DFDSS backups that I do on the z/OS for the guests. I am not sure if it matters or not to DFDSS whether the pack was initialized via CPFMTXA or z/Linux during the kick start process? Thank You, Terry Martin Lockheed Martin - Citic z/OS and z/VM Performance Tuning and Operating Systems Support Office - 443 348-2102 Cell - 443 632-4191
