HP 3000 Manuals HP 3000 Manuals
(Subsystem 104) (contd)
675 MESSAGE Bind to UNSAT procedure failed. (LDRERR 675)
CAUSE After attempting to bind all unresolved externals
to the UNSAT procedure, unsatisfied externals were
still found.
ACTION Make sure the UNSAT procedure is valid.
---------------------------------------------------------------
676 MESSAGE Failed to create the UNSAT TABLE. (LDRERR 676)
CAUSE An error occurred while creating the UNSATISFIED
EXTERNALS TABLE.
ACTION Retry. If this unsuccessful, call your
Hewlett-Packard Representative.
---------------------------------------------------------------
______________________________________________________________
''700'' ''MESSAGE''Unresolvable conflicts in data symbol attributes
(eg., size, access rights, memory residency, etc.)
between duplicate data symbols for the name(s)
listed above. (LDRERR 700)
''CAUSE'' When considering a choice between duplicates, the
LOADER selects the data export with the most
stringent attributes, i.e., the largest size, the
most restricted access rights, and the memory
resident precedence. As an example, considered the
case in which one of the duplicates is the larger
and the other is memory resident. This situation
leads to an unresolvable conflict.
''ACTION'' Examine the data symbols listed for conflicting
attributes.
---------------------------------------------------------------
______________________________________________________________
''701'' ''MESSAGE''
Symbol = !
File = !
First SOM = !
File = !
Second SOM = !
A data symbol cannot be exported by both a thread
private SOM as well as a task global SOM. (LDRERR
701)
''CAUSE'' The program and its libraries have a mixture of
task global and thread private SOMS. A duplicate
data export has been found in a thread private SOM
and also in task global SOM. This condition is not
resolvable by the LOADER.
''ACTION'' Examine the SOMs listed and determine if both SOMs
should be task global or thread private. SOMs can
be examined by using the LINKEDIT command. Use the
HP Link Editor Help facility to obtain help for the
LINKEDIT command.
---------------------------------------------------------------
______________________________________________________________
''702'' ''MESSAGE''
Symbol = !
File = !
Export SOM = !
File = !
Import SOM = !
Task global SOMs cannot import data symbols from
thread private SOMs. (LDRERR 702)
''CAUSE'' The program and its libraries have a mixture of
task global and thread private SOMS. A task global
SOM is requesting to shared a data item with a
thread private SOM which is not allowed.
''ACTION'' Examine the SOMs listed and determine if both SOMs
should be task global or thread private. SOMs can
be examined by using the LINKEDIT command. Use the
HP Link Editor Help facility to obtain help for the
LINKEDIT command.
---------------------------------------------------------------
______________________________________________________________
''703'' ''MESSAGE''
Symbol = !
File = !
Export SOM = !
File = !
Import SOM = !
Based on parmcheck rules the export data symbol
fails to satisfy the import data symbol. (LDRERR
703)
''CAUSE'' The referenced data symbol was found; however, a
difference in type, mode, structure (i.e., array or
pointer), packing, or alignment was detected.
''ACTION'' The message gives the files and the SOMs in which
the data symbol exists. Examine the declaration
for the data symbol as specified in each SOM by
using the LINKEDIT command. Use the HP Link Editor
Help facility to obtain help for the LINKEDIT
command.
---------------------------------------------------------------
______________________________________________________________
''704'' ''MESSAGE''
Symbol = !
File = !
Export SOM = !
File = !
Import SOM = !
Based on residence rules the export data symbol
fails to satisfy the import data symbol. (LDRERR
704)
''CAUSE'' The import SOM is requesting a memory resident data
symbol but the data symbol in the exporting SOM is
not memory resident.
''ACTION'' The message gives the files and the SOMs in which
the data symbol exists. Examine the residence
specification for the data symbol as specified in
each SOM.
---------------------------------------------------------------
______________________________________________________________
''705'' ''MESSAGE''
Symbol = !
File = !
Export SOM = !
File = !
Import SOM = !
Based on rules for access rights the export data
symbol fails to satisfy the import data symbol.
(LDRERR 705)
''CAUSE'' The import SOM is requesting an access rights level
for a data symbol which exceeds the access rights
level of the data symbol in the export SOM.
''ACTION'' The message gives the files and the SOMs in which
the data symbol exists. Examine the access rights
specification for the data symbol as specified in
each SOM by using the LINKEDIT command. Use the HP
Link Editor Help facility to obtain help for the
LINKEDIT command.
---------------------------------------------------------------
______________________________________________________________
''706'' ''MESSAGE''Failed to locate data exports for the data
imports listed above. (LDRERR 706)
''CAUSE'' Unresolved data symbols were encountered while
attempting to load the program and/or libraries.
''ACTION'' Alter the binding sequence to contain the specified
unresolved data symbols.
---------------------------------------------------------------
______________________________________________________________
''707'' ''MESSAGE''
Symbol = !
File = !
Export SOM = !
Failed to allocate a global data area for the SOM
containing the desired data symbol. (LDRERR 707)
''CAUSE'' Unable to allocate a global data area for the SOM
listed in the error message.
''ACTION'' Retry. If unsuccessful, record the symbol name,
the file name, and the SOM listed in the
error message and call your Hewlett-Packard
Representative.
---------------------------------------------------------------
______________________________________________________________
''708'' ''MESSAGE''Failed to allocate the header for the Process
Data Dictionary in the Process File List. (LDRERR
708)
''CAUSE'' Unable to allocate the header for the Process Data
Dictionary.
''ACTION'' Retry. If unsuccessful, call your Hewlett-Packard
Representative.
---------------------------------------------------------------
______________________________________________________________
''709'' ''MESSAGE''Failed to create the Process Data Dictionary.
(LDRERR 709)
''CAUSE'' Unable to create the Process Data Dictionary.
''ACTION'' Retry. If unsuccessful, call your Hewlett-Packard
Representative.
---------------------------------------------------------------
______________________________________________________________
''710'' ''MESSAGE''Failed to place the Process Data Dictionary under
the Symbol Table Management. (LDRERR 710)
''CAUSE'' Unable to put the Process Data Dictionary under
Symbol Table Manager control.
''ACTION'' Retry. If unsuccessful, call your Hewlett-Packard
Representative.
---------------------------------------------------------------
______________________________________________________________
''711'' ''MESSAGE''
Symbol = !
File = !
SOM = !
The export data symbol has an invalid global data
address. (LDRERR 711)
''CAUSE'' A corrupted program/library file was found. An
illegal global address was given to the data
symbol.
''ACTION'' Try rebuilding the program/library file. If
unsuccessful, record the symbol name, the file
name, and the SOM listed in the error message and
call your Hewlett-Packard Representative.
---------------------------------------------------------------
______________________________________________________________
''712'' ''MESSAGE''
Symbol = !
Existent file = !
Export SOM = !
New file = !
SOM = !
Duplicate data symbols cannot be replaced across
different load points. (LDRERR 712)
''CAUSE'' A data symbol was found while dynamically loading a
library which requires a replacement of a
previously bound duplicate. The LOADER cannot
replace an already bound data symbol. The data
symbol attributes from the SOM in the new file
exceeds the data symbol attributes of the current
data symbol.
''ACTION'' The message gives the file and the SOM in which the
current data symbol exists. Compare the data
symbol declarations in both SOMs. The data symbol
from the export SOM in the existent file must be
the most stringent in all attributes (i.e .,
largest size, memory residence, and most restricted
access rights).
---------------------------------------------------------------
______________________________________________________________
''713'' ''MESSAGE''
Symbol = !
File = !
Export SOM = !
File = !
New SOM = !
A duplicate data symbol has been found but is not
allowed. (LDRERR 713)
''CAUSE'' The duplicate data symbol option hasn't been
specified.
''ACTION'' Check the LINKEDIT command for the proper handling
of duplicate export data symbols. Use the HP Link
Editor Help facility to obtain help for the
LINKEDIT command.
---------------------------------------------------------------
______________________________________________________________
''714'' ''MESSAGE''The number of dummy data symbols in the Process
Data Dictionary are invalid. (LDRERR 714)
''CAUSE'' An error occurred in counting the occurences of
unresolvable conflicts between duplicate data
exports in regard to their attributes (i.e., size,
access rights, memory residency, etc.).
''ACTION'' Retry. If unsuccessful, call your Hewlett-Packard
Representative.
---------------------------------------------------------------
______________________________________________________________
''715'' ''MESSAGE''Failed to obtain a new entry for a data symbol
through the Symbol Table Management. (LDRERR 715)
''CAUSE'' Failure by the Symbol Table Manager to create a new
entry.
''ACTION'' Retry. If unsuccessful, call your Hewlett-Packard
Representative.
---------------------------------------------------------------
______________________________________________________________
''716'' ''MESSAGE''Failed to retrieve a data symbol from the Process
Data Dictionary. (LDRERR 716)
''CAUSE'' Failure by the Symbol Table Manager to retrieve an
existent entry.
''ACTION'' Retry. If unsuccessful, call your Hewlett-Packard
Representative.
---------------------------------------------------------------
______________________________________________________________
''717'' ''MESSAGE''Failed to delete a data symbol from the Process
Data Dictionary. (LDRERR 717)
''CAUSE'' Failure by the Symbol Table Manager to delete an
entry.
''ACTION'' Retry. If unsuccessful, call your Hewlett-Packard
Representative.
---------------------------------------------------------------
______________________________________________________________
''718'' ''MESSAGE''No Loader Process File List entry for the given
PIN. (LDRERR 718)
''CAUSE'' The native mode LOADER has no information for the
specified PIN. The process may be a compatibility
mode process. This situation was encountered
because of a request to retrieve a data symbol
location.
''ACTION'' Check the specification of the PIN.
---------------------------------------------------------------
______________________________________________________________
''719'' ''MESSAGE''
File = !
SOM = !
The SOM is not a Shared Global SOM. (LDRERR 719)
''CAUSE'' The native mode LOADER has detected a SOM that is
marked as non-shared but was previously treated as
Shared Global type. This is probably an internal
LOADER bug.
''ACTION'' Examine the SOM listed and determine if it should
be of Shared Global Data type. SOMs can be
examined by using the LINKEDIT command. Use the HP
Link Editor Help facility to obtain help for the
LINKEDIT command.
---------------------------------------------------------------
______________________________________________________________
''720'' ''MESSAGE''Attempting to bind a function pointer imported by
a data symbol causes unresolved code symbol(s)
during a dynamic load of a data symbol. (LDRERR
720)
''CAUSE'' Your request for a particular shared data symbol by
using HPGETPROCPLABEL has resulted in the binding
of function pointer declared as an imported data
symbol. After attempting to bind all unresolved
code symbols, unsatisfied externals were still
found.
''ACTION'' Check to make sure that all function pointers which
are requested in the dynamic load are valid and
will not lead to requests for code symbols which
are not in the current process.
---------------------------------------------------------------
______________________________________________________________
''800'' ''MESSAGE''
Data symbol = !
Failed to locate the data symbol in the Process
Data Dictionary. (LDRERR 800)
''CAUSE'' The data symbol requested is not in the current
process.
''ACTION'' Check the symbol to determine if the correct symbol
was requested. If not correct, then request with
the correct symbol. Check to see if the
CASESENSITIVE parameter of the HPGETPROCPLABEL
intrinsic is correctly set.
---------------------------------------------------------------
______________________________________________________________
''801'' ''MESSAGE''
File = !
The file being loaded does not have a valid
privilege value. (LDRERR 801)
''CAUSE'' The file has been built with the incorrect
capabilities because they have resulted in
privilege level that fails the Loader privilege
check.
''ACTION'' Obtain the correct capability for the specified
file.
---------------------------------------------------------------
______________________________________________________________
''802'' ''MESSAGE''A new binding sequence requires symbol resolution
through the program but there is no native mode
program file entry in the Process File List.
(LDRERR 802)
''CAUSE'' HPGETPROCPLABEL intrinsic was called with the
POSITION parameter set to PROG, but there is no
native program at the beginning of the static
binding sequence.
''ACTION'' The POSITION parameter is used only for binding
sequence which connects to the native mode program
or the subsystem library. Check to see if the
program is a CM program. If it is, you cannot use
the POSITION parameter to connect the new binding
sequence to the program.
---------------------------------------------------------------
______________________________________________________________
''803'' ''MESSAGE''
Procedure name = !
Search File = !
A pointer to the procedure in the specified file
was requested but that procedure is not present.
(LDRERR 803)
''CAUSE'' The procedure requested to be dynamically loaded
from a specified file can not be found.
''ACTION'' Check to make sure the requested procedure is in
the file specified.
---------------------------------------------------------------