Strange Rob, I was convinced SET CPCONIO was not required. With my first test I didn't set it and WAKEUP didn't capture EREP's messages. So, I tested again, and ... geee, my memory was still good, and I didn't made an error in my first test today. I had it right... but now I detected another difference between SECUSER and OBSERVER....
- With SET SECUSER, SCIF messages are captured without CPCONIO set to IUCV - With SET OBSERVER, the SCIF messages are required CPCONIO IUCV And, I concur: setting CPCONIO to IUCV and/or VMCONIO to IUCV makes it much harder to test code, one easily ends in a message loop. 2010/3/2 Rob van der Heij <rvdh...@gmail.com> > On Tue, Mar 2, 2010 at 1:57 PM, Kris Buelens <kris.buel...@gmail.com> > wrote: > > > CP SET CPCONIO IUCV is indeed required to trap SCIF messages (OK by > default > > if you use PROP, VM:Operator, Operations Manager or alike). > > Not unless big changes happened to CP ;-) Any IUCV handler is good > to catch SCIF output (in fact, it sometimes bothers me that we don't > have a SET SCIF xxxx). Setting CPCONIO to IUCV is rather tricky > because you're likely to process your own output again. PROP goes long > and strange ways to associate some virtual machine output with an > action routine (to send it back). > > pipe starmsg | cons > > CP Q SET > MSG ON , WNG ON , EMSG ON , ACNT OFF, RUN OFF > [ snip ] > MIH OFF , VMCONIO OFF , CPCONIO OFF , SVCACCL OFF , CONCEAL OFF > MACHINE ESA, SVC76 CP, NOPDATA OFF, IOASSIST OFF > CCWTRAN ON , 370ACCOM OFF > > CP SET SECUSER ESAMON * > HCPCFX6768I SECUSER of ESAMON initiated. > > CP SEND ESAMON ID > 00000008ESAMON ESAMON : 14:09:18 ESAMON AT RVDHEIJ VIA RSCS > 00000008ESAMON ESAMON : 14:09:18 Ready; T=0.01/0.01 14:09:18 > -- Kris Buelens, IBM Belgium, VM customer support
