Monitoring FTM SWIFT services

To inform users about their processing, FTM SWIFT services issue the following types of messages:
Command response
This is a response that is returned to a user who issues a command manually, for example, when using the CLI or CDP.
Application response
This is a response that is contained in the MQRFH2 header that is passed back to an application that issues a command or submits some other type of request for processing.
Event message
This is a message that is written to the event log to:
  • Describe an error
  • Describe an RMA action
  • Report status information that is obtained asynchronously and so cannot be returned in a response, for example, information about the status of an SAG or an SnF channel
Typically, an event message is issued during an automatic process such as the processing of FIN, InterAct, or FileAct messages. Each event message has the following structure: 
message_ID  UTC_timestamp  OU_name  service_name  message_text
For example: 
DNFF4068I 10/10/11 14:59:39 BANKA DNF_FSM LT XXXXDEFFA: SL OPEN confirmation timeout detected by...
          |               |               |                                                       |
          |<- timestamp ->|               |<-------------------- message text ------------------->|
For an event message, the last character of its the message ID (for example, the I in DNFF4068I) is called the message classification, and can be one of the following letters:
E
The message describes an error for which user action eventually will be required. Most FTM SWIFT event messages with classification E relate to internal errors or network problems, for example:
  • Errors when accessing DB2® or IBM® MQ
  • Errors within an IBM Integration Bus message flow
  • Inconsistencies in the FTM SWIFT configuration data
  • Network errors
  • SWIFT protocol errors
I
The message contains information only:
  • No error occurred. The message contains information about normal processing.
  • A transient error occurred, but FTM SWIFT will attempt to recover from this error automatically. Only if all automatic recovery attempts fail and user action is required does FTM SWIFT issue a message with classification E.
The associated task continues.
You monitor an FTM SWIFT service by registering to receive some or all of the event messages issued by that service, and specifying where such messages are to be sent:
  • To the reply-to queue of the CLI instance that issued the reg (register) command
  • To the input queue of the event notification service, which passes the event messages to the SYSLOG
  • To a queue from which the events can be evaluated by a user-written application
Figure 1. Event destinations
Figure showing event destinations