Re: Brain fart - redirect stderr/std out to a file and NOT see an ything after a command is run

2003-11-07 Thread James Melin
Thanks. I've always been a little fuzzy on that whole 21 business, as I use it so rarely. |-+ | | McKown, John | | | [EMAIL PROTECTED]| | | insctr.com | | | Sent by: Linux on| |

Re: Brain fart - redirect stderr/std out to a file and NOT see an ything after a command is run

2003-11-07 Thread McKown, John
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

Re: Brain fart - redirect stderr/std out to a file and NOT see an ything after a command is run

2003-11-07 Thread Post, Mark K
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

Re: Brain fart - redirect stderr/std out to a file and NOT see an ything after a command is run

2003-11-07 Thread John Rowland
{\rtf1\ansi\ansicpg1252\deff0\deflang1033{\fonttbl{\f0\froman\fprq2\fcharset0 Bookman Old Style;}} {\colortbl ;\red0\green0\blue0;} \viewkind4\uc1\pard\cf1\f0\fs24 You can use the pax command on USS to translate the text files while creating a tar file. For example:\par \par pax -wvf mypax.tar

Re: Brain fart - redirect stderr/std out to a file and NOT see an ything after a command is run

2003-11-07 Thread Post, Mark K
Jim, You can use the pax command to do the conversion on the USS side. Mark Post -Original Message- From: James Melin [mailto:[EMAIL PROTECTED] Sent: Friday, November 07, 2003 9:55 AM To: [EMAIL PROTECTED] Subject: Re: Brain fart - redirect stderr/std out to a file and NOT see anything

Re: Brain fart - redirect stderr/std out to a file and NOT see an ything after a command is run

2003-11-07 Thread McKown, John
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

Re: Brain fart - redirect stderr/std out to a file and NOT see an ything after a command is run

2003-11-07 Thread Fargusson.Alan
I did a small test of mget from z/OS Unix to Windows 2000 using the command line, and text mode seems to work for me. -Original Message- From: Post, Mark K [mailto:[EMAIL PROTECTED] Sent: Friday, November 07, 2003 8:23 AM To: [EMAIL PROTECTED] Subject: Re: Brain fart - redirect

Re: Brain fart - redirect stderr/std out to a file and NOT see an ything after a command is run

2003-11-07 Thread Dennis Wicks
Greetings; wget should work. The pages are served in ASCII by the server else they would be gibberish to any ascii machine receiving them. And, yes, I just tried it. Works great and quickly. One problem you might encounter is when the pages use SSI or pages are generated by cgi programs. Then

Re: Brain fart - redirect stderr/std out to a file and NOT see an ything after a command is run

2003-11-07 Thread Post, Mark K
That's if you access them via HTTP. Not FTP, which is what was being discussed, for the very reason you mention. CGI, JSP, etc. files wanted, but not accessible via HTTP. Mark Post -Original Message- From: Dennis Wicks [mailto:[EMAIL PROTECTED] Sent: Friday, November 07, 2003 12:08 PM

Re: Brain fart - redirect stderr/std out to a file and NOT see an ything after a command is run

2003-11-07 Thread James Melin
Well Crap. What about some obtusely complex command line thing that would extend the tarball by file type and convert known text formats using iconv and piping it through tar or what not ? Or am I making it to complex theoretically? |-+ | |

Re: Brain fart - redirect stderr/std out to a file and NOT see an ything after a command is run

2003-11-07 Thread James Melin
How does pax know what to convert and what to keep? |-+ | | John Rowland | | | [EMAIL PROTECTED]| | | c.com | | | Sent by: Linux on| | | 390 Port

Re: Brain fart - redirect stderr/std out to a file and NOT see an ything after a command is run

2003-11-07 Thread Adam Thornton
On Fri, 2003-11-07 at 13:11, James Melin wrote: Well Crap. What about some obtusely complex command line thing that would extend the tarball by file type and convert known text formats using iconv and piping it through tar or what not ? Or am I making it to complex theoretically? I think

Re: Brain fart - redirect stderr/std out to a file and NOT see an ything after a command is run

2003-11-07 Thread Post, Mark K
Good question, for which I have no good answer. If you have a mixture of text and binary files, I don't know what would happen to the binary files. Mark Post -Original Message- From: James Melin [mailto:[EMAIL PROTECTED] Sent: Friday, November 07, 2003 2:14 PM To: [EMAIL PROTECTED]

Re: Brain fart - redirect stderr/std out to a file and NOT see an ything after a command is run

2003-11-07 Thread Dennis Wicks
Greetings; I guess I missed the ftp requirement in the post I replied to. Is ftp a requirement? If not can you use NFS on USS? NFS would solve a lot of problems. All you would need to do is export the file system, then mount it (Map Network Drive in Windows-speak) on your desktop. Then all the

Re: Brain fart - redirect stderr/std out to a file and NOT see an ything after a command is run

2003-11-07 Thread Michael MacIsaac
If you have a mixture of text and binary files, I don't know what would happen to the binary files. A long time ago I wrote a script to run on USS and unpax based on file extension. It's kludgy I know, but it seemed to work: # cat /usr/local/bin/ext function usage { echo Usage:

Re: Brain fart - redirect stderr/std out to a file and NOT see an ything after a command is run

2003-11-07 Thread James Melin
Setting up NFS might be easier than doing what I'm trying to do. |-+ | | Dennis Wicks | | | [EMAIL PROTECTED] | | | Sent by: Linux on| | | 390 Port | | |

Re: Brain fart - redirect stderr/std out to a file and NOT see an ything after a command is run

2003-11-06 Thread McKown, John
James, That doesn't work. Why? First, the shell redirects STDERR to *the current STDOUT destination*, you then redirect STDOUT. Try: tar -cvzf $HOME/hawkweb.tar /it /u/sy4080/tarmessages.txt 21 -- John McKown Senior Systems Programmer UICI Insurance Center Applications Solutions Team