This page provides details of what's new in HCM for z/OS V1R12.
With the I/O Autoconfiguration function, HCM lets you discover undefined FICON storage devices (DASD and tape) connected to the processor via a switch. According to user-defined policies or to HCD provided defaults, HCM can automatically define the control units and devices of discovered controllers. Users can either accept the proposed definitions without changes, or they can update the proposed definitions before committing them to the IODF.
Accordingly, HCM provides a wizard offering:
- dialogs to define autoconfiguration policies
- dialogs to discover and automatically define the FICON storage devices.
This function is only available on IBM® zEnterprise™ 196 (z196) processors.
Generation of a D/R site OS configuration
For exploitation in a GDPS environment with peer-to-peer remote copy (PPRC) controlled DASD devices, HCM provides a function to automatically generate the OS configuration of the disaster/recovery (D/R) site.
You can enable this function by:
- specifying the name of the D/R site OS configuration as an attribute of the primary site OS configuration
- indicating the DASD devices that are used by PPRC with a PPRC usage type.
The D/R site OS configuration is generated automatically during Build production I/O definition file processing as a copy of its primary site OS configuration, whereby DASD devices, which are specified with PPRC usage type DUPLEX, are defined to the D/R site OS configuration with a reversed OFFLINE parameter.
Support of the WWPN Prediction Tool
You can use HCM to generate a file containing FCP I/O configuration data of a selected processor. HCM can launch the WWPN Prediction Tool with this file as input in order to assign worldwide port names to the FCP device paths.
Support of over-defined CIB channels
You can over-define CIB channel paths in order to avoid an outage of a stand-alone coupling facility when defining new CIB connections. You can install an over-defined CIB path later and perform a dynamic activation of the configuration.
HCM supports the IBM® zEnterprise™ 196 (z196) processor family (processor types 2817-M15, -M32, -M49, -M66, -M80).
Support of a third subchannel set
Starting with zEnterprise processors (processor type 2817), users can define devices to a third subchannel set with ID 2 (SCHS 2). In this third subchannel set, users can configure a maximum of 64K-1 devices.
With z/OS V1R12, you can define Parallel Access Volume (PAV) alias devices (device types 3380A, 3390A) of the 2105, 2107 and 1750 DASD control units, PPRC secondary devices (3390D) and DB2 data backup volumes (3390S) to SCHS 2.
New channel path types
To support the internal communication networks that connect to a zEnterprise processor to an IBM zEnterprise BladeCenter® Extension (zBX), two new channel path types are introduced:
- OSX for the intraensemble data network (IEDN)
- OSM for the intranode management network (INMN)
From an HCM perspective, these new CHPID types follow the OSD rules. However, device priority queuing is always disabled for the management network.