Now that is intuitive. An interesting effect is that using that method, following it with a pipe < file | deblock string x0d0a > newfile, the new file still in asci has more bytes than one of the files that had the quotes stripped out. When I try pipe < newfile | xlate a2e | > file3, there are no quotes in file3 - it matches the other files without the quotes.
Is there some code page other than the defaults for the A2E translation that I need to use? How and why does the translation strip the quotes? Where in Boeing's world do you live? I started my career at Boeing, Wichita Division back in '63. Regards, Richard Schuh ________________________________ From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Stricklin, Raymond J Sent: Monday, August 31, 2009 3:30 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: FTP Translation ________________________________ From: Schuh, Richard [mailto:rsc...@visa.com] Subject: FTP Translation I am trying to FTP a file that is Wnidoze ASCII to VM without having it translated to EBCDIC. In this case, the PC is the client and VM, the host. I have tried: * SITE AUTOTRANS OFF - I get a message saying that the SITE command is invalid. The same applies to using an abbreviation for AUTOTRANS. I would have expected the BIN command to give you fully untranslated results, so I don't have an answer to your actual question, ...but. To use the SITE command with the Windows built-in FTP client, you must prefix it with QUOTE (QUOTE SITE AUTOTRANS OFF). This is the mechanism they give you to send "arbitrary" commands to the server. ok r.
