$HASP875

module –

Explanation

>>-module – --reason,--RC=--rsnc-------------------------------><

 Either the $MODLOAD routine detected an error
during the loading of the specified module or the $MODCHK routine
detected an error during verification. The variable text and reason
code indicate the exact reason for the error. These are explained
under the programmer response section.
 In the message text:
 module
The name of the module.
reason
Explains the reason for the error.
rsnc
The reason code accompanying reason.

 Note: This message is issued only if MESSAGE=YES
is specified on the $MODLOAD or $MODCHK macros.

Explanation

>>-INSUFFICIENT STORAGE FOR LOAD--MODULE TABLE ENTRY, RC=01----><

 An attempt was made to allocate a load module
table entry for the displayed load module, but no storage was available.
There is no logical limit on the number of entries, except the amount
of available storage.

Explanation
 An attempt to load the module failed. The module
is probably not in the correct library (STEPLIB, LINKLIST, or LPA).

Explanation
 Because the module is not reentrant, it could
not be loaded into the common storage area (CSA).

Explanation
 On this JES2 hot start, an attempt was made to
either load a module into CSA or to load a module that was in LPA.
New common storage modules cannot be loaded on a hot start because
the existing modules may be in use for common storage exits and the
exit routines cannot be changed.

Explanation
 A request was made to load a module into CSA,
but no CSA storage was available.

Explanation
 The module being loaded is marked as RMODE 31
and resides above 16 megabytes in virtual storage. All JES2 code must
be marked RMODE 24.

Explanation
 During module verification, a JES2-format module
was checked to ensure its load module name matched the name in the
module information table (MIT). The check failed.
 Note: No JES2
uses of $MODCHK specify that this type of check should be done at
this time; the programmer specified this verification.

Explanation
 The version number in the module information table
(MIT) for this module does not match the version of the JES2 release
that is running.

Explanation
 The module was assembled with a set of MVS™ macro libraries different from the set used to assemble
the JES2 system that is running (for example MVS/ESA rather than z/OS).

Explanation
 The $MODCHK routine determined that this module
is not in common storage. This error should not occur with the modules
that JES2 loads because it forces these modules into CSA if they are
not in LPA.

Explanation
 The module information table (MIT) for the module
is not valid for one or more of the following reasons:  The module is not long enough to contain a module information
table.
The module does not begin with CL4‘MIT’.
The MITETBL pointer to the MIT entry table, which is generated
at the end of the module, points to an address outside the range of
the module.

Explanation
 No verification checks were done by $MODCHK because
the address operand was not coded on the $MODCHK macro and the entry
point was not found in the load module table ($LMT).
 Note: This
is probably because JES2 or an installation exit called $MODCHK before
a successful $MODLOAD was performed.

Explanation
 The module user version character string for this
module in the module information table (as defined by &UVERS in
$HASPGBL), does not match the version of the JES2 release that is
running.

Explanation
 The user version character string for this module
in the module information table (MIT) does not match the IBM-defined
value.

Explanation
 An IBM® module was loaded into common
storage during JES2 initialization saving the service routine's entry
point address information. At least one entry point was defined (through
the $ENTRY macro) to have its address placed at an invalid offset
within the CADDR control block.

Explanation
 An IBM module was loaded into common
storage during JES2 initialization saving the service routine's entry
point address information. At least one entry point was defined (through
the $ENTRY macro) to have its address placed at an invalid offset
within the CADDR control block where another entry point address has
already been placed.

System action
 The system action depends on the module displayed
and the specific circumstances:  If the JES2 initialization module (HASPINIT) or one of its subsystem
support modules had an error, JES2 initialization processing stops.
If an MVS module that JES2 may load (for example, IEE7603D)
had an error, JES2 asks the operator whether JES2 initialization should
end.
If the error occurred while processing a LOADMOD initialization
statement, $SCAN begins requesting input from the operator console
instead of the normal parmlib input. This allows the operator to correct
the error, if necessary.  For this type of error, the message
displayed is actually $HASP003 with one of the variable texts listed
below.

