Using FTP to Move Structured Files Without Causing Corruption
Using FTP to Move Structured Files Without
Causing Corruption
Symptom
After using FTP to copy structured files from one NonStop server to another, the
target file is corrupted.
Version
All.
Problem
Using FTP products other than those designed to move structured files between
NonStop systems results in a corrupted target file.
Fix
Use the NonStop systems FTP client to move structured files, such as
key-sequenced, relative, and entry-sequenced files, between NonStop servers.
To ensure that structured files are correctly transferred, you must first issue the
FUP INFO command using the DETAIL option for the file you wish to transfer. All
file attributes that are present in the display must be included in the get (or put)
command.
Note: If the file you want to copy is a structured file containing embedded
<CRLF> character sequences, you must first issue the stru command with the r
option. For more information about the stru command:
In G06.20 and later, see the NonStop TCP/IP Applications and Utilities
User Guide.
●
In G06.19 and earlier, see the NonStop TCP/IP Applications User Guide.●
Example
This example copies a remote key-sequenced structured file, named KEYSEQ, to the local
NonStop server.
Before starting the FTP session, obtain a detailed listing of the file:1.
100>FUP INFO KEYSEQ,DETAIL
$ABC.SOURCE.KEYSEQ (file name)
ENSCRIBE
TYPE K (filetype)
CODE 1001 (filecode)
EXT ( 5 PAGES, 5 PAGES) (primary and secondary extents)
REC 60 (record-len)
BLOCK 512
IBLOCK 512 (index_blk_len)
KEYLEN 4 (pri-key-len)
KEYOFF 0 (key-offset)