HP 9X8LX Reference Guide

HP 3000 Series 9X8LX Computer Systems

Commands Reference

ABCDE

HP Part No. B3813-90011

Printed in USA 1994

First Edition

E0494

The information contained in this document is sub ject to c

hange

without notice.

Hewlett-Packard makes no warrantyofany kind with regard to this

material, including, but not limited to, the implied w

merchantability or tness for a particular purpose. Hewlett-P

arranties of

ackard

shall not be liable for errors contained herein or for direct, indirect,

special, incidental or consequential damages in connection with the

furnishing or use of this material.

Hewlett-Packard assumes no responsibility for the use or reliabilit

yof

its software on equipment that is not furnished by Hewlett-Packard.

This do cument contains proprietary information which is protected

by copyright. All rights are reserved. Reproduction, adaptation, or

translation without prior written p ermission is prohibited, except as

allowed under the copyrightlaws.



1994 by Hewlett-Packard Company

Use, duplication, or disclosure by the U.S. Government is sub ject

to restrictions as set forth in subparagraph (c) (1) (ii) of the

Rights in Technical Data and Computer Software clause at DFARS

252.227-7013. Rights for non-DoD U.S. Government Departments and

agencies are as set forth in FAR 52.227-19 (c) (1,2).

Hewlett-Packard Company

3000 Hanover Street

Palo Alto, CA 94304 U.S.A.

Restricted Rights Legend

Printing History

The following table lists the prin

respective release dates for eac

version of the software pro duct at the time this documen

product releases do not require c

expect a one-to-one correspondence bet

editions.

Edition Date Software

First Edition April 1994 B.50.00

tings of this documen

h edition. The softw

hanges to the documen

ween product releases and documen

t, together with the

are version indicates the

twas issued. Many

t. Therefore, do not

Version

iii

In This Book

This b ook pro

vides a detailed explanation of eac

h command in this subset of

MPE/iX commands.

Chapter 1: Introduction to Command Parameters

This chapter provides introductory information on command

syntax and organization.

Chapter 2: MPE/iX Commands

This chapter provides reference information for all of the

primary MPE/iX commands. The commands are arranged in

alphabetical order.

Related Manuals

The

Commands Reference

is the fourth book in a set of v

includes the following:

Understanding Your

System

(B3813-90001)

If you are new to computers, this is a goo d place to

start. It provides an introduction to what computers do

and how they do it.

Getting Started

(B3813-90003)

Familiarizes you with your computer and computer

peripherals. It also explains how to get your system

ready for use, how to use and maintain your tape drives

and how to communicate with your system using HP

Easytime/iX.

e manuals that

Task Reference

(B3813-90009)

Describes how to communicate with your system using

MPE/iX commands. This book also includes a chapter

on how to get more information on your system, a

chapter on troubleshooting and a glossary.

New Features of

MPE/iX: Using the

Hierarchical File

System

(32650-90351)

Describes the changes to MPE/iX as of Release 4.5

and 5.0, which enhanced MPE/iX to mak

e it \POSIX

compatible." The bo ok also describes the features of

the hierarchical le system.

Note

The MPE/iX operating system has been enhanced as of Release

4.5 and 5.0 to include additional features that include POSIX

compatibility and the

le system

is tree structured and can con

hierarchical le system

tain les at many

. The

hierarchical

dierent levels. This organization provides a special kind of le

called a

Introduction to Command Parameters

This chapter provides introductory information ab out parameters. T

o get help

on any parameter not found in this bo ok, use the MPE/iX online help facilit

described in the bo ok,

Each command in this bo ok is presen

Task Reference

(B3813-90009).

ted in alphabetical order and contains the

following information:

Command

Name

Syntax

Provides the command name at the top of eac

h page, followed

by a brief denition.

Provides a diagram that shows howtoenter the command and

its parameters.

Parameters

Explains each parameter including its function, limitations, and

defaults.

Operation

Notes

Explains how to use the command and may also include

advisory information, such as requirements, restrictions, and

