HCD and HCM Downloads

The tutorial introduces the basic concepts how to work with HCM.
It contains exercises for navigating through the graphical representation of the configuration, like for example, filtering the diagram, locating objects or zooming into object details. Also, there are exercises on how to document the physical configuration aspects, for example, defining cables.
The tutorial also demonstrates how to exploit the reporting facilities on the configuration.
In the appendix, the tutorial points to the available simplified HCM wizards for complex I/O configuration tasks and gives some advice on how to prepare an HCD IODF for migration to HCM.

Download the hands-on tutorial hcm_getting_started.ppt and the file iodf00.hcm.tutorial.work.hcm which is a ready-to-use I/O configuration for working in standalone mode.

Use the file iodf00.hcm.tutorial.work.expiodf instead of the ready-to-use configuration, if you want to work with the tutorial while connected to HCD. Thus you can exploit the full HCM reporting facilities on HCD IODFs.

The HCM Demo allows you to get familiar with most of the features of Hardware Configuration Manager (HCM). The current version available for download is based on z/OS V1R13 HCM.

You can open an HCM configuration file in standalone mode (without the need to connect to a host) or you can load an IODF from the host into an HCM configuration. In an HCM configuration you can view and navigate to objects, you can create physical objects like cabinets and cables and you can exploit the full HCM reporting facilities on the loaded IODF.

You cannot perform actions that would update the IODF, for example you cannot create logical objects like processors or devices. Furthermore you cannot delete, copy, export, nor import IODFs.

The HCM Demo is shipped with the same context-sensitive online help as the full-featured HCM product.

If you want to process one of your own IODFs using this demo, it is recommended to prepare the IODF in a way that HCM can display the best possible configuration diagram. Therefore, apply the same serial number to those control units that you want to be integrated by HCM into one controller.

If you have switches installed in your configuration, define them in the IODF together with the switch-related CHPIDs attributes.

Further information about how to prepare an IODF for HCM are contained in the HCM Tutorial and in topic 'Preparing the IODF' in the HCM User's Guide.

You can use the HCM Demo to perform the exercises of the tutorial to learn about the various advantages of HCM.

Installing the HCM Demo

Download and run the z/OS V1R13 HCM Demo executable file HCM_Demo.msi. The HCM InstallShield Wizard guides you through the necessary steps.

If you want to connect to an IODF on the host, you must start the HCM dispatcher before the first HCM login request is issued to establish the appropriate communication.

Start the HCM dispatcher by submitting a batch job. You can use the sample job, which is provided as CBDQDISJ in ’SYS1.SAMPLIB’ and submit it after you have adapted it to your needs.

For information about the required changes, read the comments contained in this job. You find more background information in topic 'Establishing the host communication' in the HCM User's Guide.

As a prerequisite to connect to the host, you must install HCD APAR OA27720 on z/OS V1R7 HCD and later.

With the help of a scenario, this tutorial demonstrates the benefits of using HCM wizards and dialogs to perform the following steps:

• Step 1: Create an I/O subsystem
• Step 2: Connect the new I/O subsystem to an existing processor with             a working channel subsystem

Step 2 includes guidance for defining both the physical and the logical connections for the I/O subsystem.

Download the hands-on tutorial Creating_IO_Subsystem.ppt and the file iodf33.iosub.work.expiodf which is a ready-to-use I/O configuration for starting the tutorial while connected to HCD.

If you are experiencing problems with the TCP/IP setup on the host, please refer to the following document:

"TCPI/IP Troubleshooting"

You should verify that the C runtime services used by the HCM dispatcher (gethostname(), gethostbyname(), gethostbyaddress()) are running correctly. This can be done with a small test program which uses these services and reports which service doesn't work (if any):

Download test program