Use LXFMT from z/VM, no need to reformat the disk under Linux. Mike Walter Hewitt Associates The opinions expressed herein are mine alone, not my employer's.
>From an earlier post: Date: Mon, 28 Jan 2008 15:50:31 -0500 Reply-To: [email protected] Sender: The IBM z/VM Operating System <[email protected]> From: Rick Bourgeois <[email protected]> Organization: VSSI Subject: Free CMS utilities for Linux and Tape Comments: To: Linux on 390 Port <[email protected]> Content-Type: text/plain; charset="us-ascii" Hi all, We have just made available on our website www.vsoftsys.com three free CMS utilities. LXFMT V2.1: LXFMT is a CMS utility that provides the functions of both the DASDFMT and FDASD Linux utilities. LXFMT can be used for ECKD and FBA devices. TBROWSE: TBROWSE is a CMS utility that allows you scan a real or virtual tape in a full screen browse like format. TAPSENSE: TAPSENSE displays sense information for an attached real or defined virtual tape drive. Using the current CSL-WAVV comments on the Linux-390 list of give to get I have included the following as general information. Please feel free to ignore it as we had planned to make these utilities available anyway. An earlier version of our LXFMT utility was made available on the Sinenomine.net website last year. While at our website feel free to browse information on our VM virtualization products VTAPE (Virtual TAPE) and VPARS (Virtual Private Active Record Shadowing for TPF and Linux). I will be presenting technical information on both VPARS and VTAPE at SHARE in Orlando, Session 9155 Tuesday 2/26 at 8am and a Vendor Session Wednesday 2/27 at 4:30pm in Laredo 1. We will also be available at booth 322 at the SHARE Technology Expo with demos, I hope (if all the internet stuff works to get to our mainframe ;-). Our FLEX-ES laptop expired 2/2007 making us dependant on the internet for demos ;-(. We will also be at WAVV in Chattanooga in April. Having been a member of SHARE since the early 1970's but not attending in several years I look forward to renewing many old friendships, making new ones and thanking the VM Group members for my Knighthood at the last SHARE. Thanks and best regards, Sir Rick of PARS Rick Bourgeois [email protected] Virtual Software Systems, Inc. www.vsoftsys.com 770-781-3200 "Martin, Terry R. (CMS/CTR) (CTR)" <[email protected]> Sent by: "The IBM z/VM Operating System" <[email protected]> 03/24/2010 12:53 PM Please respond to "The IBM z/VM Operating System" <[email protected]> To [email protected] cc Subject initializing z/Linux disks 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 The information contained in this e-mail and any accompanying documents may contain information that is confidential or otherwise protected from disclosure. If you are not the intended recipient of this message, or if this message has been addressed to you in error, please immediately alert the sender by reply e-mail and then delete this message, including any attachments. Any dissemination, distribution or other use of the contents of this message by anyone other than the intended recipient is strictly prohibited. All messages sent to and from this e-mail address may be monitored as permitted by applicable law and regulations to ensure compliance with our internal policies and to protect our business. E-mails are not secure and cannot be guaranteed to be error free as they can be intercepted, amended, lost or destroyed, or contain viruses. You are deemed to have accepted these risks if you communicate with us by e-mail.
