MQSeries.net :: View topic

sgiles

Hi,

FTE does not have an agent on VMS. To transfer files to those servers we have built a Windows server with a SAMBA share to the VMS file system. We then crate FTE transfer wher the destination agent is the windows server and the destinaiton file is the samba share on the windows agent.

The majority of transfers to the SAMBA share are sucessful but occasionally there is a momentary problem in SAMBA and the transfer fails. If we issue the same transfer a short time later the transfer completes successfully.

We have been able to use the DestinationTransferEndExit routine and identify transfers that fail with the specific SAMBA error. What we want to do is to automatically re-attempt those transfers that fail.

It is my understanding that once a transfer has failed it is finished and another attempt is only possible via a re-submission.
The problem we have is there are many different source systems and they submit their transfers as a fire-and-forget. It is not possible to automate the re-submission at every source system; It is best that any re-submission is done at the destination windows server.

As we can detect the error in the DestinationTransferEndExit it makes sense to re-submit the transfer from within that routine. TheExit routine has access the source agent name, dest agent name, source file spec, dest file spec and meta data. Unfortunately it does not seem to have the source or destination queue manager name. Without this information we cannot completely rebuild the transfer request. All our FTE requests use the "agent@QM" to specify the source or targets.

Is there a way to get the source and destination queue manager name from within the FTE exit?

Is there a way we can get a failed transfer to be retried?

Thanks
Stephen