Jeff, The class B requirement is there because the instructions tell you to ATTACH the DASD to the installation guest. Obviously, if you put the DASD in the directory, you don't need to issue an ATTACH command.
Dennis O'Brien "If man does find the solution for world peace it will be the most revolutionary reversal of his record we have ever known." -- General George C. Marshall From: The IBM z/VM Operating System [mailto:IBMVM@LISTSERV.UARK.EDU] On Behalf Of Jeff Gribbin Sent: Saturday, June 11, 2011 11:20 To: IBMVM@LISTSERV.UARK.EDU Subject: Re: [IBMVM] z/VM 5.4 FTP Installation ... ? ... Just to round this off ... Installation completed successfully, exactly as per the manual. I now have a base-level system installed from an FTP server and upon which I shall soon install an up-to-date RSU. Note that 2nd-level userid used for installation is a Class G userid with no privs - I shall be raising RCF querying why manual says that Privclass B and DEFINE MDISK (if one is changing labels) are required. Onwards and upwards - thanks to Alan and Malcolm for their input! Jeff ---------------------------------------------------------------------- This message w/attachments (message) is intended solely for the use of the intended recipient(s) and may contain information that is privileged, confidential or proprietary. If you are not an intended recipient, please notify the sender, and then please delete and destroy all copies and attachments, and be advised that any review or dissemination of, or the taking of any action in reliance on, the information contained in or attached to this message is prohibited. Unless specifically indicated, this message is not an offer to sell or a solicitation of any investment products or other financial product or service, an official confirmation of any transaction, or an official statement of Sender. Subject to applicable law, Sender may intercept, monitor, review and retain e-communications (EC) traveling through its networks/systems and may produce any such EC to regulators, law enforcement, in litigation and as required by law. The laws of the country of each sender/recipient may impact the handling of EC, and EC may be archived, supervised and produced in countries other than the country in which you are located. This message cannot be guaranteed to be secure or free of errors or viruses. References to "Sender" are references to any subsidiary of Bank of America Corporation. Securities and Insurance Products: * Are Not FDIC Insured * Are Not Bank Guaranteed * May Lose Value * Are Not a Bank Deposit * Are Not a Condition to Any Banking Service or Activity * Are Not Insured by Any Federal Government Agency. Attachments that are part of this EC may have additional important disclosures and disclaimers, which you should read. This message is subject to terms available at the following link: http://www.bankofamerica.com/emaildisclaimer. By messaging with Sender you consent to the foregoing.