ERserver. Stand-Alone Input/Output Configuration Program User s Guide. zseries SB

Transcription

1 ERserver zseries Stand-Alone Input/Output Configuration Program User s Guide SB

2

3 ERserver zseries Stand-Alone Input/Output Configuration Program User s Guide SB

4 Note! Before using this information and the product it supports, be sure to read the general information under Safety Notices on page v and Appendix F, Notices on page F-1. Third Edition (October 2002) This edition, SB , applies to zseries Processors There may be a newer version of this document in PDF format available on Resource Link.Goto and click on Library on the navigation bar. A newer version is indicated by a lower case alphabetic letter following the form number suffix. For example: 00a, 00b, 01a, 01b. Copyright International Business Machines Corporation 2000, All rights reserved. US Government Users Restricted Rights Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.

5 Contents Safety v Safety Notices v Product Recycling and Disposal v World Trade Safety Information v Laser Safety Information v Laser Compliance vi Preface vii Who Should Use This Book vii How This Book is Organized vii What You Should Know vii Terms Used in this Book viii I/O Devices viii I/O Configuration Data Set (IOCDS) viii I/O Configuration Program (IOCP) viii I/O Configuration Source (IOCS) viii How to Send your Comments ix Chapter 1. Introducing the Input/Output Configuration What is the I/O Configuration Process When is the Stand-Alone Version of IOCP Needed What Can the Stand-Alone Version of IOCP Do How to Start the I/O Configuration Process I/O Configuration Source Files Starter I/O Configuration Data Sets Description of a Stand-Alone Build of an IOCDS Chapter 2. Understanding the Stand-Alone Version of IOCP Controlling the Program Navigating the I/O Configuration Panels Using the I/O Configuration Program Options Overview of Options Description of Option Actions Overview of View Description of View Actions Channel path configuration Control Unit and Device Information Image Candidate List Image Access List Partition Images Configured Token Information Configuration Program Level Supported I/O mask IOCP Wait State Codes Enabled Wait States Disabled Wait States Chapter 3. Running the Stand-Alone Version of IOCP Preparing for System Installation If the I/O Configuration Source is Available at Installation Time If the I/O Configuration Source is NOT Available at Installation Time Building an Input/Output Configuration Data Set Power-on Reset for IOCDS Import/Build Copyright IBM Corp. 2000, 2002 iii

6 Importing I/O Configuration Source Files Import File from Diskette Import File from Tape Creating a New IOCDS in a New Central Processor Complex Updating an IOCDS Using the Card-Image Input Editor Appendix A. Configuration Examples A-1 Appendix B. Resolving IOCP Errors B-1 An Error Example B-1 Explanation of Errors in Example B-2 Appendix C. Channel Path (CHPID) Assignments C-1 Appendix D. Stand-Alone IOCP Support Element Messages D-1 Appendix E. IBM Agreement for Licensed Internal Code E-1 Actions You May Not Take E-1 Appendix F. Notices F-1 Trademarks and Service Marks F-1 Electronic Emission Notices F-1 Index X-1 iv zseries: Stand-Alone Input/Output Configuration Program User s Guide

7 Safety Safety Notices Safety notices may be printed throughout this guide. DANGER notices warn you of conditions or procedures that can result in death or severe personal injury. CAUTION notices warn you of conditions or procedures that can cause personal injury that is neither lethal nor extremely hazardous. Attention notices warn you of conditions or procedures that can cause damage to machines, equipment, or programs. Product Recycling and Disposal This unit contains materials such as circuit boards, cables, electromagnetic compatibility gaskets and connectors which may contain lead and copper/beryllium alloys that require special handling and disposal at end of life. Before this unit is disposed of, these materials must be removed and recycled or discarded according to applicable regulations. IBM offers product return programs in several countries, for country specific instructions please refer to the following web site: This product may contain a sealed lead acid battery(s) or a nickel-cadmium battery(s). The battery(s) must be recycled or disposed of properly. Recycling facilities may not be available in your area. In the United States, IBM has established a collection process for reuse, recycling, or proper disposal of used sealed lead acid, nickel cadmium, and nickel metal hydride batteries and battery packs from IBM equipment. For information on proper disposal of the batteries in this product, please contact IBM at For information on disposal of sealed lead acid or nickel cadmium batteries outside the United States, contact your local waste disposal or recycling facility. These systems contain R-507 refrigerant under high pressure. This refrigerant must not be released or vented to the atmosphere. To avoid risk of personal injury or damage to the system, adding refrigerant or any repair of the refrigerant system must be done by an experienced technician. In some countries, technicians must be certified to specific government requirements. World Trade Safety Information Several countries require the safety information contained in product publications to be presented in their national languages. If this requirement applies to your country, a safety information booklet is included in the publications package shipped with the product. The booklet contains the safety information in your national language with references to the US English source publications. Before using a US English publication to install, operate, or service this IBM product, you must first become familiar with the related safety information in the booklet. You should also refer to the booklet any time you do not clearly understand any safety information in the US English publications. Laser Safety Information All zseries models can use I/O cards such as PCI adapters, ESCON, FICON, OSA, InterSystem Coupling-3 (ISC-3), or other I/O features which are fiber optic based and utilize lasers or LEDs. Copyright IBM Corp. 2000, 2002 v

8 Laser Compliance All lasers are certified in the U.S. to conform to the requirements of DHHS 21 CFR Subchapter J for class 1 laser products. Outside the U.S., they are certified to be in compliance with the IEC 825 (first edition 1984) as a class 1 laser product. Consult the label on each part for laser certification numbers and approval information. CAUTION: All IBM laser modules are designed so that there is never any human access to laser radiation above a class 1 level during normal operation, user maintenance, or prescribed service conditions. Data processing environments can contain equipment transmitting on system links with laser modules that operate at greater than class 1 power levels. For this reason, never look into the end of an optical fiber cable or open receptacle. Only trained service personnel should perform the inspection or repair of optical fiber cable assemblies and receptacles. vi zseries: Stand-Alone Input/Output Configuration Program User s Guide

9 Preface This publication assists anyone who will use a stand-alone IOCP on an IBM zseries processor. Who Should Use This Book How This Book is Organized There are representatives of support element windows displayed throughout this manual. These are displayed to help you recognize the information that you will see while performing the procedures in this manual. The information displayed on these representatives may not agree with that displayed on your system. Always use the instructions and data displayed on your system. This book is intended for anyone using stand-alone IOCP to create Input/Output configuration data files. The information in this publication may be used for creating an initial I/O configuration source file (card-image statements) or for updating existing files. It is written for both first-time data processing users and experienced users, including system planners and administrators. Read the manual in its order of presentation. Then follow the procedures in Chapter 2, Understanding the Stand-Alone Version of IOCP on page 2-1 sequentially, to minimize the possibility of error when creating your I/O configuration data set. Chapter 1, Introducing the Input/Output Configuration on page 1-1. v Gives an overview of the I/O configuration program (IOCP) v Describes the IOCP Options (File actions) in detail v Describes the IOCP View actions v Lists the type of IOCP procedures v Explains how an I/O configuration data set (IOCDS) is built v Lists Wait State codes. Chapter 2, Understanding the Stand-Alone Version of IOCP, is a step-by-step procedure for creating an initial IOCDS for new system installations. Chapter 3, Running the Stand-Alone Version of IOCP, provides examples of various configurations. Appendix B, Resolving IOCP Errors, provides instructions for resolving errors. What You Should Know You must have a basic knowledge of IOCP tasks to use this manual effectively. Important For IOCP statement syntax, detailed error message descriptions, I/O device and control unit parameters, ESCON channel examples, and IOCP instructions for specific operating systems (OS/390, z/os, z/os.e, VM, z/vm, and VSE), see Input/Output Configuration Program User s Guide, SB Copyright IBM Corp. 2000, 2002 vii

10 Determining IOCP Release Level To determine the IOCP release level installed on your support element: 1. Log on the support element with System Programmer authority level or higher. You may log on the support element directly or use the Single Object Operations task on the Hardware Management Console. 2. From the Support Element Workplace window open (double click on) Task List from Views. 3. Open CPC Configuration from the Task List Work area. 4. Open Groups from Views. 5. Drag the CPC icon (using the right-hand mouse button) and drop it on Input/Output (I/O) Configuration under CPC Configuration. 6. From the Input/Output Configuration window select the View pull-down. 7. Select Configuration Program Level. 8. Read the version/release/level of the IOCP licensed internal code installed on this system. Additional Information More detailed information can be found in the following zseries system library publications: v For information on how to use the interface, see: Hardware Management Console Guide Support Element Operations Guide Terms Used in this Book These are the terms used when configuring the channels. I/O Devices The I/O devices are the input/output controllers and devices that attach to a standard channel for the zseries Processor. I/O Configuration Data Set (IOCDS) The IOCDS defines the configuration of I/O devices on the system to the licensed internal code used by the channels. The IOCDS is stored on the support element. Only one IOCDS can be used during system activation but up to four IOCDS s can be defined. I/O Configuration Program (IOCP) The IOCP is a stand-alone utility on the support element that is used to create the IOCDS for the zseries processor. The input to the IOCP is the I/O configuration source file. I/O Configuration Source (IOCS) The I/O configuration source file is used as input to the IOCP when an IOCDS is created. The I/O configuration source is an 80-column card-image, and is initially provided in EBCDIC format on a system tape, or in ASCII format on a 3.5 inch diskette. The file is then imported to the support element hard disk. Creating the I/O configuration source is the customer s responsibility, however the service representative can edit the file to correct errors. viii zseries: Stand-Alone Input/Output Configuration Program User s Guide

