Joined: 26 Apr 2004 Posts: 4650 Location: Raleigh, NC, USA
CONNECT:Direct is a peer-to-peer file-based middleware optimized for assured delivery, high-volume, and secure data exchange within and between enterprises.
Some of the components of CONNECT:Direct OS/390 are:
- Data Transmission Facility (DTF), which executes user commands and processes.
- Application Program Interface (API), which enables user interfaces to communicate with the DTF.
- User Interfaces, such as the Interactive User Interface (IUI), the browser end-user interface (EUI), the batch interface, and the CICS interface.
- The Network Map (NETMAP), which defines the local CONNECT:Direct node (PNODE) and the nodes it communicates with (SNODE's). The NETMAP details the type of connection to be used (VTAM, TCP/IP, or ESCON Channel), what the names of the nodes are, and access parameters (user id, passwords, etc.) required on those nodes.
- The Transmission Control Queue, or TCQ, also known as the Process Queue.
A process is the set of CONNECT:Direct statements used to define what the process does. You can create and submit a new process, or submit a pre-defines process from a CONNECT:Direct Process library. When a process is submitted, a parser checks the syntax of the process. If the process passes syntax checking, it is placed in a work queue based on process parameters, such as priority, class, and start time. The process is then selected for execution based on the process parameters and the availability of the remote node.