Many years ago I stared using addresses in the range 700-7FF for virtual DASD on all may guests. I have never had real DASD in this range. That way when someone says something about a DASD at some address I know if they are talking about a real address or a virtual address. I also use the same addresses for any function on all guests. Thus every VSE spool is at 703 no matter witch VSE guest it is. Every Linux swap is at 751. It makes it easy to build new guests. You don't need to be concerned about DASD address when you copy a guest because they do not change.
[EMAIL PROTECTED] wrote:
I have a general administration / setup question for people who are running multiple Linux/390 systems under z/VM. Do all your Linux instances use the same virtual addresses for things like DASD, regardless of the actual device address? Or do you find it "better" to make the virtual DASD address match the actual device address? I'm tending towards making all Linux/390 instances use the same set of virtual DASD addresses, which are not even related to the "real" DASD addresses. I think this would be easier to maintain and "clone" new instances. Do you even try to make the Linux DASD addresses "look like" the actual device numbers, or do you simply have a range of virtual DASD addresses that you assign to physical devices. I'm using MDISK statements for Linux DASD. Basically, so far, I give each instance (OK, I only have one so far), the entire device OTHER THAN the first cylinder. Sorry, but I don't trust the Linux administrator to not destroy the DASD label, so this protects it from any mistakes. Oh, I'm the OS/390 and z/VM (new) sysprog. I am familar with Linux on Intel and did help the Linux administrator set up the initial Linux/390 system because she is not s390 literate. And I had actually done a SuSE s390 install at home under Hercules/390. So I was the "expert".
-- John McKown Senior Systems Programmer UICI Insurance Center Applications & Solutions Team +1.817.255.3225
This message (including any attachments) contains confidential information intended for a specific individual and purpose, and its' content is protected by law. If you are not the intended recipient, you should delete this message and are hereby notified that any disclosure, copying, or distribution of this transmission, or taking any action based on it, is strictly prohibited.
-- Stephen Frazier Information Technology Unit Oklahoma Department of Corrections 3400 Martin Luther King Oklahoma City, Ok, 73111-4298 Tel.: (405) 425-2549 Fax: (405) 425-2554 email: [EMAIL PROTECTED]
