z/OS HCD User's Guide
Previous topic | Next topic | Contents | Index | Contact z/OS | Library | PDF


Process overview

z/OS HCD User's Guide
SC34-2669-00

Process overview

Input to the CMT is the hardware configuration file (CFReport 1) of your machine and a valid IOCP input file (with missing or obsolete PCHIDs).

Output from the CMT is again an IOCP input file that now has all missing or updated PCHID values filled in. Upload this IOCP input file and re-import it into the validated work IODF using the HCD primary task Migrate configuration data.

Via this migration task, it is possible to update a validated work IODF with the PCHID values that have been written by the CMT into the IOCP input file. Other changes on the validated work IODF are not possible without loosing the status of a validated work IODF. A PCHID migration is only possible to a validated work IODF. Since PCHID migration changes the IODF, the IODF status is reset to 'not validated'. All functions that allow read-access to a work IODF are also possible for a validated work IODF. Activate functions are not possible, except for building an IOCP deck that can be used as input to the CMT. Only after all PCHIDs have been inserted into the validated work IODF, you can successfully build a production IODF.


1.
When a machine is ordered, the output of the order process is a binary file that represents the physical description of the final machine. One of the components of that file is the type and physical location, including the Physical Channel Identifier (PCHID) value assigned to that location, of all the I/O features in the final machine. This file is called a CFReport.

Go to the previous page Go to the next page




Copyright IBM Corporation 1990, 2014