You might consider using the CP SILENTLY command. From the help file for
SILENTLY:
Examples
1. To attach device 1234 to user MVS and suppress the messages sent to
the
issuer, to the user who is the object of the ATTACH, and to the
system
operator:
a. Enable the ATTACH command for response suppression:
modify command attach silent
b. Issue the SILENTLY command for ATTACH:
silently attach 1234 to mvs as 1234
If you are willing to add a 'NOMSG' option to the ATTACH command, might you
be willing to precede the ATTACH command with 'SILENTLY' instead? I do not
know if this meets your needs or not. Any ATTACH command that is not
preceded with SILENTLY, will continue to operate as it does now. For any
ATTACH command that is preceded with SILENTLY, message output is
suppressed. For more information, please see the HELP files for CP SILENTLY
and CP MODIFY COMMAND or get the information from the CP Commands and
Utilities Reference book.
Doug Breneman z/VM Development IBM Endicott, NY
From: "Huegel, Thomas" <[EMAIL PROTECTED]>
To: [email protected]
Date: 07/09/2008 12:05 PM
Subject: Re: The Programmable Operator Facility
Personally I think ATTACH and DETACH (and others too i.e. DIAL) should have
a NOMSG type option to just eliminate the message alltogether.
-----Original Message-----
From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED]
Behalf Of Kris Buelens
Sent: Wednesday, July 09, 2008 11:00 AM
To: [email protected]
Subject: Re: The Programmable Operator Facility
In PROP, logging is all or nothing. VM:Operator has a NOLOG option, I
don't know about IBM Operations Manager.
At the other hand: DASD isn't that expensive, incomplete log files
make debugging less easy. Alternatively, you could postprocess the
log file of the previous day and code a PIPE filter to remove what you
don't want to keep.
2008/7/9 Ray Waters <[EMAIL PROTECTED]>:
>
> We run z/VM 520 and use PROPST to filter messages to the OP1 console. We
filter several commands including ATTACHED and DETACHED commands.
>
>
>
> I would like to filter other messages such as ATTACHED and DETACHED from
going to the LOG FILE (LGYYMMDD XXXXXX) on Operator's 191 MDISK. In reading
the CMS Planning and Administration Guide, I don't see how this can be
done. We are a heavy TAPE use shop using DFSMS/RMS and there are just too
many of these messages going to this log file.
>
>
>
> Is there a way to suppress the logging of certain messages?
>
>
>
> Thanks,
>
> Ray Waters
>
> Mainframe Technical Support Analyst
>
> Open Solutions Inc.
> 11 Greenway Plaza, Suite 300
> Houston, TX 77046-1102
>
> Office 713-965-8451
>
> Cell 713-705-5403
>
> Fax 713-965-8405
>
> Email [EMAIL PROTECTED]
>
>
>
> www.bank.opensolutions.com
>
> www.opensolutions.com
>
>
>
>
>
> ________________________________
> NOTICE:
> This e-mail is intended solely for the use of the individual to whom it
is addressed and may contain information that is privileged, confidential
or otherwise exempt from disclosure. If the reader of this e-mail is not
the intended recipient or the employee or agent responsible for delivering
the message to the intended recipient, you are hereby notified that any
dissemination, distribution, or copying of this communication is strictly
prohibited. If you have received this communication in error, please
immediately notify us by replying to the original message at the listed
email address. Thank You.
--
Kris Buelens,
IBM Belgium, VM customer support
