Re: REXX EXEC - Trapping console messages w/SCIF

2007-03-11 Thread Alan Ackerman
On Wed, 28 Feb 2007 10:28:07 -0600, Dave Hansen <[EMAIL PROTECTED]> wrote: >Hello group, > > I found out SCIF changes things. I logon and I normally don't get an y traffic until I send something to the other virtual machine I am a secondary >console for and then I get a response. Without SC

Re: REXX EXEC - Trapping console messages w/SCIF

2007-02-28 Thread Kris Buelens
2007/2/28, Dave Hansen <[EMAIL PROTECTED]>: David and Kris, Thank you for your help. I trap to a stem and I'm back to figuring out my 'logic'. It's been a while since a wrote a pipe. I saw they can still be written in EXEC2. Maybe VMFOPT still works too. Thanks again, Dave H.

Re: REXX EXEC - Trapping console messages w/SCIF

2007-02-28 Thread Dave Hansen
David and Kris, Thank you for your help. I trap to a stem and I'm back to figuring out my 'logic'. It's been a while since a wrote a pipe. I saw they can still be written in EXEC2. Maybe VMFOPT still works too. Thanks again, Dave H. Hennepin County

Re: REXX EXEC - Trapping console messages w/SCIF

2007-02-28 Thread David Kreuter
-Original Message- From: The IBM z/VM Operating System on behalf of Dave Hansen Sent: Wed 2/28/2007 1:54 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: [IBMVM] REXX EXEC - Trapping console messages w/SCIF Hello, I am still having trouble with my

Re: REXX EXEC - Trapping console messages w/SCIF

2007-02-28 Thread Dave Hansen
Hello, I am still having trouble with my SCIF exec. Here it is: /* rexx */ trace r 'set msg iucv' 'pipe (endchar \)', '|starmsg CP Q MUDLAKE', '| console', '\', 'literal +2', '| delay', '| pipestop' parse upper pull input '-' var if var = 'dsc' then nop else do say 'mudlake not lo

Re: REXX EXEC - Trapping console messages w/SCIF

2007-02-28 Thread Kris Buelens
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)

Re: REXX EXEC - Trapping console messages w/SCIF

2007-02-28 Thread David Kreuter
ted to end the wait sooner. See the help for PIPE PIPESTOP. It has an example of trapping RSCS output, works similar although it is of a different type. David -Original Message- From: The IBM z/VM Operating System on behalf of Dave Hansen Sent: Wed 2/28/2007 11:28 AM To:

REXX EXEC - Trapping console messages w/SCIF

2007-02-28 Thread Dave Hansen
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. Howev