System Generation Manual for G-Series RVUs

XLLINK Messages
System Generation Manual for G-Series RVUs—523407-001
B-3
XLLINK Message Descriptions
Recovery. If you receive this message when running DSM/SCM or SYSGENR, gather
the items listed on page B-1, then call your service provider.
6
Cause. XLLINK has found more than one fully bound TNS system code or system
library file (by a TNS file option). You must not run XLLINK outside of SYSGENR.
Effect. The file supplied in the TNSFile option is copied as the TNS region in the
executable output file.
Recovery. If you receive this message when running DSM/SCM or SYSGENR, gather
the items listed on page B-1, then call your service provider.
7
Cause. The file supplied with the TNSFile option is not a type 100 file. You must not
run XLLINK outside of SYSGENR.
Effect. XLLINK does not generate an output object file.
Recovery. If you receive this message when running DSM/SCM or SYSGENR, gather
the items listed on page B-1, then call your service provider.
9
Cause. The Accelerator has run but did not accelerate filename.
Effect. XLLINK does not produce a TNS/R system code file.
Recovery. If filename refers to your own component file, use the Accelerator to
accelerate that file before running SYSGENR. If filename refers to a file supplied by
HP, gather the items listed on page B-1, then call your service provider.
10
Cause. You can use XLLINK to link files only if your program has one read/write data
block; however, XLLINK has detected more than one.
Effect. XLLINK cannot link this program.
More than one TNS object file was provided.
TNS object file filename is not type-100.
Component file filename has not been accelerated.
The program has more than one read/write data block.