OmniMessaging EMS Operator's Manual 1.8

OmniMessaging EMS Operator’s Guide
Opsol Confidential and Proprietary 77
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>, Boundary
string not found Pathmon: \OMNI.$OMNI1
Cause: While forwarding a message, zle adaptor could not retrieve the original boundary string.
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>, Subject of
forwarded message not found Pathmon: \OMNI.$OMNI1
Cause: While forwarding a message, zle adaptor could not retrieve the subject of the forwarded 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 to
be forwarded not found Pathmon: \OMNI.$OMNI1
Cause: While forwarding a message, zle adaptor could not locate the message to be forwarded.
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>, RFC header
could not be parsed Pathmon: \OMNI.$OMNI1
Cause: While retrieving a message, zle adaptor could not parse the RFC 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>, RFC header
not found Pathmon: \OMNI.$OMNI1
Cause: While retrieving a message, zle adaptor could not find the RFC 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>, Mime header
not found Pathmon: \OMNI.$OMNI1
Cause: While retrieving a message, zle adaptor could not find the Mime 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>, RFC Content
type not found Pathmon: \OMNI.$OMNI1
Cause: While retrieving a message, zle adaptor could not find the RFC 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>, Attachment
Content type not found Pathmon: \OMNI.$OMNI1
Cause: While retrieving a message, zle adaptor could not find the content type in the Mime 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>, Attachment
Content subtype not found Pathmon: \OMNI.$OMNI1
Cause: While retrieving a message, zle adaptor could not find the content subtype in the Mime 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>, Attachment
name not found Pathmon: \OMNI.$OMNI1
Cause: While retrieving a message, zle adaptor could not parse the name of the attachment in the Mime
header of the message.