operating processes.

Examples

Includes examples of how to use the command.

Provides the names of functionally related commands.

Commands

Introduction to Command Parameters 1-1

Parameters within Syntax

MPE/iX commands instruct the system to perform a desired function. If y

include parameters with the command before y

specically instruct the system ho

w it should perform the command function.

ou enter it, the parameters

There are three types of parameters:

required

optional

positional

Required parameters

You must enter all required parameters; otherwise, MPE/iX displays an error

message when you enter the command. In the syntax diagrams for each

command, either braces

In the following example,

{}

or no marks surround required parameters.

myle

is a required parameter b ecause no marks

surround it:

BUILD

Anything italicized, suchas

must be replaced with an actual name or v

myle

, is a representational name or value and

alue.

Sometimes you must select one parameter from two or more parameters. In the

following example, you must provide either a job number or a session number

because braces surround these parameters:



nnn

ALTJOB



Optional parameters

You can either specify or ignore optional parameters, if any, depending on how

you want the command to execute. In the syntax diagrams for each command,

brackets

[]

surround optional parameters. If you ignore optional parameters,

MPE/iX uses the system-dened default values for each parameter.

1-2 Introduction to Command Parameters

In the following example,

surround it:

NEWGROUP

groupname

[;PASS]

;PASS=

is an optional parameter b ecause brac

password

kets

In this example,

You would substitute an actual passw

value for the parameter

password

is optional within the optional parameter

PASS

is the parameter and

PASS

. The syntax diagram indicates that the v

password

ord in place of

is the parameter value.

password

to provide a

alue

PASS

Positional parameters

The eect of a p ositional parameter depends on its lo cation in the parameter

list. In the syntax diagram for each command, the comma (,) separates

positional parameters. If you omit a positional parameter from the list,

you must provide a comma placeholder that would normally precede that

parameter.

In the following example, the parameter values that follow the command are

positional:

LIMIT 10,32

In the following example, a comma holds the position of the curren

tvalue of

the rst parameter:

LIMIT ,32

Introduction to Command Parameters 1-3

MPE/iX Commands

The commands presented in this chapter are a subset of the MPE/iX system

commands and, in some instances, a subset of a command's parameters. Eac

command is presented in alphabetical order. T

not found in this chapter, use the MPE/iX online help facility described in the

Task Reference

(B3813-90009).

o get help on an

y parameter

To get help on a command not in this bo ok, t

next to the MPE/iX prompt. For example, to get help on

:HELP LISTFILE

ype help and the command name

LISTFILE

,type:

MPE/iX Commands 2-1

ABORTJOB/

The

ABORTJOB/

A ABORTJOB

Ctrl

A ABORTJOB

Ctrl

command terminates either a designated

job or session. Typically,you use this command to cancel a job that y

decided not to run but had already streamed. Y

to terminate one or more sessions, if necessary

ou can also use this command

, for system emergencies or

scheduled shutdowns.

Syntax

From a terminal:

;

ABORTJOB

nnn

jobname

user.acct

From the console:

;

A ABORTJOB

Ctrl

nnn

jobname

user.acct

Parameters

nnn

Species a job number.

nnn

jobname

Species a session number.

Species the name of the job, as iden

command.

user

acct

Species a user name.

Species an account name.

2-2 MPE/iX Commands

tied by the

SHOWJOB

Operation Notes

ABORTJOB/

A ABORTJOB

Ctrl

Note

You need to use the

or session number of the operation y

need more information on

command later in this c

SHOWJOB

hapter.

command to determine the job

ou want to cancel. If y

, refer to the section on that

Usage

You can enter this command from a session, a job, a program, or in break

mode. Pressing

You must enter the

enter the

JOBSECURITY

used the

ABORTJOB

command is set to

ALLOW

command, which permits you to enter this command.

Dierences b etween ABORTJOB and

does not aect this command.

Break

A ABORTJOB

Ctrl

command from the console. You can

command from a terminal other than the console if the

LOW

,orifyour system administrator has

