BBMZEnnn messages

This section lists the recovery manager messages. If an abend occurs for a critical function, the recovery manager performs the following tasks, if applicable:

BBMZE001E
RECOVERY MANAGER ESTAE ENTERED
Explanation:

The system recovery manager ESTAE has been entered due to an abend condition. The failing server function was executing in enabled, unlocked task, and non cross-memory mode.

System action:

The recovery manager creates a SYS1.LOGREC record and continues error processing.

User response:

Look for additional messages containing diagnostic information.

BBMZE002E
ABEND tnnnn-reason PASN=asid, SASN=asid, HASN=asid
Explanation:

This message provides snap dump information about an abend condition that the recovery manager is processing. This message provides the abend code and reason, and the address space information for the failing function.

The abend code is either Snnnn or Unnnn, where:

S
Indicates an MVS™ component issued the abend code.
U
Indicates a process of a user or vendor could not continue so the product or user code invoked its own ABEND macro.
nnnn
Is the abend code value.

The reason value shows the abend reason code, which provides a reason why the address space is failing.

The name of the failing address space is shown as asid.

Note:
This message issues with messages BBMZE003E through BBMZE006E.
System action:

Additional messages are issued by the recovery manager.

User response:

See the additional messages containing further snap dump information that follow this message.

BBMZE003E
ERROR PSW=PSword, IL/CC/IC=il/nn/code, LTA=address
Explanation:

This message provides snap dump information about an abend condition that the recovery manager is processing. This message provides information related to storage when the error occurred.

The program status word (PSW) is the area in storage containing the order in which program instructions were processing when the error occurred. The active PSW area for the program at the time of the error is PSword.

The instruction length of the instruction that failed is il; the completion code, nn, is shown as a decimal value and indicates the code value returned by the PSW; see Completion code values for information about the code value. The interrupt code that was issued for the error is code; and the last address translated by the hardware when the error occurred is address.

Note:
This message issues with messages BBMZE002E and BBMZE004E through BBMZE006E.
System action:

Additional messages are issued by the recovery manager.

User response:

See additional messages containing further snap dump information that precede and follow this message.

BBMZE004E
DATA AT PSW+offset|PSW-offset word1...wordn
Explanation:

This message provides snap dump information about an abend condition that the recovery manager is processing. This message provides information related to the PSW (program status word).

The offset value is the offset relative to the address of the failing PSW, shown as PSword in message BBMZE004E. The offset value is preceded by either a + (plus) or - (minus) in the message to show whether the data appears before or after the offset value.
The data is shown as word1...wordn in this message. Each word is an 8-character hexadecimal value.

Note:
This message issues with messages BBMZE002E, BBMZE003E, BBMZE005E, and BBMZE006E.
System action:

Additional messages are issued by the recovery manager.

User response:

See additional messages containing further snap dump information that precede and follow this message.

BBMZE005E
ERROR|RETRY REGISTERS nn-nn reg1 reg2 reg3 reg4
Explanation:

This message provides snap dump information about an abend condition that the recovery manager is processing. This message lists the error registers at the time of the abend and then shows the retry register values that will be used when the function's retry routine gets control.

The nn-nn values are the starting and ending register numbers and are always:

The reg1 through reg4 values are the 8-digit hexadecimal error registers.

Note:
This message issues with messages BBMZE002E through BBMZE004E and BBMZE006E.
System action:

Additional messages are issued by the recovery manager.

User response:

See additional messages containing further snap dump information that precede and follow this message.

BBMZE006E
LINKAGE TRACE module1...modulen
Explanation:

This message provides information about an abend condition that the recovery manager is processing. A link trace has been written for the modules and/or functions active at the time of the error and this message shows the path of modules and functions that were invoked prior to the abend event.

The first value shown in the message, module1, is the last module or function invoked that caused the abend. The second value shown is the function or module that invoked the module1 function or module. The last module or function listed, equating to modulen in the message, is the very first module or function invoked, which began the link trace path.

Note:
This message issues with messages BBMZE002E through BBMZE005E.
System action:

Recovery processing continues.

User response:

See additional messages containing further snap dump information that precede this message. Contact your IBM® Support Center with any of the information that is available from the list shown in Diagnostic information for BB messages.

BBMZE009E
JOB=jobname, TCB=xxxxxxxx, CSECT=csect( function + offset)
Explanation:

This message identifies the job, TCB, and CSECT that failed.

The ID of the failing CSECT is csect for the function ID of function located at the offset value of offset.

System action:

Additional messages are issued by the recovery manager.

User response:

See the additional messages containing further snap dump information that precede and follow this message.

