Setting up HCD

HCD is a base element of z/OS and therefore installed with the z/OS product. For more information, refer to z/OS Planning for Installationz/OS Planning for Installation.

The installation of HCD is carried out using SMP/E. The install logic and the JCLIN are provided by HCD. For the installation, refer to the z/OS Program Directoryz/OS Program Directory.

Setting up HCD requires the following steps:

Install z/OS with the HCD FMIDs.

Install other products that are required for HCD (refer to z/OS Planning for Installationz/OS Planning for Installation).

Before you start HCD, you have to set up the load libraries that contain the HCD help modules. You can achieve this in one of the following ways:

Include SYS1.SCBDHENU (or SYS1.SCBDHJPN for Kanji) in the linklist concatenation (LNKLSTxx member), or
Allocate data set SYS1.SCBDHENU (or SYS1.SCBDHJPN for Kanji) to ISPLLIB.

If you choose to access the libraries through the ISPLLIB concatenation, ISPLLIB must be allocated prior to invoking ISPF with the TSO ALLOC command or through a CLIST. ISPLLIB is used as a tasklib by ISPF as it is searched first.

When using the View graphical configuration report:

Include the GDDM load library in the linklist concatenation (LNKLSTxx member).
Allocate the GDDM sample data set:
For GDDM 2.1 and 2.2:
```
ALLOCate F(ADMPC) DSN('pplib.GDDM.GDDMSAM') SHR REUSE
```
For GDDM 2.3 or later:
```
ALLOCate F(ADMPC) DSN('pplib.GDDM.SGDDMSAM') SHR REUSE
```
If you are using a programmable workstation and you communicate with the host using a 3270 emulator session, the GDDM-OS/2 link files must be installed on your workstation. Note that the high-level qualifier for the GDDM data set might vary from installation to installation.

Allocate the data set SYS1.SCBDCLST to the SYSPROC ddname concatenation.

Note:

SYS1.SCBDCLST has a fixed record format (RECFM=FB). If your other SYSPROC data sets have a variable record format (RECFM=V or VB), copy SYS1.SCBDCLST to a data set with variable record format. You have to remove sequence numbers (in the CLIST) after copying the members to a data set with variable record format.

For processing large IODFs, and when HCD option IODF_DATA_SPACE is set to NO, the size of your TSO region may not be sufficient. When you specify the region size on the TSO logon panel, calculate as follows:

                 2 x IODF size + 4 MB
Example:

Assumed IODF size:  8000 blocks, 4 KB per block = 32 MB

Suggested region size:  68 MB

For setup requirements when using HCD via the HCD LDAP backend, see How to provide LDAP support for HCD.

To run HCD, the modules in SYS1.SCBDHENU (containing HCD help members) and SYS1.NUCLEUS (containing the UIMs) must be accessible. For the HCD dialog, you can achieve this in three ways:

Include SYS1.SCBDHENU in the linklist concatenation (LNKLSTxx member).

Include SYS1.SCBDHENU in the JOBLIB/STEPLIB concatenation of the TSO logon procedure.

Include SYS1.SCBDHENU in the ISPLLIB load library concatenation. If you include SYS1.SCBDHENU into the ISPLLIB concatenation, ISPLLIB must be allocated prior to invoking ISPF (in TSO or through JCL in the logon procedure). ISPLLIB is used as a tasklib by ISPF and is searched first. A pure LIBDEF for ISPLLIB does not suffice to invoke HCD.

HCD allocates SYS1.NUCLEUS automatically at initialization time if the keyword UIM_LIBNAME is not specified in the HCD profile. You may use the HCD profile to specify a different name and the volume serial number of the library that contains the UIMs (see also Defining an HCD profile). If you do not specify a name in the profile, SYS1.NUCLEUS is assumed as default name for the UIMs. For IPL, however, the UIMs and UDTs must be in SYS1.NUCLEUS.

The following HCD libraries are defined via the ISPF 'ISPEXEC LIBDEF' command if HCD is invoked via CLISTs CBDCHCD and CBDCHCD1:

SYS1.SCBDPENU for panels

SYS1.SCBDMENU for messages

SYS1.SCBDTENU for tables