Others have suggested XMIT/RECEIVE to get around problems with shipping RECFM U files. (Not only FTP has problems.)
Another possibility is to use the IBM supplied TERSE/UNTERSE. We recently had to send Level 2 exactly this kind of doc for a PMR. They were able to recreate our original file, warts and all. . . . JO.Skip Robinson Southern California Edison Company SHARE MVS Program Co-Manager 626-302-7535 Office 323-715-0595 Mobile [EMAIL PROTECTED] IBM Mainframe Discussion List <[email protected]> wrote on 11/30/2005 12:49:34 PM: > Hi all kind help pls > > I wanted to transfer SYS1.SIEALNKE dataset from one > Z/OS to another.. Let me state it as from MVSA to MVSB > following are the steps I followed > 1. Created a dump of the dataset SYS1.SIEALNKE > (which is in MVSA) in the name of THIRU.SIEALNKE using > the utility ADRDSSU. > 2. FTPied MVSA from MVSB and using the parameter > LOCSITE PRI=50 SEC=20 CY BLOCKSIZE=27998 REC=U > > BIN > GET SIEALNKE > > The file was successfully transfered. > 3. Now i tried to restore the dataset SIEALNKE > using the utility ADRDSSU in MVSB, but i facing the > below error > ADR389E (001)-IORT (01), INVALID INPUT ON DDNAME DASD, > INPUT DATA SET NOT PRODUCED BY DFDSS OR DFSMSDSS > ADR415W (001)-TDDS (02), NO DATA SETS WERE COPIED, > DUMPED, OR RESTORED FROM ANY VOLUME ---------------------------------------------------------------------- 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

