A fix is available
APAR status
Closed as new function.
Error description
New function: exploitation support
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: VM HCD users exploiting zEC12 GA2 and * * zBC12 processors. * **************************************************************** * PROBLEM DESCRIPTION: Please see Problem Summary. * **************************************************************** * RECOMMENDATION: * **************************************************************** With z/VM HCD 5.4 and z/VM HCD 6.2 users can neither define nor activate zEC12 GA2 and zBC12 processors and their new capabilites. An IODF therefore cannot be shared between zVM and zOS or different CECs or LPARs of a CEC, with the need to tolerate or exploit such definitions. If z/VM HCD 6.2 tries to write an IOCDS and the operation returns with IOCP return code RC2, the IOCP listing is no longer available to check what messages are generated by IOCP.
Problem conclusion
Temporary fix
Comments
- HCD z/VM 6.2: This APAR offers full exploitation support for processors of type 2827 ( D/T2827 ) and 2828 ( D/T2828 ). For a list of supported processor types/models and their capabilities see the 'supported hardware report' in HCD. To support PCIe functions, HCD has added the FUNCTION keyword to its config statement, which can be migrated into an IODF. A PCIe function is specified with the FUNCTION statement. The FUNCTION statement representing a PCIe function contains the following keywords: - FID Identifies the PCIe function within the processor configuration (mandatory, up to 3 HEX chars, the valid range is 000-0FF) - UNIT Identifies the PCIe function type (optional). HCD uses the default PCIe type RoCE (other supported tpye is ZEDC-EXPRESS) - PCHID Identifies the PCIe adapter card which provides the specified function by specifying the slot of the card in the I/O drawer. - VF Identifies the PCIe virtual function number (optional, up to two decimal digits, only valid for ZEDC-EXPRESS) - PNETID Identifies the physical network IDs (only valid for ROCE) - PART Specifies the access and candidate lists of partitions entitled to use the PCIe function. (only one LPAR is allowed in the access list) - DESC Specifies a description of the PCIe function (optional). The UNIT and DESC keyword are unknown to IOCP and have to be specified with *$HCD$, if used to call IOCP The CHPID statement has been enhanced to support the new optional operand PNETID only applicable for CHPID type OSD and IQD. IQD only accepts one PNETID. If the target processor type does not support PNETID values, the CHPID statement will be processed with the PNETID value being ignored. - HCD will not automatically adapt different PNETID specifications for the same PCHID value on multiple PCIe functions. Input statements have to be consistent; otherwise error message CBDG578I would be given when the production IODF is being built. Sample including the HCD internal keywords: FUNCTION FID=002,PART=((LP01),(LP03,LP04,LP12,LP22)), PNETID=(NET1,NET2,N3,),PCHID=002 *$HCDC$ UNIT=ROCE *$HCDC$ DESC='myDescription' FUNCTION FID=005,VF=1,PART=((LP14),(LP01)),PCHID=105 *$HCDC$ UNIT=ZEDC-EXPRESS *$HCDC$ DESC='myDescription' CHPID PATH=(CSS(0),11),PARTITION=((LP01),(LP04),REC), PCHID=041,PNETID=(,NET11,NET2,),TYPE=OSD *$HCDC$ DESC='myDescription' In addition, HCD provides the two new reports as part of the 'Channel Subsystem Summary Report': - The 'PCIe Function Summary Report' displays the partitions in the access and candidate lists which are entitled to access the available PCIe functions. - The PCHID Summary Report as part of the CSS Summary Report lists all defined channel paths and PCIe functions grouped by their defined PCHID values or, as applicable, by their HCA adapter or port IDs. Also the compare reports will allow to compare PCIe changes. It is printed as part of the IODF compare reports, which can be limited to the 'PCIe Compare Report' by the limit string CF. e.g. PARM= COMPARE,AB,CL,CF,PROC2,LPAR1,PROC2,LPAR1' If writing an IOCDS and the operation returns with IOCP return code 2, the IOCP listing is now available as file @@HCDIN LISTING. The listing can be used to check what reason caused the return code. - z/VM 5.4 HCD Exploitation support for the new processor type/models, but only toleration support for PCIe functions and PNETID attributes. Three scenarios need to be distinguished: 1. A work or production IODF with zEC12 GA2 or zBC12 processors does NOT contain either - PCIe functions or - CHPIDs with PNETID attributes: full support is available, including updates of a work IODF, generation of reports, build production IODF, and all kinds of dynamic activates. For a list of supported processor types and their capabilities see the 'supported hardware report' in HCD. 2. A production IODF with zEC12 GA2 or zBC12 processors contains - PCIe functions and / or - CHPIDs with PNETID attributes for the processor to be activated (in the active IODF or in the target IODF, or both). It is possible to perform a software-only activate or software activate with hardware validation. A warning message CBDG593I (MSGCBDG593) will be issued: "Processor @1 has PCIe functions or CHPIDs with PNET ID which are unknown to the HCD version or OS version. Both will be ignored.". A full dynamic activate is not possible. If it is attempted, message CBDG592I (MSGCBDG592) is given: "Processor @1 contains PCIe functions or CHPIDs with PNET ID, unsupported by the current HCD/OS version. Action is not possible.". When generating an IOCP deck or issuing several reports, the unsupported objects are ignored and CBDG593I is issued. 3. A work IODF with zEC12 GA2 or zBC12 processors contains - PCIe functions and / or - CHPIDs with PNETID attributes for the processor to be activated. It is not possible to update the IODF or to build a production IODF. In both cases, message CBDG592 is issued (MSGCBDG592). This IODF must be maintained and activated on a z/VM 6.2 with VM65239 or z/OS V2R1 HCD system with OA39234 installed.
APAR Information
APAR number
VM65239
Reported component name
HCD/HCM
Reported component ID
568411219
Reported release
540
Status
CLOSED UR1
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2012-10-09
Closed date
2013-08-20
Last modified date
2015-02-16
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UM34091 UM34092
Modules/Macros
CBDA001 CBDA001I CBDA037 CBDA037I CBDA099I CBDA121 CBDA121I CBDA159 CBDA159I CBDA196 CBDA196I CBDA241 CBDA241I CBDA270 CBDA270I CBDA374 CBDA374I CBDA425 CBDA425I CBDA435 CBDA435I CBDA449 CBDA449I CBDA599 CBDA599I CBDA605 CBDA605I CBDA630 CBDA630I CBDA691 CBDA691I CBDA698 CBDA698I CBDA821 CBDA821I CBDA848 CBDA848I CBDA854 CBDA854I CBDA880 CBDA880I CBDA901 CBDA901I CBDA902 CBDA902I CBDA903 CBDA903I CBDA904 CBDA904I CBDA950 CBDA950I CBDBLLLB CBDD816 CBDD816I CBDD824 CBDD824I CBDEM00A CBDEM00D CBDEM00G CBDG180 CBDG180I CBDG300 CBDG300I CBDG302 CBDG302I CBDG303 CBDG303I CBDG304 CBDMVPR0 CBDMVSW0 CBDMXSCH CBDMYCCB CBDMYDCC CBDMYVAL CBDMZADD CBDMZCHK CBDMZCON CBDMZCS CBDMZDEC CBDMZDEL CBDMZEP CBDMZFS CBDMZMIG CBDMZMIS CBDMZRCM CBDMZRET CBDMZUPD CBDPV020 CBDPV021 CBDP0247 CBDP0248 CBDSCOMP CBDSREP CBDZPARS
Fix information
Fixed component name
HCD/HCM
Fixed component ID
568411219
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":"540","Edition":"","Line of Business":{"code":"LOB16","label":"Mainframe HW"}}]
Document Information
Modified date:
16 February 2015