This statement is used to specify system-wide and/or user-specific POSIX default classes for POSIX-FORK tasks.
If neither a system-wide POSIX default class nor one which applies for the user concerned has been defined, the user’s POSIX-FORK tasks are started in the default class for batch or interactive jobs which applies for the user.
Format
SET-POSIX-JOB-CLASS-DEFAULT |
NAME = <name 1..8> ,ACTION = *ADD / *REMOVE ,USER = *ALL / list-poss(255): <name 1..8> |
The meaning of the operands is the same as for the GRANT-JOB-CLASS-ACCESS statement.
SET-POSIX-JOB-CLASS-DEFAULT default-class.old,*REMOVE,*ALL
SET-POSIX-JOB-CLASS-DEFAULT default-class.new,*ADD,*ALL.
If no POSIX default class has been assigned yet, the first statement is omitted.
Unlike with SET-JOB-CLASS-DEFAULT, when a job class is assigned as the POSIX default class, the selected users are not automatically guaranteed access to this job class. When required, this must be defined explicitly by the administrator using GRANT-JOB-CLASS-ACCESS. This does not automatically permit normal interactive and batch jobs to be started in this job class. POSIX-FORK tasks can use the job class, however.
A POSIX default class defined using USER=*ALL initially applies throughout the system for all user IDs. If different POSIX default classes are to apply for certain user IDs, this can be defined with further SET-POSIX-JOB-CLASS-DEFAULT statements, e.g. with the operands NAME=other_class,ACTION=*ADD, USER=list_of_users.
Default classes already defined with SET-JOB-CLASS-DEFAULT can also be defined as POSIX default classes.
A POSIX default class can belong to the category interactive or batch. It is relevant for all POSIX-FORK tasks of the interactive or batch job type.