MPE/iX Commands Reference Manual > Chapter 5 Command List III

Commands DATA thru EXIT

	MPE documents
	Complete PDF
	Table of Contents
	Index

DATA
DEALLOCATE
DEBUG
DELETESPOOLFILE
DELETEVAR
DISALLOW
DISASSOCIATE
DISCRPS
DISCUSE (UDC)
DISKUSE
DISMOUNT
DO
DOIONOW
DOWN
DOWNLOAD
DSTAT
ECHO
EDITOR
ELSE
ELSEIF
ENDIF
ENDWHILE
EOD
EOJ
ERRCLEAR
ERRDUMP
ESCAPE
EXIT

DATA

Enters data into the system from a device file. (Cannot be used to enter data from $STDIN.) (Native Mode)

Syntax


  DATA [jsname,] username [/userpass] .acctname [/acctpass]
    [;filename]

Parameters

jsname

Name of job or session that is to read data. Default is no job/session name. It may contain up to eight alphanumeric characters, beginning with a letter.

username

User name that allows you to access MPE/iX in this account, as established by the account manager. It may contain up to eight alphanumeric characters, beginning with a letter.

userpass

User password, optionally assigned by the account manager. It may contain up to eight alphanumeric characters, beginning with a letter. 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 DATA command is a first level data command (it is not nested within a second level STREAM command).

acctname

Account name under which job/session is running, as established by the system manager. It may contain up to eight alphanumeric characters, beginning with a letter.

acctpass

Account password, optionally assigned by system manager. It may contain up to eight alphanumeric characters, beginning with a letter. 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 DATA command is a first level data command (it is not nested within a second level STREAM command).

filename

Optional name for the data, used to distinguish between two separate data files that are to be read by the same program. It may contain up to eight alphanumeric characters, beginning with a letter. Default is that no distinguishing name is assigned.

Operation Notes

This command identifies data to be read from a device file other than your standard job/session input device. It can be used, for example, to input a data file from a spooled input device for later use by an interactive session or a batch job. The DATA command is the only command that can be entered before a job or session is initiated. Files identified by DATA may be input only from magnetic tape on spooled tape drives or with the STREAM command.

To designate a set of data as an auxiliary file for your job or session, enter the DATA command followed by the set of data and the EOD command. To access the data, begin your job or session using the same identity ([jsname,]username.acctname) used in the DATA command. If the filename parameter is omitted, several data files can be read from any job or session with the same identity.

When entered from magnetic tape, such data must reside in a file on a single tape volume, and the blocking factor must be 1. When the media containing the data file is placed on the tape drive and that device is placed online, MPE/iX reads the entire file. At that point, the job can access the data, which remains available until it is actually read. To submit data from a disk file, you must use the STREAM command.

The time-related parameters of the STREAM command may not be used when STREAM is used with the DATA command.

The STREAM command will prompt you for both user and account passwords if they exist and are not supplied in the DATA command if the following conditions are met:

The STREAM command is invoked from a session.
Neither $STDIN nor $STDLIST is redirected.
The DATA command is a first level data command (it is not nested within a second level STREAM command).

Use

This command may be issued from a session or job. Use the STREAM command to input a data file. This command cannot be used directly from $STDIN or from a program.

Examples

A data file is created on disk, and the STREAM command is used to make the file available to your program.

To create the file DATAFL on disk, invoke a text editor (like EDITOR) and enter the data beginning with the DATA command and ending with the EOD command. For example:


  EDITOR
  /ADD
  DATA SESSB,BROWN.ACCT1
  .
  .
  .
  EOD
  //
  /KEEP DATAFL,UNN
  /EXIT

To stream the data file using the STREAM command, enter:


  STREAM DATAFL

To log on to a session, using precisely the same identity that was used in the DATA command, enter:


  MPE XL: HELLO SESSB,BROWN.ACCT1

To enter a FILE command equating the formal file designator (used by the program) with the stream device (identified by the device class name JOBTAPE), enter:


  FILE DATAFL;DEV=JOBTAPE

To run the program that requires the data, enter:


  RUN PROGY

Once the data has been read, it is no longer available to the system. If another program requires this data, the data must be entered again with the STREAM command.

Related Information

Commands: EOD, STREAM
Manuals: None

DEALLOCATE

Deallocates a program or procedure previously loaded into memory with the ALLOCATE command.

Syntax


  DEALLOCATE [ PROGRAM | PROCEDURE ] ,name

Parameters

PROGRAM: The program file indicated by name is deallocated. Default.
PROCEDURE: The code segment containing the procedure specified by name in SL.PUB.SYS is deallocated.
name: The name of the program file or procedure to be deallocated.

Operation Notes

DEALLOCATE immediately releases table entries belonging to a program file or procedure that has been allocated. If the program is currently executing, the command takes effect once the program or procedure is no longer in use.

You may use a comma (,), a semicolon (;), and an equal sign (=) as delimiters.

NOTE: NM and CM loader error messages are reported differently, allowing you to determine the system in which the error occurred.

NM Loader Error: ErrMessage (LDERR nnnn)

CM Loader Error: ErrMessage (LOAD ERR nnnn)

Use

This command may be issued from a session, job, program, or in BREAK. Pressing Break has no effect on this command. Any program for which a user has EXECUTE access can be deallocated. A user with system supervisor (OP) capability can deallocate any program.

Example

To deallocate a program file named PROGEX, enter:


  DEALLOCATE PROGEX

DEALLOCATE does not give back memory; it gives back table entries.

Related Information

Commands: ALLOCATE
Manuals: Introduction to MPE XL for MPE V Programmers

DEBUG

Instructs MPE/iX to enter the system debugger. (Native Mode)

Syntax


  DEBUG [commands]

Parameters

commands: A series of system debugger commands to be executed before the debugger prompt is displayed. The string may be as many as 255 characters long. There are no delimiters or keywords needed to pass these commands to the debugger. If the CONTINUE command is not part of the commands string, you are left in debug after the execution of those commands.

Operation Notes

The DEBUG command enters the system debugger. An optional parameter, commands, defines a string of system debugger commands that are executed when the debugger is invoked, but before the debugger prompt is displayed.

If the string contains commands that return the user to the command interpreter, those commands are executed. Any remaining commands are pushed onto a command stack. Another invocation of the DEBUG command executes the commands saved on the stack. If you invoke DEBUG X;Y;Z and the command X returns control to the CI, then DEBUG A;B;C executes the commands A;B;C;Y;Z.

Use

This command may be issued from a session, program, or in BREAK. It may not be issued from a job. Pressing Break has no effect on this command. Privileged mode (PM) capability is required to use this command.

Example

To produce a stack trace and return to the command interpreter:


  DEBUG TRACE;C
  
  DEBUG XL A.00.00
  
  HPDEBUG Intrinsic at: a.006b4104 hxdebug+$130
     PC=a.006b4104 hxdebug+$130
  * 0) SP=40221c58 RP=a.006b8e7c exec_cmd+$73c
    1) SP=40221ac8 RP=a.006ba41c try_exec_cmd+$ac
    2) SP=40221a78 RP=a.006b8638 command_interpret+$274
    3) SP=40221620 RP=a.006bae5c xeqcommand+$1d0
    4) SP=40221210 RP=a.006b7604 ?xeqcommand+$8
      export stub: 7d.000068dc main_ci+$94
    5) SP=40221178 RP=7d.00007420 PROGRAM+$250
    6) SP=40221130 RP=7d.00000000
     (end of NM stack)
  :

Related Information

Commands: RESETDUMP, RUN, SETDUMP
Manuals: System Debug Reference Manual

DELETESPOOLFILE

Deletes a spoolfile from disk.

