We are passing transactions from the mainframe in a fixed length format.
These messages are send via MSMQT.  If we have a pipeline in the Receive
Location and the mapping fails (maybe one too many characters were
included), we get an error, but where is our message?

We are finding that the message is gone (not in HAT) and no WMI events get
fired.  There is something sent to the Event Viewer, but with the error
message, we don't know the root cause of the error.

Now I have seen blogs that state we could send to MSMQT with passthrough,
then the message would be stored in the MessageBox.  We could then subscribe
with a send port, process the message and receive all appropriate error
messages with a message in HAT.  This seems like a real work around, but is
this the only way to get the message if it fails in a pipeline?

Any help would be appreciated.
Mike Holdorf

[ Post a follow-up to this message ]

MSMQT receiver does not suspend the message if the pipeline execution
fails.
Hence the message does not appear in HAT (as it was never suspended).
The error message in the event log is what has the complete information of
the failure.  There is no other extra information of the failure that is
stored anywhere else.
sorry. 


| >>We are passing transactions from the mainframe in a fixed length format.
| >>These messages are send via MSMQT.  If we have a pipeline in the Receive
| >>Location and the mapping fails (maybe one too many characters were
| >>included), we get an error, but where is our message?
| >>
| >>We are finding that the message is gone (not in HAT) and no WMI events
get
| >>fired.  There is something sent to the Event Viewer, but with the error
| >>message, we don't know the root cause of the error.
| >>
| >>Now I have seen blogs that state we could send to MSMQT with
passthrough,
| >>then the message would be stored in the MessageBox.  We could then
subscribe
| >>with a send port, process the message and receive all appropriate error
| >>messages with a message in HAT.  This seems like a real work around,
but is
| >>this the only way to get the message if it fails in a pipeline?
| >>
| >>Any help would be appreciated.
| >>Mike Holdorf
| >>
| >>
| >>

This posting is provided "AS IS" with no warranties, and confers no rights.

EBusiness Server Team

[ Post a follow-up to this message ]