AH, OK, I understand. We run a monwrite that gets never stopped. Within
MONWRITE we run a custom pipeline, it retrieves data with the STARMON
stage and a second stage waits for the cleanup command with STARMSG. The
cleanup command forces the monwrite machine to cleanup the disks.
Before that we ran the basic MONWRITE and then we stopped the monitor
every day. But we also have PERFKIT running so there was always at least
one user connected to MONITOR. So that's a way for this, just add a user
that connects to the MONITOR and does nothing with the data ("PIPE
STARMON | HOLE").
Op 22-11-10 17:47, Wakser, David schreef:
> It seems (though I did not set this up so I am not certain) that the VM
> users are only not connected for a moment, when things get "reset" (I
> believe monitoring is stopped every hour to send off data, and then
> restarted and the user then becomes re-connected).
>
> The following display (Q MONITOR) shows the following whenever I have
> issued the command (note the connected user LINMON):
>
> q monitor
>
> MONITOR EVENT ACTIVE BLOCK 4 PARTITION 1024
>
> MONITOR DCSS NAME - MONDCSS
>
> CONFIGURATION SIZE 68 LIMIT 1 MINUTES
>
> CONFIGURATION AREA IS FREE
>
> USERS CONNECTED TO *MONITOR - LINMON
>
> MONITOR DOMAIN ENABLED
>
> PROCESSOR DOMAIN ENABLED
>
> STORAGE DOMAIN DISABLED
>
> SCHEDULER DOMAIN DISABLED
>
> SEEKS DOMAIN DISABLED
>
> USER DOMAIN ENABLED
>
> THE FOLLOWING USERIDS ARE ENABLED:
>
> UNIPRD2 UNIPROD UNITEST
>
> I/O DOMAIN ENABLED
>
> THE FOLLOWING DEVICES ARE ENABLED:
>
> 1317-13AF 1417-147A
>
> NETWORK DOMAIN DISABLED
>
> APPLDATA DOMAIN DISABLED
>
> MONITOR SAMPLE ACTIVE
>
> INTERVAL 5 MINUTES
>
> RATE 5.00 SECONDS
>
>
>
> MONITOR DCSS NAME - MONDCSS
> CONFIGURATION SIZE 1536 LIMIT 1 MINUTES
> CONFIGURATION AREA IS FREE
> USERS CONNECTED TO *MONITOR - LINMON
> MONITOR DOMAIN ENABLED
> SYSTEM DOMAIN ENABLED
> PROCESSOR DOMAIN ENABLED
> STORAGE DOMAIN DISABLED
> USER DOMAIN ENABLED
> THE FOLLOWING USERIDS ARE ENABLED:
> UNIPRD2 UNIPROD UNITEST
> I/O DOMAIN ENABLED
> THE FOLLOWING DEVICES ARE ENABLED:
> 1317-13AF 1417-147A
> NETWORK DOMAIN DISABLED
> APPLDATA DOMAIN DISABLED
> Ready; T=0.01/0.01 11:45:06
>
> -----Original Message-----
> From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On
> Behalf Of Berry van Sleeuwen
> Sent: Monday, November 22, 2010 11:44 AM
> To: IBMVM@LISTSERV.UARK.EDU
> Subject: Re: Suppressing messages
>
> But if no one is connected to the monitor, why do you keep monitor
> running?
>
> Do you have PROP running in the zVM OPERATOR? If so, add a rule in the
> PROP RTABLE to suppress HCPMXE6224I.
>
> Op 22-11-10 17:37, Wakser, David schreef:
>
>> I don't want to stop the monitor, just to suppress these messages
>>
> going
>
>> to the z/VM Operator console.
>>
>> -----Original Message-----
>> From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu]
>>
> On
>
>> Behalf Of Berry van Sleeuwen
>> Sent: Monday, November 22, 2010 11:38 AM
>> To: IBMVM@LISTSERV.UARK.EDU
>> Subject: Re: Suppressing messages
>>
>> David,
>>
>> "MONITOR STOP" to stop the CP MONITOR.
>>
>> Regards, Berry.
>>
>> Op 22-11-10 16:55, Wakser, David schreef:
>>
>>
>>> All:
>>>
>>> We have recently implemented DASD monitoring via a LINMON
>>> service machine. The following messages appear every hour on the
>>> Operator console. Is there any way we can somehow suppress these
>>> message, or route them elsewhere?
>>>
>>>
>> Confidentiality Note: This e-mail, including any attachment to it, may
>>
> contain material that is confidential, proprietary, privileged and/or
> "Protected Health Information," within the meaning of the regulations
> under the Health Insurance Portability & Accountability Act as amended.
> If it is not clear that you are the intended recipient, you are hereby
> notified that you have received this transmittal in error, and any
> review, dissemination, distribution or copying of this e-mail, including
> any attachment to it, is strictly prohibited. If you have received this
> e-mail in error, please immediately return it to the sender and delete
> it from your system. Thank you.
>
>>
>>
>>
> Confidentiality Note: This e-mail, including any attachment to it, may
> contain material that is confidential, proprietary, privileged and/or
> "Protected Health Information," within the meaning of the regulations under
> the Health Insurance Portability & Accountability Act as amended. If it is
> not clear that you are the intended recipient, you are hereby notified that
> you have received this transmittal in error, and any review, dissemination,
> distribution or copying of this e-mail, including any attachment to it, is
> strictly prohibited. If you have received this e-mail in error, please
> immediately return it to the sender and delete it from your system. Thank you.
>
>
>
