Thanks,
Someone else suggested suppressing messages, I did a quick bit of research
on our output and if we suppress CSQX500I, CSQX501I, and CSQX545I it should
reduce the total output by about 90-95% which makes things manageable. This
is discussed in the z/OS System Setup Guide as follows.
Task 21: Suppress information messages
|--------------------------------------------------------------|
| |
| |
| |
|--------------------------------------------------------------|
If your WebSphere MQ system is heavily used, with many channels stopping
and starting, a large number of information messages are sent to the z/OS
console and hardcopy log. The WebSphere MQ-IMS bridge and buffer manager
might also produce a large number of information messages.
If required, you can suppress some of these console messages by using the
z/OS message processing facility list, specified by the MPFLSTxx members of
SYS1.PARMLIB. The messages you specify still appear on the hardcopy log,
but not on the console.
Sample thlqual.SCSQPROC(CSQ4MPFL) shows suggested settings for MPFLSTxx.
See the MVS Initialization and Tuning Reference manual for more information
about MPFLSTxx.
If you want to suppress selected information messages on the hardcopy log,
you can use the z/OS installation exit IEAVMXIT. You can set the following
bit switches ON for the required messages:
CTXTRDTM
Delete the message.
The message is not displayed on consoles or logged in hardcopy.
CTXTESJL
Suppress from job log.
The message does not go into the JES job log.
CTXTNWTP
Do not carry out WTP processing.
The message is not sent to a TSO terminal or to the system message
data set of a batch job.
Notes:
1. For full details, refer to the MVS Installation Exits book.
2. You are not recommended to suppress messages other than those in the
suggested suppression list, CSQ4MPFL.
Regards
Tim A
Art Schanz
<[EMAIL PROTECTED] To: [EMAIL PROTECTED]
IT.FRB.ORG> cc:
Sent by: MQSeries Subject: Re: CHIN with millions of
lines of output
List
<[EMAIL PROTECTED]
N.AC.AT>
18/03/2003 04:17
Please respond to
MQSeries List
Tim,
A simple REXX exec that writes a JES msg to the job log of the CHIN,
initiated by your AO product will do the trick. (I'm pretty sure there is
also be a JES parm/exit that could accomplish the same thing). I wrote an
EXEC that simply writes the date at 00:00 every day - that way, you have
blocks of msgs that only span 24 hrs.
Cheers,
Art
Arthur C. Schanz
Operating Systems Programmer I. - Specialist
Federal Reserve Information Technology
Distributed Systems Engineering
IBM Certified Specialist / Solutions Expert - MQSeries
(804) 697-3889
[EMAIL PROTECTED]
Tim Armstrong <[EMAIL PROTECTED]>
Sent by: MQSeries List To:
<[EMAIL PROTECTED]> [EMAIL PROTECTED]
cc:
Subject: CHIN with
03/11/2003 08:12 PM millions of lines of output
Please respond to MQSeries List
The problem we are having is that on some of our OS/390 systems where the
MQ channel initiator and master address spaces are up and running for weeks
or months at a time we get enormous amounts of output. This makes searching
the job logs using SDSF a prolonged and resource intensive exercise. Has
anyone come up with a way to effectively segment the output?
Regards
Tim A
Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at http://www.lsoft.com
Archive: http://vm.akh-wien.ac.at/MQSeries.archive
Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at http://www.lsoft.com
Archive: http://vm.akh-wien.ac.at/MQSeries.archive
