This is a bit off-topic, but it may be of interest to others.....

If you take a good look inside the z/VM DVDPRIME exec (which is used to install z/VM 5.2 from DVD media), there is a PIPELINE specification towards the end of the code that uses an FTPGET stage......and it appears that the FTPGET stage puts each record of the retrieved file into the pipeline. Unfortunately, this FTPGET stage isn't documented anywhere that I can see.

This would make getting a file from MVS and changing it's RECFM (and/or it's LRECL, to) trivial. Maybe Mike can give it a try and report back to the list.

Have a good one.

DJ

Mike Walter wrote:
LOCSITE VARRECFM (as I'm using it, anyway) not doing it.  Proof:
When FTP started in my virtual machine, it reported: VM TCP/IP FTP Level 510 Then after connecting the following ensured... list 'FIN.P.DATA'
PORT 10,64,103,94,12,49

200 Port request OK.
LIST 'FIN.P.DATA'

125 List started OK Volume Unit Referred Ext Used Recfm Lrecl BlkSz Dsorg Dsname PRD100 3390 2006/01/05 2 756 FB 600 27600 PS 'FIN.P.DATA' 250 List completed successfully. Command: locsite varrecfm Command: locstat Trace:FALSE, Send Port:TRUE Use NETRC DATA File:TRUE, Logon Prompting:TRUE Send Site with Put command:TRUE Connected to:nn.nn.nnn.nnn, Port:FTP control (nn), logged in <--masked Local Port:nnnn <--masked Data type:a, Transfer mode:s Record format:V <--Yeah! Translate Table: STANDARD Console Width: 80 Command: cms l * * E <--- Prove it's not here before DMSLST002E File not found DTCFTC0100E CMS return code: 28 Command: get 'FIN.P.DATA' finhrs.data.e
PORT 10,64,103,94,12,50

200 Port request OK.
RETR 'FIN.P.DATA'

125 Sending data set FIN.P.DATA FIXrecfm 600 <--- No! 250 Transfer completed successfully. 39595928 bytes transferred in 3.632 seconds. Transfer rate 10901.96 Kbytes/sec. Command: cms l * * E (ISO FILENAME FILETYPE FM FORMAT LRECL RECS BLOCKS DATE TIME FIN DATA E1 F 600 69527 10185 2006-01-05 14:40:03 Command: The information contained in this e-mail and any accompanying documents may contain information that is confidential or otherwise protected from disclosure. If you are not the intended recipient of this message, or if this message has been addressed to you in error, please immediately alert the sender by reply e-mail and then delete this message, including any attachments. Any dissemination, distribution or other use of the contents of this message by anyone other than the intended recipient is strictly prohibited.

Reply via email to