On Thursday, 11/18/2010 at 04:52 EST, "Buettner, Wolfgang" <[email protected]> wrote: > Kris, > May be my sentences were missleading. > > It's the requestor's machine, not on the target machine, where the information > apppear. > Meanwhile I have included ADDRESS COMMAND though ensured that there is no > PIPE EXEC. > Never the less the new tests made it even clearer to me that it behaves
> different if running with a terminal or disconnected. > > E.g. TRYFOR TSTUSR QUERY SET > normally delivers the results to the variables and stem.s as coded to the pipe > in the program, > however, if running disconnected just to the log while > "The number of command response records from *ASYNCMD are >0<" . > > Seems something yet hidden switches when going disconnect, too? > I guess this will have to be switched back again by the EXEC or somehow > managed by the pipe? In order to use the FOR command the way you want, you need to connect to the *ASYNCMD system service and specify the PATH option on the FOR command. Without the PATH option, command responses go to the issuer's console instead, causing the *MSG-related behavior you are seeing. Alan Altmark z/VM and Linux on System z Consultant IBM System Lab Services and Training ibm.com/systems/services/labservices office: 607.429.3323 [email protected] IBM Endicott
