CORBA 2.3.3 Administration Guide (NonStop CORBA 2.3.7+)

PATHCOM lets you verify the current configurations of NonStop CORBA runtime processes.●
The NonStop CORBA error log is the primary source of information about NonStop CORBA execution
errors. A variable in the NonStop CORBA configuration file controls the error logging.
●
The NonStop CORBA trace facility lets you follow the flow of control in an application to discover when
and where an error occurred. Each component has a variable in the configuration file that controls the
tracing for that component.
●
SCF lets you verify the configuration of networking resources, validate addressing information, discover
recurrent errors, and obtain line traces and protocol traces.
●
The Ptrace utility helps you to interpret SCF traces.●
The Event Management Service (EMS), which has several interactive and programmatic interfaces, helps
you capture and integrate the error information reported by different processes including TS/MP, NonStop
TM/MP, the operating system, and the networking services. See the EMS Manual for descriptions of the
EMS interfaces.
●
What You Need to Know
To manage the NonStop CORBA runtime environment, you should be familiar with the following topics:
Procedures and considerations for managing TS/MP subsystems●
Procedures and considerations for managing NonStop TCP/IP, Parallel TCP/IP, LAN, QIO, and X25AM●
Syntax and use of the following utilities:
PATHCOM interface●
Subsystem Control Facility (SCF)●
Configuration Tool●
NonStop CORBA error log facility●
NonStop CORBA trace facility●
Ptrace●
Event Management Service (EMS)●
●
Format and semantics of the following files:
OSS Profile file●
Initialization file (default.db)●
PATHCOM configuration file (nsdstart)●
SCF configuration file●
TCP/IP HOSTS file or DNS boot and domain data files●
●
The following manuals provide information about managing NonStop Himalaya systems:
Document Title Notes