开云体育

A VM sysprog friend of mine uses this method: he copied his VM disks from track 0 to another disk starting at track 1 using DDR. Then he defines this as a minidisk to his guest VM system starting from

Hi Bob, I was just trying to explain the concept. I was not recommending any configuration with duplicate volsers. It's too easy to confuse things. With Hercules, you can have separate test and

Fish and Bob (Bolch), Nothing that you wrote was incorrect, and nothing that I wrote in the original post was incorrect either.? I didn't say that one could not use a copy of the same dasds for

I did this exercise a couple years ago, and I used John Yagers zzsa disk editor utility to change the volser on a copy of VmR6. You can get zzssa from the CBT tape site Mike

Bob Bolch wrote: Exactly! Precisely! Thank you for explaining it so clearly and concisely, Bob. -- "Fish" (David B. Trout) Software Development Laboratories http://www.softdevlabs.com mail:

When you define two disks with the same volser, in the manner Fish describes, you are defining two different disks in effect. Neither disk sees any changes made to the other disk. The case that gives

Bob Polmanter wrote: [...] Not required. At least not with z/VM anyway. I of course can't speak for VM/CE, as I've never tried it with VM/CE. But z/VM certainly doesn't mind have multiple dasds with

Note that there are several kinds of disks in a VM system. "Dedicated" disks are ATTACHed to a virtual machine when it logs on, and are usually identified by their real (to CP) device address. Other

[email protected]> wrote: Since those are both VM/370 systems, you might want to read what we all read and many of us followed in those days: Melinda Varian's famous "What Mother Never Told You

CP doesn't duplicates, that part is true. But, CP doesn't place them offline. If you have duplicate volsers, CP will use the one with the lowest address. "use" that means: the one it will attach to

René Ferland ( /g/h390-vm/message/5351 ) , thank you.? Your offer may present a good starting point for me.

I think you will need to update all the entries of the directory of the 2nd level VM as well since they are defined in terms of the old VOLSERs. Or am I wrong here? It would be simpler if you had a

If my memory holds, this is at a really high level, and done via Hercules & the primary VM the primary VM: create empty DASD with dasdinit, attach them to MAINT, use ICKDSF to label, then DDR to copy

It looks like my first step would be to make copies of my first level DASD and then rename the VOLSERs. Any suggestions on the simplest way to do this, perhaps outside of Hercules?

My first rule for running VM under VM is that my Production System (first level) NEVER uses the same volsers as the Maintenance System (second level). This takes time to setup, but once it is done, I

Hi Daniel, Generally, its pretty easy to do and the effort is about the same as it is to get MVS to run under VM.? Basically, you need to: 1. have a second VM system with which to ipl as a guest of

The next exercise I'd like to try is to IPL VM under VM.? I'll surmise that I may need to duplicate some DASD and that some DASD can be shared read only.? Does anyone have a guide, or even a stream

Just a thought while I am at it... The "help" command in CMS currently only provides information about the Class G format commands.? While this may have made sense in a typical "real world" mainframe

That was it! Thank you! pur system p class z 0035 FILES PURGED

You may need to specify the owning userid (MVS) or SYSTEM on the PURGE command: PURGE SYSTEM P CLASS Z -or- PURGE MVS P CLASS Z De