HP 3000 Manuals HP 3000 Manuals
NMGRERR Messages (contd)
NMGRERR 326 MESSAGE Cannot specify a node name when source is a
configuration file. (NMGRERR 326)
CAUSE Maintenance mode interface: Informative message
issued when a user specified a node name in
conjunction with a configuration file in a
MERGEDIR command.
ACTION Omit the node name from the command or use a
directory file as the source and retain the node
name.
--------------------------------------------------------------------------
NMGRERR 327 MESSAGE Local and global entries exist for this node
name; choose one. (NMGRERR 327)
CAUSE Maintenance mode interface: An informative
message issued when the user has given a
DELETENODE command, specifying a node name that
is not unique. For example, both a local and
global entry could exist for the node name.
ACTION Explicitly state the entry to be deleted using
;LOCAL or ;GLOBAL
--------------------------------------------------------------------------
NMGRERR 328 MESSAGE The node name must be of the form
NAME.DOMAIN.ORG. (NMGRERR 328)
CAUSE A node name was expected, however, the data
present did not conform to the node name format.
ACTION Correct the node name.
CAUSE The node name is more than 50 characters long.
ACTION Correct the node name.
--------------------------------------------------------------------------
NMGRERR 329 MESSAGE The catalog file has an error in the Batch
Command list. (NMGRERR 329)
CAUSE An internal error in NMMGR has occurred.
ACTION Run NMMAINT.PUB.SYS to make sure that you have
the correct version of NMMGR. If necessary,
restore the file NMMGRCAT.PUB.SYS from a back-up
tape. If the problem still exists, see
"Submitting an SR" at the beginning of this
appendix.
--------------------------------------------------------------------------
NMGRERR 330 MESSAGE Extra data was specified for this command.
(NMGRERR 330)
CAUSE The user specified too much data.
ACTION Check syntax of command or type "help" for more
information.
--------------------------------------------------------------------------
NMGRERR 332 MESSAGE A key operator was already specified. (NMGRERR
332)
CAUSE The user specified both a ;LOCAL and ;GLOBAL key
operator.
ACTION Retype the command with only a ;LOCAL or ;GLOBAL
key operator.
--------------------------------------------------------------------------
NMGRERR 333 MESSAGE A merge operator was already specified.
(NMGRERR 333)
CAUSE The user specified more than one merge operator
(KEEP, NOKEEP, TIMESTAMP).
ACTION Retype the command with only one merge operator.
--------------------------------------------------------------------------
NMGRERR 334 MESSAGE Unknown command encountered. (NMGRERR 334)
CAUSE The user typed in an incorrect command.
ACTION If the command is an MPE command, the command
must start with a ':'. Check the spelling of
the command name and reenter as needed.
--------------------------------------------------------------------------
NMGRERR 335 MESSAGE Internal Batch Mode error. (NMGRERR 335)
CAUSE An internal batch mode error has occurred.
ACTION See "Submitting an SR" at the beginning of this
appendix.
--------------------------------------------------------------------------
NMGRERR 336 MESSAGE Unexpected semicolon encountered. (NMGRERR 336)
CAUSE A semicolon was encountered before other
expected data was entered.
OPENDIR: no options (no semicolon)
are allowed.
MERGEDIR: no filename was specified.
LISTDIR: no options (no semicolon)
are allowed.
EXPANDDIR: no options (no semicolon)
are allowed.
ACTION Check syntax of the command or type "help" for
more information.
--------------------------------------------------------------------------
NMGRERR 337 MESSAGE Expected parameter after command. (NMGRERR 337)
CAUSE A parameter is needed after certain commands.
This error occurs if the user does not specify
that parameter. OPENDIR: needs a filename.
MERGEDIR: needs a filename. EXPANDDIR: needs an
integer.
ACTION Check syntax of the command or type "help" for
more information.
--------------------------------------------------------------------------
NMGRERR 338 MESSAGE Unknown or extra keyword parameter specifed.
(NMGRERR 338)
CAUSE This occurs in DELETENODE or MERGEDIR when the
keyword local, global, keep, nokeep, or
timestamp is spelled incorrectly or you have a
duplicate type of keyword. DELETENODE only
allows local or global keywords.
ACTION Check spelling of keywords. Check for duplicate
keyword types. Type "help" for correct syntax.
--------------------------------------------------------------------------
NMGRERR 339 MESSAGE Illegal configuration file name. (NMGRERR 339)
CAUSE Configuration file name is invalid.
ACTION Check the file name for validity. Also, make
sure the name is not too long.
--------------------------------------------------------------------------
NMGRERR 340 MESSAGE Illegal directory file name. (NMGRERR 340)
CAUSE Directory name may be too long, or contains
illegal characters.
ACTION Recheck file name specified.
--------------------------------------------------------------------------
NMGRERR 341 MESSAGE No keywords are allowed for this command.
(NMGRERR 341)
CAUSE This command does not allow keywords.
ACTION Check syntax of the command or type "help" for
more information.
--------------------------------------------------------------------------
NMGRERR 342 MESSAGE NS node name can be from 5 to 50 characters in
length. (NMGRERR 342)
CAUSE The node name length is wrong.
ACTION Check the length of each segment in the node
name. Each segment (name,domain,org) must be
1-16 characters in length.
--------------------------------------------------------------------------
NMGRERR 343 MESSAGE Name segment in node name must be from 1 to 16
chars in length. (NMGRERR 343)
CAUSE The name portion of the node name is the
incorrect length.
ACTION Fix the length of the name in NAME.domain.org.
--------------------------------------------------------------------------
NMGRERR 344 MESSAGE Domain segment in node name must be from 1 to 16
chars in length. (MNGRERR 344)
CAUSE The domain portion of the node name is the
incorrect length.
ACTION Fix the length of the domain in name.DOMAIN.org.
--------------------------------------------------------------------------
NMGRERR 345 MESSAGE org segment in node name must be from 1 to 16
chars in length. (NMGRERR 345)
CAUSE The org portion of the node name is the
incorrect length.
ACTION Fix the length of the org in name.domain.org.
--------------------------------------------------------------------------
NMGRERR 346 MESSAGE Each segment in the node name must begin with an
alphabetic char. (NMGRERR 346)
CAUSE Each segment in node name (name,domain, and org)
must begin with an alphabetic character.
ACTION Check to see that the first char in each segment
is in the set ['A'..'Z'].
--------------------------------------------------------------------------
NMGRERR 347 MESSAGE Node names may only be composed of alpha,
numeric and "_",-. (NMGRERR 347)
CAUSE Illegal character specified.
ACTION Check each segment for an illegal character.
--------------------------------------------------------------------------
NMGRERR 348 MESSAGE Expected the destination path and file to be
formatted as PATH:FILE. (NMGRERR 348)
CAUSE Incorrect format specified.
ACTION Check to make sure that the three
components--path, colon, and file--are present.
--------------------------------------------------------------------------
NMGRERR 349 MESSAGE Expected three filename parameters :
streamfile, nodefile, cmdfile. (NMGRERR 349)
CAUSE File name parameters incorrectly specified.
ACTION Check to make sure that there are three
filenames separated by commas.
--------------------------------------------------------------------------
NMGRERR 350 MESSAGE Expected the source path and file to be
formatted as PATH:FILE. (NMGRERR 350)
CAUSE Incorrect format specified.
ACTION Check to make sure that the three
components--path, colon, and file--are present.
--------------------------------------------------------------------------
NMGRERR 351 MESSAGE Missing comma. (NMGRERR 351)
CAUSE The syntax of the command requires a comma.
ACTION Reissue the command using a comma.
--------------------------------------------------------------------------
NMGRERR 352 MESSAGE Need to update data on previous screen before
adding domain name. (NMGRERR 352)
CAUSE Data was not updated for this node.
ACTION Update the data for this node.
--------------------------------------------------------------------------
NMGRERR 353 MESSAGE The specified path does not point to a paged
data screen. (NMGRERR 353)
CAUSE You did not access a paged data screen which has
only one page.
ACTION Check the path specified in the PATHCONF
command.
--------------------------------------------------------------------------
NMGRERR 354 MESSAGE Entry selected is empty. (NMGRERR 354)
CAUSE User selected an empty selection from the entry
selection window.
ACTION Select an existing entry.
--------------------------------------------------------------------------
NMGRERR 355 MESSAGE Domain labels can only end in an alphabetic
character or digit. (NMGRERR 355)
CAUSE User entered a name which contained a label that
terminated with an invalid character. Valid
terminating characters are A..Z..,a..z, or 0..9.
ACTION Enter the name correctly.
--------------------------------------------------------------------------
NMGRERR 356 MESSAGE Domain labels can only begin with an alphabetic
character. (NMGRERR 356)
CAUSE User entered a domain name which began with an
invalid character. Domain name labels can only
begin with an alphabetic character.
ACTION Enter the name correctly.
--------------------------------------------------------------------------
NMGRERR 357 MESSAGE Domain labels can only consist of A..Z, a..z,
0..9 or -. (NMGRERR 357)
CAUSE User entered an invalid domain name. Valid
characters consist of A..Z, a..z, 0..9 or -.
ACTION Enter the name correctly.
--------------------------------------------------------------------------
NMGRERR 358 MESSAGE Domain label lengths cannot exceed 63
characters. (NMGRERR 358)
CAUSE Valid label length is 1 to 63 characters. User
entered more than 63 characters.
ACTION Enter the name correctly.
--------------------------------------------------------------------------
NMGRERR 359 MESSAGE Domain name is empty. (NMGRERR 359)
CAUSE The user selected an operation which required a
domain, yet neglected to enter a domain.
ACTION Re-enter the information with the domain name
specified.
--------------------------------------------------------------------------
NMGRERR 360 MESSAGE Domain screen can be accessed only after an NS
nodename addition. (NMGRERR 360)
CAUSE User can access the domain screen only after
using the add function key to add an NS
nodename.
ACTION Follow the instructions in "Cause."
--------------------------------------------------------------------------
NMGRERR 361 MESSAGE Select an entry between 1 and 8, or enter the
full node name.
CAUSE User pressed a key which required that an entry
selection be provided.
ACTION User must either select an entry via the entry
field, or enter the full node name in the
nodename field.
--------------------------------------------------------------------------
NMGRERR 362 MESSAGE User cannot add a domain name to a record
already containing one.
CAUSE User attempted to go to the domain screen after
having just added a domain entry.
ACTION None.
--------------------------------------------------------------------------
NMGRERR 363 MESSAGE Entry field must contain a value between 1 and
8. (NMGRERR 363)
CAUSE The entry field was empty or contained a value
not in the range 1 to 8.
ACTION Enter a value in the correct range.
--------------------------------------------------------------------------
NMGRERR 364 MESSAGE Nodename too long. Max for NS is 50; Max for
Domain name is 255. (NMGRERR 364)
CAUSE User entered a name that exceeded 255 characters
for DDN name, or user entered a name that
exceeded 50 characters for NS name.
ACTION Re-enter the name correctly.
--------------------------------------------------------------------------
NMGRERR 365 MESSAGE File name entered is invalid; max length is 36
characters.
CAUSE User entered a file name that exceeded 36
characters.
ACTION Enter a filename of correct length.
--------------------------------------------------------------------------
NMGRERR 366 MESSAGE Domain name entered already exists. (NMGRERR
366)
CAUSE User entered a domain name that already existed
in the directory.
ACTION None.
--------------------------------------------------------------------------
NMGRERR 367 MESSAGE User is not allowed to merge individual domain
entries. (NMGRERR 367)
CAUSE The MERGEDIR command not permit the merging of a
single domain entry. However, you can merge
domain entries as a group, such as all the
global domains or all the local domains.
ACTION None.
--------------------------------------------------------------------------
NMGRERR 368 MESSAGE User must enter: Node Name, Type, Global, and
Enable settings. (NMGRERR 368)
CAUSE User has selected a function that needs the
above information.
ACTION Enter the above information.
--------------------------------------------------------------------------
NMGRERR 369 MESSAGE User cannot select using both Entry Name Field
and Name Field. (NMGRERR 369)
CAUSE User has entered a name into the node name field
and data into the entry number field. User can
only specify one at a time for the operation
selected (update, delete).
ACTION Re-try with the correct information.
--------------------------------------------------------------------------
NMGRERR 370 MESSAGE The options when merging from a configuration
file are LOCAL and GLOBAL. (NMGRERR 370)
CAUSE The user is using the merged command and is
attempting to merge from a configuration file.
In this case, the only valid options that can be
specified are LOCAL and GLOBAL.
ACTION Specify correct options.
--------------------------------------------------------------------------
NMGRERR 371 MESSAGE User must update prior to using NEXT function.
CAUSE User is on the directory data screen and wants
to use NEXT branching. User cannot do so until
the current data is updated.
ACTION Press UPDATE; then NEXT can be used.
--------------------------------------------------------------------------
NMGRERR 380 MESSAGE Problem accessing the existing directory file.
(NMGRERR 380)
CAUSE Maintenance mode interface: An operation on the
existing directory file could not be performed.
The possible operations are: FOPEN the file as
a KSAM file exclusively, FGETINFO and
FGETKEYINFO on the file, or FCLOSE the file with
the delete option.
ACTION Check the accompanying file system error for
more information. If the error reflects an
exclusive access violation, correct the multiple
access and/or the user capabilities.
--------------------------------------------------------------------------
NMGRERR 381 MESSAGE Problem accessing the new (expanded) directory
file. (NMGRERR 381)
CAUSE Maintenance mode interface: An operation on a
COPY of the existing directory file could not be
performed. The possible operations are:
* FOPEN the file (new) as a KSAM file
(opened with a temporary file name
"ZTMPxxxx").
* FWRITE to the file.
* FCLOSE with the save option on.
* FOPEN the data file in copy mode.
* FREADLABEL the data file.
* FWRITELABEL the data file.
* FOPEN the key file in copy mode.
* FREAD from the key file.
* FUPDATE the key file.
* FCLOSE the key file.
ACTION Check the accompanying file system error for
more information. If the error reflects a
security violation, then you are most likely (a)
trying to access a file for read/write access
for which you do not have adequate
capabilitites, or (b) trying to expand the file
in a different account than your logon
account.Since the expand operation involves a
RENAME, you MUST be logged into the same account
as the directory file that you are trying to
expand. If the original directory file does not
exist, but the temporary files (ZTMPxxxx and
"ZTMPxxxK") do exist, then the directory can be
recovered by building a new KSAM file manually
(use KSAMUTIL) with attributes identical to that
of the original file. Use FCOPY to copy the
data and key files SEPARATELY into the newly
built KSAM data and key files. Be sure to use
the ";NOKSAM" option of FCOPY. If the temporary
files do not exist, then the original directory
must be restored from a back-up tape.
--------------------------------------------------------------------------