I've got the problem too, but only when the user using TRYFOR has a secondary user. Else it works fine for me. But, as opposed to what you say, the TRYFOR exec captured the response too, that is, I see the response to Q USERID twice: Start DISCONNECT AT 12:17:41 CET THURSDAY 11/18/10 EXEC TRYFOR VMUTIL QUERY USERID VMUTIL AT LUXVMBRS cprc = 0 ********************************************************* The FOR command completed successfully] (Note: The output of the STARMSG stage starts with an 8 character message class. For *ASYNCMD this is always '00000000' (eight zeros) and is removed from the following output.) The end of command record from *ASYNCMD is: VMUTIL 0000000000000046100000000 The number of command response records from *ASYNCMD are >1< The command response records are: VMUTIL 00000000000000460BUE VMUTIL AT LUXVMBRS
********************************************************* The user ID is: >VMUTIL < The token is: >0000000000000046< The end of command record is: User ID: >VMUTIL < Token: >0000000000000046< MsgType: >1< RC: >0000< Lost Messages: >0000< The command responses are: >VMUTIL AT LUXVMBRS< TRYFOR Done ICH70001I BUELENSC LAST ACCESS AT 12:17:24 ON THURSDAY, NOVEMBER 18, 2010 Command accepted z/VM Version 5 Release 4.0, Service Level 1001 (64-bit), built on IBM Virtualization Technology There is no logmsg data FILES: 0098 RDR, 0006 PRT, NO PUN RECONNECTED AT 12:17:41 CET THURSDAY 11/18/10 AUTO LOGON GRAF L0005 BUELENSC USERS = 23 2010/11/18 Buettner, Wolfgang <[email protected]> > 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? > > Wolfgang > > > > Software AG – Group Executive Board: Karl-Heinz Streibich > (Vorsitzender/Chairman), Arnd Zinnhardt, Mark Edwards, David Broadbent, > Josef Bommersbach, Dr. Wolfram Jost, Kamyar Niroumand, Ivo Totev > > Sitz/Registered office: Uhlandstraße 12, 64297 Darmstadt, Germany, – > Registergericht/Commercial register: Darmstadt HRB 1562 - Vorstand/ > Management Board: Karl-Heinz Streibich (Vorsitzender/Chairman), David > Broadbent, Dr. Wolfram Jost, Arnd Zinnhardt; - Aufsichtsratsvorsitzender/ > Chairman of the Supervisory Board: Dr. Andreas Bereczky - * > http://www.softwareag.com* <http://www.softwareag.com/> > ------------------------------ > > *From:* The IBM z/VM Operating System [mailto:[email protected]] *On > Behalf Of *Kris Buelens > *Sent:* Thursday, November 18, 2010 9:30 AM > *To:* [email protected] > *Subject:* Re: Working with *ASYNCMD service > > I just tried TRYFOR on my 5.4 system and all is perfect, no additional > messages anywhere; not in the SPOOL CONSOLE of the target machine, not to a > secondary user. > I did not ehowever that TRYFOR SAMPEXEC does not use ADDRESS COMMAND. > Hence, if you'd have a PIPE EXEC, TRYFOR will use that instead of the PIPE > MODULE. > So, assure you have ADDRESS COMMAND in front of the execs, and change 'pipe > ... to 'PIPE .... > > > 2010/11/18 Alan Altmark <[email protected]> > >> On Wednesday, 11/17/2010 at 09:19 EST, "Buettner, Wolfgang" >> <[email protected]> wrote: >> > I have build a REXX program on base of the TRYFOR SAMPEXEC in order to >> submit >> > FOR commands and receive any response automatically. >> > So far nearly all works fine. >> > >> > The only snag is that in case the virtual machine runs disconnected >> > response from a QUERY SET is placed additionally to the CONSOLE LOG and >> >> > also to the SECUSER's screen if any exists. >> > >> > The same is true if I run TRYFOR EXEC unmodified. >> > >> > Any idea how to avoid that? >> >> You will need to open a PMR and discuss it with the Support Center. Usage >> Note #3 says, "The target of the FOR command will not receive any command >> responses." >> >> 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 >> > > > > -- > Kris Buelens, > IBM Belgium, VM customer support > -- Kris Buelens, IBM Belgium, VM customer support