BBMZE800I
RECOVERY MANAGER ESTAE|FRR DID NOT REQUEST RETRY
Explanation:

A system recovery manager ESTAE or FRR (functional recovery routine) has processed some of the information about the function abend condition and has determined that the error is not recoverable. The failing server function was executing in enabled, unlocked task, and non cross-memory mode.

Note:
Most functions are associated with an ESTAE, but some functions, such as cross-memory or SRB functions, can be associated only with an FRR.
System action:

The recovery manager ESTAE does not request MVS to invoke the function's retry routine and the address space terminates.

User response:

Contact your IBM Support Center with any of the information that is available from the list shown in Diagnostic information for BB messages.

BBMZE801I
RECOVERY MANAGER ESTAE REQUESTED ERROR RECORDING
Explanation:

The recovery manager has requested Recovery/Termination Manager (RTM) to write a software SYS1.LOGREC record to record the error containing extended diagnostic data.

System action:

A SYS1.LOGREC record is written.

User response:

Contact your IBM Support Center with any of the information that is available from the list shown in Diagnostic information for BB messages.

BBMZE802I
RECOVERY MANAGER ESTAE|FRR ’SDUMP’ COMPLETE|INITIATED RC=X’xxxx
Explanation:

A recovery manager ESTAE has just completed an SDUMP, or a recovery manager functional recovery routine (FRR) has just initiated an SDUMP. The return code for either initiating or completing the SDUMP is X'xxxx'.

Note:
Most functions are associated with an ESTAE, but some functions, such as cross-memory or SRB functions, can be associated only with an FRR.
System action:

The SDUMP is scheduled if the status shows INITIATED; the recovery manager continues processing if the status shows COMPLETED.

User response:

If the return code is not 0 (zero), check your SYS1.DUMPnn data set. The dump data set might be full or might be too small. If so, either clear or enlarge the dump data set.

BBMZE803I
RECOVERY MANAGER ESTAE|FRR REQUESTED RETRY
Explanation:

The recovery manager ESTAE or FRR has requested a retry. The system recovery manager ESTAE or FRR has processed some of the information about the function abend condition and has determined that the error is recoverable. The failing server function was executing in enabled, unlocked task, and non cross-memory mode.

Note:
Most functions are associated with an ESTAE, but some functions, such as cross-memory or SRB functions, can be associated only with an FRR.
System action:

The recovery manager ESTAE or FRR requests MVS to invoke the function's retry routine.

User response:

None.

BBMZE804I
RECOVERY MANAGER ESTAE|FRR 'SDUMP' WAS SUPPRESSED BY DAE|SLIP TRAP OPTION|INSTALLATION REQUEST
Explanation:

A recovery manager ESTAE or FRR (functional recovery routine) SDUMP was not taken for one of the following reasons:

DAE
The error conditions matched those for a previous dump, so Dump Analysis and Elimination (DAE) suppressed the dump request.
SLIP TRAP OPTION
The error condition matched an existing Serviceability Level Indication Processing (SLIP) trap, which specified DUMP=NO.
INSTALLATION REQUEST
Either the MVS system was IPLed with DUMP=NO specified in SYS1.PARMLIB member IEASYSxx, or an operator issued the CHNGDUMP SET,NODUMP command during system operation.
System action:

The system continues processing, but other error conditions can occur.

User response:

Contact your IBM Support Center with the text of this and any related messages.

BBMZE805I
RECOVERY MANAGER ESTAE|FRR IS SCHEDULING AN 'SDUMP' - PLEASE WAIT
Explanation:

This informational message is issued both to the console and to the terminal. The recovery manager ESTAE or FRR (functional recovery routine) has processed some of the information about an error condition and has determined that a dump is required.

Note:
Most functions are associated with an ESTAE, but some functions, such as cross-memory or SRB functions, can be associated only with an FRR.
System action:

The SDUMP is scheduled.

User response:

When this message is issued to the terminal, there is a delay before the keyboard is unlocked. Because the message appears on the display at the point where the dump is scheduled, the dump must be processed before control can be returned to the keyboard. Once the dump has been processed, three asterisks (***) appear on the display. Press Enter to continue.

No action is required when this message is issued to the console.

BBMZE880U
RECOVERY MANAGER ESTAE FAILED (Reason Text)
Explanation:

The system recovery manager has been entered due to a server function abend condition. The failing server function was executing in enabled, unlocked task, and non cross-memory mode. The recovery manager ESTAE has failed for one of the following reasons:

RECURSIVE ERROR
A second abend occurred while the recovery manager was attempting recovery for an existing abend condition. Recovery is not attempted again.

System Action: The recovery routine for the task terminates.

