|
|
Stops header/trailer output to a device. (Native Mode)
Syntax
HEADOFF ldev
Parameters
- ldev
The logical device number of the printer affected by the
command.
Operation Notes
Header and trailer information appears before and after a file when it is
printed. This information is not a part of the file's text. This information
identifies the file by session number, output spoolfile number, session name
(if any), user, and account. It also lists the date and time the file was
printed.
If output is directed to a line printer, MPE/iX automatically prints header and
trailer pages identifying the job that produced the file.
If the device is in use and a header has already been printed when you issue
the HEADOFF command, your request to suppress header/trailer output
takes effect after the corresponding trailer is printed.
Use
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.
Example
To stop header/trailer output to logical device number 6, enter:
HEADOFF 6
Related Information
- Commands
HEADON
- Manuals
Performing System Operation Tasks
Resumes header/trailer output to a device. (Native Mode)
Syntax
HEADON ldev
Parameters
- ldev
The logical device number of the printer affected by the
command.
Operation Notes
Header and trailer information appears before and after a file when it is
printed. This information is not a part of the file's text. This information
identifies the file by session number, output spoolfile number, session name
(if any), user, and account. It also lists the date and time the file was
printed.
When the header/trailer facility is enabled, output is directed to a line
printer, and MPE/iX automatically prints header and trailer pages identifying
the job that produced the file.
If the device is in use, your request to resume header/trailer output takes
effect after the current output is complete.
The header/trailer facility is always enabled at system startup.
Use
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.
Example
To resume header/trailer output to logical device number 6 enter:
HEADON 6
Related Information
- Commands
HEADOFF
- Manuals
Performing System Operation Tasks
Initiates an interactive session. (Native Mode)
Syntax
HELLO [sessionname,]username[/userpass].acctname[/acctpass]
[,groupname[/grouppass]]
[;TERM={ termtype | termname }]
[;TIME=cpusecs]
[;PRI={ BS | CS | DS | ES }]
[{;INPRI=inputpriority | ;HIPRI }]
[;INFO=ciinfo] [;PARM=ciparm]
Parameters
- sessionname
Arbitrary name used in conjunction with username and
acctname parameters to form a fully qualified session
identity. The name must contain from one to eight alphanumeric
characters, beginning with an alphabetic character. Default is that no
session is assigned.
- username
User name, established by the account manager, that allows you to log
on to this account. The name must contain from one to eight alphanumeric
characters, beginning with an alphabetic character.
- userpass
User password, optionally assigned by the account manager. The
password must contain from one to eight alphanumeric characters,
beginning with an alphabetic character. The user password must be
preceded by a slash (/).
- acctname
Account name as established by the system manager. The name must
contain from one to eight alphanumeric characters, beginning with an
alphabetic character. The acctname parameter must be
preceded by a period (.).
- acctpass
Account password, optionally assigned by the system manager. The
password must contain from one to eight alphanumeric characters,
beginning with an alphabetic character. The account password must be
preceded by a slash (/).
- groupname
Group name to be used for the local file domain and the CPU and
connect-time charges as established by the account manager. The name must
contain from one to eight alphanumeric characters, beginning with an
alphabetic character. Default is your home group if you are assigned one
by the account manager. (Required if a home group is not
assigned.)
- grouppass
Group password optionally assigned by the account manager. The
password must contain from one to eight alphanumeric characters beginning
with an alphabetic character. The grouppass parameter is
not needed to log on to your home group. The group password must be
preceded by a slash (/).
- termtype or termname
Determines terminal type characteristics. The termtype
parameter determines the type of terminal used for input. MPE/iX uses
this parameter to determine device-dependent characteristics such as
delay factors for carriage returns. It must be 10 or 18. The default
value for termtype is assigned by the system supervisor
during system configuration. This is a required parameter to ensure
correct listings if your terminal is not the default
termtype.
The termname parameter is the name of the file containing
the desired terminal-type characteristics. The file cannot have a
lockword or reside on a user volume.
Users of the workstation configurator are allowed to create terminal-type
files. The proper and efficient operation of a specific device by a
user-created terminal type is the responsibility of the user. The
workstation configurator utility allows the user to specify
characteristics of the terminal, including data flow control, block mode,
read trigger, special characteristics, echo, line feed, parity, and
printer control.
- cpusecs
Maximum CPU-time that a session can use, entered in seconds. When the
limit is reached, the session is aborted. It must be a value from 1 to
32767. To specify no limit, enter a question mark (?),
UNLIMITED, or omit the parameter. Default is no limit.
- BS, CS, DS, or ES
The execution priority queue that MPE/iX uses for your session, and
also the default priority for all programs executed within the session.
BS is the highest priority, ES is the lowest. If you specify a priority
that exceeds the highest priority permitted for your account or user name
by the system, MPE/iX assigns the highest priority possible below BS. DS
and ES are intended primarily for batch jobs; their use for sessions is
generally discouraged. For information on the guidelines for these
priority queues, refer to the TUNE command. Default is
CS.
|
CAUTION: Use care in assigning the BS queue. Processes in this priority
class can lock out other processes.
|
- inputpriority or HIPRI
Determines the input priority of the job. The
inputpriority option is the relative input priority used
in checking against access restrictions imposed by the jobfence. The
inputpriority option takes effect at logon time and must
be from 1 (lowest priority) to 13 (highest priority). If you supply a
value less than or equal to the current jobfence set by the system
operator, the session is denied access. Default is 8.
When logging on, the HIPRI option is used to either override the
system jobfence or to override the session limit. When using the
HIPRI option to override the jobfence, the system first checks
to see if you have system manager (SM) or system operator (OP) capability.
If you have either of these capabilities, you are logged on and your
INPRI defaults to the system's jobfence and execution limit. If
you do not have either of these capabilities, the system attempts to log
you on using INPRI=13 and succeeds if the jobfence is 12 or
less, and if the session limit is not exceeded. Only users with SM or OP
capability can use the HIPRI option to override the session
limit to log on. Use of the HIPRI option without SM or OP
capability causes the following warning to be displayed:
MUST HAVE 'SM' OR 'OP' CAP. TO SPECIFY HIPRI,
MAXIMUM INPRI OF 13 IS USED (CIWARN 1460)
- ciinfo
An INFO string to be passed to the command interpreter. For
the MPE/iX CI, it is the first command to be executed by the command
interpreter. This parameter replaces the ( ) COMMAND LOGON
command and approximates its function. The ( ) COMMAND LOGON
command caused the session to terminate after executing the specified
command. In contrast, the ciinfo parameter does not
terminate the session unless ciparm is set to 1, 3, or 5.
Running the CI as a child process in this way restricts the flexibility
of ciparm. More flexibility is available by running the
CI as a standalone program.
- ciparm
The command interpreter parameter number you wish to use. The MPE/iX
command interpreter accepts the numbers listed below. If you enter any
other value, it is treated as zero (0).
- 0, 2, 4
Executes logon UDCs and displays the CI banner and the welcome
message. This is the default.
- 1, 3, 5
Same as 0, but the CI terminates after processing the
INFO= string. If the INFO= string is not specified,
the CI terminates after executing the first user-supplied
command.
- -1
Prohibits cataloging of UDCs and suppress the display of the CI
banner and the welcome message. Invoking this level requires system
manager (SM) capability.
- -2
Same as -1, but the CI terminates after processing the
info= command. Invoking this level requires system
manager (SM) capability.
The MPE/iX CI distinguishes between ciparms 1, 3, 5 and
0, 2, 4 when it is run from within the CI, that is, after the session has
logged on.
If a user without SM capability uses -1 or -2, the system
substitutes a parameter value of 0 and does NOT display an error
message.
Operation Notes
The HELLO command initiates an interactive session and must be entered
from a terminal; no other device can be used for this command. You must supply
both a valid username and acctname in your
logon command or MPE/iX rejects your logon attempt and displays an error
message. If your logon attempt is accepted, MPE/iX displays specific logon
information and prompts you for your next MPE/iX command. In the following
example, a user has logged on under the username USER
and the acctname TECHPUBS:
MPE XL:HELLO USER.TECHPUBS
HP3000 Release: X.50.40 User Version : X.50.40
THU, DEC 8, 1994, 1:15 PM
MPE/iX HP31900 B.78.11 Copyright Hewlett-Packard 1987.
All rights reserved.
:
When you first access an MPE/iX system to log on, the MPE iX: prompt
is displayed. When you log off using the BYE command, the following
message is displayed:
CPU=1. CONNECT=1. THU, DEC 8, 1994, 1:50 PM
The RELEASE: V.UU.FF number in the logon banner is determined by
Hewlett-Packard at operating system build time and provides an identity for
software releases (also known as the MIT). This number may not be changed.
(Prior to MPE/iX release A.11.70, this was referred to as BASE.)
The USER VERSION: V.UU.FF can be assigned a value during a SYSGEN and
allows you to identify any changes to your total software package such as patch
level, third party software, or other specifics. Any ASCII character can be
used. In prior releases, this number was printed out immediately after the
MPE/iX product number HP31900.
The PRODUCT V.UU.FF, which now immediately follows the product number
HP31900, is determined by Hewlett-Packard when a new version of MPE/iX is
compiled. This V.UU.FF number cannot be changed and is used when
entering a service request (SR) against the MPE/iX operating system product for
that particular release.
If the system operator has set up a welcome message, it is displayed after the
MPE/iX verification of your logon.
The session number assigned by MPE/iX uniquely identifies your session to
MPE/iX and to other users. MPE/iX assigns such numbers to sessions in
sequential order as they are logged on. If you are on a modem and do not log on
within the system-configured time, the line is dropped. You must redial and
press Return again. If you are already logged on and you issue the
HELLO command, you will be logged off your current session and logged
on to a new session.
In certain instances, you may be required to furnish information in addition to
the user and account names in your HELLO command. This information
includes:
Group name
One or more passwords
Terminal type code
Use
This command may be issued from a session. It may not be used from a job,
program, or in BREAK. Pressing Break does not abort the execution of
this command, but may prematurely terminate the printing of the welcome message
or the execution of any logon UDCs. If you are already in a session,
HELLO terminates that session before beginning a new one.
Group Name
The group you select at logon for your local file domain is known as your logon
group. If your account manager has associated a home group with your
username, and if you want this group as a logon group, you need
not specify it. MPE/iX automatically assigns the home group as your logon group
when you log on. But if you want to use some other group as your logon group,
you must specify that group's name in your logon command in this way:
MPE iX:HELLO USER.TECHPUBS,MYGROUP
If your user name is not related to a home group, you must enter a group name
in your HELLO command, or your logon attempt is rejected.
Once you log on, if the normal (default) file security provisions of MPE/iX are
in force, you have unlimited access to all files in your logon and home groups.
Furthermore, you can read files and execute programs stored in the PUB
(public) group of your account and the PUB (public) group of the
SYS (system) account. You cannot, however, access any other files in
any way. Further information about files and file security can be found in the
Accessing Files Programmer's Guide (32650-60010).
Passwords
To enhance the security of an account, and to prevent unauthorized
accumulation of charges against the account, the system manager
may assign a password. Similarly, an account manager may associate
passwords with the user names and groups belonging to his account.
If you are using an account, user name, or group (other than your
home group) that has a password, you must furnish that password
when you log on. Include the password after the name of the protected
entity, separated from that name by a slash mark (/). (In MPE/iX,
the slash denotes security.)
For instance, if the group XGROUP requires a password, and if you use
this group as your logon group, you could enter the password in this fashion:
MPE iX:HELLO USER.TECHPUBS,XGROUP/XPASS
Note that when you specify your home group as your logon group, you need not
enter a password, even if that group has such a password.
Sometimes, when logging on to the system, it is more convenient
to have MPE/iX prompt you for any required passwords. You do this
by omitting the passwords from the logon command. When you log on,
the command is printed in the normal way; MPE/iX prompts you for
the password, then turns echo off so that the password is not printed.
If you enter the password incorrectly, the prompt reappears and
you have two more chances to enter the password correctly. After the third
incorrect entry, the message INCORRECT PASSWORD (CIERR 1441) is
displayed. You must then press Return to receive a new prompt and then
enter the HELLO command to start a new logon process. Echo is
turned on after all passwords are read.
Terminal Types
MPE/iX must be able to determine certain characteristics about
your terminal, such as input and output speed, in order to conduct
a session. If you log on using a different type of terminal than
the type the system manager has configured, you must specify your terminal
type when you log on. Refer to appendix C, "Terminal and Printer Types."
MPE iX:HELLO USER.TECHPUBS;TERM=10
Example
When you initially log on to access MPE/iX, the system prompt appears as:
MPE iX:
When you subsequently log on to another account or group,
the system prompt by default is a colon (unless you have altered
it with the SETVAR HPPROMPT command) and appears as:
:
To start a session named ALPHA, with the user USER, the
account TECHPUBS, the group XGROUP, and the group password
XPASS, enter:
MPE iX:HELLO ALPHA,USER.TECHPUBS,XGROUP/XPASS
HP3000 Release: X.50.40 User Version : X.50.40
MON, DEC 12, 1994, 7:15 AM
MPE/iX HP31900 B.78.11 Copyright Hewlett-Packard 1987.
All rights reserved.
:
Related Information
- Commands
BYE
- Manuals
None
Accesses the help subsystem (Native Mode)
Syntax
Direct access:
HELP [{ udcname commandname [{ keyword ,ALL }]
commandfilename errormessage programfilename
function name variable name
SUMMARY CLASS HELPSTUDY
EXPRESSIONS | VARIABLES | OPERATORS | FUNCTIONS }]
Interactive (subsystem) access:
>commandname {space or comma} [{ keyword ,ALL }]
HELPMENU
SUMMARY
CLASS
HELP
HELPSTUDY
Parameters
- <omitted>
If you specify the HELP command with no parameters, you enter
the help facility subsystem in interactive mode. To return to the CI,
enter E or EXIT. Refer to "Operation Notes."
- udcname
Any existing UDC. To display all UDCs within a UDC file, specify the
PRINT command. Refer to commandname.
- commandname
Any MPE/iX command. MPE/iX displays the command name and syntax. In
addition, a list of keywords for that command is displayed.
The HELP command also provides help on UDCs, command files, or
program files. The search order is UDCs, built-in commands (MPE/iX),
command files, and then program files. The search order for UDC's is user
level, account level, and system level. The search order for command
files and program files is determined by the contents of the CI variable
HPPATH. If the user's HPPATH does not contain the name
of the current group, the user can print a command file from the current
group, but cannot get help information.
For UDCs and command files, help displays the text of the user command,
unless the file contains the NOHELP option. In those cases, the
display is suppressed. In the case of program files, help displays a
header identifying it as a program file and the fully qualified file name
of the program file.
- function name
Any CI evaluator function, eg: FINFO
- keyword
One of the keywords described under the command parameter. All
commands have the following keywords:
- PARMS
PARMS is short for parameter. Lists all parameters of
the specified command.
- OPERATION
Describes the use of the specified command.
- EXAMPLE
Displays an example showing usage of the specified
command.
- ALL
Displays all parameters, operation information, and an example of
the command.
- variable name
Any CI predefined variable, eg: HPLASTJOB
- command- filename
Any existing command file. Refer to commandname,
"Operation Notes," and "Examples."
- errrormessage
Any MPE/iX error message. The keywords are:
- CIERRnn
- program- filename
Any existing program file. Refer to commandname,
"Operation Notes," and "Examples."
- SUMMARY
A brief summary of changes found in MPE/iX, including a quick
overview of the operation of the help facility.
- CLASS
A list of MPE/iX commands by functional class.
- HELPSTUDY
A beginner's guide designed to familiarize novice users with the
fundamentals of MPE/iX commands and command syntax.
- EXPRESSIONS
A description of CI expresssions
- FUNCTIONS
A list of all CI evaluator functions
- VARIABLES
A list of all CI predefined variables
- OPERATORS
A list of expression operators, like +, -, etc.
- HELP
The help facility entry on the HELP command.
- ALL
Displays the entire table of contents and the contents of each
keyword for the HELP command.
- EXIT
Exits the help subsystem. Help for the CI EXIT command is
not available in interactive mode. To get help for the CI
EXIT command, specify the direct mode in the form HELP
EXIT ALL.
Operation Notes
You use the HELP command to display information about MPE/iX in one of
two ways: by omitting command parameters to enter the Help subsystem or by
getting information about a single command from the colon prompt.
Using HELP as a subsystem
Enter the HELP command without specifying any parameters to invoke
HELP as a subsystem. You will see the first screen of Help, called
HELPMENU. It lists the choices available to you so that you can review the
operation of Help and get a brief overview of the changes found in the MPE/iX
operating system.
Once you are in the Help Subsystem, you display information by entering the
name of the command, UDC, error message, variable, expression, function or
other item that you want at the greater-than (>) prompt.
For example:
:HELP
>FINFO
Syntax: FINFO(filename, option)
Defn: A CI evaluator function that returns information about
the specified file.
Type: String, integer, or Boolean depending upon option.
Example: FINFO('x.pub',"EXISTS")
Result: TRUE
Example: FINFO('jeff',"eof")
Result: 71495
The following table summarizes the options of the FINFO function.
The description includes the option number, one or more aliases,
the data type, and a brief description of the option.
Num Alias Data Type Option Description
--- ----- --------- ------------------
0 EXIST Boolean Existence of file
1 FILENAME ONLY String File name
(24/225) Continue?
To display information up to the next keyword or command, press Return.
HELP provides a page break for every 23 lines of output and pressing
Return allows you to continue.
Do not precede the command or item name with HELP, or
you will get an error message. For example:
:HELP
>HELP FINFO
^
Can't find this keyword.
To exit the Help Subsystem, enter E or EXIT' or press
Break. To stop the display and return to a system prompt, enter
CTRL-Y. temporarily stops the display, enter CTRL-S. Use
CTRL-Q to resume.
Using HELP in direct mode
Enter HELP followed by the name of the command, UDC, error
number or other keyword to display the information you need without
entering the Help Subsystem. Entering any command name produces
the syntax for that command and a list of the keywords.
Entering a keyword such as PARMS produces a listing of all the items
for that keyword.
For example:
HELP ABORT
ABORT
Aborts current program or operation.
Syntax
ABORT
KEYWORDS: PARMS,OPERATION,EXAMPLE
:
Notice that in direct mode, MPE/iX displays the CI prompt (:) once it
has displayed the information you wanted.
Use
This command may be issued from a session, job, program, or in BREAK. Pressing
Break aborts the execution of this command.
Examples
To see the parameters for the LISTFILE command, enter:
:HELP LISTFILE PARMS
To see examples of the STORE command, enter:
:HELP STORE EXAMPLES
To see the same information from within the Help subsystem, enter:
:HELP
>STORE EXAMPLES
To see a list of predefined variables in MPE/iX, at the colon
prompt enter:
:HELP VARIABLES
Several global variables have been pre-assigned by
the command interpreter. They may be used anywhere you would use
your own variables.
All global variables are listed in the table below. To get help
with a specific variable, at the colon (:) prompt type "HELP"
followed by the variable name, for example, "HELP HPCIDEPTH".
At the Help facility prompt (>), simply type the variable name,
for example, "HPCIDEPTH".
Global Variable Types
=================================================================
R READ ONLY variable (cannot be modified).
W READ/WRITE variable (can be modified).
JCW A standard MPE/iX JCW.
I Integer format.
B Boolean format (TRUE/FALSE).
(24/225) Continue?
If LINKALL is a command file, HELP displays the file as
follows:
HELP LINKALL.TEST.UI
User-Defined Command File: LINKALL.TEST.UI
Parm streamflag=...
...
If VERSION.PUB.SYS is a program file, HELP displays:
HELP VERSION.PUB
program file: VERSION.PUB.SYS
If the UDC LISTF contains the NOHELP option (as shown in the
sample below) the HELP command will suppress the listing of this UDC,
and displays the text for the built-in command LISTF instead.
listf
option NOHELP
showme
*****
If the UDC MYUDC (which is not the name of any MPE/iX command)
contains the NOHELP option, then the Help facility displays an error.
Related Information
- Commands
None
- Manuals
System Startup, Configuration, and Shutdown Reference
Manual
Used to control the execution sequence of a job, UDC, or command file.
(Native Mode)
Syntax
IF expression [THEN]
Parameters
- expression
Logical expression, consisting of operands and relational operators.
The operators listed in Table 7-1
"Logical Operators - The IF Command" may be incorporated in
expression.
Table 7-1 Logical Operators - The IF Command
Logical operators: |
AND, OR, XOR, NOT |
Boolean functions and values: |
BOUND, TRUE, FALSE, ALPHA, ALPHANUM, NUMERIC, ODD |
Comparison operators: |
=, <>, <, >, <=, >= |
Bit manipulation operators: |
LSL, LSR, CSR, CSL, BAND, BOR, BXOR, BNOT |
Arithmetic operators: |
MOD, ABS, * , / , + , -, ^ (exponentiation) |
Functions returning strings: |
CHR, DWNS, UPS, HEX, OCTAL, INPUT, LFT, RHT, RPT, LTRIM, RTRIM, STS |
Functions returning integers: |
ABS, LEN, MAX, MIN, ORD, POS, TYPEOF |
Other functions: |
FINFO, SETVAR |
The allowed operands are any variable, integer, string, or Boolean constants,
and the MPE/iX reserved words are WARN, FATAL,
SYSTEM, and OK.
Compound logical expressions can be formed using the AND, NOT, XOR, and OR
logical operators, and nested within parentheses.
The THEN keyword is optional. It may be used or omitted and has no
effect on the results.
Operation Notes
This command begins an IF block consisting of all the commands
after the IF command up to, but not including, the next ELSE.
ELSEIF, or ENDIF statement. The ELSE, ELSEIF, or ENDIF must have
the same nesting level as the IF statement. Another similar block can
follow the ELSE statement.
Nesting of the blocks is allowed to 30 levels so long as IF
is used alone. In a case where IF is used with WHILE the total nesting
of IF and WHILE blocks cannot exceed 30 levels. Each IF or WHILE
block read by the Command Interpreter increments the nesting count even
if it resides within a different UDC or COMMAND file.
The ENDIF statement ends the IF block. The logical expression
is evaluated and, if the expression evaluates to TRUE, the IF block
is executed; if FALSE, the ELSE or ELSEIF block (if one exists)
is executed.
|
NOTE: You may not write an IF construct in such a way that it physically
crosses from one user command (UDCs or command files) to another.
|
Use
This command may be issued from a job, session, program, or in BREAK. Pressing
Break has no effect unless expression contains the INPUT
evaluator function.
Example
The following job listing illustrates the use of an IF statement with ELSE and
ENDIF statements:
!CONTINUE
!PASXL MYPROG,MYUSL
!IF JCW>=FATAL THEN
! TELL USER.TECHPUBS;COMPILE FAILED
!ELSE
! TELL USER.TECHPUBS;COMPILE COMPLETED
!ENDIF
Related Information
- Commands
CALC, ELSE, ELSEIF, ENDIF,
WHILE, ENDWHILE, ESCAPE,
RETURN
- Manuals
Appendix B, "Expression Evaluator Functions"
Permits the user to assign a value interactively to any variable that could
otherwise be set with the SETVAR command. The user may also create an
optional prompt string and have it displayed on $STDLIST before the
value is read. (Native Mode)
Syntax
INPUT [NAME=] varname [;PROMPT=prompt] [;WAIT=seconds]
[;READCNT=chars]
|
NOTE: This command follows the optional MPE/iX command line syntax.
Refer to "Optional Format for MPE/iX Commands" at the beginning of this chapter.
|
Parameters
- varname
Any variable (that can be set with SETVAR) in which the input
string from $STDIN is stored. If varname does
not already exist, INPUT creates it.
- prompt
The prompt string that is to be displayed on the standard listing
device. If prompt is omitted, nothing displays, but
INPUT then waits for an input value to store in
varname. To include delimiters, for example, a comma
(,) or semicolon (;) as part of the prompt string, you
must surround the entire prompt string with quotation marks
(" or ").
- seconds
A positive value specifying the number of seconds for a timed read.
If a value is assigned to seconds, the prompt waits
seconds for input and then terminates the command. The
default is zero, no time limit.
- chars
The number of characters you want read from $STDIN. If chars is
specified as a negative number, INPUT uses the absolute integer value.
The maximum allowed (and the default) is the maximum size of a CI
variable, which is currently 1024 characters.
Operation Notes
This command allows the user to assign a value interactively to a variable. It
also allows the user to create an optional prompt message that is displayed on
the standard list device ($STDLIST) before the value is read. This
command provides a way to establish an interactive dialog with an executing UDC
or command file. If it does not already exist, the variable
varname is always created by INPUT. If you want to
delete varname before ending a session, job, or program, use
DELETEVAR varname. Refer to the DELETEVAR
command.
CI input redirection can be used to set varname to a record in
a file.
|
NOTE: If a colon (:) is read by the INPUT command at
any level other than the root level CI, the error message END OF FILE ON
INPUT. (CIERR 900) is returned.
|
INPUT reads a value from the standard input device ($STDIN)
and stores it as a string in the variable named varname. If
varname does not exist, INPUT creates it. If
prompt is omitted, nothing is displayed, and INPUT
waits for an input value to store in varname. The variable
varname can be used as you would use any other MPE/iX string
variable.
CI input redirection can be used to set varname to a record in a file.
|
NOTE: The INPUT command does not evaluate an expression before
assigning its value to varname. The command recognizes only
strings. Expressions such as 9 + 3 are treated as strings, even though they are
not surrounded by quotation marks (" or ").
|
The user may optionally specify a timed read by creating a value for
seconds. The pending read prompt is canceled after
seconds. The INPUT command recognizes the
HPTIMEOUT variable. The length of the timed read is
seconds or HPTIMEOUT (in minutes), whichever is
smaller. If a timed read (using seconds or HPTIMEOUT)
expires, then the pending read terminates.
If varname already exists and you enter a null (a
Return), then the value of varname remains
unchanged.
The same thing happens if varname exists and
seconds or HPTIMEOUT expires before a value
for varname is entered. In this case, however, a
warning occurs, and CIERROR is set to 9003.
If varname does not exist and a null (a
Return) is entered for the variable value, then
varname is created and set to null ("").
If varname does not exist and
seconds or HPTIMEOUT expires, then
varname is created and set to null (""), and
CIERROR is set to 9003.
If the timed read expires due to the value of the
HPTIMEOUT variable, for example, HPTIMEOUT=1
(in minutes) and the user executes INPUT bleep,,65, then the
session is logged off.
Use
This command is available in a session, job, program, or in BREAK. Pressing
Break aborts the execution of this command, without creating
or modifying varname.
Examples
The INPUT command does not evaluate expressions, it stores them as a
string. For example, the command INPUT bleep accepts and stores input
(somevalue). If you want somevalue treated as
an expression and evaluated and the result assigned to bleep (as
opposed to assigning the string representation of somevalue),
use the SETVAR command after using the INPUT command:
INPUT bleep
SETVAR bleep !bleep
The first command reads whatever value you enter and sets bleep to the
string representation of that input. The second command assigns bleep
the (evaluated) value that you entered.
INPUT MYVAR <FILEONE
The above example reads the first record in FILEONE into the CI variable named
MYVAR. In order to read the entire contents of a file INPUT must be in a WHILE
loop and the while loop must have its $STDIN redirected to the file. Eg:
READFILE <FILENAME, where READFILE looks like:
SETVAR EOF FINFO(HPSTDIN, 'EOF')
WHILE SETVAR (EOF, EOF-1) >=0 DO
INPUT MYVAR
...
ENDWHILE
Table 7-2 "INPUT Command Function"
illustrates how the INPUT command functions.
Table 7-2 INPUT Command Function
INPUT bleep and the user responds with: |
What is stored in bleep: |
Value* of bleep after SETVAR bleep !bleep: |
001 | 001 | 1 (integer) |
"001" | "001" | 001 (string) |
TRUE | TRUE | TRUE (Boolean) |
9+3 | 9+3 | 12 (integer) |
Return |
(null) or bleep is not modified if it already exists |
<<error from the parser>> |
* The result is an error if the user responds with an unquoted
string:
INPUT BLEEP,>
>ABC Return
SETVAR BLEEP !BLEEP
ABC is not a number. And, without quotes around it, ABC is
not a string, either. If ABC is not a defined variable, it has no
value to extract. So, the attempt to evaluate the result of explicitly
dereferencing, !BLEEP produces an error. Refer to the SETVAR
command.
Related Information
- Commands
DELETEVAR, SETVAR, SHOWVAR,
INPUT( ) function
- Manuals
Using the HP 3000 Series 900: Advanced Skills
Defines a job to be activated with the STREAM command or an input
spooled device to run in batch mode. (Native Mode)
Syntax
JOB[ jobname,] username[/userpass].acctname[/acctpass]
[,groupname[/grouppass]]
[;TIME=cpusecs] [;PRI= BS | CS | DS | ES]
[;INPRI=inputpriority | ;HIPRI] [;RESTART] [;JOBQ=queuename]
[;OUTCLASS=[[DEVICE][,[OUTPUTPRIORITY][,NUMCOPIES]]]]
[;TERM={termtype}] [;PRIVATE][;SPSAVE]
Parameters
- jobname
Arbitrary name used with username and
acctname parameters to form a job identity. The name must
contain from one to eight alphanumeric characters, beginning with an
alphabetic character. Default is that no job name is assigned.
- username
User name, established by the account manager, that allows you to log
on to this account. The name must contain from one to eight alphanumeric
characters, beginning with an alphabetic character.
- userpass
User password, optionally assigned by account manager. The password
must contain from one to eight alphanumeric characters, beginning with an
alphabetic character. If a password exists, but is not
supplied in the command syntax, the STREAM command will prompt
you for it if:
The STREAM command is invoked from a session.
Neither $STDIN nor $STDLIST is redirected.
The JOB command is a first level JOB command (it
is not nested within a second level STREAM command).
If the password is supplied in the command syntax it must be preceded by
a slash (/).
- acctname
Account name as established by the system manager. The name must
contain from one to eight alphanumeric characters, beginning with an
alphabetic character. The acctname parameter must be
preceded by a period (.).
- acctpass
Account password, optionally assigned by the system manager. The
password must contain from one to eight alphanumeric characters,
beginning with an alphabetic character. If a password exists, but is
not supplied in the command syntax, the STREAM
command will prompt you for it if:
The STREAM command is invoked from a session.
Neither $STDIN nor $STDLIST is redirected.
The JOB command is a first level JOB command
(it is not nested within a second level STREAM
command).
If the password is supplied in the command syntax it must be preceded by
a slash (/).
- queuename
The name of the job queue the job will execute in. The default job
queue is HPSYSJQ, which is a global queue for all jobs not associated
with an individual job queue
- groupname
Group name to be used for the local file domain and for CPU-time
charges, as established by the account manager. The name must contain
from one to eight alphanumeric characters, beginning with an alphabetic
character. Default is home group if one is assigned. (Required if a home
group is not assigned.)
- grouppass
Group password, optionally assigned by the account manager. The
password must contain from one to eight alphanumeric characters,
beginning with an alphabetic character. The group password is not needed
when you log on to your home group. It is needed when you log on under
any other group for which a password exists. If a password is needed, but
is not supplied in the command syntax, the
STREAM command will prompt you for it if:
The STREAM command is invoked from a session.
Neither $STDIN nor $STDLIST is redirected.
The JOB command is a first level JOB command (it
is not nested within a second level STREAM command).
If the password is supplied in the command syntax it must be preceded by
a slash (/).
- cpusecs
Maximum CPU time allowed job, in seconds. When this limit is reached,
the job is aborted. This must be a value from 1 to 32,767. To specify no
limit, enter a question mark or UNLIM, or omit this parameter.
Default is a system-configured job limit.
- BS, CS, DS, or ES
The execution priority queue that the command interpreter
uses for your session. This is also the default priority for all
programs executed within the session. BS is the highest priority;
ES is the lowest. If you specify a priority that exceeds the highest
priority permitted for your account or user name by the system,
MPE/iX assigns the highest priority possible below BS. DS and ES
are intended primarily for batch jobs; their use for sessions is
generally discouraged. DS is the default and the maximum priority,
unless modified by system management.
|
NOTE: Use care in assigning the BS queue. Processes in this priority
class can lock out other processes.
For information on the guidelines for these priority queues, refer to the
TUNE command in this chapter.
|
- inputpriority or HIPRI
Determines the input priority of the job. The
inputpriority parameter is the relative input priority
used in checking against access restrictions imposed by the jobfence. The
inputpriority parameter takes effect at logon time and
must be from 1 (lowest priority) to 13 (highest priority). If you supply
a value less than or equal to the current jobfence set by the system
operator, the job is denied access. Default is 8.
The HIPRI option is used for two different purposes when logging
on. It can be used to override the system jobfence, or it can be used to
override the job limit. When using the HIPRI option to override
the jobfence, the system first checks to see if you have system manager
(SM) or system operator (OP) capability. If you have either of these
capabilities, you are logged on and your INPRI defaults to the
system's jobfence and execution limit. If you do not have either of these
capabilities, the system attempts to log you on using INPRI=13
and succeeds if the jobfence is 12 or less, and if the job limit is not
exceeded. In attempting to override the job limit (to log on after the
maximum number of jobs set by the operator has been reached), you can
specify HIPRI, but to do so you must have either SM or OP
capability. The system does not override the job limit automatically. Use
of the HIPRI option without SM or OP capability causes the
following warning to be displayed:
MUST HAVE 'SM' OR 'OP' CAP. TO SPECIFY HIPRI,
MAXIMUM INPRI OF 13 IS USED (CIWARN 1460)
- RESTART
Request to restart a spooled job that has been interrupted by the
system termination/restart. This parameter takes effect automatically
when the system is subsequently restarted with the START RECOVERY
option. The effect is to resubmit the job in its original form.
This parameter applies only to jobs initiated on spooled input devices.
It is ignored for other jobs. Default is that spooled jobs are not
restarted after system termination/restart.
- device
Class name or logical device number (ldev) of the
device to receive listing output. You cannot specify a magnetic tape
unit. If the parameter is not a valid LDEV or class name, an error is
generated. Default is defined in the system configuration.
|
NOTE: Nonshareable device (ND) file access capability is required in
order to use this parameter.
|
- outputpriority
The output priority for job list file, if destined for spooled line
printer. This parameter is used to select the next spooled device file
(on disk) for output, from among all those contending for a specific
printer. Must be a value from 1 (lowest priority) to 13 (highest
priority). When outputpriority is 1, output is always
deferred. To have output printed from disk, use an
outputpriority of 2 or greater.
This parameter applies only to output destined for spooled output
devices, and is ignored for other output. Default is 8.
- numcopies
Number of copies of job listing to be produced. This parameter applies
only when listing is directed to a spooled device, and is ignored in
other cases. If the number of copies is less than 1, a warning is issued.
The command still executes with the default value of 1. If the number of
copies is greater than 127, an error message is printed, and 127 copies
are printed. Default is 1.
- termtype
The TERM= option is obsolete now that the JOB
command cannot be used interactively. In order to maintain backward
compatability, the termtype parameter is still parsed,
but it is not used. If the TERM= option is used, a warning
message will be displayed.
- PRIVATE
The PRIVATE option forces the job output $STDLIST to
be a private spoolfile. The spoolfile is only accessible to privileged
users on the system. Private spoolfiles may not be saved or copied. They
may only be purged, printed, or (within limits) altered.
- SPSAVE
If this option is used, the resulting job output $STDLIST
spoolfile is created with an SPSAVE disposition. This means that
the spoolfile is not to be purged after the last copy of it has been
printed, but is instead retained in the OUT.HPSPOOL group.
SPSAVE may not be used if PRIVATE has been
specified.
|
NOTE: The "&" symbol has no meaning to the input spooler when it
reads records because the CI is not involved at that point.
|
Operation Notes
The JOB command is not used at the colon prompt (:). Rather,
it is used in interactive mode with the STREAM command at the
> prompt, or within an input jobfile, created to define a batch
job. The job defined with this command is then activated (executed) with the
STREAM command.
The JOB command is preceded by an appropriate substitute prompt
character for the colon prompt. By default, MPE/iX expects the exclamation
point (!) to be used. The JOB command must be terminated with
an EOJ command. Refer to the STREAM command.
When MPE/iX begins the job, it displays the following information on the list
device:
Job number, as assigned by MPE/iX to identify the job.
Date and time.
"HP 3000," and the modified and base MPE/iX
version.update.fix numbers.
In the JOB command, as in the HELLO command, you must always
supply your username and acctname, which you
obtain from your account manager. If you omit either of these parameters, or
enter them incorrectly, MPE/iX rejects your job and prints error messages on
the standard listing device and the console. If your job is accepted, MPE/iX
begins job processing. The job is entered with the STREAM command or
through a spooled input device. Then the job is copied to an input spoolfile.
The job is initiated from that spoolfile rather than the originating diskfile
(in the case of the STREAM command) or device (in the case of the
input spooled device). If the standard listing file is a line printer, MPE/iX
prints a header page prior to listing the JOB command. (The system
operator can disable the printing of this header page with the HEADOFF
console command.)
The job number assigned by MPE/iX always uniquely identifies your job to MPE/iX
and other users. MPE/iX assigns such numbers in sequential order as jobs are
accepted. Sometimes, the job acceptance information includes a message from the
system operator following the standard display. When present, this is the same
message output in the logon information for sessions.
The minimum information needed for job initiation is the user and account name.
However, the following also may be required:
The cases in which this information is required, and the rules for supplying
it, are the same as those for the HELLO command for sessions, except
that:
When you enter the JOB command through a device other
than a terminal, and the standard input device is different from the
standard listing device, MPE/iX does not echo passwords.
When the standard listing device is a line printer and you do not
specify a file group name, central processor time limit, execution
priority, and/or input priority in the JOB command, the
default values assigned by MPE/iX for the omitted parameters appear
on the job listing.
The STREAM command prompts for any necessary passwords that are not
supplied in the command syntax if:
The STREAM command is invoked from a session.
Neither $STDIN nor $STDLIST is redirected.
The JOB command is a first level JOB command (it
is not nested within a second level STREAM command).
All UDCs are available from a job. Any subsystem or UDC that expects input from
$STDIN requires that input within your job stream file.
Use
This command may be issued only from a job file. It may not be used from a
session, program, or in BREAK. Pressing Break has no effect on this
command.
Example
The following example illustrates creating and using an ASCII file to define a
batch job and then executing it with the STREAM command:
RUN EDITOR.PUB.SYS
/ADD
1 !JOB WXYZ,WRITER.TEC
2 !EDITOR
3 TEXT ABC
4 LIST ALL,OFFLINE
5 EXIT
6 !EOJ
//
/KEEP MYJOB
/EXIT
:STREAM MYJOB
The following example shows using the JOB command in interactive mode
with the STREAM command:
STREAM
>!JOB USER.TECHPUBS;OUTCLASS=12
Related Information
- Commands
ABORTJOB, ALTJOB, BREAKJOB,
SUSPENDJOB, RESUMEJOB, JOBFENCE,
JOBPRI, STREAM, STREAMS,
SHOWDEV, NEWJOBQ, LISTJOBQ
- Manuals
Using the HP 3000 Series 900: Advanced Skills
MPE/iX Intrinsics Reference Manual
Defines the minimum input priority that a job or session must
have in order to execute. (Native Mode)
Syntax
JOBFENCE priorityfence
Parameters
- priorityfence
A number between 0 and 14, inclusive. Within this range, smaller
numbers are less limiting; larger numbers more limiting.
Operation Notes
MPE/iX does not dispatch jobs or sessions with an input priority less than or
equal to the priorityfence until their input priority is raised
with the ALTJOB command, or until the jobfence is lowered. System
managers and system supervisors may override the jobfence setting by logging on
with the HIPRI parameter of the JOB or HELLO
commands. Or, they may log on with an input priority greater than the jobfence
as reported by the SHOWJOB command.
Use
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 unless distributed to users with the ALLOW command.
Examples
To defer all non-HIPRI jobs and sessions, first set the jobfence to
14, as shown below:
JOBFENCE 14
16:18/#J7/34/DEFERRED JOB INTRODUCED ON LDEV #10
16:18/#J8/35/DEFERRED JOB INTRODUCED ON LDEV #10
Then enter the SHOWJOB command to display the effect of the new
jobfence.
SHOWJOB
JOBNUM STATE IPRI JIN JLIST INTRODUCED JOB NAME
#S26 EXEC 20 20 THU 4:17P OPERATOR.SYS
#J7 WAIT D 8 10S 12 THU 4:18P JOB1,FIELD.SUPT
#J8 WAIT D 8 10S 12 THU 4:18P JOB2,FIELD.SUPT
3 JOBS:
0 INTRO
2 WAIT; INCL 2 DEFERRED
1 EXEC; INCL 1 SESSIONS
0 SUSP
JOBFENCE= 14; JLIMIT= 5; SLIMIT=16
Finally, reset the jobfence to 6 to allow waiting jobs to
log on:
JOBFENCE 6
16:21/#J7/34/LOGON FOR: JOB1,FIELD.SUPT ON LDEV #10
16:21/#J8/35/LOGON FOR: JOB2,FIELD.SUPT ON LDEV #10
Related Information
- Commands
ABORTJOB, ALTJOB, BREAKJOB, JOB,
SUSPENDJOB, RESUMEJOB, JOBPRI, STREAM,
STREAMS, SHOWDEV
- Manuals
Using the HP 3000 Series 900: Advanced Skills
MPE/iX Intrinsics Reference Manual
Sets or changes the default execution priority for batch jobs
and sets a maximum execution priority for batch jobs. (Native Mode)
Syntax
JOBPRI [maxsubqueue] [,defaultsubqueue]
Parameters
- maxsubqueue
The maximum priority at which batch jobs are allowed to run. This
overrides any job priority a user may have requested with the
JOB command. This parameter may be ES, DS, CS, or zero. If zero
is specified, no limit is imposed on batch jobs. Default is no change
in maximum priority.
- default- subqueue
The default execution priority for batch jobs, which may be ES, DS, or
CS. This takes effect if a user does not specify an execution priority in
the JOB command. Default is no change in execution
priority.
Operation Notes
The maxsubqueue parameter specified in the JOBPRI
command takes precedence over defaultsubqueue. Therefore,
selecting a default parameter greater than the value of
maxsubqueue parameter does not affect job execution. Jobs are
still initiated with the maximum priority parameter.
Use
This command may be issued from a session, job, program, or in BREAK. Pressing
Break has no effect on this command. System supervisor (OP) capability
is required to execute this command.
Example
To raise the maximum execution priority so that batch jobs can run in any
subqueue requested, enter:
JOBPRI 0
Related Information
- Commands
TUNE, SHOWQ, ALTPROC
- Manuals
Performing System Operation Tasks
Designates what level of user may request resources and control
the execution of jobs. (Native Mode)
Syntax
JOBSECURITY [{ HIGH | LOW }
{;PASSEXEMPT= {NONE | USER | XACCESS | MAX} }]
Parameters
- HIGH
Permits only the operator logged on at the console and users with SM
capability to use job control commands.
- LOW
Allows individual users to exercise control over their own
jobs.
- <omitted>
If you do not specify HIGH or LOW, the current job
security status is displayed (high or low).
- NONE, USER, XACCESS, or MAX
The PASSEXEMPT option set by the system manager, which has
the following meaning:
- NONE
All users must specify the required passwords to stream a
job.
- USER
Allows certain users to omit a job's password. The system manager
can omit the password when streaming any job, account managers can
omit passwords when streaming jobs that log onto their account and to
which they have access, and users can omit passwords for jobs that
match their logon identity and to which they have access.
- XACCESS
Allows users with execute access to the job file to omit passwords
when the job file logs on with the same identity as its owner or
creator.
- MAX
Sets both the USER and the XACCESS options of
the PASSEXEMPT parameter. Specifying MAX is the
only way to set both options since USER and XACCESS
are otherwise mutually exclusive.
Operation Notes
The HIGH and LOW parameters of the JOBSECURITY command determine
what kind of user may execute the ABORTJOB, ALTJOB, BREAKJOB and
RESUMEJOB commands. When JOBSECURITY is set to HIGH, only the operator
may issue these commands. When it is set to LOW, any user may issue
these commands for their own jobs (i.e., those where the job's user
name and account matches the user's) and Account Managers may control the
execution of any job in their account.
System managers may use the PASSEXEMPT parameter of the JOBSECURITY
command to control password validation when users stream a job.
If you have never used the PASSEXEMPT parameter and if the HP Security
Monitor is not installed, the initial state is NONE, which means
that job passwords are required. When you reboot the system with a
START RECOVERY the last PASSEXEMPT state is preserved.
PASSEXEMPT provides some of the functionality of the HP Security
Monitor. For example, PASSEXEMPT=USER is equivalent to the stream
privilege feature. PASSEXEMPT=XACCESS is similar to the stream authorize
feature with one difference: you may set the USER XACCESS options
independently, whereas HP Security Monitor requires you to enable
stream privilege when you want to enable the stream authorize feature.
JOBSECURITY checks for the existence of HP Security Monitor
and, if necessary, combines the settings to produce appropriate
output. When the PASSEXEMPT parameter is issued and the interaction
with the HP Security Monitor produces a different result, you will
see a warning and a notification that the HP Security Monitor is
installed. The resulting command output is also displayed with the
warning.
Use
You may issue the JOBSECURITY command 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 command.
Example
To allow any user to abort, alter, break, or resume their own jobs, enter:
JOBSECURITY LOW
To find out the current job security status, enter:
:JOBSECURITY
JOB SECURITY IS HIGH. PASSEXEMPT IS NONE.
To set the password exemption to USER and then check the current
status, enter:
:JOBSECURITY ;PASSEXEMPT=USER
:JOBSECURITY
JOB SECURITY IS LOW. PASSEXEMPT IS USER.
Suppose PASSEXEMPT is currently set to USER and you want to
change it to XACCESS. To do so, enter:
:JOBSECURITY ;PASSEXEMPT=XACCESS
Then check the current status by entering:
:JOBSECURITY
JOB SECURITY IS LOW. PASSEXEMPT IS XACCESS.
If the HP Security Monitor is installed with both stream privilege and
authorization turned on, the JOBSECURITY command will display a
warning when the output produces a different result.
:JOBSECURITY ;PASSEXEMPT=USER
Security Monitor is installed. Passexempt is MAX. (CIWARN 3128)
Related Information
- Commands
ABORTJOB, ALTJOB, BREAKJOB,
RESUMEJOB, JOBFENCE
- Manuals
Performing System Operation Tasks
Cancels a previously issued LMOUNT or VSRESERVE command. This
informs the system that the volume set is no longer reserved system-wide. The
equivalent native mode command is VSRELEASESYS. (Native Mode)
Syntax
LDISMOUNT [{ * | volumesetname }] [,groupname [.acctname]]
Parameters
- * or <blank>
Specifies the home volume set for the group and account specified, or
for the logon group and account if groupname or
groupname.acctname is not specified.
- volumesetname
An artificial component of a volume set name used to maintain backward
compatibility with MPE V/E. The volumesetname can be a
maximum of 8 characters.
- groupname
Used only for compatibility with MPE V/E. The groupname
can be a maximum of 8 characters.
- acctname
Used only for compatibility with MPE V/E. The acctname
can be a maximum of 8 characters.
Operation Notes
The LDISMOUNT command negates a previously issued LMOUNT or
VSRESERVE command. It informs MPE/iX that the volume set is no longer
reserved system-wide.
Volume sets in MPE/iX are not tied to groups and accounts. This is different
from the MPE V/E scheme of disk partitioning.
Table 7-3 "Command Acceptance of Naming
Conventions - LDISMOUNT Command" is a comparison of naming conventions for
MPE/iX volume sets and MPE V/E private volumes. MPE/iX volume set names may
consist of any combination of alphanumeric characters, including the underbar
(_) and the period (.). The name must begin with an
alphabetic character and consist of no more than 32 characters.
Table 7-3 Command Acceptance of Naming Conventions - LDISMOUNT Command
Specify |
MPE V/E xxxMOUNT Command Accesses |
MPE/iX VSxxxxxx Command Accesses |
myset.grp.acct |
The volume set named myset.grp.acct. |
The volume set named myset.grp.acct. |
myset |
The volume set named myset.logongrp.logonacct. |
The volume set myset. |
*.grp.acct. |
The home volume set of the group grp in account acct. |
Causes an error. |
myset_grp_acct |
Error (name component longer than eight characters). |
The volume set named myset_grp_acct. |
m_g_a |
The volume set named m_g_a.logongrp.logonacct, provided it
exists. If it does not exist, an error is reported. |
The volume set name m.g.a. |
In MPE V/E, the name V.G.A indicates that V is the name of a
volume set, that G is the name of a group, and that A is the
name of an account.
MPE/iX accepts that name in that form, but no interpretation is made as to the
referencing of G and A. Instead, MPE/iX accepts that name in
that form, but no interpretation is made as to the referencing of G
and A. MPE/iX treats V.G.A. as a single, long string name,
just as it would treat A_VERY_LONG_NAME_FOR_SOMETHING.
MPE/iX does, however, accept the naming convention that was used for MPE V/E
private volumes. Therefore, LDISMOUNT V.G.A succeeds, and
LDISMOUNT V accesses the same volume set, provided you are logged on
to account A, group G. The MPE V/E commands are able to
"default" the logon account and group.
However, VSRESERVE V succeeds only if there is a volume set V
in existence. The MPE/iX commands do not call up any default specifications for
group and account. VSRESERVE V.G.A succeeds only if a volumeset
V.G.A is online. With MPE/iX VSxxxxxx commands, the
.G.A component of this name is interpreted as a string, neither more
nor less specific than _G _A.
If a volume set is named according to the MPE V/E naming convention
(V.G.A), you must use an unambiguous reference when using the MPE/iX
volume set commands.
It is recommended that you not use the MPE V/E naming convention and the
xxxMOUNT commands. Instead use the MPE/iX naming convention and the
VSxxxxxx commands. Alternating between MPE V/E and MPE/iX commands may
lead to errors. For example, MOUNT X used in a job stream attempts to
access a volume set named X.logongrp.logonacct, which may or may not
be your intention.
Use
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 command.
Examples
To release a volume set named DATABASE.PAYROLL.ACCTNG, enter:
LDISMOUNT DATABASE.PAYROLL.ACCTNG
You may also use the VSRELEASESYS command:
VSRELEASESYS DATABASE.PAYROLL.ACCTNG
Related Information
- Commands
MOUNT, , LMOUNT, DISMOUNT, DSTAT,
VSRESERVE, VSRELEASE
- Manuals
Volume Management Reference Manual
Limits the number of concurrently running jobs/sessions. (Native Mode)
Syntax
LIMIT [ [[ + | - ] numberjobs] [,[ + | - ] numbersessions] ]
[;JOBQ=queuename]
Parameters
- +
Increment the limit value
- -
Decrement the limit value
- numberjobs
The number of jobs.
- numbersessions
The number of sessions.
- <omitted>
If you specify no parameter, a message is displayed listing the
current limits.
- queuename
The name of the job queue whose limit is being changed or
displayed.
Operation Notes
Maximum job and session limits are established by the system supervisor during
system configuration. Within these limits, the operator may redefine the job
and session limit with the LIMIT command. When the system is restarted
from disk in a START RECOVERY, the operator defined limits are
retained. When any other startup option is used, the values configured by the
supervisor take effect.
If you enter one parameter and omit the other, the limit of the omitted
parameter remains unchanged.
No new jobs or sessions are dispatched that would cause either of these limits
to be exceeded, unless they are initiated with the HIPRI parameter of
the JOB or HELLO commands.
Jobs that belong to individual job queues cannot begin execution while the
specific job queue limit is exceeded. Even if a specific job queue limit is not
exceeded, the global system job limit must also not be exceeded in order for
the job to begin execution.
Non-HIPRI jobs can still be introduced when the limit is achieved, but
they do not execute.
If you attempt to log on to a non-HIPRI session after the limit has
been reached, you receive the message:
CAN'T INITIATE NEW SESSIONS NOW
The specified limits may be exceeded at the time the command is issued. This
does not cause jobs or sessions executing at the time to abort. They continue
to execute, but no new jobs are allowed to enter the executing state, and no
new sessions are initiated.
Use
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 unless distributed to users with the ALLOW command.
Examples
To limit the number of jobs to 2 and the number of sessions to 15, enter:
LIMIT 2,15
SHOWJOB
JOBNUM STATE IPRI JIN JLIST INTRODUCED JOB NAME
#S24 EXEC 20 20 TUE 1:54A OPERATOR.SYS
#S26 EXEC 177 177 TUE 5:01A CHEWY,RSPOOL.S
#S96 EXEC QUIET 35 35 TUE 8:31A SLIDES.SIMON
3 JOBS:
0 INTRO
0 WAIT; INCL 0 DEFERRED
3 EXEC; INCL 3 SESSIONS
0 SUSP
JOBFENCE= 6; JLIMIT= 2; SLIMIT= 15
To limit the number of sessions to 13, but retain the current job limit, enter:
LIMIT,13
Related Information
- Commands
HELLO, JOB, SHOWJOB, LISTJOBQ
- Manuals
Performing System Operation Tasks
Creates an executable program file by merging the relocatable object modules
from all the files in its FROM= parameter. Those files may correspond
to object files, relocatable files, or a combination of them. It also searches
any relocatable libraries mentioned in the RL= parameter list and
merges any modules within those libraries that resolve an external reference.
(Native Mode)
Syntax
LINK [FROM=file [,file...] [;TO=destfile] ]
[;RL=rlfile [,rlfile...]]
[;XL=xlfile [,xlfile...]]
[;CAP=caplist]
[;NMSTACK=nmstacksize] [;NMHEAP=nmheapsize]
[;UNSAT=unsatname]
[;PARMCHECK=checklevel]
[;ENTRY=entryname]
[;NODEBUG] [;MAP] [;SHOW] [;SHARE]
[;PRIVLEV=priv_level] [;PRI=pri_level]
[;MAXPRI=max_pri_level
|
NOTE: This command follows the optional MPE/iX command line syntax.
Refer to "Optional Format for MPE/iX Commands" at the beginning of this chapter.
|
Parameters
- file
The name of an object file or a relocatable library file. It may be
any binary file of type NMOBJ or NMRL. All relocatable
objects in the FROM= specified list are merged to form the
program file specified by destfile. If you omit this
parameter, LINK merges the object modules in the file
$OLDPASS.
The FROM=, RL=, and XL= parameters allow a
series of file names. You may name each file individually, or you may
provide an indirect file by preceding that file's name with the caret
symbol (^).
- destfile
The name of the program file (type NMPRG) where LINK
places the resulting executable object module. If
destfile does not exist, LINK creates a new one
for you. If destfile does exist, it is destroyed and
replaced by the object module created by the current link
operation.
- rlfile
The name of a relocatable library file (type NMRL) that
resolves an external reference made by an object module in the
FROM= file list. LINK searches the relocatable
libraries in the RL list in the order in which you list them.
If a module from one library calls a routine in another library and then
that routine in turn refers to a module in the first library, you may
need to include the first library twice so that LINK can resolve
this "circular" reference.
The FROM=, RL=, and XL= parameters allow a
series of file names. You may name each file individually, or you may
provide an indirect file by preceding that file's name with the caret
symbol (^).
- xlfile
The name of an executable library (type NMXL). The loader
searches every executable library in the XL list in an attempt
to resolve external references that remain in a program file.
- caplist
The list of capability attributes to be assigned to the program file.
The program runs only if the group and account have matching
capabilities. (The system manager or account manager assigns these
capabilities to your group and account.) Permissible values are:
BA = Local Batch Access
IA = Interactive Access
PM = Privileged Mode
MR = Multiple RINs
DS = Extra Data Segments
PH = Process Handling
If you omit this parameter, the BA and IA capabilities are assigned to
the program file by default.
- nmstacksize
The maximum size, in bytes, to which the NM stack may grow. This must
be a decimal number. The default is zero, which instructs MPE/iX to
assign a system-defined constant as the value of
nmstacksize.
- nmheapsize
The maximum size, in bytes, to which the NM heap may grow. This must
be a decimal number. The default is -1, which instructs the command to
assign a system-defined constant as the value of
nmheapsize.
- unsatname
The name of a procedure that the loader substitutes in place of any
external reference that cannot be resolved in a program file. If you omit
this parameter and any external references remain unresolved, the loader
reports a load-time error.
- checklevel
An integer specifying the maximum level of checking that LINK
performs in binding external references to procedures. All checking
levels that are indicated in external references and procedure
definitions are reduced (but never increased) to the specified level. If
you omit this parameter, LINK sets the value to 3.
Permissible values for checklevel are defined in
Table 7-4 "Checklevel Values".
If the checking level is restricted (reduced) and reportable type errors
are detected, they are reported not as errors but as warnings.
Table 7-4 Checklevel Values
0 | No parameter check. |
1 | Check of the symbol type descriptor. |
2 | Perform Level 1 checking, then check the number
of arguments that the import procedure passed against the minimum and
maximum range that were declared in the export procedure. |
3 | Perform Level 2 checking, then check the type
of each argument that was passed. |
- entryname
The name (label) of the point within a program where
execution begins. When you omit this parameter, the loader begins
execution from the primary program entry point (which corresponds
to a program's main procedure or outer block). However, by including
the ENTRY= option, you may override this default value and
begin execution from the specified entry point. If the loader fails
to find a symbol that matches the entry point name, it reports a
load-time error.
- NODEBUG
Strips all symbolic debugging information from the
resulting program file. If you omit this parameter, the file contains
debugging information if the source file was compiled with this
option.
- MAP
Prints a symbol map to the list file, LINKLIST.
- SHOW
Displays the name of each object module as it is being merged into the
program file. You may include this option to verify the order in which
LINK processes each module.
- priv_level
Determines the privilege level used by the executable program file.
This parameter changes the privilege level of all procedures in the
symbol and export tables (of the relocatable object file) that were set
during compilation.
The values for priv_level are:
- 0
system level access
- 1
unused
- 2
privileged level access
- 3
user level access
The default is that privilege levels are set during compilation.
- pri_level
Specifies the execution priority that the program will have at run
time. The pri_level has to be one of BS, CS, DS, ES, or a
number between 100 and 255 inclusive. This value can be overridden by the
PRI= keyword on the RUN command.
- max_pri_level
Specifies the maximum execution priority that the program can have at
run time. The max_pri_level has to be one of BS, CS, DS,
ES, or a number between 100 and 255 inclusive.
- SHARE
Specifies that data symbols should be exportable and importable
(shared) in the resulting executable library.
Operation Notes
The Link Editor uses $STDINX, $STDIN, and $STDLIST
as standard files. The Link Editor reads its commands from $STDINX.
For interactive sessions this is the terminal keyboard. For a batch job, it is
the job stream file.
You can redirect $STDINX to another file. The file must be an
unnumbered ASCII file containing valid HP Link Editor/iX commands. Enter a
RUN command with the STDIN option. For example, to use the
file SCRIPT as the standard input file, enter the command:
RUN LINKEDIT.PUB.SYS;STDIN=SCRIPT
If you start the Link Editor using the LINK command, or if you execute
it by passing a command in the INFO string of the RUN
command, $STDINX is not used. Instead, the single command is executed
and the Link Editor terminates.
The Link Editor writes all prompts, error messages, and other information to
$STDLIST. During an interactive session, this is your terminal. For
a batch job, the output spoolfile is used.
You can use another device for $STDLIST. Use the RUN command
with the STDLIST option. Note that when you do this interactively, the
command prompts do not appear on the screen. For example, to send the Link
Editor output to the printer:
FILE LINKOUT;DEV=LP
RUN LINKEDIT.PUB.SYS;STDLIST=*LINKOUT
Link Editor listings and maps are sent to the file LINKLIST, not to
$STDLIST. The listings and maps sent to LINKLIST are:
The symbol map produced by the MAP option of the
LINK command.
The listing produced by the LISTPROG command.
The listing produced by the LISTOBJ command.
The listing produced by the LISTRL command.
The listing produced by the MAP option of the
ADDXL command.
The listings produced by the LISTXL command.
LINKLIST output goes to $STDLIST. But you can redirect it to
another file or device by using the FILE command. To send the listing
of the relocatable library LIBRL to the printer:
FILE LINKLIST;DEV=LP
LINKEDIT
LinkEd> LISTRL RL=LIBRL
LinkEd> EXIT
Use
This command may be issued from a session, job, or program, but not in BREAK.
Pressing Break suspends the execution of this command. Entering the
RESUME command continues the execution.
Examples
This command merges the object modules from the OBJCODE and places
them into the program EXECPROG. It assigns a program stack of 50,000
bytes and requests LINK to build a map and display the name of each
object module as it is being linked.
LINK FROM=OBJCODE;TO=EXECPROG;NMSTACK=50000;MAP;SHOW
The following command merges the object modules from the OBJCODE into
program file EXECPROG and searches the relocatable libraries
LINEDRAW and ARCDRAW to resolve external references. The
resulting program file can be executed only in batch mode by anyone with user
mode access.
LINK FROM=OBJCODE;TO=EXECPROG;RL=LINEDRAW,ARCDRAW;CAP=BA
To link module A and module MAIN and share data so that the data symbols in the
program file myprog can be exported and imported to and from the
executable library MYXL, enter:
LINK FROM=A,MAIN; TO=MYPROG; SHARE; RL=LIBCSHR.LIB.SYS; XL=MYXL
Related Information
- Commands
RUN, XEQ, LINKEDIT Utility
- Manuals
HP Link Editor/XL Reference Manual
HP Link Editor/iX Technical Addendum
Displays information about one or more accounts.
Syntax
LISTACCT [acctset] [,listfile] [;PASS]
[;FORMAT={SUMMARY | BRIEF | DETAIL}]
Parameters
- acctset
The accounts to be listed. The default is all accounts for system
managers (SM). For all other users, the default is their logon account.
Use the # symbol to specify a single numeric character. Use the
? symbol to specify a single alphanumeric character. Use the
@ symbol to specify zero or more alphanumeric characters. By
itself, @ represents all the members of a set. Each of these
wildcard characters counts toward the eight character limit for group,
account, and file names.
- listfile
The name of the output file. The default is $STDLIST, a
temporary file that cannot be overwritten by a BUILD command. It
is automatically specified as a new ASCII file with variable-length
records, closed in the temporary domain, and with user-supplied
carriage-control characters (CCTL), OUT access mode, and EXC
(EXCLUSIVE access) option. All other characteristics are the same as they
would be with the FILE command default specifications.
- PASS
Permits account managers and system managers to see the
password.
- FORMAT
Specifies one of several display formats, listed below.
- SUMMARY
Provides a summary of the account information. If FORMAT
is not specified, SUMMARY is the default.
- BRIEF
Generates a list of account names only.
- DETAIL
Displays all information associated with the account.
Operation Notes
This command produces account information in an ASCII format.
Use
This command is available from a session, a job, a program, or in BREAK.
Pressing Break aborts the execution of this command. System managers
(SM) can list any account on the system; account managers (AM) and general
users can list only their own account.
Examples
The presence of the password in the following display implies
that the user has account manager (AM) capability and this is the
user's account, or that the user has system manager (SM) capability
and this is not the user's account.
LISTACCT HPXLII;PASS
...or...
LISTACCT HPXLII;PASS;FORMAT=SUMMARY
********************
ACCOUNT: HPXLII
DISC SPACE: 754115(SECTORS) PASSWORD: ACCTPASS
CPU TIME : 3330(SECONDS) LOC ATTR: $00000000
CONNECT TIME: 102(MINUTES) SECURITY READ : ANY
DISC LIMIT: UNLIMITED WRITE : AC
CPU LIMIT : UNLIMITED APPEND : AC
CONNECT LIMIT: UNLIMITED LOCK : ANY
MAX PRI : 150 EXECUTE : ANY
GRP UFID : $00D0001 $80001050 $00138A20 $00000008 $000001FA
USER UFID: $00D4001 $80001050 $00138C20 $00000008 $000001FB
CAP: AM,AL,GL,DI,CV,UV,LG,CS,ND,SF,IA,BA,PH,DS,MR,PM
LISTACCT @;FORMAT=BRIEF
ACCOUNT1
ACCOUNT2
BACCT1
POSIX
SYS
LISTACCT POSIX;FORMAT=DETAIL
********************
ACCOUNT : POSIX
PASSWORD : **
GID : 50
DISC SPACE : 1163440(SECTORS)
CPU TIME : 199798(SECONDS)
CONNECT TIME : 1116561(MINUTES)
DISC LIMIT : UNLIMITED
CPU LIMIT : UNLIMITED
CONNECT LIMIT : UNLIMITED
MAX PRI : 150
LOC ATTR : $00000000
SECURITY : R:ANY, W:ANY, A:ANY, L:ANY, X:ANY
GRP UFID : $055A0003 $48C0B6B8 $000066B4 $918008B5 $0077B2D9
USER UFID : $055A0004 $48C0B6B8 $000066B4 $918008B5 $0077B2DF
CAP : SM,AM,AL,GL,DI,OP,CV,UV,LG,PS,NA,NM,CS,ND,SF,BA,
IA,PM,MR,DS,PH
Related Information
- Commands
LISTFILE, LISTGROUP, LISTUSER,
NEWACCT, PURGEACCT, ALTACCT
- Manuals
Performing System Management Tasks
The LISTDIR UDC executes the LISTFILE command to list all
files that are directories.
System-defined UDCs are not automatically available. Your System Manager must
use the SETCATALOG command to make these UDCs available for your use.
For example,
SETCATALOG HPPXUDC.PUB.SYS;SYSTEM;APPEND
Syntax
LISTDIR [[DIR=]dir_name] [[FORMAT=]format_opt]
Parameters
Refer to the LISTFILE command for a complete explanation of the
parameters used with the LISTDIR UDC. The following parameters are
supported with the LISTDIR UDC.
- dir_name
The name of the directory to list. The dir_name can be
in MPE or HFS syntax; wildcards may be used. For example,
/SYS/PUB, /SYS/PUB/dir@, ./abc/mydir, and
@abc are valid examples of directory names. If
dir_name is not specified, the default directory name is
./@ (all directories directly under your current working
directory).
- format_opt
An output format option. The option may be specified as a number or
mnemonic. For example,
FORMAT=2
or
FORMAT=DISC
If not specified, the default is FORMAT=6 (qualify).
Refer to the LISTFILE command for a complete description of each
available format option.
Operation Notes
The LISTDIR UDC lists all files that are directories. The UDC executes
the following form of the LISTFILE command:
LISTFILE dir_name ;FORMAT=format_opt ;SELEQ=[OBJECT=DIR] ;TREE
Use
This UDC may be issued from a session, a job, a program, or in BREAK. Pressing
Break aborts execution.
Examples
Refer to the LISTFILE command later in this chapter for examples.
Related Information
- Commands
LISTFILE, FINDDIR (UDC)
- Manuals
None
Displays all active file equations for a job or session.
Syntax
LISTEQ [listfile]
Parameters
- listfile
The name of the output file. The default is $STDLIST, a
temporary file that cannot be overwritten by a BUILD command. It
is automatically specified as a new ASCII file with variable-length
records, closed in the temporary domain, and with user-supplied
carriage-control characters (CCTL), OUT access mode,
and EXC (EXCLUSIVE access) option. All other characteristics are
the same as they would be with the FILE command default
specifications.
Operation Notes
The LISTEQ command displays all the active file equations
for a job or session.
Use
This command may be issued from a session, a job, a program, or in BREAK.
Pressing Break aborts the execution of this command.
Example
An example of LISTEQ is given below:
LISTEQ
FILE EQUATIONS
FILE TAPE1;DEV=ATAPE
FILE PP;ENV=LP2.ENV.OSE;DEV=EPOC
FILE MYFILE,NEW;REC=-80,3,F,ASCII;DISC=5000;SAVE
FILE POSIX=./mydir/myfile1
Related Information
- Commands
FILE, RESET
- Manuals
None
Displays information about one or more permanent files. (CM)
Syntax
LISTF [fileset] [,listlevel] [;listfile]
Parameters
- fileset
Specifies the set of files to be listed. The default is @,
which lists all files in your logon group. You may select the file(s) to
be listed by using the fully or partly qualified form for fileset:
filename.groupname.accountname
You may use the @ to specify zero or more alphanumeric
characters or, if used by itself, to denote all the members of a set. You
may use the symbol # to specify one numeric character and the
symbol ? to specify one alphanumeric character. The #
and ? wildcard characters count toward the eight character limit
for group, account, and file names.
- listlevel
Specifies the amount and format of information to display for the
file(s) you select. The default is 0, which displays only the file name.
The listlevel of the LISTF command is equivalent
to the format option of the LISTFILE command. The levels are
described below in Table 7-5 "Format
Options":
Table 7-5 Format Options
Listlevel |
Displayed Information |
-2 | Displays the file's ACD (access control definition).
System Managers can view the ACD for any file. Account Managers
can view the ACD for files in that account. File creators can view
the ACD for their files. Other users can view an ACD only if that
ACD specifies that the user has RACD (read ACD) access. |
-1 | Shows only the file label in hexadecimal. The
hexadecimal display generated by this format option only serves
a diagnostic purpose in MPE/iX and is subject to change. |
0 | For each directory, this option displays PATH=The
name of the file is displayed in a multicolumn format.
This is the default. |
1 | Displays the file name, file code, record size,
record format, and other file characteristics such as ASCII or binary
records, carriage-control option, file type, current end-of-file
location, and the maximum number of records allowed in the file. |
2 | Displays the file name, file code, record size,
file type, current end-of-file location, and the maximum number
of records allowed in the file. It also displays the blocking factor,
number of sectors in use, number of extents currently allocated, and
the maximum number of extents allowed. |
3 -3 | Displays the file name, record size,
extent size, number of records, user's access rights, and other
file characteristics including the date created, modified, and last
accessed. The same information for MPE and HFS files is displayed
except for the following differences:
Fully qualified MPE file name is replaced by an absolute
pathname.
Creator field displays the fully qualified user ID of the file
owner.
For MPE groups, the SECURITY field displays SAVE; for
entries other than MPE groups it is blank. All file access matrix
fields are blank for anything other than MPE accounts, MPE groups,
and files in an MPE group.
The LOCKWORD field is omitted.
The creator, group id, and label address are omitted in FORMAT=3.
These can be obtained by specifying -3 if you have sufficient capability
(AM or SM) |
4 | Displays the security matrix for the file. This includes
account, group and file-level security, and the access rights for the user.
For MPE groups and MPE accounts, the security matrix for group, account,
and account-only are displayed. The rest of the fields of the file access
matrix are blank.
For HFS directories, and files within HFS directories, all the fields of
the file access matrix are blank. In addition, LISTFILE displays
the message ACD EXISTS. |
5 -5 | Shows LISTFILE,3 data and all file-specific data
in LISTFILE,3 type format (KSAM, SPOOL, and symbolic links).
If a file has no unique data, only the option 3 data is shown. |
6 | Shows the absolute pathname of the file. |
7 | Shows all file specific data in LISTFILE,5 type
format, but does not show LISTFILE,3 data. If a file has no unique
data, only the file name is displayed. |
8 | Shows all accessors of the files listed. Restrictions
apply |
9 | Shows level 8 information and details about processes
accessing the files including file locking data. Restrictions
apply. |
10 | Shows level 1 information but in a wider format
that allows for expression o larger file sizes. Infromation is also
given on how each file is currenly being accessed; Exclusive, Read,
Write or Store |
11 | Shows level 2 information but in a wider format
that allows for expression of larger file sizes. Disk space occupied
by each file is presented in kilobytes (KB) rather than 256 byte
sectors. |
- listfile
The name of the output file to which the file information will be
written. If you omit this parameter, the output appears on $STDLIST. If
you specify listfile, the output is sent to a temporary
file created for this purpose. The temporary file is a new ASCII file
with variable length records, closed in the temporary domain, and with
user supplied carriage control characters (CCTL), OUT access
mode, and EXC (exclusive access) option. All other
characteristics are identical to the FILE command default
specifications. You may specify a different kind of file or backreference
an existing file.
When you direct LISTF output to $STDLIST from a job, or when you
direct the output to any non-disk device, a date and time stamp preceeds
the data, and listlevel 0 data appears as one file per
record rather than in the standard multi-column format.
Operation
The LISTF command displays a description of the file(s) you specified
in fileset. It only accepts MPE file name syntax, but it
displays information in one of two formats, MPE or POSIX, depending upon
whether or not your current group differs from your logon group. MPE format
examples appear below. For examples of the POSIX format, see the
LISTFILE command.
You may list any file, but there are restrictions on the kinds of information
available to various users. A standard user may specify a
listlevel of 0, 1, 2, 3, 4, 5, 6, 7, 10 or 11. If you have
account manager capability (AM), you may request listlevel -1,
-3 or -5, 8, 9 information about files in your own account. If you have System
Manager capability (SM), you can specify any listlevel to view
all information for all files on the system. List levels 8 and 9 are also
available if you are the owner of the files.
For list levels 8 and 9 the IP address of remote accessors and the program name
of the accessor process are restricted fields. PM, SM, OP, NA, or NM
capabilities are needed to see the IP address. The rules defined by the
SHOWPROC command are enforced before revealing the process
name.
The LISTF command does not display #SEG, STACK,
MAXDATA, TOTAL, DB, DL or CAP
values for program files. That information is displayed by the VERSION
utility. For more information, see the VERSION command.
You may have the information displayed on a device other than the standard
listing device. To do that, you will need to name the device with a
FILE command and then backreference the file in the LISTF
command. For example:
:FILE PRTR;DEV=LP
:LISTF @.@,2;*PRTR
Use
The LISTF command is available from a session, job, or a program, or
in BREAK. Pressing Break aborts the execution of this command.
Examples
Level 0 File Display
:LISTF
FILENAME
CLKLIST CLOCK EDIRC LINKCLK LINKFROG LINKLIST
Level 1 File Display
:LISTF L@,1
ACCOUNT= HPXLII GROUP= DEVELOP
FILENAME CODE ------------LOGICAL RECORD-------
SIZE TYP EOF LIMIT
L2 80B FA 2 12
LINKCLK 72B FA 1 11
LINKFROG 72B FA 1 11
LINKLIST 72B FA 8 18
Level 2 File Display
:LISTF L@,2
ACCOUNT= HPXLII GROUP= DEVELOP
FILENAME CODE ------------LOGICAL RECORD----------- ----SPACE----
SIZE TYP EOF LIMIT R/B SECTORS #X MX
LINKCLK 72B FA 1 11 3 8 1 1
LINKFROG 72B FA 1 11 3 8 1 1
LINKLIST 72B FA 8 18 3 8 1 1
Level 3 File Display
:LISTF DOCMNTS,3
********************
FILE DOCMNTS.DEVELOP.HPXLII
FILE CODE : 0 FOPTIONS STD,ASCII,FIXED,NOCCTL
BLK FACTOR: 16 CREATOR **
REC SIZE: 80(BYTES) LOCKWORD **
BLK SIZE: 640(BYTES) SECURITYREAD : ANY
EXT SIZE: 25(SECT) WRITE : ANY
NUM REC: 501 APPEND : ANY
NUM SEC: 165 LOCK : ANY
NUM EXT: 7 EXECUTE: ANY
MAX REC: 501 **SECURITY IS ON
MAX EXT: 7 FLAGS n/a
NUM LABELS: 0 CREATED FRI, 21 SEP 1986, 11:55 AM
MAX LABELS: 0 MODIFIED FRI, 21 SEP 1986, 12:34 PM
DISC DEV #: 3 ACCESSED FRI, 21 SEP 1986, 12:46 PM
SEC OFFSET: 0 LABEL ADDR **
VOLSET : MPEXL_SYSTEM_VOLUME_SET
or
VOLNAME : MPEXL_SYSTEM_VOLUME_SET: MEMBER1
or
VOLCLASS : MPEXL_SYSTEM_VOLUME_SET: DISC
or
CLASS : DISC LABEL ADDR: $00000010 $0010E014
Level 6 File Display
:LISTF L@,6
LINKCLK.DEVELOP.HPXLII
LINKFROG.DEVELOP.HPXLII
LINKLIST.DEVELOP.HPXLII
Level 7 File Display
********************
FILE: LINKCLK.DEVELOP.HPXLII
********************
FILE: LINKFROG.DEVELOP.HPXLII
********************
FILE: LINKLIST.DEVELOP.HPXLII
Level 8 File Display
:listfile hppxudc.pub.sys,8
********************
FILE: HPPXUDC.PUB.SYS
15 Accessors(O:15,P:15,L:0,W:0,R:15),Share
#S265 MIKEP.HPE P:2,L:0,W:0,R:2 LDEV: 49
#S263 JEFFV,MGR.JVNM P:3,L:0,W:0,R:3 LDEV: 47
#S261 KROGERS.MPENT P:2,L:0,W:0,R:2 LDEV: 50
#S231 SUSANC.MPENT P:2,L:0,W:0,R:2 LDEV: 46
#S219 FAIRCHLD.MPENT P:2,L:0,W:0,R:2 LDEV: 39
#S214 CATHY,MGR.BOSS P:2,L:0,W:0,R:2 REM : 15.14.16.198
#J434 FTPMON,FTP.SYS P:2,L:0,W:0,R:2 SPID: #O21905
Level 9 File Display
:listfile hppxudc.pub.sys,9
********************
FILE: HPPXUDC.PUB.SYS
5 Accessors(O:5,P:5,L:5,W:0,R:5),Share
#S263 JEFFV,MGR.JVNM P:3,L:3,W:0,R:3 LDEV: 47
#P147 (LFCI.PUB.SYS)
ACCESS: R-excl REC#: 0 FNUM: 13
LOCKS: Owner Waiter
FLOCK
OPEN
#P154 (CI.PUB.SYS)
ACCESS: R-excl REC#: 0 FNUM: 13
LOCKS: none
#P86 (JSMAIN.PUB.SYS)
ACCESS: R-excl REC#: 336 FNUM: 16
LOCKS: Owner Waiter
FLOCK
#J434 FTPMON,FTP.SYS P:2,L:2,W:0,R:2 SPID: #O21905
#P79 (CI.PUB.SYS)
ACCESS: R-excl REC#: 0 FNUM: 14
LOCKS: none
#P47 (JSMAIN.PUB.SYS)
ACCESS: R-excl REC#: 336 FNUM: 15
LOCKS: Owner Waiter
OPEN FLOCK
Level 10 File Display
:LISTF@.TEST,10
ACCOUNT= SYS GROUP= TEST
Name Access Fcode Recsize Type EOF File Limit
ERWS
SYSXTNTS 44 FB 11687 48806446
TEST2 500 FA 1592197 10000000
TESTFILE 500 FA 0 10000000
Level 11 File Display
:LISTF@.TEST,11
ACCOUNT= SYS GROUP= TEST
Name Access Fcode Recsize Type EOF File Limit Diskusage Exts
ERWS
SYSXTNTS 44 FB 11687 48806446 1024 5
TEST2 500 FA 1592197 10000000 777728 1382
TESTFILE 500 FA 0 10000000 1272320 2458
Level -2 File Display
:LISTF DOCMNTS,-2
FILENAME ACD ENTRIES
DOCMNTS NO ACDS
Level -3 File Display
:LISTF DOCMNTS,-3
********************
FILE DOCMNTS.DEVELOP.HPXLII
FCODE : 0 FOPTIONS: STD,ASCII,FIXED,NOCCTL
BLK FACTOR: 16 CREATOR : PETE
REC SIZE : 80(BYTES) LOCKWORD: RETEP
BLK SIZE : 640(BYTES) SECURITY--READ : ANY
EXT SIZE : 25(SECT) WRITE : ANY
NUM REC: 501 APPEND : ANY
NUM SEC: 165 LOCK : ANY
NUM EXT: 7 EXECUTE: ANY
MAX REC: 501 **SECURITY IS ON
MAX EXT: 7 FLAGS : n/a
NUM LABELS: 0 CREATED : FRI, 21 SEP 1986, 1155 AM
MAX LABELS: 0 MODIFIED: FRI, 21 SEP 1986, 1234 PM
DISC DEV #: 3 ACCESSED: FRI, 21 SEP 1986, 12:46 PM
SEC OFFSET: 0
CLASS : DISC LABEL ADDR: $00000010 $0010E014
Level 4 File Display
:LISTF DOCMNTS,4
********************
FILE DOCMNTS.DEVELOP.HPXLII
ACCOUNT ------ READ : ANY
WRITE : AC
APPEND : AC
LOCK : ANY
EXECUTE : ANY
GRUOP -------- READ : GU
WRITE : GU
APPEND : GU
LOCK : GU
EXECUTE : GU
SAVE : GU
FILE --------- READ : ANY FCODE: 0
WRITE : ANY **SECURITY IS ON
APPEND : ANY NO ACDS
LOCK : ANY
EXECUTE : ANY
FOR PETE.HPXLII: READ, WRITE, EXECUTE, APPEND, LOCK
Level -1 File Display
:LISTF LINKCLK,-1
F = LINKCLK
00000000 44495343 20202020 20202020 20202020 20202020 ....DISC
20202020 20202020 20202020 20310000 4C494E4B 434C4B20 1.
20202020 20202020 44455645 4C4F5020 20202020 20202020 DEVELOP
00000000 50455445 20202020 20202020 20202020 00000000 ....PETE
20202020 20202020 20202020 20202020 4D475220 20202020
4850584C 49492020 00000000 FC000000 04660001 10537F19 HPXLII .......
00010401 00000000 00000300 00056EE7 2F538AED 00056EE7 ..............n
2F538AED 00056EE7 2F53D1CC 00056EE7 2F538AED 00000000 /S....n./S....n
00000000 000003FF 00000000 00000000 00000000 00000000 ...............
0003FF00 00000000 00000000 00000000 00000100 00000100 ...............
00010000 00000000 00000000 00000000 ...............
Additional Information
- Commands
LISTFILE, VERSION, CHDIR, LISTDIR (UDC),
FINDFILE (UDC)
- Manuals
Performing System Management Tasks
Performing System Operation Tasks
|