Hardware resolution problems and solutions

The following table lists some hardware resolution problems and possible solutions:

Table 1. Hardware resolution problems and actions
Problem	Actions
The IOCP file contains a UUID statement that causes the parsing of the IOCP file to fail with an invalid keyword parsing error.	Change the UUID statement to a comment before importing the IOCP file into the CHPID Mapping Tool. If the UUID statement spans multiple lines, remove any continuation characters in column 72. Put an asterisk (*) in column 1 of each line of the UUID statement. Reverse these changes to the UUID statement before importing the file into HCD.
Insufficient hardware	Buy additional hardware or load a different IOCP input file.
The IOCP input file could contain channel definitions for adapter types that are not part of the new machine configuration.	Modify or remove those definitions in the IOCP.
There might be more adapter defined or implied than the machine can support. For example, if a machine is fully configured with the maximum number of CHPIDs, any definitions in the IOCP for internal coupling links cause the input to fail.	Remove adapters that are higher in number than the total number that the machine supports. You can see this information in the Adapter Type Summary pane of the Hardware Resolution view.
The IOCP input file could contain errors. For example, someone could edit a file to remove some of the channel definitions but fail to delete the control unit definitions referencing those channels. The source input must be accurate, and HCD must generate it or IOCP must verify it.	Replace the IOCP input file. Ensure that the IOCP input file is accurate by using an IOCP file that hardware configuration definition (HCD) generated or that IOCP verified. Note: The IOCP input file you provide to the tool by the direct output of HCD or IOCP must verify the input. The IOCP definitions must be output directly from a version of HCD/HCM that supports the system, or the appropriate level of ICP IOCP must verify it before you load it into the tool.
The IOCP input file might have become corrupted during editing or during a file transfer. Some characters could be dropped or the asterisks (*) used for continuation indicators could be in the wrong column. The source file must be accurate and adhere to the syntax rules of IOCP.	Replace the IOCP input file. Ensure that the IOCP input file is accurate by using an IOCP file that hardware configuration definition (HCD) generated or that IOCP verified. Note: The IOCP input file you provide to the tool by the direct output of HCD or IOCP must verify the input. The IOCP definitions must be output directly from a version of HCD/HCM that supports the system, or the appropriate level of ICP IOCP must verify it before you load it into the tool.