From:	SMTP%"SUPSER-L@WKUVX1.WKU.EDU" 21-APR-1994 10:47:43.45
To:	EVERHART
CC:	
Subj:	RE: Privileges for SUPERVISOR under VMS 6.0

X-Listname: Supervisor Series Discussion List <SUPSER-L@WKUVX1.WKU.EDU>
Warnings-To: <>
Errors-To: owner-supser-l@WKUVX1.WKU.EDU
Sender: owner-supser-l@WKUVX1.WKU.EDU
Date: Wed, 20 Apr 1994 23:10:43 -0400 (EDT)
From: "G. Del Merritt" <del@giant.intranet.com>
Reply-To: SUPSER-L@WKUVX1.WKU.EDU
Subject: RE: Privileges for SUPERVISOR under VMS 6.0
To: SUPSER-L@WKUVX1.WKU.EDU, goathunter@ALPHA.WKU.EDU
Message-Id: <0097D42AF463B880.21402A83@giant.IntraNet.com>
Content-Transfer-Encoding: 7BIT

In-reply-to: UUCP%"goathunter@ALPHA.WKU.EDU" 's message of 20-APR-1994 17:33:07.49
>Since AUDIT is one of the new privileges, it sounds like they (DEC)
>may have screwed up when adding the messages. 8-(  Meaning that it
>sounds like what was SS$_NOSHARE under V5.x is SS$_NOAUDIT under V6.x.
>I don't have a V6.x system, so I can't check it to be sure.

First I said "Hunter's right".  Well, sort of.  From OpenVMS_V60_RELNOTES.TXT:

                                                Programming Release Notes
                                                          3.2 CORRECTIONS


        3.2.7 STARLET Error Message Values

        V6.0  The values for several error messages in the STARLET
              library have been corrected. The new values are as follows:
              ___________________________________________________________

              Symbolic Name    Old Value        New Value
              ___________________________________________________________

              SS$_NOUPGRADE    %X00002914       %X00002904

              SS$_NOGRPPRV     %X0000291C       %X00002914

              SS$_NOREADALL    %X00002924       %X0000291C

              SS$_NOSHARE      %X0000292C       %X000028FC
              __________________________________________________________

              The new values ensure that the privilege-specific error
              messages are contiguous and exactly match the order of the
              privilege bit declarations defined in the $PRVDEF macro.
              The new $CHECK_PRIVILEGE system service depends on this
              type of definition.

              The order of these messages is significant because
              applications tend to reference these messages as a list.
              There is a direct relationship between these error messages
              and the privilege bit positions. Given a privilege bit
              position, an application can compute the appropriate error
              message by using the following formula:

              error_message = SS$_NOPRIVSTRT + (bit_position * 8) + 
                                                             STS$K_SEVERE


Del Merritt                                                  del@IntraNet.com
IntraNet, Inc., One Gateway Center #700, Newton, MA  02158
Voice: 617-527-7020; FAX: 617-527-6779
All my opinions.                                      Just say no to Clipper.