HP 3000 Manuals HP 3000 Manuals
NMGRERR Messages (contd.)
NMGRERR 382 MESSAGE Incompatible version of KSAM for file rename
operation. (NMGRERR 382)
CAUSE Maintenance mode interface: The location of
internal KSAM data and key information has
changed and thus cannot be updated with this
version of the NMC software.
ACTION For an intermediate solution, use KSAMUTIL to
build a larger (expanded) file and use FCOPY to
copy the directory to the new file. If the
problem still exists, see "Submitting an SR" at
the beginning of this appendix.
--------------------------------------------------------------------------
NMGRERR 383 MESSAGE Cannot specify a negative number for expansion.
(NMGRERR 383)
CAUSE Maintenance mode interface: The user gave a
negative number of records to expand the file.
ACTION Supply a positive number of records.
--------------------------------------------------------------------------
NMGRERR 384 MESSAGE Cannot open command file "NMMGRCMD". (NMGRERR
384)
CAUSE The command file NMMGRCMD could not be opened.
ACTION Check for any file equations set for "NMMGRCMD".
See the accompanying file system error message
for problem resolution.
--------------------------------------------------------------------------
NMGRERR 385 MESSAGE An NMMGR configuration file name must be
specified. (NMGRERR 385)
CAUSE Maintenance mode interface:An error message is
issued when the configuration file argument for
the OPENCONF command is missing.
ACTION Reissue the command with the configuration file
name.
--------------------------------------------------------------------------
NMGRERR 386 MESSAGE Invalid subsystem name, enter valid name (ie
NETXPORT). (NMGRERR 386)
CAUSE Maintenance mode interface:An error message is
issued when an invalid subsystem name is
entered.
ACTION Reissue the comand with a correct subsystem
name.
--------------------------------------------------------------------------
NMGRERR 387 MESSAGE Unable to OPEN, and unable to CREATE config
file.
(NMGRERR 387)
CAUSE File system error.
ACTION Check to see if user is allowed to access file.
Check to see if user and account capabilities of
NA or NM are set.
--------------------------------------------------------------------------
NMGRERR 388 MESSAGE Attempted to access non data or page data screen
with PATHCONF. (NMGRERR 388)
CAUSE Incorrect use of PATHCONF command.
ACTION Make sure that the screen you are trying to
access is data or paged data. This can be
checked by looking at the screen and seeing if
there is a data flag in the upper right corner
of the screen. If not, you are trying to access
a screen which has no data fields.
--------------------------------------------------------------------------
NMGRERR 389 MESSAGE Attempted to access a field which does not
exist. (NMGRERR 389)
CAUSE You are trying to access a field N+k when there
are only N fields on the form.
ACTION Use NMMGR to go to the path which you specified
in the PATHCONF command. Make sure that your
field count matches the field number you are
trying to access. Make sure you are not trying
to use Vplus field numbers to access the field.
--------------------------------------------------------------------------
NMGRERR 390 MESSAGE Path not specified, or path specified does not
exist. (NMGRERR 390)
CAUSE PATHCONF was not previously issued.
ACTION Check to see if you set the path with the
PATHCONF command. Check to see if the path that
you specified exists in the configuration file.
--------------------------------------------------------------------------
NMGRERR 391 MESSAGE Version stamp in VERSIONCONF does not match
NMMGR version. (NMGRERR 391)
CAUSE Version stamp must match NMMGR version.
ACTION Change the version stamp in your batch file to
match the version displayed on the NMMGR banner
line.
--------------------------------------------------------------------------
NMGRERR 392 MESSAGE VERSIONCONF must be called before this command
may be called. (NMGRERR 392)
CAUSE Tried to perform OPENCONF before VERSIONCONF.
ACTION Call VERSIONCONF with the version stamp which
NMMGR displays on the banner line.
--------------------------------------------------------------------------
NMGRERR 393 MESSAGE Missing or invalid destination path name.
(NMGRERR 393)
CAUSE The copyconf command will not operate without a
valid destination path.
ACTION Check to make sure an NMCONF path name was
specified for the copyconf command.
--------------------------------------------------------------------------
NMGRERR 394 MESSAGE Missing or invalid destination file name.
(NMGRERR 394)
CAUSE The copyconf command will not operate without a
valid destination file name.
ACTION Check to make sure that an MPE file name was
specified after the colon (:) delimiter in the
copyconf command.
--------------------------------------------------------------------------
NMGRERR 395 MESSAGE Invalid option specified for copyconf command.
(NMGRERR 395)
CAUSE An option other than KEEP was specified.
ACTION Retry with valid option.
--------------------------------------------------------------------------
NMGRERR 400 MESSAGE Cannot open the nodelist file. (NMGRERR 400)
CAUSE The nodelist file could not be opened for
read/write access.
ACTION See the accompanying file system error message
for resolution.
--------------------------------------------------------------------------
NMGRERR 401 MESSAGE Record size of nodelist file too small; must be
>>= 80 bytes. (NMGRERR 401)
CAUSE The record size of the nodelist file is too
small to be used.
ACTION If creating the nodelist file using the LISTDIR
command, then do not include a ;REC= parameter
in the file equation. Copy the nodelist file
into a file with a larger record width.
--------------------------------------------------------------------------
NMGRERR 402 MESSAGE Filecode of nodelist file non zero. (NMGRERR
402)
CAUSE The nodelist file supplied did not have a 0
filecode--it was not a standard EDITOR-type
file.
ACTION If creating the nodelist file using the LISTDIR
command, then do not include a ;CODE= parameter
in the file equation. Copy the nodelist file
into a file created with no file code.
--------------------------------------------------------------------------
NMGRERR 403 MESSAGE FREADDIR failed trying to read from nodelist
file. (NMGRERR 403)
CAUSE Could not issue a directed read to the nodelist
file. The file most likely has a
variable-length record structure.
ACTION See the accompanying file system error message
for resolution.
--------------------------------------------------------------------------
NMGRERR 404 MESSAGE FWRITEDIR failed trying to write to nodelist
file. (NMGRERR 404)
CAUSE Could not issue a directed write against the
nodelist file.
ACTION See the accompanying file system error message
for resolution.
--------------------------------------------------------------------------
NMGRERR 405 MESSAGE Cannot close nodelist file. (NMGRERR 405)
CAUSE Could not close the nodelist file.
ACTION See the accompanying file system error message
for resolution.
--------------------------------------------------------------------------
NMGRERR 406 MESSAGE FCONTROL failed trying to set EOF marker on
nodelist file. (NMGRERR 406)
CAUSE Internal error.
ACTION See "Submitting an SR" at the beginning of this
appendix.
--------------------------------------------------------------------------
NMGRERR 407 MESSAGE FPOINT failed on nodelist file. (NMGRERR 407)
CAUSE Could not set the record pointer in the nodelist
file.
ACTION See the accompanying file system error message
for resolution.
--------------------------------------------------------------------------
NMGRERR 408 MESSAGE FGETINFO failed on nodelist file. (NMGRERR 408)
CAUSE Internal error.
ACTION See "Submitting an SR" at the beginning of this
appendix.
--------------------------------------------------------------------------
NMGRERR 409 MESSAGE FREAD failed trying to read from nodelist file.
(NMGRERR 409)
CAUSE Could not read sequentially from the nodelist
file.
ACTION See the accompanying file system error message
for resolution.
--------------------------------------------------------------------------
NMGRERR 410 MESSAGE Cannot gain access to the stream file. (NMGRERR
410)
CAUSE A check to verify that the stream file does not
already exist could not be completed.
ACTION See the accompanying file system error message
for resolution.
--------------------------------------------------------------------------
NMGRERR 411 MESSAGE The stream file already exists; choose another
name. (NMGRERR 411)
CAUSE The stream file given already exists as a
permanent file. The MAKESTREAM command requires
that this file not exist.
ACTION Choose another file name or rename the existing
file to another name.
--------------------------------------------------------------------------
NMGRERR 412 MESSAGE Cannot gain access to the command file.
(NMGRERR 412)
CAUSE A check to verify that the command file does
exist could not be completed.
ACTION See the accompanying file system error message
for resolution.
--------------------------------------------------------------------------
NMGRERR 413 MESSAGE The command file does not exist. (NMGRERR 413)
CAUSE The command file given does not exist.
ACTION Supply the name of an existing command file.
--------------------------------------------------------------------------
NMGRERR 414 MESSAGE Internal catalog error: job text identifier
table overflow. (NMGRERR 414)
CAUSE Message catalog NMMGRCAT.PUB.SYS incorrect.
ACTION RESTORE NMMGRCAT.PUB.SYS from a backup tape. If
the problem still exists, see "Submitting an SR"
at the beginning of this appendix.
--------------------------------------------------------------------------
NMGRERR 415 MESSAGE Internal catalog error: incorrect format for
job text ID entry. (NMGRERR 415)
CAUSE Message catalog NMMGRCAT.PUB.SYS is incorrect.
ACTION RESTORE NMMGRCAT.PUB.SYS from a backup tape. If
the problem still exists, see "Submitting an SR"
at the beginning of this appendix.
--------------------------------------------------------------------------
NMGRERR 416 MESSAGE Error converting a catalog entry into a numeric
value. (NMGRERR 416)
CAUSE Internal error.
ACTION RESTORE NMMGRCAT.PUB.SYS from a backup tape. If
the problem still exists, see "Submitting an SR"
at the beginning of this appendix.
--------------------------------------------------------------------------
NMGRERR 417 MESSAGE Catalog entry value not in range - 32768-3276
(NMGRERR 417)
CAUSE Message catalog NMMGRCAT.PUB.SYS incorrect.
ACTION RESTORE NMMGRCAT.PUB.SYS from a backup tape. If
the problem still exists, see "Submitting an SR"
at the beginning of this appendix.
--------------------------------------------------------------------------
NMGRERR 418 MESSAGE Cannot read an entry from the message catalog.
(NMGRERR 418)
CAUSE Message catalog NMMGRCAT.PUB.SYS incorrect.
ACTION RESTORE NMMGRCAT.PUB.SYS from a backup tape. If
the problem still exists, see "Submitting an SR"
at the beginning of this appendix.
--------------------------------------------------------------------------
NMGRERR 419 MESSAGE Cannot open the stream file. (NMGRERR 419)
CAUSE The stream file could not be opened.
ACTION See the accompanying file system error message
for resolution.
--------------------------------------------------------------------------
NMGRERR 420 MESSAGE FWRITE failed trying to write to the stream
file.
(NMGRERR 420)
CAUSE Could not write to the stream file. Most
likely, the end-of-file has been reached and the
file is full.
ACTION See the accompanying file system error message
for resolution. If end-of-file has been
reached, issue a file equation for the stream
file: FILE yourfile;DISC=nnnn,32,1 where
"yourfile" is the name of the stream file, and
"nnnn" is the number of records needed in the
file. Approximately 150 records should be
allocated for each node in the nodelist file.
Note that the stream file is created as a
variable-length file, so fewer records should be
required per node. The file is opened with a
default of 5000 records. Retry the MAKESTREAM
command with the new file equation.
--------------------------------------------------------------------------
NMGRERR 421 MESSAGE Cannot close the stream file. (NMGRERR 421)
CAUSE The stream file could not be closed.
ACTION See the accompanying file system error message
for resolution.
--------------------------------------------------------------------------
NMGRERR 500 MESSAGE Missing equal sign. (NMGRERR 500)
CAUSE An equal sign was missing in the command syntax.
ACTION Re-enter the command with the proper syntax.
--------------------------------------------------------------------------
NMGRERR 501 MESSAGE Missing or invalid pathname parameter. (NMGRERR
501)
CAUSE The syntax of the command requires a pathname
parameter.
ACTION Check pathname and reissue the command.
--------------------------------------------------------------------------
NMGRERR 502 MESSAGE Missing or invalid field number. (NMGRERR 502)
CAUSE Either the field number parameter was not
specified or the field number was not terminated
with a comma.
ACTION Check the field number on the screen.
--------------------------------------------------------------------------
NMGRERR 503 MESSAGE Missing data. Data follows a comma. (NMGRERR
503)
CAUSE WRITECONF command did not list data to be
stored.
ACTION The syntax of the command requires a data
parameter. The data may be enclosed in quotes.
--------------------------------------------------------------------------
NMGRERR 504 MESSAGE Invalid option specified. (NMGRERR 504)
CAUSE An invalid option was specified for the command.
ACTION Use help to enter correct option.
--------------------------------------------------------------------------
NMGRERR 505 MESSAGE Missing or invalid version string. (NMGRERR
505)
CAUSE Did not specify version correctly.
ACTION The syntax of the command requires a valid
version string parameter.
--------------------------------------------------------------------------
NMGRERR 506 MESSAGE Missing or invalid page number. (NMGRERR 506)
CAUSE The syntax of the command requires a page
number.
ACTION The page number must be a positive integer.
--------------------------------------------------------------------------
NMGRERR 507 MESSAGE Invalid path, a select or type select path is
required. (NMGRERR 507)
CAUSE The path must be for a select or type select
screen.
ACTION Check the path and reissue.
--------------------------------------------------------------------------
NMGRERR 508 MESSAGE Unable to open Formlist as OLD or NEW. (NMGRERR
508)
CAUSE File system error.
ACTION Check the file equation. See if the file is
locked open or cannot be accessed. Check to see
if there is disk space.
--------------------------------------------------------------------------
NMGRERR 509 MESSAGE The new data is larger than the field size.
(NMGRERR 509)
CAUSE WRITECONF error.
ACTION Check to see that you are accessing the correct
field, or reduce the size of the data you are
entering.
--------------------------------------------------------------------------