[z/OS]

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: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ .
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 (jsabpref) 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.
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 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: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ .
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.
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.
WTRN9001E: ENTRY COULD NOT BE ADDED TO XA RECOVERY TABLE, {0}
Explanation OTS was attempting to add an XA resource to its internal tables but failed. OTS will retry the add.
Action If the problem persists, contact the IBM support center.
WTRN9002W: RRS ({0}) AND XA ({1}) EPOCH NUMBERS DO NOT MATCH
Explanation OTS maintains a counter in both the XA partner log and its RRS logstream. If the counters are not the same, the logs are not in sync and recovery may fail. This message indicates that the logs are not in sync, but there is no recovery work to do.
Action Ensure both the RRS logstream and XA partner log are present on the system, and have not been deleted. If the problem persists, contact the IBM Support Center.
WTRN9003E: NO ENTRY FOUND IN XA RECOVERY TABLE FOR RECOVERY ID {0}
Explanation OTS was attempting to convert a recovery ID to its corresponding XA resource implementation. The recovery ID was not found in the XA recovery table, and it therefore cannot be recovered. If the recovery ID was being looked up during the resolution of a restart RRS UR, the branch of the transaction represented by the recovery ID may not have completed.
Action The most common cause of this error is that the XA partner log was deleted from the HFS. Ensure that the partner log is present on the system and is readable by the Controller. If the problem persists, contact the IBM Support Center.
WTRN9004E: TRANSACTION FACTORY IOR IS NULL
Explanation OTS attempted to convert the TransactionFactory object into an IOR so that it could be bound into the namespace. The IOR returned from the conversion method was null. The TransactionFactory will not be bound into the namespace.
Action If no applications look up the TransactionFactory object bound in the server_root at "TransactionFactory", then this error can be ignored. If the problem persists, or if the object is needed, contact the IBM Support Center.
WTRN9005E: TRANSACTION FACTORY COULD NOT BE INFLATED FROM IOR, {0}
Explanation OTS attempted to attach the TransactionFactory IOR to an object which is bound into the namespace. The IOR could not be inflated, and the TransactionFactory will not be bound into the namespace.
Action If no applications look up the TransactionFactory object bound in the server_root at "TransactionFactory", then this error can be ignored. If the problem persists, or if the object is needed, contact the IBM Support Center.
WTRN9006E: TRANSACTION FACTORY COULD NOT BE BOUND INTO THE NAMESPACE, {0}
Explanation OTS attempted to attach the TransactionFactory object into the namespace, but recieved an exception when doing so. The exception stack trace is provided in the message.
Action If no applications look up the TransactionFactory object bound in the server_root at "TransactionFactory", then this error can be ignored. If the problem persists, or if the object is needed, contact the IBM Support Center.
WTRN9007I: RUNTIME CLASSPATH FOR SERVER {0} HAS CHANGED SINCE LAST RESTART
Explanation The Transaction service logs the runtime class path each time the server is restarted. This class path is used during transactional recovery so that connections can be established with XA resource managers. This message indicates that the current runtime class path is different from the class path in the recovery log.
Action None. The class path changes regularly when service is applied, or when resource managers are installed at the cell, node, or server level. However, if resource managers are removed from the system, and transactional recovery needs to take place with those resource managers, it may be necessary to leave these jar files or libraries on the system until recovery has completed. If you are seeing error messages relating to transactional recovery, this may be the cause. A trace specification of OTS=event=enabled will display how the class path has changed in the Controller address space.
Reference topic    

Terms and conditions for information centers | Feedback

Last updated: Jun 13, 2012 7:39:43 PM CDT
http://publib.boulder.ibm.com/infocenter/wasinfo/v7r0/index.jsp?topic=/com.ibm.websphere.messages.doc/com.ibm.ejs.resources.ws390Messages.html

© Copyright IBM Corporation 2006, 2011. All Rights Reserved.
This information center is powered by Eclipse technology. (http://www.eclipse.org)