Methods of running the stand-alone version of IOCP

Following are descriptions of various ways to run the stand-alone version of IOCP.

Before system installation, the service representative must find out if the IOCDS source file has been previously prepared for use during installation. If you are upgrading a CPC and an IOCDS was written in preparation of the upgrade, use that IOCDS. Otherwise, a new IOCDS must be written.

If the IOCDS source file has been previously prepared, then it must be imported to the CPC Support Element. The IOCDS source file can be on any of the following, if supported:
  • A location that can be accessed through FTP (uncompressed text file)
  • A USB flash memory drive in the Hardware Management Console

If no IOCDS or IOCDS source file is available, then it must be created at the time of installation. Use the editor supplied with the stand-alone I/O Configuration program to create the IOCDS source file.

If a default or old IOCDS source file exists, you can use the Delete source file action to clear the file or use the editor actions to Mark and Delete the default or existing statements in the selected IOCDS source file rather than creating a new one.

Run the stand-alone version of IOCP to:
  • Create a new IOCDS during the installation of a new CPC if the IOCDS source file is not available.
  • Update an IOCDS on an existing CPC, using the Open Source File action. In some cases where the IOCDS source file was not saved or if you are unsure of the IOCDS source file, you can select the Disassemble Data Set action to get an equivalent IOCDS source file from an existing IOCDS.
  • Replace an IOCDS (using Import and Build) in a CPC if the IOCDS source file is available on a diskette.