BBOJ

BBOJ0011I: JVM Build is {0}.

Explanation

An informational message issued during initialization of a
server that indicates the build level the started JVM.

Action

None.

BBOJ0015I: EJB Role Service is inactive.

Explanation

An informational message issued the first time the EJB
Role Service is accessed if the service is found to be inactive.

Action

Activate EJB Role Service, if required.

BBOJ0021E: Error encountered while reading "com.ibm.websphere.preconfiguredCustomServices" Java property.

Explanation

A WebSphere Application Server for z/OS server encountered an exception while
trying to read the "com.ibm.websphere.preconfiguredCustomServices" Java property.
The exception will be in the SYSPRINT along with a traceback in the
SYSOUT.

Action

This error happens if the xml filenames are not
correctly specified in the "com.ibm.websphere.preconfiguredCustomServices"
Java property. Check to see that the names are correctly specified with the
correct delimiter between them.

BBOJ0022E: Internal error encountered within Custom Services.

Explanation

A WebSphere Application Server for z/OS server encountered
an internal error within the Custom Service process. The exception will
be in the SYSPRINT along with a traceback in the SYSOUT.

Action

If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: https://ibm.biz/BdztgV WebSphere Application Server for z/OS Support page: https://ibm.biz/Bdqd4J .

BBOJ0023W: No Custom Services found in xml file {0}.

Explanation

No Custom Services were found in the specified
Custom Service xml file.

Action

Check the specified xml file.

BBOJ0024W: Custom Service class {0} not defined in xml file.

Explanation

No Custom Service class was given in the
xml file that defined the Custom Service.

Action

Check the Custom Services xml file for class definition.

BBOJ0025E: Error encountered initializing Custom Service {0}.

Explanation

A WebSphere Application Server for z/OS server encountered
an exception while running the "initialize" method on the specified Custom
Service. The exception will be in the SYSPRINT along with a traceback in
the SYSOUT.

Action

Check the implementation of the specified Custom Service.

BBOJ0026E: Error encountered creating instance of Custom Service {0}.

Explanation

A WebSphere Application Server for z/OS server encountered
an exception while creating an instance of the specified Custom Service to
be installed. The exception will be in the SYSPRINT along with a traceback
in the SYSOUT.

Action

Check the implementation of the specified Custom Service class.

BBOJ0027I: Custom Service {0} was not enabled.

Explanation

The Custom Service is not enabled.
The specified Custom Service will not be installed because it is not enabled.

Action

none

BBOJ0028E: Error encountered reading Custom Service xml file {0}.

Explanation

A WebSphere Application Server for z/OS server encountered
an exception while reading the specified xml file.
The exception will be in the SYSPRINT along with a traceback in the SYSOUT.

Action

Check that the xml file path is correctly qualified,
that the xml file exists, and that the xml file is well-formatted.

BBOJ0029E: Error encountered shutting down Custom Service {0}.

Explanation

A WebSphere Application Server for z/OS server encountered
an exception while attempting to run the implementation of Shutdown on the
specified Custom Service. The exception will be in the SYSPRINT along with
a traceback in the SYSOUT.

Action

Check the traceback to determine whether the error occurred in the
implementation of the specified Custom Service, or elsewhere.

BBOJ0031I: WebSphere for z/OS {0}

Explanation

An informational message to indicate that Global
Security Custom Property "security_EnableRunAsIdentity" to
enableSyncOSThread is set to false.

Action

None, if this is the desired mode. If this is
NOT the desired setting, set the Global Security Custom Property
"security_EnableRunAsIdentity" to true and rerun the application.

BBOJ0050I: {0}

Explanation

This message contains the trace specification for
Java tracing. The message is issued in response to the
DISPLAY,TRACE,JAVA modify command.

Action

None

BBOJ0051I: PROCESS INFORMATION: {0}/{1}, ASID={2}, PID={3}

Explanation

This message provides the job identifier (jsabjbid) and
jobname (jsabjbnm), the address space id (ASID), and the USS process id
in hexadecimal.

Action

None

BBOJ0052E: TRACE SPECIFICATION NOT VALID: {0}

Explanation

