OmniMessaging EMS Operator's Manual 1.8

OmniMessaging EMS Operator’s Guide
Opsol Confidential and Proprietary 74
EMS Message: 03-06-12 02:00:31 \OMNI.$X3H4 TANDEM.NSIM.G06 000202 OMNI Process
ADAPTOR \OMNI.$X3H4 I/O Error: File System Error <error> File Name <filename>, Invalid
forward message flag Pathmon: \OMNI.$OMNI1
Cause: While forwarding a message using zle adaptor, the forward message flag specified was invalid.
Corrective Action: Zle adaptor supports header only or full forward message flags. If unspecified, full
forward message flag is assumed.
EMS Message: 03-06-12 02:00:31 \OMNI.$X3H4 TANDEM.NSIM.G06 000202 OMNI Process
ADAPTOR \OMNI.$X3H4 I/O Error: File System Error <error> File Name <filename>, Message
handle could not be retrieved Pathmon: \OMNI.$OMNI1
Cause: While retrieving a message, zle adaptor could not get the message handle.
Corrective Action: Correct the message Id field in the get IPCs for a valid value.
EMS Message: 03-06-12 02:00:31 \OMNI.$X3H4 TANDEM.NSIM.G06 000202 OMNI Process
ADAPTOR \OMNI.$X3H4 I/O Error: File System Error <error> File Name <filename>, Invalid
password Pathmon: \OMNI.$OMNI1
Cause: While retrieving a message using zle adaptor, the password specified was invalid.
Corrective Action: Correct the password field in the get IPCs for a valid value.
EMS Message: 03-06-12 02:00:31 \OMNI.$X3H4 TANDEM.NSIM.G06 000202 OMNI Process
ADAPTOR \OMNI.$X3H4 I/O Error: File System Error <error> File Name <filename>, Invalid
mailbox name Pathmon: \OMNI.$OMNI1
Cause: While retrieving a message using zle adaptor, the mailbox name specified was invalid.
Corrective Action: Correct the mailbox name field in the get IPCs for a valid value.
EMS Message: 03-06-12 02:00:31 \OMNI.$X3H4 TANDEM.NSIM.G06 000202 OMNI Process
ADAPTOR \OMNI.$X3H4 I/O Error: File System Error <error> File Name <filename>, Invalid
attachment directory Pathmon: \OMNI.$OMNI1
Cause: While retrieving a message using zle adaptor, the OSS attachment directory specified was invalid.
Corrective Action: Correct the attachment directory field in the OMNI_getOSSMessage IPC for a valid
OSS location.
EMS Message: 03-06-12 02:00:31 \OMNI.$X3H4 TANDEM.NSIM.G06 000202 OMNI Process
ADAPTOR \OMNI.$X3H4 I/O Error: File System Error <error> File Name <filename>, Incomplete
original message file name Pathmon: \OMNI.$OMNI1
Cause: While retrieving a message using zle adaptor, the guardian file name specified to retrieve the
original message as is without any parsing was incomplete.
Corrective Action: Correct the original message file name field in the OMNI_getTelMessage IPC for the
format $VOL.SUBVOL.FILENAME.
EMS Message: 03-06-12 02:00:31 \OMNI.$X3H4 TANDEM.NSIM.G06 000202 OMNI Process
ADAPTOR \OMNI.$X3H4 I/O Error: File System Error <error> File Name <filename>, Invalid
original message file name Pathmon: \OMNI.$OMNI1
Cause: While retrieving a message using zle adaptor, the guardian file name specified to retrieve the
original message as is without any parsing was invalid.
Corrective Action: Correct the original message file name field in the OMNI_getTelMessage IPC for the
valid volume/subvolume/file name.
EMS Message: 03-06-12 02:00:31 \OMNI.$X3H4 TANDEM.NSIM.G06 000202 OMNI Process
ADAPTOR \OMNI.$X3H4 I/O Error: File System Error <error> File Name <filename>, Invalid
header buffer size Pathmon: \OMNI.$OMNI1
Cause: While sending message using sendSMTP IPC, the header buffer size specified was invalid.
Corrective Action: Zle adaptor supports header buffer size of 4096 bytes.
EMS Message: 03-06-12 02:00:31 \OMNI.$X3H4 TANDEM.NSIM.G06 000202 OMNI Process
ADAPTOR \OMNI.$X3H4 I/O Error: File System Error <error> File Name <filename>, No message
to be deleted Pathmon: \OMNI.$OMNI1
Cause: While deleting a message using zle adaptor, the message Id specified was already deleted.
Corrective Action: Correct the message Id field in the IPC for the valid value.
EMS Message: 03-06-12 02:00:31 \OMNI.$X3H4 TANDEM.NSIM.G06 000202 OMNI Process
ADAPTOR \OMNI.$X3H4 I/O Error: File System Error <error> File Name <filename>, Process Get
Info failed Pathmon: \OMNI.$OMNI1
Cause: Guardian call for process get info failed.
Corrective Action: Contact OmniMessaging support.