Let's start over because this will get confused if we don't.
My REXX code has a comment line at the start.
Driver EXEC (REXX) invokes, via a CALL, MISSLFS passing a
variable to it which SAY in MISSLFS shows it got.
MISSLFS EXEC *was* copied from MISSLFS REXX so I can experiment
with it (yes, in the environment it normally runs in it is a STAGE).
CALLPIPE in MISSLFS EXEC terminates with (-3).
I can't seem to figure out why this is.
Doesn't -3 mean a problem with the environment?
Any suggestions for this?
Steve Thompson
On 8/10/22 11:35, John P. Hartmann wrote:
Apart from what else can be said, your program is interpreted
as EXEC2, not REXX. It lacks the leading comment to identify
it as such.
On 8/10/22 17:30, Steve Thompson wrote:
Hi. I'm re-sending this because of somehow getting
unsubscribed.... And issuing commands to change some default
settings. etc.
So I have not seen anything from the list since 26JUN22.
-------------
I'm trying to test some code to figure out why I'm not getting
the results I think I should be getting from CHOP.
The code is being used by another routine, and I thought it
would work for what I need, so I modified the CHOP stage and
I'm not getting what I need.
So I built a "driver" REXX to invoke the routine that is using
'CALLPIPE filefast xxx xxx *' ,
and this is returning (-3).
Here is my driver:
---------------------
TRACE "F"
call 'MISSLFS' 'LX1000 /library'
xx=RC
SAY "CALL returned RC="xx
EXIT xx
---------------------
I'm doing this from the command line in CMS. So I tried
ADDRESS COMMAND (immediately before the call) and still get (-3).
I've been scanning the CMS Pipelines UGDE & REF and I am not
seeing what is wrong with this.
Could someone point me at the problem, or what page of what
manual I should be looking at?
I'm just getting started with CMS pipes and the VM List folks
pointed me to this list....
Regards,
Steve Thompson