11 How to Send your Comments Your feedback is important in helping to provide the most accurate and high-quality information. Send your comments by using Resource Link at Select Feedback on the Navigation bar on the left. Be sure to include the name of the book, the form number of the book, the version of the book, if applicable, and the specific location of the text you are commenting on (for example, a page number or table number). Preface ix

12 x zseries: Stand-Alone Input/Output Configuration Program User s Guide

13 Chapter 1. Introducing the Input/Output Configuration What is the I/O Configuration Process When is the Stand-Alone Version of IOCP Needed What Can the Stand-Alone Version of IOCP Do How to Start the I/O Configuration Process I/O Configuration Source Files Starter I/O Configuration Data Sets Description of a Stand-Alone Build of an IOCDS Copyright IBM Corp. 2000,

14 What is the I/O Configuration Process All models are ESA capable processors. They therefore require input describing how their I/O channels and devices are configured. You must supply this information in a source file known as the Input/Output Configuration Source (IOCS). The IOCS contains detailed information for each channel path (CHPID), each control unit, and each device. For information on the source file statement syntax and content, see the Input/Output Configuration Program User s Guide, SB The IOCS can be created in advance by the system programmer and can be saved on a system tape (in EBCDIC format) or saved on a diskette in a PC file (in ACSII format). It can also be created or altered using the editor provided by the stand-alone Input/Output Configuration Program (IOCP) on the support element. The I/O Configuration Program uses the I/O Configuration Source to create aninput/output Configuration Data Set (IOCDS). The IOCDS is used by the processor during power-on reset to tell the ESA channel subsystem how the I/O is configured. Four possible I/O configurations (that is, four IOCSs and four corresponding IOCDSs) are available for a normal power-on reset, a fifth data set D0 is available for diagnostic procedures. When is the Stand-Alone Version of IOCP Needed The stand-alone version of IOCP is needed only: v When you generate (Build) an I/O configuration data set during initial installation v If your operating system does not have a batch version of IOCP v If you want to change the I/O configuration and do not have one of the following operating systems operational: OS/390 VSE/ESA VM/ESA z/os z/os.e z/vm Notes: 1. If, after system installation and activation, you are operating with either the OS/390, z/os, z/os.e, VM, z/vm, or VSE system control program, you can use the batch version of IOCP to make IOCDS changes. The advantage of the batch version of IOCP is that it will not disrupt system processing as does the stand-alone version of IOCP. 2. The Hardware Configuration Definition (HCD) is an OS/390, z/os and z/os.e application that aids in the definition of the I/O configuration and in the distribution of the appropriate I/O definition to the appropriate CPCs. The Hardware Management Console configured as a change management focal point with LIC changes enabled, assists the HCD in finding the names of all defined CPCs. A single HCD then distributes the appropriate IOCDS to the various CPCs. What Can the Stand-Alone Version of IOCP Do Using the stand-alone version of IOCP, you can: 1-2 zseries: Stand-Alone Input/Output Configuration Program User s Guide

15 v v v v v Create a new IOCDS from scratch during the installation of a new processor complex, if an I/O configuration source file (card-image input statements) is not available. Update an IOCDS on an existing processor. In some cases where the source file was not saved or if you are unsure of the source, you can select the Disassemble data set action. Disassemble data set is used to get an equivalent source deck from an existing IOCDS. Generate a minimum IOCDS during the installation of a new processor complex, if the statement file is only available on a system tape drive and the tape drive address is not properly defined in the default starter I/O configuration data sets (IOCDS). Replace an IOCDS in a processor complex if card-image input is available on a diskette or a system tape. (The system tape source assumes that the tape drive address is already defined in either the starter IOCDS or a minimum IOCDS as stated above). Note: A coupling facility model cannot access a channel-attached tape drive. How to Start the I/O Configuration Process The stand-alone version of IOCP is shipped with the processor as part of the Licensed Internal Code (LIC). The stand-alone program lets you define the I/O configuration to the system before a control program is installed. To run the stand-alone version of IOCP, you must: v Log on the support element in either the System Programmer or Service user mode, depending on whether you are a user or a service representative. You may log on the support element directly or use the Single object operation task on the Hardware Management Console to operate the support element. v Initialize the processor in either the ESA/390 or Logically Partitioned (LPAR) mode. The stand-alone version of IOCP can create an IOCDS for any mode supported by the CPC. v v v v Note: To use the stand-alone IOCP on a coupling facility, initialize it in ESA/390 mode with the Diagnostic IOCDS (D0). From the Support Element Workplace window open (double click on) Task List from Views. Open CPC Configuration from the Task List Work area. Open Groups from Views. Drag the CPC icon (using the right-hand mouse button) and drop it on Input/Output (I/O) Configuration under CPC Configuration. You may need to use other publications to create the I/O configuration source (IOCS) before using this book. v The stand-alone program uses the object-action user interface and is designed to be used with a keyboard or a mouse. If you are not familiar with using action bars, a mouse, or the zseries processor console interface, refer to: Support Element Operations Guide Hardware Management Console Guide Chapter 1. Introducing the Input/Output Configuration 1-3

16 v For IOCP statement syntax, detailed error message descriptions, and IOCP instructions for running the batch IOCP with specific operating systems (OS/390, z/os, z/os.e, VM, z/vm, and VSE), see: Input/Output Configuration Program User s Guide, SB The stand-alone version of IOCP does not have I/O recovery capability. I/O error conditions will cause IOCP to terminate. I/O Configuration Source Files Any comment card that begins with *IYP or *IZP is removed by stand-alone IOCP. Stand-alone IOCP uses *IYP comments for IOCP messages. Therefore, when Building an IOCDS or Importing an IOCS file from channel attached tape, stand-alone IOCP removes these IOCP messages so the resultant IOCS file contains only IOCP messages from the selected function. IOCS files may only contain source card records. Fifteen additional records are reserved for IOCP messages. The maximum size of all IOCS files on the support element hard disk is approximately 6.0MB. Both maximums are enforced by the following stand-alone IOCP functions: Copy, Open, Import, Build, and Disassemble. If you select to Build an IOCDS and the resultant IOCS file is too big, IOCP removes IOCP messages from the IOCS file to reduce its size until it is small enough to be written. If you select to Import an IOCS from channel attached tape and the resultant IOCS file is too big, IOCP removes comments and IOCP messages from the IOCS file to reduce its size until it is small enough to be written. If an IOCP function fails due to space constraints or if comments or IOCP messages were removed from the IOCS file, you can do one or more of the following and then retry the IOCP function: v v For IOCP functions Copy, Open/Save, Import, and Build you can reduce the size of the IOCS file you selected. Note that for Copy, this is the source IOCS file. For IOCP functions Copy, Open/Save, Import, Build, and Disassemble you can reduce the size of IOCS files other than the one you selected. Note that for Copy, this is an IOCS file other than the source and target IOCS files. To reduce the size of an IOCS file and increase the IOCS space available on the SE hard disk, perform one or more of the following: v v v v Delete an IOCS file other than the one you selected. Prior to deleting the IOCS you may want to export it to diskette, channel attached tape, or the Hardware Management Console hard drive. Remove comment cards from an IOCS file. Note that removing comments from an IOCS file on tape for Import from channel attached tape will not provide any benefit because IOCP automatically removes all comments if the IOCS is too big. Consolidate IOCP statements that are continued across multiple cards onto a minimum number of cards. Combine individual IODEVICE statements that attach to the same control unit(s) by using common UNIT and MODEL keyword values. Do not combine IODEVICE statements if they have conflicting keyword values. Note: For small size and efficiency, the last three bullets can also be done for any IOCS file, not just for IOCS files that are too big. 1-4 zseries: Stand-Alone Input/Output Configuration Program User s Guide

17 Starter I/O Configuration Data Sets The system can have four I/O configurations available to the user. There are four user I/O configuration data sets (IOCDS) shipped with the machine, called starter data sets, as well as a diagnostic configuration data set that is only used by service representatives. Initially, the service representative must decide if the system is to be power-on reset in ESA/390, or Logically Partitioned (LPAR) mode prior to running the stand-alone IOCP. The default or starter configuration data set selected will depend on the power-on reset mode. The starter data sets contain a variety of I/O control units and devices that allow the system to power-on reset and may or may not match a tape drive or printer that is physically attached to the system. These default data sets are provided as examples only and are not intended to provide a match of the customer s actual I/O configuration. The contents of the starter data sets can be viewed using the View channel path configuration pull-down from the Input/Output Configuration window. You can determine whether a match exists for a tape drive address in case the customer configuration source is available on a system tape. Figure 1-1. Input/Output Configuration window The starter data sets are: v The A0 ESASTART configuration data set, which is for basic mode only. v The A1 ALL ADDR configuration data set, which defines primarily ESCON Converter (CVC) channels, OSA channels and CFS CHPIDs. v The A2 CF_XMPL an LPAR configuration data set that defines several coupling channel types. Chapter 1. Introducing the Input/Output Configuration 1-5

