Introduction : Overview

Overview
The TIBCO Adapter for Files z/OS supports file operations on z/OS datasets and communicates with other applications enabled for TIBCO EMS and TIBCO Rendezvous.
TIBCO Adapter for Files z/OS is typically used in a network operations center or development environment where system administrators, network administrators, and z/OS programmers need to process files between IBM z/OS applications and other operating systems.
Architecture
Typically, the Adapter transfers files from IBM z/OS external storage to applications that reside on operating systems other than IBM z/OS (Figure 1). The adapter is especially useful in batch-oriented handling of files (for example, passing automated input or output files to a billing system) or for doing quick TIBCO EMS/Rendezvous message prototypes.
Figure 1 Logical Architecture
The adapter can also provide real-time handling of files. The adapter’s main purpose is to pass TIBCO EMS or Rendezvous messages in the context of files, not to process files. The data in a message is written to a file or published from a file without being transformed by the Adapter. There are options to add constant fields to a message, and to write constant fields in the output file. If data transformation capability is required, TIBCO BusinessWorks™ should be used in conjunction with the Adapter.
Transport Mechanisms and Delivery Options
TIBCO Adapter for Files z/OS supports the following transport mechanisms:
Users of RVCM have certified delivery with the overhead of ledger files. For simple file transfer, the Adapter supports ECM (Explicit Confirmation Mode), which supplies FTP-like functionality with error handling and recovery using TIBCO Rendezvous (RV). For transfers between the Adapter and TIBCO ActiveMatrix Adapter for Files, only Block Mode over RV is supported with or without ECM. See Explicit Confirmation Mode (ECM).
Wire Format
TIBCO Adapter for Files z/OS supports only TIBCO Rendezvous wire format, not AE wire format. Support is for the MapMessage message type only, the sole exception being that nested messages in EMS are nested inside StreamMessages.