HP-UX Reference (11i v1 00/12) - 1M System Administration Commands N-Z (vol 4)
__________________________________________________________________________________________________________________________________________________________________________________________________
__________________________________________________________________________________________________________________________________________________________________________________________________
STANDARD Printed by: Nora Chuang [nchuang] STANDARD
/build/1111/BRICK/man1m/naaagt.1m
________________________________________________________________
___ ___
p
pddcesetup(1M) pddcesetup(1M)
(TO BE OBSOLETED)
NAME
pddcesetup - configure DCE for the HPDPS
SYNOPSIS
pddcesetup [force]
DESCRIPTION
The pddcesetup command is used to configure DCE information for the HP Distributed Print Service
(HPDPS).
pddcesetup must be run on each HP-UX host in your DCE cell that will execute the HPDPS in the
Extended Environment. If a host will run the HPDPS in the Basic Environment only, not in the Extended
Environment, then execution of pddcesetup is not needed on that host. If you do not intend to execute
the HPDPS in a DCE cell, or do not wish to use DCE services in conjunction with the HPDPS, then each
host must execute the HPDPS in the Basic Environment, and execution of pddcesetup is not needed on
any of the hosts in your network. pddcesetup must be executed once on each host in your DCE cell that
will execute an HPDPS client daemon, spooler, or supervisor in the Extended Environment.
pddcesetup must be executed before starting any of these HPDPS components on that host.
The first time that pddcesetup executes in your DCE cell, it will prompt for and create various DCE
security identities and CDS namespace entries that are then configured for the entire cell. On subsequent
executions of pddcesetup , only local information needed by the local host is configured; the DCE secu-
rity identities and CDS namespace entries have already been created for the cell.
If the parameter force is given, then pddcesetup will give you the option to fully recreate security
identities and CDS directories. This option is useful if DCE has been only partially configured, or if
configuration is accidentally removed after creation. If the force parameter is not given, then
pddcesetup quickly checks to see if it appears the DCE information has already been configured, and if
so, pddcesetup does not attempt to configure any of this information.
The host on which pddcesetup is executed must already be configured as a DCE client or server, using
DCE command-line utilities or the SAM program. You must also be DCE logged in using an account with
sufficient administrator privileges to modify DCE security and namespace information. The DCE login of
the cell administrator for your cell is normally used for this purpose (the default DCE login name is
cell_admin).
The HPDPS DCE information created by pddcesetup is:
• Accounts adm_user and pd_server.
• Principals adm_user and pd_server.
• Groups pd_admin and pd_operator.
• CDS namespace directories and links.
• Initial Access Control List entries.
• Local key table entries for principal pd_server.
EXAMPLES
An example execution follows. This example illustrates the execution of pddcesetup for the first time in a
DCE cell.
# pddcesetup
Checking whether your host is configured in a DCE cell.
Verifying your DCE login.
You are DCE logged in as <your login>.
Checking whether HPDPS security identities have already been configured
in your cell.
DCE security identities needed for the HPDPS have not yet been
configured in your DCE cell. The security identities that must be
configured are:
Accounts adm_user and pd_server
Principals adm_user and pd_server
Groups pd_admin and pd_operator
HP-UX Release 11i: December 2000 − 1 − Section 1M−−631
___
___