ACD Related Error Messages

UNABLE TO DEALLOCATE ACD SPACE. (CIWARN 7100)

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.

No immediate action need be taken. You may wish to report the occurrence to your System Administrator so the lost disc space can be recovered at the next system re-start.

This is only a warning, the operation you performed succeeded!

ACD VERSION DOES NOT MATCH THE CURRENT VERSION. (CIWARN 7101)

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 do not need to take any additional action to correct this problem. The ACD will be deleted successfully. You can create a new ACD, if you wish, without any further side effects.

ACD WAS CORRUPTED PRIOR TO BEING DELETED. (CIWARN 7102)

This message indicates that the ACD you deleted was corrupted. The delete operation succeeded so there is no ACD associated with the device or file in question.

No action needs to be taken. The delete operation has removed the corrupted ACD. You can create a new ACD, if you wish, without any further side effects.

OPERATION FAILED ON SOME DEVICES SPECIFIED. (CIWARN 7103)

The operation which you requested (;NEWACD, :DELACD, ;REPPAIR, ;DELPAIR, ;ADDPAIR, or ;COPYACD) did not succeed for all of the devices in the the device specification. If a device class was specified, the operation failed for one or more devices in the device class. If "@" was specified, indicating all devices on the system, then the operation failed on one or more devices.

Use the :SHOWDEV command with the ;ACD option to determine which devices the command failed on. Then execute the same :ALTSEC command against those devices one at a time to determine the reason for the failure.

MISSING CLOSE PARENTHESIS ")" IN ACD INDIRECT FILE. (CIWARN 7104)

An opening parenthesis was found in the ACD indirect file, however, the corresponding closing parenthesis was not found. This message indicates that the ACD indirect file was syntactically correct except for the missing closing parenthesis.

To avoid this message, add the closing parenthesis to your ACD indirect file. Alternatively, you could delete the opening parenthesis which is already in your ACD indirect file since it is not required.

EXTRA CLOSE PARENTHESIS ")" ENCOUNTERED IN ACD INDIRECT FILE. (CIWARN 7105)

A closing parenthesis was found in the ACD indirect file. However, the corresponding opening parenthesis was not found. This message indicates that the ACD indirect file was syntactically correct except for the extra closing parenthesis.

To avoid this message, add an opening parenthesis to your ACD indirect file. Alternatively, you could delete the closing parenthesis which is already in your ACD indirect file since it is not required.

WILDCARDS NOT ALLOWED IN FILENAME HERE. (CIERR 7221)

You have specified a generic file name which contains wildcards as the target file name or the source file name in the :ALTSEC command.

Repeat the :ALTSEC command for each file in the file set specified by the wildcard.

LOCKWORDS NOT ALLOWED IN GENERIC FILE SETS. (CIERR 7223)

A generic file specification (has wildcards) should not contain a lockword.

Remove the lockword from the generic file specification.

LOCKWORDS NOT ALLOWED. (CIERR 7224)

A lockword was specified as part of a file name.

Remove the lockword from the file name.

INVALID CHARACTER IN DEVICE CLASS NAME. (CIERR 7225)

An invalid character was included in a device class name. Device class names must begin with a letter and they can contain letters or numbers after the first character. The maximum length for a device class name is 8 characters.

Correct the device class name and issue the command again.

NUMBER SPECIFIED IS GREATER THAN 32767. (CIERR 7227)

You have specified an ASCII representation of a number which is larger than 32767. 32767 is the largest number which can be stored in a 16-bit signed integer. This number is too large to be valid in this context.

Re-issue the command using a number which is valid. Notice that the valid range for the number depends on the context in which you are using it. An ldev number, for example, must be less than 999 on MPE/iX.

WILDCARD CHARACTERS, OTHER THAN "@" BY ITSELF, NOT ALLOWED IN DEVICE CLASS NAME. (CIERR 7228)

You have specified a device class name which contains wildcard characters. The use of wildcard characters is not supported for device class names.

Please remove any wildcards included in the device class name specified.

"_" (UNDERBAR) CHARACTER NOT ALLOWED IN DEVICE CLASS NAME. (CIERR 7229)

The "_" (underbar) character was included in a device class name. Device class names must begin with a letter and they can contain letters or numbers after the first character. The maximum length for a device class name is 8 characters.

Remove the "_" (underbar) character from the device class name and re-issue the command.

SINGLE QUOTE "'" CHARACTER NOT ALLOWED IN DEVICE CLASS NAME.(CIERR 7230)

