Starting the HCD dispatcher as a started task

There is a procedure CBDQDISP provided in SYS1.PROCLIB, which you can use to start the HCD dispatcher as a started task.

You can create a new user ID or use an existing one to be associated with the task of the HCD dispatcher. This user ID has to have permission to use UNIX System Services.

After the procedure has been adapted to your installation needs, you can start it by using the start command. Start the HCD dispatcher always after the system has been IPLed. You can also start the HCD dispatcher automatically using System Automation for z/OS.

You can change the following parameters in the procedure:

Job name

The HCD dispatcher submits a job for each incoming remote HCD login request. As a default, the job name of this job starts with CBD. If you want the job names to start with something different than CBD, you can specify a different string for the beginning of the job name by setting the JNP variable. If you want the job name to contain the user ID of the remote HCD user, specify +U and the HCD dispatcher substitutes the +U with the requestor's user ID. You can also add a prefix to the user ID or append a string to the user ID. For example, a X+UY for a passed user ID BMGN would result in XBMGNY for the beginning of the job name. Note, the HCD dispatcher does not accept more than seven digits for the beginning of a job name. Strings longer than seven digits are truncated. The HCD dispatcher generates a job name using the JNP variable and fills it up to eight digits. If the JNP variable contains three digits, the job name is filled up to eight digits by using parts of the port address of the HCD dispatcher and parts of the port address of the HCD client, which are started. If the JNP variable does not have three digits, it is filled up to eight digits by using 0...9 and A...Z.

Logging information

For special cases (debugging or better control), the HCD dispatcher can write logging information into a data set. In this case, change the LOG variable.

Port

If there is any reason to use another port than 51107 on which the HCD dispatcher listens for incoming remote HCD login requests, you can specify your port by setting the PORT variable.

Skeleton

You can specify another skeleton to be used to start the HCD agent by changing the JSK variable.

Port range

It is possible to determine a different range for the ports chosen by the HCD dispatcher for communication with the HCD agent during start of the dispatcher. The port range used must be configured to be available and permitted to the HCD agent. Set the variables P0 and P1 to appropriate values. Note that ports bigger than 65535 are not allowed.

Creating a user ID

If you want to run the HCD dispatcher as a started task, you must create a user ID for it.

1. Create a user ID to be used as started task for the procedure CBDQDISP. This user ID must have permission for running UNIX System Services.
2. Define the user ID to be used for the started task procedure CBDQDISP.
3. Refresh RACF®.

The following figure shows a sample job in which the user ID for the HCD dispatcher can also be used by the UNIX System Services. (Note that the specified home directory for the HCD dispatcher is the root directory in this example).

//ADDUSER  EXEC PGM=IKJEFT01
...
//SYSIN    DD *
   AU CBDQDISP NAME('STARTED-T. M. GNIRSS') OWNER(STCGROUP) +
      DFLTGRP(STCGROUP) +
      OMVS(HOME(/) PROGRAM(/bin/sh) UID(4711))
//*
//DEFRACF  EXEC PGM=IKJEFT01
...
//SYSTSIN  DD *
   RDEF STARTED CBDQDISP.*  STDATA(USER(CBDQDISP)  GROUP(STCGROUP))
//*
//REFRESH  EXEC PGM=IKJEFT01
...
//SYSTSIN  DD *
   SETR REFRESH RACLIST(STARTED) GENCMD(*) GENERIC(*)
/*