OSF DCE Problem Determination Guide

OSF DCE Problem Determination Guide
use a correct specification for the routing. A correct specification for routing must have
the form severity:how:where[:private]. The severity must be one of the following:
FATAL
ERROR
WARNING
NOTICE
NOTICE_VERBOSE
The how field must be one of the following:
BINFILE
TEXTFILE
FILE
DISCARD
STDOUT
STDERR
The where field is a filename, that may contain a %ld string, that is replaced by the
process ID of the currently running process. The private field is optional. It is of the form
[dir_id,]gds_components.. dir_id is optional and specifies the directory ID for which the
routing specification string is designated. gds_components is a comma separated list of
components of the Global directory service. It must be one of the following:
monitor
cache
cstub
sstub
dsa
0x1260a0ec GDS_S_ROUTINGS_ERR
Severity: Warning Component: gds / GDS_S_GENERAL
Text: A call to dce_svc_routings has failed, error status = %lx.
Explanation: The program could not determine the actual setting of the serviceability
routing specification. The function has set the specified status.
Action: Look up the error status in dcesvcmsg.h. Currently there are no error states
defined.
0x1260a57d GDS_S_ROVERFLOW_ERR
Severity: Warning Component: gds / GDS_S_GENERAL
Text: An ROS-association table overflow was detected (max. no. of entries = %d)
Explanation: Stub process could not find an empty ROS-association table entry
Action: If required, the no. of ROS-association table entries can be increased by starting
the Stub process with the -R switch.
0x1260a44f GDS_S_RPC_BINDINFO
2− 326 Tandem Computers Incorporated 124330