Inbound configuration

In general, the driver has two phases of inbound operation, where it identifies inbound files and then processes the inbound files.

The driver performs its inbound duties under timer control. The specifics of what the driver does when the timer counts down depends on MODE.

Many FTP servers support the NLST and LIST commands. Consult your FTP server documentation to configure the FTPDIRLISTCMD string.

The driver passes the message into the IBDIRPARSE TPS.

This tables shows the dispositions handled by the driver:
Disposition Action
ERROR Places the message in the error database.
KILL Destroys the message.
OVER Illegal; destroys the message.
PROTO Places the message on the OB-Post-TPS queue.
SEND Places the message on the IB-Post-TPS queue.

CONTINUE messages are ordered lists of files to process. The driver does not perform another inbound scan or run the IBDIRPARSE TPS until the list is empty.

When the driver finishes processing a file, it places the file’s name in a message and passes it through the IBDEL TPS. Non-CONTINUE dispositions are handled as above; CONTINUE messages are parsed as ordered lists of files to delete.

  • If local-tps, then the driver removes those files from the inbound directory.
  • If ftp, then the driver sends a DELE file name command to the FTP server.

As long as the driver has inbound files to process, it processes a message according to IBREADINTERVAL.

The driver reads single-message files into a message and passes them into the engine. For FTP, the driver contacts the remote server, receives the data into a message, and passes it into the engine.

If configured for multi-message files, then the driver receives the file data from the FTP server and writes it to a local file (<threadname>-FTP-temp). After this is on the local disk, it is treated as a local multi-message file. The driver reads the next message, passes it into the engine, and updates the multi-message recovery state file.

When the driver has exhausted the list of input files, it reschedules itself for IBSCANINTERVAL seconds. As long as there are no files available (the inbound directory is empty for local-oldest or the IBDIRPARSE TPS produces no, or empty, CONTINUE messages), the driver rescans every IBSCANINTERVAL seconds.