18 v v The A3 MIF_XMPL is an LPAR example data set. The D0 DIAGNOSE configuration data set is used for diagnostic testing only. D0 puts all channels in a simulation mode. No external I/O can be accessed when the system has been power-on reset using this IOCDS. The stand-alone IOCP can be run after a power-on reset using D0. The system cannot be activated if D0 was used at power-on reset. Description of a Stand-Alone Build of an IOCDS IOCP performs the following steps when you specify that you want to generate, or build an IOCDS using the Build data set action. 1. The support element resets the targeted system or logical partition (System Reset Clear). 2. The support element loads the stand-alone IOCP into processor storage and starts the program. 3. IOCP reads the entire source file from the support element. Note: IOCP steps 4 through 5 are repeated for each input statement. 4. IOCP checks the syntax of each statement for correct format. If a syntax error is found (such as a missing parenthesis), IOCP inserts an error message in the card-image file following the statement that contains the error. IOCP stops checking the syntax of a statement when it encounters the first syntax error on that statement. Therefore, if there are two or more syntax errors on a single statement, the second and following errors are found on subsequent runs of IOCP. If IOCP finds an error in step 4, it performs steps 4 and 5 for the remainder of the statements and then continues with step IOCP checks the validity of each statement. For example, IOCP checks that a CNTLUNIT statement has specified a channel path that has been previously defined in a CHPID statement. If an error is found, IOCP inserts an error message in the card-image file following the statement that contains the error. If IOCP finds an error in step 5, IOCP returns to step 4, and performs only steps 4 and 5 for the remainder of the statements and then continues with step After all of the input statements have been processed, IOCP generates the IOCDS and makes additional checks. For example, IOCP checks that the maximum number of logical control units is not exceeded. If IOCP finds an error, IOCP inserts an error message at the end of the card-image file and continues with step IOCP produces IOCP configuration reports of the IOCDS generated. 8. IOCP writes the IOCDS file to the support element if no errors were found. 9. IOCP writes the source file to the support element. If errors were detected, error messages are embedded in the source file. Even if the build was successful, warning messages may be embedded in the source file. Any warning messages should be reviewed prior to using the IOCDS. 10. The support element terminates the IOCP program. (Note that starting up the IOCP code after this point will cause IOCP to put the processor in a B20 hard wait state.) 1-6 zseries: Stand-Alone Input/Output Configuration Program User s Guide

19 Chapter 2. Understanding the Stand-Alone Version of IOCP Controlling the Program Navigating the I/O Configuration Panels Input/Output Configuration Panel Using the I/O Configuration Program Options Overview of Options Enable/Disable Write Protection Copy Configuration Open Source File Import Source File Export Source File Delete Source File Build Data Set Disassemble Data Set Print Data Set Report Exit Description of Option Actions Enable/Disable Write Protection Copy Configuration Open Source File Import Source File Export Source File Delete Source File Build I/O Configuration Data Set Disassemble Data Set Print Data Set Report Using the I/O Configuration Program View Actions Overview of View Channel path configuration Parition images configured Token information Configuration program level Supported I/O mask Description of View Actions Channel path configuration Control Unit and Device Information Image Candidate List Image Access List Partition Images Configured Token Information Configuration Program Level Supported I/O mask IOCP Wait State Codes Enabled Wait States Disabled Wait States Copyright IBM Corp. 2000,

20 Controlling the Program The stand-alone version of IOCP is started and controlled from the support element. To enter the stand-alone version of the IOCP program: 1. You must be logged on the support element in the system programmer mode and the CPC must be power-on reset. 2. Open the Task List from the Views area (see Figure 2-1). 3. Open CPC Configuration from the Task List Work area. The CPC Configuration task list contains the Input/Output (I/O) Configuration task that you will start. 4. Open Groups from Views If the CPC is activated in basic mode: 5. Drag and drop the CPC on the Input/Output (I/O) Configuration task to start it. (see Figure 2-2 on page 2-3). If the CPC is activated in LPAR mode: 6. Open Images from Groups Work Area. 7. Drag and drop the partition from Images Work Area on the Input/Output (I/O) Configuration task to start it. Note: IOCP uses one CP If that CP is shared by many partitions, then a reduction in the stand-alone IOCP performance may be noticed. Figure 2-1. Support Element Workplace, Daily Tasks List 2-2 zseries: Stand-Alone Input/Output Configuration Program User s Guide

21 Figure 2-2. Support Element Workplace, CPC Configuration Tasks You are now viewing the Input/Output Configuration window (see Figure 2-3.). Figure 2-3. Input/Output Configuration window Navigating the I/O Configuration Panels The Input/Output Configuration window panel is the starting point for all of the stand-alone IOCP functions. The window in Figure 2-4 on page 2-4 shows that there are four user I/O configuration data sets, identified as A0 through A3. These data sets have names that are supplied by the system owner. Chapter 2. Understanding the Stand-Alone Version of IOCP 2-3

22 Note: If a data set appears on the IOCDS matching hardware system area (HSA) line, that data set is a dynamic capable IOCDS which is equivalent to the I/O configuration in the hardware system area (HSA). If the data set is also the active IOCDS and appears on the line Active input/output configuration data set (IOCDS), then it is not shown on the IOCDS matching HSA line. A dynamic capable IOCDS is one written using the HCD software tool on OS/390, z/os and z/os.e or the VM and z/vm IOCP CMS utility with the DYN option. The fifth data set, D0, is a diagnostic data set. D0 cannot be altered. It is intended for use by service personnel, with the following possible exception. If the user could not perform a power-on reset in ESA/390, or LPAR mode using any of the A0 through A3 data sets, D0 could be used to perform the power-on reset in ESA/390 mode. I/O cannot be accessed after a D0 power-on reset. The Input/Output Configuration window has an Options pull-down. The option actions allow the status or the content of the selected I/O configuration to be changed. The Input/Output Configuration window as well as the Options and the View actions are all explained in greater detail on the following pages. The important point here is that this window provides access to all of the information about the configuration data sets currently available on the system, and the Options pull-down permits the user to make changes to that information. Input/Output Configuration Panel Figure 2-4. Input/Output Configuration window The Input/Output Configuration window displays the following information: Data Set This is a 2-character identifier for the IOCDS. There are four IOCDSs (A0, A1, A2, and A3) that you can alter. They are described in Starter I/O Configuration Data Sets on page zseries: Stand-Alone Input/Output Configuration Program User s Guide

23 Name The 8-character name is the identification of the IOCDS. The name comes from the first eight characters that you have entered in the MSG1= field in the ID statement. The displayed name is from the IOCDS when it was written to the support element. Type The IOCDS Type can be one of the following: v ESA means that the IOCDS is an ESA mode only IOCDS v LPAR means that the IOCDS was created for logically partitioned mode. Write-Protected A NO indicates that the IOCDS is not write-protected. A YES indicates that the IOCDS is write-protected. Write-protection prevents the IOCDS from being overwritten by batch IOCP or stand-alone IOCP and from being overlaid by Copy configuration. Write-protection also prevents the I/O configuration source (IOCS) file from being: v overlaid by Disassemble data set, orbuild data set, orby Import source file from Hardware Management Console diskette, orhardware Management Console hard drive, or Support Element diskette, orchannel attached tape. v edited by Open source file v deleted by Delete source file Date Month, day, and year when the IOCDS was built. Time Hour and minute when the IOCDS was built. (Displayed in 24-hour format). Data Set Status Data Set Status may be one of the following: v Valid means the IOCDS is usable for power-on-reset (POR) purposes. Its content matches the source file only if the source status is Verified or Warnings. v Invalid means the IOCDS is not usable for power-on reset purposes. Either IOCP is currently writing to the IOCDS or the IOCDS was written in preparation for a CPC upgrade and will be unusable until the CPC is upgraded to the type of CPC supported by the IOCDS. You can select Supported I/O mask from the View action to determine why an IOCDS is invalid. v Active means this IOCDS was used during the most recent power-on-reset or by a dynamic activation from the System Control Program (SCP). Only one IOCDS can be active at a given time. The active IOCDS is made write-protected by the support element during POR with the IOCDS or after a dynamic activation by the SCP. The write protection can be removed with the Disable write protection action. Source Status The Source Status can be one of the following: v Verified means the stand-alone IOCP Build was processed with this source and was successful with no warnings or errors. v Warnings mean the stand-alone IOCP Build was processed with this source and was successful with one or more warnings or caution messages. Chapter 2. Understanding the Stand-Alone Version of IOCP 2-5

