Commands MOUNT thru OUTFENCE

The MOUNT command reserves a specific volume set for use. It notifies the system that the volume set is to remain online and is not to be taken offline by a VSCLOSE command.

Volume sets in MPE/iX are not tied to groups and accounts. This is different from the MPE V/E scheme of disk partitioning.

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

Table 9-1 “Command Acceptance of Naming Conventions - MOUNT Command” illustrates the differences between the MPE/iX and MPE V/E naming conventions for volume sets.

In MPE V/E, the name V.G.A indicates that V is the name of a volume set, that G is the name of a group, and that A is the name of an account.

MPE/iX accepts that name in that form, but no interpretation is made as to the referencing of G and A. Instead, MPE/iX 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 Hewlett-Packard users, MPE/iX accepts the naming convention that was used for MPE V/E private volumes. Thus MOUNT V.G.A succeeds and MOUNT V accesses the same volume set, provided you are logged on to account A, group G. The MPE V/E commands are able to default the logon account and group.

However, VSRESERVE V succeeds only if there is a volume set V in existence. The MPE/iX commands do not call up any default specifications for group and account. VSRESERVE V.G.A succeeds only if a volumeset V.G.A is online. With all MPE/iX VSxxxxxx commands, the .G.A component of this name is interpreted as a string, neither more nor less specific than _G_A.

If a volume set is named according to the MPE V/E naming convention (V.G.A), you must use an unambiguous reference when using the MPE/iX volume set commands.

Various user commands that give you access to your logon group's home volume set implicitly initiate reservation requests if the volume set is not reserved already. An example of one of these commands (BUILD) is:

 BUILD VFILE;DISC=500,10,1;REC=-80;DEV=VCLASS1

To issue a reserve request programmatically, you may issue an FOPEN call referencing a file residing on an unreserved volume set; this causes an implicit user initiated reserve request. An FOPEN reserve remains in effect until a corresponding FCLOSE intrinsic call is issued. The programmatic request is used when a single job/session step requires a certain volume set. Refer to the MPE/iX Intrinsics Reference Manual (32650-90028) for a description of a programmatic reserve request.

It is recommended that you not use the MPE V/E naming convention and xxxMOUNT commands. Instead use the MPE/iX naming convention and VSxxxxxx commands. Alternating between MPE V/E and MPE/iX commands may lead to errors. For example, MOUNT X used in a job stream attempts to access a volume set named X.logongrp.logonacct, which may or may not be your intention.

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.

You are logged on to account MYACCT in group GRP. To request the system operator to reserve volume set MYSET in that group and account, with a generation index of 43, enter:

 MOUNT MYSET;GEN=43

If you are logged on in another group.account, enter:

 MOUNT MYSET.GRP.MYACCT;GEN=43

The USERPASS parameter is only available if the HP Security Monitor has been installed.

The NEWACCT command may be executed only by the System Manager. The System Manager is responsible for establishing the accounting structure best suited to the computer installation.

When a keyword is specified, but its corresponding parameter is omitted (as in ACCESS= Return), the default value for that keyword is assigned (in this case, R,L,A,W,X:AC). The default is also assigned when an entire keyword parameter group (such as ACCESS=fileaccess) is omitted.

After the System Manager creates accounts and designates account managers for those accounts, the new account managers may log on and redefine their own attributes and those of their PUB groups. Account managers can also define new users and groups. The capabilities and attributes that the account manager assigns to groups and users cannot exceed those assigned to the account itself by the system manager. For example, if the system manager does not assign the account DS capability, no users in the account are permitted DS capability (which prohibits them from linking programs that use extra data segments).

The PUB group is initially assigned the same capability class attributes, permanent file space limit, CPU limit, and connect-time limit as the account, but no password. Its initial security allows READ and EXECUTE access to all users who successfully log on to the account, and APPEND, WRITE, LOCK, and SAVE access to account librarian (AL) and group users (GU) only. These access provisions are (R,X:ANY;A,W,L,S:AL,GU).

	NOTE: If you specify volume-related commands or parameters for a volume set that is not currently mounted, or for an account that does not exist, MPE/iX returns an error message.