If the exit incurred an error ($MODLOAD or $MODCHK was called
from an installation exit), the system action depends on the caller
of the service.

Operator response
 Notify the system programmer.

System programmer response
 The response depends on the type
of error that occurred. See the values of reason and rsnc and their explanations below:
 INSUFFICIENT STORAGE FOR LOAD MODULE TABLE ENTRY, RC=01

System programmer response
 Resolve the lack of storage. You
may accomplish this by reducing the number of LOADMOD initialization
statements or by increasing the common storage area (CSA) for the
system.
 MODULE COULD NOT BE LOADED, RC=02

System programmer response
 Place the module in the appropriate
library from which JES2 can successfully load it.
 MODULE IS NOT REENTRANT, RC=03

System programmer response
 Ensure that the code in the module
is reentrant. Use the linkage editor to mark it reentrant for JES2
load processing.
 NEW CSA/LPA LOADMODS INVALID ON
HOT START, RC=04

System programmer response
 If it is necessary to load new common
storage modules or replace existing ones, perform a warm start of
JES2.
 INSUFFICIENT STORAGE TO LOAD MODULE, RC=05

System programmer response
 Resolve the lack of storage by either
increasing the CSA for the system or by freeing other CSA uses.
 MODULE IS INVALID, RMODE MUST BE 24, RC=06

System programmer response
 Regenerate the module with RMODE
24.
 MODULE NAME DOES NOT MATCH ITS
MIT,EXPECTED-mit_exp ACTUAL-mit_act, RC=07

System programmer response
 Rename the load module to match the
name in the MIT.
 MODULE VERSION IS
INVALID, EXPECTED-ver_exp ACTUAL-ver_act, RC=08

System programmer response
 Reassemble the module at the same
version level as the JES2 release currently running.
 MODULE ASSEMBLED WITH INVALID MACRO LIBRARIES, EXPECTED-lib_exp
ACTUAL-lib_act, RC=09

System programmer response
 Reassemble the module with the correct
macro library level.
 MODULE IS NOT IN COMMON STORAGE,
RC=10

System programmer response
 Either place the module in LPA, or
change your exit $MODLOAD calls to request that the module be placed
in CSA.
 MODULE MIT IS INVALID, CANNOT
LOCATE LMT, RC=11
 MODULE
MIT IS INVALID, MODULE TOO SMALL, RC=11
 MODULE MIT IS INVALID, INCORRECT MITETBL
ADDRESS, RC=11
 MODULE
MIT IS INVALID, INCORRECT EYECATCHER, EXPECTED-mit ACTUAL-mit, RC=11

System programmer response
 Reassemble the module with the correct
JES2 module structure, using a $MODULE macro to start the module (and
generate the MIT), and a $MODEND macro to end the module (and generate
the MITETBL).
 MODULE NOT FOUND – MODULE CANNOT
BE VERIFIED, RC=12

System programmer response
 Either code the ADDR= parameter for
load modules when calling $MODCHK or ensure the JES2 load module was
loaded successfully by $MODLOAD.
 MODULE USER VERSION IS INVALID EXPECTED-uver_exp ACTUAL-uver_act,
RC=15

System programmer response
 Reassemble the module at the same
version level as the JES2 release currently running.
 MODULE IBM USER VERSION IS
INVALID, RC=16

System programmer response
 Ensure that the object deck is at
the correct maintenance level. If the object deck is at the correct
maintenance level and the error persists, contact your IBM support
representative.
 MODULE $ENTRY ADDRESS TABLE OFFSET(S)
NOT VALID, RC=17

System programmer response
 Ensure that the module being loaded
to common storage matches the version of JES2 code currently performing
JES2 initialization.
 MODULE CONTAINS DUPLICATE
ADDRESS TABLE $ENTRY, RC=18

System programmer response
 Ensure that the module being loaded
to common storage matches the version of JES2 code currently performing
JES2 initialization.

Module
 HASPCSV, HASPIRSI
 Routing Code: 1,2,10
 Descriptor Code: 4