The trace specification string is not valid. The fill
in message provides more details.

Action

Correct the syntax, and set the trace specification again.

BBOJ0053I: Transformer is writing to: {0}

Explanation

C2N: The XML transformer is writing a file to the specified directory.

Action

No action is required.

BBOJ0054I: Transformer symlink - Already Linked: {0} -> {1}

Explanation

C2N: The XML transformer is not regenerating the symbolic link, the
current symoblic link is correct.

Action

No action is required.

BBOJ0055I: Transformer symlink - Linking: {0} -> {1}

Explanation

C2N: The XML transformer is generating a symbolic link as indicated.

Action

No action is required.

BBOJ0056I: Transformer Processing Complete, RC=0.

Explanation

C2N: The XML transformer has completed.

Action

No action is required.

BBOJ0057E: Transformer symlink - Symlink not created properly: {0} -> {1}

Explanation

C2N: The XML transformer did not complete the symbolic link properly.

Action

Make sure the correct symbolic link was created.

BBOJ0058I: Transformer Looking: {0}

Explanation

C2N: The XML transformer looked for the specified file, but the transformer
did not find the file.

Action

No action is required. The file might not be necessary for the transformation.

BBOJ0059I: Transforming: {0}

Explanation

C2N: The XML transformer is transforming the specified file.

Action

No action is required.

BBOJ0060E: Transformer Exception: {0}

Explanation

C2N: An exception occurred during the transformation of an XML file.

Action

The message should contain the name of the file that was being transformed
and the line number where the failure occurred. Check the XML file for the characters that are not valid.

BBOJ0061I: Transformer Usage:

Explanation

This message is for informational purposes only.

Action

No action is required.

BBOJ0062I: wsc2n.sh -s <CELL_NAME> [-trace]

Explanation

This message is for informational purposes only.

Action

No action is required.

BBOJ0063I: wsc2n.sh -s <CELL_NAME> <NODE_NAME> [-trace]

Explanation

This message is for informational purposes only.

Action

No action is required.

BBOJ0064I: wsc2n.sh -s <CELL_NAME> <NODE_NAME> <SERVER_NAME> [-trace]

Explanation

This message is for informational purposes only.

Action

No action is required.

BBOJ0065I: wsc2n.sh -d <CELL_NAME> <NODE_NAME> <DAEMON_NAME> <DAEMON_INSTANCE_NAME> [-trace]

Explanation

This message is for informational purposes only.

Action

No action is required.

BBOJ0066I: wsc2n.sh -X [-trace] #Cell Transform and Daemon Transform.

Explanation

This message shows how to pass parameters to the wsc2n.sh file. This script
file generates the was.env file, the control.jvm.options file, the servant.jvm.options file, and the
adjunct.jvm.options file for each server and the was.env file for the location service daemon.

Action

Specify the parameters that you want to pass to the wsc2n.sh file.

BBOJ0067E: Transformer Processing Complete, Errors Occured, RC=8

Explanation

C2N: The transformation of the XML file completed. However, the
transformer had trouble transforming some of the data and issued a return code of 8. This return code
indicates that transformation errors occurred.

Action

Check the was.env, control.jvm.options, servant.jvm.options, and adjunct.jvm.options
files for errors.

BBOJ0068I: Transformer symlink - Deleting: {0} -> {1}

Explanation

C2N: The XML transformer is deleting the indicated symbolic link.

Action

No action is required.

BBOJ0069I: Transformer symlink - Deleting: {0}

Explanation

C2N: The XML transformer is deleting the indicated dead symbolic link. This symbolic
link does not point anywhere.

Action

No action is required.

BBOJ0077I: {0}

Explanation

This message is used to display JVM system properties
at JVM startup.

Action

None

BBOJ0078W: Exception {0} loading or parsing endpoint configuration xml file {1}

Explanation

An exception was found while reading the specified xml file.

Action

Verify the existance of the xml file and that it is a valid xml document.

BBOJ0079W: No endpoint information found in xml file {0}.

Explanation

No endpoint was provided in the specified xml file.

Action

If endpoint based classification is required, provide endpoint
configuration information according to the Inbound Classification syntax.