24 v Errors means the stand-alone IOCP Build was processed with this source and was not successful. There was a terminal error. Version v v v Note: No IOCDS is written and the IOCDS remains as it was before the Build or import from tape. Modified means the source file has been changed, by editing the file. This also indicates that the source may not match the current IOCDS. Imported means the source file was overlaid by an import from Hardware Management Console diskette, Hardware Management Console hard drive, Support element diskette, or Channel attached tape. Empty means the source file has been deleted or was erased when a batch IOCP program wrote the IOCDS. The version number identifies which version of IOCP was used to create the IOCDS. Using the I/O Configuration Program Options The action bar pull-down (list of actions or menu) shown in Figure 2-5 appears when you select the Options action on the Input/Output Configuration window. Select the action to be performed by clicking with the mouse or using the cursor movement and Enter keys. Figure 2-5. Input/Output Configuration Options Note that some of the Option actions (Enable and Disable write protection, Open source file, Copy configuration, Import from and Export to a diskette source, and Delete) are performed on the support element and do not require the stand-alone IOCP code to be loaded and run in processor storage. However, the Build data set, the Import from and Export to a system tape source, the Disassemble data set, and the Print data set report actions will automatically 2-6 zseries: Stand-Alone Input/Output Configuration Program User s Guide

25 load the stand-alone IOCP code into system storage and run the code on the system processor as did previous stand-alone IOCP programs. A request to Confirm the Action will be presented when one of these functions is selected. Note: The Confirm the Action window (see Figure 2-6) serves to warn you that any processor program or operating system will be overlaid with the stand-alone code to perform these functions. This window will only be presented the first time the IOCP stand-alone code is loaded into the processor storage. The Confirm the Action window also provides you an escape by using the Cancel action. Following is a brief overview of each Options action. References below each action Overview of Options Figure 2-6. Confirm the Action window indicate where detailed descriptions for these actions are given. Enable/Disable Write Protection Enable protects the IOCDS file on the hard disk from being overwritten. Disable resets the overwrite protection. (See Enable/Disable Write Protection on page 2-9.) Copy Configuration This action copies the I/O configuration data from one IOCDS to another. You might do this to duplicate an existing I/O configuration so you can test some changes on the copy. Both the source and IOCDS are copied. (See Copy Configuration on page 2-9.) Open Source File The Open action invokes an editor to modify the source file card-image data for the selected configuration or to create new card-image data. (See Open Source File on page 2-9.) Import Source File Import is used to transfer the card-image input to the support element hard disk from a channel-attached tape drive or from a diskette in the 3.5-inch A-drive in either the support element or the Hardware Management Console or from the Hardware Management Console hard drive. The source can then be edited and used to build an IOCDS. Source from a channel-attached tape must be in EBCDIC Chapter 2. Understanding the Stand-Alone Version of IOCP 2-7

26 80-column card-image format. Source from a diskette or Hardware Management Console hard drive must be in ASCII DOS 80-column card-image format. When importing from channel attached tape, the support element translates the source file from EBCDIC format to ASCII format. (See Import Source File on page 2-15.) Export Source File Export is used to transfer the card-image source file from the support element hard disk to the support element or Hardware Management Console diskette drive, the Hardware Management hard drive, or to a channel-attached tape drive. When exporting to channel-attached tape, the support element translates the source file from ASCII format to EBCDIC format. (See Export Source File on page 2-18.) Delete Source File This action frees disk space on the support element in the event that the allocated storage is full. Only the configuration source can be deleted. Note: Use this action with extreme care, since the source file for the selected IOCDS will be erased. A backup of the source (using the Export action) prior to performing a delete is recommended. (See Delete Source File on page 2-20.) Build Data Set The Build action: v Processes the source file data for the selected I/O configuration. v Checks the syntax and validates the configuration. v v Generates an IOCDS and, if there are no errors, writes the IOCDS to the support element hard disk. Writes the I/O configuration source (IOCS) file to the support element hard disk with any IOCP messages embedded in the file. (See Build I/O Configuration Data Set on page 2-20.) Disassemble Data Set This action generates the card-image statements (source file) from an IOCDS file on the support element hard disk and writes a new source file. (See Disassemble Data Set on page 2-23.) Print Data Set Report This action allows a formatted report of the IOCDS to be printed or written to a channel-attached tape drive. (See Print Data Set Report on page 2-24.) Exit Use Exit to leave the I/O configuration program. 2-8 zseries: Stand-Alone Input/Output Configuration Program User s Guide

27 Description of Option Actions Enable/Disable Write Protection Enable write protection is used to protect the I/O configuration data set (IOCDS) and I/O configuration source (IOCS) files on the hard disk from being overwritten. If a file is protected, a Yes will appear on the Input/Output Configuration window under the Write-Protected heading for the selected configuration. If you want to replace an IOCDS or IOCS that is write-protected, you must first remove the write protection using the Disable write protection action. Disable write protection is used to reset the protected status of the I/O configuration data set (IOCDS) and the I/O configuration source (IOCS) files on the hard disk. Files without write protection may be overwritten. Unprotected files are displayed on the Input/Output Configuration window with a No under the Write-Protected heading for the selected configuration. Copy Configuration The window shown in Figure 2-7 appears when you select the Copy configuration action on Input/Output Configuration window (Figure 2-5 on page 2-6). Figure 2-7. Copy Configuration Use this window to duplicate I/O configurations (IOCDS file and source IOCP card-image file if it exists). The selected configuration is displayed (for example, A0) as well as target configurations to be overlaid (for example, A2, A3). If you have designated certain configurations as write-protected, they will not display as copy targets. Also, the active configuration will only display if write protection has been removed. Note: In the window shown, IOCDS A1 is write-protected so it does not display as a possible target for the copy function. The copy action will fail if the I/O configuration source (IOCS) file exceeds the available space for IOCS files on the support element hard disk. For more information on the maximum size of an IOCS and how to reduce the size of an IOCS and increase the available IOCS file space, see I/O Configuration Source Files on page 1-4. Open Source File The Open source file action under Options on the Input/Output Configuration window provides the ability to: Chapter 2. Understanding the Stand-Alone Version of IOCP 2-9

28 v v Modify an existing I/O configuration source Create new card-image statements Note: If you edit a dynamic I/O configuration source (IOCS) file (an IOCS file that has been built using the Hardware Configuration Definition (HCD) or the VM IOCP CMS utility with the DYN option and imported to the support element hard disk), stand-alone IOCP disables the dynamic capability of the IOCS file. If a dynamic IOCS file is imported via diskette or from the Hardware Management Console hard drive and NOT modified, then the stand-alone IOCP Build program will create an IOCDS that is dynamic capable. This editor, by itself, will not run any of the steps necessary to generate an IOCDS. Before using the editor, the user can create a new source file from one of the following if no card-image exists: v Card-image data imported from support element or Hardware Management Console diskette v Card-image data imported from Hardware Management Console hard drive v Card-image data imported from a tape drive v Card-image recreated by disassembling an IOCDS v Card-image data copied from another source file. Sample IOCP statements can be obtained using the Insert Template at cursor position action under the Edit pull-down. These statements should be altered or deleted before a configuration report is printed or an IOCDS is written to the support element. For information about IOCP Statements and Functions, see Input/Output Configuration Program User s Guide, SB There is a source file associated with each IOCDS. If the IOCDS was generated using the Batch IOCP program, then a Disassemble action must be performed to get the equivalent source file for that I/O configuration. The following information is displayed at the bottom of the edit screen: v the number of the record at the top of the screen v the count of records in the IOCS v maximum number of records that the IOCS can contain You cannot save an IOCS that has more records than the maximum allowed. For more information on the maximum size of an IOCS and how to reduce the size of an IOCS, see I/O Configuration Source Files on page 1-4. Figure 2-8 on page 2-11 shows a sample A3 configuration as it appears when Open source file is selected under Options on the Input/Output Configuration window (see Figure 2-5 on page 2-6) zseries: Stand-Alone Input/Output Configuration Program User s Guide

29 Figure 2-8. Edit IOCDS card-image data Editor Actions Select one of the editor actions from the action bar at the top of the window. There are four types of actions: 1. File actions 2. Edit actions 3. Search actions and 4. Help. Figure 2-9 on page 2-12 shows the File actions under Open source file. Chapter 2. Understanding the Stand-Alone Version of IOCP 2-11

30 Figure 2-9. File actions pull-down File Actions The File actions are: Save (F2) Saves the current data without exiting the edit session. Exit (F3) Ends the editor. If the data in the file has changed since your last save, you will be prompted to either save the data or discard the changes. Figure 2-10 on page 2-13 shows the Edit actions under Open source file zseries: Stand-Alone Input/Output Configuration Program User s Guide

31 Figure Edit actions pull-down Edit Actions You can enter the character underlined in the pull-down action for abbreviated keyboard entry. For example, if you place the cursor over the underscored letter T (in the last action shown in the pull-down) and select Enter, IOCP recognizes a request to Define Load Tape Drive Keyboard function keys can also perform the edit actions, as shown in the following list. The Edit actions are: Undo line (Alt+Bksp) Restores the current line to previous text. Undo Restores the last deleted marked area. Copy (Alt+C) Copies lines marked with Alt+L and inserts the marked lines starting at the line following the cursor position. Copies a block of text marked with Alt+B and inserts it at the present cursor position. Move (Alt+M) Moves lines marked with Alt+L and inserts the marked lines starting at the line following the cursor position. Moves a block of text marked with Alt+M and inserts it at the present cursor position. Overlay (Alt+0) If a line mark was used (Alt+L), this will copy the marked line(s) and overlay the screen data starting with the character at the current cursor position. If a block mark was used (Alt+B) to mark an area, this will copy the marked area and overlay the screen characters starting with the character at the current cursor position (the upper left corner). Chapter 2. Understanding the Stand-Alone Version of IOCP 2-13

