Hardware Configuration Manager (HCM)


  What's New



HCM enhancements in z/OS V2.2 (September 2017 Update)

Processor support

HCM support the IBM® IBM z14 processor family:

  • processor types 3906-M01, -M02, -M03, -M04, -M05
  • processor types 3906-LM1, -LM2, -LM3, -LM4, -LM5

Support of the new zHyperLink PCIe adapter

To support the new PCIe function type is called ZHYPERLINK.

  • A new PCIe function attribute PORT is required when defining PCIe functions for this new PCIe adapter type.
  • The port value for this adapter type must be port 1 or port 2.
  • Each port allows up to 127 virtual functions.

Support of the new RoCE Express 2 PCIe adapter

To support the new PCIe function type is called ROCE-2.

  • A new PCIe function attribute PORT is required when defining PCIe functions for this new PCIe adapter type.
  • The port value for this adapter type must be port 1 or port 2.
  • One PNETID is supported by this type of PCIe function.

Support of the new CL5 adapter

To support the new channel path (CHPID) type is called CL5.


HCM enhancements in z/OS V2.2

Support of new PCIe functions

Two new PCIe function types are supported - ISM and RCE:

An ISM (Internal Shared Memory) network adapter allows a virtual PCIe function requiring a unique VCHID with up to 255 virtual function Ids. The ISM network adapter allows one PNETID to be specified which has to be identical for all virtual functions of a VCHID.

An RCE (Regional Crypto Enablement) function is used for all IBM® approved vendor crypto adapters.

Hardware support

HCM support the IBM® IBM z13 processor family (processor types 2964-N30, -N63, -N96, -NC9, -NE1; 2964-L30, -L63, -L96, -LC9, -LE1; 2965-N10 and N20 and 2965-L10 and L20).


HCM enhancements in z/OS V2.1

Enhancements of the I/O Autoconfiguration function

HCM provides the following enhancements of the I/O Autoconfiguration function that has been introduced in z/OS V1R12:

Support of PCIe functions

Peripheral Component Interconnect Express (PCIe) adapters offer new functionality to systems running on IBM zEnterprise EC12 and BC12 (zEC12 and zBC12) processors in order to connect, for example, to an IBM zEnterprise BladeCenter Extension (zBX). Therefore, HCM introduces a new dialog where users can define PCIe functions, assign them to LPAR.

PCHID Summary Report

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.

Hardware support

HCM supports the IBM zEnterprise EC12 and BC12 (zEC12 and zBC12) processor family (processor types 2827-H20, -H43, -H66, -H89, -HA1 and 2828-H06, -H13).


HCM enhancements in z/OS V1.13

Improved CUADD assignment for multiple channel path connections

HCM provides a new dialog to improve the CUADD assignment for multiple channel path connections to multiple control units. This feature helps you, for example, if you have two groups of control units that you want to connect to two sets of disjoint CHPIDs, or if you want to connect a group of control units to a second processor using the same CHPID/link addresses as used for the connection to the first processor.

Hardware Support

HCD provides the following new hardware support:


HCM enhancements in z/OS V1.12

I/O Autoconfiguration

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 HCM 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 your specified target work IODF.

Accordingly, HCM provides a wizard offering:

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:

The D/R site OS configuration is generated automatically during Build production I/O definition file or Build validated work 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.

