One of my posts may have been lost.. but I wanted to point out that I transferred the data to z/OS file server in ASCII _on purpose_. Since the rest of the install docs all talk about using a Windows SMB server or a Linux FTP server, I figured it might be retrieving everything in one "mode" (binary) and because of the platforms mentioned, assume the text files were in ASCII.
My FTP logs so far show only the file 'content' being retrieved in ASCII, followed by 'root' in binary, 'content' AGAIN but in binary, media.1/info.txt in binary, and then control.xml in binary. So, it does look like it retrieves quite a few of the text files in binary anyway. Tim Hare Senior Systems Programmer Florida Department of Transportation (850) 414-4209 "McKown, John" <[EMAIL PROTECTED]> Sent by: Linux on 390 Port <[email protected]> 03/24/2006 05:00 PM Please respond to Linux on 390 Port <[email protected]> To [email protected] cc Subject Re: Checking with the experts... > -----Original Message----- > From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On > Behalf Of Tim Hare > Sent: Friday, March 24, 2006 3:55 PM > To: [email protected] > Subject: Checking with the experts... > > > I'm trying to do the FTP install from z/OS FTP server. > > I get messages > > No Automatic proposal possible. Specify mount points in the > 'Partitioner' dialog. > > and > > Cannot read package data from installation media. Media Error? > > I suspect that this may be because yast is trying to FTP the 'package > data' in 'text mode' and therefore there's an EBCDIC-ASCII translation > happening (the FTP server automatically converts text files), but I > copied the CDs with pscp so the files are already ASCII. Can anyone > verify that this would be a probable cause of the error? > > Tim Hare You mentioned "pscp". Windows, right? That means that the files on the z/OS system are still in ASCII. That's because pscp does not translate from Windows ASCII to z/OS EBCDIC. The ftp process for "text" however, assumes that the files are in EBCDIC, and so attempts to translate from EBCDIC to ASCII. However, since it is already ASCII, the result is "junk"(tm). To double check, use ISHELL on z/OS and try to BROWSE one of the "text" files. You'll likely get hex "junk"(tm). Change to HEX ON. and you'll likely be able to tell easily that the data is still in ASCII. Since there are a lot of blanks, which are x'20' in ASCII, you'll likely see a bunch of @'s (x'20' in EBCDIC is displayed as @). -- John McKown Senior Systems Programmer UICI Insurance Center Information Technology This message (including any attachments) contains confidential information intended for a specific individual and purpose, and its content is protected by law. If you are not the intended recipient, you should delete this message and are hereby notified that any disclosure, copying, or distribution of this transmission, or taking any action based on it, is strictly prohibited. ---------------------------------------------------------------------- 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 ---------------------------------------------------------------------- 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
