OSF DCE Problem Determination Guide

STDOUT Messages are written as human-readable text to standard output

STDERR Messages are written as human-readable text to standard error

GOESTO Messages are sent to the destination designated for the speciﬁed

severity level

Messages of different severity levels can be routed differently. For example, all

"Notices" could be discarded and all "Fatal" errors could be written to a binary log.

BINFILEs can be read and manipulated with the following set of logﬁle functions:

dce_svc_log_open() Opens a logﬁle for reading.

dce_svc_log_get( ) Reads the next entry from the logﬁle.

dce_svc_free_entry() Frees the logﬁle space of the current entry.

dce_svc_log_rewind( ) Returns log processing back to the ﬁrst message.

dce_svc_log_close( ) Closes the open logﬁle.

For detailed information about the logﬁle functions, see the reference pages.

1.2.2 UsingEnvironment Variables

You can also route messages based on severity by using the environment variables:

• SVC_FATAL

• SVC_ERROR

• SVC_WARNING

• SVC_NOTICE

• SVC_NOTICE_VERBOSE

1.2.3 Usingdce_svc_routing

Message routing can be set up by the application itself, by calling the dce_svc_routing()

routine and passing to it a string formatted in the same way as a line of text from a

routing ﬁle. The routine must be called for each severity level being set.

1.2.4 UsingAttributes

The ﬁnal two routing methods allow for limited routing. Routing can be speciﬁed by

attribute, either in the message deﬁnition in the sams ﬁle, or as part of the argument list

to dce_svc_printf( ) routine.

1− 4 Tandem Computers Incorporated 124330