Build a Production IODF
Although z/VM HCD validates configuration data as it is entered, a complete validation may not be performed, because some other required data may not be defined at this time. Therefore, a "post-validation" is performed at "Build Production IODF" time. This validation might issue messages you have to deal with, according to their severity. The production IODF is not created if any errors with a severity higher than 'warning' are produced.
- For a VM operating system, the IODF must contain at least one device.
- For a processor, the IODF must contain a definition for at least one channel path, one control unit, and one device. If only receiving CF channel paths are defined for a processor, the control unit and device definitions can be omitted.
Prior to building the production or validated work IODF, HCD updates the work IODF. For processors that must be defined for a maximum HSA, it extends the processor configuration to its maximum. This means that HCD ensures that all logical channel subsystems as well as all partitions are defined for the processor, and that each channel subsystem allows for the maximum number of devices per subchannel set.
It's possible that a work IODF will satisfy all validation rules, but that a contained processor configuration supporting multiple logical channel subsystems (in the following called XMP processor processor) will be lacking at least one physical channel identifier (PCHID). In this case, the output from Build Production IODF will be a validated work IODF, but a message will show all CHPIDs for which the required PCHIDs are missing. Before you can build the final production IODF for the XMP processor, you must insert all PCHIDs into that validated work IODF.
With a validated work IODF, you can use the CHPID Mapping Tool to insert all required PCHIDs. Input to this tool is an IOCP input file. To create this input, use the REXX utility CBDSIOCP (Build an IOCDS or an IOCP Input File). The IOCP input file is suitable for use with the CHPID Mapping Tool. This tool eases the task of mapping CHPIDs to PCHIDs in an IODF. See How to interact with the CHPID Mapping Tool for more detailed information on how to interact with the CHPID Mapping Tool to insert the missing PCHIDs into the validated work IODF. As soon as all PCHIDs are inserted into the validated work IODF, the production IODF can be built.
You can build a production IODF using HCM. Also, the REXX utility CBDSPROD allows generation of a production IODF from a work IODF. For more information on invoking this utility, see Build a Production IODF (CBDSPROD).