VM66240: IOCP UPDATE

Obtain the fix for this APAR.

APAR status

• Closed as new function.

Error description

• IOCP New Function
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: IOCP users requiring support for the         *
  *                 D/T8561 IBM z15 model T01 and LinuxONE III   *
  *                 model LT1 servers and D/T8562 IBM z15 model  *
  *                 T02 and LinuxONE III model LT2 servers.      *
  ****************************************************************
  * PROBLEM DESCRIPTION: IOCP New Function                       *
  ****************************************************************
  * RECOMMENDATION: APPLY PTF                                    *
  ****************************************************************
  This PTF introduces a new release of ICP IOCP and is
  VERSION 5 RELEASE 5 LEVEL 0 (5.5.0) of the program.  ICP IOCP
  supports the 8561 z15 model T01 and LinuxONE III model LT1
  servers and the 8562 z15 model T02 and LinuxONE III model LT2
  servers.
  

Problem conclusion

Temporary fix

• FOR RELEASE ES-CMS-640-BASE :
  PREREQ: VM66179
  CO-REQ: NONE
  IF-REQ: NONE
  FOR RELEASE ES-CMS-710-BASE :
  PREREQ: VM66179
  CO-REQ: NONE
  IF-REQ: NONE
  

Comments

• *
  ICP IOCP VERSION 5 RELEASE 5 LEVEL 0 (5.5.0) provides the
  following support:
    - The 8561 Models (LT1 and T01) are supported with
      SYSTEM=(8561,1).  IOCP ignores the MAXDEV keyword on the
      RESOURCE statement and reserves the maximum number of
      devices for this model.  Also, IOCP reserves the maximum
      number of channel subsystems (CSSs) and logical partitions
      for these models.
    - The 8562 Models (LT2 and T02) are supported with
      SYSTEM=(8562,1).  IOCP ignores the MAXDEV keyword on the
      RESOURCE statement and reserves the maximum number of
      devices for this model.  Also, IOCP reserves the maximum
      number of channel subsystems (CSSs) and logical partitions
      for these models.
    - IOCP continues to use a variable amount of storage based
      on the type of IOCDS it is processing.  IOCP requires 213MB
      for the 8561 central processor complex (CPC) and 85MB for
      the 8562 CPC.
    - IOCP allows a group of FIDs to be defined with a single
      FUNCTION statement.  You specify a starting FID number and
      a count with the FID keyword of the FUNCTION statement.
      The following applies:
      + Each FID defined by the FID keyword has the same type,
        PCHID or VCHID, port, PNETIDs, and logical partitions.
      + The FID, VF, and, if applicable, UID values are
        incremented for each subsequent FID.
      + None of the FIDs can cause an error in the
        configuration (e.g. a duplicate FID number); otherwise,
        IOCP prevents the definition.
    - Any IOCDS written for a 8561 or 8562 CPC contains the
      Licensed Machine Code (LMC) partition called MCS_1 (also
      known as a firmware partition).  The LMC partition MCS_1
      can be used on a stand-alone coupling facility (CF) CPC so
      that dynamic I/O changes can be made to the CF from another
      CPC that is running the Hardware Configuration Definition
      (HCD).
    - For the 8561 T01 and 8562 T02 models:
      + A maximum of 384 coupling channel paths (TYPE=CL5, CS5,
        and ICP) are allowed.  A logical partition continues to
        have a maximum of 128 coupling channel paths.
      + A maximum of 64 internal coupling channel paths (TYPE=ICP)
        can be defined.
  *
  *
  Documentation Changes:
  There is a new publication "Input/Output Configuration
  Program User's Guide for ICP IOCP" which has order number
  SB10-7172-04.  The publication is available using Resource
  Link at http://www.ibm.com/servers/resourcelink by selecting
  section:
  Library > z15 T01 or T02
  Library > LinuxONE III LT1 or LT2
  *
  EC (Engineering Change) Information:
  This PTF level of ICP IOCP contains support for IBM z15 and
  LinuxONE III central processor complexes (CPCs).
  See Usage Notes for further information.
  *
  Information on equivalent STAND-ALONE IOCP, z/OS IOCP, z/VM
  IOCP, and z/VSE IOCP follows:
  *
  *
    - Equivalent STAND-ALONE IOCP for ICP IOCP version 5.5.0 is
      in the listed EC's.  The EC's listed are the first levels
      shipped with this release of IOCP.
          EC       MACHINE TYPE
        P46661         8561
        P46661         8562
  *
    - Equivalent z/OS, z/VM, and VSE IOCP is shipped via the
      listed APARs.
        OPERATING SYSTEM       APAR
             z/OS            OA56761
             z/VM            VM66240
             z/VSE           DY47809
  *
  *
  The EC level of the CPC can be determined from the Hardware
  Management Console or Support Element by doing the following:
    1. From Navigation pane, select 'Systems Management' on
       HMC or 'System Management' on Support Element.
    2. Select 'Systems' on HMC.
    3. Select the CPC you are interested in.
    4. Expand the 'Change Management' tasks area.
    5. Open 'System Information' in the 'Change Management'
       tasks area and look for Description 'SE Framework'
       to identify the appropriate EC level.
  *
  The STAND-ALONE IOCP version and release can be determined by
  looking at the header lines of the IOCP reports produced by
  STAND-ALONE IOCP.  The STAND-ALONE IOCP version and release can
  also be found in IOCP message ICP073I in an I/O Configuration
  Source file that was processed by STAND-ALONE IOCP.  The
  STAND-ALONE IOCP version and release can also be determined
  from the Hardware Management Console or Support Element by
  doing the following (begin with step 6 for the Support Element
  Console):
    1. Select 'Systems Management' from Navigation pane.
    2. Select 'Systems'.
    3. Select the CPC you are interested in.
    4. Expand the 'Recovery' tasks area.
    5. Open 'Single Object Operations' in the 'Recovery'
       tasks area to connect to the Support Element.
    6. Select 'System Management' from Navigation pane.
    7. Select the CPC or an activated partition.  (Note that
       an activated partition is required to write an IOCDS.)
    8. Expand 'Configuration' from the tasks area.
    9. Open 'Input/output (I/O) Configuration' in the
       'Configuration' tasks area.
    10. Select 'View' pull-down.
    11. Select 'Configuration Program Level'.
  *
  Usage Notes:
  1. If you are currently using a release of ICP IOCP and you do
     not plan on upgrading to the listed EC level, you can
     still install this PTF and replace your existing ICP IOCP.
     The 2084, 2086, 2094, 2096, 2097, 2098, 2817, 2818,
     2827, 2828, 2964, 2965, 3906, and 3907 models can power-on
     reset with an IOCDS written by the ICP IOCP shipped by this
     PTF.  Also, the 2084, 2086, 2094, 2096, 2097, 2098, 2817,
     2818, 2827, 2828, 2964, 2965, 3906, and 3907 models can still
     power-on reset with an IOCDS that was written by your
     previous release of ICP IOCP.  There is no requirement that
     you write an IOCDS with the ICP IOCP shipped by this PTF and
     perform a power-on reset after the PTF has been installed.
  2. Any IOCDS previously created by an ICP version of IOCP
     (z/OS, VM, VSE, or STAND-ALONE) can be reported on by the
     ICP version of IOCP shipped by this PTF.
  3. Any IOCDS previously created by another version of IOCP
     (e.g. IYP IOCP) cannot be reported on by the ICP version of
     IOCP shipped by this PTF or by the STAND-ALONE equivalent
     version of the ICP IOCP program.  (For HCD users, HCD manages
     the correlation of IOCP versions to CPC model for you.)
  4. If you are upgrading to a 8561 or 8562 model, IBM recommends
     writing a 8561 or 8562 IOCDS to your current 2964, 2965,
     3906, or 3907 CPC as described here.
     Use IOCP execution parameter CHECKCPC=NO or HCD option
     'Write IOCDS in preparation of upgrade'.  The IOCDS will be
     unusable until your CPC has been upgraded to a 8561 or 8562.
     Inform the installing service representative that you have
     pre-written a 8561 or 8562 IOCDS and which IOCDS should be
     selected after the upgrade.
  5. Although IOCP provides support for IXP IOCP (3090, 9021,
     9121, and 9221 only), IZP IOCP (2003, 3000, 7060, 9021,
     9121, 9672, and 9674 only), and IYP IOCP (2064 and 2066),
     these programs are not affected by this PTF.  Also, the
     IOP program option for IOP IOCP (3090 only) is no longer
     supported and will be reused at some point in the future
     for a new processor.
  
  KEYWORDS: R8561/K R8562/K
  

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

  UM35526 UM35527

Modules/Macros

• DMSICP   ICPCARDF ICPCARDS ICPCARDU ICPCARDW ICPCARDX ICPCARDY
  ICPCARDZ ICPCFRST ICPCGET  ICPCGNDS ICPCINIT ICPCIOCP ICPCIOCU
  ICPCIODV ICPCMSG  ICPCPCHK ICPCPUT  ICPCRDDS ICPCRPT  ICPCRPTA
  ICPCRPTF ICPCRPTX ICPCRTNS ICPCRTNX ICPCWTDS ICPPCNTL ICPPVM
  

Fix information

• Fixed component name

  VM CMS

• Fixed component ID

  568411201

Applicable component levels

• R640 PSY UM35526

     UP20/12/16 P 2001

• R710 PSY UM35527

     UP19/09/13 P 2001

Fix is available

• Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.