Graphical representation of physical objects

HCM represents controllers and string objects in the configuration diagram based on their physical descriptions. The physical description files, or PDFs, are templates that you can tailor. They are similar to HCD UIMs, except that the PDFs contain physical rather than logical information.

HCM comes with generic PDFs for controllers and strings, as well as PDFs for selected IBM equipment. For example, the PDF for a 3990 controller specifies that it is divided into two sections, each of which contain control units. Sample PDFs are also included which may serve as examples of how you might create PDFs for non-IBM equipment.

You can modify the PDFs for objects as part of preparing the IODF for use in HCM (see Preparing the IODF).

Unlike HCD UIMs, you do not need a PDF for each controller and string type in your configuration. PDFs are only required in special circumstances, where the controller or string would not appear correctly in the diagram using the default PDF. For example, PDFs are required in the following situations:

1. For most DASD controllers, which typically contain two segments. (Note: segments may also be known as storage clusters, storage directors or buses, depending upon manufacturer and model.)
2. For controllers, which have a hierarchical internal architecture, such as the interfaces within channel adapters contained in buses (generically referred to as segments in HCM).
3. For tape controllers, such as the 3803 and 3480, which connect to peers via communicator cables.
4. For controllers and strings which number their interfaces with a scheme that differs from A, B, C...