A single quote (') character was included in a device class name. Device class names must begin with a letter and they can contain letters or numbers after the first character. The maximum length for a device class name is 8 characters.

Remove the single quote (') character from the device class name and re-issue the command.

FULLY QUALIFIED NAME NOT ALLOWED HERE. (CIERR 7231)

A fully qualified name is not allowed in this context. This error could apply to either file names or user names.

Please issue the command without specifying the fully qualified file or user name. If it is a file name, omit the group and account. If it is a user name, omit the account.

INVALID USER SPECIFICATION. (CIERR 7250)

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

   username.acctname

   @.acctname

   @.@

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

Correct the user specification to conform to the rules specified above.

DUPLICATE ACCESS MODE SPECIFIED. (CIERR 7251)

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 userFRED.SMITH)

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

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

Delete the duplicate access mode from your list and issue the :ALTSEC command again.

DUPLICATE PERMISSION SPECIFIED. (CIERR 7252)

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).

Delete the duplicate permission from your list and issue the :ALTSEC command again.

CONTRADICTORY ACCESS MODES SPECIFIED. (CIERR 7253)

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.

Change your access modes so that the modes specified for all your entries are not contradictory.

INVALID ACCESS MODE SPECIFIED. (CIERR 7254)

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.

Correct your ACD specification to include only valid access modes.

MISSING OPEN PARENTHESIS "(". (CIERR 7255)

You have omitted the open parenthesis "(" from your ACD specification. Unless you are using an ACD indirect file, both the open and close parentheses are required.

Re-issue the command and add the missing open parenthesis.

MISSING CLOSE PARENTHESIS ")". (CIERR 7256)

You have omitted the close parenthesis ")" from your ACD specification. Unless you are using an ACD indirect file both the open and close parentheses are required.

Re-issue the command and add the missing close parenthesis.

MISSING COLON ":". (CIERR 7257)

You have omitted the colon character from your ACD specification. A colon is required after the access modes and before the user specification.

Re-issue the command and add the missing colon.

UNEXPECTED INPUT ENCOUNTERED AFTER ACD SPECIFICATION. (CIERR 7258)

At the end of your ACD specification, after the last user specification or the closing parenthesis, you have some additional input which is not recognized as be correct.

Delete the extra input and re-issue the command.

INVALID ACCOUNT NAME SPECIFIED. (CIERR 7259)

The account name you have specified is invalid for your system.

Check the account name and re-issue the command specifying the correct account name.

EMBEDDED "@" CHARACTER NOT ALLOWED IN USER SPECIFICATION. (CIERR 7260)

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

   username.acctname

   @.acctname

   @.@

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

Correct the user specification to conform to the rules specified above.

USER NAME MUST BE "@" IF ACCOUNT NAME IS SPECIFIED AS "@". (CIERR 7261)

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

   username.acctname

   @.acctname

   @.@

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

Correct the user specification to conform to the rules specified above.

"#" CHARACTER NOT ALLOWED IN USER SPECIFICATION. (CIERR 7262)

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

   username.acctname

   @.acctname

   @.@

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

Correct the user specification to conform to the rules specified above.

"?" CHARACTER NOT ALLOWED IN USER SPECIFICATION. (CIERR 7263)

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

   username.acctname

   @.acctname

   @.@

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

Correct the user specification to conform to the rules specified above.

MISSING ACCESS MODE IN ACD SPECIFICATION. (CIERR 7264)

You have either omitted an access mode in your ACD specification or you have typed an extra comma (,) in your specification.

Either delete the extra comma or provide the missing access mode when you re-issue the command.

USER SPECIFICATION MUST BE FULLY QUALIFIED. (CIERR 7265)

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

   username.acctname

   @.acctname

   @.@

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

Correct the user specification to conform to the rules specified above.

INVALID USER NAME SPECIFIED. (CIERR 7266)

The user name part of your user specification is invalid for your system. The account name is valid.

Check the user name and re-issue the command specifying the correct user name.

MISSING USER SPECIFICATION. (CIERR 7267)

You have either omitted a user specification or you have included and extra comma (,) in your ACD specification.

Either delete the extra comma or add the missing user specification to the ACD specification when you re-issue the command.

DUPLICATE USER SPECIFICATION ENCOUNTERED IN LIST. (CIERR 7268)

The ACD specification you used contains more than one reference to the same user specification.

