Gil, > The ugly truth:
> >>> STRU R > 504 Unimplemented STRU type. Depending on what the OP wants to do with the file on the Windows system, it may not matter that it does not support STRU R. The important thing is that z/OS does. If the primary goal is what we used to call "invertibility" -- getting the file back exactly as it started out -- STRU R with binary should work. You just have to make sure you tell it to the z/OS side on both transfers. Consider the following example. At the end of this exercise, IP.PKTTRACE and IP.PKTTRACE.COPY are identical data sets: ftp> dir ip.pkttrace.* 200 Port request OK. 125 List started OK Volume Unit Referred Ext Used Recfm Lrecl BlkSz Dsorg Dsname SDSMVO 3390 2013/01/10 1 2 VB 27994 27998 PS IP.PKTTRACE 250 List completed successfully. ftp: 137 bytes received in 0.00Seconds 137.00Kbytes/sec. ftp> quote site lrecl=27994 blks=27998 recfm=vb 200 SITE command was accepted ftp> binary 200 Representation type is Image ftp> quote stru r 250 Data structure is Record ftp> get ip.pkttrace 200 Port request OK. 125 Sending data set BSSJ1.IP.PKTTRACE 250 Transfer completed successfully. ftp: 77311 bytes received in 0.28Seconds 275.13Kbytes/sec. ftp> quote site lrecl=27994 blks=27998 recfm=vb 200 SITE command was accepted ftp> binary 200 Representation type is Image ftp> quote stru r 250 Data structure is Record ftp> put ip.pkttrace ip.pkttrace.copy 200 Port request OK. 125 Storing data set BSSJ1.IP.PKTTRACE.COPY 250 Transfer completed successfully. ftp: 77311 bytes sent in 0.37Seconds 206.71Kbytes/sec. ftp> dir ip.pkttrace.* 200 Port request OK. 125 List started OK Volume Unit Referred Ext Used Recfm Lrecl BlkSz Dsorg Dsname SDSMVO 3390 2013/01/10 1 2 VB 27994 27998 PS IP.PKTTRACE SDSMVN 3390 2013/01/10 2 2 VB 27994 27998 PS IP.PKTTRACE.COPY 250 List completed successfully. ftp: 214 bytes received in 0.00Seconds 53.50Kbytes/sec. Best, Steven St.Jean > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:[email protected]] On > Behalf Of Paul Gilmartin > Sent: Thursday, January 10, 2013 2:55 PM > To: [email protected] > Subject: Re: FTP variable block dataset from z/OS to Windows and back > > On Thu, 10 Jan 2013 11:50:15 -0700, Roger Bolan wrote: > > >I'm curious about how they used RECORD or STRUC R to do what they wanted. > >I haven't played with it, but my initial impression was that STRUCTURE > >RECORD might work if you were going from z/OS FTP to another z/OS FTP, > >but that the structure information might be lost if there were other non- > MVS > >systems in the path. I could be wrong about that. I'd like to know. > > > The ugly truth: > > Command: > quote syst > >>> syst > 215 UNIX Type: L8 Version: SUNOS > Command: > record > >>> STRU R > 504 Unimplemented STRU type. > Command: > > ... notwithstanding that it's specified in RFC 959. > > -- gil > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, send email > to [email protected] with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
