IBM Support

VM66549: IBM z16 and LinuxONE Emperor 4 IOCP update D/T3931

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as new function.

Error description

  • IBM z16 and LinuxONE Emperor 4 IOCP update D/T3931
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: IOCP users requiring support for the         *
    *                 D/T3931 IBM z16 model A01 server and the     *
    *                 IBM LinuxONE Emperor 4 model LA1.            *
    ****************************************************************
    * PROBLEM DESCRIPTION: IOCP New Function                       *
    ****************************************************************
    * RECOMMENDATION: APPLY PTF                                    *
    ****************************************************************
    This PTF introduces a new release of ICP IOCP and is
    VERSION 6 RELEASE 1 LEVEL 1 (6.1.1) of the program.  ICP IOCP
    supports the IBM z16 3931 model A01 and IBM LinuxONE Emperor 4
    model LA1.
    

Problem conclusion

Temporary fix

  • FOR RELEASE ES-CMS-710-BASE :
    PREREQ: VM66461
    CO-REQ: NONE
    IF-REQ: NONE
    FOR RELEASE ES-CMS-720-BASE :
    PREREQ: VM66461
    CO-REQ: NONE
    IF-REQ: NONE
    

Comments

  • PROBLEM CONCLUSION:
    *
    ICP IOCP VERSION 6 RELEASE 1 LEVEL 1 (6.1.1) provides the
    following support:
      - The 3931 models (A01 and LA1) are supported with
        SYSTEM=(3931,1).
        IOCP ignores the MAXDEV keyword on the RESOURCE statement
        and reserves the maximum number of devices for these models.
        Also, IOCP reserves the maximum number of channel
        subsystems (CSSs) and logical partitions for these models.
      - IOCP must now be run in the z/CMS environment by issuing
        'IPL ZCMS'.  After you apply this APAR, z/CMS is required
        regardless of the machine on which you run IOCP.  If you
        run IOCP in the CMS environment, the following message
        results:
    
        DMSICP340E IOCP requires z/CMS to run - exiting. IPL ZCMS
                   and try again
    
      - IOCP continues to use a variable amount of storage based
        on the type of IOCDS it is processing.  IOCP requires 215MB
        for the 3931 central processor complex (CPC).
      - IOCP now supports virtual storage above the 2GB bar.
      - IOCP now accepts blank lines in its source input.
      - IOCP has dropped support for the following CPCs:
        2084, 2086, 2094, 2096, 2097, and 2098.
      - The 3931 CPC does not support the mixing of FC and FCP CHPID
        types on a FICON adapter with or without the MIXTYPE
        keyword.  Defining a mix of 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-7177-00.  The publication is available using Resource
    Link at http://www.ibm.com/servers/resourcelink by selecting
    section:
    Library > IBM z16 A01
    Library > LinuxONE Emperor 4 LA1
    *
    EC (Engineering Change) Information:
    This PTF level of ICP IOCP contains support for IBM z16
    and LinuxONE Emperor 4 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 6.1.1 is
        in the listed EC's.  The EC's listed are the first levels
        shipped with release 6.1.0 of IOCP which is equivalent to
        6.1.1.
            EC       MACHINE TYPE
          P30763         3931
    *
      - Equivalent z/OS, z/VM, and VSE IOCP is shipped via the
        listed APARs.
          OPERATING SYSTEM       APAR
               z/OS            OA60286  (6.1.0)
               z/VM            VM66549  (6.1.1)
               z/VSE           DY47850  (6.1.1)
    *
    *
    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 2817, 2818, 2827, 2828, 2964, 2965, 3906, 3907, 8561,
       and 8562 models can power-on reset with an IOCDS written by
       the ICP IOCP shipped by this PTF.  Also, the 2817, 2818,
       2827, 2828, 2964, 2965, 3906, 3907, 8561, and 8562 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 3931 model, you MUST write a 3931
       IOCDS to your current 3906 or 8561 CPC as described here or
       write a 3931 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 a 3931.
       Inform the installing service representative that you have
       pre-written a 3931 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: R3931/K
    

APAR Information

  • APAR number

    VM66549

  • Reported component name

    VM CMS

  • Reported component ID

    568411201

  • Reported release

    710

  • Status

    CLOSED UR1

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2021-06-23

  • Closed date

    2022-04-05

  • Last modified date

    2022-09-13

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

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

    UM35957 UM35958

Modules/Macros

  • DMSICP   DMSMES   DMSMESA  DMSMESB  DMS340E  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 ICPLIM   ICPPCNTL ICPPVM   IOCPLOAD
    

Publications Referenced
SB10717700    

Fix information

  • Fixed component name

    VM CMS

  • Fixed component ID

    568411201

Applicable component levels

  • R710 PSY UM35957

       UP22/04/05 I 1000

  • R720 PSY UM35958

       UP22/04/05 I 1000

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":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SG27M"},"Platform":[{"code":"PF054","label":"z Systems"}],"Version":"710","Line of Business":{"code":"LOB16","label":"Mainframe HW"}}]

Document Information

Modified date:
13 September 2022