Delete the duplicate reference from you ACD specification and re-issue the command.

INTERNAL ERROR NUMBER "-269". (CIERR 7269)

An unexpected internal error has occurred.

Try re-issuing the command. If you still get this error, contact your HP Representative and give him/her the internal error number.

INTERNAL ERROR NUMBER "-270". (CIERR 7270)

An unexpected internal error has occurred.

Try re-issuing the command. If you still get this error, contact your HP Representative and give him/her the internal error number.

INTERNAL ERROR NUMBER "-271". (CIERR 7271)

An unexpected internal error has occurred.

Try re-issuing the command. If you still get this error, contact your HP Representative and give him/her the internal error number.

INVALID LDEV NUMBER SPECIFIED. (CIERR 7272)

You have specified an ldev number which does not correspond to an ldev which is currently configured on your system.

Correct the ldev number and re-issue the command.

INVALID TARGET LDEV NUMBER SPECIFIED. (CIERR 7273)

You have specified an ldev number which does not correspond to an ldev which is currently configured on your system.

Correct the ldev number and re-issue the command.

INVALID SOURCE LDEV NUMBER SPECIFIED. (CIERR 7274)

You have specified an ldev number which does not correspond to an ldev which is currently configured on your system.

Correct the ldev number and re-issue the command.

INVALID DEVICE CLASS NAME SPECIFIED. (CIERR 7275)

You have specified a device class name which does not correspond to any device class currently configured on your system.

Correct the device class name and re-issue the command.

ACD ENTRY DOES NOT EXIST. (CIERR 7300)

You are attempting to access (delete or replace) an ACD entry which does not exist in the specified ACD.

You can list the content of an ACD using the :LISTF ,-2 command (for file ACDs) or the :SHOWDEV command with the ;ACD option (for device ACDs).

THERE IS NO ACD ASSOCIATED WITH THE SOURCE FILE. (CIERR 7301)

You are attempting to copy an ACD from a file which does not currently have an ACD associated with it.

Copy the ACD from a file which actually has an ACD associated with it.

THE ACD ASSOCIATED WITH THE SOURCE FILE IS CORRUPTED. (CIERR 7302)

You are attempting to copy a file ACD which is corrupted.

You cannot copy this ACD because it is corrupted. It is possible to delete the ACD using the ;DELACD option on the :ALTSEC command. This will leave your file without an ACD to protect it. You can also create an ACD for that file (using the ;NEWACD option), or you can copy an existing ACD from another file (using the ;COPYACD option), without deleting the current ACD first. This is only allowed for corrupted ACDs (otherwise the file must not have an ACD prior to using the ;NEWACD or ;COPYACD options).

THERE IS ALREADY AN ACD ASSOCIATED WITH THE TARGET FILE. (CIERR 7303)

You are attempting to create a new ACD for (via the ;NEWACD option), or copy an existing ACD to (via the ;COPYACD option) a file which already has an ACD associated with it.

You must either delete the existing target file ACD prior to executing the :ALTSEC command with the ;NEWACD or ;COPYACD option, or you must use the ;ADDPAIR and ;REPPAIR options to change the existing ACD.

THE ACD ASSOCIATED WITH THE TARGET FILE IS CORRUPTED. (CIERR 7304)

You are attempting to copy a file ACD which is corrupted.

You cannot copy this ACD because it is corrupted. It is possible to delete the ACD using the ;DELACD option on the :ALTSEC command. This will leave your file without an ACD to protect it. You can also create an ACD for that file (using the ;NEWACD option), or you can copy an existing ACD from another file (using the ;COPYACD option), without deleting the current ACD first. This is only allowed for corrupted ACDs (otherwise the file must not have an ACD prior to using the ;NEWACD or ;COPYACD options).

THERE IS NO ACD ASSOCIATED WITH TARGET FILE. (CIERR 7405)

You are attempting to manipulate an ACD for a file which does not have an ACD.

You must create the ACD (via the ;NEWACD option on the :ALTSEC command) before you can manipulate it. You can determine if a file has an ACD by using the :LISTF ,-2 command.

THERE IS NO ACD ASSOCIATED WITH THE SOURCE LDEV. (CIERR 7306)

You are attempting to copy an ACD from a device which does not currently have an ACD associated with it.

Copy the ACD from a device which actually has an ACD associated with it.

THE ACD ASSOCIATED WITH THE SOURCE LDEV IS CORRUPTED. (CIERR 7307)