A ABORTJOB

Ctrl

Both of these commands function identically except that you can enter

ABORTJOB

only from the console. The=sign app ears when you press

Ctrl54A

Pressing these keys enables you to enter certain commands on a console from

which another process (suchas

STORE

) is currently running.

Recommended usage

If you use the[jobname,]user.acct

form of the command when more than

one job or session is executing with the same name, the system selects the

job or session that it ab orts. Consequently,you should use the#Jnnn

nnn

form of the command for more precise control of jobs or sessions to be

terminated. Although the job or session abnormally terminates, log records

are issued, and CPU times and connect times are updated. All I/O activit

terminates, such as printing, and reading or writing les.

Ctrl

Waiting and scheduled jobs

You can also use the

ABORTJOB

command for waiting and scheduled jobs,

as well as for executing jobs. If a request is pending at the console, the

command automatically terminates the request, and the following message

appears on the console:

time

/#S

nnn/pin

/REQUEST REQUIRING OPERATOR REPLY FOR

MPE/iX Commands 2-3

ABORTJOB/

A ABORTJOB

Ctrl

PIN #nnHAS BEEN ABORTED

Refer to the Glossary for a denition of the process iden

tication number

(PIN).

Examples

To terminate session number 139, en

ter:

:ABORTJOB #S139

The system responds b

y displaying the following logo message on the

console if the session ends successfully:

17:10/#S139/34/LOGOFF ON LDEV #12

To terminate job number 9, enter:

:ABORTJOB #J9

The system responds by displaying the following logo message if the

executing job successfully terminates:

20:18/#J9/26/LOGOFF ON LDEV #10

This message does not appear when y

ou terminate waiting or scheduled jobs.

To terminate session 6, which has the following pending device allo cation

message, enter:

?17:00/#S6/23/LDEV# FOR "SCRTAPE" ON TAPE (NUM)?

:ABORTJOB #S6

The system responds by displaying the following message:

17:10/#S6/120/REQUEST REQUIRING OPERATOR REPLY FOR

PIN 23 HAS BEEN ABORTED

17:10/#S6/120/LOGOFF ON LDEV #58

2-4 MPE/iX Commands

Related Commands

ALLOW

BREAKJOB

CONSOLE

JOBSECURITY

SHOWJOB

STREAM

ABORTJOB/

A ABORTJOB

Ctrl

MPE/iX Commands 2-5

ALLOW

The

ALLOW

users to enter one or more operator commands. The

command enables the system administrator to permit one or more

ALLOW

which users can enter operator commands, and species whic

users can enter.

Syntax

Interactive and subsystem mode:

;COMMANDS=

command

command,...

ALLOW

@.@

@.acct

user.@

user.acct

Program mo de:

ALLOW FILE=

formaldesignator

;SHOW

Parameters

command sp ecies

h commands these

@.@

@.acct

user.@

user.acct

COMMANDS

Gives access to all users whether or not they are logged on.

Gives access to all users logged on to a specic accoun

Gives access to a specic user logged on to an

Gives access to a specic user logged on in a specic accoun

Species the names of the console commands that the user(s)

can access.

FILE

Species an ASCII le name,

of from one to eight alphanumeric characters, b eginning with

an alphab etic character. The

partially qualied and can b e backreferenced in a le equation.

SHOW

Lists input lines to

2-6 MPE/iX Commands

$STDLIST

formaldesignator

y account.

, that consists

can be fully or

Operation Notes

Usage

You can enter this command from a session, a job, a program, or in break

mode. Pressing

message, but does not aect commands already en

terminates subsystem mode and produces an error

Break

tered in subsystem mode.

ALLOW

This command can only b e en

administrator has used the

tered from the console, unless y

ALLOW

command, which permits you to enter this

our system

command.

You can only allow commands to users curren

@.@

parameter. Rememb er, however, that this parameter allows commands

to all users. An alternativewould b e to use the

@.@

parameter, then use the

DISALLOW

tly logged on unless y

ALLOW

