BPE0001E BPE INITIALIZATION ERROR IN MODULE module
details
Explanation
An error occurred in early BPE initialization. This message contains two-lines. Each line begins with the message number.
In the message text:
- module
- The module that detected the error
- details
- A one-line explanation of the type of error that was detected
The details line of this
message further explains the error detected, and can be one of the
following:
- ERROR LOADING MODULE module BPELOAD RC=rc
- Load failed for a module. In the message text:
- module
- The name of a module that could not be loaded
- rc
- The return code from the BPE load service, BPELOAD
- ERROR LOADING MODULES module... BPELOAD RC=rc
- Load failed for several modules. In the message text:
- module
- The name of the first of several modules that could not be loaded
- rc
- The return code from the BPE load service, BPELOAD
- ERROR PARSING datasettype, BPEPARSE RC=rc
- An error was detected while trying to parse a configuration data
set. This message follows message BPE0003E, which provides further
details on the error. In the message text:
- data_set_type
- A description of the type of data set that was being parsed. This
can be one of the following:
- BPE CONFIG MEMBER: The main BPE configuration PROCLIB member that is specified on the BPECFG parameter of the startup JCL or procedure.
- component USER EXIT LIST MEMBER: The user exit list PROCLIB member for the indicated IMS component (for example, BPE, CQS, OM, RM, or SCI). This is the user exit list member that is specified on the EXITMBR statement in the BPE configuration PROCLIB member.
- rc
- The return code from the BPE parsing service, BPEPARSE.
- ERROR READING PROCLIB DATA SET, BPERDPDS RC=rc
- BPE could not read a PROCLIB DD data set. This message follows
message BPE0002E, which provides further details on the specific data
set and member that could not be read. In the message text:
- rc
- The return code from the BPE partitioned data set reading service, BPERDPDS
- INITIALIZATION FAILED FOR service, RC=rc
- BPE was unable to initialize a BPE system service. In the message
text:
- service
- The name of the BPE service that failed initialization. Values
for this field include:
- BPE RESMGR: An error occurred when BPE tried to establish a resource manager routine to clean up global resources that are used by BPE. The return code in this message is the return code from the MVS™ RESMGR macro call that failed.
- USER EXITS: An error occurred while trying to load user exit modules. This message might be preceded by other error messages that indicate the problem. The return code from the module that loads the user exits (BPEUXRF0) is in the rc field in this message.
- BPE SVC: An error occurred when BPE tried to initialize
the BPE SVC routine. BPE provides an internal SVC routine for use
by BPE and IMS components. The SVC is installed dynamically
when a BPE address space is started. This error message is issued
when the BPE SVC could not be installed.
If the rc field in the message is X'00000020', you are probably trying to start the address space on a z/OS system that is not at the required maintenance level. The MVS system must be at least at MVS SP 4.3.0 or higher. If the MVS system is at MVS SP 5.2.0 or below, you must have MVS APARs OW13312 and OW13315 applied.
- rc
- The return code from the lower-level initialization module that encountered the error.
- INVALID CALLABLE SERVICE CODE code IN MODULE module
- BPE detected an invalid user exit callable service code in the
indicated module. Both BPE and IMS components
that run with BPE can define callable services that user exits can
use. Each callable service has a callable service code used to request
the service. This error indicates that there is a definition error
in the specified module. In the message text:
- code
- The callable service code in error, in hexadecimal.
- module
- The name of the callable service module that had the invalid callable service code defined.
- MODULE module HAS AN INVALID VERSION NUMBER version
- A BPE definition module had an invalid version number. BPE uses
version numbers as a consistency check to ensure that the definition
modules being loaded match the version of BPE that is running. In
the message text:
- module
- The BPE definition module in which the invalid version was detected
- version
- The hexadecimal invalid version number from the definition module
- MODULE module IS LINKED REENTRANT - IT MUST BE NON-REENTRANT
- A BPE definition module was loaded into key zero storage. BPE
definition modules are modules that contain data (control blocks),
and thus must be loaded into storage that is in the same storage key
in which BPE is running. The most common cause for this error message
is linking a definition module as reentrant, which loads it into key
zero storage. BPE definition modules should be bound as non-reentrant.
In the message text:
- module
- The BPE definition module that was loaded in key zero storage
- MODULE module IS NOT A VALID type DEFINITION MODULE
- BPE encountered an error with an internal BPE definition module.
BPE uses definition modules to construct its execution environment.
If a definition module is not correct, BPE cannot build the appropriate
environment. In the message text:
- module
- The name of a BPE definition module that is in error
- type
- The type of definition module in error
- NAME-TOKEN CREATE ERROR, RC=rc
- A z/OS® name-token service
create call failed. In the message text:
- rc
- The return code from the z/OS name-token create call. For details, see the IEANTCR service return codes in z/OS MVS Programming: Authorized Assembler Services Reference, Volume 2 (EDT-IXG).
- NAME-TOKEN RETRIEVE ERROR, RC=rc
- A z/OS name-token service
retrieve call failed. In the message text:
- rc
- The return code from the z/OS name-token retrieve call. For details, see the IEANTRT service return codes in z/OS MVS Programming: Authorized Assembler Services Reference, Volume 2 (EDT-IXG).
- STORAGE OBTAIN ERROR, STORAGE RC=rc
- A z/OS STORAGE OBTAIN call
to get storage failed. In the message text:
- rc
- The return code from the z/OS STORAGE OBTAIN call. For details, see the STORAGE OBTAIN return codes in z/OS MVS Programming: Authorized Assembler Services Reference, Volume 4 (SET-WTO).
- UNABLE TO CREATE threadtype THREAD, BPETHDCR RC=rc
- A request to create a BPE thread (internal unit of work) failed.
In the message text:
- threadtype
- A 4-character name of the thread type that could not be created
- rc
- The return code from the thread create service, BPETHDCR
- UNABLE TO GET NECESSARY STORAGE, BPEGETM RC=rc
- BPE could not obtain the required storage. In the message text:
- rc
- The return code from the BPE GETMAIN service, BPEGETM
- UNABLE TO GET STORAGE FOR blocktype BLOCK, BPECBGET RC=rc
- BPE could not obtain storage for a required control block. In
the message text:
- blocktype
- A 4-character name of an internal BPE control block that could not be obtained
- rc
- The return code from the BPE control block get service, BPECBGET
- UNKNOWN ERROR, MODULE RC=rc
- An internal error occurred that BPE does not recognize. In the
message text:
- rc
- The return code from the failing module
System action
IMS abend 3400 with subcode 05 follows this message. The address space terminates.
System programmer response
If the error described in this message is caused by environmental conditions (for example, insufficient storage or modules missing from IMS.SDFSRESL), correct the indicated problem and restart the address space. Otherwise, save any memory dump and SYSLOG information, and contact IBM® Software Support.