That would work, but doing the pax command on the USS side is less work.

Once again feeling pedantic/pedagogical, I would also mention that your find
command would be better coded as
for i in `find . -type f`;do ...

since your version will also return directory names.

:)

Mark Post

-----Original Message-----
From: McKown, John [mailto:[EMAIL PROTECTED]
Sent: Friday, November 07, 2003 11:35 AM
To: [EMAIL PROTECTED]
Subject: Re: Brain fart - redirect stderr/std out to a file and NOT see
an ything after a command is run


I didn't realize that. Well how about doing the "wget" to get the entire
directory structure from MVS. You now have a directory structure in EBCDIC.
Do something like:

mkdir /waga

mkdir /waga/ebcdic

mkdir /waga/ascii

cd /waga/ebcdic

wget ...

for i in $(find . -name '*');do iconv -f IBM1047 -t ISO-8859-1 $i -o
../ascii/$i

cd /waga

rm -r ebcdic


--
John McKown
Senior Systems Programmer
UICI Insurance Center
Applications & Solutions Team
+1.817.255.3225

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.

> -----Original Message-----
> From: Post, Mark K [mailto:[EMAIL PROTECTED]
> Sent: Friday, November 07, 2003 10:23 AM
> To: [EMAIL PROTECTED]
> Subject: Re: Brain fart - redirect stderr/std out to a file
> and NOT see an ything after a command is run
>
>
> The wget command is one of my favorites, and it is available
> for Windows,
> but from my reading of the man page, wget only does binary
> transfers, not
> text/ASCII ones.  So, Jim would wind up with EBCDIC on his
> Linux/390 system,
> not ASCII.
>
>
> Mark Post
>
> -----Original Message-----
> From: McKown, John [mailto:[EMAIL PROTECTED]
> Sent: Friday, November 07, 2003 10:37 AM
> To: [EMAIL PROTECTED]
> Subject: Re: Brain fart - redirect stderr/std out to a file
> and NOT see
> an ything after a command is run
>
>
> On z/Linux, use the "wget" command. It will do recursive ftp
> "gets". On
> Windows, you are on your own <grin>. Of course, you could use
> "wget" to get
> it to Linux (converting to ASCII), then use zip or tar on
> Linux to bundle it
> up, then ftp to get the tar file to Windows.
>
>
> --
> John McKown
> Senior Systems Programmer
> UICI Insurance Center
> Applications & Solutions Team
> +1.817.255.3225
>
> 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.
>
> > -----Original Message-----
> > From: James Melin [mailto:[EMAIL PROTECTED]
> > Sent: Friday, November 07, 2003 8:55 AM
> > To: [EMAIL PROTECTED]
> > Subject: Re: Brain fart - redirect stderr/std out to a file
> > and NOT see anything after a command is run
> >
> >
> > Actually, it occurs to me that this will do exactly what I
> > wanted it to do,
> > but not what I need it to do....
> >
> > Specifically, I need to manually re-import the file system
> > structure of a
> > web site built on OS/390 Unix system services to which the developer
> > destroyed his 'frontpage' source. The import website thing
> > only follows
> > links and he has some JavaScript built menus and crap, and
> > cannot get the
> > whole thing back properly. We want to re-deploy this to
> z/Linux (minor
> > changes to scripts required)
> >
> > I had looked into having FTP recursively navigate a directory
> > structure and
> > re-created it on his desktop but I can't seem to see how to
> > do that. So I
> > was going to just tar the whole thing but the I realized the
> > text based
> > files  will be EBCDIC, so that's kinda useless.
> >
> > What is the easiest way to bring this USS installed directory
> > structure
> > into windows so we can used the developer's favorite (gack) tool to
> > redeploy this to z/Linux?
> >
>

Reply via email to