HP R4.2 logMsg, logMsg, logEvent, logEvent, logEvent, logDstPri, logEvent/logMsg, A Summary of Commands, /usr/spool/log/msgDst.rules

A Summary of Commands logEvent/logMsg

generates messages within the logging system, but which always uses SYSMSG as the message format for the messages it generates. The logEvent command emulates the logEvent( ) library routine, while the logMsg command emulates the logMsg( ) library routine.

The logEvent command requires a destination and a priority when it is called. Messages logged via this interface are explicitly logged to the specified destinations and at the specific priority.

The logMsg command does not take a destination mask or a priority. It gets these pieces of information from the logging destination and a priority shared memory maintained by the logDstPri command via the /usr/spool/log/msgDst.rules file.

Both logEvent and logMsg require that the proper number of arguments be supplied for the specified message and that numeric arguments in the message format match pure numbers from the argument list. For example:

GEN012 OUT_OF_RANGE %D<<value,D>> is out of range \ for %s<<arg,S>> in %s<<routine,S>>.

This format requires that the first argument be a number, therefore,

logMsg XXX LG_OUT_OF_RANGE -- yes var compute

will fail because “yes” is not a number, while

logMsg XXX LG_OUT_OF RANGE -- 10 var compute

will not fail.

UCS 1000 R4.2 Administration 585-313-507 Issue 3 April 2000 523