Author: Robert Sample
Posted: Sat Mar 25, 2017 8:52 pm (GMT 5.5)
Your question is in the right place. I think you need to read the z/OS HCD User's Guide manual again. It says, among other things, that:
Your questions imply that IOCDS and IODF are distinct and that the IOCDS is built first -- the quote from the manual clarifies that your thinking is the exact reverse of the way things happen. The IOCDS is built FROM the IODF, so the IODF must exist first. And yes, except for I/O devices, the various IOCDS will have the same configuration from the IODF (unless you change the production IODF before building an IOCDS in which case it may be different -- but all the IOCDS built from a single production IODF will have the same configuration).
_________________
TANSTAAFL
The first rule of code reuse is that the code needs to be worth re-using.
"We should forget about small efficiencies, say about 97% of the time: premature optimization is the root of all evil." -- Donald Knuth
Posted: Sat Mar 25, 2017 8:52 pm (GMT 5.5)
Your question is in the right place. I think you need to read the z/OS HCD User's Guide manual again. It says, among other things, that:
| Quote: |
| Build an IOCDS When a production IODF has been created, you can build an IOCDS (it can be built only from a production IODF). Processors may have varying numbers of IOCDSs. A particular IOCDS is used at POR time to make the configuration data known to the CSS. |
_________________
TANSTAAFL
The first rule of code reuse is that the code needs to be worth re-using.
"We should forget about small efficiencies, say about 97% of the time: premature optimization is the root of all evil." -- Donald Knuth