Loader, Native Mode (Subsystem 104)
MPE documents | |
 Complete PDF | |
| Table of Contents | |
| E0701 Volume II ♥ | |
| E0300 Volume I | |
| E0300 Volume II | |
| E0300 Volume III | |
| E0394 Volume I | |
| E0796 Volume II | |
| E0494 Volume III |
Loader Errors 1 - 99
- 1
- MESSAGE
CM loader returned with a warning. (LDRWARN 1)
- CAUSE
A warning occurred while loading the CM program.
- ACTION
See text, which should also be displayed, for the specific CM program.
- 2
- MESSAGE
LIBRARY ! was not used. (LDRWARN 2)
- CAUSE
All external references have been resolved by the time the specified library was reached while searching the binding sequence.
- ACTION
If the program successfully loads and runs, then remove the specified library from the binding sequence.
- 3
- MESSAGE
LIBRARY ! was not found. (LDRWARN 3)
- CAUSE
The specified library was not found.
- ACTION
Determine why the specified library is missing.
- 4
- MESSAGE
LIBRARY ! was searched but not referenced. (LDRWARN 4)
- CAUSE
No external procedure references were resolved to the specified library.
- ACTION
If the application runs, the specified library may be able to be eliminated from the binding sequence.
- 5
- MESSAGE
NL.PUB.SYS was not specified as the last file in the binding sequence. (LDRWARN 5)
- CAUSE
The system library is not the last file in the binding sequence.
- ACTION
Reorder the files in the binding sequence appropriately.
- 6
- MESSAGE
Invalid MAX PRIV OF ! was specified; default of user mode was used. (LDRWARN 6)
- CAUSE
The maximum privileged level specified is out of the valid range.
- ACTION
Retry with a correct value.
- 7
- MESSAGE
An invalid stacksize of ! bytes was specified; ! was used. (LDRWARN 7)
- CAUSE
The value specified for the stack size is invalid.
- ACTION
Retry with a correct value.
- 8
- MESSAGE
An invalid heapsize of ! specified; ! used. (LDRWARN 8)
- CAUSE
The value specified for the heap size is invalid.
- ACTION
Retry with a correct value.
- 9
- MESSAGE
CM unloader returned with a warning. (LDRWARN 9)
- CAUSE
A warning occurred while unloading the CM program.
- ACTION
See cause and action for the specific CM unload warning which occurred.
- 10
- MESSAGE
XLLIST parameter is ignored for CM programs.
(LDRWARN 10)- CAUSE
The 'XL=' parameter was specified and is not applicable to CM programs.
- ACTION
Remove the 'XL=' parameter.
- 11
- MESSAGE
XLLIST= and LIB= are mutually exclusive. XLLIST= was used; LIB= was ignored. (LDRWARN 11)
- CAUSE
The 'XL=' parameter and the 'LIB=' parameters were both specified.
- ACTION
Specify only one of the parameters.
- 12
- MESSAGE
The configured default stack size of ! bytes is too small; ! used. (LDWARN 12)
- CAUSE
The default stack size in the configuration files is too small.
- ACTION
Use SYSGEN to change the configured default stack size.
- 13
- MESSAGE
The configured maximum stack size of ! bytes is too small; ! used. (LDRWARN 13)
- CAUSE
The configured maximum stack is too small.
- ACTION
Use SYSGEN to change the configured maximum stack size.
- 14
- MESSAGE
The configure maximum heap size if ! bytes is too small; ! used. (LDRWARN 14)
- CAUSE
The configured maximum heap size is too small.
- ACTION
Use SYSGEN to change the configured maximum heap size.
- 17
- MESSAGE
Program auxiliary header not found; defaults used. (LDRWARN 17)
- CAUSE
Same as message content.
- ACTION
Check the way the program was built.
- 40
- MESSAGE
The system library (NL.PUB.SYS) contains an invalid internal file type identifier. (LDRERR 40)
- CAUSE
The system library is not an executable file.
- ACTION
Try updating your machine or call your Hewlett-Packard Representative.
- 41
- MESSAGE
Loader can not load page with gateway access type. (LDRERR 41)
- CAUSE
Invalid access rights (a gateway page) was encountered.
- ACTION
Try updating your machine or call your Hewlett-Packard Representative.
- 42
- MESSAGE
Allocation of OSINFO TABLE entry failed. (LDRERR 42)
- CAUSE
An error occurred while creating a system object.
- ACTION
Try rebooting. If unsuccessful, call your Hewlett-Packard Representative.
- 50
- MESSAGE
The loader failed to get the group capabilities from the file system. (LDRERR 50)
- CAUSE
Unable to obtain the capabilities for the specified group.
- ACTION
Check the group specified and retry. If unsuccessful, then call your Hewlett-Packard Representative.
- 51
- MESSAGE
The loader failed to get file info from FLABELINFO. (LDRERR 51)
- CAUSE
An error was returned from the FLABELINFO intrinsic.
- ACTION
See cause and action for the specified file system error.
- 52
- MESSAGE
The loader failed to get file information from the file system. (LDERR 52)
- CAUSE
An error occurred obtaining file information about the specified file.
- ACTION
Check the specified file. Recreate if necessary. If unsuccessful, then call your Hewlett-Packard Representative.
- 53
- MESSAGE
Invalid file designator specified. (LDRERR 53)
- CAUSE
The format of the specified file name is incorrect.
- ACTION
Retry with the correct file format.
- 54
- MESSAGE
There is an invalid option in the file equation. (LDRERR 54)
- CAUSE
An invalid option was found in a file equation for the specified file.
- ACTION
Check the file equation.
- 55
- MESSAGE
Missing file equation. (LDRERR 55)
- CAUSE
A file equation for the specified back referenced file was not found.
- ACTION
Check the file name specification or issue an appropriate file equation.
- 56
- MESSAGE
HPFOPEN failed. (LDRERR 56)
- CAUSE
An error occurred while opening the specified file.
- ACTION
See the cause and action for the file system error which should also be displayed.
Loader Errors 100 - 199
- 100
- MESSAGE
The system procedure name was not found in NL.PUB.SYS (LDRERR 100)
- CAUSE
Requested system procedure, during dynamic load, was not found.
- ACTION
Check the specification of the procedure name.
- 101
- MESSAGE
System SOM containing the given procedure is not loaded. (LDRERR 101)
- CAUSE
Internal error. System SOM, where the specified procedure resides, is not loaded.
- ACTION
Try again. If the problem continues, then call your Hewlett-Packard Representative.
- 102
- MESSAGE
The procedure failed to FREEZE the system PLABEL in memory. (LDRERR 102)
- CAUSE
Attempt to FREEZE in memory the XRT associated with the dynamic load of a memory resident procedure failed.
- ACTION
Retry. If problem continues, call your Hewlett-Packard Representative.
- 103
- MESSAGE
Dynamic loading unresolved external: ! (LDRERR 103)
- CAUSE
Unresolved external references of the procedure requested to be dynamically loaded exist.
- ACTION
Check the binding sequence of the dynamic load request.
- 104
- MESSAGE
The procedure failed to obtain the previous stack frame INFO. (LDRERR 104)
- CAUSE
Unable to obtain information from the previous stack frame.
- ACTION
Retry. If the problem continues, call your Hewlett-Packard Representative.
- 105
- MESSAGE
Bad procedure name specified. (LDRERR 105)
- CAUSE
The procedure name parameter specification is invalid.
- ACTION
Check the procedure name specification.
- 106
- MESSAGE
Bad FIRSTFILE name specified. (LDRERR 106)
- CAUSE
The FIRSTFILE name specified during the dynamic load is invalid.
- ACTION
Check the FIRSTFILE specification.
- 107
- MESSAGE
Bad library name specified. (LDRERR 107)
- CAUSE
The filename specification is invalid.
- ACTION
Check the filename specification.
- 109
- MESSAGE
No LOADER PROCESS FILE LIST for the given PIN. (LDRERR 109)
- CAUSE
The NATIVE MODE LOADER has no information for the specified PIN. The process may be a COMPATIBILITY MODE process.
- ACTION
Check the specification of the PIN.
- 110
- MESSAGE
The FIRSTFILE is not loaded (LDRERR 110)
- CAUSE
The specified file is not loaded by the specified process.
- ACTION
Check the file and process specifications.
- 111
- MESSAGE
The SOM containing the specified procedure name is not loaded. (LDRERR 111)
- CAUSE
The SOM associated with the SOM is not loaded.
- ACTION
Check why the SOM was not loaded prior to requesting information about how it is loaded.
- 112
- MESSAGE
Unable to find the specified procedure. (LDRERR 112)
- CAUSE
The procedure which was requested to by dynamically loaded was not found in the specified binding sequence.
- ACTION
Check the procedure name specification and/or libraries in the binding sequence.
- 113
- MESSAGE
There is no loaded file with the specified SID for the specified PIN. (LDRERR 113)
- CAUSE
The specified file is not loaded by the specified PIN.
- ACTION
Check the file specification and the process specification.
- 114
- MESSAGE
Unable to obtain the system PLABEL TABLE pointer. (LDRERR 114)
- CAUSE
Internal error. System PLABEL TABLE was not found.
- ACTION
Retry. If problem continues, try rebooting. If this is unsuccessful, call your Hewlett-Packard Representative.
- 115
- MESSAGE
Unable to find the given PLABEL in the system PLABEL TABLE. (LDRERR 115)
- CAUSE
Unable to find specified PLABEL in the system PLABEL TABLE.
- ACTION
Check the PLABEL specification. Check to make sure the PLABEL was loaded before it is trying to be released.
- 116
- MESSAGE
Unable to obtain the user's capabilities. (LDRERR 116)
- CAUSE
Unable to obtain the capabilities of the user.
- ACTION
Retry. If the problem continues, call your Hewlett-Packard Representative.
- 117
- MESSAGE
Unable to create the process PLABEL TABLE. (LDRERR 117)
- CAUSE
Unable to create the PLABEL TABLE for the dynamic load request.
- ACTION
Retry. If the problem continues, call your Hewlett-Packard Representative.
- 118
- MESSAGE
Unable to obtain an entry for the process PLABEL TABLE header. (LDRERR 118)
- CAUSE
Unable to create the header entry from the PLABEL TABLE during the dynamic load request.
- ACTION
Retry. If the problem continues, call your Hewlett-Packard Representative.
- 119
- MESSAGE
Unable to access a parameter passed to the LOADER intrinsic. (LDRERR 119)
- CAUSE
A bad parameter was specified.
- ACTION
Check the parameters specified.
- 120
- MESSAGE
This is an invalid NM library file code. (LDRERR 120)
- CAUSE
The specified library has a bad file code.
- ACTION
Rebuild the specified library.
- 121
- MESSAGE
Unable to get an entry from the process PLABEL TABLE. (LDRERR 121)
- CAUSE
Unable to obtain entry in the PLABEL TABLE for the dynamic load request.
- ACTION
Retry. If the problem continues, call your Hewlett-Packard Representative.
- 122
- MESSAGE
Invalid PLABEL specified. (LDRERR 122)
- CAUSE
The specified PLABEL is invalid.
- ACTION
Check the specified PLABEL.
- 123
- MESSAGE
Invalid FIRSTLIBRARY file name specified. (LDRERR 123)
- CAUSE
The filename specified in the FIRSTLIBRARY parameter is invalid.
- ACTION
Check the FIRSTLIBRARY specification.
- 124
- MESSAGE
Invalid MYFILE file name specified. (LDRERR 124)
- CAUSE
Internal error. The internally stored filename for the requested file is invalid.
- ACTION
Retry. If the problem persists, call your Hewlett-Packard Representative.
- 125
- MESSAGE
Invalid MYPROGRAM file name specified. (LDRERR 125)
- CAUSE
Internal error. The internally maintained filename for the requested file is invalid.
- ACTION
Retry. If the problem continues, call your Hewlett-Packard Representative.
- 128
- MESSAGE
The file name cannot be represented using the desired syntax. (LDRERR 128)
- CAUSE
MPE syntax is not appropriate to represent an HFS file. Not all MPE files (for example $OLDPASS) can be represented by an HFS pathname.
- ACTION
Use the appropriate syntax to retrieve the name.
Loader Errors 200 - 299
- 200
- MESSAGE
Parameter check error - mismatched data type in argument number !. Procedure = !, Files = !. (LDRERR 200)
- CAUSE
The referenced procedure was bound, however
- ACTION
Check formal and actual parameters for the specified procedure.
- 201
- MESSAGE
Parameter check error - mismatched mode in argument number !. Procedure = !, Files = !. (LDRERR 201)
- CAUSE
The referenced procedure was found; however, a difference in the mode of a parameter (i.e., value or reference) was detected.
- ACTION
Check the external declaration of the procedure.
- 202
- MESSAGE
Parameter check error - mismatched structure in argument number !. Procedure = !, Files = !. (LDRERR 202)
- CAUSE
The referenced procedure was found; however, a difference in the structure (i.e, array or pointer) was detected.
- ACTION
Check the actual and formal parameters as well as the external declaration of the procedure.
- 203
- MESSAGE
Parameter check error - mismatched packing in argument number !. Procedure = !, Files = !. (LDRERR 203)
- CAUSE
The referenced procedure was found; however, a difference in the packing between the formal and actual parameters was detected.
- ACTION
Check the formal and actual parameters.
- 204
- MESSAGE
Parameter check error - mismatched alignment in argument number !. Procedure = !, Files = !. (LDRERR 204)
- CAUSE
The referenced procedure was found; however, a difference in the alignment between a formal and actual parameter was detected.
- ACTION
Check the formal and actual parameters.
- 205
- MESSAGE
Parameter check error - mismatched argument count. Procedure = !, Files = !. (LDRERR 205)
- CAUSE
The referenced procedure was found; however, a difference in the number of parameters between the formal and actual parameters was detected.
- ACTION
Check the formal and actual parameters.
- 206
- MESSAGE
Symbol backward linkage was detected in program/library. (LDRERR 206)
- CAUSE
A corrupted program/library was found. A backward link in the sysmbol unit was detected.
- ACTION
Try rebuilding the program/library file. If unsuccessful, call your Hewlett-Packard Representative.
- 207
- MESSAGE
Unable to find locality; specified address is not contained in the SOM. (LDRERR 207)
- CAUSE
Unable to find a locality which contains the specified address in the specified SOM.
- ACTION
Check the specification of the SOM and the address.
- 208
- MESSAGE
Nonexisting SOM specified. (LDRERR 208)
- CAUSE
The specified SOM was not found in the specified program/library.
- ACTION
Check the specification of the SOM and program/library file.
- 209
- MESSAGE
Unable to find the locality; the specified address is not in the SOM directory. (LDRERR 209)
- CAUSE
Unable to find SOM which contains the specified address.
- ACTION
Check the specified program/library and the specified address.
- 210
- MESSAGE
Symbol name ! is too long. (LDRERR 210)
- CAUSE
The specified symbol name is too long.
- ACTION
Reduce the length of the symbol name.
- 211
- MESSAGE
The symbol type of the program entry point is invalid. (LDRERR 211)
- CAUSE
A symbol matching the entry point specified was found but was not a valid entry point type.
- ACTION
Check the entry point name specified.
- 212
- MESSAGE
Access rights are inconsistent with the usage of the subspace. (LDRERR 212)
- CAUSE
The subspace type is inconsistent with its usage.
- ACTION
Try rebuilding the subspace and/or the program/library file.
- 213
- MESSAGE
Invalid symbol type encountered. (LDRERR 213)
- CAUSE
An invalid symbol type was encountered.
- ACTION
Rebuild the corresponding program/library file. Also, check the declaration of the symbol.
- 214
- MESSAGE
The program file is not executable. (LDRERR 214)
- CAUSE
The program file specified is not an executable file.
- ACTION
Check the specification of the program file. Rebuild the program file if necessary.
- 215
- MESSAGE
There is no MPE/iX auxiliary header for the program file. (LDRERR 215)
- CAUSE
There is no MPE/iX auxiliary header in the program file.
- ACTION
Check the specification of the program file. Rebuild the program file if necessary.
- 216
- MESSAGE
Invalid file pointer specified. (LDRERR 216)
- CAUSE
Invalid file pointer was specified.
- ACTION
Check the specification of the file pointer.
- 217
- MESSAGE
The specified file does not contain a valid identifier for the internal file format. (LDRERR 217)
- CAUSE
The internal identification stamp of the file is invalid.
- ACTION
Rebuild the program/library file.
- 218
- MESSAGE
No entry point was found for the program specified. (LDRERR 218)
- CAUSE
Can not find an entry point for the specified program file.
- ACTION
Rebuild the program file.
Loader Errors 300 - 399
- 300
- MESSAGE
Failed to create the object for LOADER globals. (LDRERR 300)
- CAUSE
Failed to create the system object for the LOADER globals.
- ACTION
Try rebooting the system. If this is unsuccessful, call your Hewlett-Packard Representative.
- 301
- MESSAGE
Failed to create the system PLABEL TABLE. (LDRERR 301)
- CAUSE
Unable to create the system PROCEDURE LABEL TABLE.
- ACTION
Reboot. If this is unsuccessful, call your Hewlett-Packard Representative.
- 302
- MESSAGE
Failed to obtain an entry for the system PLABEL TABLE HEADER. (LDRERR 303)
- CAUSE
Unable to allocate the header entry in the system PLABEL TABLE.
- ACTION
Reboot. If this is unsuccessful, call your Hewlett-Packard Representative.
- 303
- MESSAGE
Failed to INIT the semaphore lock for the system PLABEL TABLE. (LDRERR 303)
- CAUSE
Failed to intitialize the semaphore for the system PROCEDURE LABEL TABLE.
- ACTION
Reboot. If this is unsuccessful, call your Hewlett-Packard Representative.
- 304
- MESSAGE
The system XRT entry is off boundary. (LDRERR 304)
- CAUSE
The specified address of the system XRT entry is out of bounds.
- ACTION
Check the address specified.
- 305
- MESSAGE
PLABEL unloaded! Unable to release entry from system PLABEL TABLE.
- CAUSE
An attempt to release an entry from the system PLABEL TABLE failed.
- ACTION
Call your Hewlett-Packard Representative.
- 350
- MESSAGE
Failed to allocate an entry from the loaded file table. (LDRERR 350)
- CAUSE
Unable to allocate an entry in the loaded file table.
- ACTION
Retry. If this is unsuccessful, call your Hewlett-Packard Representative.
- 351
- MESSAGE
Failed to INIT the semaphore lock for the loading file. (LDRERR 351)
- CAUSE
Failed to initialze the semaphore for the file entry in the loaded file table.
- ACTION
Retry. If this is unsuccessful, call your Hewlett-Packard Representative.
- 352
- MESSAGE
The max number of SOMS in NL.PUB.SYS is inconsistent with that of the PME descriptor. (LDRERR 352)
- CAUSE
The number of SOMs in the boot image does not match the number of SOMs in the system library.
- ACTION
Update. If this is unsuccessful, call your Hewlett-Packard Representative.
- 353
- MESSAGE
FLABELINFO failed to find NL.PUB.SYS. (LDRERR 353)
- CAUSE
The system library was not found.
- ACTION
Update. If this is unsuccessful, call your Hewlett-Packard Representative.
- 355
- MESSAGE
NL.PUB has an invalid file code. (LDRERR 355)
- CAUSE
The file code of the system library is invalid.
- ACTION
Update. If this is unsuccessful, call your Hewlett-Packard Representative.
- 356
- MESSAGE
Failed to allocate an entry for NL.PUB.SYS from the loaded file table. (LDRERR 356)
- CAUSE
Unable to allocate an entry in the loaded file table for the system library.
- ACTION
Reboot. If this is unsuccessful, call your Hewlett-Packard Representative.
- 357
- MESSAGE
Failed to INIT the semaphore lock for NL.PUB.SYS. (LDRERR 357)
- CAUSE
Failed to initialize the semaphore for the system libraries loaded file table entry.
- ACTION
Reboot. If this is unsuccessful, call your Hewlett-Packard Representative.
- 358
- MESSAGE
Failed to retrieve an existing entry from the loaded file table. (LDRERR 358)
- CAUSE
Failed to retrieve existing entry from the loaded file table.
- ACTION
Try running the program again. If this is unsuccessful, call your Hewlett-Packard Representative.
- 359
- MESSAGE
Failed to create the object for the loaded file table. (LDRERR 359)
- CAUSE
Unable to create the object for the loaded file table.
- ACTION
Reboot. If this is unsuccessful, call your Hewlett-Packard Representative.
- 360
- MESSAGE
Failed to create the table for loaded file table. (LDRERR 360)
- CAUSE
Unable to create the table for the loaded file table.
- ACTION
Reboot. If this is unsuccessful, call your Hewlett-Packard Representative.
Loader Errors 400 - 499
- 400
- MESSAGE
No more process XRT entries available. (LDRERR 400)
- CAUSE
The process XRT is full.
- ACTION
Call your Hewlett-Packard Representative.
- 401
- MESSAGE
No more system XRT entries available. (LDRERR 401)
- CAUSE
The system XRT is full.
- ACTION
Call your Hewlett-Packard Representative.
- 402
- MESSAGE
No external call exists for the given EXEC and XLEAST levels. (LDRERR 402)
- CAUSE
The combination of call and execute privilege levels specified is not supported.
- ACTION
Change the call and execute levels to a supported combination.
- 403
- MESSAGE
Failed to create an object for the process XRT TABLE. (LDRERR 403)
- CAUSE
Unable to create the XRT for the new process.
- ACTION
Retry. If this is unsuccessful, call your Hewlett-Packard Representative.
- 404
- MESSAGE
EXEC level of the code exceeds the maximum privilege level allowed in the file. (LDRERR 404)
- CAUSE
The execution privilege level of the code is greater than what is allowed in the file.
- ACTION
Change the execution level of the code to a valid value.
- 405
- MESSAGE
PM capability is required for memory resident linking in loader. (LDRERR 405)
- CAUSE
PM capability is required to load memory resident code.
- ACTION
Evaluate the code needs to be memory resident or not. If so, assign PM capability to the program and the group where the program resides.
- 406
- MESSAGE
No SOM auxiliary header exists for the given SOM. (LDRERR 406)
- CAUSE
An auxiliary header was not found for the specified SOM.
- ACTION
Rebuild the program or library file.
- 407
- MESSAGE
Failed to FREEZE XRT entries in memory. (LDRERR 407)
- CAUSE
Failed to FREEZE XRT entries corresponding to a memory resident procedure.
- ACTION
Retry. If this is unsuccessful, call your Hewlett-Packard Representative.
- 408
- MESSAGE
Failed to FREEZE LP in memory. (LDRERR 408)
- CAUSE
Failed to FREEZE the LINKAGE POINTER (LP) corresponding to a memory resident procedure.
- ACTION
Retry. If this is unsuccessful, call your Hewlett-Packard Representative.
- 409
- MESSAGE
The exported symbol's symbol type is incorrect. (LDRERR 409)
- CAUSE
An incorrect type of exported symbol was encountered.
- ACTION
Rebuild the program or library file.
- 410
- MESSAGE
The import symbol's symbol type is incorrect. (LDRERR 410)
- CAUSE
An incorrect type of imported symbol was encountered.
- ACTION
Rebuild the program or library file.
- 411
- MESSAGE
The XRT offset in the symbol INFO is incorrect. (LDRERR 411)
- CAUSE
Invalid XRT offset encountered in a symbol entry.
- ACTION
Rebuild the program or library file.
- 450
- MESSAGE
Failed to create an object to store the SOM's LP. (LDRERR 450)
- CAUSE
Unable to create a process global data object.
- ACTION
Retry. If unsuccessful, call your Hewlett-Packard Representative.
- 451
- MESSAGE
Invalid LOADER fixup reference type encountered. (LDRERR 451)
- CAUSE
Invalid type of loader fixup request was encountered.
- ACTION
Rebuild the program library file.
- 452
- MESSAGE
Invalid LOADER fixup space type encountered. (LDRERR 452)
- CAUSE
Invalid loader fixup request encountered in the file.''
- ACTION
Rebuild the program or library file.
- 453
- MESSAGE
Invalid LOADER fixup record encountered. (LDRERR 453)
- CAUSE
Address of loader fixup request is invalid.
- ACTION
Rebuild the program or library file.
- 454
- MESSAGE
Loader can not load page with gateway access type. (LDRERR 454)
- CAUSE
A page with gateway access type was encountered.
- ACTION
Rebuild the program or library file without the page with gateway access type.
- 457
- MESSAGE
Failed to FREEZE code in memory. (LDRERR 457)
- CAUSE
Failed to FREEZE memory resident code in memory.
- ACTION
Retry. If this is unsuccessful, call your Hewlett-Packard Representative.
- 458
- MESSAGE
PM capability is required to FREEZE code in memory. (LDRERR 458)
- CAUSE
The program or group data does not have PM capability which is required to load memory resident code.
- ACTION
Obtain the correct capabilities to run the program.
- 459
- MESSAGE
Failed to CREATE an object for global data. (LDRERR 459)
- CAUSE
Failed to CREATE an object for the precise global data.
- ACTION
Retry. If this is unsuccessful, call your Hewlett-Packard Representative.
- 460
- MESSAGE
LOADER does not load READ ONLY data. (LDRERR 460)
- CAUSE
Invalid access rights of READ ONLY data encountered when loading process global data.
- ACTION
Rebuild the program or library file with the correct access rights.
- 461
- MESSAGE
A data alignment error occurred. (LDRERR 461)
- CAUSE
The data is not aligned at the page boundary.
- ACTION
Retry. If this is unsuccessful, call your Hewlett-Packard Representative.
- 462
- MESSAGE
Failed to FREEZE data in memory. (LDRERR 462)
- CAUSE
Failed to FREEZE memory resident process global data into memory.
- ACTION
Retry. If this is unsuccessful, call your Hewlett-Packard Representative.
- 463
- MESSAGE
PM capability is required to FREEZE data in memory. (LDRERR 463)
- CAUSE
PRIVILEGE MODE capability is required to load memory resident data.
- ACTION
Obtain the proper capabilities.
- 464
- MESSAGE
Failed to alter access rights for data. (LDRERR 464)
- CAUSE
Failed to load process global data for a single SOM with multiple access rights.
- ACTION
Retry. If this is unsuccessful, call your Hewlett-Packard Representative.
- 465
- MESSAGE
PREFETCH failed on source data. (LDRERR 465)
- CAUSE
Failed to PREFETCH the source address into memory.
- ACTION
Retry. If this is unsuccessful, call your Hewlett-Packard Representative.
- 466
- MESSAGE
PREFETCH failed on destination data. (LDRERR 466)
- CAUSE
Failed to PREFETCH the destination address into memory.
- ACTION
Retry. If this is unsuccessful, call your Hewlett-Packard Representative.
- 467
- MESSAGE
Failed to load library !. (LDRERR 467)
- CAUSE
Failed to load the specified NATIVE MODE library.
- ACTION
Run the program from the CI to obtain a more detailed message as to the cause of the library not being loaded.
- 468
- MESSAGE
EXEC level of entry point exceeds the maximum privilege level of the program. (LDRERR 468)
- CAUSE
The program requires more capability than it is allowed.
- ACTION
Relink the program with the proper capabilities.
- 469
- MESSAGE
Failed to load program !. (LDRERR 469)
- CAUSE
Failed to load the specified program.
- ACTION
Run the program from the CI to obtain a more detailed message.
- 470
- MESSAGE
A call to VSM LOAD CODE file returned an error. (LDRERR 470)
- CAUSE
Failed to set up the appropriate code access rights for the file.
- ACTION
Retry. If this is unsuccessful, call your Hewlett-Packard Representative.
- 471
- MESSAGE
Failed to CREATE a system domain. (LDRERR 471)
- CAUSE
Failed to CREATE a domain when trying to load a system SOM.
- ACTION
Retry. If this is unsuccessful, call your Hewlett-Packard Representative.
- 472
- MESSAGE
The number of XRT stated in the SOM AUX header is inconsistent with the number of imports in the SOM. (LDRERR 472)
- CAUSE
Inconsistency between the number of XRTs specified in the SOM and the number of procedures referenced.
- ACTION
Rebuild the program or library file and retry.
Loader Errors 500 - 599
- 500
- MESSAGE
CM LOADER failed. (LDRERR 500)
- CAUSE
An error occurred while loading the COMPATIBILITY MODE program.
- ACTION
Run the program from the CI for a more detailed message.
- 501
- MESSAGE
The program name is too long. (LDRERR 501)
- CAUSE
The program name specified is too long.
- ACTION
Correct the program name.
- 502
- MESSAGE
The entry name is too long. (LDRERR 502)
- CAUSE
The name of the entry point specified is too long.
- ACTION
Retry with a valid entry point name.
- 503
- MESSAGE
Bad condition code was returned from CM LOADER. (LDRERR 503)
- CAUSE
An invalid status was returned from the COMPATIBILITY MODE loader.
- ACTION
Retry. If this is unsuccessful, call your Hewlett-Packard Representative.
- 504
- MESSAGE
A subsystem library binding error occurred (XL.PUB.SYS not followed by NL.PUB.SYS). (LDERR 504)
- CAUSE
XL.PUB.SYS is not followed by NL.PUB.SYS in the specified library list.
- ACTION
Retry with a valid library list specification.
- 505
- MESSAGE
Program requires more capabilities than group is allowed. (LDRERR 505)
- CAUSE
The group where the program resides has insufficient capabilities.
- ACTION
Obtain the correct capabilities.
- 506
- MESSAGE
XLLIST parm exceeds maximum length of 512 characters. (LDRERR 506)
- CAUSE
The length of the library list specification is too long.
- ACTION
Retry with a valid library list specification.
- 507
- MESSAGE
Invalid LIB parameter specified. (LDRERR 507)
- CAUSE
The value specified in the LIB parameter is invalid.
- ACTION
Correct the LIB specification.
- 508
- MESSAGE
A system library binding error occurred (NL.PUB.SYS must be the last library in XLLIST). (LDERR 508)
- CAUSE
The library NL.PUB.SYS is not the last library in the library list.
- ACTION
Correct the library specification.
- 509
- MESSAGE
ALLOCATE program is not supported for NM programs. (LDRERR 509)
- CAUSE
The ALLOCATE program is not valid for native mode programs.
- ACTION
Do not retry.
- 510
- MESSAGE
File contains an invalid file code for a program. (LDRERR 510)
- CAUSE
An invalid file code is associated with the file specified as the program.
- ACTION
Rebuild the program file.
- 511
- MESSAGE
NM library name is too long. (LDRERR 511)
- CAUSE
A library name that is too long was encountered in the library specification.
- ACTION
Correct the library specification.
- 512
- MESSAGE
Unresolved externals: ! (LDRERR 512)
- CAUSE
Unresolved external symbols were encountered while attempting to load the program and/or libraries.
- ACTION
See the following error message which will explain whether the unresolved externals are code or data symbols. Alter the binding sequence to contain the specified unresolved code (procedure) or data symbols.
- 513
- MESSAGE
System SOM is not allowed to bind to non-system SOM. (LDRERR 513)
- CAUSE
External references of system SOMs must resolve to a system SOM.
- ACTION
Retry. If this is unsuccessful, call your Hewlett-Packard Representative.
- 514
- MESSAGE
An empty file error occurred. (LDRERR 514)
- CAUSE
The program or library file specified has an EOF of zero.
- ACTION
Rebuild the program or library file.
- 515
- MESSAGE
Program does not contain interactive (IA) capability. (LDRERR 515)
- CAUSE
The program does not contain IA capability and is being attempted to be executed interactively.
- ACTION
Request the system manager to grant you IA capability and then rerun the program.
- 516
- MESSAGE
Program does not contain batch (BA) capability. (LDRERR 516)
- CAUSE
The program does not have enough capability to execute in a job.
- ACTION
Obtain the proper capability or only run the program interactively.
- 517
- MESSAGE
Program file was not found. (LDRERR 517)
- CAUSE
The program specified was not found.
- ACTION
Retry with a valid program file.
- 518
- MESSAGE
Unable to obtain user access rights to the program file from the file system.
- CAUSE
Unable to obtain access rights for the specified program file.
- ACTION
Check the files specified.
- 520
- MESSAGE
"LIB=" is an invalid option for HFS programs. (FDERR 520)
- CAUSE
"LIB=" is an invalid option for HFS programs.
- ACTION
Do not specify the option.
- 521
- MESSAGE
CM programs cannot be loaded from HFS. (LDERR 521)
- CAUSE
CM programs are not supported in HFS.
- ACTION
Move the CM program to an MPE group.
- 522
- MESSAGE
Failed to locate the exported code symbol(s) for the imported code symbol(s) listed above. (LDRERR 522)
- CAUSE
Unresolved code symbols were encountered while attempting to load the program and/or libraries.
- ACTION
Alter the binding sequence to contain the specified unresolved code symbols (procedures).
Loader Errors 600 - 699
- 600
- MESSAGE
There is a duplicate file in the library list. (LDRERR 600)
- CAUSE
The same file appeared twice in the binding sequence for the process.
- ACTION
Correct the binding sequence and retry.
- 601
- MESSAGE
Failed to get an entry from the PROCESS FILE LIST. (LDRERR 601)
- CAUSE
Unable to allocate an entry in the process file list.
- ACTION
Retry. If this is unsuccessful, call your Hewlett-Packard Representative.
- 602
- MESSAGE
-
File = !
The file being loaded is less privileged than the previous file in the binding sequence. (LDRERR 602) - CAUSE
The file specified has less capability than the preceding file in the binding sequence.
- ACTION
Obtain the correct capability for the specified file.
- 603
- MESSAGE
Failed to CREATE the PROCESS FILE LIST TABLE. (LDRERR 603)
- CAUSE
Failed to CREATE the process file list.
- ACTION
Retry. If this is unsuccessful, call your Hewlett-Packard Representative.
- 604
- MESSAGE
LOADER internal error; invalid LOADER reference count. (LDRERR 604)
- CAUSE
Internal error. Attempt to decrement the reference count when it is already zero.
- ACTION
Call your Hewlett-Packard Representative.
- 605
- MESSAGE
LOADER internal error; invalid file reference count. (LDRERR 605)
- CAUSE
Internal error. Attempt to decrement the count for the number of SOMs loaded in a file when the count is already zero.
- ACTION
Call your Hewlett-Packard Representative.
- 607
- MESSAGE
LOADER internal error; tried to CLOSE an in use file. (LDRERR 607)
- CAUSE
Internal error. Attempted to CLOSE a file which is still in use.
- ACTION
Call your Hewlett-Packard Representative.
- 608
- MESSAGE
Failed to RELEASE a process file extension record. (LDRERR 608)
- CAUSE
An error occurred while releasing a process file list extension record.
- ACTION
Retry. If this is unsuccessful, call your Hewlett-Packard Representative.
- 609
- MESSAGE
Failed to LOCK a loaded file entry. (LDRERR 609)
- CAUSE
Unable to LOCK the loaded file table entry for the file being closed.
- ACTION
Call your Hewlett-Packard Representative.
- 610
- MESSAGE
Failed to delete a loaded file entry. (LDRERR 610)
- CAUSE
An error occurred while releasing a loaded file table entry.
- ACTION
Call your Hewlett-Packard Representative.
- 611
- MESSAGE
The specified SOM is being used by LOADER. (LDRERR 611)
- CAUSE
Unable to lock the SOM for the linker because it is in use by the loader.
- ACTION
Retry later.
- 612
- MESSAGE
The specified file is not in LOADER's LOADED FILE TABLE. (LDRERR 612)
- CAUSE
The file requested by the linker to unlock a SOM is not loaded.
- ACTION
Retry. If this is unsuccessful, call your Hewlett-Packard Representative.
- 613
- MESSAGE
The file was not mapped to offset 0 (user labels not allowed in programs). (LDRERR 613)
- CAUSE
User labels were found in the program file.
- ACTION
Rebuild the file.
- 614
- MESSAGE
The max SOM limit in the file exceeds the maximum of 5000 allowed by LOADER. (LDRERR 614)
- CAUSE
The library file specified has too large of the maximum number of SOMs.
- ACTION
Rebuild the file with fewer SOMs.
- 616
- MESSAGE
Failed to get an entry for a process file extension record. (LDRERR 616)
- CAUSE
Failed to allocate an entry for the process file list extension.
- ACTION
Retry. If this is unsuccessful, call your Hewlett-Packard Representative.
- 617
- MESSAGE
LOADER internal error; past end of binding sequence. (LDRERR 617)
- CAUSE
Internal error. Attempt to read past the end of the process file list.
- ACTION
Retry. If this is unsuccessful, call your Hewlett-Packard Representative.
- 618
- MESSAGE
Failed to release the PROCESS FILE LIST TABLE. (LDRERR 618)
- CAUSE
An error occurred while releasing the PROCESS FILE LIST TABLE.
- ACTION
Retry. If this is unsuccessful, call your Hewlett-Packard Representative.
- 650
- MESSAGE
NM UNLOADER failed. (LDRERR 650)
- CAUSE
An error occurred while unloading the process.
- ACTION
Retry. If this is unsuccessful, call your Hewlett-Packard Representative.
- 651
- MESSAGE
CM UNLOADER returned an error. (LDRERR 651)
- CAUSE
An error occurred while unloading the COMPATIBILITY MODE process.
- ACTION
Retry. If this is unsuccessful, call your Hewlett-Packard Representative.
- 670
- MESSAGE
Failed to get an entry from the UNSAT TABLE. (LDRERR 670)
- CAUSE
An error occurred while attempting to allocate an entry in the unsatisfied table.
- ACTION
Retry. If this is unsuccessful, call your Hewlett-Packard Representative.
- 671
- MESSAGE
Invalid import symbol type encountered. (LDRERR 671)
- CAUSE
The type of the import entry is invalid.
- ACTION
Rebuild the program or library file.
- 672
- MESSAGE
Invalid import symbol scope encountered. (LDRERR 672)
- CAUSE
The scope of the import symbol is invalid.
- ACTION
Rebuild the program or library file.
- 673
- MESSAGE
Unable to find the UNSAT procedure. (LDRERR 673)
- CAUSE
The procedure specified with the UNSAT parm can not be found.
- ACTION
Check to make sure the procedure specified is valid.
- 674
- MESSAGE
Unresolved dynamic loading procedure. (LDRERR 674)
- CAUSE
The procedure requested to be dynamically loaded is unresolved and can not be bound to the UNSAT procedure.
- ACTION
Check to make sure the procedure which was requested to be dynamically loaded is valid.
- 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.
Loader Errors 700 - 799
- 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.
Loader Errors 800 - 899
- 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.
|
LOADER |
Chapter 2 Native Mode Spooler (Subsystem 236) |