Starting DFSMShsm

Before you can start DFSMShsm, you must have a DFSMShsm start procedure.

DFSMSHSM is used as the start procedure name. You can replace DFSMSHSM with any identification you designate for your computing system.

You can start DFSMShsm in either of two ways:

The first time you start DFSMShsm after it is installed, you can load your system control program at initial program load. In response to the request:
   IEA101A SPECIFY SYSTEM PARAMETERS
you reply with:
   R 0,CLPA,CMD=nn
where CMD=nn identifies the startup member in the PARMLIB data set for COMMNDnn, which contains a START DFSMShsm command. You add the START command for DFSMShsm to your parameter library member, COMMNDnn, in the following manner:
  COM='S DFSMSHSM,parameters'
You can issue the START DFSMShsm command from the system console after the system control program is loaded at initial program load. You do not have to load the system control program at initial program load to restart DFSMShsm. The command to start DFSMShsm is:
S DFSMSHSM,parameters

DFSMShsm only runs as a started task; you cannot start DFSMShsm as a batch job. If you plan to run more than one DFSMShsm host in an z/OS® image, you must issue the START command once for each host. At that time, you must specify a unique host identifier in the startup procedure, on the START command itself, or in an ARCSTRxx PARMLIB member that is referred to by the startup procedure or by the command.

Rule: To enable a multiple address space environment for DFSMShsm, you must specify a new keyword HOSTMODE in the DFSMShsm start procedure.

If you start more than one DFSMShsm host in an image, the following conditions must exist:

All the hosts must share the same set of control data sets; that is, they must be in the same HSMplex.
All the hosts, therefore, share the same journal.
Each host has its own log, activity logs, and PDA data sets.

To assist in problem analysis, you may want to incorporate the host-identifier characters into the names of the procedures that are used to start those hosts.

When DFSMShsm gains control after a START command has been issued, a message (ARC0001I) is issued to notify the operator that DFSMShsm is starting up. After the control data sets are opened and all major subtasks are attached, another message (ARC0008I) is issued to notify the operator that initialization is successful and that DFSMShsm is ready to accept commands.

Messages appear at the system console for each DFSMShsm command processed from the parameter library member if the monitoring of startup messages is in effect when the command is processed. These messages are only informational but could be useful if any problems occur. You start monitoring startup messages by specifying one of the following:

COM='S DFSMSHSM,STARTUP=YES'
SETSYS MONITOR(STARTUP)

You stop monitoring startup messages by specifying one of the following:

COM='S DFSMSHSM,STARTUP=NO'
SETSYS MONITOR(NOSTARTUP)

You can include the SETSYS command in the parameter library member as many times as you want. This allows you to control which commands issue messages to the system console when DFSMShsm is starting.

You can install DFSMShsm on multiple z/OS images of a sysplex or in multiple hosts in one z/OS image (or both). However, be sure that the HOST parameter of the startup procedure or the HOST parameter that is specified with the START command is unique for each instance of DFSMShsm that shares the same set of control data sets.

Note: You cannot start the DFSMShsm ABARS secondary address space from the operator’s console by using an MVS™ START command. If you attempt this, DFSMShsm fails the command.

Starting DFSMShsm

Related reading