AH! You are running CA's TCPACCESS, not IBM's stack. That really does help. And, of course, I can't test anything because I don't run that software. Unfortunately, CA will not allow a non-customer to look at their product manuals. I may have an old CD around somewhere.
We ran this software long ago. Can you try using the FTP3 client instead of FTP2? As I recall, it was closer to IBM's way of doing things. But I don't know if that is going to help or not. My mistake in asking for FTP as that is even more primitive than FTP2. Also, it might help if you make sure that the job does not have sequence numbers in columns 73-80. I don't know that for sure, but it couldn't hurt. -- John McKown Systems Engineer IV IT Administrative Services Group HealthMarkets(r) 9151 Boulevard 26 * N. Richland Hills * TX 76010 (817) 255-3225 phone * (817)-961-6183 cell [email protected] * www.HealthMarkets.com Confidentiality Notice: This e-mail message may contain confidential or proprietary information. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. HealthMarkets(r) is the brand name for products underwritten and issued by the insurance subsidiaries of HealthMarkets, Inc. -The Chesapeake Life Insurance Company(r), Mid-West National Life Insurance Company of TennesseeSM and The MEGA Life and Health Insurance Company.SM > -----Original Message----- > From: IBM Mainframe Discussion List > [mailto:[email protected]] On Behalf Of Howard Brazee > Sent: Tuesday, July 28, 2009 12:48 PM > To: [email protected] > Subject: Re: FTP to Unix directory with spaces > > On 28 Jul 2009 09:31:13 -0700, [email protected] (McKown, > John) wrote: > > > >> It's a batch job run from JCL, using production procs. > > > >OK, so your client is the z/OS ftp client. I assume (ouch!) > that you're running PGM=FTP. OOPS - looked at your original > message and you're running ftp in TSO batch. Why? Example JCL > without TSO in batch would be: > > > >//STEP1 EXEC PGM=FTP, > >// REGION=0M, > >// PARM='(EXIT' > >//SYSPRINT DD SYSOUT=* > >//OUTPUT DD SYSOUT=* > >//INPUT DD * > >ipaddress-of-remote > >userid-to-use > >password-to-use > >cd "/ps/cs90ftp/conversion_files/CC/extract/Files for Production" > >put 'UMSDEV.QA06.CCITFULL.D090714' citizen_D090714.dat > >/* > > Sorry, I submit a batch job from TSO, containing: > //QA08F1 EXEC UEAA, (TRANSMIT TRANSACTIONS TO PS) // > PASSWRD='UMSDEV.CONVSIS.LIB(OSIRIS)', //* LIBRARY AND MEMBER OF FILE > CONTAINING PASSWORDS ******************* > // FTPPARM='UMS.D44201.JCL(TESTD)' > With: > EDIT UMS.D44201.JCL(TESTD) - 01.16 Columns > Command ===> Scro > ****** ********************************* Top of Data > ********************* > ==MSG> -CAUTION- Profile changed to CAPS OFF (from CAPS ON) because > data > ==MSG> contains lower case characters. 000001 cd > "/ps/cs90ftp/conversion_files/CC/extract/Test Folder" 000002 dir > >I wonder if TSO is stripping off the quote marks?!? > > > >> > >> >How about trying something like: > >> > > >> >cd /ps/cs90ftp/convesion_files/CC/extract > >> >dir > >> > >> That's a better way to test, without creating the file in the wrong > >> place. Good idea. > >> > >> >In desperation, do you really needs the damn blanks? > >> > >> It's a political thing. I can argue with users to who are already > >> using directories with blanks, or find a way to > accommodate them. They > >> have several directories so defined. > >> > >> I suppose we could have Unix scripts moving the files > after I get them > >> to a drop off directory, if we have a trigger paid for on the > >> destination machine. > > > >Can you post the entire output of your batch ftp job? It > might help us discover what the server software is. And that > might help with debugging. Munge as little of the output as > possible (just things like IP address, userids and passwords, > if possible). > > > Is this enough? > ********************************* TOP OF DATA ************** > READY > FTP2 / FIOS > ENTRY (A) D44201.FTP.TMP.T0610908.P0392.S0392 DELETED > READY > END > ******************************** BOTTOM OF DATA ************ > > 10:06:10 -Logged in - User=D44201 Working directory "D44201." > 10:06:10 ProductID: Unicenter TCPaccess Communications Server Rel > 6.0.0 > 10:06:10 (C) Copyright 1987-2003 Computer Associates International, > Inc. > 10:06:10 Component: Client FTP, A6007420 UFTP2 10:06:10 Enter command > or '?' 10:06:10 FTP2: OPEN cs-dev-app-1.cusys.edu 10:06:10 220 Welcome > to the new SIS FTP Service. All activities can and will be logged. > 10:06:10 Enter name (CS-DEV-APP-1.CUSYS.EDU:d44201): cs90ftp 10:06:10 > Enter PASSWORD XXXXXXXX........MMMMMMMM........QQQQQQQQ..........: > ####### > 10:06:10 230 Login successful. 10:06:10 FTP2: cd > "/ps/cs90ftp/conversion_files/CC/extract/Test Folder" > 10:06:10 550 Failed to change directory. 10:06:10 FTP2: dir 10:06:11 > 150 Here comes the directory listing. 10:06:11 -Dataset opened; data > connection starting. 10:06:11 Data transfer Type is ASCII. > Structure is File. Mode is Stream. > 10:06:11 Dataset name: D44201.FTP.TMP.T0610908.P0392.S0392 Dataset > attributes: > 10:06:11 Dsorg=PS Recfm=VB Lrecl=137 Blksize=9076 Volser=DBS935 > Unit=3390 > 10:06:11 Primary allocation is 5 tracks. Secondary allocation is > 15 tracks. > 10:06:11 150 Network data which exceeds LRECL will be wrapped to the > next record. > 10:06:11 226 Directory send OK. 10:06:13 -Transfer complete. 1734 > bytes received in 0.03 seconds (57800 bytes/s) > 10:06:13 Dataset name: D44201.FTP.TMP.T0610908.P0392.S0392 > User=D44201 > 10:06:13 Data bytes written: 1686. 10:06:13 226 Disk tracks > written: 1. 10:06:13 -rw-r--r-- 1 60029 104 349853796 Apr > 06 19:26 CLASStst4 > 10:06:13 -rw-r--r-- 1 60029 104 243952 Jun 11 14:25 > address_incr.dat > 10:06:13 -rw-r--r-- 1 60029 104 0 Jul 08 12:32 > address_mdm.dat > 10:06:13 -rw-r--r-- 1 60029 104 77214 Jun 11 14:25 > citizen_incr.dat > ... > 10:06:13 -rw-r--r-- 1 60029 104 98 Jul 28 15:32 > test.dat > 10:06:14 FTP2: END 10:06:14 221 Goodbye. 10:06:14 221 Session > terminated 10:06:14 T01F2030I FTP2 returns CC=8 > > ---------------------------------------------------------------------- > 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
