 |
» |
|
|
|
System administrators should be aware of the following considerations concerning MPE/iX at Release 4.5 and 5.0: - Syntax
The HPPATH system variable does not accept HFS
pathnames. Consequently, you cannot include HFS pathnames in the default search path for a session. Remote file access does not support HFS syntax.
- Directories
The following types of files can be located only within MPE
groups; they cannot be located within HFS directories: Compatibility mode files (for example, CIR, KSAM, RIO)
- Security
ACDs are automatically assigned to HFS directories and
files residing within those directories. Also, directories
and files in root or accounts.
You cannot assign ACDs to the root directory, MPE
accounts, or MPE groups.
Successful logon for users without SM capability requires
valid UID and GID entries in the user and group databases.
By default, any user can create files in the /tmp
directory. This directory is automatically created when you
update to Release 4.5 or 5.0. While this behavior is
desirable for POSIX-based applications, some system managers
may want to restrict access to this directory.
- Commands
Frequently used MPE commands directly support HFS syntax, some do not.
The HELLO and JOB commands only log on to a group.
The FILE command allows HFS pathnames only on the
right side of the equation.
You should use the DISKUSE command instead of the
REPORT command to report on disk usage of HFS
directories that exist outside groups and accounts.
- Groups
Databases are supported only in MPE groups.
Compatibility mode files can reside only in MPE groups.
- Accounting
MPE account or group-level accounting does not extend to
directories residing outside of accounts.
System management tasks remain essentially the same with
Release 5.0. Tasks such as system startup and shutdown,
system configuration, system logging, adding user accounts
and groups all work the same with some minor enhancements to
access HFS features. By default, existing MPE/iX commands
and intrinsics assume MPE syntax. You must deliberately
activate new features to use them.
|