BBOO0000I | WEBSPHERE APPLICATION SERVER FOR Z/OS AND OS/390 LICENSED MATERIAL
- PROPERTY OF IBM 5655-I35 (C) COPYRIGHT IBM CORP. 2000, 2003 ALL RIGHTS RESERVED. U.S. GOVERNMENT USERS - RESTRICTED RIGHTS - USE, DUPLICATION, OR DISCLOSURE RESTRICTED BY GSA-ADP SCHEDULE CONTRACT WITH IBM CORP. IBM IS A REGISTERED TRADEMARK OF THE IBM CORP. |
Explanation: Displays the IBM copyright statement
User Response: None.
BBOO0001I | WEBSPHERE FOR Z/OS CONTROL PROCESS
string/string/string/string IS STARTING. |
Explanation: The WebSphere for z/OS control process address space indicated by "string" is starting. This address space is defined as a server instance in the WebSphere for z/OS Administration end-user interface. The process name strings are cell name, node name, cluster name, server name.
User Response: None.
BBOO0002I | WEBSPHERE FOR Z/OS CONTROL PROCESS string ENDED
NORMALLY. |
Explanation: The WebSphere for z/OS control process address space indicated by "string" has ended normally. This address space is defined as a server instance in the WebSphere for z/OS Administration end-user interface.
User Response: None.
BBOO0003E | WEBSPHERE FOR Z/OS CONTROL PROCESS string ENDED
ABNORMALLY, REASON=hstring. |
Explanation: The WebSphere for z/OS control process address space indicated by "string" has ended abnormally. This address space is defined as a server instance in the WebSphere for z/OS Administration end-user interface.
User Response: "hstring" indicates a minor code that describes the specific failure that occurred.
BBOO0004I | WEBSPHERE FOR Z/OS SERVANT PROCESS
string/string/string/string IS STARTING. |
Explanation: The WebSphere for z/OS application servant address space indicated by "string" is starting. This address space is defined as a server instance in the WebSphere for z/OS Administration end-user interface. The process name strings are cell name, node name, cluster name, server name.
User Response: None.
BBOO0005I | WEBSPHERE FOR Z/OS SERVANT PROCESS string ENDED
NORMALLY. |
Explanation: The WebSphere for z/OS application servant address space indicated by "string" has ended normally. This address space is defined as a server instance in the WebSphere for z/OS Administration end-user interface.
User Response: None.
BBOO0006E | WEBSPHERE FOR Z/OS PROCESS string ENDED ABNORMALLY,
REASON=hstring. |
Explanation: The WebSphere for z/OS application process address space indicated by "string" has ended abnormally. This address space is defined as a server instance in the WebSphere for z/OS Administration end-user interface.
User Response: "hstring" indicates a minor code that describes the specific failure that occurred. See previous messages in the job log or system log for further information.
BBOO0007I | WEBSPHERE FOR Z/OS DAEMON
string/string/string/string IS STARTING. |
Explanation: The WebSphere for z/OS daemon address space is starting. The process name strings are cell name, node name, cluster name, server name.
User Response: None.
BBOO0008I | WEBSPHERE FOR Z/OS DAEMON string ENDED NORMALLY. |
Explanation: The WebSphere for z/OS daemon address space has ended normally.
User Response: None.
BBOO0009E | WEBSPHERE FOR Z/OS DAEMON string ENDED ABNORMALLY,
REASON=hstring. |
Explanation: The WebSphere for z/OS daemon address space has ended abnormally.
User Response: "hstring" indicates a minor code that describes the specific failure that occurred. See previous messages in the job log or system log for further information.
BBOO0010W | The function string+dstring raised CORBA system
exception string. Error code is hstring. |
Explanation: WebSphere for z/OS identified an abnormal situation for which it raised the indicated CORBA system exception.
User Response: See additional messages to determine how WebSphere for z/OS might have handled the error. If no related messages are found, see the WebSphere for z/OS Error Codes section of this book for a description of this error.
BBOO0011W | The function string+dstring received CORBA
system exception string. Error code is hstring. |
Explanation: WebSphere for z/OS caught the indicated CORBA system exception.
User Response: See additional messages to determine how WebSphere for z/OS handled the error. If no related messages are found, see the WebSphere for z/OS Error Codes section of this book for a description of this error.
BBOO0012W | The function string+dstring raised a user
exception string. |
Explanation: WebSphere for z/OS identified an abnormal situation for which it raised the indicated CORBA user exception.
User Response: See additional messages to determine how WebSphere for z/OS handled the error.
BBOO0013W | The function string+dstring received a user
exception string. |
Explanation: WebSphere for z/OS caught the indicated CORBA user exception.
User Response: See additional messages to determine how WebSphere for z/OS handled the error.
BBOO00135 | WEBSPHERE FOR Z/OS CANCEL COMMAND ISSUED FOR SERVER
string. |
Explanation: The MVS Modify command has been issued to cancel without restart against a WebSphere for z/OS address space.
User Response: None.
BBOO0014W | The function string+dstring received an
unexpected exception. |
Explanation: WebSphere for z/OS caught an unexpected error. This is caused by an application issuing a throw of a value or an object instance other than the CORBA defined values of CORBA::SystemException and CORBA::UserException. For example, the application issued a throw error where the error might be of type int.
User Response: See additional messages to determine how WebSphere for z/OS handled the error.
BBOO0015I | INITIALIZATION COMPLETE FOR DAEMON string. |
Explanation: Initialization is complete for the WebSphere for z/OS daemon indicated.
User Response: None.
BBOO0017E | ORBSRVNAME PARAMETER WAS NOT SPECIFIED. |
Explanation: Missing ORBsrvname parameter or value for the current program.
User Response: Modify the program parameters passed to the program, passing ORBsrvname <value>.
BBOO0018I | Attempting retry in current thread (hstring
hstring). |
Explanation: WebSphere for z/OS received control in its signal handler and is attempting to retry the error.
User Response: None.
BBOO0019I | INITIALIZATION COMPLETE FOR WEBSPHERE FOR Z/OS CONTROL PROCESS
string. |
Explanation: Initialization is complete for the WebSphere for z/OS control process address space indicated. This address space is defined as a server instance in the WebSphere for z/OS Administration end-user interface.
User Response: None.
BBOO0020I | INITIALIZATION COMPLETE FOR WEBSPHERE FOR Z/OS SERVANT PROCESS
string. |
Explanation: Initialization is complete for the WebSphere for z/OS application servant address space indicated.
User Response: None.
BBOO0021E | Assertion failed: 'string', file string, line dstring. |
Explanation: The above assertion failed.
User Response: This is an internal programming error. For further information on resolving this error, consult the IBM WebSphere Application Server for z/OS Support website at: http:www-3.ibm.com/software/webservers/appserv/zos_os390/support.html This site provides searchable databases of technotes, solutions, and e-fixes. Information on contacting the WebSphere Support team is also provided.
BBOO0022W | The function string+dstring rethrew CORBA system
exception string. Error code is hstring. |
Explanation: WebSphere for z/OS identified an abnormal situation for which it caught the indicated CORBA system exception and re-threw it.
User Response: See additional messages to determine how WebSphere for z/OS handled the error. If no related messages are found, see the WebSphere for z/OS Error Codes section of this book for a description of this error.
BBOO0023W | The function string+dstring rethrew user
exception string. |
Explanation: WebSphere for z/OS identified an abnormal situation for which it caught the indicated CORBA user exception and re-threw it.
User Response: See additional messages to determine how WebSphere for z/OS handled the error.
BBOO0024I | ERRORS WILL BE WRITTEN TO string
string. |
Explanation: WebSphere for z/OS will be using the indicated repository for logging errors. For file repositories,the file is obtained from the BBOERROR DD specification. If no such specification is provided, and a system logger stream has been specified, the log stream will be used for logging errors. If logging to the designated file or log stream can not be done, then CERR will be used for error logging. Note that CERR is equivalent to SYSOUT by default.
User Response: None.
BBOO0026W | Failure during string of log file string,
errno=dstring [string]. |
Explanation: The indicated function failed while processing the indicated data set. The failure is errno. When there is an error log file failure (or DD:BBOERROR), all error messages will be routed to CERR (SYSOUT).
User Response: See the OS/390 C/C++ Library Reference for a description of this error.
BBOO0027W | Failure attempting to read/write the header record for log file
'string', error=hstring. |
Explanation: The indicated log file has a bad header record. The error is an internal value useful for IBM Support. When there is an error log file failure (or DD:BBOERROR), all error messages will be routed to CERR (SYSOUT).
User Response: Additional messages may have been written to the job log. Search the job log for messages relating to this data set and refer to the documentation on that error message. If you want to use this data set for a log file, re-allocate (being sure to specify the correct attributes) and initialize it.
BBOO0028W | Incorrect attributes for log file
'string'. |
Explanation: The indicated file cannot be used for a log because of the incorrect attributes. The correct attributes are: sequential (PO), recfm must be fixed/blocked. When there is an error log file failure, all error messages are routed to CERR (SYSOUT).
User Response: If you want to use this data set for a log file, re-allocate (being sure to specify the correct attributes) and initialize it.
BBOO0029W | Incorrect record length for log file 'string'. Record length must be dstring. |
Explanation: The indicated file cannot be used for a log because it has an incorrect record length (lrecl). When there is an error log file failure, all error messages are routed to CERR (SYSOUT).
User Response: If you want to use this data set for a log file, re-allocate and initialize it with the correct attributes.
BBOO0030W | Unable to use specified language of string. Defaulted to
use language ENUS (English US). |
Explanation: WebSphere for z/OS could not use the specified language. WebSphere for z/OS attempted to load a DLL by the name BBOxxxx where xxxx is the language indicated by string, However, the DLL load failed. WebSphere for z/OS used the default language of ENUS instead.
User Response: None.
BBOO0031E | Function 'MsgRetrieve()' not exported. Check your STEPLIB to ensure it can be located. |
Explanation: WebSphere for z/OS could not load the specified function within the message DLL.
User Response: Ensure that the message DLL is part of the execution path for this process. If it is not, add it to the execution path: STEPLIB, JOBLIB, LPA, or link list.
BBOO0032W | Processing for signal 'string'
(dstring), in current thread (hstring hstring). |
Explanation: WebSphere for z/OS received control for a signal.
User Response: Check for messages to determine the resolution of the problem. If there are no additional messages, the signal was handled and the thread continued to process.
BBOO0033W | Processing for signal 'string' (dstring) with string , in current thread (hstring hstring). |
Explanation: WebSphere for z/OS received control for a signal with accompanying information. This additional information is at least one of: original abend code (abendcode value), original abend reason code (rsncode value), signal code (si_code value in text and decimal), error number (si_errno value), or failing address (si_addr value).
User Response: Ensure the daemon is started on the system where the client is running. For abends see the appropriate messages and code documentation for the failing service. For other signal types see C/C++ Run-time Library Reference for documentation on signals. If there are no additional messages, the signal was handled and the thread continued to process.
BBOO0034W | Terminating the current thread (hstring
hstring), REASON=hstring. |
Explanation: WebSphere for z/OS is terminating the current thread within the current process (address space).
User Response: See previous messages for the reason this process was terminated.
BBOO0035W | TERMINATING THE CURRENT PROCESS, REASON=hstring. |
Explanation: WebSphere for z/OS is terminating the current process (address space).
User Response: See previous messages for the reason this process was terminated.
BBOO0036E | FUNCTION string FAILED WITH RC=dstring. |
Explanation: WebSphere for z/OS failed as indicated and that function completed with a decimal return code indicated by RC.
User Response: Consult the function in the OS/390 C++ Library Reference, OS/390 MVS Programming: Assembler Services Reference, OS/390 MVS Programming: Authorized Assembler Services Reference, OS/390 Security Server LDAP Server Adm & Usage or other appropriate OS/390 reference book for a description of this error.
BBOO0037E | Function string failed with RC=dstring,
REASON=hstring. |
Explanation: WebSphere for z/OS failed as indicated and that function completed with a decimal return code indicated by RC and a hexadecimal reason code indicated by REASON.
User Response: Consult the function indicated in the OS/390 C/C++ Library Reference, OS/390 MVS Programming: Assembler Services Reference, OS/390 MVS Programming: Authorized Assembler Services Reference, OS/390 Security Server LDAP Server Adm & Usage or other appropriate z/OS reference book for a description of this error.
BBOO0038E | Function string failed with RC=dstring,
REASON=hstring, EXTENDED REASON=hstring. |
Explanation: WebSphere for z/OS failed as indicated and that function completed with a decimal return code indicated by RC, a hexadecimal reason code indicated by REASON, and an extended hexadecimal reason code indicated by EXTENDED REASON.
User Response: Consult the function indicated in the OS/390 C/C++ Library Reference, OS/390 MVS Programming: Assembler Services Reference, OS/390 MVS Programming: Authorized Assembler Services Reference,or other appropriate z/OS reference book for a description of this error.
BBOO0039E | Function string failed with RV=dstring,
RC=dstring, RSN=hstring, [string]. |
Explanation: WebSphere for z/OS issued the indicated function and that function completed with a decimal return value indicated by RV, a decimal return code indicated by RC, and a hexadecimal reason code indicated by RSN.
User Response: See the OS/390 C++ Run-Time Library Reference or the UNIX System Services Messages and Codes for descriptions of the returned value and codes.
BBOO0040E | Function string failed with RV=dstring,
RC=dstring, RSN=hstring, [string] |
Explanation: WebSphere for z/OS issued the indicated function and that function completed with a decimal return value indicated by RV, a decimal return code indicated by RC, and a hexadecimal reason code indicated by RSN. TCPIP is not running.
User Response: See the OS/390 C++ Run-Time Library Reference or the UNIX System Services Messages and Codes for descriptions of the returned value and codes.
BBOO0041E | Function string failed with RV=dstring,
RC=dstring, RSN=hstring, [string]. |
Explanation: WebSphere for z/OS issued the indicated function and that function completed with a decimal return value indicated by RV, a decimal return code indicated by RC, and a hexadecimal reason code indicated by RSN.
User Response: See the OS/390 C++ Run-Time Library Reference or the UNIX System Services Messages and Codes for descriptions of the returned value and codes.
BBOO0042E | Function string failed with RV=dstring,
RC=dstring, RSN=hstring, [string]. |
Explanation: WebSphere for z/OS issued the indicated function and that function completed with a decimal return value indicated by RV, a decimal return code indicated by RC, and a hexadecimal reason code indicated by RSN.
User Response: See the OS/390 C++ Run-Time Library Reference or the UNIX System Services Messages and Codes for descriptions of the returned value and codes.
BBOO0043E | Server session failed with invalid foreign host
sin_addr=hstring. |
Explanation: WebSphere for z/OS attempted to construct a session with a client but could not obtain a dotted internet protocol address from the sin_addr.
User Response: See the OS/390 C++ Run-Time Library Reference for a description of the code. Correct the address information for the client.
BBOO0044E | Internal communications error:
REASON=hstring. |
Explanation: WebSphere for z/OS experienced a communications error.
User Response: See the WebSphere for z/OS Error Codes section of this book for a description of this error.
BBOO0045E | Internal failure, REASON=hstring. |
Explanation: WebSphere for z/OS failed with an internal error.
User Response: See the WebSphere for z/OS Error Codes section of this book for a description of this error.
BBOO0046E | Internal failure, REASON=hstring, EXTENDED
REASON=hstring. |
Explanation: WebSphere for z/OS failed with an internal error.
User Response: See the WebSphere for z/OS Error Codes section of this book for a description of this error.
BBOO0047E | Function string failed with errno=dstring
[string]. |
Explanation: WebSphere for z/OS failed as indicated and that function completed with a decimal return code indicated by errno. The string describing the errno is shown between the braces.
User Response: Consult the function indicated in the OS/390 C/C++ Library Reference, OS/390 MVS Programming: Assembler Services Reference, OS/390 MVS Programming: Authorized Assembler Services Reference, or other appropriate z/OS reference book for a description of this error.
BBOO0048W | WEBSPHERE FOR Z/OS COMPONENT TRACE MAY HAVE LOST ENTRIES. |
Explanation: The WebSphere for z/OS administrator started the WebSphere component trace (or the trace was started by default). WebSphere for z/OS overlaid some older entries before they could be captured by a component trace external writer. The system could not write the trace entries to the data set for one of the following reasons: 1. The operator did not start the external writer before connecting the WebSphere component trace to the external writer. 2. WebSphere for z/OS reused the full trace buffer before the system could write the trace entries out to the trace data set. Some older trace entries have been lost. System action: The WebSphere for z/OS component trace continues. Newer trace entries continue to overlay older trace entries.
User Response: Change your trace buffer size specification or your number of trace buffers specification for the next request.
BBOO0049E | Local comm call string failed with RV=dstring,
RC=dstring, RSN=hstring, [string]. |
Explanation: Error occurred inside of Local IIOP processing. Additional information, including the message size, will be appended to "[string]" when EMSGSIZE or ENOMEM errors are encountered during IIOP message send.
User Response: This is an internal programming error. For further information on resolving this error, consult the IBM WebSphere Application Server for z/OS Support website at: http:www-3.ibm.com/software/webservers/appserv/zos_os390/support.html This site provides searchable databases of technotes, solutions, and e-fixes. Information on contacting the WebSphere Support team is also provided.
BBOO0050I | An error occurred in EXEC SQL. The description returned from the
DSNTIAR service is: string: |
Explanation: A non-zero result was returned from EXEC SQL.
User Response: Refer to DB2 reference books and perform the appropriate actions.
BBOO0051W | THE DB2 DSNTIAR SERVICE COULD NOT BE FETCHED. A DETAILED
DESCRIPTION OF SQLCODE COULD NOT BE OBTAINED. |
Explanation: An attempt to FETCH the DSNTIAR module failed. Details of the SQL error code could not be obtained.
User Response: The DSNTIAR module is supposed to be in the DB2 SDSNLOAD data set. Ensure that the data set is part of the execution path of this process: STEPLIB, JOBLIB, LPA, or link list.
BBOO0052W | Key values were not set, data store not changed. |
Explanation: The data object was asked to update the data store but the KEY values had not been set.
User Response: none.
BBOO0053E | CLASS MANAGER FAILED TO LOAD DLL string. |
Explanation: Class Manager failed to load the specified DLL. The data set containing the DLL might be missing from the STEPLIB for the servant process handling the request.
User Response: This is an internal programming error. For further information on resolving this error, consult the IBM WebSphere Application Server for z/OS Support website at: http:www-3.ibm.com/software/webservers/appserv/zos_os390/support.html This site provides searchable databases of technotes, solutions, and e-fixes. Information on contacting the WebSphere Support team is also provided.
BBOO0054W | CLASS MANAGER FAILED TO FIND CLASS string IN THE CLASS
LIST. |
Explanation: Class manager failed to find the specified class in the list of classes supported by the server. If the class not being found is a problem then throw was done by the caller of the class manager service. If the caller did throw an exception then the application that contains this class may not be properly defined or installed on the server.
User Response: If no exception occurred, ignore the warning. If a subsequent exception occurred, use the Systems Management GUI to display the active applications installed on the server that experienced the exception. If the GUI indicates the class is supported, report the problem to your next level of support or the IBM Support Center.
BBOO0055E | CLASS MANAGER FAILED TO FIND FACTORY FUNCTION string IN
DLL string. |
Explanation: Class Manager failed attempting to get an address for the factory function. This could be caused by improper installation of the class by the application provider.
User Response: For further information on resolving this error, consult the IBM WebSphere Application Server for z/OS Support website at: http:www-3.ibm.com/software/webservers/appserv/zos_os390/support.html This site provides searchable databases of technotes, solutions, and e-fixes. Information on contacting the WebSphere Support team is also provided.
BBOO0056E | CONTEXT SERVICE 'string' FAILED WITH RETURN
CODE=hstring. |
Explanation: WebSphere for z/OS failed in the context service indicated and that service completed with a hexadecimal return code indicated.
User Response: See return codes for context services in the MVS Programming: Resource Recovery book.
BBOO0057W | AUTOMATIC RESTART MANAGER (IXCARM) SERVICE
'string' WARNING/FAILURE, RC=hstring REASON=hstring. |
Explanation: WebSphere for z/OS detected a problem in the automatic restart manager (IXCARM) service indicated and that service completed with a hexadecimal return code indicated by RC and a hexadecimal reason code indicated by REASON.
User Response: See return codes for IXCARM services in the OS/390 MVS Programming: Sysplex Services Reference.
BBOO0058E | THE OPERATION string IS NOT SUPPORTED BY THE DISPATCH
METHOD. |
Explanation: The dispatch method returned indicating that the operation was not executed.
User Response: Ensure that the server is running with a DLL for the class that has a version of the xxxxxxxs_S.cpp file that supports the requested operation.
BBOO0059I | PROXYFACTORY string WAS NOT FOUND. |
Explanation: The WebSphere for z/OS ORB was attempting to create a proxy object for an input class name, but a factory does not exist for that class.
User Response: Check that the application that contains the class name is correctly installed on that server.
BBOO0060I | OBJECT LEVEL TRACE (OLT) DLL WAS LOADED SUCCESSFULLY. |
Explanation: The WebSphere for z/OS OLT DLL was loaded.
User Response: None.
BBOO0061W | The function string+dstring raised an exception
string. Additional data: string. |
Explanation: WebSphere for z/OS identified an abnormal situation for which it raised the indicated CORBA user exception. Additional data related to the exception is also shown.
User Response: See additional messages to determine how WebSphere for z/OS handled the error. See also the explanation for exceptions under the indicated function.
BBOO0062E | COULD NOT LOAD OBJECT LEVEL TRACE DLL. |
Explanation: Object Level Trace was enabled, but the DLL could not be loaded.
User Response: Check the installation and usage information for OLT and ensure the OLT DLL is available.
BBOO0063E | COULD NOT LOCATE OBJECT LEVEL TRACE INIT ROUTINE. |
Explanation: The object level trace (OLT) DLL was loaded but the system could not locate its init routine. OLT could not be started.
User Response: This is an internal programming error. For further information on resolving this error, consult the IBM WebSphere Application Server for z/OS Support website at: http:www-3.ibm.com/software/webservers/appserv/zos_os390/support.html This site provides searchable databases of technotes, solutions, and e-fixes. Information on contacting the WebSphere Support team is also provided.
BBOO0064E | METHODS IN CLASS string CANNOT BE DISPATCHED BY THE
SERVER. |
Explanation: Methods on this class cannot be dispatched because the object was IDL compiled as localonly instead of remotable.
User Response: Recompile your object interface as a remotable object.
BBOO0065W | SHASTA RUNTIME FUNCTIONstringDID NOT FIND
CLASSstring. |
Explanation: The Shasta Runtime was unable to find a class.
User Response: Determine if the desired class name is correct and if it should have been found. For further information on resolving this error, consult the IBM WebSphere Application Server for z/OS Support website at: http:www-3.ibm.com/software/webservers/appserv/zos_os390/support.html This site provides searchable databases of technotes, solutions, and e-fixes. Information on contacting the WebSphere Support team is also provided.
BBOO0066I | SHASTA RUNTIME FUNCTIONstringDETECTED THATstring
string. |
Explanation: The Shasta Runtime detected the condition described in this informational message.
User Response: none
BBOO0067W | SHASTA RUNTIME FUNCTIONstringDETECTED THATstring
string. |
Explanation: The Shasta Runtime detected the condition described in this warning message.
User Response: Determine if this warning message is associated with the occurrence of an exception. If so, investigate the root cause of the exception and correct.
BBOO0068E | Shasta Runtime function string detected that
string string. |
Explanation: The Shasta Runtime detected the condition described in this error message.
User Response: For further information on resolving this error, consult the IBM WebSphere Application Server for z/OS Support website at: http:www-3.ibm.com/software/webservers/appserv/zos_os390/support.html This site provides searchable databases of technotes, solutions, and e-fixes. Information on contacting the WebSphere Support team is also provided.
BBOO0069E | SHASTA RUNTIME FUNCTION string COULD NOT LOAD THE JAVA
IMPLEMENTATION CLASS string FOR CLASS string. |
Explanation: The Shasta Runtime detected an error while attempting to load a Java implementation class.
User Response: For further information on resolving this error, consult the IBM WebSphere Application Server for z/OS Support website at: http:www-3.ibm.com/software/webservers/appserv/zos_os390/support.html This site provides searchable databases of technotes, solutions, and e-fixes. Information on contacting the WebSphere Support team is also provided.
BBOO0070E | SHASTA RUNTIME FUNCTION string COULD NOT FIND THE JAVA
VM DLL string. |
Explanation: The Shasta Runtime could not find the specified DLL for the Java virtual machine.
User Response: Verify that the LIBPATH environment variable specifies the correct path to the Java virtual machine DLL.
BBOO0071E | Shasta Runtime function string failed to establish a JNI
environment. |
Explanation: The Shasta Runtime could not establish function pointers required to enable its Java Native Interface (JNI) environment.
User Response: For further information on resolving this error, consult the IBM WebSphere Application Server for z/OS Support website at: http:www-3.ibm.com/software/webservers/appserv/zos_os390/support.html This site provides searchable databases of technotes, solutions, and e-fixes. Information on contacting the WebSphere Support team is also provided.
BBOO0072E | Shasta Runtime function string detected that the Java VM
was not started. |
Explanation: The Shasta Runtime detected that the Java VM was not loaded and initialized.
User Response: For further information on resolving this error, consult the IBM WebSphere Application Server for z/OS Support website at: http:www-3.ibm.com/software/webservers/appserv/zos_os390/support.html This site provides searchable databases of technotes, solutions, and e-fixes. Information on contacting the WebSphere Support team is also provided.
BBOO0073E | Shasta Runtime function string detected that the
following exception occurred in the Java VM ...JVM E Explanation: The Shasta Runtime has received the given stack trace from the Java VM Programmer response: Analyze the exception from within the Java VM stack trace. Determine if the failing method within the Java VM stack trace was from user code, if it is a user application method correct coding errors and retry application. |
Explanation: The Shasta Runtime has received the given stack trace from the Java VM
User Response: Analyze the exception from within the Java VM stack trace. Determine if the failing method within the Java VM stack trace was from user code, if it is a user application method correct coding errors and retry application.
BBOO0074E | INCORRECT MODIFY COMMAND. |
Explanation: An incorrect modify command was entered from the operator console.
User Response: Re-enter the modify command. Issue F <JOBNAME>,CANCEL,ARMRESTART if an ARM restart of the address space is necessary, or F <JOBNAME>,CANCEL to cancel the address space.
BBOO0075E | UNABLE TO SCHEDULE WORK, WLM APPLICATION ENVIRONMENT
string HAS STOPPED. |
Explanation: An attempt was made to schedule work using the WLM application environment specified, however the application environment was stopped.
User Response: Determine why the application environment has stopped and if the problem which stopped it has been resolved. Restart it using the V WLM command.
BBOO0076E | Daemon asynchio routine failed with RV=dstring,
RC=dstring, RSN=hstring, [string]. |
Explanation: WebSphere for z/OS daemon processing detected an error during asynchio processing. Asynchio processing failed with a decimal return value indicated by RV, a decimal return code indicated by RC, and a hexadecimal reason code indicated by REASON.
User Response: See the OS/390 C++ Run-Time Library Reference or the OS/390 OpenEdition Messages and Codes for descriptions of the returned value and codes.
BBOO0077I | WEBSPHERE FOR Z/OS SERVANT PROCESS string HAS BEEN
RECYCLED. |
Explanation: The servant process identified has been stopped and another servant process of the same type will be started. This allowed the system to reclaim resources that might have been leaked. How frequently the servant process is recycled (if at all) is controlled by the system administrator.
User Response: None. Active transactions are completed before the space is recycled. The programmer should not see the results of this administrative action.
BBOO0078E | WEBSPHERE FOR Z/OS SERVANT PROCESS string CAN NOT BE
RECYCLED. |
Explanation: The servant process has attempted to recycle itself to reclaim storage. It has attempted to call WLM to perform the recycle function but received a return code that indicates that the function can not be done.
User Response: None.
BBOO0079E | Internal failure, REASON=hstring, RC=dstring,
EXTENDED REASON=hstring. |
Explanation: WebSphere for z/OS failed with an internal error.
User Response: See the WebSphere for z/OS Error Codes section of this book for a description of this error. For further information on resolving this error, consult the IBM WebSphere Application Server for z/OS Support website at: http:www-3.ibm.com/software/webservers/appserv/zos_os390/support.html This site provides searchable databases of technotes, solutions, and e-fixes. Information on contacting the WebSphere Support team is also provided.
BBOO0080W | The string value of string from the environment
file has an invalid character at position dstring. Error logging will be directed to CERR. |
Explanation: The LOGSTREAM value in the environment file has the following restrictions: 1. A logstream name is made up of 1 or more qualifiers separated by periods, up to the maximum of 26 characters 2. Each qualifier can contain up to 8 numeric, alphabetic, or national (, or haracaters. 3. The first character of each qualier must be an alphabetic or national character. 4. Each qualifier must be separated by periods which you must count as characters.
User Response: Value is ignored. If you wish to use the value, fix it in the environment file and restart the WebSphere daemon address space.
BBOO0081W | The logstream name in the Systems Management configuration does
not match the value of the LOGSTREAMNAME environment variable. The Systems Management configuration value, string, is being used. |
Explanation: The logstream name is retrieved from the Systems Management configuration if it is available. This message is issued to notify the user that changing the LOGSTREAMNAME environment variable will not affect where the output is written. Use the Systems Management Administration tool to modify the logstream being used. Remaining characters must be alphanumeric
User Response: None.
BBOO0082E | System Logger service string for stream string
returned with failure - RC=hstring, RSN=hstring. Error logging will be directed to CERR. |
Explanation: During the invocation of the specified system logger service, an error was encountered. The error is indicated by the hexadecimal return code and reason code.
User Response: Consult the function indicated in OS/390 MVS Programming: Assembler Services Reference, OS/390 MVS Programming: Authorized Assembler Services Reference, or other appropriate OS/390 reference book for a description of this error.
BBOO0083E | Input to program BBORBLOG specifies incorrect input parameter.
A stream name must be supplied. |
Explanation: The user did not specify a proper system logger stream name as the first parameter to the indicated program.
User Response: Rerun the program specifying the appropriate input.
BBOO0084E | Input to program BBORBLOG specifies stream name of incorrect
length. Length must be <=26 characters. |
Explanation: The user did not specify a proper system logger stream name as the first parameter to the indicated program. Length must be less than or equal to 26 characters in length.
User Response: Rerun the program specifying the appropriate input.
BBOO0085E | Input to program BBORBLOG specifies incorrect format option. Valid format options are 80 and NOFORMAT. |
Explanation: The user did not specify a proper format option as the second parameter to the indicated program. Valid format option values are 80 and NOFORMAT.
User Response: Rerun the program specifying the appropriate input.
BBOO0086E | Program BBORBLOG encountered an error opening file associated
with DD:BBOLOG. |
Explanation: Error occurred attempting to open the log stream browse file.
User Response: Verify that the data set exists and is valid.
BBOO0087E | Program BBORBLOG encountered error during invocation of system
logger service string. Service returned with - RC=hstring, RSN=hstring. |
Explanation: During the invocation of the specified system logger service, an error was encountered. The error is indicated by the hexadecimal return code and reason code.
User Response: Consult the function indicated in OS/390 MVS Programming: Assembler Services Reference, OS/390 MVS Programming: Authorized Assembler Services Reference, or other appropriate OS/390 reference book for a description of this error.
BBOO0088E | Program BBORBLOG encountered an error writing to file associated
with DD:BBOLOG. |
Explanation: Error occurred while writing to the log stream browse file.
User Response: Verify that the data set exists and is valid.
BBOO0089E | Program BBORBLOG terminated due to errors. Browse file output
may be truncated. |
Explanation: Error occurred in program BBORBLOG while processing a log stream. Output contained in the generated browse file may be incomplete.
User Response: Correct the error reported by error message issued previous to this message and rerun the browser program.
BBOO0090E | Connect failed to log stream string. Log stream BLKSIZE
dstring is less than allowed minimum of 255. |
Explanation: The log stream was not created with the required minimum BLKSIZE of 255. Error logging will be directed to CERR.
User Response: Have the installation redefine the log stream to conform to the IBM recommended range of 255 to 4096.
BBOO0091E | Server alias string not found in the Implementation
Repository. |
Explanation: CORBA::ImplRepository::find_impldef_by_alias was invoked to find a ImplementationDef for the input server alias but the server alias was not found in the implementation repository.
User Response: Ensure that the server is started before invoking CORBA::ImplRepository::find_impldef_by_alias.
BBOO0092E | implid string not found in the Implementation
Repository. |
Explanation: CORBA::ImplRepository::find_impldef was invoked to find a ImplementationDef for the input implid but the implid was not found in the implementation repository.
User Response: Ensure that the server is started before invoking CORBA::ImplRepository::find_impldef.
BBOO0093E | WEBSPHERE FOR Z/OS DAEMON NOT FOUND BY SERVER
string. |
Explanation: WebSphere server address spaces can not start without an active WebSphere Daemon on the same system. The server which attempted to start was unable to locate a Daemon on this system and will terminate in error.
User Response: Start the WebSphere for z/OS Daemon on this system prior to starting other WebSphere for z/OS servers.
BBOO0095E | WEBSPHERE FOR Z/OS DAEMON FAILED TO INITIALIZE BECAUSE ANOTHER
DAEMON WAS STARTING. |
Explanation: An attempt was made to start a WebSphere for z/OS Daemon while another WebSphere for z/OS Daemon of the same name was also starting. Only one WebSphere for z/OS Daemon of a given name can be active on a system at one time. This Daemon terminates in error.
User Response: Do not attempt to start two WebSphere for z/OS Daemons with the same name on the same system at the same time.
BBOO0100E | WEBSPHERE FOR Z/OS CONTROL PROCESS string FAILED TO
INITIALIZE BECAUSE ANOTHER CONTROL PROCESS OF THE SAME NAME WAS STARTING. |
Explanation: An attempt was made to start a WebSphere for z/OS Control process while another control process of the same specific server name was also starting. Only one Control process of a given specific server name can be active at one time.
User Response: Do not attempt to start two Control processes with the same specific server name at the same time.
BBOO0101E | WEBSPHERE FOR Z/OS CONTROL PROCESS string FAILED TO
INITIALIZE BECAUSE ANOTHER CONTROL PROCESS OF THE SAME NAME WAS ACTIVE. |
Explanation: An attempt was made to start a WebSphere for z/OS Control process while another control process of the same specific server name was active. Only one Control process of a given specific server name can be active at one time.
User Response: Do not attempt to start two Control processes with the same specific server name at the same time.
BBOO0102W | WEBSPHERE FOR Z/OS UNEXPECTED DELAY WAITING FOR START OF SERVER
string. |
Explanation: When WebSphere automatically starts another WebSphere server, it waits for the server to initialize before it continues. After a significant portion of the configured server_start_wait_for_initialization_Timeout has elapsed, this messages is issued to indicate this condition. WebSphere will continue to wait and will issue a subsequent warning message as the processing time approaches the configured timeout.
User Response: The system may be slow or there may be a problem which is preventing the indicated server from starting. You may be able to determine the cause of the problem and correct it before the timeout expires.
BBOO0103W | WEBSPHERE FOR Z/OS WAITING FOR START OF SERVER string,
SECOND WARNING. |
Explanation: When WebSphere automatically starts another WebSphere server, it waits for the server to initialize before it continues. After a significant portion of the configured server_start_wait_for_initialization_Timeout has elapsed, this messages is issued to indicate this condition. WebSphere will continue to wait and will issue a subsequent error message if the configured timeout expires.
User Response: The system may be slow or there may be a problem which is preventing the indicated server from starting. You may be able to determine the cause of the problem and correct it before the timeout expires.
BBOO0104E | WEBSPHERE FOR Z/OS WAITING FOR START OF SERVER string HAS
TIMED OUT. |
Explanation: When WebSphere automatically starts another WebSphere server, it waits for the server to initialize before it continues. This message is issued when the configured server_start_wait_for_initialization_Timeout has expired. WebSphere will give up waiting and may throw exceptions and terminate other processing that required this server to start.
User Response: The system may be slow or there may be a problem which is preventing the indicated server from starting. You should attempt to determine what caused the delay, correct the problem, and try again or change the server_start_wait_for_initialization_Timeout property to a value more appropriate for your environment.
BBOO0105E | WEBSPHERE FOR Z/OS CONTROL PROCESS string PROGRAM
string PPT ENTRY string IS NOT SPECIFIED. |
Explanation: This PPT entry must be specified to run the program.
User Response: Make sure the PPT requirements are correct. Verify the SCHEDxx PARMLIB member has been properly modified as directed in the WebSphere for z/OS Installation and Customization Guide.
BBOO0106E | WEBSPHERE FOR Z/OS CONTROL PROCESS string PROGRAM
string PPT ENTRY string SHOULD NOT BE SPECIFIED. |
Explanation: This PPT entry should not be specified to run the program.
User Response: Make sure the PPT requirements are correct. Verify the SCHEDxx PARMLIB member has been properly modified as directed in the WebSphere for z/OS Installation and Customization Guide.
BBOO0107E | WEBSPHERE FOR Z/OS CONTROL PROCESS string PROGRAM
string PPT ENTRY string IS SPECIFIED INCORRECTLY. |
Explanation: This entry is specified incorrectly to run the program.
User Response: Make sure the PPT requirements are correct. Verify the SCHEDxx PARMLIB member has been properly modified as directed in the WebSphere for z/OS Installation and Customization Guide.
BBOO0108E | WEBSPHERE FOR Z/OS PROGRAM string PPT ENTRY
string IS NOT SPECIFIED. |
Explanation: This PPT entry must be specified to run the program.
User Response: Make sure the PPT requirements are correct. Verify the SCHEDxx PARMLIB member has been properly modified as directed in the WebSphere for z/OS Installation and Customization Guide.
BBOO0109E | WEBSPHERE FOR Z/OS PROGRAM string PPT ENTRY
string SHOULD NOT BE SPECIFIED. |
Explanation: This PPT entry should not be specified to run the program.
User Response: Make sure the PPT requirements are correct. Verify the SCHEDxx PARMLIB member has been properly modified as directed in the WebSphere for z/OS Installation and Customization Guide.
BBOO0110E | WEBSPHERE FOR Z/OS PROGRAM string PPT ENTRY
string IS SPECIFIED INCORRECTLY. |
Explanation: This entry is specified incorrectly to run the program.
User Response: Make sure the PPT requirements are correct. Verify the SCHEDxx PARMLIB member has been properly modified as directed in the WebSphere for z/OS Installation and Customization Guide.
BBOO0111E | Attempt to dispatch method string of class
string encountered uncaught system exception string. |
Explanation: During dispatch of a method, WebSphere ORB, caught a system exception.
User Response: Contact the provider of the class indicated in the message to assist with problem determination. The application provider could be IBM, the customer, or other vendors of WebSphere applications.
BBOO0112E | Attempt to dispatch method string of class
string encountered uncaught user exception string. |
Explanation: During dispatch of a method, WebSphere ORB, caught a user exception.
User Response: Contact the provider of the class indicated in the message to assist with problem determination. The application provider could be IBM, the customer, or other vendors of WebSphere applications.
BBOO0113E | Attempt to dispatch method string of class
string encountered uncaught throw. |
Explanation: During dispatch of a method, WebSphere for z/OS ORB, caught something other than a system or user exception.
User Response: Contact the provider of the class indicated in the message to assist with problem determination. The application provider could be IBM, the customer, or other vendors of WebSphere for z/OS applications.
BBOO0114W | Program BBORBLOG encountered error trying to browse logstream.
Logstream is empty. |
Explanation: The logstream being browsed contains no data.
User Response: Verify the logstream name.
BBOO0115E | Program BBORBLOG encountered error trying to connect to logstream. User does not have READ access to logstream. |
Explanation: The user trying to browse the logstream does not have READ access to the logstream.
User Response: Issue the appropriate RACF commands to give the user READ access to the logstream.
BBOO0116E | Program BBORBLOG encountered error trying to connect to log
stream. The log stream specified has not been defined. |
Explanation: The log stream name specified has not been defined in the LOGR policy.
User Response: Ensure that the required log stream name has been defined in the LOGR policy.
BBOO0117E | Function string for host ip_addr string failed
with RV=dstring, RC=dstring, RSN=hstring, [string] |
Explanation: WebSphere for z/OS issued the indicated function and that function completed with a decimal return value indicated by RV, a decimal return code indicated by RC, and a hexadecimal reason code indicated by RSN.
User Response: See the OS/390 C++ Run-Time Library Reference or the UNIX System Services Messages and Codes for descriptions of the returned value and codes.
BBOO0118E | Function string for hostname string failed with
RV=dstring, RC=dstring, RSN=hstring, [string] |
Explanation: WebSphere for z/OS issued the indicated function and that function completed with a decimal return value indicated by RV, a decimal return code indicated by RC, and a hexadecimal reason code indicated by RSN.
User Response: See the OS/390 C++ Run-Time Library Reference or the UNIX System Services Messages and Codes for descriptions of the returned value and codes.
BBOO0119S | COULD NOT BUILD PROXY FOR CLASS string |
Explanation: A call to create_proxy returned a NULL
User Response: Ensure that the DLL for the class is in the steplib or linklist
BBOO0120E | LOCATE REQUEST FAILED FOR SERVER - string. |
Explanation: A Locate request to a daemon failed because a target server could not be found. If WebSphere for z/OS can determine the target generic server name, this server name will appear in the above text. Otherwise the server name will appear as the name 'unknown'.
User Response: Please ensure that the target server is initialized.
BBOO0121E | GIOP reply message with RequestID = hstring was received
for which no corresponding request could be found. |
Explanation: GIOP reply message was received, but no corresponding request could be found.
User Response: For further information on resolving this error, consult the IBM WebSphere Application Server for z/OS Support website at: http:www-3.ibm.com/software/webservers/appserv/zos_os390/support.html This site provides searchable databases of technotes, solutions, and e-fixes. Information on contacting the WebSphere Support team is also provided.
BBOO0122E | NULL ENTRY IN TABLE WHEN LOOKING UP CLASSNAME
string |
Explanation: Found NULL when looking up classname in ptable in encode_objref()
User Response: For further information on resolving this error, consult the IBM WebSphere Application Server for z/OS Support website at: http:www-3.ibm.com/software/webservers/appserv/zos_os390/support.html This site provides searchable databases of technotes, solutions, and e-fixes. Information on contacting the WebSphere Support team is also provided.
BBOO0123E | VALUE SPECIFIED FOR ORBID PARAMETER IS NOT VALID |
Explanation: The value specified to the ORB_init() function for the ORBid keyword must be BOSS. No other value is accepted.
User Response: Specify a valid value for ORBid
BBOO0124E | NO VALUE SPECIFIED FOR ORBID KEYWORD |
Explanation: The ORBid keyword to ORB_init() must be specified with a value.
User Response: Specify a valid value for ORBid
BBOO0125E | NO VALUE SPECIFIED FOR ORBSRVNAME KEYWORD |
Explanation: The ORBsrvname keyword to ORB_init() must be specified with a value.
User Response: Specify a valid value for ORBsrvname
BBOO0126E | NO VALUE SPECIFIED FOR ORBTYPE KEYWORD |
Explanation: The ORBType keyword to ORB_init() must be specified with a value.
User Response: Specify a valid value for ORBType
BBOO0127E | LOAD FAILED FOR MODULE string |
Explanation: During initialization of a WebSphere for z/OS server, an attempt was made to load the product module whose name is in the message text. The load module was not found. The server terminates. The load module should be in the search path for this server (STEPLIB, LPA, or Linklist).
User Response: Determine where the load module is and whether it should be in a STEPLIB, LPA or Linklist, correct the problem and restart the server
BBOO0128E | WEBSPHERE FOR Z/OS UNABLE TO LOCATE RRS |
Explanation: The RRS address space must be up and initialized for WebSphere for z/OS servers to start. Initialization for this server was unable to locate RRS. The server terminates. Make sure RRS is active and fully initialized before starting WebSphere for z/OS servers.
User Response: Make sure RRS is started and restart the server
BBOO0129E | VALUE SPECIFIED FOR ORBCBI KEYWORD IS NOT VALID |
Explanation: The ORBCBI keyword to ORB_init() must be specified with a valid value (one of COLD, WARM, or HOT).
User Response: Specify a valid value for ORBCBI
BBOO0130E | NO VALUE SPECIFIED FOR ORBCBI KEYWORD |
Explanation: The ORBCBI keyword to ORB_init() must be specified with a value (one of COLD, WARM, or HOT).
User Response: Specify a valid value for ORBCBI
BBOO0131W | ERROR ENCOUNTERED DURING DAEMON ATTEMPT TO STOP SERVER
string. |
Explanation: A Stop command was entered for the WebSphere for z/OS Daemon which in turn stops the Systems Management server on the system with the Daemon since the Daemon is required for the other servers to function. In issuing the stop for the Systems Management server an error was encountered.
User Response: Either the named server has simply already ended in which case no action is required or there is some problem with the server which may require you to cancel it to allow the stop of the Daemon to complete. Look for the server whose specific server name is given in the message to determine which case it may be. Specific server name is a parameter provided to the server when it is started.
BBOO0132I | OTHER WEBSPHERE FOR Z/OS SERVERS HAVE STOPPED, STOP OF DAEMON
CONTINUES. |
Explanation: When a Stop command is issued for the WebSphere for z/OS Daemon the Daemon stops the Systems Management server on this system since the Daemon is required for it to function. The Daemon waits for the Systems Management Sever to stop before continuing to shut down himself. This message indicates that Systems Management Sever is down and that Daemon will now continue to its own termination.
User Response: None.
BBOO0133I | WEBSPHERE FOR Z/OS STOP COMMAND ISSUED FOR SERVER
string. |
Explanation: The modified MVS Stop command has been issued against a WebSphere for z/OS address space.
User Response: None.
BBOO0134I | WEBSPHERE FOR Z/OS CANCEL,ARMRESTART COMMAND ISSUED FOR SERVER
string. |
Explanation: The MVS Modify command has been issued to cancel a WebSphere for z/OS address space requesting ARM restart.
User Response: None.
BBOO0136E | UNABLE TO START SERVER string BECAUSE WEBSPHERE FOR Z/OS
DAEMON IS STOPPING |
Explanation: A Stop command has been issued for the WebSphere Daemon and other servers are are in the process of being stopped as part of Daemon termination. No other servers can start while the Daemon is terminating.
User Response: Once the Daemon has stopped and has, if desired, been restarted, you may try again to start this server.
BBOO0137W | An 0D6 Abend occurred. The target PC is no longer valid. |
Explanation: The address space for where the PC was targeted has ended. This is an informational message.
User Response: None.
BBOO0138W | WEBSPHERE FOR Z/OS UNEXPECTED DELAY WAITING FOR STOP OF SERVER
string. |
Explanation: When WebSphere automatically stops another WebSphere server during warm start, it waits for the server to come down before it continues. After the first timeout has elapsed, this message will be issued to indicate that more time has passed waiting for this server to stop than seems reasonable. WebSphere will continue to wait and will issue a subsequent warning message after the second timeout has expired.
User Response: The system may be slow or there may be a long running transaction on the indicated server which is preventing the server from stopping. You may be able to determine the problem and allow the server to stop before the timeout expires.
BBOO0139W | WEBSPHERE FOR Z/OS WAITING FOR STOP OF SERVER string,
SECOND WARNING. |
Explanation: When WebSphere automatically stops another WebSphere server during warm start, it waits for the server to come down before it continues. After the second timeout has elapsed, this message will be issued to indicate that more time has passed waiting for this server to stop than seems reasonable. WebSphere will continue to wait and will issue a subsequent error message after the third timeout has expired indicating that we have given up waiting for this server to stop.
User Response: The system may be slow or there may be a long running transaction on the indicated server which is preventing the server from stopping. You may be able to determine the problem and allow the server to stop before the timeout expires.
BBOO0140E | WEBSPHERE FOR Z/OS WAITING FOR STOP OF SERVER string HAS
TIMED OUT. |
Explanation: When WebSphere automatically stops another WebSphere server during warm start, it waits for the server to come down before it continues. After the three timeouts have elapsed, this message will be issued to indicate that more time has passed waiting for this server to stop that seems reasonable. WebSphere will give up waiting and may throw exceptions and terminate other processing that required this server to stop.
User Response: The system may be slow or there may be a long running transaction on the indicated server which is preventing the server from stopping. Retry the warm start when there is less load on the system and/or server.
BBOO0141E | Class/method string not implemented. |
Explanation: The indicated class contains the indicated method, which is not implemented.
User Response: Do not call this method for an instance of an object of this class.
BBOO0142E | Socket bind() for Server=string to Port=dstring
failed with RV=dstring, RC=dstring, RSN=hstring , [string]. |
Explanation: WebSphere for z/OS issued the bind function and that function completed with a decimal return value indicated by RV, a decimal return code indicated by RC, and a hexadecimal reason code indicated by RSN.
User Response: See the OS/390 eNetwork Communication Server books for descriptions of the returned value and codes.
BBOO0143I | ARM REGISTRATION FAILED - ARM NOT ACTIVE ON THIS SYSTEM |
Explanation: WebSphere for z/OS always trys to register with OS/390 ARM (automatic restart manager), during the start of a recoverable address space ARM indicated that it was either not installed or not configured.
User Response: No action is required. However if you desire or require ARM services you should review your ARM definitions to ensure that you have configured it correctly.
BBOO0144I | ARM DETECTED A FAILURE AND IS RESTARTING THIS SERVER |
Explanation: When ARM detects a failure it will restart the server. This message is informing you that an ARM restart is occurring.
User Response: No action is required. This message is just informational and may assist in debugging restart error scenarios.
BBOO0145E | ARM REGISTRATION FAILED - ARM COUPLE DATASET FULL |
Explanation: During registration with ARM the ARM couple dataset has become full. The ARM registration fails and the server continues to come up.
User Response: Because WebSphere for z/OS has several address spaces registering with ARM you may not have defined the ARM couple dataset large enough to handle all of the ARM registrations. You should consult the ARM documentation and increase the size of the ARM couple dataset.
BBOO0146I | ARM REGISTRATION FAILED - ARM DETECTED A DUPLICATE NAME |
Explanation: During registration with ARM the name used was already registered somewhere else in the sysplex. The server continues to come up.
User Response: No action is required. However if you desire or require ARM services you should review your WebSphere for z/OS server names to ensure that they are unique in a sysplex. In a non-datasharing sysplex where more than one WebSphere for z/OS image is started ARM cannot be used.
BBOO0147I | ARM READY FAILED - ARM TIMEOUT EXCEEDED |
Explanation: WebSphere for z/OS issued the ARM READY call and ARM waited the amount of time defined in the ARM policy. The registered server did not become ready before the timeout expired. The server continues to come up and may experience additional errors due to its dependent servers not being ready.
User Response: In general you should investigate what is causing the address spaces not to become ready. Alternatively you can review your ARM policy and increase the timeout values.
BBOO0148W | ARM READY FAILED - SERVER NOT REGISTERED |
Explanation: WebSphere for z/OS issued the ARM READY call but the server had not been registered before. Activation failed. The server continues to come up and may experience additional errors due to its dependent servers not being ready.
User Response: In general you should investigate what is causing the address spaces not being registered
BBOO0149I | ARM WAITPRED FAILED - ARM TIMEOUT EXCEEDED |
Explanation: WebSphere for z/OS issued the ARM WAITPRED call and ARM waited the amount of time defined in the ARM policy. The dependent server did not become ready before the timeout expired. The server will continue to come up and may experience additional errors due to its dependent servers not being ready.
User Response: In general you should investigate what is causing the dependent server not to become ready. Alterntatively you can review your ARM policy and increase the timeout values.
BBOO0150E | COMMAND IGNORED, STOP COMMAND ALREADY ISSUED FOR SERVER
string |
Explanation: The MVS STOP console command or the System Managment EUI STOP command has already been issued for this server. Subsequent commands are ignored.
User Response: Wait for the current stop processing to complete or escalate to an EUI Cancel or MVS console Modify Cancel command.
BBOO0151E | COMMAND IGNORED, MODIFY CANCEL COMMAND ALREADY ISSUED FOR SERVER
string |
Explanation: The MVS Modify Cancel console command or the System Managment EUI Cancel command has already been issued for this server. Subsequent commands are ignored.
User Response: Wait for the current cancel processing to complete
BBOO0152E | STOP AND MODIFY COMMANDS ARE NOT SUPPORTED FOR WEBSPHERE FOR Z/OS
SERVANT PROCESSES |
Explanation: The MVS Stop and Modify commands are not supported by servant processes. You may shut down servant processes either by stopping their owning control process or through the use of the VARY WLM command.
User Response: The command is ignored, consider one of the alternatives described in the Explanation.
BBOO0153I | THE FOLLOWING NUMBER OF MESSAGES WERE WRITTEN TO CERR PRIOR TO
CONNECTING TO LOGSTREAM: dstring. |
Explanation: Before WebSphere could successfully connect to the log stream there were a number of messages to be recorded which had to be redirected to CERR.
User Response: Check job log for messages.
BBOO0154E | WEBSPHERE FOR Z/OS DAEMON string UNABLE TO RUN
AUTHORIZED |
Explanation: WebSphere for z/OS Daemon and Control process must run authorized. However, the space has detected that it is not. The space ends in error.
User Response: The most probable cause of this is a dataset in the Steplib for the proc that is not in the APF list or the PPT settings for the load module(bbodaemn) should be verified to be set and contain the settings from the BBOSCHED member of the CNTL dataset generated from the Customization Dialogs as documented by the customized instructions, BBOINSTR, for updating SCHEDxx member in SYS1.PARMLIB
BBOO0155E | WEBSPHERE FOR Z/OS CONTROL PROCESS string UNABLE TO RUN
AUTHORIZED |
Explanation: WebSphere for z/OS Daemon and Control process must run authorized. However, the space has detected that it is not. The space ends in error.
User Response: The most probable cause of this is a dataset in the Steplib for the procedure that is not in the APF list or the PPT settings for the load module(bboctl) should be verified to be set and contain the settings from the BBOSCHED member of the CNTL dataset generated from the Customization Dialogs as documented by the customized instructions, BBOINSTR, for updating SCHEDxx member in SYS1.PARMLIB
BBOO0156I | CONTINUATION dstring FOR string ON
TCB=hstring |
Explanation: A message was issued that requires more than 10 lines. This message is issued to continue displaying the data for the indicated message 9 lines at a time.
User Response: None.
BBOO0157E | JVM EXIT API DRIVEN. JVM EXITING WITH
CODE=dstring |
Explanation: JVM exit API has been driven with the specified error code, indicating that the JVM is ending abnormally.
User Response: Look for other accompanying error messages in the error log
BBOO0158E | JVM ABORT API DRIVEN. JVM ABORTING. |
Explanation: JVM abort API has been driven.
User Response: Look for other accompanying error messages in the error log.
BBOO0159E | Thread Type (dstring) string. |
Explanation: Threads of a type restarted 5 or more times.
User Response: None.
BBOO0160E | Function string failed with RV=dstring,
RC=dstring, RSN=hstring, [string] hostname/ip: string |
Explanation: WebSphere for z/OS issued the indicated function and that function completed with a decimal return value indicated by RV, a decimal return code indicated by RC, and a hexadecimal reason code indicated by RSN.
User Response: See the OS/390 C++ Run-Time Library Reference or the UNIX System Services Messages and Codes for descriptions of the returned value and codes.
BBOO0161E | Function string failed with RV=dstring,
RC=dstring, RSN=hstring, [string] hostname/ip: string port: dstring |
Explanation: WebSphere for z/OS issued the indicated function and that function completed with a decimal return value indicated by RV, a decimal return code indicated by RC, and a hexadecimal reason code indicated by RSN.
User Response: See the OS/390 C++ Run-Time Library Reference or the UNIX System Services Messages and Codes for descriptions of the returned value and codes.
BBOO0162W | LOAD FAILED FOR MODULE string. |
Explanation: During initialization of a WebSphere for z/OS server or client, an attempt was made to load the product module whose name is in the message text. The load module was not found. The server or client continues. The load module should be in the search path (STEPLIB, LPA, or Linklist).
User Response: Determine where the load module is and whether it should be in a STEPLIB, LPA or Linklist, correct the problem and restart the server or client.
BBOO0163W | FAILED TO FIND string FUNCTION IN MODULE
string. |
Explanation: Failed attempting to get an address for the function. The load module does not contain the function.
User Response: Determine where the load module is being loaded from and ensure that it is the correct version. Correct the problem and restart the server or client.
BBOO0164W | Function string failed with RC=dstring. System
determined REASON=string |
Explanation: WebSphere for z/OS failed as indicated and that function completed with a decimal return code indicated by RC. The first 'string' is the name of the function that failed. The second 'string' indicates the reason as to why it failed.
User Response: Consult the function in the OS/390 C++ Library Reference, or other appropriate OS/390 reference book for a description of this error. Correct the problem.
BBOO0165E | ARM REGISTRATION FAILED - TIMEOUT |
Explanation: ARM registration failed with a return code of 8 and a reason code of 5B8. This means that it took too long to restart and ARM gave up. Will continue to start, but are now not registered with ARM.
User Response: If you want the server which issued this message to be restarted by ARM in the event of a failure, then you must stop and restart it.
BBOO0166E | WEBSPHERE FOR Z/OS CONTROL PROCESS string NOT FOUND BY
SERVANT PROCESS. |
Explanation: WebSphere for z/OS servant process address spaces can not start without the Control process they are associated with being active on the same system. The server which attempted to start was unable to its owning Control process whose name is given in the message text. The servant process terminates.
User Response: This can happen either because the servant process was started as the owning Control process was ending or because the servant process was started manually instead of allowing WLM to start it and the input parameters were incorrect or the server was started on the wrong system. In the case of the owning Control process terminating, this error is normal and can be ignored. If servant processes are being started manually, check that the input parameters correspond to an active control process and that the servant process was started on the same system as the control process which owns it. Note that servant processes should only be started manually when running in WLM compatability mode.
BBOO0167E | Servant process could not send request/response because length
of message (dstring) exceeded maximum (dstring). |
Explanation: The size of the response to be sent from the servant process back to the client exceeded the maximum length for local IIOP messages.
User Response: Try sending a smaller message.
BBOO0168W | Unable to return response string to method
string request from string |
Explanation: WebSphere for z/OS experienced a communications error attempting to send a response to a client. The first string describes the response type (NO_EXCEPTION, USER_EXCEPTION, LOCATION_FORWARD, or SYSTEM_EXCEPTION). If the response type is SYSTEM_EXCEPTION then the string also includes the exception type and minor code. The second string is the method name in the request for which a response was unable to be sent. The third string is host name and port number of the client for clients using TCP/IP. For a local client, this string contains the jobname and asid of the client address space.
User Response: This message is provided to document that the server was unable to respond to a client. This may be because the client has gone away, but it may also result in a client that is in a hang waiting for a response. This message provides you with the information needed to identify the problem in the event a client appears hung and wants to know if the server has failed trying to respond to a request.
BBOO0169W | Returning response string to method string
request from string |
Explanation: WebSphere for z/OS is returning a system exception in a response to a client. The first string describes the exception type and minor code. The second string is the method name in the request. The third string is the host name and port number of the client for clients using TCP/IP. For a local client, this string contains the jobname and ASID of the client address space.
User Response: This message simply serves to document that a system exception was returned to a particular client. In the event the client reports a problem, the error log could be searched using the client's hostname to find if a system exception was returned which may be related to the reported problem.
BBOO0170E | CEE3DMP FAILED WITH MESSAGE NUMBER:
dstring |
Explanation: Signal handler invoked CEE3DMP which failed.
User Response: See CEE3DMP documentation for a description of the message number. Most of the time an invalid option was specified on the BBODUMP_CEE3DMP_OPTIONS environment variable.
BBOO0171I | WEBSPHERE FOR Z/OS CONTROL PROCESS string NOT STARTING
ON CONFIGURED SYSTEM string |
Explanation: Each control process is configured to run on a specific system in the sysplex. If a control process is started on a different system than it is configured to run on, then it is assumed to be attempting to release locks and resolve in doubt work caused by a failure of the system on which this control process normally runs. After that work is complete, the control process will automatically terminate.
User Response: If the control process is being started on a system other than where it is configured due to a failure of the configured system, as described above, then no action is required and the control process will terminate as described. If there is no such work to do, then the control process will simply terminate. If you are trying to start the control process to handle work, you need to start it on the configured system or configure another instance of the control process to run on this system. Changing the system where a control process is configured to run can be dangerous as the configured system name is part of the RRS Resource Manager Name and shouldn't change.
BBOO0172I | WEBSPHERE FOR Z/OS SERVANT PROCESS string NOT STARTING
ON CONFIGURED SYSTEM string |
Explanation: Each control process is configured to run on a specific system in the sysplex. When a control process is started out-of-place it attempts to release locks and resolve in doubt work caused by a failure of the system on which it usually runs. It is not expected that a servant process would need to be started to do this processing, however servant processes are not prohibited from starting. This message is is issued simply to note the fact that one started.
User Response: None
BBOO0173I | SERVER string/string ACTIVE ON string
AT LEVEL stringstring |
Explanation: This message is the response to the operator modify display command. The first two fill-in strings are the generic and specific server name for the server. The third fill-in string is the system name where the server is active. The fourth fill-in string is the IBM internal name for the code level the server is running. The fifth and final fill-in may contain text indicating that the server is running on a system where it is not configured to run in order to perform resource recovery. If that is not the case, the fifth fill-in string will be blank.
User Response: None
BBOO0174E | TOO MANY SPECIFIC TRACE POINTS HAVE BEEN SPECIFIED |
Explanation: Only a limited number (presently 100)of specific trace points may be turned on. More than that have been specified. This and any future specific trace points specified will not be activated.
User Response: Restart the control process or use the TRACENONE option to clear the specific trace points and start over.
BBOO0175E | OPEN PARENTHESIS FOUND WITHOUT CLOSE PARENTHESIS |
Explanation: Processing the TRACESPECIFIC option an open parenthesis was found indicating a list of trace points follows. However, no close parenthesis was found to indicate the end of the list.
User Response: Retry setting the trace value using a right parenthesis to close the list.
BBOO0176E | TRACE POINT IDENTIFIER LENGTH INCORRECT |
Explanation: All trace points specified to TRACESPECIFIC must be eight digits long. End of data, a comma, or a close parenthesis was found before the final digit of a trace point was found.
User Response: Ensure all trace points specified contain eight hex digits.
BBOO0177E | TRACE POINT IDENTIFIER CONTAINS NON-HEXADECIMAL VALUES |
Explanation: All trace points specified to TRACESPECIFIC must be in hexadecimal. A non-hexadecimal value (i.e. not 0-9,A-F) was found processing a trace point value.
User Response: Ensure all trace points specified contain eight valid hex digits.
BBOO0178I | THE COMMAND string MAY BE FOLLOWED BY ONE OF THE
FOLLOWING KEYWORDS: |
Explanation: In response to a Modify or Display command requesting help with the syntax, this message is issued followed by the following message which lists all the valid keywords which may be placed at this point in the command.
User Response: None
BBOO0179I | string - string |
Explanation: This message is issued repeatedly in response to a Modify or Display command requesting help with the syntax. Each occurance identifies a valid keyword which may be issued at this point in the command.
User Response: None
BBOO0180E | THE FINAL KEYWORD OF THE COMMAND string IS NOT
RECOGNIZED, ALLOWABLE VALUES ARE: |
Explanation: The last keyword specified in the command shown is unrecognized. A list of valid keywords will be shown in messages following this one.
User Response: Issue the command again using a valid keyword
BBOO0181E | KEYWORDS FOR THE DISPLAY COMMAND MUST BE SEPARATED FROM THE
COMMAND BY A COMMA |
Explanation: The display command takes numerous options which are separated from the display keyword by commas.
User Response: Issue the command again with a comma following the 'display' keyword.
BBOO0182I | SERVER ASID SYSTEM LEVEL |
Explanation: This message acts as a header for the response to the DISPLAY,SERVERS command.
User Response: None
BBOO0183I | string/string %4Xx string
string |
Explanation: This message repeats in response to the DISPLAY,SERVERS command, once per active server. The columns, as shown in the header, indicate the generic and specific server names, the ASID (in hex) of the server control process, the system name where the server is active, and the code level of the server.
User Response: None
BBOO0184I | SERVER string/string HAS NO SERVANT
PROCESSES |
Explanation: This message is issued in response to the DISPLAY,SERVANTS command to indicate that the control process which received the command has no active servant processes.
User Response: None
BBOO0185I | SERVER string/string HAS dstring
SERVANT PROCESSstring (ASIDstring: string) |
Explanation: This message is issued in response to the DISPLAY,SERVANTS command to indicate the number of servant processes which are active under the control process which received the display command. The ASIDs (in hex) of the servant processes are then listed unless there are too many to list in which case text is placed in the message to indicate this.
User Response: None
BBOO0186E | THE string COMMAND HAS NO ADDITIONAL KEYWORDS |
Explanation: The indicated command was issued with additional keywords provided beyond what is shown. These additional keywords are not required and should not be used.
User Response: Reissue the command without the extraneous keywords
BBOO0187I | NO SERVERS ARE ACTIVE |
Explanation: This message is issued in response to the DISPLAY,SERVERS command when there are no servers active besides the Daemon.
User Response: None
BBOO0188I | END OF OUTPUT FOR COMMAND string |
Explanation: At the end of every display command, this message is issued to indicate completion of processing for the command. The purpose of this message is to enable automation to find the end of the output for a display command it issued.
User Response: None
BBOO0189I | PROTOCOLS AND LISTENING PORTS FOR SERVER
string/string |
Explanation: This message is issued in response to the DISPLAY,SESSIONS or DISPLAY,SESSIONS,LISTENERS command. It is the header for the response and identifies the generic and specific server names for the control process which received the command.
User Response: None
BBOO0190I | string dstring |
Explanation: This message repeats as the body of the reply to the DISPLAY,SESSIONS or DISPLAY,SESSIONS,LISTENERS command. Each line indicates the protocol and the port number on which this server listens for that protocol.
User Response: None
BBOO0191I | SERVER SESSION COUNTS FOR PROTOCOLS USED BY SERVER
string/string |
Explanation: This message is issued in response to the DISPLAY,SESSIONS,SERVER command. It acts as the header for the response and identifies the generic and specific names for the control process which received the command.
User Response: None
BBOO0192I | string dstring |
Explanation: This message repeats as the body of the reply to the DISPLAY,SESSIONS,SERVER command. Each line indicates a protocol and the number of server sessions which exist for that protocol.
User Response: None
BBOO0193I | SERVER string/string HAS dstring
string SERVER SESSIONS |
Explanation: This message is issued in response to the command DISPLAY,SESSIONS,SERVER,xxxx where xxxx is one of the valid protocols for which information can be requested. Use the DISPLAY,SESSIONS,SERVER,HELP command to get a list of valid protocols. This message identifies the generic and specific server names of the control process which received this command and the count of server sessions for the protocol. The protocol name specified is the final fill-in value.
User Response: None
BBOO0194I | SERVER string/string HAS dstring
string SERVER SESSIONS AS FOLLOWS |
Explanation: This command acts as the header for the response to the DISPLAY,SESSIONS,SERVER,xxxx,LIST command where xxxx is one of the valid protocols for which information can be requested. Use the DISPLAY,SESSIONS,SERVER,HELP command to get a list of valid protocols. This message identifies the generic and specific server names of the control process which received this command and the count of server sessions for the protocol. The protocol name specified is the final fill-in value.
User Response: None
BBOO0195I | string |
Explanation: This message repeats as the response to the command DISPLAY,SESSIONS,SERVER,xxxx,LIST where xxxx is one of the valid protocols for which information can be requested. Use the DISPLAY,SESSIONS,SERVER,HELP command to get a list of valid protocols. The message identifies the hostname and port number of the client connected to this server session, or, in the case of local clients, the jobname and ASID.
User Response: None
BBOO0196I | TRACE INFORMATION FOR SERVER
string/string |
Explanation: This message acts as the header to the response to the DISPLAY,TRACE command. It identifies the generic and specific server names for the control process processing the command.
User Response: None
BBOO0197I | string |
Explanation: This message repeats as the body of the response to the DISPLAY,TRACE command. It may indicate the aggregate trace level across the various components, indicate the destination for trace output, list the components which have tracing active at the various trace levels, or list individual trace points which have been activated.
User Response: None
BBOO0198E | AN EQUALS SIGN IS REQUIRED AFTER THIS KEYWORD |
Explanation: The Modify command was issued with a keyword which must be followed by an equal sign and some value. No equal sign was found.
User Response: Reissue the command with an equals sign following the keyword.
BBOO0199E | THIS MODIFY COMMAND REQUIRES NO ADDITIONAL KEYWORDS |
Explanation: A modify command was issued with a keyword which required no additional keywords, however more text was supplied on the command.
User Response: Reissue the command without the extraneous text.
BBOO0200E | THIS MODIFY COMMAND REQUIRES DATA FOLLOWING THE EQUALS SIGN.
SPECIFY =HELP FOR HELP |
Explanation: A modify command was issued with a keyword which requires an equal sign followed by some value. No value was found after the equal sign. Reissue the command specifying a value of HELP after the equal sign for a list of valid responses.
User Response: Reissue the command with a valid value after the equal sign.
BBOO0201I | JVM HEAP INFORMATION FOR SERVER
string/string/string |
Explanation: This message acts as the header to the response to the DISPLAY,JVMHEAP command. It identifies the generic server name, the specific server name, and the JES job prefix for the control or servant process processing the command.
User Response: None
BBOO0202I | (string) string |
Explanation: This message repeats as the body of the response to the DISPLAY,JVMHEAP command. For each heap/subpool/page pool that information was returned from the JNI method QueryGCStatus.
User Response: None
BBOO0203E | SHASTA RUNTIME FUNCTION string COULD NOT LOAD THE JAVA
VM DLL string. string |
Explanation: The Shasta runtime could not load the specified DLL for the Java virtual machine.
User Response: Verify that the LIBPATH environment variable specifies the correct path to the Java virtual machine DLL. Verify that the target DLL is APF authorized.
BBOO0204I | JVM HEAP INFORMATION FOR SERVER
string/string/string COMPLETE |
Explanation: This message acts as the trailer to the response to the DISPLAY,JVMHEAP command. It identifies the generic server name, the specific server name, and the JES job prefix for the control or servant process processing the command.
User Response: None
BBOO0205E | NO CLOSING QUOTE WAS FOUND FOR THE TRACE GROUP NAME |
Explanation: When specifying trace points, a trace group name may be specified. The group name is the name of an environment variable which contains a list of one or more trace points. Trace group names are delimited by single quotes. A single quote was found indicating the beginning of the trace group name, but no matching closing single quote was found to indicate the end of the trace group name.
User Response: Use a closing single quote to indicate the end of the trace group name.
BBOO0206E | NOTHING WAS FOUND AFTER A TRACE GROUP IN A LIST |
Explanation: When specifying trace points, a trace group name may be specified. The group name is the name of an environment variable which contains a list of one or more trace points. Trace group names are delimited by single quotes. A list of trace points or group names is enclosed in parenthesis. An open parenthesis was found and at least one trace group name was found and processed, however the closing quote of the trace group name was not followed by a comma, indicating another trace point or group name follows, or by a closing parenthesis indicating the end of the list.
User Response: The closing quote of a trace group name must be followed by a comma or a closing parenthesis.
BBOO0207E | SPECIFIED TRACE GROUP string CONTAINS NO DATA |
Explanation: When specifying trace points, a trace group name may be specified. The group name is the name of an environment variable which contains a list of one or more trace points. Trace group names are delimited by single quotes. The environment variable specified is either undefined or is defined to nothing (i.e. TGROUP1= ).
User Response: Either use the correct environment variable name as the trace group name or define the environment variable used to contain the trace points you require.
BBOO0208E | TOO MANY LEVELS OF TRACE GROUPS |
Explanation: When specifying trace points, a trace group name may be specified. The group name is the name of an environment variable which contains a list of one or more trace points or other trace groups. Since a trace group definition can contain the name of another trace group, it is possible to have layers upon layers of groups. However, due to a typing error it is also possible to form a chain that points back on itself producing an infinite loop attempting to process it. To prevent this, a limit exists on the number of levels of trace groups that may be defined.
User Response: Specify the trace points you want in fewer layers of groups or examine your trace group names for errors producing a circular list.
BBOO0209E | A COMMA IN A DISPLAY COMMAND MUST BE FOLLOWED BY A
KEYWORD |
Explanation: The display command syntax consists of keywords separated by commas. A command ending in a comma is not valid. Some valid keyword must follow the comma.
User Response: Provide a valid keyword after the comma
BBOO0210E | TRACETOSYSPRINT= MUST BE FOLLOWED BY EITHER YES OR NO |
Explanation: You must specify either YES or NO to turn tracing to sysprint on or off.
User Response: Provide a valid value
BBOO0211I | MODIFY COMMAND string COMPLETED string |
Explanation: Trace related modify commands issue this message when processing in the control process is completed. If the command did not complete successfully, previous messages will indicate the error encountered.
User Response: None.
BBOO0212I | VALUE 'string' SPECIFIED FOR string IS NOT VALID |
Explanation: A value for TRACEALL, TRACEBASIC or TRACEDETAIL was specified which is not valid.
User Response: Specify valid values for the indicated variable.
BBOO0213I | TRACEPOINT hstring OCCURRED ON TCB %06X |
Explanation: The specified trace point has caused execution for the specified TCB to stop until this WTOR is responded to as the result of special trace options being set.
User Response: Respond to the WTOR when you are ready for the thread to continue.
BBOO0214I | string |
Explanation: The message consists of the header for the indicated trace point as written to sysprint.
User Response: None.
BBOO0215I | PRODUCT 'string' SUCCESSFULLY REGISTERED WITH
IFAED SERVICE. |
Explanation: The specified product was successfully registered with the IFAED service, as described in publication SA22-7604.
User Response: None.
BBOO0216E | PRODUCT 'string' FAILED TO REGISTER WITH IFAED
SERVICE. Return code: dstring |
Explanation: The specified product failed to register with the IFAED service.
User Response: See publication SA22-7604 for an explanation of the return code.
BBOO0217A | FAILED TO OPEN HTTP TRANSPORT TRANSACTION CLASS MAPPING FILE
string. |
Explanation: WebSphere for z/OS was unable to open the file specified by the environment variable BBOC_HTTPALL_BBOC_HTTPALL_TCLASS_FILE.
User Response: Make sure the file is correctly specified and the permissions are correct.
BBOO0218A | HTTP TRANSPORT TRANSACTION CLASS MAPPING FILE string HAD
PARSE ERRORS. |
Explanation: WebSphere for z/OS detected parse errors in the file specified by the environment variable BBOC_HTTPALL_BBOC_HTTPALL_TCLASS_FILE.
User Response: Check the WebSphere for z/OS error log for details.
BBOO0219A | HTTP TRANSPORT TRANSACTION CLASS MAPPING FILE PARSE ERROR AT
LINE=dstring. |
Explanation: WebSphere for z/OS detected a syntax error with the TransClassMap entry at the specified line of the file specified by the environment variable BBOC_HTTPALL_BBOC_HTTPALL_TCLASS_FILE.
User Response: Make sure the file is correctly specified and the permissions are correct.
BBOO0220E | string |
Explanation: Java code ported from another platform may issue messages which do not conform to z/OS message conventions. In that case, error messages are wrapped with this message to ensure compliance.
User Response: For more information about this message, refer to the WebSphere Application Server for z/OS V5.0 InfoCenter, access to which can be obtained through the WebSphere for z/OS library Web site http:www.ibm.com/software/webservers/appserv/zos_os390/library.html.</ p>
BBOO0221W | string |
Explanation: Java code ported from another platform may issue messages which do not conform to z/OS message conventions. In that case, warning messages are wrapped with this message to ensure compliance.
User Response: For more information about this message, refer to the WebSphere Application Server for z/OS V5.0 InfoCenter, access to which can be obtained through the WebSphere for z/OS library Web site http:www.ibm.com/software/webservers/appserv/zos_os390/library.html.</ p>
BBOO0222E | Configuration synchronization failed. |
Explanation: Configuration files could not be synchronized between the deployment manager and the node.
User Response: Look at the other log entries to get information on the specific error. One common reason is that the deployment manager is unreachable.</ p>
BBOO0222I | string |
Explanation: Java code ported from another platform may issue messages which do not conform to z/OS message conventions. In that case, informational messages are wrapped with this message to ensure compliance.
User Response: For more information about this message, refer to the WebSphere Application Server for z/OS V5.0 InfoCenter, access to which can be obtained through the WebSphere for z/OS library Web site http:www.ibm.com/software/webservers/appserv/zos_os390/library.html.</ p>
BBOO0223I | string |
Explanation: Java code ported from another platform may issue messages which do not conform to z/OS message conventions. In that case, messages whose severity is indeterminate (not E, W, or I) are wrapped with this message to ensure compliance.
User Response: For more information about this message, refer to the WebSphere Application Server for z/OS V5.0 InfoCenter, access to which can be obtained through the WebSphere for z/OS library Web site http:www.ibm.com/software/webservers/appserv/zos_os390/library.html.</ p>
BBOO0224I | TRACE INFORMATION FOR SERVER
string/string/string |
Explanation: This message acts as the header to the response to the DISPLAY,TRACE command. It identifies the generic and specific server namesand the JES job prefix for the control or servant process.
User Response: None
BBOO0225I | TRACE INFORMATION FOR SERVER
string/string/string COMPLETE |
Explanation: This message acts as the trailer to the response to the DISPLAY,TRACE command. It identifies the generic server name, the specific server name, and the JES job prefix for the control or servant process processing the command.
User Response: None
BBOO0226E | WEBSPHERE FOR Z/OS DAEMON FAILED BECAUSE DAEMON GROUP NAME IS
NOT SET. |
Explanation: In order for the WebSphere for z/OS Daemon to start properly, the DAEMON GROUP NAME environment variable must be set.
User Response: Set the DAEMON GROUP NAME environment variable.
BBOO0227E | WEBSPHERE FOR Z/OS SERVER FAILED BECAUSE DAEMON GROUP NAME IS
NOT SET. |
Explanation: In order for the WebSphere for z/OS server to start properly, the DAEMON GROUP NAME environment variable must be set.
User Response: Set the DAEMON GROUP NAME environment variable.
BBOO0228E | WEBSPHERE FOR Z/OS SERVER FAILED BECAUSE DAEMON GROUP
string IS NOT ACTIVE. |
Explanation: In order for the WebSphere for z/OS server to start properly, the Daemon for the Daemon group must be active.
User Response: Ensure the Daemon for the Daemon group is active before starting the server.
BBOO0229W | The string DLL for messages could not be loaded. Check
your STEPLIB to ensure it can be located. |
Explanation: WebSphere for z/OS could not load the specified DLL.
User Response: Ensure that the specified DLL is part of the execution path for this process. If it is not, add it to the execution path: STEPLIB, JOBLIB, LPA, link list or path.
BBOO0230E | LOADED WRONG VERSION OF MODULE string |
Explanation: During initialization of a WebSphere for z/OS server, an attempt was made to load the product module whose name is in the message text. The load module was found but it is the wrong version. The server terminates.
User Response: Determine where the load module is and fix STEPLIB, LPA or Linklist so that the correct version will be loaded. Restart the server after fixing the problem.
BBOO0231I | DAEMON LOADED MODULES INTO COMMON. |
Explanation: During initialization of a WebSphere for z/OS server, modules were loaded into common. This occurs when steplib has a dataset containing modules required to be in common.
User Response: None.
BBOO0232W | A request for Class Name 'string' and Method Name
'string', from string, has timed out. The servant process associated with the request will be terminated. Request Id( hstring) |
Explanation: A request has timed out that was associated with a servant process. The associated servant process will be terminated. The "from" string identifies the client of the request. For clients using TCP/IP the host name and port number will appear in the message. For a local client, this field contains the jobname and ASID of the client address space. The "Request Id" is a unique identifier of this request.
User Response: Examine the application for possible coding errors which may have lead to delays.
BBOO0233E | SYSBBOSS TRACE REQUEST FAILED. OPTIONS ARE NOT ALLOWED. |
Explanation: The system rejected the request to trace the SYSBBOSS component. The TRACE command specified options, but options are not allowed (except for option WTR).
User Response: Reenter the TRACE command specifying no options or the WTR option.
BBOO0234I | SERVANT PROCESS THREAD COUNT IS dstring. |
Explanation: Indicates the number of worker threads present in the servant process.
User Response: None
BBOO0235E | FUNCTION INET_ADDR RETURNED INADDR_NONE FOR ADDRESS
string. |
Explanation: Indicates the inet_addr function returned the value INADDR_NONE due to a bad IP address being supplied to the function. The IP address is taken from the IIOP listen IP address in the configuration. This error can occur if the specified address is not a valid dotted decimal address.
User Response: Verify the IIOP listener IP address is a valid IP address
BBOO0236I | UNIX SYSTEM SERVICES SHUTDOWN INITIATED. ISSUING STOP TO DAEMON
string. |
Explanation: In response to a shutdown of Unix System Services, the DAEMON is stopped.
User Response: None.
BBOO0237I | WEBSPHERE FOR Z/OS DAEMON
string/string/string IS STARTING. |
Explanation: The WebSphere for z/OS daemon address space is starting with cell long name/ node long name /server long name
User Response: None.
BBOO0238I | WEBSPHERE FOR Z/OS CONTROL PROCESS
string/string/string IS STARTING. |
Explanation: The WebSphere for z/OS application control process address space is starting with cell long name/ node long name /server long name
User Response: None.
BBOO0239I | WEBSPHERE FOR Z/OS SERVANT PROCESS
string/string/string IS STARTING. |
Explanation: The WebSphere for z/OS application servant process address space is starting with cell long name/ node long name /server long name
User Response: None.
BBOO0240E | TRACETOTRCFILE= MUST BE FOLLOWED BY EITHER YES OR NO |
Explanation: You must specify either YES or NO to turn tracing to trcfile on or off.
User Response: Provide a valid value
BBOO0241W | OPEN JVM_LOGFILE FAIL: string with
errno=dstring [string]. |
Explanation: Could not open specified jvm_logfile.
User Response: Correct the variable setting and re-start WebSphere for z/OS.
BBOO0242E | string STARTUP IS DELAYED, WAITING FOR INFORMATION FROM
GRS. |
Explanation: Daemon / Control / Server region is starting and is delayed because GQSCAN returned RC=0xC, RSN=0xC so the region is unable to determine the state of required ENQs. Start of the region is delayed until GRS is able to provide an answer.See the documentation for the MVS macro GQSCAN in MVS Programming:: Authorized Assembler Services Reference, Volume 2 for more information.
User Response: none.
BBOO0243W | HTTP LARGE DATA INPUT BUFFER LENGTH dstring COULD NOT BE
OBTAINED. |
Explanation: Control region could not obtain storage for the HTTP large data input buffer.
User Response: If the buffer is required, decrease the storage used by the server or decrease the value specified on the protocol_http_large_data_inbound_buffer variable and re-start the server.
BBOO0244W | HTTP LARGE DATA INPUT BUFFER LENGTH dstring LESS THAN
LARGE CELL SIZE dstring . |
Explanation: Control region did not allocate a HTTP large data input buffer because the requested length is not greater than the large cpool cell size.
User Response: If the buffer is required, increase the value specified on the protocol_http_large_data_inbound_buffer variable and re-start the server.
BBOO0245W | SOCKET BIND TO CONFIGURED PORT dstring FOR SERVER
string FAILED. STARTUP WILL PROCEED USING ANOTHER AVAILABLE PORT. |
Explanation: WebSphere for z/OS issued the bind function which failed. Details of the failure can be seen in previous message BBOO0142E. The bind will retry once on a random available port.
User Response: The most likely cause of this failure is that the configured port is already in use. In order for peer restart and recovery to function correctly, port numbers must be unique on all WebSphere servers across the entire sysplex. When the configured port is not available, WebSphere will attempt to use another available port, but this may prevent communication between other servers or resource managers due to firewall settings. Verify that each server in your sysplex is using a set of unique port numbers.
BBOO0246I | INITIALIZATION COMPLETE FOR DAEMON
string/string/string/string. |
Explanation: Initialization is complete for the WebSphere for z/OS daemon indicated. The process name strings are cell name, node name, cluster name, server name.
User Response: None.
BBOO0247I | INITIALIZATION COMPLETE FOR WEBSPHERE FOR Z/OS CONTROL PROCESS
string/string/string/string. |
Explanation: Initialization is complete for the WebSphere for z/OS control process address space indicated. This address space is defined as a server instance in the WebSphere for z/OS Administration end-user interface. The process name strings are cell name, node name, cluster name, server name.
User Response: None.
BBOO0248I | INITIALIZATION COMPLETE FOR WEBSPHERE FOR Z/OS SERVANT PROCESS
string/string/string/string. |
Explanation: Initialization is complete for the WebSphere for z/OS application servant address space indicated. The process name strings are cell name, node name, cluster name, server name.
User Response: None.
BBOO0249E | INSTALLATION ROOT AND CONFIGURED ROOT ARE NOT RUNNING AT THE SAME
\ SERVICE LEVEL. USE SMP/E TO RETURN TO LEVEL string AND THEN USE \ BACKOUTPTF.SH TO RETURN TO LEVEL string BEFORE SMP/E RESTORING OFF. |
Explanation: The post installer detected that the configured root is at a higher service level than the installation root. This occurs when SMP/E is used to restore off to a previous service level without first running the backoutPTF.sh shell script. To fix this issue, SMP/E must be used to return to the level specified in the message and then the backoutPTF.sh script is run specifying the target level. Then a SMP/E restore off is re-executed to return to the original target level.
User Response:
BBOO0250W | WARNING(S) ISSUED DURING THE INSTALLATION OF string, SEE
LOG FILE FOR DETAILS: string |
Explanation: During the post install processing of the level specified in the message, warnings were issued during the apply processing of a service unit. The application of service was successful, but the warning messages should be examined. The warning messages are listed in the log file in the hfs file specified in the message.
User Response:
BBOO0251E | ERROR(S) ISSUED DURING THE INSTALLATION OF string, SEE
LOG FILE \ FOR DETAILS: string |
Explanation: The post installer encountered a fatal error while installing the service level indicated in the message. The details of the error are contained in the hfs log file specified in the message. The server will not be permitted to start until the error(s) are corrected.
User Response:
BBOO0252E | BATCH SERVICE INSTALLATION PENDING. APPLYPTF.SH MUST BE MANUALLY
\ RUN FROM A USERID WITH THE NECESSARY AUTHORITY. |
Explanation: The post installer detected that there is "batch" service pending and the post installer was launched in "inline" mode. The applyPTF.sh shell script must be launched directly from the shell or from the BBOWAPLY job from a user id that has the proper authority.
User Response:
BBOO0253W | HTTP LARGE DATA RESPONSE BUFFER LENGTH dstring MUST BE
GREATER THAN dstring . |
Explanation: Control region did not allocate a HTTP large data response buffer because the requested length is not greater than the default size.
User Response: If the buffer is required, increase the value specified on the protocol_http_large_data_response_buffer variable and re-start the server.
BBOO0254W | HTTP LARGE DATA RESPONSE BUFFER LENGTH dstring COULD NOT
BE OBTAINED. |
Explanation: Control region could not obtain storage for the HTTP large data response buffer.
User Response: If the buffer is required, decrease the storage used by the server or decrease the value specified on the protocol_http_large_data_response_buffer variable and re-start the server.
BBOO0255I | TIME OF LAST WORK DISPLAY string |
Explanation: This message is part of the response to a display,work command. Subsequent messages may show the differences (delta) in the amount of work processed since the previous display,work command was issued. This messages tells you the time of the previous command, so that you can tell time window for which the delta applies.
User Response: None
BBOO0256I | TOTAL string REQUESTS dstring (DELTA
dstring) |
Explanation: This message shows the total number of requests of type string received by the controller. The delta is the difference between the total shown here and the total at the time of the previous display,work command. Note that display,work command processing is not serialized with respect to running work so the calculated delta may not be the exact difference between the value shown here and on the previous display,work command.
User Response: None
BBOO0257I | CURRENT string REQUESTS dstring |
Explanation: This message shows the total number of requests of type string currently being processed by this server. The request may in dispatch in a servant or may be in one of various queues waiting for resources. This number indicates the number of requests received for which responses have not yet been sent.
User Response: None
BBOO0258I | string REQUESTS IN DISPATCH dstring |
Explanation: This message shows the number of requests of type string currently running in a servant for this server. Note that by 'in dispatch' we mean just that the servant has picked up the work from the controller's queue and has not yet given a response back to the controller. This is not an indication that the request is executing vs. being blocked etc.
User Response: None
BBOO0259I | string: TOTAL string REQUESTS
dstring (DELTA dstring) |
Explanation: This message shows the total number of requests of the indicated type received by the servant whose jobid preceeds the colon. The delta is approximately the difference in this value since the last display,work command was issued. Note that display,work command processing is not serialized with respect to running work so the calculated delta may not be the exact difference between the value shown here and on the previous display,work command.
User Response: None
BBOO0260I | string: string REQUESTS IN DISPATCH
dstring |
Explanation: This message shows the total number of requests of the indicated type being processed currently by the servant whose jobid preceeds the colon.
User Response: None
BBOO0261I | TOTAL REQUESTS TO SERVER dstring (DELTA
dstring) |
Explanation: This message shows the total number of requests received by the controller. The delta is the difference between the total shown here and the total at the time of the previous display,work command. Note that display,work command processing is not serialized with respect to running work so the calculated delta may not be the exact difference between the value shown here and on the previous display,work command.
User Response: None
BBOO0262I | TOTAL CURRENT REQUESTS dstring |
Explanation: This message shows the total number of requests currently being processed by this server. The request may in dispatch in a servant or may be in one of various queues waiting for resources. This number indicates the number of requests received for which responses have not yet been sent.
User Response: None
BBOO0263I | TOTAL REQUESTS IN DISPATCH dstring |
Explanation: This message shows the number of requests currently running in a servant for this server. Note that by 'in dispatch' we mean just that the servant has picked up the work from the controller's queue and has not yet given a response back to the controller. This is not an indication that the request is executing vs. being blocked etc.
User Response: None
BBOO0264I | string: TOTAL REQUESTS dstring (DELTA
dstring) |
Explanation: This message shows the total number of requests received by the servant whose jobid preceeds the colon. The delta is approximately the difference in this value since the last display,work command was issued. Note that display,work command processing is not serialized with respect to running work so the calculated delta may not be the exact difference between the value shown here and on the previous display,work command.
User Response: None
BBOO0265I | string: TOTAL REQUESTS IN DISPATCH
dstring |
Explanation: This message shows the total number of requests being processed currently by the servant whose jobid preceeds the colon.
User Response: None
BBOO0266I | (string) string |
Explanation: This message is issued in response to the display errlog command and contains a copy of a message written to the WebSphere Error Log. The value in parenthesis is the jobid of either the controller or the servant where the message was issued.
User Response: None
BBOO0267I | TOTAL string TIMEOUTS dstring (DELTA
dstring) |
Explanation: This message shows the total number of requests of type string timed out. The delta is the difference between the total shown here and the total at the time of the previous display,work command. Note that display,work command processing is not serialized with respect to running work so the calculated delta may not be the exact difference between the value shown here and on the previous display,work command.
User Response: None
BBOO0268I | TOTAL TIMED OUT REQUESTS dstring (DELTA
dstring) |
Explanation: This message shows the total number of requests timed out by the controller. The delta is the difference between the total shown here and the total at the time of the previous display,work command. Note that display,work command processing is not serialized with respect to running work so the calculated delta may not be the exact difference between the value shown here and on the previous display,work command.
User Response: None
BBOO0269E | BIND FOR string PORT FAILED BECAUSE PORT dstring
WAS ALREADY IN USE |
Explanation: This message is issued due to bind failure because the port was already in use.
User Response: Change the port number to one that is available.
BBOO0270E | WEBSPHERE APPLICATION SERVER FOR Z/OS LICENSING AGREEMENT NOT
MET |
Explanation: For customers who are applying the program on top of existing configurations of WebSphere Application Server for z/OS version 5.0, you will also be required to review and indicate acceptance of additional terms.
User Response: You access these additional terms as follows: 1. Invoke the Configuration Dialog. 2. You will be presented with these additional licensing terms & conditions upon invocation of the Configuration Dialog. 3. After reading the additional terms, you will be prompted for acceptance. If you do not accept these terms, execution of the code will be denied. 4. Once you accept, you will be on the main panel of the dialog. Select the option "Configure v5.02 License Agreement Refresher." 5. Follow through the option "Configure v5.02 License Agreement Refresher." to generate the jobs and follow the generated instructions. 6. You need to repeat step 5 for each hfs for WebSphere configuration data, WAS_HOME (for example /WebSphere/V5R0M0/AppServer), that you have configured.