DCE Installation, Configuration, and Management Guide

Managing a DCE Cell
HP NonStop DCE Installation, Configuration, and Management Guide—429552-005
7-3
Problem Prevention
3. Verify that the DCE cell has been started by executing the commands cell ping
and cell show from a dcecp prompt. For example, the se commands indicate
that this cell is behaving normally:
cell ping
DCE services available
cell show
{secservers
/.../dce_cell.domain.company.com/subsys/dce/sec/master}
{cdsservers
/.../dce_cell.domain.company.com/hosts/hostname}
{dtsservers
/.../dce_cell.domain.company.com/hosts/hostname}
{hosts
/.../dce_cell.domain.company.com/hosts/hostname}
4. If any demons in this virtual host are not running, restart them by doing one of the
following:
•
Run /etc/dce_config and select option 3 (START) from the main menu.
•
Execute the /etc/rc.dce.hostname file.
•
From a dcecp prompt, enter the following command :
ksh -c "/etc/rc.dce.hostname"
5. Issue a new dce_login in case your ticket expired.
6. Check for recently created saveabend files, which indicate that DCE programs
have abended. For example, enter the following command at a dcecp prompt:
ksh -c "ls -l $(find /opt/dcelocal.hostname -name ZZSA\* -print)"
7. Enable serviceability debug messages for individual components. For example, for
cdsclerk demons, you can execute the following OSS shell command before
starting the demons:
export SVC_CDS_DBG-cds:*.9:TEXTFILE:/tmp/CDS_OUT
If demons are already running, these messages can be enabled immediately by
executing the log modify command within dcecp. For example:
log modify /.:/hosts/hostman/cds-clerk \
-change {{cds:*.9:TEXTFILE:/tmp/CDS_OUT}}
8. If the DCE library (shared run-time library for the TNS version, user library for the
TNS/R and TNS/E versions) is installed in a location different from its previous
Note. Start a fresh dcecp to avoid having an invalid dce_login shell.