Create entry in user catalog
Component: | SRPMNUC |
Functional area: | User management |
Domain: | USER-ADMINISTRATION |
Privileges: | STD-PROCESSING USER-ADMINISTRATION |
Routing code: | $ |
Function
The ADD-USER command enables systems support personnel to create an entry in the user catalog for a pubset, which means that a user catalog entry is set up for a user ID.
If an entry is created for the user catalog of the home pubset, the access rights to the system (e.g. user ID, accounting number, user ID password, etc.) and the assignment of a default pubset for the user must be defined. Only in the user catalog of the home pubset is a check made whether the user has observed the correct syntax in the specifications (LOGON validation).
The system support staff enters all the necessary pubset-specific information in the user catalog of the default pubset.
Systems support must define an upper limit for the user up to which the user may occupy storage space on this pubset. Additionally, provisions can be made for the possibility of exceeding this limit.
The name of a new user ID can be chosen freely - within the set of permissible characters. The prefix ‘SYS’, however, is reserved for system IDs and must not be used.
The LOCK-USER=*YES operand can be used to set an access lock for the new user ID until all the desired attributes have been assigned and group membership has been declared. The entry must be stored on the home pubset; for data pubsets, the lock is irrelevant.
The lock is retained until an UNLOCK-USER command is issued.
Restriction
The only nonprivileged users (STD-PROCESSING privilege) authorized to issue this command are those designated as group administrators. The actions a group administrator can take are defined by systems support. On setting up and managing user groups see the “SECOS” manual [35].
Format
ADD-USER | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Operands
USER-IDENTIFICATION = <name 1..8>
Defines the user ID to be entered in the catalog of the pubset in question.
GROUP-IDENTIFICATION =
Identifier of the user group to which the new user ID is to be assigned. SECOS can be used to install a hierarchy of user groups to each of which a number of user IDs can be assigned. Without this software product, all of the user IDs are subordinate to the group *UNIVERSAL, which acts as a dummy group in the system.
GROUP-IDENTIFICATION = *OWN
The user ID is assigned to the user group of the command issuer.
If the command issuer does not belong to a user group or SECOS is not installed, *UNIVERSAL is assumed.
GROUP-IDENTIFICATION = *UNIVERSAL
The user ID is explicitly assigned to the group *UNIVERSAL.
If SECOS is used, this value permits a user ID to be created outside of group hierarchies.
GROUP-IDENTIFICATION = <name 1..8>
Existing user group to which the new user ID is assigned.
This value can be specified only if the SECOS product is installed.
PROTECTION-ATTRIBUTE = *PARAMETERS(...)
Defines protection attributes.
LOGON-PASSWORD = *NONE / <c-string 1..8> / <c-string 9..32> / <x-string 1..16> / *SECRET
Password protecting the user ID from unauthorized access (long password (<c-string 9..32>), see the MODIFY-USER-PROTECTION command).
PASSWORD-ENCRYPTION = *YES / *NO
The password of the user ID is encrypted after entry or is stored in its original form. Password encryption presupposes that the system parameter ENCRYPT=Y is set in the parameter file (see the “Introduction to System Administration” [14]).
ADD-USER | parameter file | |
|---|---|---|
ENCRYPT=Y | ENCRYPT=N | |
PASS-ENCRYPT =*YES | Encryption | No encryption |
PASS-ENCRYPT =*NO | No encryption | No encryption |
PASSWORD-MANAGEMENT =
Specifies the user’s rights with regard to modification of his password.
If SECOS is used, the value defined here will be ignored and the SECOS specific value *LOGON-DEFAULT will be assigned instead.
The current meaning of this value (*BY-USER, *BY-ADMINISTRATOR or *USER-CHANGE-ONLY) can be determined with the SECOS command SHOW-LOGON-DEFAULTS (see the “SECOS, Volume 1” manual [35]).
PASSWORD-MANAGEMENT = *BY-USER
The user may define, modify or delete a password.
PASSWORD-MANAGEMENT = *BY-ADMINISTRATOR
Only systems support staff may define, modify or delete the password for the user ID.
PASSWORD-MANAGEMENT = *USER-CHANGE-ONLY
The user may define and modify a password. Deletion of the password, i.e. cancellation of access rights, is not permissible.
TAPE-ACCESS =
Defines whether error messages generated during label checking of tapes may be ignored by the operator for the user concerned.
TAPE-ACCESS = *STD
Error messages must not be ignored.
TAPE-ACCESS = *PRIVILEGED
The following error messages for input and output files may be ignored by the owner of the tape or by systems support staff:
invalid VSN
tape is write-protected
incorrect file set identifier in the HDR1 label of the tape.
TAPE-ACCESS = *READ
The user may ignore error messages relating to input files; label checking is not deactivated. The following errors may result in messages during tape processing:
invalid volume serial number (VSN)
invalid file name
invalid label on tape
invalid access method
invalid file sequence number on tape
tape mark instead of end-of-volume label on tape
double tape mark instead of end-of-volume label on tape.
TAPE-ACCESS = *BYPASS-LABEL
Label checking and thus any data protection for tape files is deactivated for tapes processed in INPUT or REVERSE mode. This privilege implies the TAPE-ACCESS=*READ function.
TAPE-ACCESS = *ALL
All error messages may be ignored. This privilege implies the TAPE-ACCESS=*PRIVILEGED and TAPE-ACCESS=*BYPASS-LABEL functions.
FILE-AUDIT = *NO / *ALLOWED
Defines whether the user is authorized to activate the AUDIT mode.
This mode serves to monitor DMS accesses to files or file generations by system exit routines or, if the SECOS software product is used, by the SAT component.
MAILING-ADDRESS = *NONE / <c-string 1..64 with-low> / <x-string 1..128>
Mailing address of the user for spoolout lists.
EMAIL-ADDRESS = *NONE / <composed-name 1..1800> / <c-string 1..1800 with-low> / <x-string 1..3600>
Specifies an email address or a list of email addresses for the users of this user ID. The addresses must be entered in the format '<local-part>@<domain>[,...]'. Optionally an address can also be prefixed by an address name in parentheses (see "Example"). A list consists of multiple addresses separated by a comma and can only be specified as a string (c or x string).
The address or address list entered is evaluated when a file is sent by email (see the MAIL-FILE command).
PUBLIC-SPACE-LIMIT = *STD / *MAXIMUM / <integer 0..2147483647 2Kbyte >
Assigns the maximum storage space the user may occupy for his files on public volumes on the pubset allocated with the PUBSET operand. The specified value must be <= 2,147,483,647.
PUBLIC-SPACE-LIMIT = *STD
By default the user is allocated 16,777,215 PAM pages.
PUBLIC-SPACE-LIMIT = *MAXIMUM
The user may use the full capacity of 2,147,483,647 PAM pages.
PUBLIC-SPACE-EXCESS =
Defines whether the user may exceed the limit defined by the PUBLIC-SPACE-LIMIT operand for the storage space on the allocated pubset.
PUBLIC-SPACE-EXCESS = *NO
The storage space limit must not be exceeded.
PUBLIC-SPACE-EXCESS = *TEMPORARILY-ALLOWED
In the case of storage space requests on the user’s default pubset, the storage space limit may be exceeded, provided that it had not already been exceeded at logon time. For all other pubsets, PUBLIC-SPACE-EXCESS=*TEMPORARILY-ALLOWED has the same effect as PUBLIC-SPACE-EXCESS = *NO.
PUBLIC-SPACE-EXCESS = *ALLOWED
The storage space limit may be exceeded.
ADDRESS-SPACE-LIMIT = *STD / <integer 1..2147483647 Mbyte >
Defines how much user memory a task can request under this user ID. The user memory comprises both conventional class-6 memory (program space) and (data spaces). The maximum user memory depends on the size of the virtual memory and can be less than the value specified here.
ADDRESS-SPACE-LIMIT = *STD
The value of the system parameter SYSGJASL is assigned (the system parameter SYSGJASL has the default value 16 MB).
MAX-ACCOUNT-RECORDS =
Defines how many user-specific accounting records for each job or program are allowed to be written into the accounting file of the system.
MAX-ACCOUNT-RECORDS = 100
The user is authorized to write 100 user-specific accounting records to the accounting file for each job or program. He is not allowed to write accounting records of his own.
MAX-ACCOUNT-RECORDS = *NO-LIMIT
The user is authorized to write any number of user-specific accounting records and accounting records of his own in the accounting file.
MAX-ACCOUNT-RECORDS = <integer 0..32767>
Defines how many user-specific accounting records can be written in the system accounting file for each job or program. The user is not authorized to add accounting records of his own.
PROFILE-ID =
Determines whether the user ID is assigned an SDF-PROFILE-ID. This PROFILE-ID characterizes a (SDF) group of user IDs which use a common group syntax file. Systems support can effect direct assignment of a user ID to a group syntax file by means of a suitable entry in the SDF parameter file.
PROFILE-ID = *NONE
The user ID is not assigned a profile ID and thus indirectly no group syntax file.
PROFILE-ID = <structured-name 1..30>
Defines the name of a PROFILE-ID to which a group syntax file can be assigned in the SDF parameter file.
PUBSET =
Defines the pubset whose user catalog is to accept the entry.
PUBSET = *HOME
The entry is made in the user catalog of the home pubset.
PUBSET = <cat-id 1..4>
Catalog identifier of the pubset whose user catalog is to accept the entry.
RESIDENT-PAGES = *STD / *MAXIMUM / <integer 0..2147483647 4Kbyte >
Defines the maximum number of resident main memory pages available to the user ID.
RESIDENT-PAGES = *STD
The user may use 32,767 resident main memory pages.
RESIDENT-PAGES = *MAXIMUM
The user may use 2,147,483,647 resident main memory pages.
CSTMP-MACRO-ALLOWED = *NO / *YES
Determines whether the user may use the CSTMP macro in his programs. The user can use the CSTMP macro to write-protect a memory pool (in class 6 memory) that can be shared by multiple users or explicitly cancel this protection. This feature is described in detail in the “Executive Macros” manual [22].
DEFAULT-PUBSET =
Assigns the user ID a default pubset on which the user can store his files and request storage space. If a file belonging to the newly entered user ID is accessed under any arbitrary user ID, and if the catalog ID is not specified, the catalog ID in the path name will automatically be extended by “:catid:”. Systems support can change the DEFAULT-PUBSET operand in any user catalog of an imported pubset. However, the user default pubset is determined only with the aid of the user catalog of the home pubset. For the TSOS user ID, the value of DEFAULT-PUBSET must be identical to the value of PUBSET.
DEFAULT-PUBSET = *HOME
Defines the home pubset to be the user default pubset.
DEFAULT-PUBSET = <cat-id 1..4>
Defines a pubset to be a user default pubset by means of the catalog ID.
TEST-OPTIONS = *PARAMETERS(...)
Defines the maximum possible privilege for testing and diagnostic analysis of programs. The test privilege is interpreted by the software products AID and DAMP as well as the access method ANITA.
Even at privilege level 2 the user has access to task-specific, sensitive data (system tables and control blocks). Higher values should be allocated only on request and for a limit period to selected user IDs. The values possible here and explanations are described in section "Overview of test privileges".
READ-PRIVILEGE = 1 / <integer 1..9>
Defines the maximum read privilege level.
WRITE-PRIVILEGE = 1 / <integer 1..9>
Defines the maximum write privilege level.
MODIFICATION =
Specifies whether the user requires the operator’s permission to modify his/her current test privilege.
MODIFICATION = *CONTROLLED
The user requires the operator’s permission.
MODIFICATION = *UNCONTROLLED
The user does not require the operator’s permission.
AUDIT = *PARAMETERS (...)
Defines user-specific audit authorization. Authorization may be assigned to users separately for hardware audit and linkage audit. System-wide availability of the audit function is defined via the AUDALLOW system parameter.
Note
Hardware audit is only supported on /390 architecture (SUs /390 and S servers).
HARDWARE-AUDIT = *ALLOWED / *NOT-ALLOWED
Specifies whether a user is authorized to control the hardware audit mode. The audit mode can be controlled by means of the START-, STOP-, HOLD- and RESUME-HARDWARE-AUDIT commands and via the AUDIT macro for the function states
TU (task unprivileged) and TPR (task privileged). Modifications only affect the user ID’s new tasks.
HARDWARE-AUDIT = *ALLOWED
The user is allowed to control the hardware audit mode, provided the audit function is available throughout the system.
HARDWARE-AUDIT = *NOT-ALLOWED
The user is not allowed to control the hardware audit mode.
LINKAGE-AUDIT = *ALLOWED / *NOT-ALLOWED
Specifies whether a user is authorized to control the linkage audit mode. The audit mode can be controlled by means of the START-, STOP-, HOLD- and RESUME-LINKAGE-AUDIT commands and via the AUDIT macro for the function states TU (task unprivileged), TPR (task privileged) and SIH (system interrupt handling).
Modifications only affect the user ID’s new tasks.
LINKAGE-AUDIT = *ALLOWED
The user is allowed to control the linkage audit mode, provided the audit function is available throughout the system.
LINKAGE-AUDIT = *NOT-ALLOWED
The user is not allowed to control the linkage audit mode.
DEFAULT-MSG-LANGUAGE = *STD / <name 1..1>
Specifies the language in which messages are output by default.
DEFAULT-MSG-LANGUAGE = *STD
The language defined using the MSGLPRI system parameter is used.
FILE-NUMBER-LIMIT =
Specifies the maximum number of files that may be created. This upper limit, or any lower value, may be assigned to subgroups or group members.
FILE-NUMBER-LIMIT = *MAXIMUM
The maximum number of files is 16777215.
FILE-NUMBER-LIMIT = <integer 0..16777215>
Specifies the maximum possible number of catalog entries as an exact number.
JV-NUMBER-LIMIT =
Specifies the maximum number of job variables that may be created. This upper limit, or any lower value, may be assigned to subgroups or group members.
JV-NUMBER-LIMIT = *MAXIMUM
The maximum number of job variables is 16777215.
JV-NUMBER-LIMIT = <integer 0..16777215>
Specifies the maximum possible number of job variables as an exact number.
TEMP-SPACE-LIMIT =
Specifies the maximum amount of temporary storage space which may be occupied on the shared volumes specified in the PUBSET operand.
TEMP-SPACE-LIMIT = *MAXIMUM
The maximum amount of storage space is 2147483647 PAM pages.
TEMP-SPACE-LIMIT = <integer 0..2147483647 2Kbyte >
Specifies exactly the amount of temporary storage space.
DMS-TUNING-RESOURCES =
Specifies which performance measures may be utilized, and the form in which they may be used.
DMS-TUNING-RESOURCES = *NONE
No tuning measures my be utilized.
DMS-TUNING-RESOURCES = *CONCURRENT-USE
The user may reserve preferred resources, but in doing so competes with all other users who have the same authorization.
DMS-TUNING-RESOURCES = *EXCLUSIVE-USE
The user may make exclusive reservations of preferred resources.
Permitted performance measures for the home and data pubsets
PUBSET = *HOME | ||||
|---|---|---|---|---|
DMS-TUNING RESOURCES= | Resident ISAM pools | Resident FASTPAM environment | File attribute PERFORMANCE | |
|HIGH | =*VERY-HIGH | |||
*NONE | no | no | no | - |
*CONCURRENT-USE | yes | no | - | - |
*EXCLUSIVE-USE | yes | yes | - | - |
PUBSET = <Data pubset> | ||||
DMS-TUNING-RESOURCES= | Resident ISAM pools | Resident FASTPAM environment | File attribute PERFORMANCE | |
| HIGH | =*VERY-HIGH | |||
*NONE | - | - | no | no |
*CONCURRENT-USE | - | - | yes | no |
*EXCLUSIVE-USE | - | - | yes | yes |
CODED-CHARACTER-SET = *STD / <name 1..8>
Specifies which CODED-CHARACTER-SET (CCS) is to be used. A name should only be specified here if the one required differs from the one preset by the system (*STD). A CCS identifies a character set (specific to a country) which is, for example, to be activated when files are being created. The specified CCS should be an EBCDIC character set.
PHYSICAL-ALLOCATION = *NOT-ALLOWED / *ALLOWED
Governs whether the user is allowed to perform physical space allocation (direct allocation) for the pubset.
PHYSICAL-ALLOCATION = *NOT-ALLOWED
The user is no longer allowed to perform physical space allocation for the pubset.
PHYSICAL-ALLOCATION = *ALLOWED
The user is now allowed to perform physical space allocation for the pubset.
CRYPTO-SESSION-LIMIT = *STD / *MAXIMUM / <integer 0..32767>
Defines the maximum number of openCRYPT sessions within a BS2000 session. The number of openCRYPT sessions already used is set to 0 at the start of a BS2000.
CRYPTO-SESSION-LIMIT = *STD
Defines the maximum number of 128 openCRYPT sessions.
CRYPTO-SESSION-LIMIT = *MAXIMUM
Defines the maximum number of 32767 openCRYPT sessions.
NET-STORAGE-USAGE = *ALLOWED / *NOT-ALLOWED
Specifies whether the user may occupy space on Net-Storage volumes.
NET-STORAGE-USAGE = *ALLOWED
The user is permitted to use Net-Storage volumes. The space occupied on the Net-Storage volume is not counted toward the user's PUBLIC-SPACE-LIMIT.
NET-STORAGE-USAGE = *NOT-ALLOWED
The user is not permitted to use Net-Storage volumes.
NET-CODED-CHAR-SET = *STD / *ISO / *NO-CONVERSION / <name 1..8>
Defines which Net-Storage coded character set (NETCCSN) is to be used for node files on Net-Storage. A character set conversion is only performed for SAM node files.
NET-CODED-CHAR-SET = *STD
The setting is adopted from the NETCODE system parameter.
NET-CODED-CHAR-SET = *ISO
A suitable ISO character set is used. For details on character set conversion see the CREATE-FILE command or the “Introductory Guide to DMS” manual [13].
NET-CODED-CHAR-SET = *NO-CONVERSION
There is no code conversion for SAM node files.
NET-CODED-CHAR-SET = <name 1..8>
Name of the character set to be used. It should be an ASCII character set.
ACCOUNT-ATTRIBUTES = *PARAMETERS(...)
Specifications that are valid for only one account number of the user ID. The maximum number of account numbers per user ID is 60.
ACCOUNT = <alphanum-name 1..8>
Account number of the user ID, to which the following information refers.
CPU-LIMIT = *STD / *MAXIMUM / <integer 0..2147483647 seconds >
Total CPU time allocated to the user jobs under the specified account number.
CPU-LIMIT = *STD
The default value set in the SYSGJCPU system parameter (see the “Introduction to System Administration” [14]) is available.
CPU-LIMIT = *MAXIMUM
The time allotted the user is 2,147,483,647 CPU seconds.
SPOOLOUT-CLASS = 0 / <integer 0..255> / STD
Spoolout class for the first account number of the user ID
SPOOLOUT-CLASS = *STD
The default value set in the SYSGJCLA system parameter (see the “Introduction to System Administration” [14]) is available.
MAXIMUM-RUN-PRIORITY = *STD / <integer 30..255>
Specifies the highest priority that may be assigned jobs of the user ID (see note).
MAXIMUM-RUN-PRIORITY = *STD
The default value set in the SYSGJPRI system parameter (see the “Introduction to System Administration” [14]) is available.
MAX-ALLOWED-CATEGORY =
This operand defines which task attributes user jobs are allowed to attain.
If the user employs the TINF macro in his/her programs, a check is made in both the job class used by the job concerned and in the user catalog to see whether the right to use the task attribute TP was assigned to the user under the specified account number.
MAX-ALLOWED-CATEGORY = *STD
The tasks of the user can attain the task attributes BATCH and DIALOG.
MAX-ALLOWED-CATEGORY = *TP
The user jobs may attain the task attributes BATCH, DIALOG and TP.
MAX-ALLOWED-CATEGORY = *SYSTEM
All task attributes are permitted for the tasks of the user.
PRIVILEGE = *NO / *PARAMETERS(...) / list-poss(3): *NO-CPU-LIMIT / *START-IMMEDIATE /
*INHIBIT-DEACTIVATION
Job management authorization declarations.
PRIVILEGE = *NO
The user ID is not given any job management privileges.
PRIVILEGE = *PARAMETERS(...)
A sequence of authorizations is to be agreed upon.
NO-CPU-LIMIT = *NO / *YES
Declares whether the user receives the authorization to run batch jobs without time restrictions.
NO-CPU-LIMIT = *YES
The user ID receives the authorization to run batch jobs without time restrictions under the specified account number.
This applies even if the job class assigned to the job does not permit this start attribute.
If the user specified the CPU-LIMIT=*NO operand in the SET-LOGON-PARAMETERS or ENTER-JOB command and this function is authorized neither in the user catalog nor in the job class assigned to the job, the batch job is rejected with an error message.
In the case of tasks without a time limit, the user’s CPU account is not debited.
START-IMMEDIATE = *NO / *YES
Defines whether the use is authorized to use the job express function.
START-IMMEDIATE = *YES
The user is authorized to use the job express function. With this authorization batch jobs are started immediately, even if the class limit of the job class in which the job concerned is to be started has been reached.
This applies even if the definition of the job class does not permit this start attribute. If the EXPRESS function is not permitted either in the user catalog or in the job class definition, the batch job is accepted, but it is not started as an EXPRESS job.
INHIBIT-DEACTIVATION = *NO / *YES
Defines whether the user is authorized to inhibit deactivation.
INHIBIT-DEACTIVATION = *YES
The user ID is authorized to inhibit deactivation.
The user’s jobs are thus independent of the PRIOR function, by means of which jobs are placed in subordinate queues according to their system service requirements (macro time slice).
PRIVILEGE = *NO-CPU-LIMIT
The user is authorized to run batch jobs without time limitation under the specified account number.
PRIVILEGE = *START-IMMEDIATE
The user is authorized to use the job express function.
PRIVILEGE = *INHIBIT-DEACTIVATION
The user ID is authorized to inhibit deactivation.
POSIX-RLOGIN-DEFAULT = *NO / *YES
Defines whether the designated account number is to be used for POSIX remote login session accounting (the account number may likewise be used for BS2000 session accounting).
If the user entry does not include an account number for POSIX remote login session accounting, access to the system by remote login is not possible. Systems support personnel working under the TSOS user ID have access even without an account number.
LOGON-DEFAULT = *NO / *YES
Defines whether the designated account number is to be used as the default account number for BS2000 timesharing mode if no account number is specified in the case of dialog or batch access.
LOCK-USER =
Defines whether the user ID is to be locked after its creation.
LOCK-USER = *NO
The user ID is not locked.
The user has free access to the system after entering his ID.
LOCK-USER = *YES
The user ID is locked.
The system support staff is thus able to assign all desired attributes to the user ID and block premature access by the user.
If the product SECOS is used, the system support staff can achieve integration in the group structure and the protective mechanisms for the password in this way without thereby permitting SET-LOGON-PARAMETERS on the ID in question.
The access lock must be explicitly canceled (UNLOCK-USER command) by the system support staff.
Return codes
(SC2) | SC1 | Maincode | Meaning |
|---|---|---|---|
0 | CMD0001 | No error | |
2 | 0 | SRM6001 | Command executed with a warning |
1 | SRM6010 | Syntax error | |
32 | SRM6020 | System error during command processing | |
64 | SRM6040 | Semantic error | |
130 | SRM6030 | Command cannot temporarily be executed |
Notes
Task scheduling priorities
The task scheduling priorities (30-255) for job control are defined:
- in the user catalog (ADD-USER command, MAXIMUM-RUN-PRIORITY operand)
- in the job class definition (JMU statement DEFINE-JOB-CLASS, RUN-PRIO operand; in addition to the default priority, a maximum priority can be defined)
If the user specifies a task scheduling priority in the SET-LOGON-PARAMETERS or ENTER-JOB command, then this priority is checked both in the user catalog and in the job class assigned to the job. An example is given below:
Priority in the SET-LOGON-PARAMETERS or ENTER-JOB command
Priority in the job class
Priority in the user catalog
Priority with which the job is started
DEFAULT
MAXIMUM
200
190
150
180
200
150
190
150
180
150
130
190
150
180
190
-
190
150
180
190
130
190
150
130
130
130
190
150
200
200
200
190
NO
180
200
170
190
NO
180
190
130
190
NO
180
190
-
190
NO
180
190
If the priority specified by the user in the SET-LOGON-PARAMETERS or ENTER-JOB command is worse than the best priority of the job class and in the user catalog (i.e. allowed either in the job class or in the user catalog), the job is started with the priority specified by the user. If the priority specified by the user in the SET-LOGON-PARAMETERS or ENTER-JOB command is better than the priorities of the job class and in the user catalog (i.e. not allowed either in the job class or in the user catalog), the job is given whichever is worse, the default priority of the job class or the priority in the user catalog.
If the user does not specify any priority in the SET-LOGON-PARAMETERS or ENTER-JOB command, the job is started with the default priority.
- Threshold values for files, job variables, temporary memory and address space
These threshold values are defined for the user ID using the FILE-NUMBER-LIMIT, JV-NUMBER-LIMIT, TEMP-SPACE-LIMIT and ADDRESS-SPACE-LIMIT operands. The user ID TSOS may exceed the defined limits. All other user IDs must always comply with the defined limits.
When creating or modifying a user ID, a global user administrator may specify values which exceed the group potential of these limit values.
Example
/add-user user-id=cognibs3,prot-attr=(logon-pass='8743ryz9',
pass-manag=*user-cha-only,tape-access=*read),
mail-addr=c'Abteilung Z8 Raum 55.105',
email-addr=c'alfred.holli@incognito.de,joachim.vogi@incognito.de,
(jk)johannes.kuli@incognito.de,(mr)mathias.reh@incognito.de',
pub-space-lim=20000,
account-attr=(account=acc00015,cpu-limit=10000,privil=*start-immed)
/show-user-attr cognibs3
%SHOW-USER-ATTRIBUTES --- PUBSET TK82 - USER COGNIBS3 2017-01-29 15:09:50 %------------------------------------------------------------------------------ %USER-ID COGNIBS3 PUBLIC-SPACE-USED 0 %GROUP-ID *UNIVERSAL PUBLIC-SPACE-LIMIT 20000 %DEFAULT-PUBSET TK82 PUBLIC-SPACE-EXCESS *NO %MAX-ACCOUNT-RECORDS 100 TEMP-SPACE-USED 0 %DEFAULT-MSG-LANGUAGE TEMP-SPACE-LIMIT 2147483647 % FILES 0 %PROTECTION-ATTRIBUTES... FILE-NUMBER-LIMIT 16777215 %LOGON-PASSWORD *YES JOB-VARIABLES 0 %PASSWORD-MGMT *USER-CHANGE-ONLY JV-NUMBER-LIMIT 16777215 %TAPE-ACCESS *READ RESIDENT-PAGES 32767 %FILE-AUDIT *NO ADDRESS-SPACE-LIMIT 16 % DMS-TUNING-RESOURCES *NONE %TEST-OPTIONS... CSTMP-MACRO-ALLOWED *NO %READ-PRIVILEGE 1 CODED-CHARACTER-SET EDF03IRV %WRITE-PRIVILEGE 1 PHYSICAL-ALLOCATION *NO %MODIFICATION *CONTROLLED USER-LOCKED *NO % CRYPTO-SESSION-USED 0 %AUDIT... CRYPTO-SESSION-LIMIT 128 %HARDWARE-AUDIT *ALLOWED NET-STORAGE-USAGE *ALLOWED %LINKAGE-AUDIT *ALLOWED NET-CODED-CHAR-SET *ISO % %PROFILE-ID *NONE %MAIL-ADDRESS Abteilung Z8 Raum 55.105 %EMAIL-ADDRESS alfred.holli@incognito.de, % joachim.vogi@incognito.de, % (jk)johannes.kuli@incognito.de, % (mr)mathias.reh@incognito.de % %+---------+-----------+---------+--------+------------+-------+------+------+ %!ACCOUNT-#! CPU-LIMIT !SPOOLOUT-!MAX-RUN-!MAX-ALLOWED-!NO-CPU-!START-!INHIB-! %! ! ! CLASS !PRIORITY! CATEGORY ! LIMIT ! IMMED! DEACT! %+---------+-----------+---------+--------+------------+-------+------+------+ %! ACC00015! 10000! 0 ! 255 ! STD ! NO ! YES ! NO ! %+---------+-----------+---------+--------+------------+-------+------+------+ %DEFAULT-ACCOUNT-# FOR LOGON: *NONE %DEFAULT-ACCOUNT-# FOR REMOTE-LOGIN: *NONE % %DEFAULT-JOB-CLASS FOR BATCH-JOBS: JCB05000 %DEFAULT-JOB-CLASS FOR DIALOG-JOBS: JCDSTD %DEFAULT-JOB-CLASS FOR POSIX-JOBS: JCPOSSTD %LIST OF JOB-CLASSES ALLOWED: %JCBNACHT JCBNAMCM JCBNAMCP JCBSHUT JCB00050 JCB00200 JCB02000 JCB05000 %JCB10000 JCB32000 JCDSTD %------------------------------------------------------------------------------ %SHOW-USER-ATTRIBUTES END OF DISPLAY FOR USER COGNIBS3 ON PUBSET TK82 /