 |
» |
|
|
|
RECALL/=RECALL | |
Displays all pending console REPLY messages. A user, the system operator, a job or a program issues the RECALL command to determine if any pending resource requests
are currently awaiting a response. Pending resource requests are
responded to by using the REPLY command. This command may be issued from a session, job, program, or
in BREAK. Pressing Break has no effect on this command. It may be issued only from
the console. Any user may execute the RECALL command. However, the CTRL A =RECALL command may only be executed at the physical console,
and cannot be executed from a job or a program. To display all pending system console messages, which require
a response, enter: RECALL
THE FOLLOWING REPLIES ARE PENDING:
10:05/#J19/15/LDEV # FOR "L00576" ON TAPE1600 (NUM)? |
If any replies are pending, the request(s) are displayed on
the console as shown above. If no replies are pending, the following
message appears on the console: RECALL
NO REPLIES PENDING (CIWARN 3020) |
Use the =RECALL command if the RECALL command is ineffective, or when a job or subsystem
is being executed from the console. CTRL A
=RECALL
NO REQUESTS PENDING (SYS 15) |
- Commands
REPLY - Manuals
STORE and TurboSTORE/iX Manual Performing System Operation Tasks
REDO | |
Allows the user to edit and reexecute any command still retained
in the command line history stack. (Native Mode) - cmdid
Specifies the command to execute. The command may
be specified by its relative or absolute order in the command line
history stack, or by name (as a string). The default is -1, the
most recent command. The following Table 11-1 “Re-execute Directives for the REDO Command” illustrates the
result of using various forms of the cmdid parameter.
Table 11-1 Re-execute Directives for the REDO Command | cmdid | Executes |
|---|
| (omitted) | Previous command (same as REDO -1). | | -n | The nth command
before the most recent one. The n represents
a number in the command line stack relative to the most recent command,
which is -1. | | m | Command number m in
the command line stack. The number m is absolute
(not relative). | | string | The most recent command beginning with string. |
MPE/iX detects an error if you specify a cmdid that
cannot be found in the history stack. - editstring
A string specifying the first (of one or more) edit(s)
to be performed on cmdid before it is displayed
on the standard listing device ($STDLIST). When the (edited) command line is displayed, you may edit
the line interactively. REDO displays the command line and accepts further
edits repeatedly, until you signal completion by entering a Return only. At this point, the CI executes the edited version
of the command. If you omit editstring, then you are given the opportunity to edit the command
line interactively, after which the command is reexecuted. If you specify editstring, it must appear, character for character, and space
for space, exactly as it would if you were using the REDO command in interactive mode. The edit string must be surrounded by quotation marks (" ") if it contains any scanner/parser delimiters
such as: , ; " ' [ ] or = or spaces.
REDO executes the command specified as cmdid.
The user may specify an optional editstring that edits the command before it is reexecuted. This
command is a companion to the MPE/iX DO command. Unlike the DO command, the REDO command does permit interactive editing. If editstring is specified, the edit
is performed on cmdid before the command is
presented for interactive editing. If editstring is
omitted, then editing is interactive. In either case, the (edited) line is echoed to $STDLIST before it is reexecuted. At this point, you may
edit the line interactively. The interactive (editing) mode, remains
available to you until you press only Return. Both cmdid and editstring must
be surrounded by either single or double quotation marks if they
contain any delimiters such as , ; " " [, ], =, or a space. The editing directives used in editstring are
defined in Table 6-3. . Table 11-2 Editing Directives for the REDO Command | Directive | Effect |
|---|
| i | INSERT. If text follows the i, the text following i is inserted in the current line at the position
after the i. | | r | REPLACE. If text follows the r, the text following r replaces the same number of characters in the
current line, beginning at the position of r. | | d | DELETE. Deletes a character from the current line for
each specified in the edit line. Note that "d d" does not specify a range but simply deletes one
character from the position above each d. Multiple d's may be followed by an insert or replace operation. | | dw | DELETE WORD. Deletes a word starting at the letter d. A word is defined as all characters except a
space, comma, or semicolon. If you place the d directly beneath a word delimiter, then the word
and the delimiter characters are deleted. If no word exists on the
command line, no delete occurs. You may follow this directive with other
edits. | | ddelim | DELETE TO DELIMITER. Deletes all characters starting at the position
of the d and ending at, but not including, the specified
delimiter. If delim is not found, no delete occurs. You may follow this
directive with other edits. | | d> | DELETE TO EOL. Deletes to the end of the current line from the
position specified by d>. It may be followed by an INSERT or REPLACE operation. | | ^ | UPSHIFT. Upshifts the character positioned at the ^. You
may specify multiple ^ characters to upshift a series of characters.
Or, you may type multiple ^ characters, followed by spaces, then followed
by more ^'s to upshift some characters while skipping others.
You may follow this directive with other edits. | | ^w | UPSHIFT WORD. Upshifts the word starting at the position specified
by ^. A word is defined as all characters except a
space, comma, or semicolon. If you place the ^ directly beneath a word delimiter, the delimiter
is skipped and only the word is upshifted. If no word exists on
the command line, no upshift occurs. You may follow this directive
with other edits. | | ^delim | UPSHIFT TO DELIMITER. Upshifts all characters starting at the position
specified by the ^ and ending at, but not including, the specified
delimiter. If delim is not found, no upshift occurs. You may follow this
directive with other edits. | | ^> | UPSHIFT TO EOL. Upshifts all characters starting from the position
specified by the ^ to the end of the current line. You may follow
this directive with other edits. | | v | DOWNSHIFT. Downshifts the character positioned at the v. You may specify multiple v's to downshift a series of characters. Or, you
may type multiple v's, followed by spaces, then followed by more v's to downshift some characters while skipping others.
You may follow this directive with other edits. | | vw | DOWNSHIFT WORD. Downshifts the word starting at the position
specified by v. A word is defined as all characters except a
space, comma, or semicolon. If you place the v directly beneath a word delimiter, the delimiter
is skipped and only the word is downshifted. If no word exists on
the command line, no downshift occurs. You may follow this directive
with other edits. | | vdelim | DOWNSHIFT TO DELIMITER. Downshifts all characters starting at the position
of the v and ending at, but not including, the specified
delimiter. If delim is not found, no downshift occurs. You may follow
this directive with other edits. | | v> | DOWNSHIFT TO EOL. Downshifts all characters starting from the position
specified by the v to the end of the current line. You may follow
this directive with other edits. | | >text | APPEND. The > followed by text appends the text to the end of
the current line. If > is positioned beyond the end of the current line,
then a replacement is performed instead. | | >d | DELETE FROM EOL. Deletes from the end of the current line, right-to-left.
Multiple d's may be specified after >, as well as INSERT and REPLACE strings. | | >dw | DELETE WORD FROM EOL. Deletes the last word in the command line. To
find the last word, trailing word delimiters are skipped. If no
word exists in the command line, then none is deleted. If you follow >dw with additional editing directives, each edit
is performed recursively. That is, the first edit is performed (updating
the current EOL), then the next edit is performed (again updating
the current EOL), and so on. | | >ddelim | DELETE TO DELIMITER FROM EOL. Starting at the end of the current line, deletes all
characters right-to-left up to, but not including, delim. If the delimiter is not found, no delete occurs.
If you follow this directive with additional editing directives,
each edit is performed recursively. That is, the first edit is performed (updating
the current EOL), then the next edit is performed (again updating
the current EOL), and so on. | | >^ | UPSHIFT FROM EOL. Upshifts the character at the current EOL. You
may specify multiple ^'s to upshift a series of characters (read right-to-left)
from the EOL. Also, you may follow this directive with other edits. | | >^w | UPSHIFT WORD FROM EOL. Upshifts the last word in the command line. You
may follow this directive with other edits. | | >^delim | UPSHIFT TO DELIMITER FROM EOL. Starting at the end of the current line, upshifts
all characters right-to-left up to, but not including, delim. If the delimiter is not found, no upshift occurs.
You may follow this directive with other edits. | | >v | DOWNSHIFT FROM EOL. Downshifts the character at the current EOL.
You may specify multiple v's to downshift a series of characters (read right-to-left)
from the EOL, and you may follow this directive with other edits. | | >vw | DOWNSHIFT WORD FROM EOL. Downshifts the last word in the command line.
You may follow this directive with other edits. | | >vdelim | DOWNSHIFT TO DELIMITER FROM EOL. Starting at the end of the current line, downshifts
all characters right-to-left up to, but not including, delim. If the delimiter is not found, no downshift occurs.
You may follow this directive with other edits. | | >rtext | REPLACE. Replaces characters at the end of
the command line. The replacement is done so that the last (rightmost)
character of the replacement string is at the end of the line. | | c | CHANGE. Changes all occurrences of one string to another
in the current line when the search string and replace string are
properly delimited. A proper delimiter is a nonalphabetic character
(such as ', ", / or ,). The substitution is specified as: c<delim> search-string<delim> [replace-string [<delim>]].
Omitting the replace-string causes occurrences
of search-string to be deleted, with no substitution. | | u | UNDO. A single u in column one cancels the most recent edit of
the current line. Using the UNDO command twice in a row cancels all edits for the
current line and reestablishes the original, unedited line. If u is placed anywhere other than column one of the
current line, then a simple replacement is performed. UNDO makes sense only if you have a line on which you
have performed some editing that can be "undone." | | other | Simple replacement. Any other character (not i, r, d, d>, >, >d, c, or u) causes that character to be replaced in the current
line at the position indicated by the character. In fact, simple
replacement also occurs for the editing characters i, r, c, or > if they are not followed by text; or if > appears at or beyond the current end of line. |
The Table 11-3 “REDO Editing Samples” shows examples of using the
REDO command. Table 11-3 REDO Editing Samples | Edit | Action |
|---|
| u | First occurrence undoes the previous
edits. The u must be in column one. | | u | Second occurrence undoes all edits
on the current line. The u must be in column one. | | rxyz | Replaces the current text with xyz starting at the position of r. | | xyz | Replaces the current text with xyz starting at the position of x. | | ixyz | Inserts xyz into the current line, starting at the position
immediately before the i. | | ddd | Deletes three characters, one
above each d. | | d xyz | Deletes a single character above
the d, skips one space, then replaces the current text
with xyz starting at the position of x. | | ddixyz | Deletes two characters, then inserts xyz in the current line in the position before the i. | | d d | Deletes one character above the
first d, skips two spaces, and deletes a second character
above the second d. It does not delete a range of characters. | | d d>xyz | Deletes a single character above
the first d, skips two spaces, and deletes to the end of the
line beginning at the second d, and then appends xyz to the end of line. | | >xyz | Appends xyz to the end of the current line. | | >ddxyz | Deletes the last two characters
from the end of the current line and then appends xyz to the end of the line. | | >rxyz | Replaces the last three characters
in the current line with xyz. | | >ixyz | Appends xyz to the end of the line. In this case, the i command is superfluous, because > accomplishes the same result. Using >xyz would be sufficient. | | c/ab/def | Changes all occurrences of ab to def, starting at c. | | c"ab" | Deletes all occurrences of "ab" starting at c. | | cxyz | Replaces the current text with cxyz, starting at c. Because delimiters have been specified (as they
were in the previous two examples), this is a simple replacement. | | ^wix | Upshifts the word above the ^ and inserts an "x" at the end of the word it just upshifted. | | v/abc | Starting at the position of v, downshifts all characters up to, but not including, the
"/", then replaces the "/" and the next two characters with "abc". | | >dw^.dw | Deletes the last word in the current line,
recalculates the EOL, then upshifts all characters up to, but not
including, the dot (.), then deletes the word to the left of the
characters that were upshifted. |
This command is available in a session or in BREAK. It is
not available in a job or from a program. Pressing Break aborts the execution of this command. The following are examples of editing options for the REDO command: - REDO PAS
Edits the most recent command beginning with the
string PAS. - REDO 10
Edits command number 10 (absolute) on the command
history stack. - REDO -2
Edits the second-to-last command on the stack (one
command before the most recent).
- Commands
DO, LISTREDO - Manuals
Using the HP 3000 Series 900: Advanced
Skills
REFUSE | |
Disables jobs/sessions and/or data on a designated device. REFUSE [JOBS,] [DATA,] ldev - JOBS
Disables the JOB (or HELLO) command from the designated device. - DATA
Disables the DATA command from the designated device. - ldev
The logical device number of the device for which JOB (or HELLO) and DATA commands are refused.
The REFUSE command prevents a device from automatically recognizing
and accepting one or more of the three commands (JOB, HELLO, and DATA) users execute to introduce jobs or sessions.
The JOBS parameter in the REFUSE command refers to both jobs and sessions. If neither
the JOBS nor DATA parameter is supplied, both JOB (or HELLO) and DATA commands are refused. To undo the effect of the REFUSE command, use ACCEPT. This command may be issued from a session, job, program, or
in BREAK. Pressing Break has no effect on this command. It may be executed only
from the console unless distributed to users with the ALLOW or ASSOCIATE command. To prevent logical device 35 from recognizing the DATA command, enter: To prevent both jobs and data recognition on logical device
35 enter: - Commands
ACCEPT - Manuals
Performing System Operation Tasks (32650-90137)
RELEASE | |
Removes security provisions from a file. Security does not
resume for a released file until you enter the SECURE command for the file. - filereference
Specifies the actual file designator of the file
whose file access matrix access control you want to disable. The filereference can
be either in MPE or HFS syntax. MPE Syntax If the filereference does not begin with
a dot or a slash, it is parsed according to the MPE syntax and has
the form: filename[/lockword][.groupname[.acctname]] |
If the file has a lockword, you must specify it; otherwise,
the system prompts you for it. If you do not specify groupname.acctname, the system assumes the logon group and account. HFS Syntax If the filename begins with a dot (.)
or a slash (/), it is parsed according to HFS syntax.
Usage You can use this command only for permanent disk files you
have created. Under default system security provisions, the file
must be in your logon account and must belong to your logon or home
group. Checking the file status You can enter the LISTFILE command to determine if a file is currently released
or secured. Refer to the LISTFILE command for more information. Access control definition An access control definition (ACD) overrides file access controls
whether or not you have released or secured the file. For more information about ACDs, refer to the ALTSEC command in this manual. Unaffected access controls This command does not affect the following access controls: - Privileged files
You cannot release privileged files. - Lockwords
You cannot override lockwords. - ACDs
This command does not affect the security on files
with access control definitions. However, if you remove the ACD,
the file is released. Refer to the ALTSEC command in this book for more information about
ACDs.
You can enter this command from a session, a job, a program,
or in BREAK. Pressing Break does not affect this command. To release all security
provisions for a file named FILE1 in your logon group and account, enter: If the system fails to locate the file, the following error
message appears: UNABLE TO ACCESS FILE1.GROUP1.ACCT1. (CIERR 356) |
- Commands
ALTSEC, LISTF, LISTFILE, SECURE, ALTLOG, CHANGELOG, GETLOG, LISTLOG, LOG, OPENLOG, RESUMELOG, SHOWLOGSTATUS, SWITCHLOG - Manuals
None
RELLOG | |
Removes a user logging identifier from the system. - logid
The logging identifier to be removed from the system.
The RELLOG command removes a user logging identifier from
the system by deleting it from the directory of logging identifiers.
This command may be issued only by the user who created the logging
identifier. System supervisor (OP) or user logging (LG) capability
is required to use this command. After RELLOG is issued, programs containing the removed logging
identifier are not allowed to access the logging system. This command may be issued from a session, job, program, or
in BREAK. Pressing Break has no effect on this command. To remove the logging identifier DATALOG from the system, enter: - Commands
GETLOG - Manuals
User Logging Programmer's Guide
RENAME | |
Changes the file name, lockword, and/or group name of a disk
file. RENAME oldfilereference,newfilereference [;TEMP] - oldfilereference
Current name of file, written in the format: [*]filename[/lockword][.groupname[.acctname]] |
To use HFS syntax, preceed the file name with a dot (.), or
a slash (/). - newfilereference
New name of file, in the same format as oldfilereference. If you omit acctname and/or groupname, the logon account and/or group are assumed. To use HFS syntax, preceed the file name with a dot (.), or
a slash (/). - TEMP
Indicates that the old file was, and the new file
will be, temporary files. If you do not specify TEMP, RENAME assumes that the files are permanent.
The RENAME command changes the system file identification
for a permanent or temporary disk file. You can use it to change
the name of a file, to change the lockword of an MPE file, or to
move any file to a different location. - MPE Files
To rename an MPE file, you must have DD access to
the source MPE group and CD access to the target MPE group. If you
specify groupname or acctname, you must have save access to the
group or account. Users with System Manager (SM) capability can
rename any file to any location on the system. You can use RENAME to move native mode MPE files to HFS directories.
You cannot move compatability mode MPE files to HFS directories.
For example, you can use RENAME with KSAM/XL files, but you cannot
use it to rename MPE V/E KSAM files. To successfuly rename a file across group or account boundaries,
you must move it within a single volume set and that volume set
must be physically mounted. When you use RENAME to move a file that does not have an ACD
to a directory or to another account, an ACD is automatically created
for the file to ensure that it is protected by the appropriate file
access matrix of its new location. - HFS Files
To rename a file in an HFS directory, you must have
delete directory entry access (DD) to the old directory and create
directory entry access (CD) to the new directory. Files in HFS directories can be renamed to files in the MPE
account group structure, and they can be renamed to files in other
HFS directories. You cannot rename a directory. If either oldfilereference or newfilereference is actually a directory, you will get an error. - Spool Files
If you have access to spoolfiles, you can rename
them. In this case, the name of the file changes, but the contents
and links to the spooler remain the same.
This command may be issued from a session, a job, a program,
or in BREAK. Pressing Break has no effect on this command. Since temporary files exist only for the duration of your
current job or session, their fully qualified file names correspond
to your logon group and account. The following example shows the
command entry to change the name of a temporary file from OLDFILE to NEWFILE, and reassign it to the group NEWG. RENAME OLDFILE,NEWFILE.NEWG,TEMP |
To change the lockword of the permanent file FILE2 from LOCKA to LOCKB, enter: RENAME FILE2/LOCKA,FILE2/LOCKB |
To transfer a file from one group to another within the same
account, use the RENAME command, simply naming the new group in the second
parameter. You must have SAVE access to GROUP2 and both groups must be in the system domain or
reside on the same volume set. For example, to move the file MYFILE from GROUP1 to GROUP2, enter: RENAME MYFILE.GROUP1,MYFILE.GROUP2 |
The following command renames the file dir2/doc/print.txt in the current working directory (CWD) to MYFILE in the group and account MYGROUP.MYACCT. RENAME ./dir2/doc/print.txt, MYFILE.MYGROUP.MYACCT |
The following command renames the file FILE1 in the PUB group to new_txt in the HFS directory dir1 under the root directory. RENAME FILE1.PUB, /dir1/new_txt |
The following command renames the KSAM XL file KSFILE in the PUB group to ksfile in the HFS directory dir1 under the root directory. RENAME KSFILE.PUB, /dir1/ksfile |
- Commands
BUILD, COPY, PURGE, PRINT - Manuals
None
REPLY/=REPLY | |
Replies to pending resource requests at the console. REPLY pin,reply
=REPLY pin,reply - pin
The process identification number (PIN) of the message
sender. As part of the message requesting the REPLY, the PIN always appears after the second slash
mark (/). In the following example, the PIN is 43. ?16:15/#S25/43/LDEV# FOR "T" ON TAPE (NUM)? |
- reply
The reply type specified in parentheses in the message,
defined by one of the following: - (NUM)
Reply must be a logical device number. - (Y/N)
Reply must be either YES (or Y) or NO (or N). - (MAX CHARS.=nn``)
Reply must be a string expression consisting of nn characters
or less.
User programs that have requested the use of a device and
are waiting for you to reply remain suspended indefinitely and cannot
be aborted until a REPLY or a Break/ABORT is issued. If for any reason you cannot reply
as requested (for example, if the particular device is nonexistent
or a special form is unavailable), then use REPLY/=REPLY with 0 if type NUM is requested, or with N if type Y/N is requested. This returns an error code to the program
and the REPLY/=REPLY is aborted. The reply usually takes the form (NUM) or (Y/N), since (MAX CHARS.=nn) is used only for labeled tapes and the PRINTOPREPLY intrinsic. If your reply is not of the type specified, an error message
is displayed. This command may be issued from a session, job, program, or
in BREAK. Pressing Break has no effect on this command. It may be issued only from
the logical console, unless distributed to specific users with the ALLOW or ASSOCIATE command. The Ctrl A =REPLY command can be used only from the physical console.
It cannot be executed from a job or a program. Use the REPLY command to respond to a message from the MPE/iX
system, as follows: 10:05/#J19/15/LDEV# FOR "NAS" OF TAPE1600 (NUM)?
REPLY 15,7 |
or Use the REPLY command to respond to a FORMS message from the MPE/iX system, as follows: 15:46/#S93/22/FORMS: PLEASE MOUNT MAILING LABEL FORMS
?15:46/#S39/22/SP#12/LDEV# FOR #S93;OUTFILE ON LP (NUM)?
REPLY 22,12
15:46/#S39/22/LDEV#12 FORMS ALIGNED OK (Y/N)? |
Answering NO causes the printing to be deferred to a much lower
priority. After the forms have been aligned, use the ALTSPOOLFILE command to change the spooling priority, in order
to send the spoolfile to the printer. REPLY 22,NO
15:48/#S93/22/LDEV#12 FORMS ALIGNED OK (Y/N)? |
Answering YES causes the spoolfile to go to the printer in its
assigned sequence. When the next spoolfile becomes ACTIVE, you are requested
to mount the appropriate special or standard forms. To reply to a standard forms request, enter: 16:00/#S93/22/STANDARD FORMS
?16:00/#S93/22/LDEV # FOR #S95;L ON LP (NUM)?
REPLY 22,12 |
- Commands
RECALL - Manuals
Performing System Operation Tasks System Startup, Configuration, and Shutdown Reference
Manual
REPORT | |
Displays accounting information for the logon account and
group. Any user may obtain REPORT information about the user's logon group. (Compatibility
Mode) REPORT [groupset] [,listfile] [;ONVS=[volumesetname]] - groupset
Specifies the accounts and groups for which information
is to be listed. The permissible entries, some of which use wildcard
characters, and their capability requirements such as account manager
(AM) and/or system manager (SM) are listed below: - group
Reports on the specified group in the logon account.
This is the default for standard users, who may specify only their logon
group. - @
Reports on all groups in the logon account. This
is the default for account managers, but may be executed by users
with AM or SM capability. - group.acct
Reports on the specified group in the specified
account. This requires SM capability. - @.acct
Reports on all groups in the specified account.
This requires AM capability (if it is the logon account) or SM capability
for any account. - @.@
Reports on all groups in all account totals. This
is the default for system managers and requires SM capability. ONVS= should always be used when @.@ is used as the groupset parameter. - group.@
Reports on specified group in any account. This
requires SM capability.
You may use the wildcard characters, @, #, and ? to specify a set of names. - @
Specifies zero or more alphanumeric characters.
Used by itself, it specifies all possible combinations of such characters.
Used with other characters, it indicates all the possible names
that include the specified characters (@ABC@ = all names that include ABC anywhere in the name). - #
Specifies one numeric character (A###@ = all names that begin with A followed by any three digits, followed by any combination
of zero to three alphanumeric characters). - ?
Specifies one alphanumeric character (A?# = all the three-character names that begin with A, followed by an alphanumeric, followed by a digit.)
The characters may be used as follows: - n@
Report on all groups starting with the character
"n". - @n
Report on all groups ending with the character "n". - n@x
Report on all groups starting with the character
"n" and ending with the character "x". - n##``...#
Report on all groups starting with the character
"n". - ?n@
Report on all groups whose second character is "n". - n?
Report on all two-character groups starting with
the character "n". - ?n
Report on all two-character groups ending with the character
"n".
These characters, when placed appropriately in the groupset parameter, may
also be used to report on accounts. - listfile
Actual file designator of the output file to which
information is to be written. The default is $STDLIST, but output may be redirected with a FILE equation as follows: FILE LIST1;DEV=LP
REPORT, *LIST1 |
- volume- setname
Instructs MPE/iX to report account information for
the specified volume set. If this parameter is omitted, the default
is the MPE/iX system volume set. Refer to "Operation Notes."
The REPORT command displays the total resource usage logged
against accounts and groups, and the limits on those resources.
For standard users, data is displayed for their own group(s) only;
account managers may specify all groups in their account; system managers
may specify any or all groups in any or all accounts. The information includes usage counts and limits for permanent
file space (in sectors), CPU-time (in seconds), and session connect-time
(in minutes). The file space usage count reflects the number of
sectors used at the time the REPORT command is issued. However, CPU-time and connect-time
usage appear as they were immediately before the beginning of the
current session. CPU-time and connect-time contain non-zero values only when the MPE/iX system volume set is specified (either
in the ONVS= parameter or by default when ONVS= is not used). CPU-time and connect-time are displayed
as zero for non-system volume sets. If you specify the ONVS= parameter, REPORT displays file space counts for the specified volume
set(s) only. If you specify a non-system volume, all other volume
names are also displayed, but their file space counts are displayed as zero even though they may not be zero. You should always specify ONVS= when @.@ is the groupset parameter. If data for the MPE/iX system volume set is requested (either
with or without the ONVS= parameter), file space counts are displayed for all volume sets (both system and non-system). However, the account total display reflects only file space in the MPE/iX system
volume set. 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. MPE/iX uses a naming convention for volume sets that differs
from the MPE V/E naming convention for private volumes. As a convenience
to established Hewlett-Packard users, MPE/iX does, however, accept
the naming convention that was used for MPE V/E private volumes.
Refer to the VSRESERVE or VSRELEASE commands in this chapter. For information on migrating files from MPE V/E private volumes
to MPE XL mountable volume sets, please refer to the chapter on
DIRMIG in the Migration Process Guide. | | | |  | NOTE: The REPORT does not produce the same output as DISCFREE because REPORT does not account for disk space taken up by objects
such as directory files and label tables. To determine how much
space is taken up by other objects, issue the FSCHECK TOTALEXTENTS command. | | | | |
This command may be issued from a session, job, program, or
in BREAK. Pressing Break aborts the execution of this command. Account manager
(AM) capability is required to issue the command for an entire account,
or system manager (SM) capability to issue the command for the entire
system. To obtain the display of account information for the group, SOPRM, enter: REPORT SOPRM
ACCOUNT FILESPACE-SECTORS CPU-SECONDS CONNECT-MINUTES
/GROUP COUNT LIMIT COUNT LIMIT COUNT LIMIT
SOPRM 13599 ** 30144 ** 17258 **
/GLOSSARY 1068 ** 542 ** 656 **
/PUB 182 ** 123 ** 1155 **
/SECT1 180 ** 85 ** 429 **
/SECT10 11779 ** 25271 ** 9716 **
/SECT2 390 ** 4123 ** 5302 ** |
- Commands
VSCLOSE, VSOPEN, VSRELEASE, VSRESERVE, VSRESERVESYS, VSTORE, VSUSER, RESETACCT, DISKUSE, DISCFREE Utility, LISTFILE - Manuals
Volume Management Reference Manual
RESET | |
Cancels file equations. RESET { formaldesignator @ } - formal- designator
A formal file designator name in the form file[.group[.account]] [:nodespec], for which a FILE command has been issued. The nodespec portion
may be an environment identifier indicating the location of the
file, or it may be $BACK. Specifying $BACK means that the file resides one "hop" back toward
your local system (which may be the local system itself). - @
Signifies all formal file designators specified
in all FILE commands previously issued in this session or
job.
This command may be issued from a session, job, program, or
in BREAK. Pressing Break has no effect on this command. To cancel the effects of a previous FILE command that specified characteristics for a file programmatically
referred to as ALPHA enter: - Commands
FILE, LISTEQ - Manuals
None
RESETACCT | |
Resets the running counts of CPU-time or connect-time accumulated
by an account and by all groups within that account to zero. RESETACCT [{ @ acct } [,{ CPU CONNECT }]] - @
Specifies that the counters for all accounts, and
all groups within the accounts, are to be reset. Default. - acct
Specifies the name of a particular account, and
all groups within the account are to be reset. - CPU
Specifies that only the CPU usage counter is to
be reset. Default is that both the CPU-time and connect-time counters
are reset. - CONNECT
Specifies that only the connect-time usage counter
is to be reset. Default is that both the CPU-time and connect-time
counters are reset.
This command resets the running counts of CPU-time or connect-time
accumulated by an account and by all groups within that account
to zero. If all parameters are omitted when you execute RESETACCT, all counters (except file space) for all groups
in all accounts are reset. 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 execute this command. To reset the CPU counter for all accounts in the system, enter: - Commands
REPORT - Manuals
None
RESETDUMP | |
Disarms the debug facility call that is made during abnormal
process termination. (Native Mode) This command disarms the debug facility (armed by using the SETDUMP command) after a process abort. It affects all
processes created later under the current session or job. This command may be issued from a session, job, program, or
in BREAK. Pressing Break has no effect on this command. Issuing this command in
BREAK does not affect existing processes. To disarm the stackdump/debug facility enter: - Commands
DEBUG, SETDUMP - Manuals
System Debug Reference Manual
RESTORE | |
Returns files that have been stored on backup media to the
system. RESTORE [restorefile] [;filesetlist] [;option [;...]] [ ;SHOW [ =showparmlist]] [ ;ONERROR= { QUIT | SKIP | FULL}] |
[;{ LOCAL GROUP=groupname ACC[OUN]T=accountname}] |
[;CREATE= { ACCT | GROUP | CREATOR | PATH }] |
[;CREATOR[ =username]] [;GID[ =filegroupname]] |
[;KEEP NOKEEP] [;OLDDATE NEWDATE] [;DIRECT0RY] [;LISTDIR] [;PROGRESS[ =minutes]] |
[ ;FCRANGE=filecode/filecode[,...] ;FILES=maxfiles] |
[ ;DEV=device] [;VOL=volumename] [;VOLCLASS=volumeclassname] [;VOLSET=volumesetname] |
[ ;COPYACD] [;NOACD] [;TREE] [;STOREDIR[ECTORY] =directoryname] |
[;PARTI[IAL] DB] [ ;RESTORESET=(device[,...])] |
The following parameters are available with TurboStore/iX
and TurboSTORE/iX True-Online Backup products only: [;RESTORESET=(device [,...]) [,(device [,...]) [,...]]]
[
;MOSET=(ldev [,...]) [,(ldev[,...]) [,...]]]
[
;NAME=backupname] - restorefile
The name of the device that contains the files you
want restored to the system. This file must be backreferenced, using
an asterisk (*). A File equation for restorefile should be set up before invoking RESTORE. If you want to restore files from a file called
SOURCE enter this file equation before running RESTORE: The restorefile can now reference a remote device. For example, FILE REMOTE;DEV=REMSYS#TAPE
RESTORE *REMOTE;@;SHOW |
NM RESTORE will restore all files from the specified remote
device. Although the initial tape mount request will appear on the
remote console, all of RESTORE's console messages will be displayed on the local
console. Currently, labeled tapes and Magneto-optical devices cannot
be used for remote backup. A message is displayed on the system console requesting the
operator to mount the tape identified by the restorefile parameter and to allocate the device. If restorefile is not supplied and the RESTORESET option is not used, then RESTORE creates a default file name. The default file
name is the user's logon username. No file equation is used. Sequential and parallel devices are specified with the RESTORESET option. Similarly, magneto-optical devices are
specified using the MOSET option. You should not specify restorefile when using RESTORESET or MOSET. A disk file can also be specified with a file equation for restorefile. An example of such a file equation would be: :FILE MYDISC=DISCBACK.DAILY.BACKUP;DEV=DISC |
Note that DEV=DISC must be specified for RESTORE to recover files from disk backups. All other
information in the file equation will be ignored by RESTORE. | | | | | NOTE: TurboSTORE/iX 7x24 True-Online Backup must be used to
create disk backups. | | | | |
- filesetlist
Specifies the set of files to be restored. The default
depends on the user's capability, as shown below: - Default
Capability - @
None - @.@
Account manager (AM) - @.@.@
and/or system supervisor (OP)
The filesetlist parameter has the form shown below: filesetitem[,filesetitem[...]] |
where filesetitem can be ^indirectfile or fileset. - indirectfile
A file name that backreferences a disk file. The
syntax is ^indirectfile or !indirectfile This file may consist of fileset(s) and option(s), but only options can appear after the first semicolon
(:) on each line. An option specified on one line will operate on
all files in the filesetlist. ^indirectfile is the preferred format. If you use !indirectfile, the CI will interpret this as a variable reference,
so you will have to specify indirectfile instead. - fileset
Specifies a set of files to be restored, and optionally
those files to be excluded from the RESTORE operation. The fileset parameter has the form: filestorestore[-filestoexclude[..]] |
The system restores any file that matches filestorestore unless the file also matches filestoexclude, which specifies files to be excluded from the RESTORE
operation. You may specify an unlimited number of filestoexclude. Since "-" is a valid character for HFS syntax file names,
a blank character must separate it from HFS file sets to obtain
the special negative file set meaning. - filestorestore
filestoexclude Both filestorestore and filestoexclude may be entered in MPE or HFS syntax. Wildcards are
permitted for both MPE and HFS syntax. The MPE syntax is as follows: filename[.groupname[.accountname]] |
A lockword may be specified for files to be restored, in the
form: filename/lockword.group.account |
|