command with the

ou use the

command to disallow commands to

selected users.

Additional commands that you allow for users are valid only for the duration

of their current session. When a user logs o and then bac

k on to the

system, the previously allowed commands are no longer available until they

are allowed again.

Command mo des

The

ALLOW

command enables you to enter the command in one of three

modes:

interactive

subsystem

program

When using interactive mo de, you enter the entire command along with

the desired parameters as shown in syntax and press

mode is similar, except you just enter the

ALLOW

command and then provide

Return

. Subsystem

the remaining parameters after the subsystem prompt (>) appears. The

subsystem accepts command parameters until you enter the

EXITorEND

command.

Program mo de is benecial from an administrative persp ective, because you

can create a customized le granting specic permissions that you do not

MPE/iX Commands 2-7

ALLOW

have to alter, unless desired. When using program mo de, y

ou rst create a

le that:

Identies the users and accounts that are permitted to use op erator

commands.

Lists the allowed commands.

Then you enter the

ALLOW

command, using the

SHOW

parameter to display

each command line as it executes from the le.

Refer to \Examples" for examples of all three mo des.

Console commands versus operator commands

Console commands function dierently from operator commands. Console

commands are not allo wable, must be entered on the actual console (usually

congured as LDEV 20), and must be preceded by

Ctrl54A

commands have the same name as non-console commands, suchas

. Some console

RECALL

which can b e entered on any device.

Operator commands are generally used in the daily operation of y

our system

and are generally allowable.

Allowable commands

You can allo w up to 19 of the follo

wing commands at a time in interactive

and subsystem modes. If you need to sp ecify more than 19 commands, use

program mo de.

ABORTIO HEADON RESUMESPOOL

ABORTJOB JOBFENCE SHUTQ

ACCEPT JOBSECURITY STARTSPOOL

ALLOW LDSMOUNT STOPSPOOL

ALTJOB LIMIT STREAMS

ALTSPOOLFILE LOG UP

CONSOLE MRJECONTROL VMOUNT

DELETESPOOLFILE OPENQ VSCLOSE

DISALLOW OUTFENCE VPOPEN

DISCRPS REFUSE VSRELEASESYS

DOWN REPLY VSRESERVESYS

DOWNLOAD RESUMEJOB WARN

HEADOFF SPOOLER WELCOME

2-8 MPE/iX Commands

ALLOW

Not all of these commands are described in this c

about commands not described in this c

hapter, use the Help F

Before allowing any users access to these commands, y

SHOWALLOW

command to determine which operator commands ha

been allowed.

Examples

In interactive mo de, to allow a user named

and

ABORTJOB

commands, enter the following command at the console:

USER.TECH

:ALLOW USER.TECH;COMMANDS=REPLY,ABORTJOB

In subsystem mode, to allow a user named

BREAKJOB

command, enter the following command sequence at the console:

MGR.MANUALS

:ALLOW

>MGR.MANUALS;COMMANDS=BREAKJOB

>EXIT

In program mo de, to allow the users named

JOHN.ACCTNG

to enter the

LIMIT

command, do the following:

SUSAN.PAYROLL

hapter. For information

acility.

ou should enter the

ve already

to enter the

and

1. Execute the

ALLOWTMP

, as shown:

:EDITOR

HP32201A.07.17 EDIT/3000 WED, MAY 8, 1991, 3:02 PM

/ADD

...

/K ALLOWTMP

EDITOR

command, create a program le, and saveit to

1 SUSAN.PAYROLL;COMMANDS=LIMIT

2 JOHN.ACCTNG;COMMANDS=LIMIT

3 //

MPE/iX Commands 2-9

ALLOW

2. Execute the

display each command line as it executes from the le:

:ALLOW FILE=ALLOWTMP;SHOW

You can also include a lo c

:ALLOW FILE=ALLOWTMP/LOCKWORD;SHOW

You can backreference the le with a le equation, as sho

:FILE BACKF=ALLOWTMP

:ALLOW FILE=*BACKF;SHOW