32 Adjust mark (Alt+A) Provides the same function as Copy (Alt+C) except the initial marked line or area is blanked out after the copy takes place. Unmark (Alt+U) Unmarks a line or area Delete (Alt+D) Deletes a marked area. Mark Current Line (Alt+L) Marks a line or group of lines. To mark a line, place the cursor anywhere on the line and hold the Alternate key while pressing the L key (Alt+L) (or select this action on the Edit pulldown). The line will be highlighted to indicate that it is marked. To mark a group of lines, use the Alt+L keys to mark the first line and the last line in the group. Marks (Alt+B) Marks a block area. To mark a block of characters, place the cursor on the upper left character of the block to be marked and hold the Alternate key down while pressing the B key (Alt+B) (or select this action on the Edit pull down). The character will be highlighted to indicate that it is marked. Place the cursor on the lower right character of the block of characters to be marked and use the Alt+B keys to mark the second character. The entire block of characters will be highlighted to indicate it is marked. There are also a number of control actions associated with the Edit pull-down. The control actions are: Previous page (PgUp) Scrolls back one page of data. Next page (PgDn) Scrolls forward one page of data. Top of file (Ctrl+Home) Scrolls to the top of data. Bottom of file (Ctrl+End) Scrolls to the bottom of data. Top of page (Ctrl+PgUp) Moves the cursor to the top of page. Bottom of page (Ctrl+PgDn) Moves the cursor to the bottom of page. Start of line (Home) Moves the cursor to the start of the line. End of line (End) Moves the cursor to the end of the line. There are 2 unique IOCP edit actions. They are: Define Load Tape Drive (Alt+T) Defines the configuration for the tape drive containing the IOCP Definition load source. Insert template at cursor position (Alt+l) Inserts a template of the IOCP statements. The template statements are inserted immediately following the cursor position line zseries: Stand-Alone Input/Output Configuration Program User s Guide

33 Figure 2-11shows the Search actions under Open source file. Figure Search pull-down actions Search Actions The Search actions let you locate data either by line number or by a specified string of characters. A repeat function is included for searching a specified character string. The Search actions are: Search/Replace (Ctrl+S) Scrolls to (or replaces) a specified search argument. You specify the desired search argument. Find Next (Ctrl+F) Scrolls to the next occurrence of the search argument last specified. Use this action as many times as necessary until the bottom of the data is reached. Ctrl+Home will put the cursor back to the top of the data. Change Next (Ctrl+C) Replaces the next occurrence of the search argument last specified. Use this action as many times as necessary until the bottom of the data is reached. Ctrl+Home will put the cursor back to the top of the data. Search for IOCP messages (Ctrl+A) Locates IOCP messages. These messages begin with *IYP. Import Source File The window shown in Figure 2-12 appears when the Import source file action is selected on the Input/Output Configuration window (Figure 2-5 on page 2-6). You Chapter 2. Understanding the Stand-Alone Version of IOCP 2-15

34 are prompted to select the source device from which the card-image statements (source) file is to be imported. The active selection for importing from a hard drive/diskette depends on if you are operating from the support element or Hardware Management Console. An import will fail if the I/O configuration source (IOCS) file has too many source records or it exceeds the available space for IOCS files on the support element hard disk. For more information on the maximum size of an IOCS and how to reduce the size of an IOCS and increase the available IOCS file space, see I/O Configuration Source Files on page 1-4. Note: The zseries coupling facility cannot access a channel attached tape. Figure Import source file action If you select Channel attached tape, the Import from Tape window is displayed (Figure 2-13). If this is the first time an attempt to load IOCP code into processor storage has been made, the Confirm the Action window shown in Figure 2-6 on page 2-7 is presented to warn that processor program storage will be overlaid and to provide an escape. Figure Import from Tape window From this window: 1. In the Tape drive address field, enter the device number of the tape drive that contains the card-image input deck. Note: The tape drive specified must be a channel-attached device. 2. Note that if you select a channel-attached tape drive as an input device, it must be defined in the current IOCDS that you selected in the current power-on reset 2-16 zseries: Stand-Alone Input/Output Configuration Program User s Guide

35 and the tape must be able to be manually mounted on the drive (i.e. IOCP does not support tape library systems). Note also that IOCP requires that the input records have a length of 80 bytes of EBCDIC data and a block size of 80 to bytes, where the block size is a multiple of Select importing a source file for logically partitioned mode, if the IOCDS to be generated is to be an LPAR IOCDS. 4. In the File number field, enter the number of the physical file on the tape (such as 1, 2, or 3) that contains the IOCP input deck. The file number should include any leading tape marks or files containing tape labels. IOCP issues a Rewind command followed by forward space file commands to position the tape to the requested file. 5. Select Ok. Note: During the Import from Tape, a build of the IOCDS will take place (see Figure 2-21 on page 2-22 through Figure 2-23 on page 2-23). If you select Support element diskette or Hardware Management Console diskette the Import Source File window is displayed (Figure 2-14). Figure Import Source File window From this window: 1. Select the source file name. IOCP assumes that input records from a diskette have a length of 80 bytes of ASCII data, and are in DOS file format. 2. Select Ok. If you select Hardware Management Console Hard Drive, the Import Source File window is displayed (Figure 2-15). Chapter 2. Understanding the Stand-Alone Version of IOCP 2-17

36 Figure Import from Hardware Management Console Hard Drive window From this window: 1. Enter the fully qualified file name for the source data set. IOCP assumes that input records from a diskette have a length of 80 bytes of ASCII data, and are in DOS file format. 2. Select Ok. Export Source File The window shown in Figure 2-16 appears when the Export Source File action is selected on the Input/Output Configuration window (Figure 2-5). You are prompted to select the target device to which the I/O configuration source (IOCS) file is to be exported. The active selection for exporting to a hard drive/diskette depends on if you are operating from the support element or Hardware Management Console. Note: The zseries coupling facility cannot access a channel-attached tape. Figure Export window If you select Channel attached tape, the Export to Tape window is displayed (Figure 2-17 on page 2-19). If this is the first time an attempt to load IOCP code into processor storage has been made, the Confirm the Action window shown in Figure 2-6 on page 2-7 is presented to warn that processor program storage will be overlaid and to provide an escape zseries: Stand-Alone Input/Output Configuration Program User s Guide

37 Figure Export to Tape window From this window: 1. In the Tape drive address field, enter the device number of the tape device that is to receive the IOCS file. Note: If you select a channel-attached tape drive as an output device, it must be defined in the current IOCDS that you selected in the current power-on-reset and the tape must be able to be manually mounted on the drive (i.e. IOCP does not support tape library systems). IOCP writes to tape with a block size of In the File number field, enter the number of the physical file on the tape (such as 1, 2, or 3) where you want to store the file. IOCP issues a Rewind command followed by forward space file commands to position the tape to the requested file. 3. Select Ok. If you select Support element diskette or Hardware Management Console Diskette the Export Source File window is displayed (Figure 2-18). Figure Export Source File window From this window: 1. Type the target file name. 2. Select Ok. If you select Hardware Management Console Hard Drive the Export Source File window is displayed (Figure 2-19). Chapter 2. Understanding the Stand-Alone Version of IOCP 2-19

38 Figure Export to Hardware Management Console Hard Drive window From this window: 1. Type the fully qualified file name for the target data set. 2. Select Ok. Delete Source File Use this action to free disk space. The delete function erases the selected I/O configuration source (IOCS) file and replaces it with a minimum default template IOCS file. If you have several large source files and have used up all allocated disk space, you could export one or more files to a diskette or channel attached tape and then use this delete function to free up more disk space to edit another source. A configuration is made up of the IOCDS file and a statement card-image input source file. The source is not required for operation, only the IOCDS. The source may not always be there, as in the case of a delete, or the case of a batch IOCP program writing the IOCDS file to the support element hard disk, which performs the source delete function automatically. Build I/O Configuration Data Set To create an IOCDS file, select the Build data set action on the Input/Output Configuration window (Figure 2-5 on page 2-6) zseries: Stand-Alone Input/Output Configuration Program User s Guide

39 Figure Build Configuration Data Set window From this window: 1. If the resultant IOCDS is to be used in LPAR mode, select Build the IOCDS for logically partitioned mode. Note: Selection is indicated by ' in the check box. You can select more than one box or none at all. For example, you can select Build the IOCDS for logically partitioned mode and Send output to a printer at the same time. 2. To print the output, select Send output to a printer. 3. In the Printer address field, enter the device number of the printer that is to print IOCP messages and reports. Note: The output printer address that you specify in this display window must be a channel-attached device and must be in the current IOCDS that you selected at power-on reset and must be available to the processor complex you are using to run IOCP. The output printer must be initialized (print/forms buffer must be loaded) before you run IOCP. While running the configuration program, you should assign exclusively to the program any devices and control units that IOCP uses. (Other systems should not share the devices and control units). Channel attached printers cannot be accessed by a zseries coupling facility. 4. In the Lines per page field, enter the maximum number of lines that you want on an output page (you can specify a maximum of 99). The default is 55. (IOCP uses a value of 20 if you specify a value less than 20.). 5. De-select the Continue printing if data errors occur option to cause the printer to stop if a data check occurs during printing. The first time an attempt to load IOCP code into processor storage is made (for example, for the Build data set action), the Confirm the Action window shown in Figure 2-6 on page 2-7 is presented to warn that processor program storage will be overlaid and to provide an escape. The completion of the build will be reported in one of three ways: v Successful v Warnings (see Figure 2-22 on page 2-22) v Errors (see Figure 2-23 on page 2-23). Chapter 2. Understanding the Stand-Alone Version of IOCP 2-21

