OSF DCE Application Development Guide--Core Components

Using the DCE Serviceability Application Interface
main is the name of the subcomponent, specified in quotes.
hel_i_svc_main is a name that will be used (later on in the file) to identify a
message that describes the subcomponent.
(Note that sams assigns values to all of these indexes automatically.)
The third (and final) part of the sams file consists of a series of records that specify the
messages themselves. Each record is delimited by the start and end keywords. Within
each record, a series of keywords identifies the various information that each message
consists of or has associated with it.
Our file will contain only one message, the text of which is to be ‘‘Hello World’’. The
record that specifies it is as follows:
# Part III
start
code hel_s_hello
subcomponent hel_s_main
attributes "svc_c_sev_notice | svc_c_route_stderr"
text "Hello World"
explanation "A short informational greeting"
action "None required."
end
The keywords specified have the following meanings:
start Marks the beginning of a message definition. This keyword can
optionally be followed by various values.
• A number following the keyword specifies that the ID that is
generated by sams for the message should be based on
(number multiplied by 100). This allows the ID numbers of
messages that belong to the same subcomponent of an
application to be in the same numerical subseries
(collection), even if additional messages for subcomponents
have to be added later on. If each subcomponent’s first
message is started with a collection number that allows for
enough extra ID space in the previous subcomponent to
accommodate a reasonable number of future additional
definitions, then each subcomponent’s ID series will be able
to maintain its unbroken series.
As mentioned, the default size of a collection number is 100.
Thus, the following collection specification is interpreted as
‘‘200’’:
start 2
124245 Tandem Computers Incorporated 4−5