OmniMessaging EMS Operator's Manual 1.8

OmniMessaging EMS Operator’s Guide
Opsol Confidential and Proprietary 78
Corrective Action: Contact OmniMessaging support.
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>, Text/Plain
Content type not found Pathmon: \OMNI.$OMNI1
Cause: While retrieving a message, zle adaptor could not parse the Text/Plain content type in the header
of the message.
Corrective Action: Contact OmniMessaging support.
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>, Encoding
type not found Pathmon: \OMNI.$OMNI1
Cause: While retrieving a message, zle adaptor could not find the encoding type in the header of the
message.
Corrective Action: Contact OmniMessaging support.
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>, Section Body
not found Pathmon: \OMNI.$OMNI1
Cause: While retrieving a message, zle adaptor could not find the body of a section of the message.
Corrective Action: Contact OmniMessaging support.
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 Text
not found Pathmon: \OMNI.$OMNI1
Cause: While retrieving a message, zle adaptor could not find the message body text.
Corrective Action: Contact OmniMessaging support.
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>, Unknown text
encoding type Pathmon: \OMNI.$OMNI1
Cause: While retrieving a message, zle adaptor could not decode the message body text.
Corrective Action: The message body text encoding type is not supported. Try to compose a message
with supported encoding types and then retrieve it using zle adaptor. Else contact OmniMessaging support
to enhance the zle adaptor.
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>, HTML Text
not found Pathmon: \OMNI.$OMNI1
Cause: While retrieving a message, zle adaptor could not find the HTML text.
Corrective Action: Contact OmniMessaging support.
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>, Attachment
name could not be decoded Pathmon: \OMNI.$OMNI1
Cause: While retrieving a message, zle adaptor could not decode the attachment name.
Corrective Action: Contact OmniMessaging support.
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>, Attachment
could not be decoded Pathmon: \OMNI.$OMNI1
Cause: While retrieving a message, zle adaptor could not decode the attachment.
Corrective Action: Contact OmniMessaging support.
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>, Empty message
found Pathmon: \OMNI.$OMNI1
Cause: While retrieving the WAP encoded message, zle adaptor found the empty message.
Corrective Action: Contact OmniMessaging support.
EMS Message: 03-06-12 02:00:31 \OMNI.$X3H4 TANDEM.NSIM.G06 000202 OMNI Process