Got it.  Thanks for all the help.

-----Original Message-----
From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf 
Of Dean, David (I/S)
Sent: Tuesday, June 08, 2010 2:16 PM
To: IBMVM@LISTSERV.UARK.EDU
Subject: Re: MONDCSS segment update

Have the nss segment done
Have monwrite user set up
Doing xautolog monwrite from maint
Why does it keep saying inactive??


q mon
MONITOR EVENT INACTIVE    BLOCK    4     PARTITION    0
MONITOR DCSS NAME - MONDCSS
CONFIGURATION SIZE       68 LIMIT         1 MINUTES
CONFIGURATION AREA IS FREE
USERS CONNECTED TO *MONITOR - MONWRITE           PENDING-CONFIG



-----Original Message-----
From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf 
Of Dean, David (I/S)
Sent: Tuesday, June 08, 2010 11:41 AM
To: IBMVM@LISTSERV.UARK.EDU
Subject: Re: MONDCSS segment update

I am positive I did not do what I want.  I can kill the users since they are 
part of this project.  If I do that and run saveseq mondcss will this 
straighten it out? 



-----Original Message-----
From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf 
Of Rob van der Heij
Sent: Tuesday, June 08, 2010 11:30 AM
To: IBMVM@LISTSERV.UARK.EDU
Subject: Re: MONDCSS segment update

On Tue, Jun 8, 2010 at 5:23 PM, Dean, David (I/S) <david_d...@bcbst.com> wrote:
> Ok ,I have successfully(?) created two MONDCSS segs in the same address, how 
> do I get rid of one?

No, it's not successful yet... once you SAVESEG MONDCSS it will
activate the skeleton (0038) and purge the current (0011). But you
can't as long as the monitor is active and someone is connected to
*MONITOR (the user count of 2 says so).
And from what I can see here, the old and new are the same. So I'm not
sure you did what you wanted to do.

Rob

>
>
> 0011 MONDCSS  CPDCSS     N/A    09000  09FFF   SC  R  00002   N/A       N/A
> 0010 GUICSLIB DCSS       N/A    01F00  01FFF   SR  A  00000   N/A       N/A
> 0009 CMSFILES DCSS       N/A    01900  01BFF   SR  A  00003   N/A       N/A
> 0008 SVM      DCSS       N/A    01900  019FF   SR  A  00000   N/A       N/A
> 0007 CMSPIPES DCSS       N/A    01800  018FF   SR  A  00009   N/A       N/A
> 0005 INSTSEG  DCSS       N/A    01400  016FF   SR  A  00009   N/A       N/A
> 0003 DOSINST  DCSS       N/A    00900  0090F   SR  A  00000   N/A       N/A
> 0038 MONDCSS  CPDCSS     N/A    09000  09FFF   SC  S  00000   N/A       N/A
>
> -----Original Message-----
> From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On 
> Behalf Of Barton Robinson
> Sent: Monday, June 07, 2010 4:09 PM
> To: IBMVM@LISTSERV.UARK.EDU
> Subject: Re: MONDCSS segment update
>
> Totally safe. Only users of the star monitor function will notice - so
> the monitor does need to stop and start.
>
> Dean, David (I/S) wrote:
>> Is it safe to change MONDCSS sizes on running system, i.e., I won't run
>> over memory being used somewhere else?
>>
>> David M. Dean
>> Information Systems
>> BlueCross BlueShield Tennnessee
>>
>>
>>
>>
>> -----------------------------------------------------
>> Please see the following link for the BlueCross BlueShield of Tennessee 
>> E-mail disclaimer:  http://www.bcbst.com/email_disclaimer.shtm
> -----------------------------------------------------
> Please see the following link for the BlueCross BlueShield of Tennessee 
> E-mail disclaimer:  http://www.bcbst.com/email_disclaimer.shtm
>



-- 
Rob van der Heij
Velocity Software
http://www.velocitysoftware.com/
-----------------------------------------------------
Please see the following link for the BlueCross BlueShield of Tennessee E-mail 
disclaimer:  http://www.bcbst.com/email_disclaimer.shtm
-----------------------------------------------------
Please see the following link for the BlueCross BlueShield of Tennessee E-mail 
disclaimer:  http://www.bcbst.com/email_disclaimer.shtm
-----------------------------------------------------
Please see the following link for the BlueCross BlueShield of Tennessee E-mail 
disclaimer:  http://www.bcbst.com/email_disclaimer.shtm

Reply via email to