Ray Mansell (I think it was) wrote CALLER, which also accesses the caller's environment. It may be at the IBM VM download page.
But how come such a module is acceptable when the PIPE module is not? They do the same and affect the SVC204 stack in the same way. j. On 1 February 2011 16:14, DUGALEIX Michaël <[email protected]>wrote: > Hello everyone, > > Is there some non-pipeline equivalent to this instruction, on z/VM, in > "pure-rexx" (rexx with no CMP or CP) : > "PIPE rexxvars 1 | spec w4 1 | var callingProgram" > > ... which, used in a program PRG2 EXEC, gives me the name of the program, > PRG1 EXEC, that called PRG2 EXEC ? > > > I searched in the "DMS..." routines, discovered "DMSCALLR" which seemed > nice, and tried this : > call CSL "DMSCALLR" retcode caller_id 3 > > ... which gives me what I want (precisely : "EXEC PRG1") for > non-compiled EXEC, but which says that the calling program is "EAGRTPRC..." > for compiled-EXEC. > > > By the way, I'm asking this because I'm writing a tool to analyse the calls > to commands/programs in our EXEC programs (something similar to TRACEXEC, > I'd say). > And I can't use the usual commands (PIPE, ERASE, ...) in this tool if I > want to analyse the calls to theses commands. > > > Thanks > Michaël >
