z/OS HCD User's Guide
Previous topic | Next topic | Contents | Index | Contact z/OS | Library | PDF


Build System z cluster IOCDSs

z/OS HCD User's Guide
SC34-2669-00

Build System z cluster IOCDSs

The following procedure describes how to build an IOCDS for processors in a System z cluster with an SNA address defined.

To build IOCDSs within a System z cluster:

  • The SNA address has to be defined for a CPC configured in a System z cluster
  • Specific RACF authority has to be attained (for details on required access authority, refer to Security-related considerations).
  • The operating system must not be running as a guest under z/VM.

Perform the following steps:

  1. On the Primary Task Selection panel, select Activate or process configuration data and from the resulting panel select Build and manage System z cluster IOCDSs, IPL attributes and dynamic I/O changes. The System z Cluster List is displayed:

    Figure 93. System z Cluster List
       Goto  Query  Help
     ------------------------------------------------------------------------------
                                 System z Cluster List                  Row 1 of 18
     Command ===> _______________________________________________ Scroll ===> PAGE
    
     Select one or more CPCs, then press Enter.
    
        --------------CPC--------------   IODF
      / SNA Address        Type   Model   Processor ID
      s IBM390PS.DAN2      2094   S28     DAN2
      s IBM390PS.ECL2      2097   E40     ECL2
      _ IBM390PS.G14       2084   B16     G14
      _ IBM390PS.G15       2084   D32     G15
      _ IBM390PS.H05       2097   E26     H05
      _ IBM390PS.H37       2097   E26     H37
      _ IBM390PS.H42       2097   E26     H42
      _ IBM390PS.POL1      2096   S07     POL1
      # IBM390PS.P0ZGMR04
      _ IBM390PS.P0000H27  2097   E56     H27
      # IBM390PS.RAP       2066   004
      _ IBM390PS.R17       2817   M32     R17
      v IBM390PS.R35       2817   M49     R35
      _ IBM390PS.R37       2817   M32     R37

    This panel shows all CPCs configured in a System z cluster. They are identified by the SNA address of their support element and displayed together with their Type and Model as well as the Processor ID in the IODF. The SNA address has been specified in the processor definition task for the IODF processor definitions and enables the relation to the configured CPCs.

    A disabled sign (#) in the action entry field can be due to:

    • SNA address not defined in the IODF. In this case, the IODF Processor ID shows no value. Either define the SNA address for a corresponding processor in the accessed IODF or use another IODF.
    • SE (support element) of CPC did not respond. In this case, the CPC Type and Model fields show no values.

    A processor ID followed by two dots (..) indicates that this SNA address has been defined for several processors in the IODF. The first processor ID (in alphabetical order) with the SNA address is displayed. If you want to apply any of the group actions on another processor, use Select other processor configuration from the context menu (or action code p).

  2. On the System z Cluster List, select the CPCs for which you want to build and manage the IOCDSs and Work with IOCDSs from the context menu (or action code  s ). HCD displays the IOCDS List (shown with sample data):
    Figure 94. IOCDS List invoked from the System z Cluster List
       Goto  Query  Help
     ------------------------------------------------------------------------------
                                       IOCDS List          Row 1 of 8 More:       >
     Command ===> _______________________________________________ Scroll ===> PAGE
    
     Select one or a group of IOCDSs, then press Enter.
    
                                              -----Token Match----- Write
     / IOCDS       Name     Type   Status     IOCDS/HSA IOCDS/Proc. Protect
     _ A0.DAN2     052DAN2  LPAR   POR        Yes       Yes         Yes-POR
     _ A0.ECL2     062AECL2 LPAR   Alternate  No        No          No
     u A1.DAN2     021ADAN2 LPAR   Alternate  No        No          No
     _ A1.ECL2     054AECL2 LPAR   Alternate  No        Yes         No
     _ A2.DAN2     025ADAN2 LPAR   Alternate  No        No          No
     _ A2.ECL2     059AECL2 LPAR   Alternate  No        No          No
     _ A3.DAN2     026ADAN2 LPAR   Alternate  No        No          No
     _ A3.ECL2     062AECL2 LPAR   POR        No        No          Yes-POR

    On the IOCDS List, all applicable IOCDSs of the selected CPCs are displayed and arranged in ascending order by IOCDS names (starting, for example, with A0-IOCDSs, A1-IOCDSs). This list enables you to apply the IOCDS functions as group actions against one or several IOCDSs for all selected processors.

    The data displayed is retrieved directly from the support elements. If, however, the support element does not answer, HCD displays the data saved in the IODF and issues a message accordingly.

    A production IODF will be updated with data retrieved from the support element if discrepancies between that data and the stored IODF data are detected. A work IODF will remain unchanged.

    The Type field contains one of the following types of power-on reset modes to be used with the I/O configuration defined in the IOCDS: S/370, ESA/390, or LPAR.

    The Status field indicates the status of the IOCDS:

    Alternate
    not to be used at the next POR
    POR
    to be used at the next POR
    Invalid
    IOCDS is opened for update

    The Token Match-IOCDS/HSA field indicates whether the IOCDS token matches the current HSA token. If Yes is shown, it means that the IOCDS has been built by HCD, and that it matches the current I/O configuration - either because this IOCDS was used for the last POR, or the matching configuration has been activated dynamically.

    The Token Match-IOCDS/Proc. field indicates whether the IOCDS token matches the processor token in the IODF, currently used in the HCD dialog. If Yes is shown, the IOCDS has been built from the IODF currently used in the HCD dialog.

  3. On the IOCDS List, you can select the following actions from the context menu:
    • Use the Update IOCDS action (or action code  u ) to build or update the selected IOCDSs with the I/O configuration data from the currently accessed production IODF. See step 4 on how to proceed.
    • Use the Switch IOCDS action (or action code s) to mark an IOCDS as the IOCDS that is used for the next POR. The Status field will be set accordingly.

      You can only switch to an IOCDS that has an IOCDS/HSA token match or to an IOCDS of a processor that is not activated ('POR-required' status).

    • Use the Enable write protection or Disable write protection action (or action codes e and w) to allow or prohibit updating the selected IOCDSs of the designated CPCs. The Write Protect field will be set accordingly.

    Use the F20=Right key to move the screen to the right to see information such as date and time of the last IOCDS update and the IOCDS configuration token.

  4. If you select the Update IOCDS action, HCD displays the Build IOCDSs dialog.
    *------------------------------- Build IOCDSs ------------------------------*
    |                                                                  Row 1 of 1 |
    | Command ===> ___________________________________________ Scroll ===> PAGE   |
    |                                                                             |
    | Specify or revise the following values.                                     |
    |                                                                             |
    | IODF name . . . . . . . . . : 'SYS1.IODF01'                                 |
    |                                                                             |
    | Title1 . ________________________________________________________________   |
    | Title2 : SYS1.IODF01 - 2011-02-24 09:40                                     |
    |                                                                             |
    |                            Write IOCDS in                                   |
    | IOCDS        Switch IOCDS  preparation of upgrade                           |
    | A1.DAN2      No            No                                               |
    | ***************************** Bottom of data ****************************** |
    |                                                                             |
    |  F1=Help        F2=Split       F3=Exit        F5=Reset       F7=Backward    |
    |  F8=Forward     F9=Swap       F12=Cancel     F22=Command                    |
    *-----------------------------------------------------------------------------*

    On this panel you can:

    • Enter identification information you want to be written on the first header line of the IOCP input data set in the Title1 field.
    • Specify the Switch IOCDS option, if you want to make this IOCDS the active one for the next power-on reset (POR).
    • Specify whether to Write IOCDS in preparation of upgrade. This specifies whether an IOCDS is to be written regardless of processor type. This is useful to prepare for a processor upgrade.

      If Yes is specified, an IOCDS for the selected processor is written regardless of the processor type. For a list of processors that support writing an IOCDS, in preparation for a processor upgrade, or for which such an IOCDS can be written, see Supported Hardware Report.

      Note:
      If, as a result of a processor upgrade, an IOCDS download is not possible you can, after having built the production IODF, create an IOCP input data set that can be used with the stand-alone IOCP to generate an IOCDS for use with POR.
  5. After pressing the Enter key on the Build IOCDSs panel, the Job Statement Information panel is displayed. Specify the information for the batch job that HCD generates to build the IOCDSs.

    The recommended region size is 2 MBytes more than the IOCP needs. For the region size required by IOCP, refer to the IOCP User's Guide for your processor.

Go to the previous page Go to the next page




Copyright IBM Corporation 1990, 2014