OmniMessaging EMS Operator's Manual 1.8

OmniMessaging EMS Operator’s Guide
Opsol Confidential and Proprietary 76
Cause: Zle adaptor could not write to the temporary file created for retrieving attachment 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>, Could not
write correct len to att Pathmon: \OMNI.$OMNI1
Cause: Zle adaptor could not write exact number of bytes to the temporary file created for retrieving
attachment 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>, No message
found Pathmon: \OMNI.$OMNI1
Cause: While retrieving a message, zle adaptor could not find the message Id specified.
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>, Message to
be forwarded not found Pathmon: \OMNI.$OMNI1
Cause: While forwarding a message using zle adaptor, the message Id specified could not be found.
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>, Original
Message not found Pathmon: \OMNI.$OMNI1
Cause: While retrieving the original message as is without any parsing, zle adaptor could not find the
message Id specified.
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>, Subject of
forwarded message not found Pathmon: \OMNI.$OMNI1
Cause: While forwarding a message, zle adaptor could not parse the subject 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>, Failed while
allocating segment Pathmon: \OMNI.$OMNI1
Cause: Zle adaptor could not allocate memory segment.
Corrective Action: Make sure that the Zle adaptor server process and the client, both are running on the
same CPU to share a memory segment. Else 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>, Failed while
deallocating segment Pathmon: \OMNI.$OMNI1
Cause: Zle adaptor could not deallocate memory segment.
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>, Extended
memory segment too small Pathmon: \OMNI.$OMNI1
Cause: The allocated memory segment is too small to retrieve the message.
Corrective Action: Allocate a bigger extended memory segment in the client invoking 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>, Message with
no header Pathmon: \OMNI.$OMNI1
Cause: While forwarding a message, zle adaptor could not locate 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>, Error while
retrieving message header Pathmon: \OMNI.$OMNI1
Cause: While forwarding a message, zle adaptor could not retrieve the RFC header of the message.
Corrective Action: Contact OmniMessaging support.