This command may be issued from a session, a job, a program, or in BREAK. Pressing Break has no effect on this command. System manager (SM) capability is required to use this command.

To create an account with the account name ACI, and the account manager name MNGR, with all other parameters assigned by default, enter:

  NEWACCT ACI,MNGR

To create the account DOCTOR on the system volume set, with the manager named WHO, and on the volume set called MY_VOL, you must create it with two parallel commands:

  NEWACCT DOCTOR,WHO;CAP=IA,BA,GL,AM,AL
  NEWACCT DOCTOR,WHO;ONVS=MY_VOL

The second command connects the accounting structures established on the system volume and on the volume set. By default, however, the PUB group of this account is on the system volume set.

To place the PUB group on the volume set MY_VOL, you need to use the PUB parameter in the first command:

  NEWACCT DOCTOR,WHO;CAP=IA,BA,SF,ND,GL,AM,AL
  NEWACCT DOCTOR,WHO;ONVS=MY_VOL
  ALTGROUP PUB.DOCTOR;HOMEVS=MY_VOL

To create the account DOCTOR on the system volume set, with the manager named WHO, and a UID of 150 and a GID of 120, enter:

  NEWACCT DOCTOR,WHO;UID=150;GID=120;CAP=IA,BA,SF,ND,GL,AM,AL

All of the parameters for the NEWCI command are identical (syntactically and semantically) to the RUN command. See the help text for RUN for complete descriptions of all the parameters except the "progfile" parameter.

The syntax for the NEWCI command (and all of the parameters) is identical to the RUN command. The behavior of the NEWCI command differs from the RUN command is several important ways:

The NEWCI command can only be executed from a session, it is not allowed in a job.The NEWCI command is only executable from the root CI process, which is sometimes referred to as the usermain process. Normally, NEWCI is executed from the root CI process when executing a logon UDC. If a NEWCI command is executed, then the newly created process replaces the existing root CI process and becomes the new root CI process for that session. The NEWCI command can be executed programmatically provided the caller is executing in a session and the calling process is the root process for the session.

The NEWCI command is not executable in break mode. If a user runs a program (via the RUN command) and then hits break, then that user's session is in break mode. The SHOWME command displays a message indicating a session is in break mode. When in break mode, if the user tries to execute another program via the NEWCI command (or the RUN command), then the user will be asked if they wish to abort the program that is current running. If the user answers "YES" then the current program will be aborted and the new program will execute. In the case of NEWCI, the new program will replace the existing CI process.

The NEWCI command disables break handling for the session. Break remains disabled even if the program calls FCONTROL to re-enable break. The only way to re-enable break for the session is to execute "newci ci.pub.sys". This causes the MPE/iX Command Interpreter to replace the current CI, and CI.PUB.SYS re-enables break. CI.PUB.SYS also re-executes logon UDCs which may in turn disable break via the option nobreak feature.

NEWCI effects various session resources as follows:

The NEWCI command can be used to replace the current CI process (which may not be the standard MPE/iX CI if a NEWCI command was previously done) with the standard MPE/iX CI. This is done by executing the command "newci ci.pub.sys". If CI.PUB.SYS is executed using the NEWCI command, the behavior is slightly different than if it is executed using the RUN command. The behavior of the MPE/iX CI is identical to its behavior at logon time.

NEWCI from a Logon UDC

The most common usage of NEWCI is from a logon UDC (most commonly an OPTION NOBREAK logon UDC). Many system manager setup their users such that a logon UDC automatically execute the appropriate application program at logon time. Consider the following example logon udc:

dologon
option logon nobreak
file progdata=datafile.pub.payroll
newci payroll.pub.payroll
*****

NEWCI Programmatically

