ACD Related Error Messages

ACD information is kept as an MPE "pseudo extent". A pointer to this "pseudo extent" is maintained for each file or device which has an ACD. If you are attempting to delete an ACD, the pseudo extent will be deallocated by MPE. Even if the operation fails and you get this warning, the ACD will still be deleted.

If you are attempting to add additional entries to an existing ACD, then it may be necessary to create a larger ACD (and therefore allocate a larger pseudo extent). After the new ACD is created, MPE will deallocate the old pseudo extent automatically. You may get the warning if the deallocation of the old pseudo extent fails. The new ACD entries succeed regardless, and an ACD with all of the desired entries will be associated with the device or file.

There is a version number associated with the MPE software which implements ACDs. This version number is placed in the ACD itself when an ACD is created. Each time an ACD is accessed the version number in the ACD is checked against the current version number for the software running on your system.

If you are attempting to delete an ACD and these numbers do not match, then MPE will issue this warning message. Note that the version numbers here are not the same as the version update fix (V.UU.FF) numbers associated with MPE. Instead they are internal version numbers associated only with the ACD component of MPE.

You must specify a standard MPE user specification. This specification must take one of the following forms:

You must use "fully qualified" user specifications (for example, you cannot put the username by itself and default acctname to the logon account).

Your ACD specification contains a duplicated access mode in the list of access modes specified for a single ACD entry.

Examples:

:ALTSEC FILENAME;NEWACD=( R,W,R: FRED.SMITH )

The :ALTSEC command shown above is illegal because read access is specified twice for a single ACD entry (corresponding to user FRED.SMITH).

:ALTSEC FILENAME;NEWACD=( R,W: JOE.SMITH; R,X: BILL.SMITH )

In the :ALTSEC command above, however, it is not illegal to specify read access twice because it is for two different ACD entries (corresponding to JOE.SMITH and BILL.SMITH).

Your ACD specification contains a duplicated permission in the list of access modes specified for a single ACD entry.

Examples:

:ALTSEC FILENAME;NEWACD=( R,W,RACD,X,RACD: FRED.SMITH )

The :ALTSEC command shown above is illegal because read ACD permission is specified twice for a single ACD entry (corresponding to user FRED.SMITH).

:ALTSEC FILENAME;NEWACD=( R,W,RACD: JOE.SMITH; R,X,RACD: BILL.SMITH )

In the :ALTSEC command above, however, it is not illegal to specify read ACD permission twice because it is for two different ACD entries (corresponding to JOE.SMITH and BILL.SMITH).

You have specified access modes for a given entry which are contradictory. The examples below will clarify what is meant by contradictory access modes.

Examples:

:ALTSEC FILENAME;NEWACD=( R,W,NONE: @.@ )

The :ALTSEC command shown above is illegal because you are granting read and write access to the same user (@.@) you are granting no access.

:ALTSEC FILENAME;NEWACD=( R,W: @.@; NONE: BILL.SMITH )

In the :ALTSEC command above, however, it is not illegal because you are granting read and write access to a different user than the one to whom you are granting no access.

You have specified an invalid access mode. Only the following access modes are legal in an ACD specification:

   Mode                     Meaning 



    R                    Read access allowed

    W                    Write access allowed

    X                    eXecute access allowed

    L                    Lock access allowed

    A                    Append access allowed

    NONE                 No access allowed

    RACD                 Read ACD permission

Upper or lower case is allowed. You may specify each mode only once for a given ACD entry. If NONE is specified then you may not specify any other access mode or permission for the same entry.

You must specify a standard MPE user specification. This specification must take one of the following forms:

You must use "fully qualified" user specifications (for example, you cannot put the username by itself and default acctname to the logon account).

You must specify a standard MPE user specification. This specification must take one of the following forms:

You must use "fully qualified" user specifications (for example, you cannot put the username by itself and default acctname to the logon account).

You must specify a standard MPE user specification. This specification must take one of the following forms:

You must use "fully qualified" user specifications (for example, you cannot put the username by itself and default acctname to the logon account).

You must specify a standard MPE user specification. This specification must take one of the following forms:

You must use "fully qualified" user specifications (for example, you cannot put the username by itself and default acctname to the logon account).

You must specify a standard MPE user specification. This specification must take one of the following forms:

You must use "fully qualified" user specifications (eg: you cannot put the username by itself and default acctname to the logon account).

The user attempting to manipulate the ACD does not have sufficient capabilities, or is not the creator of the file.

The capability requirements for manipulating an ACD are as follows:

a user with SM capability can manipulate any ACD;

a user with AM capability can manipulate any ACD associated with a file in the account for which he/she has AM capability;

only a user with SM capability can manipulate device ACDs.

The creator of the file is not required to have any specific capabilities to manipulate the ACD.

Notice, however, that SM or AM capability always takes precedence over the permissions granted explicitly within the ACD. Even if you have specified that MANAGER.SYS has no access, he or she can still access the ACD.

The user attempting to read the ACD does not have sufficient capabilities, is not the creator of the file, or has not been granted explicit "read ACD" (RACD) permission.

The capability requirements for reading an ACD are as follows:

a user with SM capability can read any ACD;

a user with AM capability can read any ACD associated with a file in the account for which he/she has AM capability;

the creator of the file can read the ACD.

Users granted "read ACD" (RACD) permission can read an ACD regardless of their capabilities. Note that SM or AM capability always takes precedence over the permissions granted explicitly within the ACD. Even if you specify that MANAGER.SYS has no access, he or she can still do so.

The user attempting to copy the ACD does not have sufficient capabilities, is not the creator of the file, or has not been granted explicit "read ACD" (RACD) permission.

The capability requirements for copying an ACD are as follows:

a user with SM capability can copy any ACD;

a user with AM capability can copy any ACD associated with a file in the account for which he/she has AM capability;

the creator of the file can copy the ACD.

Users granted "read ACD" (RACD) permission can copy an ACD regardless of their capabilities. Note that SM or AM capability always takes precedence over the permissions granted explicitly within the ACD. Even if you specify that MANAGER.SYS has no access, he or she can still do so.

A syntax or semantic error occurred while parsing an ACD specification in an ACD indirect file. This message indicates the "pair number" where the error occurred. The actual syntax or semantic error will be stated in the next message issued by the command interpreter.

If the ACD specification is for any of the following :ALTSEC operations ;ADDPAIR, ;REPPAIR, ;NEWACD, then a pair will consist of a modes specification followed by a list of users. If the ACD specification is for the ;DELPAIR operation then a pair refers to the user name (the modes specification is not necessary).

Examples:

   :ALTSEC filename;NEWACD=indirect 



      where indirect contains: 



        (r,w,l:user1.acct1, user2.acct2; none: @.@) 



   :ALTSEC  filename;DELPAIR=indirect 



      where indirect contains: 



        (user1.acct1, user2.acct2, @.acct3, @.@)