Hardware Support

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 (SS 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 SS 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:

From an HCM perspective, these new CHPID types follow the OSD rules. However, device priority queuing is always disabled for the management network.


HCM enhancements in z/OS V1.11

New HCM installation process

The installation process for HCM has changed. The code is delivered as an MSI package and is installed using the Windows® Installer.

New location of the HCM INI file

The location of the EEQHCM.INI file changed from C:\WINDOWS to the user-specific application data directory. HCM creates separate versions of this file, if multiple users are working on the same workstation. Each user can thus take advantage of his own preferred session settings.

Due to changes in the user authorization methods for Windows XP and later versions, the change of the location is necessary to allow users who are not administrators to update this file.

Supporting IPv6

HCM supports the Internet Protocol, Version 6 (IPv6), which you can use when establishing a communication session with HCD.

Handling multi-user access enabled IODFs

HCM lets you load a multi-user access (MUA) enabled IODF from HCD into a new HCM configuration file and lets you also open an existing HCM configuration associated with a MUA enabled IODF. You can use the viewing and reporting features of HCM on such configurations and you may perform physical changes. However, you cannot update the associated IODF.


HCM enhancements in z/OS V1.10

Enhanced named view

HCM handles the display of named views in a more intuitive way. Therefore, the following information is additionally saved when creating a named view:

If you selected Objects not connected to processors in the Change View Attributes dialog, not all disconnected devices and their controllers are shown, but only disconnected devices/controllers of those types that you included in that dialog.

If the Objects not connected to processors checkbox is selected, the diagram now shows the controllers of the selected controller types which are not connected to processors, while in previous releases unconnected controllers of all types had been shown without regarding the user’s controller type selection.

Using configuration packages with HCM

A configuration package is a subset of a centrally maintained master IODF which is extracted from that master IODF and distributed for activation at specified target systems. Up to now, working with configuration packages was only possible with HCD. Starting with this release of z/OS new HCM dialogs let users define, edit, transmit and delete configuration packages, corresponding to the HCD functionality.

This function is not available for z/VM.

Create and migrate I/O configuration statements

HCM implements new dialogs that let users perform the following tasks, that so far have been available in HCD only:

Enhanced copy wizards

The Copy Channel Subsystem wizard allows you to specify an existing target CSS if it contains reserved partitions only.

The Copy Partition wizard allows you to specify an existing reserved partition as target partition.

CUADD value is shown on the Control Unit List

A new column CUADD is introduced on the Control Unit List to display the defined logical address for a control unit, where available.

New channel path type for coupling over InfiniBand

The use of InfiniBand technology is supported by a new channel path type CIB to emulate coupling connections in the Host Communication Adapter (HCA). Support is provided on type 2094, 2096 and type 2097 processors to define coupling links and STP links between CPCs.

Handling multi-user access enabled IODFs

In z/OS V1R10 HCD, when creating an IODF, you can specify a multi-user access (MUA) option so that multiple users can simultaneously update this IODF. From HCM’s IODFs and IODF Details dialogs, you can find out whether an IODF’s MUA status is enabled or disabled. However, you cannot work with MUA-enabled IODFs in HCM.

Removed support

HCM support for making exported data accessible for the Tivoli Inventory database is no longer available.


HCM enhancements in z/OS V1.9

HCM master configuration file (MCF)

The HCM master configuration file (MCF) is a HCM configuration stored on the host. It provides a central shared repository, allowing several HCD/HCM users to work on a single configuration cooperatively and safely. This does not mean concurrent access to the configuration: the MCF enforces sequential access, one user (in connected mode) at a time.

When physical updates are applied to a shared configuration in stand-alone mode, MCF helps merging the changes into the master configuration later (using a mismatch resolution dialog).

Support of password phrases for HCM logon

As an alternative to a logon password, HCM now also lets you specify a password phrase for user logon. A password phrase is a sentence (including blanks) of at least 9 and up to 100 mixed-case characters.

Enhanced HCM and IODF reports

Besides printing HCM and IODF reports on paper, users can now select new formats for saving the reports in files:


  1. These options are not available for HCM or IODF compare reports.
  2. The HTML format is not available for IODF reports.

Additionally, HCM provides a new method to limit the reports to those objects which need to be included. From the modified printing dialog, users can select multiple objects of specific types, depending on the selected report(s). HCM will only include these selected objects into the limited reports.

Vertical processor view in the configuration diagram

In the existing horizontal view for XMP processors, the channel subsystems are shown from left to right, providing a logically oriented arrangement of spanned CHPIDs and PCHIDs shown multiple times. Optionally, users can now request a vertical view, where the channel subsystems are arranged one above the other, with spanned CHPIDs (and their PCHIDs) appearing only once, thus providing a physically oriented view of the processor.

This function is available as SPE:

Modify I/O subsystems

To ease the task of modifying an existing I/O subsystem consisting of many control units and devices, HCM offers a new Edit I/O Subsystem wizard which can be invoked from a controller’s context menu. This wizard supports users in efficiently performing actions that affect a large number of components when upgrading a controller, like for example, increase the number of control units and/or strings and devices or changing the object topology inside the I/O subsystem.

Applying default port names

You can automatically apply standard names to all ports of multiple or all switches with one action from the Edit a Switch dialog. For the selected switches, this action composes a default name for all involved ports, taking up to the first 24 characters of the corresponding connection information.

This function is available as SPE:

Compressing HCM configuration files

HCM offers a new option to store the HCM configuration files in a compressed format. Compressed configuration files use less disk space. They cannot be opened with HCM versions prior to z/OS V1R9. However, at any time you can switch from compressed to uncompressed format.

Save As... behavior

The behavior of the Save As... function has been enhanced in a way that HCM now remembers multiple directories that you last selected depending on the file type you wanted to save.

Enhancements with importing/exporting data

New column ‘Position’ in PATCHPRT table:< /br> The Export Data function now exports the position of a cabinet patchport or general box port (needed for positioning in the diagram) in the new optional column ‘Position’ of the PATCHPRT table.


Label change for objects:< /br> Starting with z/OS 1.9 HCM, you can no longer create controller adapters and controller device adapters with a label containing a period (’.’). Also, if you edit existing objects of these types containing a period in their labels, HCM enforces a label change by issuing a corresponding message. The reason for this behaviour is that objects with a period in their labels cannot be imported.

Removed support

Starting with this release, support of APPC to establish the host connection is withdrawn.

Contact IBM

Browse z/OS