| |
Enterprise Data Streaming Technology
Parallel Data Mover (PDM) is a Server-to-Server data movement and data access/sharing application. File transfer between z/OS and any UNIX, Windows or Linux node in the network, and/or directly between z/OS nodes, is achieved using extraordinarily efficient and high-speed data streaming technology. With robust client interfaces on all supported platforms, PDM moves data between any applications that read and/or write sequential files. PDM also allows piping of data, which promotes true data sharing between applications running on disparate systems.
Configuration Alternatives
At least one node must be direct-attached by way of either a FICON-FCP connection adapter or TCP/IP. Using FICON-FCP, file transfer to and from direct-attached nodes run at very high data transfer rates with data streaming. Data is transferred to other nodes in the network through gateway direct-attached nodes, which perform at TCP/IP network speeds.
Configuration Examples [see illustrations]
In the discussion that follows, we refer to non-PDM nodes, PDM nodes and PDM client nodes.
- Non-PDM node - has no component of PDM installed.
- PDM node - has the PDM product installed and configured.
- PDM client node - is a PDM node with a Node File Transfer Client installed.
- If your do not install any PDM clients, you use a TCP/IP client, and only those functions supported by TCP/IP are allowed.
Example 1: A simple homogenous zOS 2 configuration involves two MVS nodes attached directly to one another. Both nodes must have PDM installed. FICON, ESCON, or TCP/IP can be the physical connection.
Example 2: A heterogeneous zOS-Open System configuration involves a zOS node attached directly to multiple open systems or PC nodes. Again, every direct-attached node must have PDM installed on it. FICON to FCP (see PDM/SNA) or TCP/IP is the physical connection.
Example 3: Any combination of the above can also be created. Note that MVS Clients move data to any PDM node (MVS or Open Systems) or any network node accessible through a PDM direct-attached node. MVS clients consist of the following components:
- File Transfer client
- ISPF client
- REXX interface
- The COBOL/Assembler Callable API
- BSAM/QSAM interface (SSI)
- Enhanced File Transfer client (DMEXCLI)
Detailed Characteristics [see complete lists]
- MVS--MVS Data Access and Movement
- MVS--UNIX/Windows/Linux Data Access and Movement
- Security
- Reliability
- Management Facilities
- Performance
- Client Interfaces
- Supported Platforms
- Connectivity Options
|
|
|
