I don't think that NetView will change the colors of messages on the MVS
console, only within NetView, either in NetView's log or on a operator
whois logged on and is setup to receive those messages.
I don't think you can change the color with re-issuing or using a exit.
I would have to read up on and test using MSGGFGPA.
When you "re-issued" the message with WTO did you change the message
ID? If not, then the ID is still $HASP395 and will still be suppresed.
Now what I setup is a CLIST called HIGHLITE and the code is:
/* HIGHLITE */
TRACE ERROR
/*-------------------------------------------------------------------*/
/* HIGHLITE: Issues WTO as Critical eventual action. */
/* Text is highlited and help on console. Used for */
/* "OPERATOR NOTICE THIS NOW" type stuff. */
/* */
/*-------------------------------------------------------------------*/
ROUTCDE = '01' /* 2 - Operator Information. */
DESC = '0100' /* SET DESC CODE AS IMMED ACTION (2). */
MCSFLAG = '00000000' /* MCSFLAG = 0 */
LINETYPE= ' ' /* ' ' - Single line WTO. */
'WTO ###'ARG(1)''
EXIT
You could then code the following in your DSIMSGxx
IF MSGID = '$HASP050' & TEXT = MSG
THEN EXEC(CMD('HIGHLITE 'MSG) ROUTE(ONE *))
DISPLAY(N) NETLOG(N) CONTINUE(Y);
This not only makes the message highlighted on the console it makes it
held. the MSGID is changed because of adding the ### to the begining
This way the operator must manually remove it.
Do NOT test this with a message that comes up often. As the operators
must manually remove the message (assuming you don't have your consoles
in roll mode) they will hate you if they have to manually remove a
message that pops up all of the time. On top of the fact that it could
fill your console buffers.
However, IIRC $HASP050 gets issues as a action WTO normally.
Wallace, Jason wrote:
I understand I am responding to a really old message, but I have been
stuck on this very issue for the past few days and haven't been getting
the best of luck.
Unfortunately I have very limited Netview experience, but what am I
missing.. why doesn't this work?
(We are testing with "job ended" messages since they appear constantly
on the master console. The real msgid we would like to change is
$HASP050 for spool shortages.)
IF MSGID='$HASP395' THEN
COLOR(RED);
I entered that as a new DSIPARM member, ran the AUTOTBL command and
successfully added it to the Automation Table, but the messages on the
master console never changed color. I ran a Netview report and verified
that the messages were being trapped, but it was as if the COLOR parm
simply did not function. (We are using Netview V1R4.)
I have also tried suppressing the original message and creating a
CNMCLST exec that generated a new WTO message with MSGGFGPA =
'00F20000'x (which means "make the message red"), but that also didn't
work.
The only thing that works is to create the custom message with a
descriptor code of 1.
Questions:
- Why doesn't "COLOR(RED)" work?
- Why doesn't MSGGFGPA work? (Would it have something to do with these
not being "MDB messages"? The Netview Automation manual says that
MSGGFGPA only works on those message types and not others.)
- How do I change the color of an existing message without creating a
new one? (ansd without using an MPF exit. My supervisor avoids exits for
maintenance reasons.)
Any ideas?
Thank you,
Jason Wallace
[EMAIL PROTECTED]
Systems Analyst
Oklahoma State University IT Dept.
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
