A fix is available
APAR status
Closed as new function.
Error description
New Function.
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: * **************************************************************** This PTF introduces a new release of ICP IOCP and is VERSION 5 RELEASE 2 LEVEL 0 (5.2.0) of the program. ICP IOCP supports the 2965 z13s and the 2964 z13.
Problem conclusion
ICP IOCP VERSION 5 RELEASE 2 LEVEL 0 (5.2.0) provides the following support: - The 2965 Models (L10, L20, N10, N20) are supported with SYSTEM=(2965,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 85M for the 2965 CPC. - New 2964 Models (L30, L63, L96, LC9, LE1) are supported with SYSTEM=(2964,1). - For 2964 and 2965 models: + New FUNCTION TYPE=ISM for a SMC-L virtual network connection (internal). + New FUNCTION TYPE=RCE for a Regional Crypto Enablement adapter.
Temporary fix
Comments
Documentation Changes: There is a new publication "Input/Output Configuration Program User's Guide for ICP IOCP" which has order number SB10-7163-01. 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.2.0 is in the listed EC's. The EC's listed are the first levels shipped with this release of IOCP. EC MACHINE TYPE P00339 2964 P00339 2965 * - Equivalent z/OS, z/VM, and VSE IOCP is shipped via the listed APARs. OPERATING SYSTEM APAR z/OS OA47938 z/VM VM65736 z/VSE DY47635 / DY47641 * * 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 one of the listed EC's, you can still install this PTF and replace your existing ICP IOCP. The 2965 model must power-on reset with an IOCDS written by the ICP IOCP shipped by this PTF. The 2084, 2086, 2094, 2096, 2097, 2098, 2817, 2818, 2827, 2828, and 2964 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, and 2964 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 2965 model, you must power-on reset with an IOCDS written for the 2965. Following an upgrade, you cannot power-on reset with an IOCDS that was written for the prior CPC unless the 2965 IOCDS was written in preparation of an upgrade. 5. If you are upgrading to a 2965 model, IBM recommends writing an IOCDS to your current 2828 or 2818 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 2965. Inform the installing service representative that you have pre-written a 2965 IOCDS and which IOCDS should be selected after the upgrade. 6. Although FMID HIO1104 also includes support for IXPIOCP (3090, 9021, 9121, and 9221 only), IZPIOCP (2003, 3000, 7060, 9021, 9121, 9672, and 9674 only), and IYPIOCP (2064 and 2066), these programs are not affected by this PTF. Program IOPIOCP (3090 only) will be reused at some point in the future for a new processor.
APAR Information
APAR number
DY47635
Reported component name
VSE/AF IOCP
Reported component ID
5686CF909
Reported release
51C
Status
CLOSED UR1
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2015-12-07
Closed date
2016-01-13
Last modified date
2016-06-30
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UD54155 UD54156 DY47641
Modules/Macros
ICPCARDF ICPCARDS ICPCARDU ICPCARDW ICPCARDX ICPCARDY ICPCARDZ ICPCFRST ICPCGET ICPCGNDS ICPCINIT ICPCIOCP ICPCIOCU ICPCIODV ICPCMSG ICPCPCHK ICPCPUT ICPCRDDS ICPCRPT ICPCRPTX ICPCRTNS ICPCRTNX ICPCWTDS ICPPCNTL ICPPVSE VSEIOCP
| SB10716302 |
Fix information
Fixed component name
VSE/AF IOCP
Fixed component ID
5686CF909
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":"SG32M","label":"APARs - VSE\/ESA environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"51C","Edition":"","Line of Business":{"code":"","label":""}}]
Document Information
Modified date:
11 December 2020