You are attempting to copy a device ACD which is corrupted.

You cannot copy this ACD because it is corrupted. It is possible to delete the ACD using the ;DELACD option on the :ALTSEC command. This will leave your device without an ACD to protect it. You can also create an ACD for that device (using the ;NEWACD option), or you can copy an existing ACD from another device (using the ;COPYACD option), without deleting the current ACD first. This is only allowed for corrupted ACDs (otherwise the device must not have an ACD prior to using the ;NEWACD or ;COPYACD options).

THERE IS ALREADY AN ACD ASSOCIATED WITH THE TARGET LDEV. (CIERR 7308)

You are attempting to create a new ACD for (via the ;NEWACD option), or copy an existing ACD to (via the ;COPYACD option) a device which already has an ACD associated with it.

You must either delete the existing ACD prior to executing the :ALTSEC command with the ;NEWACD or ;COPYACD option, or you must use the ;ADDPAIR and ;REPPAIR options to change the existing ACD.

THE ACD ASSOCIATED WITH THE TARGET LDEV IS CORRUPTED. (CIERR 7309)

You are attempting to manipulate a device ACD which is corrupted.

You cannot manipulate this ACD because it is corrupted. It is possible to delete the ACD using the ;DELACD option on the :ALTSEC command. This will leave your device without an ACD to protect it. You can also create an ACD for that device (using the ;NEWACD option), or you can copy an existing ACD from another device (using the ;COPYACD option), without deleting the current ACD first. This is only allowed for corrupted ACDs (otherwise the device must not have an ACD prior to using the ;NEWACD or ;COPYACD options).

THERE IS NO ACD ASSOCIATED WITH TARGET LDEV. (CIERR 7310)

You are attempting to manipulate an ACD for a device which does not have an ACD.

You must create the ACD (via the ;NEWACD option on the :ALTSEC command) before you can manipulate it. You can determine which devices have ACDs using the :SHOWDEV command with the ;ACD option.

ERROR OPENING ACD INDIRECT FILE. (CIERR 7311)

An error occurred when opening the ACD indirect file. An additional message will be printed indicating the exact cause of the error.

Take the appropriate action to correct/avoid the error. The additional message should help you figure out what action to take.

INVALID ACD INDIRECT FILE CODE. FILE CODE MUST BE 0. (CIERR 7312)

You have specified an ACD indirect file with a non-zero file code. This should not be a problem very often because most editors create text files with a file code of zero.

You can determine if the file code for a file is zero by using the :LISTF command. You can use :FCOPY to copy the file to another file which has a file code of zero.

INVALID ACD INDIRECT FILE RECORD SIZE. MUST BE <= 88 BYTES. (CIERR 7313)

You have specified an ACD indirect file with a record length greater than 88 bytes. This should not be a problem very often because most editors create text files with record lengths less than or equal to 88 bytes. The record length is often affected by whether or not you choose to use numbered or unnumbered files. Either file type is acceptable if the total record length is less than or equal to 88 bytes.

You can determine the record length of a file by using the :LISTF command. You can use :FCOPY to copy the file to another file with an appropriate record length. Be careful not to truncate important data when copying the file.

ACD INDIRECT FILE MUST BE ASCII. (CIERR 7314)

You have specified an ACD indirect file which is not an ASCII file. This should not be a problem very often because most editors create ASCII text files.

You can determine if the file is an ASCII file by using the :LISTF command. You can use :FCOPY to copy the file to another file which is an ASCII file.

INVALID ACD INDIRECT FILE RECORD FORMAT. MUST BE FIXED. (CIERR 7315)

You have specified an ACD indirect file which does not have fixed length records. This should not be a problem very often because most editors create text files with fixed length records, or they offer some option to allow the user to select the record format.

You can determine if the file has fixed length records by using the :LISTF command. You can use :FCOPY to copy the file to another file with fixed length records to avoid this problem.

MAXIMUM NUMBER OF ACD ENTRIES (40) WOULD BE EXCEEDED. (CIERR 7316)

You are attempting to add some number of entries to the ACD. If you added these entries to the ACD then the total number of entries in the ACD would exceed the maximum number allowed (40).

You cannot have more than 40 entries in a given ACD. You may be able to combine some of the entries by using wildcards. For example, you could have one entry for all the FINANCE users instead of having separate entries for JOHN.FINANCE, SAM.FINANCE, TOM.FINANCE, for example. This will only work if the users are supposed to have the same access rights.

