'Scuse me, I'm confused.
If these binary files were created on an ASCII thinking box and those files were uploaded to MVS without any translation then you don't want to translate them to/from ASCII & EBCDIC as you don't care.
An example would better illustrate the thinking here...
Example, I create a jpeg on my Linux box and upload it to VM as binary. When the VM webserver serves the file, it doesn't care what format the file is in, it's just a file. You may have to set something in the webserver's tables to say that a jpg file is ASCII/jpg or whatnot for the receiving web browser but otherwise...
No ASCII/EBCDIC translation, no EBCDIC/ASCII translation.
This works, I spent quite a number of years doing this, to great success. I never told the upload program to do any translation on this sort of file, ever.
Yes, yes, I know, I know - if this, if that, if the other. I know the ifs and buts. It's the concept that's important here. There's a bit of fuzzy thinking somewhere in the original problem def.
Plain text files on the other hand... if I had access to CMS Pipelines or it's MVS equivalent, I'd run them through an xlate stage and use the tcp stages to send them off to the Linux image... but then I'm like that.
Rod
---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
