Preparation
The fax is prepared as usual on the originating system and reaches the originating COPIAFACTS node for transmission.
On detecting the matched destination by checking the ACTION_CODES content, the transmission is suppressed and instead a single TIF is saved in the specified delivery folder.
The originating FS file is saved in a folder named RDFSFILES in the CALLBACK folder, and a message labeled with the FS filename and containing the FS content is written to the RD_OUT queue.
Transfer for Delivery
A user-provided application receives the RD_OUT message containing the FS content. It then forwards it to a selected delivery system node along with the TIF name derived from the message label.
After forwarding the message the TIF should be removed from the delivery folder.
Collection for Delivery
A user-provided application makes the TIF available for processing in a delivery folder on the delivery system and forwards the incoming message to a RD_IN queue consumed by one or more delivery nodes.
The message should not be forwarded to a delivery node until the TIF is known to be available for delivery by the delivery node.
Delivery Completion
On completion of a delivery attempt, a message is written to the RD_OUT queue containing an updated copy of the original FS content, with attempt information added. The temporary FS content used on the delivery node will be optionally recorded in a trace file for diagnostic purposes, and the faxable TIF is left in the delivery folder. It can be deleted from there using CFHK on the delivery system.
Transfer of Delivery Results
A user-provided application receives the RD_OUT message containing the FS content on the delivery system. It then forwards it to the originating system from which it originated.
Delivery Results Processing
Messages in the RD_IN queue on an originating node are handled as fax FSQ messages, but the fax processing is skipped. Instead the outcome code from the last attempt record is processed to determine the outcome. One of three actions is then taken:
•For a successful transmission, the matching file in the RDFSFILES folder is deleted and the incoming FS content is saved as an FS file in the SENT folder. A NQ_FAX_COMPLETE message is sent to the notify queue.
•For a failed transmission, the matching file in the RDFSFILES folder is deleted and the incoming FS content is saved as an FS file in the FAIL folder. A NQ_FAX_COMPLETE message is sent to the notify queue.
•For a retry, the matching file in the RDFSFILES folder is deleted and the incoming FS file is placed in the appropriate TOSEND folder. A NQ_FAX_ATTEMPT message is sent to the notify queue if specified.
The NQ messages sent, if any, are as specified for the originating system.
If a retry has been specified, the FS file will be picked up in the usual way and will be reselected for remote delivery after the specified delay time.
