Kees, >* When the message is an action message (descriptor code 1,2,3 or 11) >* and not a WTOR, domaction nodelmsg and hold disable is specified. >* This signifies that the NetView program does not expect to receive a >* DOM for this message and will not keep any internal record of it >* for future deletion by a DOM request. The message is not hold on any >* opretator screen. >********************************************************** ************* > IF ACTIONMG(1)='1' & IFRAUWF1(6)¬='1' THEN > DOMACTION(NODELMSG) HOLD(DISABLE) CONTINUE(Y); > Wow! The discussion currently raging in the ETR is that I say HOLD(DISABLE) fixes the problem and NetView disagrees. They say that the HOLD parm shouldn't have any influence. (Note they said *shouldn't*! :-)
I didn't know about the ACTIONMG keyword, though. That looks better than my current 'solution': IF DESC(x)='1' THEN DOMACTION(NODELMSG) HOLD(DISABLE) CONTINUE(Y); for x=3..10,12..16 I was reluctant so far to set this unequivocally for *all* descriptor codes, but your post gives me the confidence to put this into my sandplex, re-IPL (to see if it still works :-) and then introduce to the production plexes. - I have also posed the question to NetView why they *always* assume that an action message MUST HAVE a DOM. And have based their design on that. My take is that a DOM *may* occur, but doesn't *have to*. And I think that that is the cause for a lot of contortions. - Best regards, Barbara ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
