 |
» |
|
|
|
ABORT | |
Aborts the current program or operation suspended by BREAK.
(Native Mode) The ABORT command terminates a process that has been suspended
by pressing the Break key. Programs do not terminate while critical system code
is executing on their behalf, but terminate immediately following
execution of that code. The ABORT command is available only from a session and only
during BREAK, but it does not disrupt the session. Some operations
abort immediately upon entering BREAK without requiring the ABORT command. An ABORT command results in the job control word (JCW)
being set to the SYSTEM 0 state. For a discussion of job control words,
refer to the SETJCW command. This command may be issued from a session (in BREAK only).
It is not available from a job or a program. Pressing Break has no effect on this command. To abort the current program or operation, press Break. When the colon prompt (:) appears, enter: The system then displays the message PROGRAM ABORTED PER USER REQUEST and redisplays the colon prompt (:). - Commands
RESUME, SETJCW - Manuals
None
ABORTIO/ =ABORTIO | |
Aborts a single pending I/O request for a device. - ldev
The logical device number of the device for which
you intend to abort one pending I/O request.
You may issue the ABORTIO command from a session, job, program, or in BREAK.
Pressing Break has no effect on this command. It is executable only from
the console unless distributed to users with the ALLOW or ASSOCIATE command. The =ABORTIO console command cannot be issued from a job. To abort a pending I/O request for logical device 53, enter: It is necessary to issue several ABORTIO commands to abort all pending I/O operations on
a spooled device, as shown below: STOPSPOOL 5
11:20/31/SP#5/STOPPED
11:20/31/LDEV#5 NOT READY
REFUSE 5
ABORTIO 5
ABORTIO 5
11:21/40/NO I/O TO ABORT FOR DEVICE 5 |
- Commands
SHOWDEV - Manuals
Performing System Operation Tasks
ABORTJOB/ =ABORTJOB | |
Aborts a job or session. ABORTJOB { #Jnnn #Snnn [jobname,] user.acct } =ABORTJOB { #Jnnn #Snnn [jobname,] user.acct } - #Jnnn
A job number. - #Snnn
A session number. - jobname
The name of the job, as identified by the SHOWJOB command. - user
A user name. - acct
An account name.
The ABORTJOB command terminates the designated job or session,
and displays the following message on the job/session list device: SESSION ABORTED BY SYSTEM MANAGEMENT |
If you use the [jobname,]user.acct form of the command when
there is more than one job or session executing under that name,
MPE/iX selects which job/session to abort. Therefore, to exercise
more precise control when aborting jobs or sessions, use the #Jnnn or #Snnn form of the ABORTJOB command. Although the job/session is abnormally terminated,
log records are issued, and CPU-times and connect-times are updated.
Any I/O activity, such as printing or file storage, is terminated. The ABORTJOB command can be applied to waiting and scheduled
jobs, as well as to executing jobs. If the spooler input file ($STDIN) for a batch job has been created and not yet
opened (in other words, the job is in the WAIT state), the entire
file is deleted. If the ABORTJOB command is issued before the output spoolfile
is complete, only that portion of the file already spooled is printed,
along with an error message indicating that the job was aborted.
If a request is pending at the system console, it is automatically
terminated by the ABORTJOB/=ABORTJOB command and the following message appears on the
system console: time/#Snnn/pin/REQUEST REQUIRING OPERATOR REPLY FOR PIN #nn HAS BEEN ABORTED |
When the ABORTJOB command is successful, a logoff message is displayed
on the console, indicating that the job has been aborted, as shown
in the example below: ABORTJOB #S9
11:20/#S9/34/LOGOFF ON LDEV #77 |
The standard error message that appears when a request is
manually terminated by entering Y in response to =REPLY (or REPLY) is displayed on the user's terminal: SESSION ABORTED BY SYSTEM MANAGEMENT |
The =ABORTJOB command may be used at the physical console if ABORTJOB is ineffective. Refer to the "Use" section of
this command. To terminate session number 139, enter: ABORTJOB #S139
17:10/#S139/34/LOGOFF ON LDEV #62 |
To terminate job number 9, enter: ABORTJOB #J9
20:18/#J9/26/LOGOFF ON LDEV #10 |
In both of the preceding examples, the LOGOFF ON LDEV # messages indicates that ABORTJOB command was successfully executed. To terminate session 6, which has a pending device allocation
message, enter: ?17:00/#S6/23/LDEV# FOR "SCRTAPE" ON TAPE (NUM)?
ABORTJOB #S6
17:10/#S6/120/REQUEST REQUIRING OPERATOR REPLY FOR
PIN 23 HAS BEEN ABORTED
17:10/#S6/120/LOGOFF ON LDEV #58 |
- Commands
ALTJOB, BREAKJOB, JOBFENCE, JOBSECURITY, RESUMEJOB, SHOWJOB, STREAM - Manuals
Performing System Operation Tasks
ABORTPROC | |
The ABORTPROC command aborts the specified process(es). This
command requires OP or SM capability. ABORTPROC [ [PIN=]{pinspec }] {(pinspec
[,pinspec ]...)} [;SYSTEM] - pinspec
The process(es) to abort. This is a required parameter.
The syntax for pinspec is: [#P]pin[.tid]where
PIN is the Process ID number and TID is an optional thread ID number.
A leading "#P" is optional.To abort more than one process, a list
of PINSPECs can be specified. The list is enclosed in parenthesis
and individual PINSPECs are separated by commas. If a list is specified
it is processed in order, from left to right. ABORTPROC stops processing
the list if an error is detected. Duplicate PINs are not detected.Although
a PIN value of zero has meaning in the SHOWPROC and ALTPROC commands,
it is invalid in ABORTPROC. To kill yourself use the HPPIN variable,
e.g., ABORTPROC !hppinAborting detached system processes requires
SM capability as well as specifying the SYSTEM option. - SYSTEM
The SYSTEM option is necessary if the target process
is a detached system process. SM capability is required to use
the SYSTEM option.MPE/iX supports 8 process types (shown below).
Every process has a process type. Processes with a process type
greater than or equal to four (4) are considered system processes.
System processes are not abortable unless they have a process type
of six (6), indicating they are "detached". Process
Type
Abortable Restrictions -----------------------------------------------
0 User Y
SM or OP capability.
1
Son Y
SM or OP capability.
2
Usermain Y SM or OP capability.
3
reserved n/a n/a
4
System N Not
Abortable! 5 Detached Y
Must specify ;SYSTEM.
SM
capability is required.
6
JSMAIN N Not Abortable!
7
reserved n/a
n/a Processes
with a process type of 0, 1 or 2 are considered user processes,
and are abortable by any user with SM or OP capabilities. The
Command Interpreter (CI) process for all jobs and sessions
has a process type of two. Any process that is an immediate
child of a CI process has a process type of one. Processes
which are descendants of processes with process type
1 or 0, have a process type of 0. If
a user specifies the SYSTEM option, and the process is not a system
process (process type < 4), the SYSTEM option is silently
ignored.
The ABORTPROC command attempts to abort the specified process(es)
and all of their children processes. MPE/iX currently does not
support a means for children processes to survive the death of their
parent process. If one or more child processes cannot be aborted, their
parent process cannot be terminated either.There are specific circumstance
where a process is not abortable. Examples discussed below involve
"critical" processes and session processes in break mode. The MPE/iX Operating System uses a mechanism known as SETCRITICAL
to prevent a process from being aborted. The SETCRICIAL method
is used to protect the integrity of system data structures. A process
that is SETCRITICAL cannot be aborted. It is normal for all processes
to periodically be SETCRICIAL (e.g., when executing system code),
and they will RESETCRITICAL when it is safe for them to be aborted.
The ABORTPROC command works in conjunction with the SETCRITICAL
mechanism. It is designed so that it will never abort a process
which is SETCRICIAL. If a process is critical, ABORTPROC will notify
the process that it should abort as soon as it is possible to terminate
safely. If the target process, or any of its children processes, are
in break mode they cannot be aborted, and an error is reported.
This is due to the MPE implementation of break, and because all
processes in the same session process tree share the same terminal
LDEV. The target process needs to be resumed before it can be aborted
by the ABORTPROC command. The one exception is when the target
process is the usermain process, typically the CI. In this case
it is abortable by ABORTPROC, even when it is in break mode. When ABORTPROC fails to fully terminate the process the target
process is marked as having an "abort pending". Processes with
aborts pending are terminated when the condition that prevented
the successful abort is resolved. When ABORTPROC is used on a process
that is already marked as dying, a CI warning is reported. - Commands
ABORTJOB, ALTPROC, BREAKJOB, RESUME, SHOWPROC - Manuals
MPE/iX Intrinsics Reference Manual
ACCEPT | |
Permits a designated device to accept jobs/sessions and/or
data. ACCEPT [ JOBS | DATA ] ,ldev The operator or system supervisor uses this command to designate
which devices may be used to initiate jobs or sessions and/or data.
When a device is configured as an accepting device, MPE/iX automatically
scans the first input record for a valid JOB, HELLO, or DATA command. This feature, called auto-recognition,
allows users to access the device without specifically requesting
use of the device with a message to the system console. If you explicitly specify the JOBS parameter, the ACCEPT command is not executed unless the device is configured
as a default output device. This command may be issued from a session, job, program, or
in BREAK. Pressing Break has no effect on this command. It is executable only from
the console unless distributed to users with the ALLOW command. To permit logical device 19 to accept jobs and data, enter: ACCEPT 19
SHOWDEV 19
LDEV AVAIL OWNERSHIP VOLID ASSOCIATION
19 AVAIL |
To permit logical device 19 to accept jobs and
data, and to allow the device to be spooled, enter: ACCEPT 19
STARTSPOOL 19
11:12/31/SP#/SPOOLED IN
11:12/6/LDEV#19 NOT READY
SHOWDEV 19
DEV AVAIL OWNERSHIP VOLID DEN ASSOCIATION
19 SPOOLED SPOOLER OUT |
- Commands
REFUSE - Manuals
Introduction to MPE XL for MPE V System
Administrators System Startup, Configuration, and Shutdown
Reference Manual
ALLOCATE | |
Loads a compatibility mode program or procedure into virtual
memory. ALLOCATE [ PROCEDURE, | PROGRAM, ] name |
- PROCEDURE
The procedure in SL.PUB.SYS to be allocated. The default is PROGRAM. - PROGRAM
The program file to be allocated. Default. - name
The name of the program file or procedure to be
allocated.
This command may be issued from a session or program. Pressing Break has no effect on this command. System supervisor (OP)
capability is required to use this command. In addition to comma (,) a semicolon (;) and equal sign (=)
may be used as a delimiter. To allocate a procedure identified as PROC1, that resides in SL.PUB.SYS, enter: Program files residing in the nonsystem domain (a volume set)
are not allocated. Attempts to do so result in a LOAD ERR 92 message. - Commands
DEALLOCATE - Manuals
Introduction to MPE XL for MPE V Programmers
ALLOW | |
Grants a user access to a specific operator command. ALLOW FILE=formaldesignator[ ;SHOW] |
ALLOW[ @.@ | user.@ | @.acct | user.acct |
;COMMANDS=command [ ,command,...] |
- formal- designator
An ASCII file name, which may consist of one to
eight alphanumeric characters, beginning with an alphabetic character.
It may be fully or partially qualified and may be back-referenced
in a file equation. - SHOW
Lists input lines on $STDLIST. - @.@
Grants access to all users whether logged on or
not. - user.@
Grants access to a specific user in all accounts. - @.acct
Grants access to all users in a specific account. - user.acct
Grants access to a specific user in a specific account. - command
The names of those commands to which the user is
granted access.
The operator uses the ALLOW command to distribute specific operator commands
to system users. ALLOW specifies which users may execute operator commands,
and which commands they may execute. You may specify an indirect file with the ALLOW command, or you may execute ALLOW in subsystem mode. Each of these is explained
below. Using an indirect file to allow commands To allow commands via an indirect file, you create a file
that contains records identifying the users and accounts to whom
you are allowing operator commands, followed by the list of commands
allowed. Using an indirect file with the ALLOW command is particularly convenient for system administrators
since, once you make the file, you can reuse it to disallow the
set of commands (via the DISALLOW command) or to allow the same set of commands
again. Here is an example of an indirect file: EDITOR
HP32201A.07.17 EDIT/3000 TUES, MAY 29, 1994, 5:08 PM
(C) HEWLETT-PACKARD CO. 1985
/ADD
1 SUSAN.PAYROLL;COMMANDS=ALTJOB,ALTSPOOLFILE
2 JOHN.ACCTNG;COMMANDS=ALTJOB,DELETESPOOLFILE
3 //
...
/KEEP ALLOWTMP
/E |
Once you create an indirect file, you then issue the ALLOW command, using the ;SHOW parameter to display each command line as it is
executed from the file. For example: You may backreference the file with a file equation as follows: FILE BACKF=ALLOWTMP
ALLOW FILE=*BACKF;SHOW |
If the file has a lockword, enter it in the command line after
the filename. For example, "ALLOWTMP/password". Using ALLOW in subsystem mode To use the ALLOW command in subsystem mode, following these steps: Enter ALLOW, followed by Return. At the prompt (>), enter all of the commands you want to allow. When you finish, press Return and enter a colon : as the first character of the new line. (You may
also type EXIT.)
You cannot use the FILE= parameter in subsystem mode. The ALLOW subsystem will terminate if it encounters an error. You may allow commands only to users who are currently logged
on unless you specify the @.@ option, which allows commands to all users. (Since this option has obvious disadvantages,
you can remedy the situation by then issuing a DISALLOW command to disallow command use to selected users.) Additional capabilities granted to a user are valid only for
the duration of their current session. Once the user logs off, any
special capabilities previously assigned are no longer applicable. To determine which operator commands have been allowed globally
(that is, using the @.@ construct), or to a specific user, use the SHOWALLOW command. | | | |  | NOTE: Do not confuse console commands which are NOT allowable with operator commands. Operator commands are used in the day-to-day
operation of your system and are generally allowable. A console
command must be executed on the actual system console and must be
preceded by cntl-A. Some console commands have the same name as non-console
commands, an example is RECALL, which may be executed on any device. | | | | |
The following is a list of commands that may be allowed. ABORTIO HEADON RESUMESPOOL
ABORTJOB JOBFENCE SHUTQ
ACCEPT JOBSECURITY STARTSPOOL
ALLOW LDISMOUNT STOPSPOOL
ALTJOB LIMIT STREAMS
ALTSPOOLFILE LOG UP
CONSOLE MRJECONTROL VMOUNT
DELETESPOOLFILE OPENQ VSCLOSE
DISALLOW OUTFENCE VSOPEN
DISCRPS REFUSE VSRELEASESYS
DOWN REPLY VSRESERVESYS
DOWNLOAD RESUMEJOB WARN
HEADOFF SPOOLER WELCOME |
You may issue this command from a session, job, program, or
in BREAK. Pressing Break will terminate subsystem mode and produce an error message
but has no effect on commands already entered in subsystem mode.
This command is executable only from the console unless distributed
to users with the ALLOW command. To give the user USER.TECH the ability to execute the REPLY and ABORTIO commands, you would enter the following at the
system console: ALLOW USER.TECH;COMMANDS=REPLY,ABORTIO |
In subsystem mode, to give the user MGR.MANUALS the ability to execute the BREAKJOB command, you would enter the following at the
system console: ALLOW
>MGR.MANUALS;COMMANDS=BREAKJOB
>EXIT |
- Commands
DISALLOW, SHOWALLOW - Manuals
Performing System Operation Tasks
ALTACCT | |
Changes the attributes of an existing account. ALTACCT acctname [ ;PASS=[ password] ] [ ;FILES=[ filespace]] [ ;CPU=[ cpu]] |
[ ;CONNECT=[ connect] ] [ ;CAP=[ capabilitylist] ] [ ;ACCESS=[ (fileaccess)]] |
[ ;MAXPRI=[ subqueuename] ] [ ;LOCATTR=[ localattribute] ] |
[ ;ONVS=volumesetname] [ ;USERPASS=[ {REQ | OPT } ] ] (1) |
(1) The USERPASS parameter is only available if the HP Security
Monitor has been installed. - acctname
The name of the account to be altered. - password
The password to be assigned to the account. If you omit password, any existing password is removed. If you omit PASS=, any existing password is unchanged. - filespace
Disk storage limit, in sectors, for the permanent
files in the account. The filespace limit cannot be less than the number of sectors currently
in use for the account. - cpu
The limit on cumulative CPU-time, in seconds, for
the account. This limit is checked only when a job or session is
initiated, and, therefore, never causes the job or session to abort.
The maximum value allowed is 2,147,483,647 seconds. You may set
the counter to zero with the RESETACCT command. - connect
The limit on total cumulative session connect-time,
in minutes, allowed the account. This limit is checked at logon.
Every time the process terminates the counter is updated. The maximum
value allowed is 2,147,483,647 minutes. You may reset the counter
to zero with the RESETACCT command. - capabilitylist
Either 1) a list of capabilities, separated by commas,
permitted the account, or 2) a list of additions and/or deletions
to be applied to the account's existing set of capabilities. Additions
and deletions are specified by a "+" or "-" immediately followed
by the capability to add or delete, separated by commas. If "+"/"-" is to be specified in the list, then the list must
begin with "+" or "-". For example, CAP=+MR,-PH is legal, but CAP=MR,-PH is not. It is not necessary to prefix each capability
to be added or deleted with "+" / "-", as the occurrence of "+"
/ "-" indicates an action that remains in effect until the indicator
changes. For example, CAP=+MR,PH,-PM,DS is equivalent to CAP=+MR,+PH,-PM,-DS If a capability is removed at the account level, users within
the account are also denied that capability. No explicit change
to the user's capabilities is necessary. Similarly, if a capability
is returned to the account, any users with that capability regain
it automatically. Each capability is denoted by a two letter mnemonic, as follows: System Manager = SM
Account Manager = AM
Account Librarian = AL
Group Librarian = GL
Diagnostician = DI
System Supervisor = OP
Network Administrator = NA
Node Manager = NM
Save Files = SF
Access to Nonshareable
I/O Devices = ND
Use Volumes = UV
Use Communication
Subsystem = CS
Programmatic Sessions = PS
User Logging = LG
Process Handling = PH
Extra Data Segments = DS
Multiple RINs = MR
Privileged Mode = PM
Interactive Access = IA
Batch Access = BA |
Default is AM, AL, GL, SF, ND, IA, BA, except for the SYS account. The SYS account has no true default. It is assigned the
maximum account capabilities when the system is delivered and, under
normal circumstances, should not be altered. If a capability is taken away from an account, it is unavailable
to users in that account. However, users are not affected by this
change until they log off and then log back on. - fileaccess
The restrictions on file access pertinent to this
account. Default is R,L,A,W,X:AC, entered as follows: ([{ R | L | A | W | X } [ ,...] : { ANY | AC } ] [ ;...] ) |
The R, L, A, W, and/or X specify modes of access by types
of users (ANY and/or AC ) as follows: R = READ
L = LOCK
A = APPEND
W = WRITE
X = EXECUTE |
LOCK allows exclusive access to the file. APPEND implicitly specifies LOCK. WRITE implicitly specifies APPEND and LOCK. The user types are specified as follows. ANY = Any user
AC = Member of this account only |
- subqueuename
Name of the highest priority subqueue that can be
requested by any process of any job/session in the account, specified
as AS, BS, CS, DS, or ES. When you specify ;MAXPRI= without a value, subqueuename defaults to CS.
| | | |  | CAUTION: User processes executing in the AS or BS subqueues
can deadlock the system. If you assign these subqueues to nonpriority
processes, other critical system processes may be prevented from
executing. Exercise extreme caution when choosing subqueues. | | | | |
- localattribute
Local attribute of the account, as defined at the
installation site. This is a double-word bit map, of arbitrary meaning,
that might be used to further classify accounts. While it is not
involved in standard MPE/iX security provisions, it is available
to processes through the WHO intrinsic. Programmers may use localattribute in their own programs to provide security. Default
is double word 0 (null). - volume- setname
The MPE/iX volume set in which the account is to
be altered. This volume set must be already defined and recognized
by the system. When ONVS=volumesetname is specified, the volume set directory is assumed. When ONVS= is specified without volumesetname, the system directory is assumed. MPE/iX volume set names consist of from 1 to 32 characters,
beginning with an alphabetic character. The remaining characters
may be alphabetic, numeric, the underscore, or periods. This parameter only works with the FILES parameter (all other parameters are ignored). - REQ
USERPASS=REQ specifies that all users in the account
must have a non-blank password. It is available only if the HP Security
Monitor has been installed. - OPT
USERPASS=OPT specifies that users in this account
may or may not have passwords. If you do not use the USERPASS parameter,
the old value remains. It is available only if the HP Security Monitor
has been installed.
The system manager uses the ALTACCT command to change the attributes of an existing account.
You may enter multiple keywords on a single command line as shown
in "Examples." When you change one capability in a capabilitylist that contains several nondefault values, you must
specify the entire new %capabilitylist. When you omit an entire keyword parameter group
from the ALTACCT command, that parameter remains unchanged for
the account. When you include a keyword, but omit the corresponding parameter
(for example, PASS= Return), the default value is assigned. Table 2-2 lists the default
values for the ALTACCT command. Table 3-1 “Default Parameters for the ALTACCT Command” shows the defalut parameters for
the ALTACCT Command. Table 3-1 Default Parameters for the ALTACCT Command | Parameter | Default Values |
|---|
| password | No password | | filespace | Unlimited | | cpu | Unlimited | | connect | Unlimited | | capabilitylist | AM, AL, GL, SF, ND, IA, BA (All
accounts except SYS) | | | SM, AM, AL, GL, DI, OP, SF, ND,
PH, DS, MR, PM (SYS account only) | | fileaccess | (R,A,W,L,X:AC) (All accounts except SYS) | | | (R,X:ANY;A,W,L:AC) (SYS account only) | | subqueuename | CS subqueue | | localattribute | 0 (null) |
Any value changed with the ALTACCT command takes effect the next time MPE/iX is requested
to check the value. If an attribute is removed from an account while
users are logged on, they are not affected until they log off their
current job or session and log on again. MPE/iX does not automatically
generate a message informing users of the change; it is your responsibility
to warn account members in advance of any changes. If you take a capability
away from an account, all account members and groups within the
account are denied the capability the next time that they log onto
the account. You cannot remove system manager (SM) capability from the SYS account or account manager (AM) capability from
any account. From within any account, you can remove AM capability
from all but one (the last) of the users assigned it. It is possible,
however, to remove AM capability from all users in an account, but
only if you do so from another account that has SM capability. | | | | | NOTE: If you specify volume-related commands or parameters
for a volume set that is not currently mounted, or for an account
that does not exist, MPE/iX returns an error message. | | | | |
This command may be issued from a session, job, program, or
in BREAK. Pressing Break has no effect on this command. System manager (SM) capability
is required to use this command. To change an account named AC2 so that its password is GLOBALX, and its filespace is limited to 50,000 sectors, enter: ALTACCT AC2;PASS=GLOBALX;FILES=50000 |
To change the password and the file space of an account called MALCHIOR in the volume set TIME_LORD, you need to issue two commands: ALTACCT MALCHIOR;PASS=OMSBOROS
ALTACCT MALCHIOR;ONVS=TIME_LORD;FILES=20000 |
You must specify the changes for the system volume set (the
first command) and for the volume set itself (the second command).
Specifying a volumesetname limits the user to changing only FILES in the second command. - Commands
ALTGROUP, ALTUSER, LISTACCT, LISTGROUP, LISTUSER, NEWACCT, NEWGROUP, NEWUSER, RESETACCT - Manuals
Performing System Management Tasks
ALTFILE | |
Changes the attributes of an existing file or directory. (Native
Mode) ALTFILE[ FILE=] filename [ ] ;OWNER=ownername] ] [ [ ;GROUPID=] POSIXgroupname] |
- filename
The filename of the object to be altered, specified
in either MPE or HFS syntax. The filename may name a file, hierarchical directory, root, MPE group
or account. Note that MPE groups or accounts can ONLY be named via
HFS (Hierarchical File System) syntax. Temporary files are not recognized. This is a required parameter. You may not use wildcards, back-reference
a file equation, or name a system-defined file such as $NULL. If the filename is in MPE syntax and it has a lockword, do
NOT include the lockword on the command line, or you will get an
error. - ownername
The name of the user who will become the owner (UID)
of filename. This ownername must already exist on the system. Default is for
the UID of the file to remain unchanged. Note that no qualification
is done on this name; it must be fully specified. To have the ownername upshifted, enclose it in quotes. - POSIXgroupname
The name of the POSIX group (GID) that this file
will belong to. This POSIXgroupname must already exist on the system. You cannot use
this parameter to change the GID of an MPE group or account. Default
is for the file to retain its previous GID. To have POSIXgroupname upshifted, enclose it in quotes.
You use the ALTFILE command to alter a file's characteristics. Currently
the attributes that you may modify are the owner (UID) and POSIX
group (GID) for a file, hierarchical directory, MPE group or account,
with the restriction that you may not alter the GID for MPE groups
or accounts. You must have the appropriate privilege to change the requested
attribute(s). In order to change the UID of a file, you must be
one of the following: The file's account manager (your logon
account matches the GID of the file and you have MPE/iX account
manager (AM) capability). In this case, ownername must specify a user belonging to the account manager's
logon account. A system manager (a user who has the MPE/iX system
manager (SM) user capability). In this case, ownername may specify any user existing in the user database.
In order to change the GID of a file, you must be one of the
following: The file owner (your logon name matches
the UID of the file). In this case, POSIXgroupname must specify your logon account. The file's account manager (your logon account matches
the GID of the file and you have the MPE/iX account manager (AM)
capability). In this case, POSIXgroupname must specify the account manager's logon account. A system manager (you have MPE/iX system manager
(SM) capability). In this case, POSIXgroupname may specify any GID existing in the group database.
You may issue the command once to modify multiple attributes.
If you specify multiple attributes, all modifications must succeed
for any to take effect. If you enter no attributes, the command
has no effect on the specified file. - Commands
ALTSEC, LISTFILE, RELEASE, SECURE - Manuals
Performing System Management Tasks
ALTGROUP | |
Changes one or more attributes of a group. ALTGROUP groupname [ .acctname] |
[ ;PASS=[ password]] [ ;CAP=[ capabilitylist] ] |
[ ;FILES=[ filespace] ] [ ;CPU=[ cpu] ] |
[ ;CONNECT=[ connect] ] [ ;ACCESS=[ (fileaccess)] ] |
[ ;ONVS=volumesetname] [ ;HOMEVS=volumesetname] |
- groupname
The name of the group whose attributes are to be
changed. - acctname
The name of the account in which the group is to
reside. System manager (SM) capability is required to use this parameter. - password
The password to be assigned to the group, which is used to verify
logon and access only. If the PASS parameter is omitted, no change is made. If PASS is used and password is omitted, the existing password is removed. If PASS is used and password is specified the existing password is changed; if there
is no existing password for the group a password is created. - capabilitylist
Either 1) a list of capabilities, separated by commas,
permitted this group, or 2) a list of additions and/or deletions
to be applied to the group's existing set of capabilities. Additions
and deletions are specified by a "+" or "-" immediately followed
by the capability to add or delete, separated by commas. If "+"/"-" is to be specified in the list, then the list must
begin with "+" or "-". For example, CAP=+MR,-PH is legal, but CAP=MR,-PH is not. It is not necessary to prefix each capability to be added
/ deleted with "+" / "-", as the occurrence of "+" / "-" indicates
an action that remains in effect until the indicator changes. For
example, CAP=+MR,PH,-PM,DS is equivalent to CAP=+MR,+PH,-PM,-DS. Each capability is denoted by a two letter mnemonic, as follows: Process Handling = PH
Extra Data Segments = DS
Multiple RINs = MR
Privileged Mode = PM
Interactive Access = IA
Batch Access = BA |
Default is IA, BA except for the PUB group of the SYS account which has no true default. It is assigned
the maximum group capabilities when the system is delivered and
should not normally be changed.
- filespace
Disk storage limit, in sectors, for the permanent
files of the group. A group's filespace cannot be set to a value greater than the corresponding limits
currently defined for the group's account. Nor can a group's filespace be set to a value less than the actual number of
sectors in use in that group. Default is unlimited file space. - cpu
The limit on the total cumulative CPU-time, in seconds,
for the group. This limit is checked only when a job or session
is initiated; the limit never causes a job/session to abort. The
maximum value allowed is 2,147,483,647 seconds. If the limit is
exceeded, users with account manager capability are warned when
logging on; other users are denied access. The CPU limit for a group cannot be set to a value greater
than the corresponding limit currently defined for the group's account.
Default is unlimited CPU-time. The counter may be set to zero with
the RESETACCT command. - connect
The limit on the total cumulative session connect-time,
in minutes, that the group is allowed. This limit is checked at
logon, and whenever the session initiates a new process. The maximum
value allowed is 2,147,483,647 minutes. If the limit is exceeded,
users with account manager capability are warned when logging on;
other users are denied access. A group's connect limit cannot be set to a value greater than
the corresponding limit currently defined for the group's account.
Default is unlimited connect-time. The counter may be set to zero
with the RESETACCT command. - fileaccess
The restriction on file access pertinent to this
group. Default is R,X:ANY;A,W,L,S:AL,GU for the public group (PUB); and R,A,W,L,X,S:GU for all other groups, where
R, L, A, W, and X specify modes of access by types of users (ANY,
AC, GU, AL, GL) as follows: R = READ
L = LOCK
A = APPEND
W = WRITE
X = EXECUTE
S = SAVE |
LOCK allows exclusive access. APPEND implicitly specifies LOCK. WRITE implicitly specifies APPEND and LOCK. The user types are specified as follows: ANY = Any user
AC = Member of this account only
GU = Member of this group only
AL = Account librarian user only
GL = Group librarian user only |
To specify two or more user or access types, separate them
by commas. - ONVS
A particular volume set for which the group attributes
are to be changed. The volume set must be already defined and recognized
by the system. If you specify ONVS, the only other parameter that works with it is
the FILES parameter. If volumesetname is omitted from the ONVS= parameter, or you omit ONVS, the operation is performed on the system volume
set. - HOMEVS
Changes the home volume set from the current set
to the set specified by volumesetname. You may do this only if the group on the current
home system volume set is empty and not in use; no one is logged
onto that group. - volume setname
The full name of the MPE/iX volume set, consisting
of from 1 to 32 characters, beginning with an alphabetic character.
The remaining characters may be alphabetic, numeric, the underscore,
or periods. You cannot change the home volume set if the home volume set
is the system volume set, and it contains files. If it contains
no file, you can change the home volume set. Consider the following when changing the home volume set: If the home volume set is the system
volume set, no files may exist in the group and the group may not
be in use (no users may be logged onto the group). Otherwise, the
command fails. If the current home volume set is not the system
volume set but the volume set is mounted, no files may exist in
the group on that volume set, and the group may not be in use. Otherwise,
the command fails. If the current home volume set is not the system
volume set and it is not mounted, it may be changed.
It is permissible to reassign a group to a different volume
set despite the presence of files belonging to groupname. This is possible provided that the old volume set
is not the system volume set and the groupname is not currently bound to its home volume set. This
binding occurs automatically when the volume set is mounted; it
occurs explicitly when the MOUNT or VSOPEN commands are invoked; it occurs implicitly when
the FOPEN intrinsic is invoked.
This command changes one or more attributes of a group. Multiple
parameters may be specified on a single command line as shown in
"Examples." When an entire parameter is omitted from an ALTGROUP command, the corresponding value for the group
remains unchanged. When a keyword is included but the corresponding
parameter is omitted (as in PASS = Return), the default value is assigned. Table 2-3 lists the default
values for the ALTGROUP command. Table 3-2 “Default Values for the ALTGROUP Command” shows the
default values for the ALTGROUP Command. Table 3-2 Default Values for the ALTGROUP Command | Parameter | Default Values | | |
|---|
| password | Null (No password) | | | | | IA, BA (except PUB.SYS) | | | | capabilitylist | PH, DS, MR, PM, IA, BA (PUB.SYS only) | | | | | Unlimited | | | | filespace | Unlimited | | | | cpu | Unlimited | | | | connect | R,A,W,L,X,S:GU (All groups except PUB) | | | | fileaccess | R,X:ANY;A,W,L,S:AL,GU (PUB group only) | | |
When a parameter is modified with the ALTGROUP command, it immediately takes effect in the directory.
It does not affect any active users with open files in the group,
until they log off their current session and log on to that username and group again. For this reason, notify all group
users of any planned changes in advance. | | | | | NOTE: If you specify volume created commands or parameters
for a volume set that is not currently mounted, or for an account
that does not exist, MPE/iX returns an error message. | | | | |
This command may be issued from a session, job, program, or
in BREAK. Pressing Break has no effect on this command. Account manager (AM) or
system manager (SM) capability is required to use this command. To assign a new password, PASS2, to a group named GROUPX, enter: ALTGROUP GROUPX;PASS=PASS2 |
To alter the group LEILA that resides on the volume set TIME_LORD: ALTGROUP LEILA;ONVS=TIME_LORD;FILES=10000 |
If the group LEILA contains no files, and no one is logged onto the
group, you may also alter the home volume set to DICHONDRITE, provided DICHONDRITE exists and is recognized by the system: ALTGROUP LEILA;HOMEVS=DICHONDRITE |
However, if LEILA does contain files, you cannot change the home
volume set for this group without creating a new group and transferring
those files to it. - Commands
ALTACCT, ALTUSER - Manuals
Volume Management Reference Manual
ALTJOB | |
Alters the attributes of waiting or scheduled jobs. (Native
Mode) ALTJOB[ JOB=] { #Jnnn #Snnn } |
[ ;INPRI=inputpriority] [ ;OUTDEV={ ldev devclass } ] |
[.HIPRI][;JOBQ=queuename] |
- #Jnnn
A job number. - #Snnn
A session number. (Although syntactically correct,
this parameter is rarely used: sessions do not wait.) - inputpriority
The new input priority (0 = lowest; 14 = highest). - ldev or devclass
The logical device number or device class name of
the destination device job's $STDLIST. - HIPRI
Allows the OP or SM to bypass the joblimit, see
the JOB command for more detail. - queuename
The name of the job queue whose limit is being changed.
The ALTJOB command, in conjunction with the JOBFENCE command, allows you to control the flow of all
jobs on the system with the exception of HIPRI |
