IBM Support

VM66827: Z/VM 7.4 CMS: HARDWARE SUPPORT - FEATURE 02 FIX 00

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as new function.

Error description

  • IOCP Update
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: IOCP users requiring support for the         *
    *                 9175 IBM z17 model ME1 server and the IBM    *
    *                 LinuxONE Emperor 5 model ML1.                *
    ****************************************************************
    * PROBLEM DESCRIPTION: IOCP New Function                       *
    ****************************************************************
    * RECOMMENDATION: APPLY PTF                                    *
    ****************************************************************
    This PTF introduces a new release of ICP IOCP and is
    VERSION 7 RELEASE 1 LEVEL 0 (7.1.0) of the program.  ICP IOCP
    supports the IBM z17 9175 model ME1 and the IBM LinuxONE
    Emperor 5 model ML1.
    

Problem conclusion

Temporary fix

  • FOR RELEASE ES-CMS-740-BASE :
    PREREQ: VM66834
    CO-REQ: NONE
    IF-REQ: NONE
    

Comments

  • PROBLEM CONCLUSION:
    *
    ICP IOCP VERSION 7 RELEASE 1 LEVEL 0 (7.1.0) provides the
    following support:
      - The 9175 models (ME1 and ML1) are supported with
        SYSTEM=(9175,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 this model.
      - IOCP continues to use a variable amount of storage based
        on the type of IOCDS it is processing.  IOCP requires 215MB
        for the 9175 central processor complex (CPC).
      - For 9175 models:
        + The number of PCIe function FIDs is increased such that
          the maximum FID value is 4FFF hexadecimal.
        + New CHPID TYPE=CL6 for a Coupling Express3 LR 25Gb
          adapter.  Type CL6 channel paths can only connect to other
          CL6 channel paths.  The current CL5 CHPID type is
          associated with 10Gb coupling adapters and can only
          connect to other CL5 channel paths.  CL6 channel paths
          are defined the same as CL5 channel paths and have the
          same rules and maximums.
        + New CHPID TYPE=OSH for a Network Express adapter which
          supports the Enhanced Queued Direct I/O (EQDIO)
          architecture.  An OSH CHPID can be enabled for link
          aggregation by specifying CHPARM=02 for its definition.
        + New FUNCTION TYPE=NETH for a Network Express adapter.
        + A TYPE=OSH CHPID and a TYPE=NETH function can co-exist
          on the same PCHID port of a Network Express adapter.
        + New keyword FIDPARM on FUNCTION statement allows a NETH
          function to operate in promiscuous mode (e.g. FIDPARM=01).
        + New FUNCTION TYPE=NETD for a Network Express adapter.
        + New FUNCTION TYPE=PAIA for the IBM Spyre(TM) Accelerator.
        + New keyword PF on FUNCTION statement which defines a
          function ID (FID) as a physical function.  The PF is
          assigned to a logical partition and allows an operating
          system to control the adapter port associated with its
          PCHID.  The NETD and PAIA function types require the
          definition of a FID as a PF.
    
      - The 9175 CPC does not support the mixing of FC and FCP CHPID
        types on a FICON adapter with or without the MIXTYPE
        keyword.  Also, networking adapters do not support the
        definition of both OSC and OSD CHPIDs on the same adapter
        but IOCP does not prevent this except for the 9175 CPC.
        Defining a mix of either of these channel path types results
        in the following error message:
    
        ICP374I  INVALID MIX OF CHPID TYPES FOR PCHIDS xxx AND yyy
    
        To correct the error, change one of the channel path types
        so that the PCHIDs have the same channel path type.
    *
    *
    Documentation Changes:
    There is a new publication "Input/Output Configuration
    Program User's Guide for ICP IOCP" which has order number
    SB10-7183-00.  The publication is available at
    https://www.ibm.com/docs/en/systems-hardware/zsystems
    by selecting the appropriate IBM Z model and then
    section Library Overview.
    *
    EC (Engineering Change) Information:
    This PTF level of ICP IOCP contains support for IBM z17
    central processor complexes (CPCs).
    See Usage Notes for further information.
    *
    Information on equivalent STAND-ALONE IOCP, z/OS IOCP, and z/VM
    IOCP follows:
    *
    *
      - Equivalent STAND-ALONE IOCP for ICP IOCP version 7.1.0 is
        in the listed EC's.  The EC's listed are the first levels
        shipped with this release of IOCP.
              EC      MACHINE TYPE
          P30924.001      9175
    *
      - Equivalent z/OS and z/VM IOCP is shipped via the
        listed APARs.
          OPERATING SYSTEM       APAR
               z/OS            OA65190
               z/VM 7.3        VM66741
               z/VM 7.4        VM66827
    *
    *
    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 'Input/Output
         Configuration Program' 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 2827, 2828, 2964, 2965, 3906, 3907, 8561, 8562, 3931, and
       3932 models can power-on reset with an IOCDS written by the
       ICP IOCP shipped by this PTF.  Also, the 2827, 2828, 2964,
       2965, 3906, 3907, 8561, 8562, 3931, and 3932 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 9175 model, you MUST write a 9175
       IOCDS to your current 8561 or 3931 CPC as described here or
       write a 9175 IOCDS after the upgrade is completed.  Prior
       to the upgrade, 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
    
    KEYWORDS: R9175/K D/T9175 SPYRE/K
    

APAR Information

  • APAR number

    VM66827

  • Reported component name

    VM CMS

  • Reported component ID

    568411201

  • Reported release

    740

  • Status

    CLOSED UR1

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    YesSpecatt / New Function / Xsystem

  • Submitted date

    2025-02-21

  • Closed date

    2025-04-08

  • Last modified date

    2025-09-30

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

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

    UM90520

Modules/Macros

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

Publications Referenced
SB10718300    

Fix information

  • Fixed component name

    VM CMS

  • Fixed component ID

    568411201

Applicable component levels

  • R740 PSY UM90520

       UP25/04/08 P 2502

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.

[{"Business Unit":{"code":"BU011","label":"Systems - zSystems software"},"Product":{"code":"SG27M"},"Platform":[{"code":"PF054","label":"z Systems"}],"Version":"740","Line of Business":{"code":"LOB16","label":"Mainframe HW"}}]

Document Information

Modified date:
30 September 2025