Running Debug Manager as a started task or user job
You can add the Debug Manager started task to the system PROCLIB to run it as a started task, or you can define a RACF profile to run it as a user job.
Running Debug Manager as a started task
Customize the
EQAW.SEQASAMP(EQAZPCM)
sample started task member, as described
within the member, and copy it to SYS1.PROCLIB
as member DBGMGR
.
As shown in the following code sample, provide the following information: - The time-zone offset, default
EST5DST
- The port used for external (client-host) communication, default
5335
- The port used for internal (host-confined) communication, default
5336
- The high-level qualifier of the load library, default
EQAW
Notes:
- This is an optional started task. It is used by z/OS®
Debugger if the
DBM
orDBMDT TEST
runtime parm is used. - For the recommended Workload Manager (WLM) goals for this task, see WLM considerations.
Starting Debug Manager as a user job
When not run as a started task, Debug Manager queries your security
product for explicit permission to start.
Security profile | Required access |
---|---|
EQADTOOL.START.BATCH.jobname.port |
READ |
Name | Substitution |
---|---|
jobname | Name of the job |
port | port number (the port used for internal communication) |
The security class where this profile resides can be specified with SAFCLASS
command line parameter, and is defined as FACILITY
by default. Use
SAFCLASS=CLASS_NAME
command line option to modify the default name. When the
profile is not defined or the class is not active, permission is denied and batch startup fails.
Use the following sample RACF commands to allow user ID
IBMUSER
to start
Debug Manager in batch with job name
EQADBM
and port 5336
:RDEFINE FACILITY EQADTOOL.START.BATCH.EQADBM.5336 UACC(NONE) DATA('start DBM in batch')
PERMIT EQADTOOL.START.BATCH.EQADBM.5336 CLASS(FACILITY) ACCESS(READ) ID(IBMUSER)
SETROPTS RACLIST(FACILITY) REFRESH