![]() |
MPE/iX Commands Reference Manual
> Chapter 7 Command List VCommands HEADOFF thru LISTF |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
HEADOFFStops header/trailer output to a device. (Native Mode) SyntaxHEADOFF ldev Parameters
Operation NotesHeader 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.UseThis 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.ExampleTo stop header/trailer output to logical device number 6, enter:HEADOFF 6 Related Information
HEADONResumes header/trailer output to a device. (Native Mode) SyntaxHEADON ldev Parameters
Operation NotesHeader 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.UseThis 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.ExampleTo resume header/trailer output to logical device number 6 enter:HEADON 6 Related Information
HELLOInitiates 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
Operation NotesThe 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 PMThe 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:
UseThis 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 NameThe 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,MYGROUPIf 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). PasswordsTo 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/XPASSNote 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 TypesMPE/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 ExampleWhen 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
HELPAccesses the help subsystem (Native Mode) SyntaxDirect 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
Operation NotesYou 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.
UseThis command may be issued from a session, job, program, or in BREAK. Pressing Break aborts the execution of this command.ExamplesTo see the parameters for the LISTFILE command, enter::HELP LISTFILE PARMSTo see examples of the STORE command, enter: :HELP STORE EXAMPLESTo see the same information from within the Help subsystem, enter: :HELP >STORE EXAMPLESTo 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.SYSIf 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
IFUsed to control the execution sequence of a job, UDC, or command file. (Native Mode) SyntaxIF expression [THEN] Parameters
Operation NotesThis 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.
UseThis command may be issued from a job, session, program, or in BREAK. Pressing Break has no effect unless expression contains the INPUT evaluator function.ExampleThe 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
INPUTPermits 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]
Parameters
Operation NotesThis 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.
UseThis command is available in a session, job, program, or in BREAK. Pressing Break aborts the execution of this command, without creating or modifying varname.ExamplesThe 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 !bleepThe 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 <FILEONEThe 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,> >ABC Return SETVAR BLEEP !BLEEPABC 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
JOBDefines 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
Operation NotesThe 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:
UseThis 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.ExampleThe 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
JOBFENCEDefines the minimum input priority that a job or session must have in order to execute. (Native Mode) SyntaxJOBFENCE priorityfence Parameters
Operation NotesMPE/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.UseThis 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.ExamplesTo 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 #10Then 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
JOBPRISets or changes the default execution priority for batch jobs and sets a maximum execution priority for batch jobs. (Native Mode) SyntaxJOBPRI [maxsubqueue] [,defaultsubqueue] Parameters
Operation NotesThe 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.UseThis 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.ExampleTo raise the maximum execution priority so that batch jobs can run in any subqueue requested, enter:JOBPRI 0 Related Information
JOBSECURITYDesignates 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
Operation NotesThe 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.UseYou 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.ExampleTo allow any user to abort, alter, break, or resume their own jobs, enter:JOBSECURITY LOWTo 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=XACCESSThen 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
LDISMOUNTCancels 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
Operation NotesThe 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
UseThis 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.ExamplesTo release a volume set named DATABASE.PAYROLL.ACCTNG, enter:LDISMOUNT DATABASE.PAYROLL.ACCTNGYou may also use the VSRELEASESYS command: VSRELEASESYS DATABASE.PAYROLL.ACCTNG Related Information
LIMITLimits the number of concurrently running jobs/sessions. (Native Mode) Syntax
LIMIT [ [[ + | - ] numberjobs] [,[ + | - ] numbersessions] ]
[;JOBQ=queuename]
Parameters
Operation NotesMaximum 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 NOWThe 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. UseThis 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.ExamplesTo 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
LINKCreates 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
Parameters
Operation NotesThe 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=SCRIPTIf 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=*LINKOUTLink Editor listings and maps are sent to the file LINKLIST, not to $STDLIST. The listings and maps sent to LINKLIST are:
FILE LINKLIST;DEV=LP LINKEDIT LinkEd> LISTRL RL=LIBRL LinkEd> EXIT UseThis 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.ExamplesThis 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;SHOWThe 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=BATo 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
LISTACCTDisplays information about one or more accounts. Syntax
LISTACCT [acctset] [,listfile] [;PASS]
[;FORMAT={SUMMARY | BRIEF | DETAIL}]
Parameters
Operation NotesThis command produces account information in an ASCII format.UseThis 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.ExamplesThe 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
LISTDIR (UDC)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 SyntaxLISTDIR [[DIR=]dir_name] [[FORMAT=]format_opt] ParametersRefer 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.
Operation NotesThe 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 UseThis UDC may be issued from a session, a job, a program, or in BREAK. Pressing Break aborts execution.ExamplesRefer to the LISTFILE command later in this chapter for examples.Related Information
LISTEQDisplays all active file equations for a job or session. SyntaxLISTEQ [listfile] Parameters
Operation NotesThe LISTEQ command displays all the active file equations for a job or session.UseThis command may be issued from a session, a job, a program, or in BREAK. Pressing Break aborts the execution of this command.ExampleAn 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
LISTFDisplays information about one or more permanent files. (CM) SyntaxLISTF [fileset] [,listlevel] [;listfile] Parameters
OperationThe 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 UseThe LISTF command is available from a session, job, or a program, or in BREAK. Pressing Break aborts the execution of this command.ExamplesLevel 0 File Display:LISTF FILENAME CLKLIST CLOCK EDIRC LINKCLK LINKFROG LINKLISTLevel 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.HPXLIILevel 7 File Display ******************** FILE: LINKCLK.DEVELOP.HPXLII ******************** FILE: LINKFROG.DEVELOP.HPXLII ******************** FILE: LINKLIST.DEVELOP.HPXLIILevel 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: #O21905Level 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 ACDSLevel -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 $0010E014Level 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
|