User Response: Contact your IBM Support Center with any of the information that is available from the list shown in Diagnostic information for BB messages.

NO SDWA
The MVS Recovery/Termination Manager (RTM) did not provide a System Diagnostic Work Area (SDWA). Recovery is not attempted.

System Action: The recovery routine for the task terminates.

User Response: Increase the address space's region size to prevent this situation from occurring in the future. Contact your IBM Support Center with any of the information that is available from the list shown in Diagnostic information for BB messages.

NO CECA
The recovery manager was unable to locate the active server environment block (CECA). Recovery is not attempted.

System Action: The recovery routine for the task terminates.

User Response: Contact your IBM Support Center with any of the information that is available from the list shown in Diagnostic information for BB messages.

NO RMWA STORAGE
The recovery manager was unable to allocate storage for the Recovery Manager Work Area (RMWA) The RMWA is necessary to analyze and recover the abend condition. Recovery is not attempted.

System Action: The recovery routine for the task terminates.

User Response: Increase the address space's region size to prevent this situation from occurring in the future. Contact your IBM Support Center with any of the information that is available from the list shown in Diagnostic information for BB messages.

LOCAL ESTAE ERROR FOR routine
The recovery manager was unable to establish the local ESTAE recovery routine named routine. This routine is necessary to analyze and recover the abend condition. Recovery is not attempted.

System Action: The recovery routine for the task terminates.

User Response: Contact your IBM Support Center with any of the information that is available from the list shown in Diagnostic information for BB messages.

BBMZE881E
RECOVERY MANAGER ESTAE|FRR ’SDUMP’ FAILED - RC=X’xxxx’ / REASON=X’code
Explanation:

A recovery manager ESTAE or functional recovery routine (FRR) SDUMP has failed due to the return code, X'xxxx', and reason code, X'code', shown in the message.

Note:
Most functions are associated with an ESTAE, but some functions, such as cross-memory or SRB functions, can be associated only with an FRR.
System action:

Recovery continues but no SDUMP is available.

User response:

Check the appropriate MVS manual about SDUMP processing to determine the reason for the SDUMP failure. Contact your IBM Support Center with any of the information that is available from the list shown in Diagnostic information for BB messages.

BBMZE982E
TASK TERMINATION RESOURCE RECOVERY FAILED (Reason Text)
Explanation:

The task resource recovery subsystem service routine was entered to recover local resources owned by a terminating service task. The recovery manager ESTAE has failed for one of the following reasons:

INSUFFICIENT STORAGE
The recovery manager was unable to obtain the necessary working storage to process the release of the local resources for the terminating task. The amount of storage available in the address space is critically low.

System Action: Task termination continues, but some local resources may not be released.

User Response: Increase the address space's region size to prevent this situation from occurring in the future. Contact your IBM Support Center with any of the information that is available from the list shown in Diagnostic information for BB messages.

MAINLINE CODE FAILURE
An abend condition in the recovery manager mainline path has prevented completion of the local resource recovery function.

System Action: Task termination continues, but some local resources may not be released.

User Response: Contact your IBM Support Center with any of the information that is available from the list shown in Diagnostic information for BB messages.

BBMZE989I
CONTROL TASK (nnnn) RESOURCE RECOVERY COMPLETE - addspace (tttiiiii)
Explanation:

The task resource recovery subsystem service routine was entered to recover local resources owned by a terminating service task, where:

addspace
Is the name of the address space in which the local (task) resource recovery manager executed
tttiiiii
Is the JES identifier assigned to the address space in which the local (task) resource recovery manager executed, where:
ttt
Represents the address space type (STC, JOB or TSU)
iiiii
Is a unique JES assigned address space identification number

All local resources owned by the terminating task have been released.

This message is issued only when the system or user session is executing in extended diagnostic mode (XDM).

User response:

None.

BBMZE990E
GLOBAL RESOURCE RECOVERY ESTAE EXIT ENTERED
Explanation:

The global resource recovery subsystem ESTAE exit has been entered to recover an abend condition encountered while a global resource recovery function was in control.

User response:

Collect the system log (SYSLOG), software LOGREC data, and, if available, system (SDUMP)/SYSxDUMP contents at the time of the error. Then contact your IBM Support Center.

BBMZE991E
MODULE=nnnnnnnn OFFSET=llll ABEND CODE=txxxx
Explanation:

The global resource recovery subsystem ESTAE exit has been entered to recover an abend condition encountered while a global resource recovery function was in control, where:

nnnnnnnn
Is the failing module (CSECT) name
llll
Is the offset from the start of the failing module where the abend occurred
t
Is the abend type (S for system or U for user)
xxxx
Is the system or user abend code
User response:

