Updating an IOCDS using the card-image input editor

This procedure describes how to update the I/O configuration data in an IOCDS for an installed CPC.

To update the I/O configuration for a CPC:
  1. Ensure that the CPC is in a power-on-reset state with an appropriate existing IOCDS.
  2. Select the I/O Configuration task. See Starting the program.
  3. Select the IOCDS to update.
  4. Check to see if the IOCDS source file matches the contents of the IOCDS. (The source status is Verified or Warnings, and the IOCDS status is Valid when the IOCDS was built from the IOCDS source file). If the status for the IOCDS source file and the IOCDS do not match, then the IOCDS source file for the selected IOCDS might be different than the IOCDS source file used to create the IOCDS. The IOCDS source file might have been imported or it might have been modified using the editor. You can create a reconstructed IOCDS source file by selecting the Disassemble Data Set action. The Disassemble Data Set action reads the selected IOCDS and creates an equivalent to the IOCDS source file used to create the IOCDS.
  5. If you are adding (or deleting) I/O from your configuration, update the IOCDS source file (Open Source File) to reflect any new I/O configured in the CPC.
  6. Prepare the system line printer or channel-attached tape drive if you want printed output. The printer must be initialized (the print/forms buffer must be loaded).
  7. Select the Build Data Set action under Options on the Input/Output Configuration window of the Support Element.
    1. Select the appropriate parameters and press Enter.

      During the build, IOCP reads the input statements, saves them as card-image data in storage, checks the syntax, validates it, and generates an IOCDS. It produces configuration reports of the IOCDS generated. (See IOCP statements and functions for more details.)

      IOCP displays messages to give the status of the IOCDS build.

    2. An error message is displayed if IOCP has detected errors in the IOCDS source file. To correct the errors, on the Input/Output Configuration window of the Support Element after the completion message, click Options and then Open Source File.

      Errors IOCP detects are displayed in the editor. Errors are displayed in the form of IOCP comments that begin with *ICP in column 1, followed by the error message number and the message text. See IOCP messages for an explanation of the error messages. Correct the errors in the IOCDS source file. It is not necessary to remove the error messages from the file. IOCP removes the messages when no errors are detected on subsequent builds.

  8. View the generated IOCDS content using the View action (Control Unit Information and Device Information windows) or analyze the configuration reports produced in Step 7.a to ensure that the I/O configuration you want has been generated. If the IOCDS source file must be changed, use the editor to modify the IOCDS source file on the Hardware Management Console and return to the Build Data Set process (Step 7).
  9. If the input file is correct and the build is complete, the IOCDS is on the CPC Support Element hard disk.
  10. Export the IOCDS source file to provide a backup if editing was done on the Hardware Management Console or SE console.
  11. Exit IOCP by clicking the Cancel action on any IOCP window.

    The I/O configuration data in the new Ax IOCDS now contains your new configuration. Selecting a power-on reset, with Ax as the IOCDS parameter, activates the new configuration and makes the Ax IOCDS the configuration that the I/O subsystem uses to control I/O requests. Select the IOCDS and the system mode on the Power-on Reset window.

  12. Test the new configuration following the procedures established for your installation.
Notes:
  1. If you change the hardware configuration with the stand-alone version of IOCP and you use a z/OS® system or if you use a VM system on which you have chosen to use HCM and HCD, make the same changes using HCM or HCD and rewrite the IOCDS before performing the power-on reset. This action ensures consistency between the software and hardware configurations and makes the CPC capable of dynamic I/O configuration.
  2. If you change the hardware configuration with the stand-alone version of IOCP and you use a VM system but do not use HCM and HCD, make any appropriate changes to the VM system before performing the power-on reset. If VM cannot sense all the device changes in the hardware configuration during initial program load (IPL), modify the system configuration file and re-IPL your operating system. These actions ensure consistency between the software and hardware configurations.

    For a CPC capable of dynamic I/O configuration, you must rewrite the IOCDS from VM using privilege class B and perform a power-on reset.

  3. For a VSE system, if you change the hardware configuration with the stand-alone version of IOCP, update your software configuration to reflect the changes (modify the ASI Procedure file). Doing so ensures consistency between the software and hardware configurations.