CMS Pipelines does not care which kind of variable environment it accesses. Thus it has no concept of caller type. However, if the EXECCOMM environment supplies a source string, it can be extracted using REXXVARS, but that is as far as it goes.
j. On 1/25/07, Schuh, Richard <[EMAIL PROTECTED]> wrote:
Thanks. Rob was a faster typist, but he only pointed the way. I have already included the code (after finding out that the running EXEC was gen 1 and the caller, gen 2). It would have been nice if DMSCALLR and Pipelines had been consistent. I think that the two are imbedded now so that it is too late for an RCF to do any good. Regards, Richard Schuh -----Original Message----- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of Don Russell Sent: Wednesday, January 24, 2007 4:40 PM To: [email protected] Subject: Re: EXECCOMM Environment Schuh, Richard wrote: > > I must be losing it. I do not remember how to tell if an EXEC was > called from another REXX or EXEC2 EXEC other than using a pipe to > reach back and see if it touches anything. Is there a built-in > function or a CSL call for doing this, or is using a pipe the best > solution? > > Regards, > Richard Schuh > From the archives...ref: http://listserv.uark.edu/scripts/wa.exe?A2=ind0606&L=ibmvm&T=0&P=37120 It has a nice example of using DMSCALLR Don Russell
