States of a FileReceived scenario

Notes:
- Note1
- The MSIF transfer service received a negative response to its fetch request due to an unrecoverable error, for example, because the SAG is not subscribed or because there is no SnF session with the specified ID.
- Note2
- The received request primitive is not authorized by the RM data.
- Note3
- The file transfer did not begin within a timeout period equal to three times the request expiration period.
- Note4
- This state transition is possible only for an SnF file transfer for which a request primitive with a PDMHistory indication was received.
| Transfer State | Description | Recovery of inError condition |
|---|---|---|
| Initial | The MSIF transfer service received a FileAct request and initiated a FileReceived scenario. | |
| FetchRequested | The MSIF transfer service sent a request to
fetch a file that was sent in SnF delivery mode, and is waiting for
the corresponding response. The MSIF transfer service sets the
transfer condition to inError in the following situations:
|
auto |
| Responded | For a real-time file transfer, the MSIF Transfer Service sent a response indicating that it received the file transfer request. For an SnF file transfer, the MSIF transfer service received a positive response to its request to fetch a file. | |
| Accepted | The MSIF transfer service accepted the file transfer request, and the file transfer has begun. | |
| FileReceived | The SAG received the file from the counterpart. The MSIF transfer service sets the transfer condition to inError if it encounters an error moving the received file from the SAG to the host file system. |
manual |
| TransferComplete | The transfer is complete. The MSIF transfer service sets the transfer
condition to inError in the following situations:
|
manual |
| DelivComplete | The received file was delivered with the completion code Ok. | |
| DelivWarning | The received file was delivered with the completion code PartialOk, for example, because it is a possible duplicate. | |
| DelivFileInError | The received file was delivered with the completion code Failed. | |
| Invalid | The inbound request is invalid and cannot be processed. The MSIF transfer service sent a response to the counterpart. | |
| Error | The attempt to send a response to the counterpart failed. | |
| Rejected | One of the following errors occurred:
|
|
| Duplicate | The MSIF transfer service sends a response to the counterpart indicating that the file was already sent. | |
| Aborted | A user aborted the attempt to receive the file. | |
| Failed | The attempt to receive the file from the counterpart
(for a real-time transfer) or the SIPN (for an SnF transfer) failed. The MSIF transfer service sets the transfer condition to inError if it receives, from the SIPN, a File Transfer event indicating that the file transfer for an SnF transfer failed. |
auto (for an SnF transfer) |


Notes:
- Note1
- Either:
- An unrecoverable error occurred.
- A recoverable error occurred, and none of the automatic recovery attempts were successful.
- Note2
- A delivery notification response that was flagged as being a possible duplicate message (PDM) was received.
| Notification State | Description | Recovery of inError condition |
|---|---|---|
| None | No notification was sent. If the MSIF Transfer Service encounters an IBM MQ error while sending the SNL request primitive for a real-time delivery notification, it sets the transfer condition to inError. |
manual (for a real-time transfer) |
| Sent | A delivery notification request was sent. The
MSIF transfer service sets the transfer condition to inError in the
following situations:
|
manual (for a real-time transfer), auto |
| Failed | A delivery notification request was sent, but a response was not received within the configured timeout period for SNL primitives. This notification state applies only to SnF transfers. | |
| Complete | A delivery notification response was received. |