BBOJ0080E: Error encountered during initialization {0}.

Explanation

A WebSphere Application Server for z/OS server encountered an error
during server startup.

Action

Exception details accompany error message.

BBOJ0081W: EJB {0} requests SyncToOSThread, but the server is not enabled for SyncToOSThread

Explanation

SyncToOSThread synchronizes the Java EE role identity to the
OS thread. The OS thread identity is equal to the Java EE role identity for
the duration of the EJB method invocation. This message indicates that
while an application has been configured to use SyncToOSThread functionality,
the server where the application is installed is not configured to support SyncToOSThread.

Action

If SyncToOSThread support is required, refer to the WebSphere Application Server
for z/OS Information Center for instructions on how to enable SyncToOSThread.

BBOJ0083W: Exception {0} {1} connection browser for MDB {2}: {3}

Explanation

An exception was found while starting or stopping the connection browser
for the specified Message Driven Bean. If the connection browser was being started,
message delivery to the specified MDB will not work properly.

Action

BBOJ0084W: Application {0} has requested SyncToOSThread, but the server is not enabled for SyncToOSThread

Explanation

SyncToOSThread synchronizes the Java EE role identity to
the OS thread. The OS thread identity is equal to the Java EE role identity
for the duration of the request. This message indicates that while an
application has been configured to use SyncToOSThread functionality,
the server where the application is installed is not configured to support SyncToOSThread.

Action

If SyncToOSThread support is required, refer to the WebSphere Application Server
for z/OS Information Center for instructions on how to enable SyncToOSThread.

BBOJ0085E: PROBLEMS ENCOUNTERED PARSING WLM CLASSIFICATION XML FILE {0}

Explanation

Processing the XML file pointed to by configuration variable
"wlm_classification_file" resulted in a failure. The contents
of the file are not used. The specific exception, with details, is provided
in the fill-in.

Action

Correct the problem in the XML file and restart the
server

BBOJ0086E: Invalid value specified for property {0}. Value: {1}. Valid values: {2}

Explanation

The property value is not valid. This could result in
unexpected behavior.

Action

Assign a valid value to the property.

BBOJ0088I: MLP NAME {0} TIME {1} secs.

Explanation

This message is used to display MDB statistics.

Action

None

BBOJ0089I: {0}

Explanation

This message is used to display MDB statistics headers.

Action

None

BBOJ0090I: {0}

Explanation

This message is used to display MDB statistics.

Action

None

BBOJ0091I: Duplicate Message Reference Count:{0} MR:{1}

Explanation

This message is used to display MDB statistics.

Action

None

BBOJ0092I: NO ACTIVE LISTENER PORT, {0} COMMAND IGNORED

Explanation

There are no Listener Ports for which to display MDB statistics.

Action

None

BBOJ0093W: WEBSPHERE MQ JAVA FEATURE NOT INSTALLED

Explanation

WebSphere MQ Java classes cannot be found.

Action

Verify that the identity associated with the
controller region process has the authority to read and execute
in the path specified by the environment variable MQ_INSTALL_ROOT.

BBOJ0094E: MDB {0} REGISTRATION FAILED - CAUSE: {1}

Explanation

There was a problem registering the indicated MDB in the Controller
Region for scalable messaging processing. Messages will not be
delivered to the indicated MDB. The exception message is included.

Action

Resolve the problem included in the
message.

BBOJ0095W: JAVA VERSION/LEVEL IS NOT SUPPORTED BY WEBSPHERE FOR Z/OS

Explanation

The current Java Runtime Environment version/level is not supported.

Action

Update the Java Runtime Environment to the supported version/level and restart the server.

BBOJ0096I: WEBSPHERE FOR Z/OS INSTALL-HFS SERVICE LEVEL: {0}, DATE: {1}

Explanation

Displays the WebSphere Application Server for z/OS installed
HFS Service Level and Service Date, as read from the HFS installation root.

Action

None

BBOJ0097E: MDB FAILURE: {0}, IN CLASS: {1}, IN METHOD: {2}

Explanation

This message is intended as a generic serious error message
for MDB error conditions that do not require their own distinct error messages.

