On Thu, 26 Mar 2009 19:13:40 -0500, Hal Merritt <[email protected]> wrote:
I think I see what you mean. This will not work for a "z/OS to z/OS" VSAM transmission, since VSAM is not supported under z/OS FTPD. But it will allow you to: 1) Retrieve a flat file from anywhere and, as long as it's properly sorted, put it in to a z/OS KSDS. 2) Transmit from a z/OS KSDS to a sequential file on a remote system. 3) Retrieve a KSDS from VSE into a KSDS on z/OS. 4) Transmit a KSDS from z/OS to VSE. 3 and 4 work because VSE totally supports FTPing of VSAM files, even when VSE is the server. Actually, while this all seems to work with ESDS, KSDS seems to be a bit more picky. In my original test I went to/from VSE with a KSDS on both sides. This seems to require the "STRUCTURE RECORD" command which as far as I know is supported only by z/OS and VSE. If you try it without this it fails with this: EZA2564W Open of //DD:ACHTOTL failed. EZA1735I Std Return Code = 16000, Error Code = 00018 I have not been able to determine what those codes actually mean. I am able to get a file from a "distributed" FTP server (as long as the data is all ASCII) and place it into an ESDS using the //DD method, no STRUCTURE command required. For whatever that does for me... All in all, I can't say I totally understand what should and should not / does and does not work. Frank >Define 'work'. Is the destination file a VSAM KSDS? > >-----Original Message----- >From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Frank Swarbrick >Sent: Thursday, March 26, 2009 6:31 PM >To: [email protected] >Subject: FTP of VSAM file > >Did you know that, in some circumstances you *can* FTP a VSAM file? >Use "DD name support". See the following: > >//FTP1 JOB CLASS=A,MSGCLASS=X,NOTIFY=&SYSUID >//EXEC EXEC FTP,SERVER=10.1.112.95 >//FTP.INPUT DD DISP=SHR,DSN=FJS.WORK.FTPDATA(PEPVSE) >// DD * >cd inetcat >structure record >binary >get ach.prod.ksds.achtotl //DD:ACHTOTL >quit >/* >//ACHTOTL DD DISP=OLD,DSN=FJS.VSAM.ACHTOTL > >FJS.VSAM.ACHTOTL is a KSDS. I can't see that it's documented anywhere >that this works, but it does in fact work. > >Maybe you all knew this, but I've seen many statements that FTP does not >support VSAM. And doing it most other ways it does not. > >Frank > >BTW, this is my FTP proc: >//FTP PROC PORT=, >// AUTH=, >// FTPDATA=, >// EXIT='-e', >// TIMEOUT='-w 20' >//FTP EXEC PGM=FTP,REGION=0M, >// PARM='&FTPDATA &AUTH &EXIT &TIMEOUT &SERVER &PORT' >// PEND > >---------------------------------------------------------------------- >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 >NOTICE: This electronic mail message and any files transmitted with it are intended >exclusively for the individual or entity to which it is addressed. The message, >together with any attachment, may contain confidential and/or privileged information. >Any unauthorized review, use, printing, saving, copying, disclosure or distribution >is strictly prohibited. If you have received this message in error, please >immediately advise the sender by reply email and delete all copies. > >---------------------------------------------------------------------- >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 ---------------------------------------------------------------------- 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
