OmniMessaging EMS Operator's Manual 1.8

OmniMessaging EMS Operator’s Guide
Opsol Confidential and Proprietary 73
Corrective Action: Contact OmniMessaging support.
EMS Message: 02-03-23 17:23:21 \OMNI.$Z6SV TANDEM.NSIM.G06 000202 OMNI Process
ADAPTOR \OMNI.$Z6SV I/O Error: File System Error <error> File Name <filename>, MTP_Reply failed.
Pathmon: \OMNI.$OMNI5
Cause: Interprocess communication failed.
Corrective Action: Contact OmniMessaging support.
EMS Message: 02-03-23 17:23:21 \OMNI.$Z6SV TANDEM.NSIM.G06 000202 OMNI Process
ADAPTOR \OMNI.$Z6SV I/O Error: File System Error <error> File Name <filename>, Error in
AWAITIOX Pathmon: \OMNI.$OMNI5
Cause: AWAITIOX call did not complete successfully.
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>, Invalid
originator DSN flag Pathmon: \OMNI.$OMNI1
Cause: While sending or forwarding a message using zle adaptor, the originator DSN flag specified was
invalid.
Corrective Action: Correct the originator DSN flag field in the send or forward IPC. Zle adaptor supports
values from the ADAPT_OrigDSN enum specified in the ADAPTH header file.
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
recipient DSN flag Pathmon: \OMNI.$OMNI1
Cause: While sending or forwarding a message using zle adaptor, the recipient DSN flag specified was
invalid.
Corrective Action: Correct the recipient DSN flag field in the send or forward IPC. Zle adaptor supports
values from the ADAPT_RcptDSN enum specified in the ADAPTH header file.
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
return path address Pathmon: \OMNI.$OMNI1
Cause: While sending or forwarding a message using zle adaptor, the return path address specified was
invalid.
Corrective Action: Correct the return path address field in the send or forward IPC according to the
RFC822 format.
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
originator address Pathmon: \OMNI.$OMNI1
Cause: While sending or forwarding a message using zle adaptor, the originator address specified was
invalid.
Corrective Action: Correct the originator address field in the send or forward IPC according to the
RFC822 format.
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 count Pathmon: \OMNI.$OMNI1
Cause: While sending or forwarding a message using zle adaptor, the number of attachments specified
was invalid.
Corrective Action: Zle adaptor supports maximum 10 attachments. Try to compose a message with up
to 10 attachments and correct the attachment count field in the send or forward IPC for a limit of 10.
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
subject length Pathmon: \OMNI.$OMNI1
Cause: While sending or forwarding a message using zle adaptor, the length of the subject field specified
was invalid.
Corrective Action: Zle adaptor supports subject of maximum 255 chars. Try to compose a message with
subject length up to 255.