Collect the system log (SYSLOG), software LOGREC data, and, if available, system (SDUMP)/SYSxDUMP contents at the time of the error. Then contact your IBM Support Center.

BBMZE991E
PSW=pppppppp IC=cccc/ILC=ll
Explanation:

The global resource recovery subsystem ESTAE exit has been entered to recover an abend condition encountered while a global resource recovery function was in control, where:

pppppppp
Is the PSW at the time of the error
cccc
Is the hexadecimal interrupt code at completion of the last instruction executed before the abend condition was signaled
ll
Is the failing instruction length (in decimal)
User response:

Collect the system log (SYSLOG), software LOGREC data, and, if available, system (SDUMP)/SYSxDUMP contents at the time of the error. Then contact your IBM Support Center.

BBMZE991E
ttt REGS xx-yy: hhhhhhhh hhhhhhhh hhhhhhhh hhhhhhhh
Explanation:

The global resource recovery subsystem ESTAE exit has been entered to recover an abend condition encountered while a global resource recovery function was in control, where:

ttt
Indicates whether the general register contents are those of the global resource recovery exit (RB) or those captured at the time of the error (ERR)
xx-yy
Indicates which general register contents are displayed in the right part of the message
hhhhhhhh
Is the hexadecimal contents of the indicated general registers

Either 4 or 8 BBMZE991E ttt REGS messages are issued. The error level registers are always displayed. The RB level registers are displayed only if they are different from the error level register contents.

User response:

Collect the system log (SYSLOG), software LOGREC data, and, if available, system (SDUMP)/SYSxDUMP contents at the time of the error. Then contact your IBM Support Center.

BBMZE992E
GLOBAL RESOURCE RECOVERY FAILED (Reason Text)
Explanation:

The global resource recovery subsystem service routine was entered to recover global resources owned by a terminating address space or server/user session control task. The global resource recovery subsystem service routine has failed for one of the following reasons:

INSUFFICIENT STORAGE
The global resource recovery subsystem service routine was unable to obtain the necessary working storage to process the release of resources for the address space. The amount of storage available in the address space is critically low.

System Action: Address space termination continues, but some address space resources may not be released.

User Response: If this message is issued out of the coordinating address space (CAS) or a user address space, increase the appropriate region size to prevent this situation from occurring in the future.

If the failure occurred in a user address space, it may be necessary to terminate that address space and restart the session.

If the failure occurred in the CAS, it may be necessary to COLD start the CAS.

Contact your IBM Support Center with any of the information that is available from the list shown in Diagnostic information for BB messages.

MAINLINE CODE FAILURE
An abend condition in the global resource recovery subsystem mainline path has prevented completion of the global resource recovery function.

System Action: Address space termination continues, but some address space resources may not be released.

User Response: Contact your IBM Support Center with any of the information that is available from the list shown in Diagnostic information for BB messages.

MTXL PROCESSING FAILURE
A failure has occurred in processing the Memory Termination Exit List (MTXL).

System Action: Address space termination continues, but global resources have been left in the system due to the failure of global resource cleanup.

User Response: Contact your IBM Support Center with any of the information that is available from the list shown in Diagnostic information for BB messages.

BBMZE993E
UNABLE TO LOCATE CAXT ENTRY FOR ASID X’xxxx
Explanation:

The global resource recovery subsystem service routine was entered to recover global resources owned by a terminating address space or server/user session control task, but the resource manager was unable to locate a CAXT (coordinating address space index table) entry for the address space's data structure.

The data structure identifies the global resource block for the terminating address space. The terminating address space is shown as the MVS hexadecimal address space ID X'xxxx'.

System action:

Some global resources owned by the terminating address space or control task may not be released.

User response:

Use the operator DUMP command to take a system dump (SDUMP) of the failing address space (if possible) and/or master (ASID=0001) address space. Contact your IBM Support Center with any of the information that is available from the list shown in Diagnostic information for BB messages.

BBMZE999I
GLOBAL RESOURCE RECOVERY COMPLETE - nnnnnnnn (tttiiiii)
Explanation:

The global resource recovery subsystem service routine was entered to recover global resources owned by a terminating address space or server/user session control task, where:

nnnnnnnn
Is the name of the terminating or terminated address space for which global resources were released
tttiiiii
Is the JES identifier assigned to the terminating or terminated address space for which global resources were released, where:
ttt
Represents the address space type (STC, JOB or TSU)
iiiii
Is a unique JES assigned address space or job identification number

All global resources owned by the terminating address space or control task have been released. This message is issued only when the system is executing in extended diagnostic mode (XDM).

User response:

None.

[[ Contents Previous Page | Next Page Index ]]