Tom Marchant wrote:
On Sun, 24 Apr 2016 11:31:42 -0500, Mike Schwab wrote:
Once a volume exceeds 64K cylinders, the allocations must be a
multiple of 21 cylinders, and the volume must be a multiple of 1113
cylinders. That is the z/OS requirements for EAV volumes.
More precisely, allocations from the Cylinder-managed space on an EAV
are rounded up to the next multiple of 21 cylinders. Allocations from the
track-managed space area up to cylinder 65520 continue to be allocated
as before. The boundary between them is cylinder 65520.
I don't know if there are any restrictions for using an EAV for an IPL volume.
Data sets that are accessed early in IPL must be below the line on an
EAV, as must those which have their own access methods and have not been
rewritten to support doing I/O to the cylinder-managed space. The
latter are probably most important for a one-pack system.
The (probably incomplete) list I have for system data sets has not been
updated since z/OS V1.13, but I think these still cannot be above the line:
- Imbed and Keyrange attributes, incompatible CA sizes for VSAM
- NUCLEUS
- SVCLIB
- LOGREC
- VTOC & VTOCIX
- RACF databases
- Page data sets
- HFS data sets
- Parmlib concatenation data sets
- XRC Control, Master, or Cluster non-VSAM data sets
This should *not* be read to mean or imply that everything that is not
listed here is supported above the line. It's just the list of things I
know about that don't work.
--
John Eells
IBM Poughkeepsie
[email protected]
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
