SCOUG Logo


Next Meeting: Sat, TBD
Meeting Directions


Be a Member
Join SCOUG

Navigation:


Help with Searching

20 Most Recent Documents
Search Archives
Index by date, title, author, category.


Features:

Mr. Know-It-All
Ink
Download!










SCOUG:

Home

Email Lists

SIGs (Internet, General Interest, Programming, Network, more..)

Online Chats

Business

Past Presentations

Credits

Submissions

Contact SCOUG

Copyright SCOUG



warp expowest
Pictures from Sept. 1999

The views expressed in articles on this site are those of their authors.

warptech
SCOUG was there!


Copyright 1998-2024, Southern California OS/2 User Group. ALL RIGHTS RESERVED.

SCOUG, Warp Expo West, and Warpfest are trademarks of the Southern California OS/2 User Group. OS/2, Workplace Shell, and IBM are registered trademarks of International Business Machines Corporation. All other trademarks remain the property of their respective owners.

The Southern California OS/2 User Group
USA

SCOUG-Programming Mailing List Archives

Return to [ 31 | October | 1998 ]

>> Next Message >>


Date: Sat, 31 Oct 1998 16:25:09 PDT
From: "Gregory W. Smith" <gsmith@well.com >
Reply-To: scoug-programming@scoug.com
To: < "SCOUG-Programming@scoug.com" > SCOUG-Programming@scoug.com >
Subject: SCOUG-Programming: Pipes and REXX

Content Type: text/plain

-----BEGIN PGP SIGNED MESSAGE-----

Is there an elegant way to invoke a command from within REXX and have
it redirect the output to the standard input? Right now I am using
pipes as in the example:

bar | blatz

The program bar.exe wites to standard out which is piped into
blatz.cmd. The main processing loop in blatz.cmd looks something like:

while lines() >
linetoprocess = linein()
...
end

I can almost do what I want if I use a temporary file. I start bar.exe
in the REXX script and put the output in a file and then read from the
file:

'@bar >sometempfile'
while lines('sometempfile') >0
linetoprocess = lienin('soemtempfile')
.....
end

Is there and easy way to run bar.exe and have it write to what the
REXX .cmd program sees as input. Making a scratch file and cleaning up
afterward is not much of a problem. But finding all of the linein(),
charin(), and other IO statements in a long program is a pain.
===============================================================
Gregory W. Smith (WD9GAY) gsmith@well.com
finger gsmith@well.com for PGP public key
-----BEGIN PGP SIGNATURE-----
Version: 2.6.2

iQCVAwUBNjuq4DtML4mvizAhAQFoIwP/TUcVstdYhs02NSNmtFtEYr2dGEi08ip0
FQehY2E9wQICn8fG7jLkrIC+/oawTxiCGJREinNIqRPh2SYaeHyIu9AU0PHFiaas
69B3pE5+/+VLmMVMFoYY6R8Q+CVTIzGQK7qewdSYE1h8VFbDutkVMCm5TsXfeyd9
2hSPH9uPXWw=
=4ORh
-----END PGP SIGNATURE-----

=====================================================

To unsubscribe from this list, send an email message
to "steward@scoug.com". In the body of the message,
put the command "unsubscribe scoug-programming".

For problems, contact the list owner at
"rollin@scoug.com".

=====================================================


>> Next Message >>

Return to [ 31 | October | 1998 ]



The Southern California OS/2 User Group
P.O. Box 26904
Santa Ana, CA 92799-6904, USA

Copyright 2001 the Southern California OS/2 User Group. ALL RIGHTS RESERVED.

SCOUG, Warp Expo West, and Warpfest are trademarks of the Southern California OS/2 User Group. OS/2, Workplace Shell, and IBM are registered trademarks of International Business Machines Corporation. All other trademarks remain the property of their respective owners.