40 At this point the system is reset, the stand-alone IOCP is loaded into storage, and IOCP is started using a program status word (PSW) restart. After the restart, the Configuration Task in Progress window displays (Figure 2-21), indicating the steps being processed. Certain error, warning or informational messages may also display to assist you with the build. Figure Configuration Task in Progress If the build was successful and there are no caution or warning messages, the resultant IOCDS has been written to the support element hard disk. If the build was successful but had caution or warning messages, the window shown in Figure 2-22 is displayed. The resultant IOCDS has been written to the support element hard disk. Use the Open source file action, described in Open Source File on page 2-7 to correct the caution and warning conditions, if necessary. Note: If you edit a dynamic I/O configuration source (IOCS) file (an IOCS file that has been built using the Hardware Configuration Definition (HCD) or the VM IOCP CMS utility with the DYN option and imported to the support element hard disk), stand-alone IOCP disables the dynamic capability of the IOCS file. Figure Configuration Task in Progress - build with cautions or warnings If the build was not successful, an error message will appear, as in, and the resultant IOCDS will NOT be written to the support element hard disk zseries: Stand-Alone Input/Output Configuration Program User s Guide

41 Figure Configuration Task in Progress - build with errors The caution, warning, and error messages are embedded in the I/O configuration source (IOCS) file at the line where the condition was detected. To correct the condition, go to the editor by selecting the Open source file action on the Input/Output Configuration window. IOCP messages are displayed in the editor as comments. The messages begin with *IYP in column 1, followed by the IOCP message. IOCP Messages are explained in the Input/Output Configuration Program User s Guide, SB It is not necessary to remove the messages from the file. IOCP will remove the messages when the conditions are no longer detected. If you have changed the IOCS file on the support element and have built a new IOCDS on the support element hard disk, an inconsistency may occur between the operating system configuration and the I/O configuration in the newly built IOCDS. v v For an OS/390, z/os and z/os.e system, if you change the hardware configuration with stand-alone IOCP, you should make the same changes using HCD, rewrite the IOCDS, and perform a power-on reset. This action ensures consistency between the software and hardware configurations and allows the CPC to be dynamic-capable. For a VM and z/vm system, if you change the hardware configuration with stand-alone IOCP and VM and z/vm cannot sense all the device changes in the hardware configuration during initial program load (IPL), modify the real I/O configuration file and regenerate the operating system; or modify the system configuration file and re-ipl your operating system. This action ensures consistency between the software and hardware configurations. (The real I/O configuration file is HCPRIO. The system configuration file is SYSTEM CONFIG.) v Note: For a dynamic-capable system, you must rewrite the IOCDS from z/vm using the DYN option and perform a power-on reset. For a VSE system, if you change the hardware configuration with stand-alone IOCP, you should update the software configuration to reflect the changes (modify the ASI Procedure file). This action ensures consistency between the software and hardware configurations. IOCP will remove some messages, if necessary, to prevent the I/O configuration source (IOCS) from exceeding the available space for IOCS files on the support element hard disk. For more information on the maximum size of an IOCS and how to reduce the size of an IOCS and increase the available IOCS file space, see I/O Configuration Source Files on page 1-4. Disassemble Data Set Use this action to read an IOCDS from the hard disk on the support element and create an I/O configuration source file (IOCS). IOCP reads the IOCDS, converts it into an IOCS file then writes the file to the support element hard disk. The IOCS contains the full configuration described in the original customer input file, and is the Chapter 2. Understanding the Stand-Alone Version of IOCP 2-23

42 logical equivalent of the card input deck. The IOCS may not appear as it did in the original. Since IOCP does not save comments, comments do not appear in the source file. If the Data Set Status is invalid, the Disassemble Data set option is not available. If this is the first time an attempt to load IOCP code into processor storage has been made, the Confirm the Action window shown in Figure 2-6 on page 2-7 is presented to warn that processor program storage will be overlaid and to provide an escape. The disassemble action will fail if the I/O configuration source (IOCS) file generated by IOCP exceeds the available space for IOCS files on the support element hard disk. For more information on how to reduce the size of an IOCS and increase the available IOCS file space, see I/O Configuration Source Files on page 1-4. Print Data Set Report This action reads the selected IOCDS file and prints the I/O configuration reports on the system printer or writes the formatted reports to a channel-attached tape. The window shown in Figure 2-24 displays when the Print data set report option is selected from the Input/Ouput Configuration window. If the Data Set Status is invalid, the Print data set report option is not available. Note: The zseries coupling facility cannot perform the Print data set report action. Figure Print data set report If you select Print to printer, the Printer information window is displayed (Figure 2-25 on page 2-25). If this is the first time an attempt to load IOCP code into processor storage has been made, the Confirm the Action window shown in Figure 2-6 on page 2-7 is presented to warn that processor program storage will be overlaid and to provide an escape zseries: Stand-Alone Input/Output Configuration Program User s Guide

43 Figure Print to printer 1. In the Printer address field, enter the device number of the printer that is to print IOCP messages and reports. Note: The output printer that you specify in this display window must be a channel-attached device and must be in the current IOCDS that you selected at power-on reset and must be available to the processor complex you are using to run IOCP. The output printer must be initialized (print/forms buffer must be loaded) before you run IOCP. While running the configuration program, you should assign exclusively to the program any devices and control units that IOCP uses. (Other systems should not share the devices and control units). Channel-attached printers cannot be accessed by a zseries coupling facility. 2. In the Lines per page field, enter the maximum number of lines that you want on an output page (you can specify a maximum of 99). The default is 55. (IOCP uses a value of 20 if you specify a value less than 20.) If you select Write report to tape, the Write report to tape window is displayed (Figure 2-26). If this is the first time an attempt to load IOCP code into processor storage has been made, the Confirm the Action window shown in Figure 2-6 on page 2-7 is presented to warn that processor program storage will be overlaid and to provide an escape. Figure Write report to tape 1. In the Tape drive address field, enter the device number of the tape device that is to receive the formatted I/O configuration reports. Note: The tape drive that you specify in this display window must be a channel-attached device and must be defined in the current IOCDS that you selected at power-on reset and must be available to the processor complex you are using to run IOCP. The tape must be able to be Chapter 2. Understanding the Stand-Alone Version of IOCP 2-25

44 manually mounted on the drive (for example, IOCP does not support tape library systems). IOCP writes the report with records that have a length of 133 bytes (where the first character is an ANSI carriage control character) and blocks that are 1330 bytes long. 2. In the File number field, enter the number of the physical file on the tape (such as 1, 2, or 3) where you want to store the file. IOCP issues a Rewind command followed by forward space file commands to position the tape to the requested file. 3. Select Ok. Using the I/O Configuration Program View Actions The action bar pull-down shown in Figure 2-27 appears when you select the View action on the Input/Output Configuration window action bar. Select the action to be performed by clicking with the mouse or using the cursor movement and Enter keys. Figure Input/Output Configuration View Actions Overview of View The View actions let you see what is actually written in the selected IOCDS file. Note: The information displayed using View is read directly from the IOCDS file, not the source. Channel path configuration Channel path configuration displays information that defines channel paths in the selected input/output (I/O) configuration. If the data set status is invalid, the Channel path configuration option is not available. (See Channel path configuration on page 2-27.) Parition images configured Partition images configured displays the image numbers and names of logical partitions supported by the selected input/output (I/O) configuration. If the data set status is invalid, the Partition images configured option is not available. (See Partition Images Configured on page 2-30) 2-26 zseries: Stand-Alone Input/Output Configuration Program User s Guide

45 Description of View Actions Token information Token information displays the current channel subsystem hardware system area (HSA) token and the token of the selected input/output configuration data set (IOCDS). If the data set status is invalid, the Token information option is not available. (See Token Information on page 2-30.) Configuration program level Configuration program level displays the version, release, and level of the licensed internal code for the stand-alone input/output configuration program (IOCP) on this support element. If the data set status is invalid, the Configuration program level option is not available. (See Configuration Program Level on page 2-31.) Supported I/O mask Supported I/O mask displays the hexadecimal values that identify the processor functions or channel path types. If the data set status is invalid, the Supported I/O mask option is not available. (See Supported I/O mask on page 2-31.) Channel path configuration By selecting Channel path configuration the Channel Path Configuration window appears (Figure 2-28). Figure Channel Path Configuration Control Unit and Device Information Control Unit Information and Device Information is displayed on a per path basis. A path is the combination of CHPID, link address, and control unit logical address. Therefore, when you select either of these options after selecting an Chapter 2. Understanding the Stand-Alone Version of IOCP 2-27

