Establishing attributes for address spaces

Through the ATTR parameter, you can define some of the attributes for programs that run in the new address space. Table 1 describes the options for ATTR and identifies what definitions override those options.

Table 1. ATTR options for address spaces
Option	Description	Override
NONURG	The address space is to be used by nonurgent services. The defaults for dispatch priority as well as service class or performance group depend on whether the address space is privileged or not. The dispatching priority of programs that run in the new address space is to be low.	The service definitions of the workload management (WLM) policy
HIPRI	The address space is to be used by services with a high priority. The defaults for dispatch priority as well as service class or performance group depend on whether the address space is privileged or not. The dispatching priority of programs that run in the new address space is high.	The service definitions of the WLM policy
PERM	The address space does not terminate when the task that created the address space terminates.	No override
JOBSPACE	The address space should be marked as a job (started task) space, rather than as a system address space.	No override

The NONURG and HIPRI parameters set the dispatching priority for programs that execute in the new address space. Your installation can also set the dispatching priority through service definitions in the WLM policy. See z/OS MVS Planning: Workload Management.

Do not set the dispatching priority in more than one way.

If you want the new address space to exist after the TCB of the creating program terminates, use ATTR=(PERM).

When the address space is marked as a job, the resource name used for the started class profile will be procname JOBNAME. Display it with the DISPLAY A,L command.