The NEWCI command is programmatically executable, but only from the "root" CI process. Some programs allow users to interactively enter CI commands (by convention CI commands are generally prefixed with a : character). Most HP product/utilities allow CI commands to be entered interactively. In the example below, the NEWCI command is executed programmatically from within TDP. In this example, TDP is the root CI (it became the root CI when the first NEWCI command was issued).

:hello mgr.paryoll
:newci tdp.pub.sys
TDP/V (A.05.05)  HP36578 Editor (c) COPYRIGHT Hewlett-Packard Co. 1993
/:newci payroll.pub.payroll
CORPORATE PAYROLL (Version A.00.00)
CMD>

	NOTE: In the above example the ":newci payroll.pub.payroll" command would not be allowed if the RUN command had been used in place of the NEWCI command to load TDP.

NEWCI CI.PUB.SYS

The NEWCI command can be used to replace the current CI process with the standard Hewlett- Packard Command Interpreter (CI.PUB.SYS). When CI.PUB.SYS is executed using the NEWCI command it functions exactly the same as it does at logon time (see table above).

:hello mgr.paryoll
HP3000  Release: X.60.16   User Version: X.60.16   WED, JUL 14, 1999,  9:21 PM
MPE/iX  HP31900 C.16.01  Copyright Hewlett-Packard 1987.  All rights reserved.
** System Welcome Message...
:newci payroll.pub.payroll
CORPORATE PAYROLL (Version A.00.00)
CMD> :newci ci.pub.sys
** System Welcome Message...
:

	NOTE: This example assumes that the application program payroll.pub.payroll allows the user to enter CI commands interactively (prefixed with a :). This is a common feature in MPE application programs - but it does vary from program to program. In this example the command "newci ci.pub.sys" could be executed by either the COMMAND or HPCICOMMAND intrinsic.

None

The NEWDIR command creates a directory named dir_name. All parent directories must already exist. The new directory inherits the group ID (GID) from its parent directory and the user ID (UID) from the user creating the directory. The special directory entries dot (.) and dot-dot (..) are automatically created under dir_name.

By default NEWDIR creates an MPE-named directory, which means that dir_name must follow all MPE naming rules. Since the MPE name syntax defines three levels, fully (or partially) qualified MPE-named directories can only be created under MPE groups. Unqualified MPE-named directories are created relative to the CWD.

If dir_name begins with a dot (.) or a slash (/), then HFS naming rules are enforced.

Directories do not support lockwords, file equations, or system defined file names (for example, $NEWPASS).

You must have create directory entries (CD) permission for the parent directory and save files (SF) capability. Furthermore, traverse directory entries (TD) ac cess is required for each directory component named in dir_name. (Refer to the ALTSEC command in this chapter for further information on directory permissions.)

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

In the following two examples, a user creates a directory called DIR1. In the first example, the full pathname of the directory is specified in all uppercase since HFS syntax is case-sensitive. In the second example, the user enters the information in lower case using the MPE syntax dir_name.groupname.acctname. (Any case-lower-, mixed-, or uppercase could be used since the CI will automatically shift pathnames entered in MPE syntax to uppercase.)

  NEWDIR /MYACCT/MYGRP/DIR1
 
 NEWDIR dir1.mygroup.myacct

The following example creates an HFS-named directory called john by specifying the full pathname of the directory. Since the directory will reside in the MPE/iX account MYACCT, and since HFS syntax is case-sensitive, the user enters "MYACCT" in uppercase.

  NEWDIR /MYACCT/jones/cmdf/john

The following example creates an MPE-named directory called DIR1 in the current working directory (CWD). Note that the dir_name is shifted to uppercase.

  NEWDIR dir1

The following example creates an HFS-named directory called dir1 in the current working directory (CWD). Note that in this example, the dir_name is not shifted to uppercase.

  NEWDIR ./dir1

The following example creates an HFS-named directory called dir2 by specifying POSIX syntax:

  NEWDIR ./dir2