Related Commands

CONSOLE

DISALLOW

SHOWALLOW

ALLOW

command using the

kword for the le, if an

SHOW

parameter, if desired, to

y, as shown:

wn:

2-10 MPE/iX Commands

ALTACCT

The

ALTACCT

command enables a system administrator to c

parameters of an existing accoun

Syntax

ALTACCT

hange the

ALTACCT

;PASS=

;ACCESS=

Parameters

acctname

PASS

CAP

acctname

password

(

leaccess

332

;CAP=

)

capabilitylist

Species the name of the account that you want to alter. The

name must consist of one to eight alphanumeric characters,

beginning with an alphab etic character.

Species the account password, only used for verifying logon

access. Entering the

retains the current password. Entering

password

specifying

removes the existing password. Entering

password

ALTACCT

command without this parameter

PASS

without specifying

PASS

changes the current password or creates

one if a password did not previously exist.

Species the list of capabilities permitted for this accoun

were assigned with the

NEWACCT

command. Each capabilityis

indicated byatwo-letter mnemonic, separated by commas, as

follows:

SM = System manager

AM = Account manager

DI = Diagnostician

OP = System supervisor

NA = Network administrator

NM = Node manager

SF = Save files

ND = Access to nonshareable I/O devices

UV = Use volumes

and

t that

MPE/iX Commands 2-11

ALTACCT

CV = Create volumes

CS = Use communication subsystem

PS = Programmatic sessions

LG = User logging

PH = Process handling

DS = Extra data segments

MR = Multiple RINs

PM = Privileged mode

IA = Interactive access

BA = Batch access

ACCESS

The defaults are AM, SF, ND, IA, and BA, for all accoun

except for the

SYS

account. The defaults for the

SYS

account

are SM, AM, AL, GL, DI, OP, SF, ND, PH, DS, MR, and PM.

You should not alter the

SYS

account because it is assigned the

maximum account capabilities when the system is delivered.

If you remove a capability from an account, it is unavailable to

users of that account only after they log o the system and

then log back on.

Species the restriction on le access p ertinent to this account.

Valid syntax options are as follo ws:

(

;

...

ANY

where R, L, A, W, X, and S sp ecify mo des of access b

;

...

)

ytypes

of users (ANY, AC, GU, AL, GL) and are dened as follows:

R = Read

L = Lock (exclusive file access)

A = Append (implies L)

W = Write (implies A and L)

X = Execute

S = Save

2-12 MPE/iX Commands

ALTACCT

The user types are dened as follo

ws:

ANY = Any user

AC = Member of this account only

GU = Member of this group only

AL = Account librarian user only

GL = Group librarian user only

You can specify t

wo or more user and/or access t

ypes if you

separate them with commas.

The defaults are R,A,L,W,X:AC for all accoun

SYS

. The

SYS

account defaults are (R,X:ANY;A,W,L:AC).

ts except for

Operation Notes

Usage

You can enter this command from a session, a job, a program, or in break

mode. Pressing

does not aect this command.

Break

You must have system manager (SM) capability in order to use this

command.

Altering account parameters

Basic guidelines for altering account parameters are as follows:

You can enter multiple parameters on a single command line b

y using the

semicolon (;) delimiter.

When you change one capability in a capability list that contains several

nondefault values, you must specify an entire new capability list.

A parameter remains unchanged for the accountifyou omit a parameter

and its value when entering the command.

When you include a parameter but omit its value as in

PASS=

Return

default value is assigned.

MPE/iX Commands 2-13

, the

ALTACCT

Activating the changes

If you alter one or more parameters while users are logged on, the c

do not become eectiv

euntil the users log o their curren

t jobs or sessions

hanges

and log back on. Since the system does not automatically generate a message

informing users of changes, you should notify users b efore y

accountchanges. This is particularly advisable when y

from an account. In this case, all accoun

account are denied the capabilit

t members and groups within the

ou makeany

ou remove a capability

Restrictions

You cannot remove system manager (SM) capability from the

