That's exactly what it sounds like, but, per p.3 of "Streamlining Your
Pipes", we are using RITA MODULE. (I don't think we actually had a
choice. :-) )
We use a configuration variable PIPE that we set to RITA when we want to
get performance info., so we know that the programs haven't changed.
Our pipe statements look like:
Pipe "(listerr end ? name" UsedName"."ExecType"."LineNo()")",
...
A number of programs all show the same problem. Since these programs
sub-filters all receive and set the callers variables correctly when
PIPE is "pipe", and not when it's "rita", it would seem to be something
external to the programs.
Any ideas?
- Hobart
-----Original Message-----
From: CMSTSO Pipelines Discussion List
[mailto:[EMAIL PROTECTED] On Behalf Of Rob van der Heij
Sent: Wednesday, May 28, 2008 5:14 PM
To: [email protected]
Subject: Re: [CMS-PIPELINES] FW: Rita+*VAR*+CALLPIPE
On Wed, May 28, 2008 at 4:08 PM, SPITZ, HOBART CTR DFAS
<[EMAIL PROTECTED]> wrote:
> When we run RITA and we have a filter, any *VAR* stages (REXXVARS,
VAR,
> VARLOAD, VARSET, etc.), in a CALLPIPE, seem to not be able to get the
> variables that they get when we run without RITA.
>
> Are we doing something wrong?
Could it be you have a PIPE or RITA EXEC involved. That would
introduce another level of execcomm and mess up things.
Rob
