To operate the FMT FIN processing, a user with the DnfFmtOperator
role issues, to the service DNF_PF_CMD, the commands described in
Table 1.
Table 1. FMT FIN operation tasks
| Operation task |
Command |
| Enable an LT to send FMT FIN messages |
fmtenable |
| Start the sending and receiving of FMT FIN messages
by an LT |
fmtstart |
| Display information about FIN messages processed
by the FMT FIN service |
query |
| Recover FIN messages that were processed by
the FMT FIN service but that failed to be routed to their destinations |
recover |
| Stop the sending and receiving of FMT FIN messages
by an LT |
fmtstop |
| Disable an LT from sending FMT FIN messages |
fmtdisable |
Reset the input or output sequence counter of
an LT to a particular value, stop FMT FIN processing for that LT Note: To
prevent DB2® insertion errors,
before you reset the input or output sequence counter of an LT it
is imperative that:
- The DNF_IAMS table is empty
- The DNF_OAMS table contains no messages that are in process
- The DNF_MSGS table is empty
To achieve this:
- Stop all traffic (both SIPN FIN and FMT FIN) to and from the LT.
- Wait until the LT finishes processing all FIN messages. To check
this, periodically issue the query command with the query option m to
the DNF_ILC_CMD service. For example, the response to the following
command indicates that no OAMS messages are in process, but that the
IAMS still contains 2 messages, and therefore is not yet empty:
INST1.BANKA.DNF_ILC_CMD>query -lt XXXXUSNYA -qo m
DNFH3555I Outbound messages in OAMS for LT 'XXXXUSNYA':
APC: queued= 0, in process= 0, acknowledged= 0
FIN: queued= 0, in process= 0, acknowledged= 2
Inbound messages in IAMS for LT 'XXXXUSNYA': 2
- After the IAMS is empty and the OAMS contains no in-process messages,
delete the contents of the DNF_MSGS table manually.
|
fmtreset |
Table 2 and
Table 3 describe how the contents of a
message, the FMT FIN configuration, and the FMT FIN operation commands
issued for an LT determine how the message is processed.
Table 2. FMT FIN messages submitted to the
FMT FIN service (DNF_PF_IS)
| The LT is... |
FMT FIN traffic for the LT is... |
The message is... |
| enabled |
started |
sent immediately via FMT FIN |
| stopped |
held in the OAMS, and sent via FMT FIN when
FMT FIN traffic for the LT is restarted |
| disabled |
started |
held in the OAMS, and sent via FMT FIN when
the LT is enabled |
| stopped |
held in the OAMS, and sent via FMT FIN when
the LT is enabled and FMT FIN traffic for the LT is restarted |
Table 3. FMT FIN messages
submitted to the SIPN FIN service (DNF_ILC_FIN)
| The LT is... |
FMT FIN traffic for the LT is... |
Message type and FIN service name1... |
FMT mode2 is... |
The message is... |
| enabled |
started |
match the configuration |
forced |
sent immediately via FMT FIN |
| not forced |
sent immediately via FMT FIN |
| do not match the configuration |
forced |
sent immediately via FMT FIN |
| not forced |
sent via SIPN FIN3 |
| stopped |
match the configuration |
forced |
held in the OAMS; sent via FMT FIN when FMT
FIN traffic for the LT is restarted |
| not forced |
held in the OAMS; sent via FMT FIN when FMT
FIN traffic for the LT is restarted |
| do not match the configuration |
forced |
held in the OAMS; sent via FMT FIN when FMT
FIN traffic for the LT is restarted |
| not forced |
sent via SIPN FIN3 |
| disabled |
started |
match the configuration |
forced |
held in the OAMS; sent via FMT FIN when the
LT is enabled |
| not forced |
sent via SIPN FIN3 |
| do not match the configuration |
forced |
held in the OAMS; sent via FMT FIN when the
LT is enabled |
| not forced |
sent via SIPN FIN3 |
| stopped |
match the configuration |
forced |
held in the OAMS; sent via FMT FIN when the
LT is enabled and FMT FIN traffic for the LT is restarted |
| not forced |
sent via SIPN FIN3 |
| do not match the configuration |
forced |
held in the OAMS; sent via FMT FIN when the
LT is enabled and FMT FIN traffic for the LT is restarted |
| not forced |
sent via SIPN FIN3 |
Notes:
- 1
- The message type and FIN service name of the message correspond
to values configured for the receiving destination as described in Configuring destinations to which FMT FIN messages can be sent.
- 2
- The sending application sets the FMT mode in the RFH2 header of
the message. For more information, see FIN message transfer services.
- 3
- The message is sent immediately after a session was established
for the LT.
|