|Main index||Section 3||Options|
The classification argument is the bitwise inclusive OR of zero or one of the manifest constants from each of the classification groups below. The Output classification group is an exception since both MM_PRINT and MM_CONSOLE may be specified.
|MM_PRINT||Output should take place on stderr.|
|Output should take place on the system console.|
|Source of Condition (Major)|
|MM_HARD||The source of the condition is hardware related.|
|MM_SOFT||The source of the condition is software related.|
|MM_FIRM||The source of the condition is firmware related.|
|Source of Condition (Minor)|
|MM_APPL||The condition was detected at the application level.|
|MM_UTIL||The condition was detected at the utility level.|
|MM_OPSYS||The condition was detected at the operating system level.|
|The application can recover from the condition.|
|MM_NRECOV||The application is unable to recover from the condition.|
Alternatively, the MM_NULLMC manifest constant may be used to specify no classification.
The label argument indicates the source of the message. It is made up of two fields separated by a colon (‘:’). The first field can be up to 10 bytes, and the second field can be up to 14 bytes. The MM_NULLLBL manifest constant may be used to specify no label.
The severity argument identifies the importance of the condition. One of the following manifest constants should be used for this argument.
|MM_HALT||The application has confronted a serious fault and is halting.|
|MM_ERROR||The application has detected a fault.|
|MM_WARNING||The application has detected an unusual condition, that could be indicative of a problem.|
|MM_INFO||The application is providing information about a non-error condition.|
|MM_NOSEV||No severity level supplied.|
The text argument details the error condition that caused the message. There is no limit on the size of this character string. The MM_NULLTXT manifest constant may be used to specify no text.
The action argument details how the error-recovery process should begin. Upon output, fmtmsg() will prefix "TO FIX:" to the beginning of the action argument. The MM_NULLACT manifest constant may be used to specify no action.
The tag argument should reference online documentation for the message. This usually includes the label and a unique identifying number. An example tag is "BSD:ls:168". The MM_NULLTAG manifest constant may be used to specify no tag.
fmtmsg(MM_UTIL | MM_PRINT, "BSD:ls", MM_ERROR, "illegal option -- z", "refer to manual", "BSD:ls:001");
BSD:ls: ERROR: illegal option -- z TO FIX: refer to manual BSD:ls:001
The same code, with MSGVERB set to "text:severity:action:tag", produces:
illegal option -- z: ERROR TO FIX: refer to manual BSD:ls:001
In order for fmtmsg() to output to the system console, the effective user must have appropriate permission to write to /dev/console. This means that on most systems fmtmsg() will return MM_NOCON unless the effective user is root.
|FMTMSG (3)||August 5, 2002|
|Main index||Section 3||Options|
|“||On two occasions I have been asked [by members of Parliament], 'Pray, Mr. Babbage, if you put into the machine wrong figures, will the right answers come out?' I am not able rightly to apprehend the kind of confusion of ideas that could provoke such a question.||”|
|— Charles Babbage|