|
Users and userclass definition |
|
|
Users are defined with the "define user" directive. Each "define user" creates an user entry in the SNT, providing all the attributes and authorizations for the users. When a large number of users must be defined, administrators may need to group users into classes sharing the same authorizations and/or attributes (i.e. OPID, OPKEY). This task is achieved by means of the userclass definition. An userclass is a collection of user attributes: all the users belonging to the userclass inherit the attributes defined in it. Those attributes defined in the user's definition too (define user) override the userclass's ones. The userclass is defined with the "define userclass" directive. Default user XCICS/TS requires a default user to identify the operator when connected, before he does a sign-on operation. This user must be defined as usual with a "define user" directive and declared to XCICS/TS with the "set default_user" directive (see example below). System users XCICS/TS requires two system users: the sysuser to execute the background task, and the tduser to execute the task triggered by Transient Data queues. These users may be manually defined with a standard "define user" directive including the "sysuser" or "tduser" parameter in the declaration. If they are not defined, XCICS/TS automatically creates the $$DFHSYS and $$DFHTDQ users with full authorizations. A practical example # |