Action

If the problem persists, contact the IBM support center.

BBOJ0098E: MDB PROBLEM: JMSEXCEPTION CAUGHT IN CONTROLLER. EXCEPTION: {0}

Explanation

A JMSException was thrown on the JMS Connection backing the controller
portion of an MDB listener. An exception stack trace is displayed. MDB listener
recovery will be attempted (or not) according to Message Listener Service settings.

Action

If the underlying cause of the exception requires the intervention of a
WebSphere MQ Administrator to resolve, then perform the approriate administrative actions.
If the problem persists, contact the IBM support center.

BBOJ0099E: MDB PROBLEM: INTERNAL STOP ISSUED FOR MDB LISTENER PORT: {0}, DESTINATION: {1} FOR SERVER: {2}

Explanation

Listener Port has been stopped. Previous log entries should
indicate what reason the Listener Port was stopped for (e.g. because the
maximum retries limit was reached for a given message or because the
maximum number of recovery attempts was reached for a controller or servant
portion of an MDB listener).

Action

Attempt to resolve the root cause of the Listener Port stop,
and then restart the Listener Port.

BBOJ0100I: MDB LISTENER STARTED SUCCESSFULLY FOR MDB: {0}, LISTENER PORT: {1}, DESTINATION: {2}

Explanation

The controller portion of the given MDB listener has started successfully.

Action

None

BBOJ0101I: MDB LISTENER STOPPED SUCCESSFULLY FOR MDB: {0}, LISTENER PORT: {1}, DESTINATION: {2}

Explanation

The controller portion of the given MDB listener has been stopped.

Action

If the stop has occurred unexpectedly, examine the controller logs
for preceeding error messages.

BBOJ0102I: MDB LISTENER FOR MDB: {0}, LISTENER PORT: {1} WILL ATTEMPT TO RESTART IN {2} SECONDS. RECOVERY COUNT = {3}.

Explanation

The controller portion of the given MDB listener has stopped due to error,
but since the user has defined the Message Listener Service custom properties:
MAX.RECOVERY.RETRIES and RECOVERY.RETRY.INTERVAL, the controller will attempt to restart it.

Action

None

BBOJ0103E: MAXIMUM RESTART RETRY COUNT OF {0} REACHED FOR MDB: {1}, LISTENER PORT: {2}

Explanation

The controller portion of the given MDB listener has reached its retry
limit for restarting, resulting in the stopping of the associated Listener Port and
all MDB listeners mapped to it.

Action

Examine the controller logs to understand the root cause of the failure
to restart the controller portion of the MDB listener. If the underlying cause of the
failure requires the intervention of a WebSphere MQ Administrator to resolve, then
perform the approriate administrative actions. When the root cause is resolved, then
restart the Listener Port.

BBOJ0104W: RUNNING WITH JIT DISABLED IS NOT RECOMMEDED FOR WEBSPHERE ON Z/OS

Explanation

Running Java Runtime Environment with JIT disabled may cause reduced performance.

Action

Update Java Runtime Environment to run with JIT enabled and restart the server.

BBOJ0105W: DETECTED DUPLICATE BASE REGISTRAR: {0}. APPLIED REGISTRATION DATA: {1}

Explanation

Duplicate BASE registrar data was detected while reading the *.registrar
files from the configuration. The duplicate data is discarded.
The WebSphere Application Server for z/OS will register using the
applied registration data indicated in the message.

Action

There should be only one registrar entry with an id element of BASE in
the *.registrar files in the configuration. Check your configuration data.

BBOJ0106I: REQUEST {0} ASID {1} TCB {2}

Explanation

Response to the MODIFY DISPLAY,THREADS command.

Action

None

BBOJ0107I: SERVANT DISPATCHED REQUEST AT {0}

Explanation

Shows the servant dispatch time for the request previously displayed under message BBOJ0106I

Action

None

BBOJ0108I: JVM THD {0} HUNG: ITI {1}

Explanation

