Each MSIF transfer service is implemented as IBM® Integration Bus message flow
that is called as the service it implements, DNF_O_FT, DNF_O_FT1, DNF_O_FT2 and DNF_O_FT3. The flows
read messages from five input queues that are dedicated to a particular purpose:
prefix.DNF_O_FTx
For application request messages sent by the customer application to issue a new transfer
scenario.
prefix.DNF_O_FTUMHx
For application response messages replied by the customer application to continue a transfer
scenario.
prefix.DNF_O_FTTMHx
For messages received from the SAG.
prefix.DNF_O_FTTMLx
For internal messages sent by the MSIF transfer service to itself to trigger an internal
processing step.
prefix.DNF_O_FTIOx
For internal messages sent by the MSIF transfer service to itself to trigger a file I/O
operation.
Each flow contains a controlled input node (CIN) that coordinates reading messages from the
five input queues to that service. If an MSIF transfer service encounters a database error or
program error that prevents the service from processing the message in a meaningful sense, it rolls
back the current transaction and routes the message to an error queue. If an MSIF transfer service
detects that the same error occurs for several messages, it stops the CIN so it does not read
messages from the input queue. For more information on error handling done by the CIN, see Error queue. An MSIF transfer service has two input queues to control the CIN in
such error situations:
prefix.DNF_O_FTRSTx
For commands issued by an FTM SWIFT operator by means of the CLI to
control the CIN, for instance to start reading messages from the input queues of the MSIF transfer
service when the CIN has stopped reading messages.
prefix.DNF_O_FTERRx
Messages that the MSIF transfer service failed to process in a meaningful way.
Figure 1. MSIF transfer service.
The following entities are specific to one particular MSIF transfer
service. If you are using more than one DNF_O_FTx service,
you must use a separate entity of that type:
SAG message partner option-set and the corresponding message partner
configured in the SAG
SnF queue configured at SWIFT and the corresponding SnF output
channels
SnF queue configured at SWIFT and the corresponding SnF queue
option-set use to acquire an SnF queue session
SnF input channel
Service interface and input queues
Subscriptions to receive from an SAG FileAct events or Queue events.
For more information on subscriptions to SNL events, see Subscriptions to SNL events
