A fix is available
APAR status
Closed as new function.
Error description
IOCP Update
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: IOCP users requiring support for the * * D/T2965 IBM z13s and for the * * D/T2964 IBM z13. * **************************************************************** * PROBLEM DESCRIPTION: IOCP New Function * **************************************************************** * RECOMMENDATION: APPLY PTF * **************************************************************** This PTF introduces a new release of ICP IOCP and is VERSION 5 RELEASE 3 LEVEL 0 (5.3.0) of the program. ICP IOCP supports the 2965 z13s and the 2964 z13.
Problem conclusion
Temporary fix
FOR RELEASE ES-CMS-630-BASE : PREREQ: VM65817 CO-REQ: NONE IF-REQ: NONE FOR RELEASE ES-CMS-640-BASE : PREREQ: NONE CO-REQ: NONE IF-REQ: NONE
Comments
* ICP IOCP VERSION 5 RELEASE 3 LEVEL 0 (5.3.0) provides the following support: - Support for Coupling Express LR channel paths (TYPE=CL5). The 2965 and 2964 central processor complexes (CPCs) support CL5 channel paths at the EC levels listed below. - A maximum of 128 coupling channel paths (TYPE=CIB, CL5, CS5, and ICP) are allowed to access a logical partition on 2965 and 2964 CPCs. These CPCs continue to support a maximum of 256 coupling channel paths for the CPC. * * Documentation Changes: There will be a new publication "Input/Output Configuration Program User's Guide for ICP IOCP" which has order number SB10-7172-00. The publication is available using Resource Link at http://www.ibm.com/servers/resourcelink by selecting section: Library > z13 Library > z13s * EC (Engineering Change) Information: This PTF level of ICP IOCP contains support for IBM z13s and IBM z13 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.3.0 is in the listed EC's (with MCLs). The EC's listed are the first levels shipped with this release of IOCP. EC MACHINE TYPE P00339.314 2964 (Note 1) P00339.314 2965 (Note 1) * Note 1: This is EC P00339 with LIC patch MCL314 installed. Your CPC must also have EC P00339.328 installed for the CPC to support CL5 channels. See the APAR record for the updated information on or before September 13, 2017. * - Equivalent z/OS, z/VM, and z/VSE IOCP is shipped via the listed APARs. OPERATING SYSTEM APAR z/OS OA51111 z/VM VM65880 z/VSE N/A (see DY47686, DY47687) * * 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 MCL 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, and 2965 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, and 2965 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. If you have a 2964 or 2965 model and install the listed MCL level, IBM recommends installing this PTF. 3. 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. 4. 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.) 5. If you are upgrading to a 2964 or 2965 model, you must power-on reset with an IOCDS written for the 2964 or 2965. Following an upgrade, you cannot power-on reset with an IOCDS that was written for the prior CPC unless the 2964 or 2965 IOCDS was written in preparation of an upgrade. 6. 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.
APAR Information
APAR number
VM65880
Reported component name
VM CMS
Reported component ID
568411201
Reported release
630
Status
CLOSED UR1
PE
NoPE
HIPER
NoHIPER
Special Attention
YesSpecatt / New Function / Xsystem
Submitted date
2016-08-16
Closed date
2017-07-17
Last modified date
2017-11-24
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UM35163 UM35164
Modules/Macros
DMSICP ICPCARDF ICPCARDS ICPCARDU ICPCARDW ICPCARDX ICPCARDY ICPCARDZ ICPCFRST ICPCGET ICPCGNDS ICPCINIT ICPCIOCP ICPCIOCU ICPCIODV ICPCMSG ICPCPCHK ICPCPUT ICPCRDDS ICPCRPT ICPCRPTX ICPCRTNS ICPCRTNX ICPCWTDS ICPPCNTL ICPPVM
SB10717200 |
Fix information
Fixed component name
VM CMS
Fixed component ID
568411201
Applicable component levels
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":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG27M","label":"APARs - z\/VM environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"630","Edition":"","Line of Business":{"code":"LOB16","label":"Mainframe HW"}}]
Document Information
Modified date:
24 November 2017