IND$FILE lacks the options to do this. FTP requires the right parameters on the downlaod and the upload.
- use ISPF to get the original DCB and space information for both the PDS and the sequential backup as you may need them later. To download: ftp> bin 200 Representation type is Image ftp> quote stru r 250 Data structure is Record ftp> get seq.backup 200 Port request OK. 125 Sending data set KTOMIAK.SEQ.BACKUP 250 Transfer completed successfully. ftp: 9587 bytes received in 0.09Seconds 101.99Kbytes/sec. ftp>quit to upload: ftp> bin 200 Representation type is Image ftp> quote site recfm=vs blksize=32740 lrecl=32736 <==. enter the original sequential backup dcb information 200 SITE command was accepted ftp> quote site tracks primary=20 secondary=10 unit=sysallda <== enter your space needs here 200 SITE command was accepted ftp> put seq.backup seq.backup2 200 Port request OK. 125 Storing data set KTOMIAK.SEQ.BACKUP2 250 Transfer completed successfully. ftp: 9587 bytes sent in 0.00Seconds 9587000.00Kbytes/sec. ftp>quit That should be the complete answer for anyone really wanting to just use IEBCOPY to create a sequential backup, store it on a PC for some amount of time, and then use it on z/OS once again. Assuming the FTP translation tables on both the download and upload are the same. They are on my test. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
