How to invoke HCD batch utility functions

You can invoke HCD batch utility functions:

• With an input parameter string. The diagram below shows how to invoke an HCD batch utility function. For formats of the input parameter strings and sample batch jobs see Input parameter string.
  HCD Batch Invocation

  >>-EXEC--PGM=CBDMGHCP,--PARM='-| Input Parameter String |-'----><
   
  

• By using an ATTACH or LINK module programming statement to invoke the module CBDMGHCP.

  When you invoke the module, register 1 must contain the address of a two-word parameter list.

  Word 1

  Address of input parameter (see Input parameter string), preceded by a two byte length field.

  Word 2

  Address of a list of alternate DD names. If not used, the address must be binary zero. For the list format of alternate DD names see List of alternate DD names.

You may overwrite standard DD names listed in Table 6 as desired before invoking HCD.

If you specify the UIMs and UDTs in a library other than SYS1.NUCLEUS, you have to add the following statement to your batch jobs:

//HCDPROF DD DSN=BPAN.HCD.PROF,DISP=SHR

In the HCD profile (in our example BPAN.HCD.PROF) specify the following keyword:

UIM_LIBNAME=libname

If the keyword is omitted, SYS1.NUCLEUS is assumed. If you specify an asterisk (*) as data set name, HCD assumes that the UIM data set is part of the ISPF load library concatenation chain, contained in the JOBLIB/STEPLIB concatenation chain, or specified in the active LNKLSTxx member. For more information, see Defining an HCD profile.

Running jobs in a sysplex environment: 

If you want to execute a job on a specific system in a sysplex, you must specify in your batch job which system is to be used. If you do not specify the exact system of a sysplex for which the batch job is planned to execute on, the job executes on the system that has the free space to run on.

The output from some of the HCD functions depend very much on where the job was executed; for example, downloading IOCDSs and requesting the I/O Path report.