46 ESCON or FICON CHPID with multiple link addresses, the Select a Link Address window is displayed first, as shown in Figure This window displays all the link addresses defined in the selected IOCDS for the selected CHPID. From this window, you choose the specific link address for which you want information to be displayed. Figure Select a Link address Figure Control Unit Information 2-28 zseries: Stand-Alone Input/Output Configuration Program User s Guide

47 Figure Device Information Image Candidate List Select Image candidate list to display a list of logical partitions that have authority to access the CHPID. Figure Image Candidate List Image Access List Select Image access list to display the logical partitions that will initially have access to the CHPID at logical partition activation following the initial power-on reset of the IOCDS. Chapter 2. Understanding the Stand-Alone Version of IOCP 2-29

48 Figure Image Access List Partition Images Configured When Partition images configured is selected from the View action pull-down, the names of all the partitions defined in the selected IOCDS are displayed. Figure Partition Names window Token Information When Token information is selected from the View action pull-down, data pertaining to the selected IOCDS is displayed zseries: Stand-Alone Input/Output Configuration Program User s Guide

49 Figure Token information pull-down The Data set token field displays the token information contained in the I/O configuration data set (IOCDS) selected. A Hardware system area token is only displayed if the system has been power-on reset using an IOCDS that had a token in it. (The token was built by the HCD tool in OS/390, z/os and z/os.e or the VM and z/vm IOCP CMS utility with the DYN option). If any dynamic I/O configuration changes have been made, the hardware system area token displayed is the current token and not the token from the power-on reset. Configuration Program Level The Configuration program level is the current level of the Stand Alone IOCP on the support element. Figure Configuration program level Supported I/O mask When the Supported I/O mask is selected from the View action pull-down, the functions and channel path types supported by the machine are identified. The IOCDS Supported I/O mask identifies the functions and channel path types defined in the IOCDS. If the IOCDS mask contains a value not in the Machine Supported mask, then the Unsupported mask items display shows which items are not supported by the machine. A third item will display in the window if there is an unsupported I/O mask. The machine cannot power-on reset with this IOCDS and the IOCDS is marked Invalid. See CPC Activation and Power-on Reset Error in the Input/Output Configuration Program User s Guide (SB ), for a description of the supported functions and channel types. Chapter 2. Understanding the Stand-Alone Version of IOCP 2-31

50 Figure Supported I/O mask 2-32 zseries: Stand-Alone Input/Output Configuration Program User s Guide

51 IOCP Wait State Codes Enabled Wait States During execution of the stand-alone version of IOCP, the central processor enters many enabled wait states (PSW bit 7 is on). These are normal conditions while IOCP waits for the support element to respond to IOCP requests such as a read or write of an IOCDS. If the central processor stays in an enabled wait state for more than six minutes, other than waiting for operator input on a console, the support element is busy. You may either wait for the support element to finish or press the Cancel key and restart IOCP at a later time. If the problem persists, contact the service representative. Disabled Wait States During execution of the stand-alone version of IOCP, IOCP issues the following disabled wait state codes when the indicated conditions occur. (Note that the OS/390, z/os, z/os.e, VM, z/vm, and VSE versions of IOCP do not issue wait state codes.) Wait State codes are hexadecimal and are stored in the low-order bytes of the address area of the PSW. B20 Explanation: The operator who is running the stand-alone version of IOCP has started IOCP processing after the IOCP function has completed, or IOCP was unable to read from the support element the selected function to perform. Operator Response: If IOCP completed the selected function, no action is required. Otherwise, notify your system programmer. Problem Determination: If IOCP did not complete the selected function, save all associated output. Contact the service representative. Operator Response: Notify your system programmer. Problem Determination: Save all associated output. Contact the service representative. B24 Explanation: During execution of the stand-alone version of IOCP, IOCP has encountered an error in the support element and cannot communicate with the person operating IOCP. Operator Response: Notify your system programmer. Problem Determination: Save all associated output. Contact the service representative. B21 Explanation: A program-check interruption has occurred during execution of the stand-alone version of IOCP. Operator Response: Notify your system programmer. Problem Determination: Save all associated output. Contact the service representative. B22 Explanation: A machine-check interruption has occurred during execution of the stand-alone version of Operator Response: Notify your system programmer. Problem Determination: Save all associated output. Contact the service representative. B23 Explanation: An uncorrectable I/O error has occurred during execution of the stand-alone version of IOCP. Chapter 2. Understanding the Stand-Alone Version of IOCP 2-33

52 2-34 zseries: Stand-Alone Input/Output Configuration Program User s Guide

53 Chapter 3. Running the Stand-Alone Version of IOCP Preparing for System Installation If the I/O Configuration Source is Available at Installation Time If the I/O Configuration Source is NOT Available at Installation Time Creating an I/O Configuration Source (IOCS) File Building an Input/Output Configuration Data Set Power-on Reset for IOCDS Import/Build Importing I/O Configuration Source Files Import File from Diskette Importing the Input File from Diskette to the Hard Disk Building the IOCDS Power-on Reset to Enable the IOCDS Import File from Tape Build an IOCDS with tape unit defined Defining the Load Device Example Building an IOCDS for the channel attached tape drive Power-on Reset to Enable IOCDS Just Built Importing the Input File from Tape to the Hard Disk Power-on Reset to Enable the IOCDS Correcting Cautions, Warnings, and Errors Creating a New IOCDS in a New Central Processor Complex Updating an IOCDS Using the Card-Image Input Editor Copyright IBM Corp. 2000,

54 Preparing for System Installation Before system installation, it is the customers responsibility to supply the service representative with an I/O configuration source (IOCS) file, consisting of card-image input statements. The IOCS contains specific data about all attached control units and I/O devices. It must be created in 80-column card-image format and can be provided on either tape (EBCIDIC format file) or 3.5-inch diskette (DOS, ASCII format file). The IOCS is the input to the I/O configuration program (IOCP). The IOCP loads the IOCS into the processor and uses it to build thei/o configuration data set (IOCDS). Note: If you are upgrading to a zseries Processor, you can specify CHECKCPC=NO in the PARM parameter of the EXEC statement for IOCP on OS/390, z/os, z/os.e and VSE or specify CMS option NOCHKCPC for IOCP on VM and z/vm. These options allow you to write the IOCDS for your new processor to your current processor prior to the upgrade. You can also write an IOCDS when preparing to upgrade from one of the following processors. Inform the service representative which IOCDS should be used after the upgrade. v 9672 Parallel Enterprise Server Model R06 at EC F99918 v 9672 Parallel Enterprise Server Models R16-RX6, Y16-YX6, T16-T26, RA6, RB6, RC6, and RD6 at EC F99918 v 9672 Parallel Enterprise Server Models X17-X27 and Z17-ZZ7 at EC F If the I/O Configuration Source is Available at Installation Time... If the I/O configuration source file (card-image statements) has been previously prepared, then you can begin the procedure of importing it to the support element and generating an IOCDS. Follow the steps provided in Building an Input/Output Configuration Data Set on page 3-4. If the I/O Configuration Source is NOT Available at Installation Time... If no I/O configuration source file (card-image statements) is available, then you must create one at installation time. The Input/Output Configuration Program User s Guide, SB , provides instructions on the card-image format and syntax. Note: If the I/O Configuration Source is NOT Available, Installation Time is increased significantly. Creating an I/O Configuration Source (IOCS) File The IOCS can be created on either tape or diskette, as follows: Note: Channel attached tape cannot be accessed on a zseries Coupling Facility. v If the source is to be saved on channel attached tape, use a utility program available with your operating system (e.g., IEBGENER on OS/390, z/os and z/os.e) to copy the IOCS file to tape. After it is created, go to Building an Input/Output Configuration Data Set on page 3-4. v If the source is to be saved on diskette, you can use any personal computer or equivalent, with DOS, OS/2, or an equivalent ASCII file editor to create the 80 column card-image diskette. You can also use the stand-alone IOCP editor on the support element to input the I/O definition. Procedures for using the support element editor are found in Creating a New IOCDS in a New Central Processor Complex on page zseries: Stand-Alone Input/Output Configuration Program User s Guide

55 If a default or old source file already exists, you may 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 source file rather than create a new one from scratch. Procedures are found in Updating an IOCDS Using the Card-Image Input Editor on page For I/O configuration examples, refer to the Input/Output Configuration Program User s Guide, SB Chapter 3. Running the Stand-Alone Version of IOCP 3-3

56 Building an Input/Output Configuration Data Set If an I/O configuration source file has been prepared on either tape or diskette, then proceed with the following steps: Power-on Reset for IOCDS Import/Build Important! The procedures that follow were written with instructions for use with the mouse. To use the mouse, simply move the mouse so the tip of the mouse pointer is on the text of the selection you want, then click the left mouse button. For details on mouse, keyboard, and mnemonic usage, see Support Element Operations Guide for your system. If you want to change a Write-Protected data set, select the data set, then select Options from the action bar and Disable write protection from the pull-down. Power-On Reset will be prevented if the support element has locked out disruptive tasks. User Action 1 From the Support Element Workplace window open (double click on) Task List from Views. 2 Open CPC Recovery from the Task List Work Area. Result The Task List Work Area displays. The CPC Recovery task list displays in the task area. 3 Open Groups from Views. The Groups Work Area displays. 3-4 zseries: Stand-Alone Input/Output Configuration Program User s Guide

