|
Use the CHANGE subcommand to change data (nodes and user attributes)
in entries in the UADS and user IDs in the broadcast data set; or
to change only the requirements of procedures.
When making changes to the UADS, CHANGE ensures that no identical
(redundant) paths will exist in the UADS structure after the change
operation. On the other hand, if an ‘impossible merge’ situation arises
(identical procedure names associated with different data), CHANGE
cannot determine which data to retain. Therefore, it terminates processing
of the current structure and issues an explanatory message.
The syntax of the CHANGE subcommand of ACCOUNT to change nodes
and user attributes within entries in the UADS and user IDs in the
broadcast data set is:
- The first parameter (enclosed within parentheses) is the positional parameter
(nodelist); all others are keyword parameters.
- To change a user ID in the UADS and the broadcast data set, explicitly
specify userid as the only item in the positional
parameter and specify userid in the DATA
parameter. (The specification c (*) data (userid) is
not valid.)
- To change a password, account number, or procedure name under
a user ID (or user IDs), specify the item as the final item in the
positional parameter, and specify the corresponding item in the DATA
parameter.
- If you created (with the ADD subcommand) an entry in the UADS
with an asterisk (*) specification for password
and/or account number, you cannot change the asterisk-specification
to an actual password and/or account number under that userid.
- If you change MAXSIZE, the specification of a region size smaller
than an existing SIZE for any procedure under a user ID is not valid.
- The specification of SIZE and/or UNIT is valid only if you specify proc in
the DATA parameter.
- userid
- Change either this user ID in the UADS and the broadcast data
set, or data under this user ID
- value:
- 1-7 alphanumeric characters, beginning with an alphabetic or special
character
If you plan to send data through a JES2 network
using the TRANSMIT/RECEIVE commands, do not define a user ID
that: - is the same as the name of an external writer
- or begins with any of the following characters: R, RM, RMT.
In the broadcast data set, the effect of c userid1 data (userid2) is
as follows: - If userid1 and userid2 do
not exist, add userid2 as a new
entry.
- If userid1 exists and userid2 does
not, delete userid1; add userid2 as
a new entry; chain messages for userid1 to userid2.
- If userid1 and userid2 both
exist, delete userid1; chain
messages for userid1 to userid2.
- *
- Change data under all userids
- password
- Change either this password or node(s) under this password
- value:
- 1-8 alphanumeric characters
- *
- Change node(s) under all passwords
- acct_nmbr
- Change either this account number or node(s) under this account
number
- value:
- 1-40 EBCDIC characters excluding the following characters:
- blank
- comma
- semicolon
- apostrophe
- tab
- *
- Change node(s) under all account numbers
- proc
- Change the procedure name
- value:
- 1-8 alphanumeric characters, beginning with an alphabetic or special
character
- *
- Change all procedure names
- DATA
- Change
specific nodes in an existing entry (or entries)
- userid
- The new user ID
- value:
- 1-7 alphanumeric characters, beginning with an alphabetic or special
character
- password
- The new password
- value:
- 1-8 alphanumeric characters
- acct_nmbr
- The new account number
- value:
- 1-40 EBCDIC characters excluding the following characters:
- blank
- comma
- semicolon
- apostrophe
- tab
- proc
- The new procedure name
- value:
- 1-8 alphanumeric characters, beginning with an alphabetic or special
character
- SIZE
- The
assigned minimum region size for the new procedure if
- you do not specify the region size in the LOGON pre-prompt exit
routine
- this user does not specify the SIZE parameter on the LOGON command
In addition, if the preceding two conditions are true and
you do not specify SIZE or specify SIZE(0), TSO/E assigns a region
size based on the value of the REGION= parameter on the EXEC statement
in the user's logon procedure or a default size based on JES initialization
parameters.
If you specify in SIZE a minimum region size that
is larger than MAXSIZE for this user ID, TSO/E sets SIZE equal to
MAXSIZE. - rgn_size
- Number of 1024-byte units of virtual storage for this user's private
area
- value:
- an integer in the range 0-2096128
- UNIT
- Default
specification of device type when this user allocates new data sets
but does not specify a volume. (Data sets allocated using the catalog
are an exception. See the ALLOCATE command in z/OS TSO/E Command Reference.)
Note: The default specification for UNIT in the UADS is related to
the logon procedure selected in the foreground, not to the user ID.
For jobs submitted in the background, TSO/E does not use the
default specification.
- name
- The new name of a device or group of devices (for example, SYSDA)
- value:
- 1-8 alphanumeric characters
- USERDATA
- Change
optional data under this user ID. The 2-byte field in the UADS is
a four-digit hexadecimal number that represents the contents of data.
This hexadecimal data can be used by this user's programs.
- data
- The new optional data
- value:
- 4 EBCDIC characters (valid characters 0-9 and A-F)
- ACCT
- Allow
this user to use the ACCOUNT command
- NOACCT
- Do
not allow this user to use the ACCOUNT command
- DEST
- The
default remote destination for processing dynamically allocated SYSOUT
data sets. The establishment of this default eliminates the need
for ROUTE statements in this user's submitted batch jobs. The user
can override the default destination through the use of the ALLOCATE,
FREE, and other commands.
Note: If a user submits a job at a node
other than that specified in the DEST parameter, that user will not
be able to view held output.
- id
- The default destination (remote workstation)
- value:
- 1-7 alphanumeric characters, beginning with an alphabetic or special
character
- NODEST
- This
user must explicitly route SYSOUT data sets for processing
- JCL
- Allow
this user to use the SUBMIT, STATUS, CANCEL, and OUTPUT commands
- NOJCL
- Do
not allow this user to use the named commands
- MAXSIZE
- The
maximum region size that this user may request at logon. If you do
not specify MAXSIZE or specify MAXSIZE=0, TSO/E assumes NOLIM.
- region
- The number of 1024-byte units of virtual storage for this user's
private area
- value:
- an integer in the range 0-2096128
- NOLIM
- Do
not restrict this user to a maximum region size at logon
- MOUNT
- Allow
this user to issue dynamic allocation requests that result in the
need for volume mounting
The volume request can be either explicit
(for example, when this user issues the ALLOCATE command) or implicit
(for example, when this user issues commands that cause the allocation
of temporary space).
This user will sit in a "locked out" condition
at the terminal until the operator responds to the request. Therefore,
this user should send a message to the operator prior to issuing the
command requesting a particular volume.
- NOMOUNT
- Ignore
the issuance by this user of dynamic allocation requests that result
in the need for volume mounting
- OPER
- Allow
this user to use the OPERATOR command
- NOOPER
- Do
not allow this user to use the OPERATOR command
- HOLD
- Place
the job output from a job submitted with the HOLD keyword on the SUBMIT
command in the hold queue
- class
- Assign a default held output class to the submitted job
- value:
- 1 alphanumeric character, excluding special characters
- NOHOLD
- Assign
a default output class to the submitted job as indicated by the MSGCLASS
parameter
- JOBCLASS
- Assign
a default job class to a job submitted without a JOB statement
- j_class
- The default job class
- value:
- 1 alphanumeric character, excluding special characters
- NOJOBCLASS
- JES2
or JES3 assigns the default job class to a job submitted without a
JOB statement
- MSGCLASS
- If
this user submits a job without a JOB statement or without the specification
of the MSGCLASS= parameter on the JOB statement; and specifies the
NOHOLD keyword on the SUBMIT command, assign the job to a default
output class.
- o_class
- The default output class
- value:
- 1 alphanumeric character, excluding special characters
- NOMSGCLASS
- If
this user submits a job without a JOB statement or without the specification
of the MSGCLASS= parameter on the JOB statement; and specifies the
NOHOLD keyword on the SUBMIT command, JES2 or JES3 assigns the default
output class
- SYSOUT
- If
this user does not specify class with the
SYSOUT keyword on an ALLOCATE command, assign a default SYSOUT class
- s_class
- The default SYSOUT class
- value:
- 1 alphanumeric character, excluding special characters
- NOSYSOUT
- If
this user does not specify class with the
SYSOUT keyword on an ALLOCATE command, JES2 or JES3 assigns the default
SYSOUT class
- RECOVER
- Allow
this user to use the EDIT recovery facility
- NORECOVER
- Do
not allow this user to use the EDIT recovery facility
- PERFORM
- Allow
this user to explicitly request a performance group (or groups) at
logon
- perf_group
- The identification of the performance group (or groups)
- value:
- an integer in the range 1-255
Note: If you write an installation control specification for TSO/E
users, the following applies to the interpretation of the PERFORM
parameter under the stated conditions:
- TSO/E bypasses the performance group(s) in the UADS. When a user
logs on, the performance group TSO/E assigns depends upon the values
you specify for PGN and OPGN in the installation control specification
and the value the user specifies at logon:
- logon PERFORM value = OPGN value: accept logon value
- logon PERFORM value ¬= OPGN value: assign PGN value
- logon PERFORM value = PGN value: accept logon value
- logon PERFORM value ¬= PGN value (no OPGN value specified): assign
PGN value
- NOPERFORM
- Do
not allow this user to request a performance group
The syntax of the CHANGE subcommand of ACCOUNT to change only
the requirements of a procedure (or procedures) is:
- The first parameter (enclosed within parentheses) is the positional parameter
(nodelist); all others are keyword parameters.
- userid
- Change the requirements of a procedure (or procedures) under this
user ID
- value:
- 1-7 alphanumeric characters, beginning with an alphabetic or special
character
- *
- Change the requirements of a procedure (or procedures) under all
user IDs
- password
- Change the requirements of a procedure (or procedures) under this
password
- value:
- 1-8 alphanumeric characters
- *
- Change the requirements of a procedure (or procedures) under all
passwords
- acct_nmbr
- Change the requirements of a procedure (or procedures) under this
account number
- value:
- 1-40 EBCDIC characters excluding the following characters:
- blank
- comma
- semicolon
- apostrophe
- tab
- *
- Change the requirements of a procedure (or procedures) under all
account numbers
- proc
- Change the requirements of this procedure
- value:
- 1-8 alphanumeric characters, beginning with an alphabetic or special
character
- *
- Change the requirements of all procedures under the specified
nodes
- SIZE
- The assigned
minimum region size for the new procedure(s) if
- you do not specify the region size in the LOGON pre-prompt exit
routine
- this user does not specify the SIZE parameter on the LOGON command
In addition, if the preceding two conditions are true and
you do not specify SIZE or specify SIZE(0), TSO/E assigns a region
size based on the value of the REGION= parameter on the EXEC statement
in the user's logon procedure or a default size based on JES initialization
parameters.
If you specify in SIZE a minimum region size that
is larger than MAXSIZE for this user, TSO/E sets SIZE equal to MAXSIZE.
- rgn_size
- Number of 1024-byte units of virtual storage for this user's private
area
- value:
- an integer in the range 0-2096128
- UNIT
- Change
the default specification of device type when this user allocates
data sets but does not specify a volume. (Data sets allocated via
the catalog are an exception. See the ALLOCATE command in z/OS TSO/E Command Reference.)
Note: The default specification for UNIT in the UADS is related to
the logon procedure selected in the foreground, not to the user ID.
For jobs submitted in the background, TSO/E does not use the
default specification.
- name
- The name of a device or group of devices (for example, SYSDA)
- value:
- 1-8 alphanumeric characters
|