Lizette Koehler wrote:
List -
Just curious if the EAV volumes can be used for SYSRES volumes or if there are
any concerns with using them for SYSRES volumes?
If they can be used for SYSRES, any considerations with using them?
Well, yes. Every data set type we use to distribute software is, I
believe, supported above the line (i.e., in the EAS). But that does not
mean that all the users of all those data sets tolerate the different
format of the cylinder address.
It's certainly safest to put any system software run-time (target
library or file system) for which we do not explicitly document support
in the EAS below the line on an EAV. This is what I'd recommend for
now. However, I am not sure we actually put this information into the
books (vs. only adding it to the announcements).
I have lost track of this for a few years, but when I last knew, these
things *were* supported in EAS:
- PDS and PDSE (including load modules and program objects)
- Plain vanilla (nonextended format) sequential
- BDAM
- GDG
- LPALIB
- LPA list data sets
- Link list data sets
- SYSn.IPLPARM
- Catalogs
- VVDSs
- JES2 and JES3 spool and checkpoint, JES3 JCT
- DFSMSrmm data sets
- DFSMShsm data sets
- Standalone Dump data sets
- VSAM
...and these things *were not* supported in EAS:
- Imbed and Keyrange attributes, incompatible CA sizes for VSAM
- NUCLEUS
- SVCLIB
- LOGREC
- VTOC and VTOCIX,
- RACF databases
- Page data sets
- HFS data sets
- Parmlib concatenation data sets
- XRC Control, Master, or Cluster non-VSAM data sets
Some of the things on the second list could have migrated to the first
while I wasn't looking specifically at these lists. However, from my
memory of release plans since z/OS V1.12 (when I last updated the lists
above), I am moderately confident that none of them have, with the
possible exception of SVCLIB, which I found on both lists (oops).
Obviously, at least to me, some of the things on the first list do not
*belong* on the IPL volume, including any operational data set.
You can also put all the DLIBs above the line, since they are processed
by system utilities that understand how to address data in the EAS. The
same goes for SMP/E CSI data sets and volume-specific user catalogs,
which can live on the volumes they represent.
--
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
