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
[mailto:[EMAIL PROTECTED] On
Behalf Of John P. Hartmann
Sent: Thursday, January 25, 2007 1:33 AM
To: IBMVM@LISTSERV.UARK.EDU
Subject: Re: EXECCOMM Environment
CMS Pipelines does not care which kind of variable environment it
accesses. Thus it has no concept of caller type. However, if the
EXECCOMM
] On
Behalf Of Stracka, James (GTI)
Sent: Thursday, January 25, 2007 6:29 AM
To: IBMVM@LISTSERV.UARK.EDU
Subject: Re: EXECCOMM Environment
Are you referring to:
parse upper source . . program . . synonym .
/* source = environment invocation program type mode synonym address
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
On 1/24/07, Schuh, Richard [EMAIL PROTECTED] 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
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
