Product Overview
SAN DataMover software provides a way to move large amounts of disk data quickly and efficiently between the MCP and the Windows environments using a shared disk subsystem as a transport mechanism (transfer volume).
For transfers from a Windows environment to a ClearPath MCP Environment, you can only use Virtual Sector Size, Version 2 (VSS-2) formatted disks as transfer volumes. For transfers from a ClearPath MCP Environment to a Windows environment, you can use disks of any format (VSS-1, VSS-2, VSS-3, or Native) on any storage type (physical or emulated disk units) as transfer volumes. If a transfer volume is not available, files can be transferred between an MCP Environment and a Windows environment in either direction over a TCP/IP connection.
| Note: | For information on disk formats and storage types, see the Disk and Tape Storage Systems Configuration Guide. |
General Features
Supported File Types
SAN DataMover can transport files with the following characteristics:
-
FILESTRUCTURE value of ALIGNED180 or STREAM
-
BLOCKSTRUCTURE value of FIXED
-
FILEORGANIZATION value of NOTRESTRICTED or RELATIVE
Other types of ClearPath MCP files are not supported.
File Transfers from an MCP System to a Windows System
Two file transfer methods are available with San DataMover when transferring files from an MCP system to a Windows system:
-
Using a transfer volume
This method uses a disk subsystem that is visible to both the MCP and Windows systems. The disk must be either an MCP emulated disk (also known as a logical disk) or an external physical disk configured as either a VSS-1 or a VSS-2 MCP labeled disk. The MCP writes the files to the transfer volume, and the Windows system reads the file from the transfer volume.
-
Using TCP/IP
SAN DataMover on the MCP system opens a TCP/IP port to SAN DataMover on the Windows system and then transfers the file over the TCP/IP connection. This method is slower than using a transfer volume, but because the Windows system performs the data translation and formatting, it is faster than a conventional FTP file transfer.
File Transfers from a Windows System to an MCP System
Two file transfer methods are also available with San DataMover when transferring files from a Windows system to an MCP system:
-
Using a transfer volume
This method uses a disk subsystem that is visible to both the MCP and Windows systems. The disk must be an external physical disk configured as a VSS-2 MCP labeled disk. The Windows system writes the files to the transfer volume, and the MCP system reads the files from the transfer volume.
-
Using TCP/IP
SAN DataMover on the MCP system opens a TCP/IP port to SAN DataMover on the Windows system which then transfers the file over the TCP/IP connection. This method is slower than using a transfer volume, but because the Windows system performs the data translation and formatting, it is faster than a conventional FTP file transfer.
Initiation and Management of File Transfers
You can initiate and manage file transfers between a local Windows environment and a ClearPath MCP Environment using a Windows client (for example, a GUI, a command prompt, a VB Script or a C++ API), a ClearPath MCP command line interface (such as MARC, CANDE, or ODT), a WFL interface, or ALGOL or COBOL API interfaces.
Dynamic WRAP and UNWRAP File Transfer
When an MCP file is moved from the MCP Environment to Windows using SAN DataMover, the MCP file attributes are lost. To maintain these attributes, which is desirable when using SAN DataMover for backup or disaster recovery functions, you need to explicitly WRAP the files before transferring them to Windows. This process is slow and uses valuable MCP processing time. It also requires the use of scripts or a manual two-step process.
The dynamic WRAP and UNWRAP file transfer feature offloads the process of wrapping a file to the SAN DataMover service that is running on Windows. When the file is moved back to the MCP, it is unwrapped by the Windows service, thus preserving the MCP file attributes. Because the file is wrapped and unwrapped during transfer, the file header information is preserved.
File transfers using the dynamic wrapping process are faster than normal MCP FTP copies for customers who cannot use BNA file transfers.
Other Features
The following features provide many helpful capabilities.
-
Convert printer backup files to plain text (txt) or rich text formatted (rtf) files when transferring files from a ClearPath MCP system to a Windows system.
-
Copy multiple files from the MCP Environment to the Windows environment.
-
Use wild cards to easily copy multiple files from an MCP Environment to a Windows environment.
-
Translate files from EBCDICUTL to Codepage 950 (WINBIG5) on Windows.
-
Copy files with or without FTP servers between ClearPath MCP systems and remote Windows systems.
-
Copy files between a remote (Windows Unix, or Linux) FTP server and the ClearPath MCP Environment, using a local Windows server running the SAN DataMover Windows service.
-
Add sequence numbers and blank IDs to records as a file is being transferred from Windows to the ClearPath MCP Environment.
-
Supports FTPS and SFTP between a local SAN DataMover Windows environment and a remote Windows, UNIX, or Linux server.
-
Supports SSL transfers between a local SAN DataMover Windows environment and a remote SAN DataMover Windows environment.
-
Supports SSL transfers between a ClearPath MCP Environment and a local SAN DataMover Windows environment.
-
The SAN DataMover tool stores Trace files in the “Backups” directory when they reach a certain size. The files are then automatically deleted from the directory after a specified number of days.
-
Supports PRINTER BACKUP source files with a FILESTRUCTURE of ALIGNED180 or BLOCKED.
-
The /F command in the windows batch interface specifies that a carriage return and line feed character set (CR/LF) represents a new record.
New Features/Enhancements
The new feature/enhancement for this release is an enhancement of the responses returned by the STATUS and STATUS ALL commands.
The STATUS command now returns the current status of the SAN DataMover environment in detail, including the number of active copy requests and the maximum number of requests allowed.
The STATUS ALL command now returns all request numbers and their associated statuses. A detailed status is also logged in the SAN DataMover log files.
Additionally, four new commands are now available:
-
STATUS ACTIVE
-
STATUS PENDING
-
STATUS FAILED
-
STATUS COMPLETED
Configuration Information
|
ClearPath MCP System |
|
|
Primary Workstation |
A PC running Microsoft Windows (See the Compatibility Matrices at URL that follows.) |
|
See the Compatibility Matrices at https://www.support.unisys.com/common/matrices/matrixTOC.aspx?pla=MCP&nav=MCP |
|
|
Additional Workstations (Running only the Administration software for Windows and Windows client) |
A PC running Microsoft Windows See the Compatibility Matrices at URL listed previously. |
|
Transfer Volume |
A transfer volume is required only if you want to use it to move files from a Windows environment to an MCP Environment. For file transfers from an MCP Environment to a Windows environment, SAN DataMover can move files through TCP/IP if a transfer volume is not available. A transfer volume must be a disk subsystem with these characteristics:
Emulated disks can be used as a transfer volume only for transfers from an MCP Environment to a Windows environment. |
Ordering Information
|
Platform |
Style |
|
ClearPath |
The ordering style for the SAN DataMover is VSSnn-SDM, where nn represents performance groups 10 through 160 (in increments of 10). |
Source code is not available for this product.
Product Information
Refer to the SAN DataMover Help (4310 7127) for more information.