Shows details for the request previously displayed under message BBOJ0106I. JVM THD HUNG indicates that the thread is waiting on either Java socket based network I/O, or an Object.wait condition. The ITI status is given as "inactive" if no attempts have been made to interrupt the thread, "active" if the ITI is currently trying to interrupt the thread, or "ended" if the maximum number of attempts to interrupt the thread have been exceeded.

Action

None

BBOJ0109I: URI: {0}

Explanation

Shows the request URI (if available) for the request previously displayed under message BBOJ0106I.

Action

None

BBOJ0110I: DETAILS FOR {0}: {1}

Explanation

Shows details for an ODI registered to the request previously displayed under message BBOJ0106I. There may be multiple ODIs registered for each request, so there may be more than one BBOJ0110I message per request. The details shown here are provided by the ODI implementor.

Action

None

BBOJ0111I: REQUEST ASID JW TO RE DISPATCH TIME

Explanation

Displays the column labels for the data displayed under message BBOJ0112I when a summary command is issued via the MODIFY DISPLAY,THREADS command. REQUEST is the request ID, ASID is the address space identifier which the request is running in, JW indicates the thread is hung in a Java socket call or is waiting on a lock, TO indicates the request is being cleaned up by the interruptible thread infrastructure, RE indicates the retry count of the interruptible thread infrastructure has been exceeded for this request, and dispatch time shows the time and date that the request was received into the controller region.

Action

None

BBOJ0112I: {0}

Explanation

Displays the details for a request when a MODIFY DISPLAY,THREADS command is issued. The column labels can be found in message BBOJ0111I.

Action

None

BBOJ0113I: The Interruptible Thread Infrastructure is attempting to advance work running under request {0}

Explanation

Indicates that the Interruptible Thread Infrastructure has been activated for the indicated request. This occurs when one of the request level timeouts has been exceeded. The presence of this message indicates that an attempt will be made to advance work, but does not guarantee that the work will advance. For more information about the request, a modify command may be issued against the server and the request ID (ex. MODIFY server,DISPLAY,THREADS,REQUEST=x).

Action

None

BBOJ0114I: The Interruptible Thread Infrastructure is attempting to interrupt a request {0} that exceeded its CPU Time

Explanation

Indicates that the Interruptible Thread Infrastructure has been activated for the indicated request. This occurs when the request has exceeded its allotted CPU Time. The presence of this message indicates that an attempt will be made to interrupt the request.

Action

None

BBOJ0115E: AN ERROR OCCURRED PROCESSING TOKEN {0}

Explanation

Indicates that part of the display threads command was not understood.

Action

Verify that the syntax used on the display threads command was valid, and re-issue the command. To get a list of supported commands, replace the failing keyword with HELP, and obtain the list of supported commands from message BBOJ0016I.

BBOJ0116I: THIS COMMAND MAY BE FOLLOWED BY ONE OF THE FOLLOWING KEYWORDS: {0}

Explanation

Response to keyword HELP in a DISPLAY,THREADS command. A list of valid keywords is displayed.

Action

Re-issue the display command using one of the indicated keywords.

BBOJ0117I: JAVA THREAD STACK TRACEBACK FOR THREAD {0}: {1}

Explanation

Displays the Java stack traceback for the given Java thread.
This message is issued to the error log.

Action

None.

BBOJ0118I: {0}

Explanation

Displays the details for a request as a result of a MODIFY DPM command.

Action

None

BBOJ0119I: CONTROLLER RECEIVED REQUEST AT {0}

Explanation

Shows the time the request was received into the controller for the request previously displayed under message BBOJ0106I

Action

None

BBOJ0120I: CONTROLLER QUEUED REQUEST TO WLM AT {0}

Explanation

Shows the time the request was queued to WLM for the request previously displayed under message BBOJ0106I

Action

None

BBOJ0121I: The Interruptible Thread Infrastructure attempted to interrupt a request {0} that exceeded its CPU Time. The request completed prior to performing CPU Time Exceeded recovery actions.

Explanation

Action

None

BBOJ0122I: The Interruptible Thread Infrastructure about to drive a ODI to advance work running under request {0}, ODI details: {1}

Explanation

