[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference csc32::consolemanager

Title:POLYCENTER Console Manager
Notice:Kits, Scans, Docs on CSC32:: as PCM$KITS:,PCM$DOCS:, PCM$SCANS:
Moderator:CSC32::BUTTERWORTH
Created:Thu Aug 06 1992
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:1541
Total number of notes:6564

1284.0. " Event attribute "bell count" doesn't honor "0" (zero) " by CSC32::D_DONOVAN (SummaNulla(The High Point of Nothing)) Tue Apr 30 1996 16:11

       I want to post this issue to a wider audience before doing an IPMT
on this.  Please REPLY if you find different behavior or any noted
restrictions I may have overlooked.

Thanks,

Dennis

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Configuration:

        OpenVMS Alpha V6.1
        PolyCenter Console Mangager V1.6-201

Problem:

        Console Manager doesn't honor a "0" (zero) setting for the
        "C3 Event Priority Attributes - Bell Count".

Discussion:

        After receiving this issue from a customer I tested it out
        on one of my Lab systems.  I set the "Bell Count to - 0" on
        the slider saved the C3 configuration and examined my
        "CONSOLE$C3.DAT" file which had:

                                .
                                .
                                .
                        MAJOR_COLOR: #FFFF0000FFFF
                        MAJOR_BELL: 0
                        MAJOR_VOLUME: 100
                                .
                                .
                                .


        I then made up a "major" test event and associated it with a
        system for a test.  As the customer stated the "% volume" will
        change but the "bell count" will still "beep" once with the above
	settings.

        Both the customer and I used the "$SET WATCH" facility to ensure
        that our user "CONSOLE$C3.DAT" file was being opened and read.
        However I noticed that after changing the "bell count" to "0"
        and restarting my C3 the "C3 Event Priority Attributes" pop-up
        had a "1" in my MAJOR priority slider rather than a "0".

        I ran through the ECO2 listings and couldn't find any specific
        code that set the "MIN_" value but may not have been looking in
        the right places.
T.RTitleUserPersonal
Name
DateLines
1284.1ALEXWS::ELLAWed May 01 1996 08:377
Hello,

	We know about this problem. You can open IPMT case with low priority.
	We will include it to wishlist for future release.

Regards,
	Ella.