The next example creates an MPE-named directory called A.group.logon_acct.

  NEWDIR a.group

Account managers use the NEWGROUP command to create groups within their accounts and assign attributes to each. The attributes assigned to the group may not exceed those permitted the accounts themselves (defined when the system manager created the accounts). However, within account limits, the account manager may redefine the group and user attributes and capabilities, as well as those of the PUB group.

The PUB group is initially assigned and the same capability class attributes, permanent file space limit, and CPU-time limit as the account but no password. Its initial security grants READ (R) and EXECUTE (X) access to all users (ANY) who successfully log on to the account. APPEND (A), WRITE (W), LOCK (L), and SAVE (S) access is assigned to the account librarian (AL) and group users (GU) only.

When a keyword parameter (such as PASS=) or keyword parameter group (such as PASS=password) is omitted from the NEWGROUP command, the default value corresponding to that parameter is assigned.

	NOTE: If you specify volume-related commands or parameters for a volume set that is not currently mounted, or for an account that does not exist, MPE/iX returns an error message.

This command may be issued from a session, job, program, or in BREAK. Pressing Break has no effect on this command. Account manager (AM) capability is required to use this command.

To create a new group named GROUP1 (on the system volume set), which will be assigned all default capabilities, enter:

  NEWGROUP GROUP1

To create a new group named G2 in the account GRIMSBY (on the system volume set) and give it process handling (PH) and multiple RINs (MR) capabilities, enter:

  NEWGROUP G2.GRIMSBY; CAP=PH,MR

To create the group LEELA on the nonsystem volume set TIME_LORD, you must use two parallel commands, as follows:

  NEWGROUP LEELA;CAP=IA,BA,PH;HOMEVS=TIME_LORD
  NEWGROUP LEELA;ONVS=TIME_LORD

The first command creates the group on the system volume set, but also informs the system that the files are to reside on another volume set that will be the home volume set for the files.

The second command builds the group on the volume set TIME_LORD.

