>> Currently all of my linux guests IPL CMS to create VDISK swap disks and >> signatures. For a linux to work with LGR it must IPL from a device or NSS so >> no CMS if I want to LGR. I've been doing it this way for so long I'm unsure >> of >> how I would create the swap signature in my VDISKs without IPLing CMS >> first. >> >> Suggestions would greatly be appreciated.
>IPL 190. While not optimal for memory usage, it circumvents most of the >problem. IPL 190 solves nothing. Whether you IPL from 190 or the CMS NSS is irrelevant. To use LGR, you can't have any links to non-shared disks. As Alan Altmark pointed out, your choices are to create a set of shared CMS disks or to detach the disks before IPLing Linux. If you create a shared CMS, you get to design a maintenance process for it. SERVICE and PUT2PROD will update the non-shared CMS. You either need to create PPF overrides, make MAINT 19x shared, or copy from the non-shared disks to a shared set. You also need to make sure that the segments are the same on all nodes. If I were to choose this approach, I would leave IBM's maintenance process alone, and copy from the non-shared disks to the shared disks every time I applied maintenance. I would then resave the shared CMS (call it SHARECMS) on each node. I'm not sure whether creating overrides or making the MAINT disks shared would work very well. You might have problems if you PUT2PROD from multiple members onto the same disks, because it wasn't intended to work that way. I didn't want to add steps to the maintenance process, so I chose to detach the MAINT 19x disks instead. Dennis O'Brien There are three kinds of people, those who can count and those who can't. ---------------------------------------------------------------------- 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. ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 ---------------------------------------------------------------------- For more information on Linux on System z, visit http://wiki.linuxvm.org/
