If memory serves: If you have an active SECUSER, the console output is presented there rather than to whatever the virtual machine would like to see.
I think you're snookered. j. 2010/3/31 van Sleeuwen, Berry <[email protected]> > Hello listers, > > We have the CMS machine MONWRITE collecting MONITOR records in a > pipeline. The PIPE should end when issuing MSG MONWRITE STOP. Now in one > VM it does, in the second VM it doesn't. > > The exec running is: > > 'SET MSG IUCV' > 'SEGMENT LOAD MONDCSS' > 'PIPE (end \) STARMSG', /* 1-8 msgclass 9-16 uid 17-* msg */ > '| locate 17.4 /STOP/', /* Stop when STOP is issued */ > '| a: gate strict', /* Sever connections */ > '\ STARMON MONDCSS SHARED', /* connect to MONITOR */ > '| a:', /* Sec input to gate */ > '| moncoll' /* Process monitor records */ > 'CP LOGOFF' > > I have found why the MONWRITE can't be stopped but I haven't found the > way to solve this. The machine has spooled it's console to OPERATOR so > that OPERATOR logs the console in PROP. When I SET SECUSER MONWRITE OFF > the STARMSG stage feeds the STOP message into a GATE STRICT. But with > SECUSER OPERATOR it looks like this message doesn't get through. So it > looks like the secondary console prevents the MSG to arrive at the > MONWRITE console. > > How can I get the MONWRITE to react upon the CP MSG MONWRITE STOP > message? > > Met vriendelijke groet/With kind regards, > Berry van Sleeuwen > Flight Forum 3000 5657 EW Eindhoven > > ( +31 (0)6 22564276 > > > > > > Atos Origin <http://www.atosorigin.com/> > > > MO CF SC Mainframe Services > > > > > >