Syntax


  DELETESPOOLFILE { #Onnn #Innn ldev }

Parameters

#Onnn: The identification of a READY or ACTIVE output spoolfile.
#Innn: The identification of a READY, input spooled data file.
ldev: The logical device number on which the spoolfile is ACTIVE.

Operation Notes

Before deleting an ACTIVE spoolfile, first take the output device offline. This allows you time to enter the command and determine that the ACTIVE spoolfile corresponds to the correct output device. When MPE/iX returns the colon prompt (:), you know that the DELETESPOOLFILE command instruction has been sent to the spooler process. It is not executed, however, until the output device is put back online.

You may not use the DELETESPOOLFILE command on the following type of files:

System-defined standard input spoolfiles ($STDIN). Delete them with the ABORTJOB command.
ACTIVE spoolfiles with data input, entered with the STREAM command. You may delete these only when they are READY. You may not delete these files when they are OPEN.

The DELETESPOOLFILE command deletes ACTIVE data input files that are submitted on a spooled device. It cannot delete such files while they are being streamed.

Use

This command may be issued from a session, program, or in BREAK. It may not be issued from a job. Pressing Break has no effect on this command. This command may be used only from the console unless distributed to users with the ALLOW or ASSOCIATE command.

Example

To delete the ACTIVE spoolfile being printed on LDEV 6, first take the printer offline. This generates a NOT READY message at the console, after which you may enter the DELETESPOOLFILE command, as shown below:


  11:21/7/LDEV#6 NOT READY
  DELETESPOOLFILE 6

When you put the device back online, the trailer page is printed, and the file deleted. If you have suppressed header/trailer output with the HEADOFF command, no trailer is printed before the spoolfile is deleted. However, the printer skips to the top of the next physical page. If the device is a page printer, the default environment is reloaded.

Related Information

Commands: ALTSPOOLFILE
Manuals: Native Mode Spooler Reference Manual

DELETEVAR

Deletes one or more MPE/iX variables. (Native Mode)

Syntax


  DELETEVAR varname [,varname] ... [,varname]

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: The name of the variable to be deleted.

Operation Notes

Deletes a specific MPE/iX variable, or all variables specified by a pattern. If you specify more than one varname, you must separate them with commas.

You may use the wildcard characters, @, #, ?, and [ ] to specify a set or range of values.

@

Specifies zero or more alphanumeric characters, or the underbar character (_). Used by itself, it specifies all possible combinations of such characters. Used with other characters it indicates all the possible names that include the specified characters. @ABC@ specifies all names that include ABC anywhere in the name.

#

Specifies one numeric character. A###@ specifies all names that begin with A followed by any three digits, followed by any combination of 0 to 251 alphanumeric (or underbar) characters.

?

Specifies one alphanumeric character. A?# specifies all three-character names that begin with A, followed by an alphanumeric, followed by a digit.

[ ]

Specifies a set or range of characters. The set may appear anywhere in the name. This range specification is not case sensitive and, therefore, [A-K] is the same as [a-k]. If you specify a null set such as [k-a], MPE/iX reports an error.

@[abc]@# =: All names containing A, B, or C and ending in a single digit.
[a-k]@ =: All names that begin with any one of the letters A through K.
[n-a] =: Is not valid and is flagged as an error.

Use

This command is available in a session, job, program, or in BREAK. Pressing Break has no effect on this command.

Examples

To delete two specific variables, enter:


  DELETEVAR firstvariable, secondvariable

To delete all variables beginning with a single alphabetic character and ending with the characters axval, enter:


  DELETEVAR ?axval

To delete all variables created by the user, enter:


  DELETEVAR @

To delete a range of variables, for example, those that begin with the letters P, Q, R, S, or T followed by zero or more characters that end with the string module. In the following example variables such as PMODULE, QMODULE, RMODULE, SMODULE, TMODULE, and TIME_MODULE are all deleted by entering:


  DELETEVAR [P-T]@MODULE

MPE/iX predefined variables, which are listed in appendix A, cannot be deleted.

To delete all variables beginning in T and ending in two digits such as TMP11, T25, TMP_237 but not T2, enter:


  DELETEVAR T@##

Related Information

Commands: SETJCW, SETVAR, SHOWJCW, SHOWVAR
Manuals: Using the HP 3000 Series 900: Advanced Skills
Appendix A, "Predefined Variables in MPE/iX"

DISALLOW

Prohibits access to a specific operator command.

Syntax


  DISALLOW FILE=formaldesignator [;SHOW]
  DISALLOW {@.@ | user.@ | @.user | user.acct}
    ;COMMANDS=command [,command [,...] ]

Parameters

formal- designator: An ASCII file name, which may consist of one to eight alphanumeric characters, beginning with an alphabetic character. It may be fully or partially qualified and may be back-referenced in a file equation.
SHOW: Lists input lines on $STDLIST.
@.@: Prohibits access to all users whether logged on or not.
user.@: Prohibits access to a specific user in all accounts.
@.acct: Prohibits access to all users in a specific account.
user.acct: Prohibits access to a specific user in a specific account.
command: The names of those commands to which the user is prohibited access.

Operation Notes

The operator uses the DISALLOW command to prohibit a user from executing specific operator commands previously allowed with the ALLOW command. You can use the command in any of three ways:

Direct mode, in which you enter specific user names and account and the list of prohibited commands directly at the console.
Indirect mode, in which you use a text editor such as EDIT/3000 to create a file that contains the user name and account of those users who will be prohibited from executing certain operator commands, and a list of disallowed commands.
Subsystem mode, in which you enter the DISALLOW command, press Return, and, at the ">" prompt, enter the user and account names and the list of prohibited commands.

See the "Examples" section for more information.

You may enter as many prohibited commands as you want, in any of the three modes. However, in direct mode and subsystem mode, DISALLOW acts to prohibit the first nineteen commands and ignores any additional commands you may have specified. To disallow more than nineteen commands, create a file that contains the necessary information and specify it on the command line (i.e. "Indirect mode").

NOTE: Do NOT confuse operator commands with console commands. For a description of the difference between console and operator commands refer to the ALLOW command. The commands which may be disallowed are the same as the commands which may be allowed. Refer to the ALLOW command for a list of commands which may be allowed.

Use

This command may be issued from a session, job, program, or in BREAK. Pressing Break will terminate subsystem mode and produce an error message but has no effect on commands already entered in subsystem mode. This command may be used only from the console unless distributed to users with the ALLOW command.

Examples

To prohibit the user USER.TECH from executing the REPLY and ABORTIO commands, enter the following at the system console:


  DISALLOW USER.TECH;COMMANDS=REPLY,ABORTIO

To use subsystem mode to prohibit the user MGR.MANUALS from executing the BREAKJOB command, enter the following at the system console:


  DISALLOW
  >MGR.MANUALS;COMMANDS=BREAKJOB
  >EXIT
  :

To use indirect mode, you create a file with all of the necessary information, and then invoke the changes by specifying the file using the FILE= parameter of the DISALLOW command.


  EDITOR
  HP32201A.07.17 EDIT 3000 TUE, MAY 29, 1987, 5:08 PM
  (C) HEWLETT-PACKARD CO. 1985
  /ADD
    1  SUSAN.PAYROLL;COMMANDS=ALTJOB,ALTSPOOLFILE
    2  JOHN.ACCTNG;COMMANDS=ALTSPOOLFILE,DELETESPOOLFILE
    3  //
  ...
  /KEEP COMNDTMP
  /E
  
  DISALLOW FILE=COMNDTMP;SHOW

If you want MPE/iX to display each command line as it is executed from the file, inclue the SHOW parameter.

You may backreference the file with a file equation as follows:


  FILE BACKF=COMNDTMP
  DISALLOW FILE=*BACKF;SHOW

If the file has a lockword it may be inserted as follows:


  DISALLOW FILE=COMNDTMP/LOCKWORD;SHOW

Related Information

Commands: ALLOW, SHOWALLOW
Manuals: Performing System Operation Tasks

DISASSOCIATE

Removes control of a device class from the user.

Syntax


  DISASSOCIATE devclass

Parameters

devclass: The name of a device class configured during SYSGEN.

Operation Notes

This command negates a previously issued ASSOCIATE command by removing control of a device class from a user. The command may be issued by the system operator or by the user. The user implicitly disassociates a device when logging off.

Use

This command may be issued from a session, program, or in BREAK. Pressing Break has no effect on this command.

Example

To terminate control of the device class TAPE, enter:


  DISASSOCIATE TAPE

Related Information

Commands: ASSOCIATE

DISCRPS

Enables or disables the rotational position sensing (RPS) feature on a specified logical device. It requires a special firmware upgrade CS-80 disk drives.

Syntax


  DISCRPS ldev { ,ENABLE [{,value,value}] ,DISABLE }

Parameters

ldev

The logical device number of the specified CS-80 disk drive.

ENABLE

Enables rotational position sensing on the device.

DISABLE

Disables rotational position sensing on the device.

value

Allows the time-to-target and window size to be tuned, in hundreds of micro seconds. If you specify one value you must specify both values. The first is interpreted as the time-to-target value; the second is interpreted as the window size value. This parameter only works in conjunction with ENABLE.


                            (micro seconds)
  Default time-to-target 90 (9000         )
           window size   30 (3000         )

ONLY use this parameter if you have a clear understanding of its meaning and implications.

Operation Notes

The DISCRPS command allows you to enable or disable the rotational position sensing feature for CS-80 disk drives. With RPS enabled, the disk drive signals its availability to do an I/O only when it is a small rotational distance away from the target data. This improves system performance when more than one drive is connected to the same HP-IB channel.

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 commands.

Example

To enable the RPS feature on logical device 1 and display the status of the disk drive, enter:


  DISCRPS 1,ENABLE
  SHOWDEV 1
  LDEV   AVAIL    OWNERSHIP  VOID  DEN ASSOCIATION
  1    DISC (RPS) 50 FILES

To use the value parameter with ENABLE to set time-to-target and window size to the default values, enter:


  DISCRPS ldev,ENABLE,90,30

Related Information

Commands: SHOWDEV
Manuals: CS/80 Instruction Set Programmers Manual

DISCUSE (UDC)

The DISCUSE UDC executes the DISKUSE command to display disk space usage, in sectors, for one or more directories or a directory tree. This UDC is provided for those who are used to spelling disk with a "c".

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

Syntax


  DISCUSE [ [DIR=]dir_name] [;USENAME | ;TREE | ;NOTREE]

Parameters

Refer to the DISKUSE command for a complete explanation of the parameters used with the DISCUSE UDC. The following parameters are supported with the DISCUSE UDC.

dir_name: Directory name for which information is being listed (optional).
TREE: Causes all directories below and including dir_name to be reported.
NOTREE: Causes dir_name only to be reported.
USENAME: Causes DISKUSE to use dir_name name to decide whether or not to display multiple levels of directories.

Operation Notes

The DISCUSE UDC runs the DISKUSE command and reports disk space, in sectors, for a directory. Refer to the DISKUSE command for a complete explanation of the operation.

Use

This UDC may be issued from a session, a job, a program, or in break mode. Pressing Break aborts execution.

Examples

The following example illustrates the use of the DISCUSE UDC. Note that a message is printed to remind you to use the DISKUSE command.


  DISCUSE
  Please use the DISKUSE command.
                 ^
  SECTORS
    TREE   LEVEL DIRECTORY (CWD= /ACCT/GROUP/d0)
           BELOW
    2100   330   .

Refer to the DISKUSE command later in this chapter for additional examples.

Related Information

Commands: DISKUSE, LISTFILE, REPORT

DISKUSE

Displays disk space usage, in sectors, for one or more directories or a directory tree.

Syntax


  DISKUSE [[DIR=]dir_name] [; TREE | NOTREE | USENAME ]

Parameters

dir_name: Directory name for which information is being listed (optional). The dir_name is assumed to be an MPE syntax name. HFS-named directories may be shown if dir_name starts with a dot (.) or a slash (/). If dir_name is an HFS name and ends in a slash, then all objects at all levels under and including dir_name are reported, unless the NOTREE option is specified. The use of wildcards is permitted. If dir_name is omitted, the process' current working directory (CWD) is assumed.
TREE: Causes all directories below and including dir_name to be reported. The dir_name may or may not end in a slash (/), with no error or warning detected. Since the MPE naming convention does not support a trailing slash (/), the TREE option is the only way to report multi-level disk space usage for an MPE-named directory in a single command.
NOTREE: Causes dir_name only to be reported. If dir_name is an HFS name and ends in a slash (/), a warning tells you that NOTREE overrides the trailing slash (/).
USENAME: Causes DISKUSE to use dir_name name to decide whether or not to display multiple levels of directories. If dir_name is an HFS name and ends in a slash (/), then it and all directories under it are shown. If dir_name does not end in a slash (/), then only dir_name is reported. The USENAME parameter only applies to HFS-named directories and is ignored for MPE-named directories. The USENAME parameter is the default.

Operation

The DISKUSE command reports disk space, in sectors, for a directory. Disk space allocated to directories themselves (including accounts and MPE groups) is counted as part of the total number of sectors. The process' CWD is shown for all relative pathnames.

The number of components in the pathname controls the level of directories being reported. If a pathname has four components, for example, /a/b/c/d, then only directories with four or more components contribute to the output. This also applies to the use of wildcard component names. For example, /@/@/@/@ only counts directories with at least four components in their pathname (absolute or relative, depending on how it was specified). MPE names follow the same formula: @.@.@ reports only MPE-named directories one level below MPE groups. (@.@ is the same since it is qualified with the logon account name.)

Use

You must have traverse directory entries (TD) and read directory entries (RD) permissions to each directory contributing to the reported totals. TD access is needed to each directory component named in dir_name. (Refer to the ALTSEC command in this chapter for additional information on directory permissions.)

Note that the MPE syntax cannot specify a group.account. MPE syntax only permits dir.group.acct if dir is a valid MPE name; that is, all uppercase alphanumeric. (If group.account were specified, it would be interpreted as a file called group.account.logon_account.)

Directory errors can occur while DISKUSE is collecting file space information. For example, if you lack traverse directory entries (TD) access to one or more of the lower level directories, an error occurs.

If ;TREE is specified, you will only be able to see directories that you have TD and RD access to. DISKUSE stops on the first error encountered. This may result in no data (other than a header) displayed, or in the case of wildcard names, some directories are seen (up to the directory where the error occurred). Even in the wildcard directory name case, once an error is encountered, DISKUSE terminates.

There are several ways to see all disk space used on the system:

To show the disk space for every directory on the system, enter:
```
  DISKUSE /
```

To show only the total system disk space in one line, enter:


  DISKUSE /;NOTREE
  NOTREE option overrides directory name ending in "/".
    (CIWARN 9041)

To display disk space used by all directories directly under the root, enter:
```
  DISKUSE /@
```

Examples

The illustration below shows a hierarchical directory structure, upon which all of the succeeding examples are based. Directory names are shown as the character d plus a number (for example, d0), and file names are shown as the character f plus a number (for example f1). For illustrative purposes, the HPPROMPT variable has been set to show the current working directory (HPCWD). For example:


  :setvar hpprompt "hpcwd:"
  /ACCT/GROUP/d0:

Hierarchical Directory Structure


                 /ACCT/GROUP/d0 = CWD
                    |
   -----------------|------------------------------
   |        |                  |            |  |  |
   d1       d2                 d3           f1 f2 f3
            |                  |
   ---------|--------------    |---------------------
    |   |  |   |      |   |       |   |  |  |  |
    d4  f4 f5  d5    d6  f6      d7  f7 f8 f9 f10
    |          |      |           |
  --|----     -|-  ---|------   --|--------------------
   |    |      |   |  |     |   |    |   |   |    |   |
  f11 f12    d8  f13 f14 f15  d9  f16 f17 f18 f19 f20

The example shown below illustrates the format of the DISKUSE output. In this example, the TREE option is implied by the trailing slash (/). The current working directory (CWD) relative display is shown as part of the header line. If the CWD name is long, it truncates with a dollar sign ($).


  /ACCT/GROUP/d0:diskuse ./
      SECTORS
    TREE    LEVEL  DIRECTORY (CWD= /ACCT/GROUP/d0)
            BELOW
     64 +     0  ./d1/
     96      32  ./d2/d4/
     64       0  ./d2/d5/d8/
     128     64  ./d2/d5/
     112     48  ./d2/d6/
     448 +  240  ./d2/
     64       0  ./d3/d7/d9/
     208    144  ./d3/d7/
     336 +  128  ./d3/
     48 +     0   (files directly below specified directory)
     960    240  ./ (64 +)
  /ACCT/GROUP/d0:

Each of the columns contains information about the directory.

DIRECTORY

(left-justified) Displays the selected directory name, in HFS-format. The directory pathname wraps around to the next line if it is longer than the field.

LEVEL BELOW

(right-justified) Shows the number of sectors allocated directly to all objects immediately under the named directory. The space used by the listed directory file (container) does not contribute to this number, nor does the space used by the objects under directories under the displayed directory. The sum of the number of sectors reported by the following command equals the number shown under the LEVEL BELOW column. The number in the LEVEL BELOW column is zero if the reported directory is empty.


  LISTFILE dir_name/@,2;NOTREE

TREE

(right-justified) Displays the total number of sectors used by the directory listed. This includes space used by the directory itself, all files immediately under the directory, and space used by all subdirectory entries. The sum of the number of sectors seen in the following command equals the total number in the TREE column.


  LISTFILE dir_name,2;TREE

The plus signs (+) shown in the TREE column refer to the directories that are one level below the target directory. When added, the sectors shown in this example equal 896. The last entry shows the total number of sectors (960) used by all subdirectories under the target directory (896) plus the sectors used by the target directory itself (64).

The next example illustrates the use of the NOTREE option. Only the directory name is displayed.


  /ACCT/GROUP/d0:diskuse /ACCT/GROUP/d0 ;notree
      SECTORS
    TREE    LEVEL  DIRECTORY
            BELOW
     960     240  /ACCT/GROUP/d0/
  /ACCT/GROUP/d0:

If the directory name parameter is omitted, the CWD is assumed, as seen in the following example:


  /ACCT/GROUP/d0:diskuse
      SECTORS
    TREE    LEVEL  DIRECTORY (CWD= /ACCT/GROUP/d0)
            BELOW
     960     240  ./

The next example illustrates the use of the TREE option. Information is reported for the dir_name (d3) and all directories below.


  /ACCT/GROUP/d0:diskuse ./d3/@ ;tree
      SECTORS
    TREE    LEVEL  DIRECTORY (CWD= /ACCT/GROUP/d0)
            BELOW
     64      0  ./d3/d7/d9/
     208 + 144  ./d3/d7/
     208        ./d3/@
  /ACCT/GROUP/d0:

MPE syntax can also be used, as shown in the following example (note that the dir_name (MYDIR) is upshifted.) This example is not based on the directory structure shown.


  DISKUSE mydir.group.acct
       SECTORS
     TREE   LEVEL  DIRECTORY
            BELOW
     2100    330  /ACCT/GROUP/MYDIR

NOTE: The output is presented in HFS syntax, even if the directory name is supplied in MPE syntax. If wildcards were used to specify the directory name in MPE syntax, then the final line of output is the user-supplied directory name (upshifted) in MPE format.

Wildcards can be used to see a "horizontal cut" of disk s pace usage at an arbitrary directory depth. Wildcarding can be used in TREE and NOTREE output, as shown in the following examples.


  /ACCT/GROUP/d0:diskuse ./@
      SECTORS
    TREE    LEVEL  DIRECTORY (CWD= /ACCT/GROUP/d0)
            BELOW
     64 +       0  ./d1/
     448 +    240  ./d2/
     336 +    128  ./d3/
     848           ./@
  /ACCT/GROUP/d0:

  /ACCT/GROUP/d0:diskuse ./@/
      SECTORS
    TREE    LEVEL  DIRECTORY (CWD= /ACCT/GROUP/d0)
            BELOW
     64 +     0  ./d1/
     96      32  ./d2/d4/
     64       0  ./d2/d5/d8/
     128     64  ./d2/d5/
     112     48  ./d2/d6/
     448 +  240  ./d2/
     64       0  ./d3/d7/d9/
     208    144  ./d3/d7/
     336 +  128  ./d3/
     848         ./@
  /ACCT/GROUP/d0:

The last line of output contains the directory name and the total number of sectors (under the TREE column). The final TREE number always equals the sum of all other TREE numbers for directories with the same number of components as contained in the user-specified name that are designated with a plus sign (+) in the TREE column. For example, if you specified a pathname with three components, then the sum of the TREE field for all directory names with exactly three components equals the final total value.

Related Information

Commands: LISTFILE, REPORT
Manuals: None.

DISMOUNT

Releases a volume set that was explicitly reserved by the user with a MOUNT or VSRESERVE command. The equivalent native mode command is VSRELEASE. (Native Mode)

Syntax


  DISMOUNT [{ * 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.
volume- setname: 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 DISMOUNT command allows you to release a volume set that you explicitly reserved using the MOUNT or VSRESERVE command. You can request a release only for a volume set that you have reserved; you cannot alter the status of the volume set for other users.

Volume sets in MPE/iX are not tied to groups and accounts (this differs from the MPE V/E scheme of disk partitioning).

The naming convention for MPE/iX volume sets differs from the naming convention for MPE V/E private volumes. MPE/iX volume set names may consist of any combination of alphanumeric characters, including the period (.) and the underbar (_). The name must begin with an alphabetic character and consist of no more than 32 characters.

Table 5-1 "Command Acceptance of Naming Conventions - DISMOUNT Command" is a comparison of naming conventions between the MPE/iX VSxxxxxx and MPE V/E xxxMOUNT commands.

Table 5-1 Command Acceptance of Naming Conventions - DISMOUNT 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.logon acct`.	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 named `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 the V.G.A. name in that form, but no interpretation is made as to the referencing of G and A. Instead, MPE/iX treats V.G.A as a single, long string name, just as it would treat A_VERY_LONG_NAME_FOR_SOMETHING.

As a convenience to established HP users, MPE/iX accepts the naming convention that was used for MPE V/E private volumes. DISMOUNT V.G.A will succeed. DISMOUNT V will access 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, VSRELEASE V succeeds only if a volume set V exists. The MPE/iX commands do not call up any default specifications for group and account. VSRELEASE V.G.A succeeds only if a volumeset V.G.A is on line. With all 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.

We recommend that you do no 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 confusion and, in some cases, 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. Use volumes (UV) or create volumes (CV) capability is required to use this command.

Examples

To release the volume set MYSET.B.C, that was previously reserved with a MOUNT or VSRESERVE command, enter:


  DISMOUNT MYSET.B.C

You may also use the VSRELEASE command:


  VSRELEASE MYSET.B.C

Related Information

Commands: MOUNT, LMOUNT, DSTAT, VSRESERVE, VSRELEASE
Manuals: Volume Management Reference Manual

DO

Allows the user to reexecute any command still retained in the command line history stack. It also permits the user to edit the command before reexecuting it, but without having to use the interactive mode of the REDO command. (Native Mode)

Syntax


  DO [CMD=cmdid] [;EDIT=editstring]

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

cmdid

The command to reexecute. The command may be specified by its relative or absolute order in the command line history stack, or by name (as a string), in whole or in part. The default is -1, the most recent command. MPE/iX detects an error if cmdid does not exist in the command line history stack. Table 5-1 "Command Acceptance of Naming Conventions - DISMOUNT Command" defines the DO command directives.

Table 5-2 DO Command - Reexecute Directives

`cmdid`	Executes
(omitted)	Previous command.
-`n`	The `n`th command before the most recent one, where `n` is a number in the command line stack relative to the most recent command, which is -1.
`m`	Command number `m` in the command line stack. The number `m` is absolute (not relative).
`string`	The most recent command beginning with `string`.

editstring

String specifying the edit to be performed on cmdid before it is reexecuted. If you omit editstring, the command is reexecuted immediately, with no editing performed.

If you specify editstring, it must appear, character for character, and space for space, exactly as it would if you were using the REDO command in interactive mode.

The editing directives used in editstring are defined in Table 3-5

Table 5-3 Editing Directives for the DO Command

Directive Effect

i INSERT. If text follows the i, the text following i is inserted in the current line at the position after the i.

r REPLACE. If text follows the r, the text following r replaces the same number of characters in the current line, beginning at the position of r.

d DELETE. Deletes a character from the current line for each specified in the edit line. Note that "d d" does not specify a range but simply deletes one character from the position above each d. Multiple d's may be followed by an insert or replace operation.

dw DELETE WORD. Deletes a word starting at the letter d. A word is defined as all characters except a space, comma, or semicolon. If you place the d directly beneath a word delimiter, then the word and the delimiter characters are deleted. If no word exists on the command line, no delete occurs. You may follow this directive with other edits.

ddelim DELETE TO DELIMITER. Deletes all characters starting at the position of the d and ending at, but not including, the specified delimiter. If delim is not found, no delete occurs. You may follow this directive with other edits.

d> DELETE TO EOL. Deletes to the end of the current line from the position specified by d>. It may be followed by an INSERT or REPLACE operation.

^ UPSHIFT. Upshifts the character positioned at the ^. You may specify multiple ^ characters to upshift a series of characters. Or, you may type multiple ^ characters, followed by spaces, then followed by more ^'s to upshift some characters while skipping others. You may follow this directive with other edits.

^w UPSHIFT WORD. Upshifts the word starting at the position specified by ^. A word is defined as all characters except a space, comma, or semicolon. If you place the ^ directly beneath a word delimiter, the delimiter is skipped and only the word is upshifted. If no word exists on the command line, no upshift occurs. You may follow this directive with other edits.

^delim UPSHIFT TO DELIMITER. Upshifts all characters starting at the position specified by the ^ and ending at, but not including, the specified delimiter. If delim is not found, no upshift occurs. You may follow this directive with other edits.

^> UPSHIFT TO EOL. Upshifts all characters starting from the position specified by the ^ to the end of the current line. You may follow this directive with other edits.

v DOWNSHIFT. Downshifts the character positioned at the v. You may specify multiple v's to downshift a series of characters. Or, you may type multiple v's, followed by spaces, then followed by more v's to downshift some characters while skipping others. You may follow this directive with other edits.

vw DOWNSHIFT WORD. Downshifts the word starting at the position specified by v. A word is defined as all characters except a space, comma, or semicolon. If you place the v directly beneath a word delimiter, the delimiter is skipped and only the word is downshifted. If no word exists on the command line, no downshift occurs. You may follow this directive with other edits.

vdelim DOWNSHIFT TO DELIMITER. Downshifts all characters starting at the position of the v and ending at, but not including, the specified delimiter. If delim is not found, no downshift occurs. You may follow this directive with other edits.

v> DOWNSHIFT TO EOL. Downshifts all characters starting from the position specified by the v to the end of the current line. You may follow this directive with other edits.

>text APPEND. The > followed by text appends the text to the end of the current line. If > is positioned beyond the end of the current line, then a replacement is performed instead.

>d DELETE FROM EOL. Deletes from the end of the current line, right-to-left. Multiple d's may be specified after >, as well as INSERT and REPLACE strings.

>dw DELETE WORD FROM EOL. Deletes the last word in the command line. To find the last word, trailing word delimiters are skipped. If no word exists in the command line, then none is deleted. If you follow >dw with additional editing directives, each edit is performed recursively. That is, the first edit is performed (updating the current EOL), then the next edit is performed (again updating the current EOL), and so on.

>ddelim DELETE TO DELIMITER FROM EOL. Starting at the end of the current line, deletes all characters right-to-left up to, but not including, delim. If the delimiter is not found, no delete occurs. If you follow this directive with additional editing directives, each edit is performed recursively. That is, the first edit is performed (updating the current EOL), then the next edit is performed (again updating the current EOL), and so on.

>^ UPSHIFT FROM EOL. Upshifts the character at the current EOL. You may specify multiple ^'s to upshift a series of characters (read right-to-left) from the EOL. Also, you may follow this directive with other edits.

>^w UPSHIFT WORD FROM EOL. Upshifts the last word in the command line. You may follow this directive with other edits.

>^delim UPSHIFT TO DELIMITER FROM EOL. Starting at the end of the current line, upshifts all characters right-to-left up to, but not including, delim. If the delimiter is not found, no upshift occurs. You may follow this directive with other edits.

>v DOWNSHIFT FROM EOL. Downshifts the character at the current EOL. You may specify multiple v's to downshift a series of characters (read right-to-left) from the EOL, and you may follow this directive with other edits.

>vw DOWNSHIFT WORD FROM EOL. Downshifts the last word in the command line. You may follow this directive with other edits.

>vdelim DOWNSHIFT TO DELIMITER FROM EOL. Starting at the end of the current line, downshifts all characters right-to-left up to, but not including, delim. If the delimiter is not found, no downshift occurs. You may follow this directive with other edits.

>rtext REPLACE. Replaces characters at the end of the command line. The replacement is done so that the last (rightmost) character of the replacement string is at the end of the line.

c CHANGE. Changes all occurrences of one string to another in the current line when the search string and replace string are properly delimited. A proper delimiter is a nonalphabetic character (such as ', ", / or ,). The substitution is specified as: c<delim> search-string<delim> [replace-string [<delim>]]. Omitting the replace-string causes occurrences of search-string to be deleted, with no substitution.

u UNDO. A single u in column one cancels the most recent edit of the current line. Using the UNDO command twice in a row cancels all edits for the current line and reestablishes the original, unedited line. If u is placed anywhere other than column one of the current line, then a simple replacement is performed. UNDO makes sense only if you have a line on which you have performed some editing that can be "undone."

other Simple replacement. Any other character (not i, r, d, d>, >, >d, c, or u) causes that character to be replaced in the current line at the position indicated by the character. In fact, simple replacement also occurs for the editing characters i, r, c, or > if they are not followed by text; or if > appears at or beyond the current end of line.

NOTE: A word is defined as a grouping of characters delimited by a space, comma, semicolon, =, (, ), ^", ', tab.

Operation Notes

Reexecutes the command specified by cmdid. The user may specify an optional edit string to edit the command before it is reexecuted. This command is a companion to the enhanced MPE/iX version of the REDO command. Unlike REDO, the DO command does not permit interactive editing.

If editstring is specified, the edit is performed on cmdid before the command is reexecuted. The editstring must appear exactly as it would if you were using the REDO command.

Both cmdid and editstring must be surrounded by quotation marks (either " or ') if they contain any delimiters such as ; " ' [, ], =, or a space.

Use

This command is available in a session or in BREAK. It is not available in a job or from a program. Pressing Break terminates recursive command executions from the history/redo stack.

Editing Samples

Practical uses of the editing commands listed above are shown in Table 5-4 "Editing Samples for the DO Command".

Table 5-4 Editing Samples for the DO Command

Edit	Action
`u`	First occurrence undoes the previous edits. The `u` must be in column one.
`u`	Second occurrence undoes all edits on the current line. The `u` must be in column one.
`rxyz`	Replaces the current text with `xyz` starting at the position of `r`.
`xyz`	Replaces the current text with `xyz` starting at the position of `x`.
`ixyz`	Inserts `xyz` into the current line, starting at the position immediately before the `i`.
`ddd`	Deletes three characters, one above each `d`.
`d xyz`	Deletes a single character above the `d`, skips one space, then replaces the current text with `xyz` starting at the position of `x`.
`ddixyz`	Deletes two characters, then inserts `xyz` in the current line in the position before the `i`.
`d d`	Deletes one character above the first `d`, skips two spaces and deletes a second character above the second `d`. It does not delete a range of characters.
`d d>xyz`	Deletes a single character above the first `d`, skips two spaces and deletes to the end of the line beginning at the second `d`, and then appends `xyz` to the end of line.
`>xyz`	Appends `xyz` to the end of the current line.
`>ddxyz`	Deletes the last two characters from the end of the current line and then appends `xyz` to the end of the line.
`>rxyz`	Replaces the last three characters in the current line with `xyz`.
`>ixyz`	Appends `xyz` to the end of the line. In this case, the `i` command is superfluous, because `>` accomplishes the same result. Using `>xyz` would be sufficient.
`c/ab/def`	Changes all occurrences of `ab` to `def`, starting at `c`.
`c"ab"`	Deletes all occurrences of `"ab"` starting at `c`.
`cxyz`	Replace the current text with `cxyz`, starting at `c`. Because delimiters have been specified (as they were in the previous two examples), this is a simple replacement.
dw	delete the word starting at the d
>dw	delete the last word
^w	upshift the word starting at the ^
>vw	downshift the last word

Examples

DO PAS: Reexecutes the most recent command beginning with the string PAS.
DO 10: Reexecutes command number 10 (absolute) on the command history stack.
DO -2: Reexecutes the second-to-last command on the stack (one command before the most recent).
DO -2, c/5A/5B: Change all occurrences of 5A to 5B in the command preceding the most recent one before reexecuting it. The default is -1.
do ,c/5A/5B: Change all occurrences of 5A to 5B in the most recent command before reexecuting it.
DO RUN, ">;DEBUG": Append ;DEBUG to the most recent RUN command and then reexecute it.
DO 'RUN MYP', '>;LIB=G': Find the most recent command beginning with RUN MYP and append ;LIB=G before reexecuting it.

Related Information

Commands: REDO, LISTREDO, WORD evaluator function
Manuals: Using the HP 3000 Series 900: Advanced Skills

DOIONOW

Executes the changes to the I/O configuration made with the SYSGEN utility, while the system remains online.

Syntax


  DOIONOW

Parameters

None.

Operation Notes

Use the DOIONOW command to start the online reconfiguration of your I/O devices.

Use

This command is available from a job, session, a program, or in BREAK. Pressing Break has no effect on this command.

Example

After you have made changes to the system I/O configuration with SYSGEN's I/O Configurator, enter:


  :DOIONOW

Related Information

Commands: SYSGEN
Manuals: Performing System Management Tasks System Startup, Configuration, and Shutdown

DOWN

Removes a device from normal system use. This command does not apply to the system console or to disk drives.

Syntax


  DOWN ldev

Parameters

ldev: The logical device number of the device being taken offline.

Operation Notes

When the DOWN command is issued for a device that is in use, the request is responded to when the process currently accessing it releases the device.

The system console cannot be taken down. Any attempt to do so results in the following error message:


  DOWN NOT PERFORMED ON CONSOLE DEVICE (CIERR 3150)

CAUTION: When any device is powered down without the use of the DOWN command, subsequent access to that device can result in indefinite waiting, erroneous transfers, or other incorrect operation. Often these failures occur with no indication to the system operator or to the user. For this reason, it is very important that every device that is not fully operational (especially those that are powered down) be taken down with the DOWN command. A device that will be inoperable for more than a few hours can be temporarily removed from the I/O configuration 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 used only from the console unless distributed to users with the ALLOW or ASSOCIATE command.

Example

To take logical device number 7 offline, enter:


  DOWN 7

To take logical device number 10 (an input-spooled, job-accepting magnetic tape) offline, enter:


  DOWN 10
  STOPSPOOL 10
  11:16/31/SP#10/STOPPED
  11:16/31/LDEV#10 NOT READY

Related Information

Commands: SHOWDEV, UP, ABORTIO
Manuals: Performing System Operation Tasks

DOWNLOAD

Downloads format information to a line printer.

Syntax


  DOWNLOAD ldev [ ,filename ,MARGIN=nn ] [,...]

Parameters

ldev: The logical device number of the output device. This device must be an HP 2608 or HP 2563 Line Printer.
filename: The fully qualified name of a file containing the download control information.
nn: The print position that the first byte of data assumes. This number can be between 1 and 16, inclusive. Note that the HP 2608 hardware documentation discusses a margin offset which varies from 0-15. This offset is not relevant to the margin parameter of the DOWNLOAD command, as the software compensates for the hardware offset of nn -1.

Operation Notes

The operator uses the DOWNLOAD command to transmit format information to system printers only. It cannot be used with remote printers.

The vertical format control (VFC) image file (filename) can define the margin setting as well as the VFC image on an HP 2608A or HP 2608S Line Printer. The number of print lines per form is limited to 127. Although the HP 2608S printer recognizes the DOWNLOAD command, Hewlett-Packard recommends controlling the HP 2608S with an environment file rather than the DOWNLOAD command. You cannot download a VFC file to an HP 2631B printer, only the MARGIN=nn is allowed.

If the MARGIN=nn parameter is specified on an HP 2608A or HP 2608S, and a MARGIN record has also been specified in the VFC file, the MARGIN record in the VFC file overrides the MARGIN parameter of the DOWNLOAD command. This parameter should only be used in cases where there is no MARGIN record in the VFC file.

When a particular print job has requirements for forms and/or a VFC file, the user indicates this need by way of a FORMS message. Refer to "Examples."

CAUTION: Do not issue a DOWNLOAD command to an HP 2608S while a spoolfile is ACTIVE. This makes the device UNAVAILABLE, and it remains so until the system is restarted with a START RECOVERY.

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 or ASSOCIATE command.

Examples

To respond to a forms message such as the following:


  IO/15:46/22/FORMS: PLEASE MOUNT PAYCHECK FORMS. USE VFC=VFCPAY
  IO/15:46/22/SP#11/LDEV# FOR #S93;OUTFILE ON HP 2608 (1)

enter:


  DOWNLOAD 11,VFCPAY

To reset the VFC to its original state, you must reference a file that contains default specifications (such as VFC6 in this example) by entering:


  DOWNLOAD 11,VFC6.PUB.SYS

To set the left margin print position to column 4 (the installation defined default) enter:


  DOWNLOAD 11,MARGIN=4

Related Information

Commands: SHOWDEV, ABORTIO
Manuals: Performing System Operation Tasks

DSTAT

Displays the current status of the disk drives on the system. (Native Mode).

Syntax


  DSTAT [ ldev ALL ]

Parameters

ldev: An integer specifying the logical device number of the disk drive whose status is requested.
ALL: Displays the status of all disk drives, both system and nonsystem. The default is that if no parameter is included, only the status of nonsystem disks is displayed.

Operation Notes

The DSTAT command is used to display the current status of one or more disk drives on the system. For example:


  DSTAT ALL
  
  LDEV-TYPE   STATUS     VOLUME (VOLUME SET-GEN)
   1- 07935    MASTER     MEMBER1   (MPEXL_SYSTEM_VOLUME_SET-0)
   2- 07935    MEMBER     MEMBER2   (MPEXL_SYSTEM_VOLUME_SET-0)
   3- 07935    MEMBER     MEMBER3   (MPEXL_SYSTEM_VOLUME_SET-0)
   4- 07935    MEMBER     MEMBER4   (MPEXL_SYSTEM_VOLUME_SET-0)
  15- 07935    MASTER     MEMBER1   (USER_VOLUME_SET-0)
  16- 07935    MEMBER     MEMBER2   (USER_VOLUME_SET-0)
  17- 07935    UNKNOWN

Table 5-5 "Disk Drive Status" defines the various status responses.

Table 5-5 Disk Drive Status

Status	Meaning
`UNKNOWN`	A volume in the `UNKNOWN` state does not have a label that the system can recognize. The volume may be from another system, it may be a new disk pack, or it may be a volume that has been formatted. An `UNKNOWN` volume is available for initialization.
`SCRATCH`	A volume in the `SCRATCH` state can be initialized. It may contain data, but by scratching the volume, the user has indicated that the data is no longer needed.
`LONER`	The volume is in the `LONER` state when its master is not mounted or when the volume set is closed by the `VSCLOSE` command.
`MASTER`	A volume in this state is the master volume of a volume set. In order for the system to recognize the volume set, the master volume must be mounted.
`MEMBER`	A volume in this state belongs to a volume set whose master is mounted. If the master is not mounted, the volume is in the `LONER` state.

If you have purchased Mirrored Disk/XL, you may see PENDING or DISABLED as well. PENDING indicates the partner disk failed to mount; DISABLED indicates the volume is not available to the system due to a disk failure. If you have Mirrored Disk/XL you also may see the following suffixes in the status portion of the display:

-MD: Mirrored disk
-SU: Split user volume
-SB: Split backup volume

Use

This command may be issued from a session, job, program, or in BREAK. Pressing Break has no effect on this command.

Example

To display the status of LDEV 1, enter:


  :DSTAT 1
  
  LDEV-TYPE   STATUS  VOLUME (VOLUME SET-GEN)
   1- 079371   MASTER  MEMBER1 (MPEXL_SYSTEM_VOLUME_SET-0)

Related Information

Commands: SYSGEN, LMOUNT, LDISMOUNT, MOUNT, DISMOUNT, VSRESERVE, VSRELEASE, VOLUTIL Utility
Manuals: Volume Management Reference Manual

ECHO

Displays a message on the standard list device. (Native Mode)

Syntax


  ECHO [message]

Parameters

message: The message to be displayed to the $STDLIST.

Operation Notes

Displays its argument, message, on the standard list device ($STDLIST). The command ignores delimiters. Quotation marks are not required around message. The ECHO command does not perform dereferencing of any kind. If you want variable dereferencing you must use explicit dereferencing (!) in the argument. A null message ( Return ) displays a linefeed.

The ECHO command is not suppressed by OPTION NOLIST in a UDC or command file, or by any setting of the HPMSGLEVEL variable.

Use

This command is available in a session, job, program, or in BREAK. Pressing Break has no effect on this command.

Examples

In the following example, although there is a variable named a that has a string value, ECHO simply displays the character a because no dereferencing has been specified.


  SETVAR a, 'hi there'
  
  ECHO a
  a

This time ECHO is given the value of the variable a argument. Explicit dereferencing has been specified and the dereferencing is done before ECHO is executed.


  ECHO !a
  hi there

Two exclamation points are resolved to one exclamation point by string substitution, and MPE/iX is prohibited from making the value substitution (even number rule).


  ECHO a
  !a

Triple (or any odd number of) exclamation points treat the argument as !a, which resolves to ! and !a, giving !hi there (odd number rule).


  ECHO !a
  !hi there

If you entered the following command line in a user command, you would see a message when an error occurred:


  IF CIERROR <> 0 THEN
  ECHO ** A CIERROR OCCURRED!: (CIERR !CIERROR) **

The first instance of CIERROR has no dereferencing, and so ECHO treats it literally. The second instance, !CIERROR, contains explicit dereferencing, and so MPE/iX substitutes a value for the system variable CIERROR before the message is displayed to $STDLIST. So, for example, if the program generated error 975, you would see this message:


  ** A CIERROR OCCURRED!: (CIERR 975) **

Related Information

Commands: CALC, SET, SETVAR, COMMENT, TELL, WARN
Manuals: Appendix A, "Predefined Variables in MPE/iX"

EDITOR

Starts the EDIT/3000 subsystem, which is used to create and manipulate ASCII text or program files.

Syntax


  EDITOR [listfile]

Parameters

listfile: Actual file designator of file to receive any output resulting from EDIT/3000 LIST and XPLAIN commands when the OFFLINE option is specified. It can be any ASCII output file. The formal file designator and default is EDTLIST. If specified with no device parameter, default device is LP.

You cannot backreference the formal file designator EDTLIST as an actual file designator in the command parameter list. For further information, refer to the "Implicit FILE Commands for Subsystems" discussion of the FILE command.

Operation Notes

The EDITOR command starts the EDIT/3000 subsystem.

Use

This command may be issued from a session or job. It may not be used from a program unless the user or the program has process handling (PH) capability. It may not be used from BREAK. Pressing Break suspends the execution of this command. Entering the RESUME command continues the execution.

Example

To run EDIT/3000 during a session and specify a line printer (device class LP) as the list device for offline output, enter:


  FILE LISTFILE;DEV=LP
  EDITOR *LISTFILE

Because the listfile is often a line printer, it is often defined with the FILE command and backreferenced as in the preceding example.

Related Information

Commands: BUILD, LISTF, LISTFILE, LISTEQ, FILE
Manuals: EDIT/3000 Reference Manual

ELSE

Provides an alternate execution sequence within an IF statement. (Native Mode)

Syntax


  ELSE

Parameters

None.

Operation Notes

The ELSE command is used only in conjunction with the IF and ELSEIF commands. The IF command is used with the ENDIF command, and optionally with the ELSE command, to control the execution of a job. The IF, ENDIF, and optional ELSE commands constitute an IF block. A logical expression is evaluated, and if true, the IF block is executed; if false, the ELSE block (if one exists) is executed.

Use

This command may be issued from a session, job, program, or in BREAK. Pressing Break has no effect on this command.

Example

The following job listing illustrates using the ELSE command:


  !CONTINUE
  !PASXL MYPROG,MYUSL
  !IF JCW>=FATAL THEN
  !  TELL USER.TECHPUBS;COMPILE FAILED
  !ELSEIF JCW>=WARN THEN
  !  TELL USER.TECHPUBS;COMPILE COMPLETED WITH WARNINGS
  !ELSE
  !  TELL USER.TECHPUBS;COMPILE COMPLETE WITH NO WARNINGS
  !ENDIF

Related Information

Commands: DELETEVAR, ELSEIF, ENDIF, IF, SETJCW, SETVAR, SHOWJCW, SHOWVAR
Manuals: None

ELSEIF

Provides an alternate execution sequence within an IF statement. Native Mode

Syntax


  ELSEIF expression [THEN]

Parameters

expression: Logical expression, consisting of operands and relational operators. The THEN keyword is optional. It may be used or omitted and has no effect on the results. The operators listed in Table 5-6 "Logical Operators - The ELSEIF Command" may be incorporated in expression.

Table 5-6 Logical Operators - The ELSEIF Command

Type	Operators
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, STR
Functions returning integers:	ABS, LEN, MAX, MIN, ORD, POS, TYPEOF
Other functions:	FINFO, SETVAR

Operation Notes

The ELSEIF command is used only in conjunction with the IF command. The ELSEIF command provides a way of avoiding nested IF statements. ELSEIF has meaning only when used after an IF construct.

Any number of ELSEIF commands may follow an IF command. In contrast, only one ELSE command may follow an IF or ELSEIF command. Refer to the ELSE and IF commands.

Use

This command may be issued from a session, job, program, or in BREAK. Pressing Break has no effect unless expression contains the INPUT evaluator function.

Example

The following example illustrates using the ELSE command with the IF command:


  IF EXPN1 THEN
    ...
  ELSE
    IF EXPN2 THEN
      ...
    ELSE
      IF EXPN3 THEN
        ...
      ELSE
        ...
      ENDIF
    ENDIF
  ENDIF

The same result can be accomplished more efficiently by using the ELSEIF command:


  IF EXPN1 THEN
    ...
  ELSEIF EXPN2 THEN
    ...
  ELSEIF EXPN3 THEN
    ...
  ELSE
    ...
  ENDIF

Notice that only one ELSE may follow an ELSEIF, while any number of ELSEIF commands may follow an IF.

Related Information

Commands: CALC, DELETEVAR, ELSE, ENDIF, IF, SETJCW, SETVAR, SHOWJCW, SHOWVAR
Manuals: None

ENDIF

Terminates an IF block. (Native Mode)

Syntax


  ENDIF

Parameters

None.

Operation Notes

The ENDIF command is used to terminate an IF block. The IF command, the optional ELSE and ELSEIF commands, and the ENDIF command constitute an IF block. A logical expression is evaluated, and if true, the IF block is executed; if false, the ELSE block (if one exists) is executed. If false and no ELSE exists, then execution continues following the ENDIF.

Use

This command may be issued from a session, job, program, or in BREAK. Pressing Break has no effect on this command.

Example

The following examples show the IF block ending with the ENDIF command:


  IF logical_expression
  ELSE logical_expression
    .
    .
    .
  ENDIF
  
  IF logical_expression
  ELSEIF logical_expression
    .
    .
    .
  ENDIF

Related Information

Commands: IF, ELSE, ELSEIF
Manuals: None

ENDWHILE

Terminates a WHILE block. (Native Mode)

Syntax


  ENDWHILE

Parameters

None

Operation Notes

This command terminates a conditional block that begins with a WHILE command. The WHILE and ENDWHILE commands constitute a WHILE block. The WHILE command evaluates an expression, and so long as that expression evaluates as true, the command(s) between WHILE and ENDWHILE are executed. If the expression evaluates as false, execution of the WHILE block ceases and execution passes to the command following ENDWHILE. Execution terminates if any command not protected by a preceding CONTINUE causes an error.

Use

This command may be issued from a session, job, program, or in BREAK. Pressing Break terminates the WHILE command loop.

Example

The following is an example of a simple WHILE block:


  WHILE logical_expression
    .
    .
    .
  ENDWHILE

Related Information

Commands: WHILE
Manuals: None

EOD

Denotes end-of-data on input stream from a job file (from an input other than $STDIN). It also terminates data initialized by the DATA command. The colon (:) is a required part of this command. (Native Mode)

Syntax

EOD

NOTE: The "&" symbol has no meaning to the input spooler when it reads records because the CI is not involved at that point.

Parameters

None.

Operation Notes

The EOD command is used to signify the end of data whose beginning was signified by a DATA command. It is also used to signify the end of a data set that was read from the standard input device.

Although in most cases programmers use EOD for delimiting data, any record beginning with a colon may delimit the data. Using a record other than EOD for this purpose, however, depends upon whether the standard input file is opened with the file name $STDIN or $STDINX.

When using a compiler language that does not provide a convention for terminating compilation (such as END. in SPL), you must enter EOD after the last record of your source program to ensure proper delimiting of your input. (EOD is not required when using the BASIC interpreter since the subsystem provides different conventions for delimiting data.)

An EOD causes the read of the FREAD intrinsic to return the CCG condition code to the calling program. This condition code indicates the end-of-file condition on the terminal. Table 5-7 "End-of-File Indicators" defines the various end-of-file indicators.

Table 5-7 End-of-File Indicators

Type of File	Indicators
`DATA` file from standard input device (for jobs and sessions)	`EOD` - terminates `$STDIN` and `$STDINX`. : followed by any other character - terminates `$STDIN`.
`DATA` files	EOD JOB DATA

Use

EOD is available only in a job or a session that is submitted with the STREAM command. It cannot be used directly from $STDIN or from a program.

Examples

To terminate a data file entered by using the STREAM command for a session identified as SESS1,BLACK.ACCTSP, your data file would contain EOD as its last record, as follows:


  DATA SESS1,BLACK.ACCTSP
    .
  data
    .
  EOD

The following program is an example of how EOD is used to terminate a set of data entered through a standard input device:


  FORTRAN
  
  PAGE 0001  HP32102B.01.12  (C) HEWLETT-PACKARD CO. 1986
  
  >$CONTROL USLINIT
  >  PROGRAM MONEY
  >  INTEGER QUARTERS,DIMES,NICKELS,PENNIES
  >  DISPLAY "INPUT MONEY AMOUNT IN DECIMAL FORM"
  >  ACCEPT DECIMALFORM
  >  CALL CHANGER(DECIMALFORM,QUARTERS,DIMES,NICKELS,PENNIES)
  >  DISPLAY QUARTERS," QUARTERS"
  >  DISPLAY DIMES," DIMES"
  >  DISPLAY NICKELS," NICKELS"
  >  DISPLAY PENNIES," PENNIES"
  >  STOP
  >  END
  
  PROGRAM UNIT MONEY COMPILED
  >  SUBROUTINE CHANGER(DECIMALFORM,QUARTERS,DIMES,NICKELS,PENNIES
  >  INTEGER QUARTERS,DIMES,NICKELS,PENNIES
  >  DECIMALFORM = DECIMALFORM*100
  >  QUARTERS = DECIMALFORM/25
  >  REMAINDER = DECIMALFORM-(QUARTERS*25)
  >  DIMES=REMAINDER/10
  >  REMAINDER=REMAINDER-(DIMES*10)
  >  NICKELS=REMAINDER/5
  >  PENNIES=REMAINDER-(NICKELS*5)
  >  RETURN
  >  END
  
  PROGRAM UNIT CHANGER COMPILED
  >  EOD
  ****   GLOBAL STATISTICS     ****
  ****  NO ERRORS,  NO WARNINGS   ****
  TOTAL COMPILATION TIME 0:00:01
  TOTAL ELAPSED TIME   0:01:29
  
  END OF COMPILE

Related Information

Commands: DATA
Manuals: None

EOJ

Ends a batch job. (Native Mode)

Syntax

EOJ

NOTE: The "&" symbol has no meaning to the input spooler when it reads records because the CI is not involved at that point.

Parameters

None.

Operation Notes

The EOJ command terminates a batch job and displays the CPU-time (in seconds) and the elapsed time since the beginning of the job (rounded to the nearest minute). MPE/iX also adds the central processor time and file space used by your job to the resource usage counters maintained for your logon account and group.

If you omit the EOJ command from a job, the next JOB command terminates the current job and starts a new one. The end of the first job is indicated by the standard end-of-job display, and the beginning of the next job is denoted by the normal job initiation display.

Use

This command may be issued from a job. It may not be used from a session, program, or in BREAK. Pressing Break has no effect on this command.

Example

The following example shows how EOJ is used within a job file to terminate a batch job:


  !JOB USER.PUBS
  !RUN MYPROG1
  !RUN MYPROG2
  !EOJ

Related Information

Commands: JOB
Manuals: Using the HP 3000 Series 900: Advanced Skills

ERRCLEAR

Zeros out all HP predefined error-related variables. (Native Mode)

Syntax


  ERRCLEAR

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

None

Operation Notes

This command is equivalent to the following:

SETVAR CIERROR 0
SETVAR HPCIERR 0
SETVAR HPCIERRCOL 0
SETVAR HPFSERR 0

Use

This command is available from a job or session. It is not available from a program or in BREAK. Pressing Break has no effect on this command.

Example


  errclear
  continue
  run database
  if hpcierr < 0 then
    echo database warning ![abs(hpcierr)] detected, proceeding...
  elseif hpcierr > 0 then
    echo FATAL database error !hpcierr detected, halting...
    escape
  endif

Related Information

Commands: ESCAPE, RETURN
Manuals: None

ERRDUMP

Allows a user to dump either the process or system error stack to a specified depth. (Native Mode)

Syntax


  ERRDUMP [errorstackdepth] [;SYS]

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

errorstackdepth

The number of error stack messages to be printed. If the actual error stack size is less than the errorstackdepth then all messages on the error stack are printed with no warnings or errors.

The process error stack currently runs from zero to sixteen. The system error stack currently runs from zero to one hundred and twenty-seven. If the errorstackdepth specified is beyond the boundaries of the process error stack, the process error stack is not dumped, and CIERR 9155 is displayed, as follows:


  INVALID PROCESS STACK DEPTH;
  EXPECTED A VALUE 0 - 16 (CIERR 9155)

If the errorstackdepth specified is beyond the boundaries of the system error stack, (specified with SYS) the system error stack is not dumped, and CIERR 9156 is displayed, as follows:


  INVALID SYSTEM STACK DEPTH;
  EXPECTED A VALUE 0 - 127 (CIERR 9156)

An errorstackdepth value of 0 dumps the entire error stack. The default value is 0.

SYS

The SYS option specifies that the system error stack is to be dumped. If the SYS option is not used, then the process error stack is dumped.

Operation Notes

The ERRDUMP command allows the user to dump either the process or the system error stack to a specified depth. If the depth specified is greater than the number of errors on the error stack, then all errors on the error stack are dumped without any warnings or errors.

If the user specifies an errorstackdepth outside of the boundaries of the error stack, an error message is displayed and the error stack is not dumped.

Use

This command may be issued from a session, job, program, or in BREAK. Pressing Break has no effect on this command.

Examples

To obtain an error stack dump, enter:


  ERRDUMP

A sample system response is:


  TYPE MANAGER; THE END-OF-FILE HAS BEEN DETECTED.
  FILE SYSTEM MESSAGE 1023.

Another example specifies that the system error stack be dumped:


  ERRDUMP 1;SYS

A sample system response is:


  THE STATUS OF THE TIME ENTRY IS NON-ACTIVE.
  TUE, FEB 9, 1988, 12:18

Related Information

Commands: ERRCLEAR
Manuals: None

ESCAPE

Allows the CI programmer to simulate all aspects of CI error handling. (Native Mode)

Syntax


  ESCAPE [ [CIERR=] errnum]

Parameters

ERRNUM: Sets the CIERROR variable to the absolute value of errnum and the HPCIERR variable is set to errnum.

Operation Notes

The ESCAPE command causes control to leave all user commands (regardless of nesting levels) and return to the CI. Batch jobs terminate (unless a CONTINUE is in effect) and sessions issue the prompt.

If no CONTINUE is active, ESCAPE causes the CI to act as it would for any error: for sessions the user command environment is cleared and the prompt is displayed; jobs terminate.

If CONTINUE is active , then ESCAPE causes the CI to execute the second command after the CONTINUE. In the following example, the CI will execute cmd2 after the ESCAPE.


  cmd1
  CONTINUE
  udc1
    ucmdA
    ucmdB
    ESCAPE
  cmd2

Use

This command may be issued from a session, job, program, or in BREAK. Pressing BREAK has no effect on this command.

Example


  errclear
  continue
  run database
  if hpcierr < 0 then
    echo database warning ![abs(hpcierr)] detected, proceeding...
  elseif hpcierr > 0 then
    echo FATAL database error !hpcierr detected, halting...
    escape
  else
    .
    .
    .
  endif

Related Information

Commands: ERRCLEAR, RETURN
Manuals: MPE/iX Commands Reference Manual Volumes I and II
Command Interpreter Access and Variables Programmer's Guide

EXIT

Terminates the command interpreter. (Native Mode)

Syntax


  EXIT

Parameters

None

Operation Notes

When you are using MPE/iX you can start another Command Interpreter by running it as a program. To do so, you enter CI.PUB.SYS, or simply CI. If you enter this command more than once, you will create levels of the CI program.

To determine what level of the command interpreter you are in, use the SHOWVAR HPCIDEPTH command. Then, to back out from the CI, enter the EXIT command. If the command interpreter is the root CI, EXIT is equivalent to BYE and ends the session. Otherwise, EXIT returns to the previous process. To go beyond HPCIDEPTH=2 requires process handling (PH) capability. To end a session without backing out of the CI level-by-level with the EXIT command, enter BYE.

Use

This command is available from a job or session. It is not available from a program or in BREAK. Pressing Break has no effect on this command.

Example

The following example shows how to determine what level of the CI you are in, and then, using the EXIT command, to back out to the root CI:


  SHOWVAR HPCIDEPTH
  HPCIDEPTH=2
  EXIT
  SHOWVAR HPCIDEPTH
  HPCIDEPTH=1

To back out from the second level to the first, use the EXIT command. To back out from the session from any level, use the BYE command.

Related Information

Commands: BYE, HELLO, RUN, XEQ, SHOWVAR
Manuals: Appendix A, "Predefined Variables in MPE/iX"

Chapter 5 Command List III

Chapter 6 Command List IV