Serviceability messages can be written to any of the normal output destinations. Routing for serviceability messages can be specified in any of three different ways (in ascending order of precedence):
1. By the contents of a routing file
2. By the contents of a routing environment variable
3. By calling the dce_svc_routing( ) routine (often as part of processing an application's command-line arguments)
Additional routing (that is, in addition to whatever routing has been specified by the means described) of a message to standard error can be performed in either of the following two ways:
· By specifying the routing as one of the message's attributes (in the sams file definition of the message)
· By specifying the attribute in the call to dce_svc_printf( ) (or other serviceability output routine) to generate the message
Routing a message actually consists of specifying two things:
· How the message should be processed (the form it should be put in)
· Where the message should be sent (its destination)
The two specifications are sometimes closely interrelated, and sometimes specifying a certain destination implies that the message must be put into a certain form. This fact allows certain combinations of processing and destination to be abbreviated.
In the following topics, each of the ways to route serviceability messages is described.
Note that debug messages are routed by a similar, but slightly different, technique. For a full description, see Using Serviceability for Debug Messages .
More:
Routing by Environment Variable
Calling dce_svc_routing( ) to Set Routing
Additional Routing by Attribute