System Generation Manual for G-Series RVUs

nld Messages
System Generation Manual for G-Series RVUs—523407-001
C-2
nld Message Descriptions
Cause. nld has created a temporary file, but cannot purge the existing file of the same
name in order to rename the temporary file to that name. This can happen if
filename is secured so that nld cannot purge it, or if filename is currently open.
Effect. SYSGENR terminates.
Recovery. Depending on file-system error nnn, resecure or close the file and rerun
SYSGENR.
Cause. The file filename existed when nld started, but disappeared while nld was
running, generating file-system error nnn.
Effect. SYSGENR terminates.
Recovery. Refer to the Guardian Procedure Errors and Messages Manual for
corrective action for file-system error nnn. Then rerun SYSGENR.
Cause. nld has found inconsistent information among two or more input files.
Possible causes include the following:
•
pTAL users might have forgotten to specify EXPORT_GLOBALS when compiling
the module that defines dataname.
•
Shared run-time library (SRL) clients might not have specified the filename of the
SRL that exports dataname.
•
If SRL clients did specify the filename of the SRL that exports dataname, then
they might not have exported dataname when building that SRL.
Effect. SYSGENR terminates.
Recovery. Gather the items listed on page C-1, then call your service provider.
Can’t {purge|rename} existing file ‘filename‘, file error
nnn.
Can’t re-open filename, file error nnn.
Data block ‘dataname’ is referenced but never defined.
The first reference was in filename.
For a list of all the places where it is referenced,
run nld again with the ‘-y dataname’ option.