Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!tut.cis.ohio-state.edu!ucbvax!YKTVMH3.BITNET!PERSHNG
From: PERSHNG@YKTVMH3.BITNET ("John A. Pershing Jr.")
Newsgroups: comp.lang.asm370
Subject: (none)
Message-ID: <9008171356.AA18634@ucbvax.Berkeley.EDU>
Date: 17 Aug 90 13:41:12 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Reply-To: IBM 370 Assembly Programming Discussion List
              <ASM370@OHSTVMA.BITNET>
Distribution: inet
Organization: The Internet
Lines: 22

I believe you said that you were a neophyte with Assembler.  If so, then
I do not recommend that you try this at home...

...however, probably the *best* way to do what you want is to define a
SUBCOMmand environment in your Assembler program before invoking the
REXX macro, and change the REXX macro to pass its "output" back to you
via your SUBCOMmand entry.  E.g., if your SUBCOMmand environment is
called 'ZORN', then the REXX macro would say, e.g.,

         address ZORN 'OUTPUT' text

This gives your Assembler routine a chance to "digest" the output as it
is being generated.  For details, look in the "Application Development
Reference for CMS" and the "Application Development Guide for CMS"
manuals for "SUBCOM".

Lacking the time or motivation to do the SUBCOM thing, it is probably
best to have the REXX macro write its output into a file (e.g., using
EXECIO) and then read the file back in after the REXX macro is done.

      John Pershing
      IBM Research, Yorktown Heights