On Monday, 07/13/2009 at 12:23 EDT, "Gentry, Stephen" <[email protected]> wrote: > I have a simple EXEC that pipes the output of the NETSTAT command to a stem. > > If I issue NETSTAT in a normal CMS session, I get the results back that I > expect. > > When run it in an EXEC containing a PIPE, I get errors from the NETSTAT command. > > Code: PIPE CMS NETSTAT TELNET | stem myStem. > > There two files with the name NETSTAT, one is a MODULE the other an EXEC. When > I run it from a CMS session, the EXEC gets invoked but when I run it from and > EXEC I wrote containing the PIPE command above it seems to invoke the MODULE. > > Is that the way PIPES work? I thought the CMS param set the environment.
PIPE CMS NETSTAT will invoke the NETSTAT EXEC (which invokes the NETSTAT MODULE), just as if you had typed it at the console. By what means did you conclude that PIPE CMS NETSTAT did *not* invoke the exec? Alan Altmark z/VM Development IBM Endicott
