HP 3000 Manuals HP 3000 Manuals
(CIERR) (contd.)
536 MESSAGE GENERIC FILE NAME IS NOT PERMITTED IN THIS
COMMAND. (CIERR 536)
CAUSE A wild card character, was used in place of the
file name.
ACTION Re-enter the command and supply a completely
alphanumeric file name.
---------------------------------------------------------------
540 MESSAGE FIRST CHARACTER IN GROUP NAME NOT ALPHABETIC.
(CIERR 540)
CAUSE The group name specified does not start with an
alphabetic character. You probably mistyped the
group name.
ACTION Retype the command.
---------------------------------------------------------------
541 MESSAGE GROUP NAME MISSING. (CIERR 541)
CAUSE You did not specify a group name on the command
line.
ACTION Specify a group name on the command line.
---------------------------------------------------------------
542 MESSAGE GROUP NAME IS MORE THAN EIGHT CHARACTERS LONG.
(CIERR 542)
CAUSE Your group name is greater than eight characters,
and group names can only be eight characters or
fewer in length. You probably mistyped the group
name.
ACTION Retype the command.
---------------------------------------------------------------
543 MESSAGE EXPECTED GROUP NAME; "@" NOT PERMITTED. (CIERR
543)
CAUSE "@" was specified instead of an alphanumeric name
for the group.
ACTION Re-enter the command and supply an alphanumeric
name for the group.
---------------------------------------------------------------
544 MESSAGE EMBEDDED NON-ALPHANUMERIC CHARACTER IN GROUP
NAME. (CIERR 544)
CAUSE A control or unprintable character was typed as
part of the group name.
ACTION Re-enter the command. Make sure that you do not
type in an escape code or control characters.
---------------------------------------------------------------
545 MESSAGE MISSING DELIMITER AFTER GROUP NAME. (CIERR 545)
CAUSE The command interpreter expected a delimiter after
the group name but did not find it.
ACTION Re-enter the command and supply a delimiter after
the group name.
---------------------------------------------------------------
546 MESSAGE GENERIC GROUP NAME IS NOT PERMITTED IN THIS
COMMAND. (CIERR 546)
CAUSE This command does not allow pattern matching
characters in the group name.
ACTION Re-enter the command and supply a completely
alphanumeric group name.
---------------------------------------------------------------
547 MESSAGE NO HOME GROUP FOR USER. (CIERR 547)
CAUSE User does not have a home group as a default group
to log on to.
ACTION Re-enter the command and specify a group name. As
a long term solution you may consider assigning a
home group to the user. See the ALTUSER command.
---------------------------------------------------------------
550 MESSAGE FIRST CHARACTER IN ACCOUNT NAME NOT ALPHABETIC.
(CIERR 550)
CAUSE Account name specified does not start with an
alphabetic character.
ACTION Re-enter the command and supply a valid account
name.
---------------------------------------------------------------
551 MESSAGE ACCOUNT NAME MISSING. (CIERR 551)
CAUSE Account name was not specified as part of the
command line.
ACTION Re-enter the command and supply an account name.
---------------------------------------------------------------
552 MESSAGE ACCOUNT NAME IS MORE THAN EIGHT CHARACTERS LONG.
(CIERR 552)
CAUSE The name specified for the account is more than 8
characters long.
ACTION Re-enter the command and supply an account name
that is up to 8 characters long.
---------------------------------------------------------------
553 MESSAGE EXPECTED ACCOUNT NAME; "@" NOT PERMITTED. (CIERR
553)
CAUSE "@" was specified instead of an alphanumeric name
for the account.
ACTION Re-enter the command and supply a completely
alphanumeric name for the account.
---------------------------------------------------------------
554 MESSAGE EMBEDDED NON-ALPHANUMERIC CHARACTER IN ACCOUNT
NAME. (CIERR 554)
CAUSE A control or unprintable character was typed as
part of the account name.
ACTION Re-enter the command. Make sure that you do not
type in an escape code or control characters.
---------------------------------------------------------------
555 MESSAGE MISSING DELIMITER AFTER ACCOUNT NAME. (CIERR
555)
CAUSE The command interpreter expected a delimiter after
the account name but did not find it.
ACTION Re-enter the command and supply a delimiter after
the account name.
---------------------------------------------------------------
556 MESSAGE GENERIC ACCOUNT NAME IS NOT PERMITTED IN THIS
COMMAND. (CIERR 556)
CAUSE This command does not allow pattern matching
characters in the account name.
ACTION Re-enter the command and supply a completely
alphanumeric account name.
---------------------------------------------------------------
560 MESSAGE FIRST CHARACTER IN LOCK WORD NOT ALPHABETIC.
(CIERR 560)
CAUSE You specified a lockword that does not start with
an alphabetic character.
ACTION Re-enter the command and supply a valid lockword.
---------------------------------------------------------------
561 MESSAGE LOCKWORD EXPECTED, NOT FOUND. (CIERR 561)
CAUSE You forgot to specify the lockword after the slash.
ACTION Re-enter the command and supply the lockword.
---------------------------------------------------------------
562 MESSAGE LOCKWORD > 8 CHARACTERS LONG. (CIERR 562)
CAUSE The name specified for the lockword is more than 8
characters long.
ACTION Re-enter the command and supply a lockword that is
up to 8 characters long.
---------------------------------------------------------------
563 MESSAGE EXPECTED LOCKWORD; "@" NOT PERMITTED. (CIERR
563)
CAUSE "@" was specified instead of an alphanumeric
lockword.
ACTION Re-enter the command and supply a completely
alphanumeric lockword.
---------------------------------------------------------------
564 MESSAGE EMBEDDED NON-ALPHANUMERIC CHARACTER IN LOCKWORD.
(CIERR 564)
CAUSE A control or unprintable character was typed as
part of the lockword.
ACTION Re-enter the command. Make sure that you do not
type in any control characters.
---------------------------------------------------------------
565 MESSAGE MISSING DELIMITER AFTER LOCKWORD. (CIERR 565)
CAUSE The command interpreter expected a delimiter after
the lockword but did not find it.
ACTION Re-enter the command and supply a delimiter after
the lockword.
---------------------------------------------------------------
566 MESSAGE GENERIC LOCKWORD IS NOT PERMITTED. (CIERR 566)
CAUSE A wild card character was used in place of the
lockword.
ACTION Re-enter the command and supply a completely
alphanumeric lockword.
---------------------------------------------------------------
569 MESSAGE LOCKWORD NOT PERMITTED FOR FILENAME OF "@".
(CIERR 569)
---------------------------------------------------------------
570 MESSAGE FIRST CHARACTER IN VSD NAME NOT ALPHABETIC.
(CIERR 570)
CAUSE Volume Set Definition (VSD) name specified does not
start with an alphabetic character.
ACTION Re-enter the command and supply a valid VSD name.
---------------------------------------------------------------
571 MESSAGE VSD NAME MISSING. (CIERR 571)
CAUSE Volume Set Definition (VSD) name was not specified
as part of the command line.
ACTION Re-enter the command and supply a VSD name.
---------------------------------------------------------------
572 MESSAGE VSD NAME > 8 CHARACTERS LONG. (CIERR 572)
CAUSE The name specified for the Volume Set Definition
(VSD) is more than 8 characters long.
ACTION Re-enter the command and supply a VSD name that is
up to 8 characters long.
---------------------------------------------------------------
573 MESSAGE EXPECTED VSD NAME; "@" NOT PERMITTED. (CIERR
573)
CAUSE "@" was specified instead of an alphanumeric Volume
Set Defintion (VSD) name.
ACTION Re-enter the command and supply a completely
alphanumeric VSD name.
---------------------------------------------------------------
574 MESSAGE EMBEDDED NON-ALPHANUMERIC CHARACTER IN VSD NAME.
(CIERR 574)
CAUSE A control or unprintable character was typed as
part of the Volume Set Definition (VSD) name.
ACTION Re-enter the command. Make sure that you do not
type in any control characters.
---------------------------------------------------------------
575 MESSAGE MISSING DELIMITER AFTER VSD NAME. (CIERR 575)
CAUSE The command interpreter expected a delimiter after
the Volume Set Definition (VSD) name but did not
find it.
ACTION Re-enter the command and supply a delimiter after
the VSD name.
---------------------------------------------------------------
576 MESSAGE GENERIC VSD NAME IS NOT PERMITTED IN THIS
COMMAND. (CIERR 576)
CAUSE A wild card character, was used in place of the
Volume Set Definition (VSD) name.
ACTION Re-enter the command and supply a completely
alphanumeric VSD name.
---------------------------------------------------------------
579 MESSAGE VSD MAY NOT HAVE A LOCKWORD. (CIERR 579)
CAUSE A lockword was specified for the Volume Set
Definition (VSD).
ACTION Re-enter the command without specifying a lockword
on the VSD.
---------------------------------------------------------------
580 MESSAGE UNKNOWN SYSTEM DEFINED FILE NAME. (CIERR 580)
CAUSE Only $STDIN, $STDINX, $STDLIST, $NULL, $NEWPASS,
AND $OLDPASS are accepted as valid system defined
files.
ACTION Re-enter the command and supply the appropriate
system defined file name.
---------------------------------------------------------------
581 MESSAGE UNEXPECTED CHARACTER IN FILE NAME; EXPECTED "."
(CIERR 581)
CAUSE A "." was expected in order to construct a fully
qualified file name.
ACTION Re-enter the command and supply a fully qualified
file name.
---------------------------------------------------------------
582 MESSAGE UNEXPECTED CHARACTER IN FILE NAME; EXPECTED "."
OR "/". % IS THE DELIMITER BETWEEN PARAMETERS
CORRECT? (CIERR 582)
CAUSE The file name contains a character that is neither
alphanumeric nor a period or a backslash.
ACTION Re-enter the command and use alphanumeric
characters in the file name. If you are specifying
a fully qualified file name use a period between
file name, group and account names. If you are
specifying a lockword use a backslash after the
file name and before the ".group.account."
---------------------------------------------------------------
583 MESSAGE UNEXPECTED, EXTRANEOUS SPECIAL CHARACTER. (CIERR
583)
CAUSE An unexpected character was foung in the directory
name. Most likely the user omitted the leading "."
or "/" (specifying an HFS name), or tried to create
an MPE group directory, or tried to specify a
directory lockword.
ACTION MPE directory names must follow MPE naming rules.
HFS directory names are only accepted if the name
begins with a "." or a "/".
---------------------------------------------------------------
586 MESSAGE EXPECTED A DELIMITER OF SOME SORT. (CIERR 586)
---------------------------------------------------------------
590 MESSAGE FIRST CHARACTER IN USER NAME NOT ALPHABETIC.
(CIERR 590)
CAUSE The user name specified does not start with an
alphabetic character.
ACTION Re-enter the command and supply a valid user name.
---------------------------------------------------------------
591 MESSAGE USER NAME MISSING. (CIERR 591)
CAUSE You did not include a user name on the command
line.
ACTION Specify a user name.
---------------------------------------------------------------
592 MESSAGE USER NAME > 8 CHARACTERS LONG. (CIERR 592)
CAUSE The user name that you specified is greater than
eight characters. User names can only be eight
characters or fewer in length. You probably
mistyped the user name.
ACTION Retype the command.
---------------------------------------------------------------
593 MESSAGE EXPECTED USER NAME; "@" NOT PERMITTED. (CIERR
593)
CAUSE "@" was specified instead of an alphanumeric user
name.
ACTION Re-enter the command and supply a completely
alphanumeric user name.
---------------------------------------------------------------
594 MESSAGE EMBEDDED NON-ALPHANUMERIC CHARACTER IN USER NAME.
(CIERR 594)
CAUSE User names can be comprised of both alphabetic and
numeric characters. One of the characters in the
user name that you specified is neither alphabetic
nor numeric. You probably mistyped the user name.
ACTION Retype the command.
---------------------------------------------------------------
595 MESSAGE MISSING DELIMITER AFTER USER NAME. (CIERR 595)
CAUSE The command interpreter expected a delimiter after
the user name but did not find it.
ACTION Re-enter the command and supply a delimiter after
the user name.
---------------------------------------------------------------
596 MESSAGE GENERIC USER NAME IS NOT PERMITTED IN THIS
COMMAND. (CIERR 596)
CAUSE A wild card character, was used in place of the
user name.
ACTION Re-enter the command and supply a completely
alphanumeric user name.
---------------------------------------------------------------
600 MESSAGE NO PROGRAM FILE SPECIFIED. (CIERR 600)
CAUSE The program file name was not supplied to the RUN
command.
ACTION Re-enter the command and supply the name of an
executable program file.
---------------------------------------------------------------
601 MESSAGE NO USL FILE SPECIFIED. (CIERR 601)
CAUSE The command requires that name of a USL file be
supplied.
ACTION Re-enter the command and supply name of a USL file.
---------------------------------------------------------------
602 MESSAGE NEITHER PROGRAM FILE OR USL FILE SPECIFIED.
(CIERR 602)
CAUSE The command requires that name of a USL file or
program file be specified.
ACTION Re-enter the command and supply name of a USL file
or program file.
---------------------------------------------------------------
603 MESSAGE NO PROGRAM FILE SPECIFIED FOR PREP. (CIERR 603)
CAUSE The PREP command expected a file name as its second
parameter.
ACTION Re-enter the command and supply a file name as the
second parameter to PREP.
---------------------------------------------------------------
604 MESSAGE EXPECTED SEMICOLON OR CARRIAGE RETURN, FOUND
COMMA. (CIERR 604)
CAUSE A "," was specified where a ";" or carriage return
should have been supplied.
ACTION Re-enter the command.
---------------------------------------------------------------
605 MESSAGE EXPECTED SEMICOLON OR CARRIAGE RETURN, FOUND
EQUAL SIGN. (CIERR 605)
CAUSE An "=" was specified where a ";" or carriage return
should have been typed.
ACTION Re-enter the command.
---------------------------------------------------------------
606 MESSAGE IGNORED EXTRANEOUS DELIMITER. (CIWARN 606)
CAUSE The command interpreter detected a delimiter that
is neither required nor causes any problems if
present.
ACTION The delimiter was ignored and command was executed.
---------------------------------------------------------------
607 MESSAGE CONTEXT FOR THIS KEYWORD IS THE RUN COMMAND, NOT
PREP. (CIERR 607)
CAUSE A keyword that is only valid with the RUN command
was specified with the PREP command.
ACTION Determine the context of your operation and enter
either the RUN command or the PREP command.
---------------------------------------------------------------
608 MESSAGE CONTEXT FOR THIS KEYWORD IS THE PREP COMMAND, NOT
RUN. (CIERR 608)
CAUSE A keyword that is only valid with the PREP command
was specified with the RUN command.
ACTION Determine the context of your operation and enter
either the RUN command or the PREP command.
---------------------------------------------------------------
609 MESSAGE EXPECTED ONE OF ZERODB, PMAP, MAXDATA, STACK, DL,
RL, CAP, % PATCH, NOSYM, FPMAP, NOFPMAP. (CIERR
609)
CAUSE A keyword other than the ones listed above was
specified.
ACTION Re-enter the command and supply one of the keywords
listed above.
---------------------------------------------------------------