57 User Action 4 Drag the CPC icon (using the right-hand mouse button) and drop it on the Power-on Reset task under CPC Recovery. Result The Power-on Reset window displays. User Action 5 Select the desired system Mode and IOCDS, then select Ok. 6 Select the storage size for your system, then select Ok. Result The Change Storage Size window displays. The Confirm the Action window displays. User Action Result 7 Select Power-on reset. The Power-on Reset in Progress window displays. The power-on reset takes approximately five minutes. A message displays when the reset completes. 8 Select OK, then go to Importing I/O Configuration Source Files on page 3-6. End of power-on procedure. Chapter 3. Running the Stand-Alone Version of IOCP 3-5

58 Importing I/O Configuration Source Files If you have the input file on tape, go to Import File from Tape on page Import File from Diskette If you have the input file on diskette, follow these steps: Importing the Input File from Diskette to the Hard Disk Note: The steps for importing a source file from the support element diskette are similar to those for importing a source file from the hardware management console diskette or hardware management console hard drive. User Action 1 From the Support Element Workplace window initiate the Input/Output (I/O) Configuration task. If necessary, refer to the procedure described in Controlling the Program on page 2-2 Result The Input/Output Configuration window displays. 3-6 zseries: Stand-Alone Input/Output Configuration Program User s Guide

59 User Action Result 2 Select any data set that is NOT write protected. Note: The data set you select will be replaced by the file you are going to import. The Import window displays. Select Options. Select Import source file. User Action 3 Select support element diskette, then select Ok. Note: The active selection depends on if you are operating from the support element or the Hardware Management Console. 4 Insert the diskette into the diskette drive, then select Ok. Result The Insert Diskette window displays. The Import Source File window displays. User Action 5 Select the file name and extension of the source file, then select Ok. Result The Remove Diskette window displays. 6 Remove the diskette, then select Ok. The Input/Output Configuration window displays. Chapter 3. Running the Stand-Alone Version of IOCP 3-7

60 Building the IOCDS From the Input/Output Configuration window: User Action 7 Select Options, then select Build data set. Result The Confirm the Action window displays for the first build only. User Action Result 8 Select Ok. The Build Configuration window displays. User Action 9 Select the appropriate parameters then select Ok. If desired, select Build the IOCDS for logically partitioned mode and/or Send output to a printer. Note: Selection is indicated by a ' in the check box. You can select more than one box or none at all. For example, you can select Build for the IOCDS for logically partitioned mode and Send output to a printer at the same time. Result The Confirmation Task in Progress window displays while the IOCP program runs. The run can take up to 12 minutes. Status messages will display to indicate the progress of the IOCDS build. The program completes and a final IOCP status message displays which states whether or not the build was successful (see IOCP messages box). 3-8 zseries: Stand-Alone Input/Output Configuration Program User s Guide

61 IOCP Messages If the build is successful, one of the following messages is displayed: IYP500A: PROCESSING COMPLETED. CHECK PRINTER FOR LISTING OR RETURN TO EDITOR. IYP501A: PROCESSING COMPLETED. NO PRINTER SPECIFIED-NO LISTING. PROCEED. In case of cautions or warnings, the following message is displayed: IYP502A: PROCESSING COMPLETED BUT HAS MESSAGE(S), RETURN TO EDITOR. In case of errors, one of the following messages is displayed: IYP506A: CARD INPUT ERROR(S) FOUND, RETURN TO EDITOR. IYP507A: IOCDS GENERATION ERROR, RETURN TO EDITOR. The IOCP messages are embedded in the source file at the line where the condition was detected. Use the Open source file action to correct the condition. For a brief description of the editor, go to Correcting Cautions, Warnings, and Errors on page For an example of some typical errors, see Appendix B, Resolving IOCP Errors on page B-1. For more detailed error information, see Input/Output Configuration Program User s Guide, SB User Action Result 10 Select Ok. The Input/Output Configuration window displays. 11 Do you have more data sets to install? YES - go to back to step 2. NO - close the Input/Output Configuration window and go to step 12. Chapter 3. Running the Stand-Alone Version of IOCP 3-9

62 Power-on Reset to Enable the IOCDS User Action 12 From thesupport Element Workplace window open (double click on) Task List from Views. 13 Open CPC Recovery from the Task List Work Area. Result The Task List Work Area displays. The CPC Recovery task list displays in the task area. 14 Open Groups from Views. The Groups Work Area displays. 15 Drag the CPC icon (using the right-hand mouse button) and drop it on the Power-on Reset task under CPC Recovery. The Power-on Reset window displays. 16 Select the desired system mode and IOCDS, then select Ok. 17 Select the desired system mode and IOCDS, then select Ok. TheChange Storage Size window displays. The Confirm the Action window displays. 18 Select Power-on reset. The Power-on Reset in progress window displays. The power-on reset takes approximately 5 minutes. A message displays when the reset completes. 19 Select Ok. End of import procedure. Import File from Tape Build an IOCDS with tape unit defined Use Channel path configuration under the View pulldown to determine if a tape drive is already defined. If the tape unit is already defined, go to step 20. If no tape unit is defined begin with the following: User Action 1 From the Support Element Workplace window initiate the Input/Output (I/O) Configuration task. If necessary refer to the procedure described in Controlling the Program on page 2-2. Result The Import window displays zseries: Stand-Alone Input/Output Configuration Program User s Guide

63 User Action 2 Select any data set that is not write-protected from the menu. Select Options, then select Open source file. 3 Note: If the file contains any source data, delete the data as follows: v Press F3 to exit the editor. v Select Options, then select Delete Source File. v Select Options, then select Open Source File. v Continue with step 4. Result The configuration window for the selected data set displays (shown on the next page). The data is deleted. Note: Before deleting selected IOCS data confirm that it is not needed or save the data by exporting it to a diskette. Chapter 3. Running the Stand-Alone Version of IOCP 3-11

64 User Action 4 Select Edit. Select Defined Load Tape Device. 5 Select the tape unit from the list, then select Ok. Enter the CHPID that the tape is on, then select Ok. Select the CHPID type from the list, then select Ok. Type in the unit address of the tape drive. Note: The tape must be able to be manually mounted on the drive or be preloaded on the drive (i.e. IOCP does not support tape library systems). Select Ok. Result The Define load tape device window displays. A message displays stating that the input tape unit statements were created zseries: Stand-Alone Input/Output Configuration Program User s Guide

65 User Action Result 6 Select File, then select Save. The Input/Output Configuration window displays. Proceed to step 8. Defining the Load Device Example The following is an example of the source file after completing steps 1 thru 6. If the data displayed on your support element editor is similar to the one shown here, go to step 8. Otherwise, perform a delete function, then edit the file. Enter the correct data, exactly as displayed here, substituting the addresses for your tape drive and its control unit. (Lines beginning with * are comment lines and are not required.) Chapter 3. Running the Stand-Alone Version of IOCP 3-13

66 The example source is shown in the window. You can change the I/O device address for your load device using the procedure in step 7. If the channel type is not a converter (CVC) then change the CVC to an ESCON channel type (CNC or FCV), or parallel channel type BL. User Action 7 1. Locate the statement UNITADD=((F0,16)) and change the F0 to the first unit address recognized by your tape control unit, and change the 16 to the number of unit addresses supported by your control unit. 2. Locate the statement IODEVICE ADDRESS=(37F0,1), and change the F0 portion of the device address to the unit address of the tape drive you intend to use. 3. Change 37 to the channel path identifier (CHPID) to which your tape drive is attached (37 appears 3 times in the default file. Change all 3 places.) 4. Change 3490 to your device type (such as 3420). Select File from the action bar. Select Save and exit from the pull-down. Result The first five steps input the data for your system s load source. The last two steps save your input. Data Recovery If this data is ever lost or destroyed, perform a delete function, then edit the file. Enter the correct data, exactly as displayed here (comment lines are not needed), substituting the addresses for your tape drive as just described. Proceed to step zseries: Stand-Alone Input/Output Configuration Program User s Guide

67 Building an IOCDS for the channel attached tape drive From the Input/Output Configuration window: User Action 8 Select Options, then select Build data set. Result The Confirm the action window displays on the first build only. 9 Select Ok. The Build Configuration Data Set window displays. User Action 10 Select the appropriate parameters then select Ok. If desired, select Build the IOCDS for logically partitioned mode and/or Send output to a printer. Note: Selection is indicated by ' in the check box. You can select more than one box or none at all. For example, you can select Build the IOCDS for logically partitioned mode and Send output to a printer at the same time. Result The Configuration Task in Progress window displays while the IOCP program runs. The run can take up to 12 minutes. Status messages will display to indicate the progress of the IOCDS build. The program completes and a final IOCP status message displays which states whether or not the build was successful. Chapter 3. Running the Stand-Alone Version of IOCP 3-15