I thought I had been abandoned, but Andrea pulled thru for me. Thanks.
What hurts is that I had a similar problem about a month ago, and solved it
this way. The mind is the second thing to go....
Dan Murphy [EMAIL PROTECTED]
EMC Corp. 508-249-3322
Hopkinton, MA 01748
EMC˛
where information lives
-----Original Message-----
From: Andrea Holstein [mailto:[EMAIL PROTECTED]]
Sent: Saturday, November 17, 2001 3:14 PM
To: [EMAIL PROTECTED]
Subject: Re: NT - piping input to my perl script
Daniel Murphy schrieb:
>
> OK, I've been lurking long enough. Got what I think is a very simple
> question which may be more of an NT command shell question as it is a Perl
> question.
>
> I have a very simple script (below) which reads data from STDIN and
converts
> the supposed EBCDIC hex data to readable text (yes, I'm a mainframer....).
> This works fine when I run it normally from the command line and enter
data
> from the keyboard. So, if I enter 'c1c2c3c4' when prompted, it will print
> out 'ABCD'. Piece o' cake.
>
> Now, I was hoping to pipe data to this script from the output of a
previous
> command. For example, from NT, you can say:
>
> type testpgm.c | more
>
> ...which will pipe the output (STDOUT) from 'type' to the input to 'more'
> (STDIN).
>
> OK, so I try the same thing using my script by entering:
>
> type ebcdic.data | hexeb.pl
A long time ago, I had i similar problem under NT.
I assume that perl files are assigned to start perl.exe.
So in reality NT starts first the assignment and the perl.
All in and output goes into this asssignment too.
What helped ?!
type ebcdic.data | perl hexeb.pl
^^^^
Hope it helps you.
Best Wishes,
Andrea
PS: As you can see, Windows has it's own imagination of piping.
That's not bad, Windows is simply not an OS for people who want to work.
It's cool for playing :-))
--
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
