I was a bit hasty in my reply. My response was correct. You can add an OS VTOC to any volume.
For clarification, this could impact what you are able to do with the volume. If it has an OS VTOC, you cannot use for CP Owned spaces like the Object Direct, Spooling, Paging, TDISK, etc. Depending on you directory manager, you may still be able to allocate mini-disks on the volume as long as they don't overlay the VTOC that you have allocated. I presume that you have a reason to have an OS VTOC. It is not necessary to have an OS VTOC to be able to make VM volumes available on a z/OS system. z/OS can mount a VM volume and leaving the standard VM volume labels will prevent z/OS from writing over you VM mini-disks because the volume will appear to have no free space. If you want an OS-formatted disk to run a guest, you could consider creating a mini-disk that starts somewhere higher than cylinder 0 of the real volume and put an OS VTOC on that. ____________________________________ Rick Barlow Systems Engineering Consultant Nationwide Services Co., Enterprise Business Intelligence Services Mainframe, z/VM and zSeries Linux Support One Nationwide Plaza 3-25-02 Columbus OH 43215-2220 U.S.A Voice: (614) 249-5213 Fax: (614) 677-7681 mailto:[EMAIL PROTECTED] Richard R Barlow/Nationwide/NWIE wrote on 02/08/2006 08:29:09 AM: > You can put an OS VTOC on the voluems using ICKDSF. The control > statements would look something like this: > INIT UNIT(dev) VOLID(volser) - > VTOC(001,00,150) INDEX(000,01,14) - > MAP NOVERIFY NOCHECK NOVALIDATE > > > VM/ESA and z/VM Discussions <[email protected]> wrote on > 02/08/2006 08:21:34 AM: > > > [email protected] > > > > Hello. We are a VM shop only, therefore our DASD is formatted for VM > > and have a VM VTOC. Is it possible to put an osvtoc (the 'O' word > > <g>) on these volumes without totally reformatting the drive, etc? > > Thanks, > > Steve G.