Limit is the only queue controlling property. The jobs in the queue are sorted by their INPRI. In case of a tie for INPRI, jobs are sorted by their INTRO time. The global limit takes precedence over individual queue limits. That is, even if a jobqueue has a slot available, if the overall limit has been reached, jobs have to wait till one of the jobs finish or the global limit is increased. When a global slot becomes available, the next job is picked from among the eligible jobqueues (those which haven't yet reached their individual limits).The job queues persist across reboots, provided a START RECOVERY is done. Any other system starts will cause the job queues to be deleted and they will have to be created again.This command is available in a session, job, or in BREAK. Pressing [Break] has no effect on this command. This command is not allowed in the SYSSTART file.

SM/OP capability is required to execute this command.

You can use the NEWLINK command to create a link to a file, group, account, or directory.

When newlink represents a path to a symbolic link, the target of that symbolic link is used as the name of the new link that is being created. The NEWLINK command fails if the path represented by linkname points to a file or directory that already exists.

The following table lists all the CI commands that operate on files, groups, accounts, or directories and are affected by symbolic linking. Keep in mind the following data points when using Table 9-3 “CI Commands Affected by Symbolic Links” below:

You can issue the NEWLINK command from a session, job, program, or in BREAK. NEWLINK requires Save Files (SF) capability, Create Directory entry (CD) and Traverse Directory (TD) permissions.

The following tree structure will be used to construct the examples that follow it. Assume that the CWD is /ACCT1/PUB.

               ROOT
         |-
        |       |       |
       ACCT1      dir     SOFTWARE
        |       / \      |
     -   f1 f2  
    |        |      |         |
    PUB      dir1     PUB        CODE
    |      /  \     |         |
  -   file1 file2  ACCTORG  -
  |     |               |   |    |    |
ACCTUDC  FILE3            COMMON TERMIO COMPALL  dir2
                                 / | \
                                f1 f2 dir3

To create a symbolic link named PAYCODE to the file PAYROLL.CODE.SOFTWARE, enter the following command:

  :NEWLINK LINK=PAYCODE; TO=PAYROLL.CODE.SOFTWARE

Or, optionally use the positional parameters and enter:

  :NEWLINK PAYCODE, PAYROLL.CODE.SOFTWARE

You now can access PAYROLL.SAFE.SOFTWARE through PAYCODE. For example, if you have read access to the file PAYROLL.CODE.SOFTWARE, you may enter the following command to print the contents of the file:

  :PRINT PAYCODE

To create a symbolic link named FARFILE in PUB.ACCT1 that references /SOFTWARE/CODE/dir2/f1, enter the following command:

  :NEWLINK LINK=FARFILE; TO=/SOFTWARE/CODE/dir2/f1

Suppose that file COMMON.CODE.SOFTWARE contains information that is used frequently. To display the contents of the file the following command has been used:

  :PRINT COMMON.CODE.SOFTWARE

By creating a symbolic link to the file, you can simplify what users need to type to print it. For example:

  :NEWLINK COMMON, COMMON.CODE.SOFTWARE
 
  :PRINT COMMON

Suppose that a user is currently logged on as USER1 in the group PUB.SOFTWARE. To access the files in /ACCT1/dir1 directory without entering the full path name each time, USER1 may establish a link named "morecode" to that directory as follows:

  :NEWLINK LINK=./morecode; TO=/ACCT1/dir1

Then, to get a list of the files under /acct1/dir1/, the user enters:

  :LISTFILE ./morecode/

Absolute symbolic links

The following command creates FILE3 as a symbolic link to the nonexistent file SOURCE1.CODE.SOFTWARE.

  :NEWLINK LINK=FILE3.PUB.ACCT1; TO=SOURCE1.CODE.SOFTWARE

The following command creates a symbolic link FILE4 as a link to an existing file.

  :NEWLINK LINK=FILE4.PUB.ACCT1; TO=/SOFTWARE/CODE/dir2/f1

The following command creates /ACCT1/PUB/softPUB which points to /SOFTWARE/PUB, which is the group PUB in SOFTWARE account:

  :NEWLINK LINK=/ACCT1/PUB/softPUB; TO=/SOFTWARE/PUB

The following command creates the symbolic link FILE9 as a link to the root directory:

  :NEWLINK LINK=FILE9.PUB.ACCT1; TO=/

Relative symbolic links

The following examples show how to create symbolic links that are relative to the current working directory (CWD). For these examples assume that CWD is /SOFTWARE/CODE/dir2

The following command creates a symbolic link /SOFTWARE/CODE/F1 which points to the file ./f1:

  :NEWLINK LINK=../F1; TO=./f1

The following command creates a symbolic link /SOFTWARE/CODE/F2 which points to the file ./f2:

  :NEWLINK LINK=F2.CODE; TO=./f2

The following command creates the link /SOFTWARE/CODE/dir2/dir which points to the directory ../../../dir:

  :NEWLINK LINK=./dir; TO=../../../dir

If you enter the following command, you will get an error message:

  :NEWLINK LINK=FILE1.PUB.ACCT1; TO=/dir/f1
 
   Duplicate name in directory. (CIERR 906)

Similarly, the following command also generates an error message:

   :NEWLINK LINK=../TERMIO; TO=./f1
 
   Duplicate name in directory. (CIERR 906)

The USERPASS parameter is only available if the HP Security Monitor has been installed.

The account manager uses the NEWUSER command to define an account member. When the user is defined, the account manager may also assign the user a password, a user ID, capabilities, and may limit the user's use of system resources. Parameters defining these values may also be omitted from the command line; in this case, the defaults are assigned the user.

This command may be issued from a session, a job, a program, or in BREAK. Pressing Break has no effect on this command. Account manager (AM) or system manager (SM) capability is required to execute this command.

To define a new user named LHSMITH, assign a password of SMITTY and a home group of