Using the Node Management Services (NMS) Utilities (32022-90053)

254 AppendixA
NMS Error Messages
NMGR Error and Warning Messages
MESSAGE: Problem accessing the new (expanded) directory file.
(NMGRERR 381)
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 capabilities, 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.
MESSAGE: Incompatible version of KSAM for file rename operation.
(NMGRERR 382)
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.