Using the CHPID Mapping Tool Support utility

HCM can prepare an IOCP file as input to the CHPID Mapping Tool (CMT) in order to add or update PCHIDs to this IOCP for XMP processors. You can download the CHPID Mapping Tool from the Resource Link home page.

It runs on a Windows workstation. Input to the CHPID Mapping Tool is the hardware configuration file (CFReport 1) of your machine and a valid IOCP input file (with missing or obsolete PCHIDs).

In HCM, invoke the CHPID Mapping Tool Support dialog from either the Utilities menu or from the Edit Processor dialog (see Editing a processor). This utility offers the following functions:

  • It exports (downloads) an IOCP file of a selected processor from the host.
  • It launches the CHPID Mapping Tool with the exported IOCP file as input. Using the CHPID Mapping Tool, you can assign PCHID values to CHPIDs. The modified IOCP file is saved on the workstation.
  • It imports (uploads) the modified IOCP file back to the host where it automatically invokes a PCHID migration. Then it also refreshes the local configuration with the new CHPID-PCHID assignment.
Figure 1. CHPID Mapping Tool Support
Support. This dialog is accessible from the HCM product GUI and includes accessible help information.

Using the dialog shown in Figure 1 you can update PCHID values in your configuration performing the following steps:

  1. From the Processor listbox, you must select a processor, if you invoked this utility from the Utilities menu. If invoked from the Edit Processor dialog, this listbox contains the current processor, and you cannot select a different one.
  2. Selecting the Export IOCP File for CMT radio button receives the IOCP file for the selected processor from the host. The IODF for the current configuration must be a work IODF. The dialog proposes a name for the file where to store the IOCP file on the workstation, or, using the "..." button, you can browse for a file where to store the retrieved IOCP. When you press the OK button, HCD creates a validated work IODF on the host and exports an IOCP file for the selected processor. HCM then downloads the exported IOCP file and saves it on the workstation in the previously specified file. If HCD encounters errors during generation of the validated work IODF, HCM displays the corresponding messages and does not download any IOCP file.
  3. Following a successful download of the exported IOCP file, select the Launch CMT radio button. However, this button is only enabled if the CHPID Mapping Tool is correctly installed on your workstation. Note that the feature to be launched from HCM is available for the CHPID Mapping Tool version 4.02 or later.

    In the Input IOCP File for CMT entry field, specify the IOCP file exported in step 2. In the Output IOCP File for CMT entry field, specify the output file where the CHPID Mapping Tool should write the modified IOCP file with the new PCHID assignment. For IOCP input and output, you can use the same file.

    When you press the OK button, HCM starts the CHPID Mapping Tool, passing the selected file names as parameters. Now use the CMT to perform the PCHID assignment and save the updated IOCP file. The new IOCP file contains the original I/O definitions together with inserted and/or updated PCHID values. The original hardware configuration token is still contained in the generated statements.

    For information about how to use the CMT, refer to its online help and related documentation.

  4. Now, back in the CHPID Mapping Tool Support dialog, select the Import IOCP File from CMT radio button and press the OK button to send the updated IOCP file back to the host. This action automatically migrates the new CHPID-PCHID assignment into the affected IODF on the host, thus creating an updated work IODF without further need to use the HCD dialog. This action also refreshes the HCM configuration file on the workstation with the PCHID assignment, thus keeping the configurations on host and workstation consistent.
Note:
  1. If for any reasons for an XMP processor you want to define a channel that is not physically installed on the machine yet, you can use the method of over-defining a channel path as described in Over-defining a CHPID. Thus you can avoid to let the CHPID Mapping Tool run into an error, because it cannot find the PCHID.
  2. If the PCHID migration produces an assembler error listing, you can use button Show Listing to display an assembler listing for error analyzing purposes.
  3. When during importing an IOCP data set from the CHPID Mapping Tool, you get a message due to insufficient space allocation, you can use the HCD profile keyword ALLOC_SPACE to overwrite the default space allocation. For more information, refer to the z/OS HCD User's Guide.
  4. The CHPID Mapping Tool support is not available for configurations with an associated MUA-enabled 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.