Path: utzoo!attcan!uunet!cs.utexas.edu!usc!elroy.jpl.nasa.gov!ncar!gatech!ncsuvx!news
From: dan@hobbes.ncsu.edu (Daniel Heath)
Newsgroups: comp.lang.rexx
Subject: Re: Using the system stack
Message-ID: <1991Jan13.063643.28478@ncsuvx.ncsu.edu>
Date: 13 Jan 91 06:36:43 GMT
References: <1991Jan09.180541.4246@eecs.wsu.edu>
Reply-To: dan@hobbes.ncsu.edu (Daniel Heath)
Organization: NCSU Computing Center
Lines: 17

In article <1991Jan09.180541.4246@eecs.wsu.edu> dfrank@yoda.UUCP (Duane D. Frank) writes:
>I am using REXX on an IBM 3090 machine running VM/SP HPO (CMS), and I have
>written an EXEC in REXX that does all of the things that the UNIX function
>GREP does.  
> 
>My question is:  If I want to call this GREP exec from another exec or
>function, and I want the GREP program to put it's output information on
>the system stack so it can be pulled off by the calling EXEC, (with a 
>do while queued() for instance) how would I go about putting the output
>information onto the stack?

Your best bet is to use the CMS function GLOBALV.  It will allow you to 
carry variable values across applications.

                                              Later,
                                              Dan Heath
                                              dan@hobbes.catt.ncsu.edu