A fix is available
APAR status
Closed as unreproducible in next release.
Error description
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: IOCP users requiring support for the * * D/T3906 IBM z14 or IBM LinuxONE Emperor II, * * or D/T3907 IBM z14 or IBM LinuxONE * * Rockhopper II. * **************************************************************** * PROBLEM DESCRIPTION: IOCP New Function * **************************************************************** * RECOMMENDATION: * **************************************************************** This PTF introduces a new release of ICP IOCP and is VERSION 5 RELEASE 4 LEVEL 1 (5.4.1) of the program. ICP IOCP supports the 3906 z14 and Emperor II and 3907 z14 and Rockhopper II.
Problem conclusion
* ICP IOCP VERSION 5 RELEASE 4 LEVEL 1 (5.4.1) provides the following support: - New FUNCTION TYPE=NVME for the IBM Adapter for NVMe. The 3906 and 3907 central processor complexes (CPCs) support NVME functions at the EC levels listed below. - The 3906 and 3907 CPCs introduce a Licensed Machine Code (LMC) partition called MCS_1 (also known as a firmware partition). The LMC partition MCS_1 can be defined 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). **NOTE** The stand-alone CF must be power-on reset with an IOCDS that contains the MCS_1 partition before dynamic I/O changes can be made to the stand-alone CF. * * Documentation Changes: There is a new publication "Input/Output Configuration Program User's Guide for ICP IOCP" which has order number SB10-7172-02. The publication is available using Resource Link at http://www.ibm.com/servers/resourcelink by selecting section: Library > z14 Library > z14 ZR1 * EC (Engineering Change) Information: This PTF level of ICP IOCP contains support for IBM z14, LinuxONE Emperor II, and LinuxONE Rockhopper II 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.4.1 has the listed EC's. The EC's listed are the first levels shipped with this release of IOCP. EC MACHINE TYPE P41473 3906 P41473 3907 * - Equivalent z/OS, z/VM, and VSE IOCP is shipped via the listed APARs. OPERATING SYSTEM APAR z/OS OA55404 z/VM VM66179 z/VSE DY47799 / DY47800 / DY47801 * * 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 3906 model, you may be required to power-on reset with an IOCDS written for the 3906. Following an upgrade from a 2964 model, you can power-on reset with an IOCDS that was written for the 2964. But when upgrading from a 2827 CPC, you cannot power-on reset with an IOCDS that was written to the 2827 unless the IOCDS was a 3906 IOCDS written in preparation of the upgrade. 5. If you are upgrading to a 3907 model from a 2965 model, you can power-on reset with an IOCDS that was written for the 2965. You do not have to write an IOCDS for the 3907 but you will not be able to use any new features available only on the 3907 without a new IOCDS. 6. If you are upgrading to a 3906 or 3907 model, IBM recommends writing an IOCDS to your current 2964, 2965, or 2827 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 3906 or 3907. Inform the installing service representative that you have pre-written a 3906 or 3907 IOCDS and which IOCDS should be selected after the upgrade. 7. 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.
Temporary fix
Comments
KEYWORDS: R3906/K R3907/K ×**** PE20/10/01 FIX IN ERROR. SEE APAR OA60242 FOR DESCRIPTION
APAR Information
APAR number
OA55404
Reported component name
IOCP COMMON
Reported component ID
566529101
Reported release
104
Status
CLOSED UR1
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2018-04-26
Closed date
2018-09-12
Last modified date
2020-10-01
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UA97193
Modules/Macros
ICPCARDF ICPCARDS ICPCARDU ICPCARDW ICPCARDX ICPCARDY ICPCARDZ ICPCFRST ICPCIOCP ICPCIODV ICPCMSG ICPCPUT ICPCRDDS ICPCRPT ICPCRPTA ICPCRPTF ICPCRPTX ICPCRTNS ICPCRTNX ICPPCNTL
SB10717202 |
Fix information
Fixed component name
IOCP COMMON
Fixed component ID
566529101
Applicable component levels
R104 PSY UA97193
UP18/10/02 P F810
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":"SG19M","label":"APARs - z\/OS environment"},"Platform":[{"code":"PF054","label":"z\/OS"}],"Version":"104"}]
Document Information
Modified date:
02 October 2020