SYS

account

or account manager (AM) capability from any account. From within any

account, you can remove AM capability from all but one (the last) of the

users assigned the capability; however, you can remove AM capability from

all users in an accountifyou do this from another user and accoun

t with SM

capability.

Examples

Tochange the password of an account named

AC2toGLOBALX

,enter:

:ALTACCT AC2;PASS=GLOBALX

To add SM capability to an account named

capabilities, enter:

:ALTACCT AC2;CAP=SM,AM,AL,GL,ND,SF,BA,IA

2-14 MPE/iX Commands

AC2

and retain the default

Related Commands

ALTGROUP

ALTUSER

LISTACCT

LISTGROUP

LISTUSER

NEWACCT

NEWGROUP

NEWUSER

REPORT

RESETACCT

ALTACCT

MPE/iX Commands 2-15

ALTFILE

This command changes the attributes of an existing le or directory

SYNTAX

ALTFILE

;GROUPID=

FILE=

lename

POSIXgroupname

;OWNER=

ownername

PARAMETERS

lename

The le name of the ob ject to be altered. The lename

may name a le, hierarchical directory, root, MPE group

or account. Note that MPE groups or accounts can ONLY

be named via HFS (Hierarchical File System) syn

Temporary les are not recognized.

This is a required parameter. You cannot use wildcarding

to sp ecify le names, nor can you use back-referenced le

equations. This parameter cannot name a system-dened

le (such as $NULL). You can specify le names using b oth

MPE and HFS syntaxes. MPE-syntax names may not

include lo ckwords; the lockword for a lockworded le is not

needed for this command to succeed, and if included in the

lename

results in an error.

tax.

ownername

The name of the user who will become the o

lename

the system. Default is for the UID of the le to remain

unchanged. Note that no qualication is done on this

name; it must b e fully specied. This name will be

upshifted if it is NOT quoted. [Optional]

POSIXgroupname

The name of the group (GID) that this le will belong to.

This

This parameter cannot be used to change the GID of an

MPE group or account. The default is for the le to retain

its previous GID. This name is upshifted when you enclose

it in quotes.

2-16 MPE/iX Commands

. This

ownername

POSIXgroupname

wner (UID)

must already exist on

must already exist on the system.

Operation Notes

Usage

ALTFILE

You use the

modify the owner (UID) and POSIX group (GID) for a le, hierarc

directory, MPE group or accoun

ALTFILE

command to alter a le's c

t. You cannot alter the GID of MPE groups

haracteristics. You can

hical

or accounts.

Required Capabilities

The user must have the appropriate privilege to c

attribute. Tochange the UID of a le, y

ou must b e one of the follo

hange the requested

wing:

The le's account manager whose logon account matches the GID of the

le and who has the MPE/iX account manager capability. In this case,

ownername

must specify a user b elonging to the accoun

t manager's logon

account.

A system manager who has the MPE/iX system manager user capabilit

In this case,

ownername

may specify any user existing in the user

database.

Tochange the GID of a le, you must b e one of the following:

The le owner (a user whose logon name matches the UID of the le). In

this case,

POSIXgroupname

must specify the user's logon account.

The le's account manager whose logon account matches the GID of the

le and who has the MPE/iX account manager (AM) user capability.In

this case,

POSIXgroupname

must specify the account manager's logon

account.

A system manager who has the MPE/iX system manager user capabilit

In this case,

POSIXgroupname

may specify any GID existing in the group

database.

You can use

ALTFILE

to mo dify multiple attributes at the same time. If you

try mo difying multiple attributes, all changes must succeed for any to take

eect. If you do not specify any attributes, the command has no eect on the

le specied.

MPE/iX Commands 2-17

ALTFILE

Related Commands

ALTSEC

2-18 MPE/iX Commands

+ 304 hidden pages

HP 9X8LX Reference Guide

Contents

Introduction to Command Parameters

Parameters within Syntax

MPE/iX Commands

ALLOW

ALTACCT

ALTFILE