z/OS DFSMShsm Implementation and Customization Guide
Previous topic | Next topic | Contents | Contact z/OS | Library | PDF


Configuring DFSMShsm to invoke DFSMSdss as a started task

z/OS DFSMShsm Implementation and Customization Guide
SC23-6869-01

When DFSMShsm invokes DFSMSdss using the DFSMSdss cross memory API, DFSMShsm will request that DFSMSdss use a unique address space identifier for each unique DFSMShsm function and host ID. For a list of DFSMSdss address space identifiers, see DFSMSdss address spaces started by DFSMShsm.

If you plan to configure DFSMShsm to start DFSMSdss in its own address space using the DFSMSdss cross memory API, you might need to configure your security system to permit these tasks.

These tasks can be defined explicitly in the same manner as the DFSMShsm started task in Method 1–RACF started procedures table (ICHRIN03) or they can be defined generically in the same manner as the DFSMShsm started task in Method 2–RACF STARTED class.

The following is an example of the commands you might use. The user ID DFHSM, also in the example for Method 2–RACF STARTED class, is used for illustration only.
SETR GENERIC(STARTED)
RDEFINE STARTED ARC*.*  STDATA(USER(DFHSM))
SETR RACLIST(STARTED) REFRESH

Normally the starting process for DFSMSdss is IEESYSAS. When viewing active jobs in SDSF, IEESYSAS will appear as the job name, and the DFSMShsm passed address space identifier will appear as the step name.

Go to the previous page Go to the next page




Copyright IBM Corporation 1990, 2014