HP 3000 Manuals HP 3000 Manuals
ACD Related Error Messages
This appendix lists error messages which may be encountered when creating
or modifying ACDs.
---------------------------------------------------------------------------------------
7100 MESSAGE UNABLE TO DEALLOCATE ACD SPACE. (CIWARN 7100)
CAUSE 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.
ACTION 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!
---------------------------------------------------------------------------------------
7101 MESSAGE ACD VERSION DOES NOT MATCH THE CURRENT VERSION. (CIWARN 7101)
CAUSE 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.
ACTION 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.
Table A-0. (cont.)
---------------------------------------------------------------------------------------
7102 MESSAGE ACD WAS CORRUPTED PRIOR TO BEING DELETED. (CIWARN 7102)
CAUSE 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.
ACTION 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.
---------------------------------------------------------------------------------------
7103 MESSAGE OPERATION FAILED ON SOME DEVICES SPECIFIED. (CIWARN 7103)
CAUSE 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.
ACTION 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.
---------------------------------------------------------------------------------------
7104 MESSAGE MISSING CLOSE PARENTHESIS ")" IN ACD INDIRECT FILE. (CIWARN
7104)
CAUSE 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.
ACTION 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.
---------------------------------------------------------------------------------------
7105 MESSAGE EXTRA CLOSE PARENTHESIS ")" ENCOUNTERED IN ACD INDIRECT FILE.
(CIWARN 7105)
CAUSE 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.
ACTION 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.
Table A-0. (cont.)
---------------------------------------------------------------------------------------
7221 MESSAGE WILDCARDS NOT ALLOWED IN FILENAME HERE. (CIERR 7221)
CAUSE You have specified a generic file name which contains wildcards
as the target file name or the source file name in the :ALTSEC
command.
ACTION Repeat the :ALTSEC command for each file in the file set
specified by the wildcard.
---------------------------------------------------------------------------------------
7223 MESSAGE LOCKWORDS NOT ALLOWED IN GENERIC FILE SETS. (CIERR 7223)
CAUSE A generic file specification (has wildcards) should not contain
a lockword.
ACTION Remove the lockword from the generic file specification.
---------------------------------------------------------------------------------------
7224 MESSAGE LOCKWORDS NOT ALLOWED. (CIERR 7224)
CAUSE A lockword was specified as part of a file name.
ACTION Remove the lockword from the file name.
---------------------------------------------------------------------------------------
7225 MESSAGE INVALID CHARACTER IN DEVICE CLASS NAME. (CIERR 7225)
CAUSE 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.
ACTION Correct the device class name and issue the command again.
---------------------------------------------------------------------------------------
7227 MESSAGE NUMBER SPECIFIED IS GREATER THAN 32767. (CIERR 7227)
CAUSE 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.
ACTION 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.
---------------------------------------------------------------------------------------
7228 MESSAGE WILDCARD CHARACTERS, OTHER THAN "@" BY ITSELF, NOT ALLOWED IN
DEVICE CLASS NAME. (CIERR 7228)
CAUSE You have specified a device class name which contains wildcard
characters. The use of wildcard characters is not supported
for device class names.
ACTION Please remove any wildcards included in the device class name
specified.
Table A-0. (cont.)
---------------------------------------------------------------------------------------
7229 MESSAGE "_" (UNDERBAR) CHARACTER NOT ALLOWED IN DEVICE CLASS NAME.
(CIERR 7229)
CAUSE 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.
ACTION Remove the "_" (underbar) character from the device class name
and re-issue the command.
---------------------------------------------------------------------------------------
7230 MESSAGE SINGLE QUOTE "'" CHARACTER NOT ALLOWED IN DEVICE CLASS NAME.
(CIERR 7230)
CAUSE 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.
ACTION Remove the single quote (') character from the device class
name and re-issue the command.
---------------------------------------------------------------------------------------
7231 MESSAGE FULLY QUALIFIED NAME NOT ALLOWED HERE. (CIERR 7231)
CAUSE A fully qualified name is not allowed in this context. This
error could apply to either file names or user names.
ACTION 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.
---------------------------------------------------------------------------------------
7250 MESSAGE INVALID USER SPECIFICATION. (CIERR 7250)
CAUSE 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).
ACTION Correct the user specification to conform to the rules
specified above.
Table A-0. (cont.)
---------------------------------------------------------------------------------------
7251 MESSAGE DUPLICATE ACCESS MODE SPECIFIED. (CIERR 7251)
CAUSE 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).
ACTION Delete the duplicate access mode from your list and issue the
:ALTSEC command again.
---------------------------------------------------------------------------------------
7252 MESSAGE DUPLICATE PERMISSION SPECIFIED. (CIERR 7252)
CAUSE 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).
ACTION Delete the duplicate permission from your list and issue the
:ALTSEC command again.
Table A-0. (cont.)
---------------------------------------------------------------------------------------
7253 MESSAGE CONTRADICTORY ACCESS MODES SPECIFIED. (CIERR 7253)
CAUSE 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.
ACTION Change your access modes so that the modes specified for all
your entries are not contradictory.
---------------------------------------------------------------------------------------
7254 MESSAGE INVALID ACCESS MODE SPECIFIED. (CIERR 7254)
CAUSE 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.
ACTION Correct your ACD specification to include only valid access
modes.
---------------------------------------------------------------------------------------
7255 MESSAGE MISSING OPEN PARENTHESIS "(". (CIERR 7255)
CAUSE 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.
ACTION Re-issue the command and add the missing open parenthesis.
Table A-0. (cont.)
---------------------------------------------------------------------------------------
7256 MESSAGE MISSING CLOSE PARENTHESIS ")". (CIERR 7256)
CAUSE 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.
ACTION Re-issue the command and add the missing close parenthesis.
---------------------------------------------------------------------------------------
7257 MESSAGE MISSING COLON ":". (CIERR 7257)
CAUSE You have omitted the colon character from your ACD
specification. A colon is required after the access modes and
before the user specification.
ACTION Re-issue the command and add the missing colon.
---------------------------------------------------------------------------------------
7258 MESSAGE UNEXPECTED INPUT ENCOUNTERED AFTER ACD SPECIFICATION. (CIERR
7258)
CAUSE 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.
ACTION Delete the extra input and re-issue the command.
---------------------------------------------------------------------------------------
7259 MESSAGE INVALID ACCOUNT NAME SPECIFIED. (CIERR 7259)
CAUSE 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.
---------------------------------------------------------------------------------------
7260 MESSAGE EMBEDDED "@" CHARACTER NOT ALLOWED IN USER SPECIFICATION.
(CIERR 7260)
CAUSE 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).
ACTION Correct the user specification to conform to the rules
specified above.
Table A-0. (cont.)
---------------------------------------------------------------------------------------
7261 MESSAGE USER NAME MUST BE "@" IF ACCOUNT NAME IS SPECIFIED AS "@".
(CIERR 7261)
CAUSE 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).
ACTION Correct the user specification to conform to the rules
specified above.
---------------------------------------------------------------------------------------
7262 MESSAGE "#" CHARACTER NOT ALLOWED IN USER SPECIFICATION. (CIERR 7262)
CAUSE 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).
ACTION Correct the user specification to conform to the rules
specified above.
---------------------------------------------------------------------------------------
7263 MESSAGE "?" CHARACTER NOT ALLOWED IN USER SPECIFICATION. (CIERR 7263)
CAUSE 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).
ACTION Correct the user specification to conform to the rules
specified above.
---------------------------------------------------------------------------------------
7264 MESSAGE MISSING ACCESS MODE IN ACD SPECIFICATION. (CIERR 7264)
CAUSE You have either omitted an access mode in your ACD
specification or you have typed an extra comma (,) in your
specification.
ACTION Either delete the extra comma or provide the missing access
mode when you re-issue the command.
Table A-0. (cont.)
---------------------------------------------------------------------------------------
7265 MESSAGE USER SPECIFICATION MUST BE FULLY QUALIFIED. (CIERR 7265)
CAUSE 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).
ACTION Correct the user specification to conform to the rules
specified above.
---------------------------------------------------------------------------------------
7266 MESSAGE INVALID USER NAME SPECIFIED. (CIERR 7266)
CAUSE The user name part of your user specification is invalid for
your system. The account name is valid.
ACTION Check the user name and re-issue the command specifying the
correct user name.
---------------------------------------------------------------------------------------
7267 MESSAGE MISSING USER SPECIFICATION. (CIERR 7267)
CAUSE You have either omitted a user specification or you have
included and extra comma (,) in your ACD specification.
ACTION Either delete the extra comma or add the missing user
specification to the ACD specification when you re-issue the
command.
---------------------------------------------------------------------------------------
7268 MESSAGE DUPLICATE USER SPECIFICATION ENCOUNTERED IN LIST. (CIERR 7268)
CAUSE The ACD specification you used contains more than one reference
to the same user specification.
ACTION Delete the duplicate reference from you ACD specification and
re-issue the command.
---------------------------------------------------------------------------------------
7269 MESSAGE INTERNAL ERROR NUMBER "-269". (CIERR 7269)
CAUSE An unexpected internal error has occurred.
ACTION Try re-issuing the command. If you still get this error,
contact your HP Representative and give him/her the internal
error number.
Table A-0. (cont.)
---------------------------------------------------------------------------------------
7270 MESSAGE INTERNAL ERROR NUMBER "-270". (CIERR 7270)
CAUSE An unexpected internal error has occurred.
ACTION Try re-issuing the command. If you still get this error,
contact your HP Representative and give him/her the internal
error number.
---------------------------------------------------------------------------------------
7271 MESSAGE INTERNAL ERROR NUMBER "-271". (CIERR 7271)
CAUSE An unexpected internal error has occurred.
ACTION Try re-issuing the command. If you still get this error,
contact your HP Representative and give him/her the internal
error number.
---------------------------------------------------------------------------------------
7272 MESSAGE INVALID LDEV NUMBER SPECIFIED. (CIERR 7272)
CAUSE You have specified an ldev number which does not correspond to
an ldev which is currently configured on your system.
ACTION Correct the ldev number and re-issue the command.
---------------------------------------------------------------------------------------
7273 MESSAGE INVALID TARGET LDEV NUMBER SPECIFIED. (CIERR 7273)
CAUSE You have specified an ldev number which does not correspond to
an ldev which is currently configured on your system.
ACTION Correct the ldev number and re-issue the command.
---------------------------------------------------------------------------------------
7274 MESSAGE INVALID SOURCE LDEV NUMBER SPECIFIED. (CIERR 7274)
CAUSE You have specified an ldev number which does not correspond to
an ldev which is currently configured on your system.
ACTION Correct the ldev number and re-issue the command.
---------------------------------------------------------------------------------------
7275 MESSAGE INVALID DEVICE CLASS NAME SPECIFIED. (CIERR 7275)
CAUSE You have specified a device class name which does not
correspond to any device class currently configured on your
system.
ACTION Correct the device class name and re-issue the command.
Table A-0. (cont.)
---------------------------------------------------------------------------------------
7300 MESSAGE ACD ENTRY DOES NOT EXIST. (CIERR 7300)
CAUSE You are attempting to access (delete or replace) an ACD entry
which does not exist in the specified ACD.
ACTION 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).
---------------------------------------------------------------------------------------
7301 MESSAGE THERE IS NO ACD ASSOCIATED WITH THE SOURCE FILE. (CIERR 7301)
CAUSE You are attempting to copy an ACD from a file which does not
currently have an ACD associated with it.
ACTION Copy the ACD from a file which actually has an ACD associated
with it.
---------------------------------------------------------------------------------------
7302 MESSAGE THE ACD ASSOCIATED WITH THE SOURCE FILE IS CORRUPTED. (CIERR
7302)
CAUSE You are attempting to copy a file ACD which is corrupted.
ACTION 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).
---------------------------------------------------------------------------------------
7303 MESSAGE THERE IS ALREADY AN ACD ASSOCIATED WITH THE TARGET FILE. (CIERR
7303)
CAUSE 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.
ACTION 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.
Table A-0. (cont.)
---------------------------------------------------------------------------------------
7304 MESSAGE THE ACD ASSOCIATED WITH THE TARGET FILE IS CORRUPTED. (CIERR
7304)
CAUSE You are attempting to copy a file ACD which is corrupted.
ACTION 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).
---------------------------------------------------------------------------------------
7305 MESSAGE THERE IS NO ACD ASSOCIATED WITH TARGET FILE. (CIERR 7405)
CAUSE You are attempting to manipulate an ACD for a file which does
not have an ACD.
ACTION 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.
---------------------------------------------------------------------------------------
7306 MESSAGE THERE IS NO ACD ASSOCIATED WITH THE SOURCE LDEV. (CIERR 7306)
CAUSE You are attempting to copy an ACD from a device which does not
currently have an ACD associated with it.
ACTION Copy the ACD from a device which actually has an ACD associated
with it.
---------------------------------------------------------------------------------------
7307 MESSAGE THE ACD ASSOCIATED WITH THE SOURCE LDEV IS CORRUPTED. (CIERR
7307)
CAUSE You are attempting to copy a device ACD which is corrupted.
ACTION 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).
Table A-0. (cont.)
---------------------------------------------------------------------------------------
7308 MESSAGE THERE IS ALREADY AN ACD ASSOCIATED WITH THE TARGET LDEV. (CIERR
7308)
CAUSE 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.
ACTION 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.
---------------------------------------------------------------------------------------
7309 MESSAGE THE ACD ASSOCIATED WITH THE TARGET LDEV IS CORRUPTED. (CIERR
7309)
CAUSE You are attempting to manipulate a device ACD which is
corrupted.
ACTION 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).
---------------------------------------------------------------------------------------
7310 MESSAGE THERE IS NO ACD ASSOCIATED WITH TARGET LDEV. (CIERR 7310)
CAUSE You are attempting to manipulate an ACD for a device which does
not have an ACD.
ACTION 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.
---------------------------------------------------------------------------------------
7311 MESSAGE ERROR OPENING ACD INDIRECT FILE. (CIERR 7311)
CAUSE An error occurred when opening the ACD indirect file. An
additional message will be printed indicating the exact cause
of the error.
ACTION Take the appropriate action to correct/avoid the error. The
additional message should help you figure out what action to
take.
Table A-0. (cont.)
---------------------------------------------------------------------------------------
7312 MESSAGE INVALID ACD INDIRECT FILE CODE. FILE CODE MUST BE 0. (CIERR
7312)
CAUSE 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.
ACTION 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.
---------------------------------------------------------------------------------------
7313 MESSAGE INVALID ACD INDIRECT FILE RECORD SIZE. MUST BE <= 88 BYTES.
(CIERR 7313)
CAUSE 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.
ACTION 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.
---------------------------------------------------------------------------------------
7314 MESSAGE ACD INDIRECT FILE MUST BE ASCII. (CIERR 7314)
CAUSE 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.
ACTION 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.
---------------------------------------------------------------------------------------
7315 MESSAGE INVALID ACD INDIRECT FILE RECORD FORMAT. MUST BE FIXED. (CIERR
7315)
CAUSE 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.
ACTION 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.
Table A-0. (cont.)
---------------------------------------------------------------------------------------
7316 MESSAGE MAXIMUM NUMBER OF ACD ENTRIES (40) WOULD BE EXCEEDED. (CIERR
7316)
CAUSE 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).
ACTION 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.
---------------------------------------------------------------------------------------
7317 MESSAGE ATTEMPTING TO MODIFY MORE ENTRIES THAN CURRENTLY EXIST IN ACD.
(CIERR 7317)
CAUSE You are attempting to modify (with the :ALTSEC ;REPPAIR or
;DELPAIR option) more entries than currently exist in the ACD.
ACTION 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.
---------------------------------------------------------------------------------------
7318 MESSAGE ENTRY ALREADY EXISTS IN ACD. (CIERR 7318)
CAUSE 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.
ACTION 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.
Table A-0. (cont.)
---------------------------------------------------------------------------------------
7319 MESSAGE INCOMPATIBLE TARGET AND SOURCE FOR COPYING ACD. (CIERR 7319)
CAUSE 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.
ACTION 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.
---------------------------------------------------------------------------------------
7320 MESSAGE SOURCE AND TARGET FOR COPYING ACD ARE THE SAME. (CIERR 7320)
CAUSE 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.
ACTION Either the target or the source must be changed for this
command to execute correctly.
---------------------------------------------------------------------------------------
7321 MESSAGE USER DOES NOT HAVE SUFFICIENT CAPABILITIES TO MANIPULATE ACD.
(CIERR 7321)
CAUSE 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.
ACTION 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.
Table A-0. (cont.)
---------------------------------------------------------------------------------------
7322 MESSAGE OPERATION FAILED ON ALL DEVICES SPECIFIED. (CIERR 7322)
CAUSE 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.
ACTION Execute the same :ALTSEC command against those devices one at a
time to determine the reason for the failure.
---------------------------------------------------------------------------------------
7323 MESSAGE USER NOT ALLOWED TO READ THE ACD. (CIERR 7323)
CAUSE 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.
ACTION The person attempting to read the ACD must request the
appropriate permission/capability from either the file creator
or a system or account manager.
Table A-0. (cont.)
---------------------------------------------------------------------------------------
7324 MESSAGE USER NOT ALLOWED TO COPY THE SOURCE ACD. (CIERR 7324)
CAUSE 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.
ACTION The person attempting to copy the ACD must request the
appropriate permission/capability from either the file creator
or a system or account manager.
---------------------------------------------------------------------------------------
7325 MESSAGE ERROR OPENING TARGET FILE. (CIERR 7325)
CAUSE 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.
---------------------------------------------------------------------------------------
7326 MESSAGE ERROR OPENING SOURCE FILE. (CIERR 7326)
CAUSE An error occurred when opening the source file. An additional
message will be printed indicating the exact cause of the
error.
ACTION Take the appropriate action to correct/avoid the error. The
additional message should help you figure out what action to
take.
Table A-0. (cont.)
---------------------------------------------------------------------------------------
7400 MESSAGE ACD INTERNAL ERROR. (CIERR 7400)
CAUSE 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.
ACTION Contact you HP Support Representative.
---------------------------------------------------------------------------------------
7401 MESSAGE ERROR ENCOUNTERED WITHIN ACD INDIRECT FILE.
CAUSE 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.
ACTION 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.
---------------------------------------------------------------------------------------
7402 MESSAGE ERROR OCCURRED IN ACD PAIR NUMBER !.
CAUSE 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, @.@)
ACTION Correct the syntactic or semantic error in you ACD indirect
file and re-issue the :ALTSEC command.
Table A-0. (cont.)
---------------------------------------------------------------------------------------
7403 MESSAGE ACD INTERNAL STATUS ! - SUBSYSTEM NUMBER !.
CAUSE An unexpected internal error has occurred.
ACTION Try re-issuing the command. If you still get this error, call
in the internal error number to your HP Representative.