DCE for the HP e3000 (B3821-90002)

General Information
DCE/3000 versus DCE/9000: Differences
Chapter 1
21
DCE/3000 versus DCE/9000: Differences
It is assumed that readers have the basic understanding of the differences between
MPE/iX POSIX environment and a UNIX based system environment. This section is
intended to give end users some key concepts on their first exposure to DCE/3000.
File Naming Convention
The traditional MPE directory structure is made up for a three-level hierarchy and
names for those accounts, groups, and files are all upshifted. The addition of POSIX
functionality to MPE/iX makes it possible for DCE programs and utilities to have the
same name and location as they are used on an HP 9000. While those DCE programs can
be executed in the MPE shell environment, a similar MPE name is also available from
the MPE CI environment. Table 1-6 lists some examples of the similarities in names.
Managing DCE Daemons
The DCE daemons (rpcd, secd, cdsd, and so on) are run as MPE/iX jobs that log on as
manager.sys. If passwords are required, you are prompted for them.
It is important to set the job limit high enough so that all the DCE daemons can logon.
For better performance, these daemons should run in the CS queue. Be sure to issue the
jobpri cs command at startup, to allow these jobs to run in the C queue.
Security and Remote Login Utilities
You can use standard MPE remote login commands to perform remote DCE cell
administration; there are no DCE-integrated MPE/iX login utilities. However, this
exposes the cell administrator’s password to network attackers whenever you perform a
task on a remote system. If a network attacker obtains the password, the security of the
cell's DCE services is compromised. The most secure way to perform the cell
administration is to log in locally to each system you need to administer.
Table 1-6 DCE Program Name Comparisons
Shell MPE CI
acl_edit ACLEDIT
rgy_edit RGYEDIT
dce_login DCELOGIN
sec_admin SECADMIN
klist KLIST
rpccp RPCCP
cdscp CDSCP