Openview::Message::opcmsg - Perl extension for sending OpenView messages.

   #low level access to the opcmsg API:
   use Openview::Message::opcmsg ;
   opcmsg( OPC_SEV_MINOR 
          ,'application' 
          ,'object' 
          ,'msg_text' 
          ,'msg_group' 
          ,hostname 
         );

Openview::Message::opcmsg provides low level access to the HP OpenView Operations opcmsg() library API. This enables perl scripts to send Openview messages without having to use system() calls or fork sub- processes which is much more efficient than using the opcmsg command.

The following symbols are exported by default:

   opcmsg
   OPC_SEV_NORMAL
   OPC_SEV_WARNING
   OPC_SEV_MINOR
   OPC_SEV_MAJOR
   OPC_SEV_CRITICAL

The following symbols may attitionally be imported, but are probably not very useful:

   OPC_SEV_UNKNOWN
   OPC_SEV_UNCHANGED
   OPC_SEV_NONE

Openview::Message::Sender for an OO interface to this function, which does not export symbols into the user's namespace.

Apparently, the HP Openview library is "not fork-safe". This creates problems for forking servers. A work-around for this is to 'pre-fork' an opcmsg server that implements this function, and have your forking servers send it messages.

Alternatively, you can set CLI_MESSAGE_SENDER=1 in your environment, we this module will use the CLI interface instead.

HP refused to offer support to the author's employer for linking with opcmsg() on their own platforms (HP), so we fake it with Openview::Message::cliopcmsg.

Lincoln A. Baxter <lab@lincolnbaxter.com>