You need to issue WAKEUP +0 (IUCVMSG before you send the command to the primary machine. Then in your REXX exec, loop on WAKEUP +xx (IUCVMSG while rc=5 At the end, issue WALEUP RESET The hard thing is knowing when the primary machine has fisched sending its response (i.e. having a value for +nn)
You can also use PIPE STARMSG as alternative to WAKEUP. 2007/2/28, Dave Hansen <[EMAIL PROTECTED]>:
Hello group, I found out SCIF changes things. I logon and I normally don't get any traffic until I send something to the other virtual machine I am a secondary console for and then I get a response. Without SCIF I can get my message in REXX by issuing a command and then doing a PULL. However with SCIF I get a VM READ as I watch the message being returned while I am tracing the exec. I have used wakeup before and then it captures the 'activity' by return code. I could spool my console and close it, but then I probably won't be able to trap the spoolid. Yes, I could set something unique in the spool name or type. But this probably isn't the best solution. Any ideas? Thank you, Dave H.
-- Kris Buelens, IBM Belgium, VM customer support
