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


Repair an IODF

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

Repair an IODF

If your IODF contains defects, some of them can be repaired with the REPAIR option of the TRACE ID=IODF command.

First, your IODF must be set in update mode to correct defects. You can do this, for example, by changing a processor description field in your work IODF. A production IODF cannot be repaired.

To repair defects in your work IODF, add the REPAIR option to the TRACE ID=IODF command: TRACE ON,REPAIR,ID=IODF.

Each corrected defect is recorded in the trace data set with the string Defect has been corrected.

If a defect has been repaired, message CBDA998I, Defect(s) detected in IODF xxx. Repair action performed is issued. Repeat the TRACE ID=IODF command to check whether all defects could be corrected.

An IODF that has been enabled for multi-user access cannot be repaired. You first must disable it for multi-user access before it can be set into update mode and be repaired.

If defects in the IODF cannot be repaired via the REPAIR option, you may have to rebuild the IODF. You accomplish this task by exporting the configuration data from the IODF via dialog option 2.10 Build I/O configuration data. You can then migrate this data to a new IODF:

  1. Export configuration types Processor, Operating System and Switch with configuration ID * into three different output data sets (see Build I/O configuration data). This will generate I/O configuration statements for all processor, operating system and switch configurations. You can set the profile option SHOW_CONFIG_ALL to YES to also generate configuration statements for unconnected control units and devices in addition to those for switches (see Export/import additional configuration objects).
  2. Successively migrate the processor, OS configuration and switch data into a new IODF (see Migrate I/O configuration statements). You must use batch jobs for this purpose, since in dialog mode, HCD does not support the configuration ID *.
  3. Verify - for example using compare reports - that the new IODF includes all data. If necessary, add any missing items manually.
  4. Check that the IODF is free from defects.

Go to the previous page Go to the next page




Copyright IBM Corporation 1990, 2014