ATTEMPTING TO MODIFY MORE ENTRIES THAN CURRENTLY EXIST IN ACD. (CIERR 7317)

You are attempting to modify (with the :ALTSEC ;REPPAIR or ;DELPAIR option) more entries than currently exist in the ACD.

You can use either :LISTF -2 or :SHOWDEV to determine what the ACD currently looks like. Issue the :ALTSEC command again (with the appropriate ;REPPAIR or ;DELPAIR option) making sure that you are modifying only entries which actually exist in the ACD.

ENTRY ALREADY EXISTS IN ACD. (CIERR 7318)

You are attempting to add an entry to an ACD which already contains an entry corresponding to the same user. This error will only occur if the user name matches exactly a user name already specified in the ACD. For example, if you are attempting to add an entry for JOHN.DOE and an entry already exists for @.DOE this will not result in an error. If, however, you attempt to add an entry for @.DOE you will get this error.

You can modify an existing entry in an ACD by using the ;REPPAIR option on the :ALTSEC command. Or you can delete the entry using the ;DELPAIR option and re-issue the :ALTSEC command with the ;ADDPAIR option.

INCOMPATIBLE TARGET AND SOURCE FOR COPYING ACD. (CIERR 7319)

The target and source file/device specified on the :ALTSEC command must be of the same type. Either they must both be devices, or they must both be files.

If you want to grant the same explicit access rights to a file and a devices you should create an indirect file containing the ACD specification and use this indirect file on the :ALTSEC command with the ;NEWACD option.

SOURCE AND TARGET FOR COPYING ACD ARE THE SAME. (CIERR 7320)

The source and target specified on the :ALTSEC command are the same. Either they are the same device, or they are the same file. You cannot copy an ACD onto itself.

Either the target or the source must be changed for this command to execute correctly.

USER DOES NOT HAVE SUFFICIENT CAPABILITIES TO MANIPULATE ACD.(CIERR 7321)

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 person attempting to manipulate the ACD must request the appropriate capability from either system or account manager. Alternatively, the user can ask the file creator to make the desired change to the ACD.

OPERATION FAILED ON ALL DEVICES SPECIFIED. (CIERR 7322)

The operation which you requested (;NEWACD, :DELACD, ;REPPAIR, ;DELPAIR, ;ADDPAIR, or ;COPYACD) did not succeed for any of the devices in the the device specification. If a device class was specified, the operation failed for all of the devices in the device class. If "@" was specified, indicating all devices on the system, then the operation failed on all devices on the system.

Execute the same :ALTSEC command against those devices one at a time to determine the reason for the failure.

USER NOT ALLOWED TO READ THE ACD. (CIERR 7323)

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 person attempting to read the ACD must request the appropriate permission/capability from either the file creator or a system or account manager.

USER NOT ALLOWED TO COPY THE SOURCE ACD. (CIERR 7324)

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.

The person attempting to copy the ACD must request the appropriate permission/capability from either the file creator or a system or account manager.

ERROR OPENING TARGET FILE. (CIERR 7325)

An error occurred when opening the target file. An additional message will be printed indicating the exact cause of the error.

Take the appropriate action to correct/avoid the error. The additional message should help you figure out what action to take.

ERROR OPENING SOURCE FILE. (CIERR 7326)

An error occurred when opening the source file. An additional message will be printed indicating the exact cause of the error.

Take the appropriate action to correct/avoid the error. The additional message should help you figure out what action to take.

ACD INTERNAL ERROR. (CIERR 7400)

This message indicated that some kind of internal error occurred while processing your command. This message will be preceded by another message indicating the internal status and subsystem number. This information will be helpful in diagnosing the cause of the problem.

Contact you HP Support Representative.

ERROR ENCOUNTERED WITHIN ACD INDIRECT FILE.

A error occurred when performing an :ALTSEC command using an indirect file. This message will be followed by additional messages to help you isolate the problem.

The message printed by the command interpreter after this message will indicate the actual error and the position where that error occurred. Refer to the descriptions of those messages for the appropriate action(s) to be taken.

ERROR OCCURRED IN ACD PAIR NUMBER !.

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, @.@)

Correct the syntactic or semantic error in you ACD indirect file and re-issue the :ALTSEC command.

ACD INTERNAL STATUS ! - SUBSYSTEM NUMBER !.

An unexpected internal error has occurred.

Try re-issuing the command. If you still get this error, call in the internal error number to your HP Representative.