Indicates that the Interruptible Thread Infrastructure is about to invoke the interrupt method on the indicated ODI for the indicated request. This occurs when one of the request level timeouts has been exceeded. The presence of this message indicates that an attempt will be made to advance work, but does not guarantee that the work will advance. For more information about the request, a modify command may be issued against the server and the request ID (ex. MODIFY server,DISPLAY,THREADS,REQUEST=x). This message can be suppressed by setting application server custom property com.ibm.ws390.interrupt.disableBBOJ0122I=true.

Action

None

BBOJ0123I: The Interruptible Thread Infrastructure is attempting to advance work running under request {0}, request details: {1}

Explanation

Action

None

BBOJ0124I: The Interruptible Thread Infrastructure timed out a request and it has become unresponsive, request {0}, request details: {1}

Explanation

Action

None

BBOJ0125I: The Interruptible Thread Infrastructure detected a request {0} that exceeded its CPU Time, request details: {1}

Explanation

Action

None

BBOJ0129I: The {0} workload classification file was loaded at {1}

Explanation

This message is for informational purposes only.

Action

No action is required.

BBOJ0130I: CONNECTION MANAGEMENT IN A SERVANT REGION DETECTED THAT THE RESOURCE IDENTIFIED BY JNDI NAME {0} IS DISCONNECTED FROM SERVER {1}. ACTION TAKEN: {2}.

Explanation

A resource used by WebSphere applications is disconnected. This message may be used by automation to reroute work away from the server. The property "failureNotificationActionCode" configures the action taken when a resource is disconnected.

Action

No action is required.

BBOJ0131I: RESTORATIVE ACTION IS BEING TAKEN FOR THE RESOURCE IDENTIFIED BY JNDI NAME {0} ON SERVER {1}, REASON={3}. ACTION TAKEN: {2}.

Explanation

Taking restorative action for a resource used by WebSphere applications. This message may be used by automation to reroute work back to the server. The property "failureNotificationActionCode" configures the action taken when a resource is reconnected. Reason code 1 means that Connection Management in a servant region detected that the resource is reconnected. Reason code 2 means that all servant regions that detected the resource being disconnected have been terminated.

Action

No action is required.

BBOJ0132I: MDB LISTENER PORT {0} FAILED TO RESTART FOR A WORKLOAD CLASSIFICATION UPDATE - CAUSE: {1}

Explanation

The Listener Port failed to restart during the
processing of a workload classification document reclassify command.
The exception message is included.

Action

Identify and correct the cause of the failure then
restart the Listener Port.

BBOJ0133I: The configured primary resource with a JNDI name of {0} is unavailable. New requests will be routed to the configured alternate resource that has a JNDI name of {1}.

Explanation

Connection Management has detected that the configured primary resource is unavailable. New requests will be routed to the configured alternate resource.

Action

Contact your database or system administrator to determine the state of the resource in question.

BBOJ0134I: The configured primary resource with a JNDI name of {0} and the configured alternate resource that has a JNDI name of {1} are unavailable.

Explanation

Connection Management has detected that both the configured primary and alternate resources have become unavailable. Requests cannot be rerouted.

Action

Contact your database or system administrator to determine the state of the resources in question.

BBOJ0135I: The configured resource with a JNDI name of {0} is available to process new requests for the resource with a JNDI name of {1}.

Explanation

The configured primary or alternate resource with the specified JNDI name is now available to process new requests.

Action

No action is required.

BBOJ0137E: Failed to parse registrar file {0}.

Explanation

A registrar file associated with the WebSphere Application Server for z/OS installation was unable to be parsed. The server could be running with invalid or missing registration information.

Action

Ensure that the registrar file in question is encoded in ASCII and is properly formatted. Check the server"s FFDC log files for more information on any causing exceptions.

BBOJ0138I: THE SERVER HAS THE FOLLOWING INTERIM FIXES INSTALLED IN THE RUNTIME: {0}.

Explanation

Any fixes that are installed are listed along with a list of APARs included in those installed fixes. No installed fixes are indicated as "none". An ‘unavailable’ indication is presented when an error occurs in retrieving the iFix list. A ‘contents unknown’ indication is presented when the APARs within an installed iFix cannot be determined.

Action

No action is required.