System Generation Manual for G-Series RVUs

XLLINK Messages
System Generation Manual for G-Series RVUs—523407-001
B-4
XLLINK Message Descriptions
Recovery. Verify that all the data needs to be global and shared. If it does, cluster the
read-write data into one global data block. If some of the data does not, redefine it in a
private data block.
11
Cause. One of the files listed in the SYSTEM_LIBRARY_CODE_FILES entry is not a
type 100 file. You must not run XLLINK outside of SYSGENR.
Effect. XLLINK terminates.
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.
12
Cause. The files filename1 and filename2 contain a procedure with the same
procname name.
Effect. XLLINK terminates.
Recovery. If you are accelerating your own system code and system library, make
sure that procedure names are unique. Rerun the Accelerator against your programs
with the modified procedure name or names, then rerun DSM/SCM or SYSGENR. If
filename1 and filename2 are objects supplied by HP, gather the items listed on
page B-1, then call your service provider.
13
Cause. The number of TNS instructions in the object file filename1 is different from
the number of TNS instructions in the object file filename2. You must not run
XLLINK outside of SYSGENR.
Effect. XLLINK terminates.
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.
Component file filename is not type-100.
Procedure procname appears in both component file filename1
and component file filename2.
The size of the procedure procname differs between the TNS
object file filename1 and the component file filename2.