Problem | Displays the IBM copyright statement |
User response | None. |
Problem | The WebSphere Application Server for z/OS control @TUC process address space indicated by "string" is starting. This address space is defined as a server instance in the WebSphere Application Server for z/OS Administration end-user interface. The process name strings are cell name, node name, cluster name, server name. |
User response | None. |
Problem | The WebSphere Application Server 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 Application Server for z/OS Administration end-user interface. |
User response | None. |
Problem | The WebSphere Application Server 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 Application Server for z/OS Administration end-user interface. |
User response | "hstring" indicates a minor code that describes the specific failure that occurred. |
Problem | The WebSphere Application Server for z/OS application servant address space indicated by "string" is starting. This address space is defined as a server instance in the WebSphere Application Server for z/OS Administration end-user interface. The process name strings are cell name, node name, cluster name, server name. |
User response | None. |
Problem | The WebSphere Application Server 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 Application Server for z/OS Administration end-user interface. |
User response | None. |
Problem | The WebSphere Application Server 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 Application Server 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. |
Problem | The WebSphere Application Server for z/OS daemon address space is starting. The process name strings are cell name, node name, cluster name, server name. |
User response | None. |
Problem | The WebSphere Application Server for z/OS daemon address space has ended normally. |
User response | None. |
Problem | The WebSphere Application Server 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. |
Problem | WebSphere Application Server 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 Application Server for z/OS might have handled the error. If no related messages are found, see the WebSphere Application Server for z/OS Error Codes section of this book for a description of this error. |
Problem | WebSphere Application Server for z/OS caught the indicated CORBA system exception. |
User response | See additional messages to determine how WebSphere Application Server for z/OS handled the error. If no related messages are found, see the WebSphere Application Server for z/OS Error Codes section of this book for a description of this error. |
Problem | WebSphere Application Server 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 Application Server for z/OS handled the error. |
Problem | WebSphere Application Server for z/OS caught the indicated CORBA user exception. |
User response | See additional messages to determine how WebSphere Application Server for z/OS handled the error. |
Problem | WebSphere Application Server 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 Application Server for z/OS handled the error. |
Problem | Initialization is complete for the WebSphere Application Server for z/OS daemon indicated. |
User response | None. |
Problem | Missing ORBsrvname parameter or value for the current program. |
User response | Modify the program parameters passed to the program, passing ORBsrvname <value>. |
Problem | WebSphere Application Server for z/OS received control in its signal handler and is attempting to retry the error. |
User response | None. |
Problem | Initialization is complete for the WebSphere Application Server for z/OS control process address space indicated. This address space is defined as a server instance in the WebSphere Application Server for z/OS Administration end-user interface. |
User response | None. |
Problem | Initialization is complete for the WebSphere Application Server for z/OS application servant address space indicated. |
User response | None. |
Problem | The above assertion failed. |
User response | This is an internal programming error. For further assistance &&SERVICETEXT&& This site provides searchable databases of technotes, solutions, and e-fixes. Information on contacting the WebSphere Support team is also provided. |
Problem | WebSphere Application Server 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 Application Server for z/OS handled the error. If no related messages are found, see the WebSphere Application Server for z/OS Error Codes section of this book for a description of this error. |
Problem | WebSphere Application Server 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 Application Server for z/OS handled the error. |
Problem | WebSphere Application Server 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. |
Problem | 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. |
Problem | 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. |
Problem | 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. |
Problem | 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. |
Problem | WebSphere Application Server for z/OS could not $S9C use the specified language. WebSphere Application Server 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 Application Server for z/OS used the default language of ENUS instead. |
User response | None. |
Problem | WebSphere Application Server for z/OS could not @TUC 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. |
Problem | WebSphere Application Server 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. |
Problem | WebSphere Application Server for z/OS received @TUC 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. |
Problem | WebSphere Application Server 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. |
Problem | WebSphere Application Server for z/OS is terminating the current process (address space). |
User response | See previous messages for the reason this process was terminated. |
Problem | WebSphere Application Server for z/OS failed as @TUC 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. |
Problem | WebSphere Application Server for z/OS failed as @TUC 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. |
Problem | WebSphere Application Server for z/OS failed as @TUC 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. |
Problem | WebSphere Application Server 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. |
Problem | WebSphere Application Server 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. |
Problem | WebSphere Application Server 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. |
Problem | WebSphere Application Server 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. |
Problem | WebSphere Application Server 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. |
Problem | WebSphere Application Server for z/OS experienced a communications error. |
User response | See the WebSphere Application Server for z/OS Error Codes section of this book for a description of this error. |
Problem | WebSphere Application Server for z/OS failed with an internal error. |
User response | See the WebSphere Application Server for z/OS Error Codes section of this book for a description of this error. |
Problem | WebSphere Application Server for z/OS failed with an internal error. |
User response | See the WebSphere Application Server for z/OS Error Codes section of this book for a description of this error. |
Problem | WebSphere Application Server 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. |
Problem | The WebSphere Application Server for z/OS administrator started the WebSphere component trace (or the trace was started by default). WebSphere Application Server 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 Application Server 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 Application Server 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. |
Problem | 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 assistance &&SERVICETEXT&& This site provides searchable databases of technotes, solutions, and e-fixes. Information on contacting the WebSphere Support team is also provided. |
Problem | A non-zero result was returned from EXEC SQL. |
User response | Refer to DB2 reference books and perform the appropriate actions. |
Problem | 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. |
Problem | The data object was asked to update the data store but the KEY values had not been set. |
User response | none. |
Problem | 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 assistance &&SERVICETEXT&& This site provides searchable databases of technotes, solutions, and e-fixes. Information on contacting the WebSphere Support team is also provided. |
Problem | 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 &&SERVICETEXT&& |
Problem | 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 assistance &&SERVICETEXT&& This site provides searchable databases of technotes, solutions, and e-fixes. Information on contacting the WebSphere Support team is also provided. |
Problem | WebSphere Application Server 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. |
Problem | WebSphere Application Server 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. |
Problem | 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. |
Problem | The WebSphere Application Server 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. |
Problem | The WebSphere Application Server for z/OS OLT DLL was loaded. |
User response | None. |
Problem | WebSphere Application Server 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 Application Server for z/OS handled the error. See also the explanation for exceptions under the indicated function. |
Problem | 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. |
Problem | 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 assistance &&SERVICETEXT&& This site provides searchable databases of technotes, solutions, and e-fixes. Information on contacting the WebSphere Support team is also provided. |
Problem | 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. |
Problem | 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 assistanc &&SERVICETEXT&& This site provides searchable databases of technotes, solutions, and e-fixes. Information on contacting the WebSphere Support team is also provided. |
Problem | The Shasta Runtime detected the condition described in this informational message. |
User response | none |
Problem | 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. |
Problem | The Shasta Runtime detected the condition described in this error message. |
User response | For assistance &&SERVICETEXT&& . This site provides searchable databases of technotes, solutions, and e-fixes. Information on contacting the WebSphere Support team is also provided. |
Problem | The Shasta Runtime detected an error while attempting to load a Java implementation class. |
User response | For assistance &&SERVICETEXT&& . This site provides searchable databases of technotes, solutions, and e-fixes. Information on contacting the WebSphere Support team is also provided. |
Problem | 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. |
Problem | The Shasta Runtime could not establish function pointers required to enable its Java Native Interface (JNI) environment. |
User response | For assistance &&SERVICETEXT&& . This site provides searchable databases of technotes, solutions, and e-fixes. Information on contacting the WebSphere Support team is also provided. |
Problem | The Shasta Runtime detected that the Java VM was not loaded and initialized. |
User response | For assistance &&SERVICETEXT&& . This site provides searchable databases of technotes, solutions, and e-fixes. Information on contacting the WebSphere Support team is also provided. |
Problem | 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. |
Problem | 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. |
Problem | 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. |
Problem | 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. |
Problem | 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. |
Problem | 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. |
Problem | WebSphere Application Server for z/OS failed with @TUC an internal error. |
User response | See the WebSphere Application Server for z/OS Error Codes section of this book for a description of this error. For further assistance &&SERVICETEXT&& This site provides searchable databases of technotes, solutions, and e-fixes. Information on contacting the WebSphere Support team is also provided. |
Problem | 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 @) characaters. 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. |
Problem | 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. |
Problem | 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. |
Problem | 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. |
Problem | 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. |
Problem | 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. |
Problem | Error occurred attempting to open the log stream browse file. |
User response | Verify that the data set exists and is valid. |
Problem | 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. |
Problem | Error occurred while writing to the log stream browse file. |
User response | Verify that the data set exists and is valid. |
Problem | 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. |
Problem | 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. |
Problem | 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. |
Problem | 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. |
Problem | WebSphere Application Server 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 Application Server for z/OS Daemon on this system prior to starting other WebSphere Application Server for z/OS servers. |
Problem | An attempt was made to start a WebSphere @TUC Application Server for z/OS Daemon while another WebSphere Application Server for z/OS Daemon of the same name was also starting. Only one WebSphere Application Server 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 Application Server for z/OS Daemons with the same name on the same system at the same time. |
Problem | An attempt was made to start a WebSphere Application Server 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. |
Problem | An attempt was made to start a WebSphere Application Server 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. |
Problem | 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. |
Problem | 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. |
Problem | 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. |
Problem | 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 Application Server for z/OS Installation and Customization Guide. |
Problem | 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 Application Server for z/OS Installation and Customization Guide. |
Problem | 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 Application Server for z/OS Installation and Customization Guide. |
Problem | 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 Application Server for z/OS Installation and Customization Guide. |
Problem | 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 Application Server for z/OS Installation and Customization Guide. |
Problem | 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 Application Server for z/OS Installation and Customization Guide. |
Problem | 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. |
Problem | 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. |
Problem | During dispatch of a method, WebSphere Application Server 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 Application Server for z/OS applications. |
Problem | The logstream being browsed contains no data. |
User response | Verify the logstream name. |
Problem | 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. |
Problem | 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. |
Problem | WebSphere Application Server for z/OS issued the @TUC 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. |
Problem | WebSphere Application Server for z/OS issued the @TUC 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. |
Problem | GIOP reply message was received, but no corresponding request could be found. |
User response | For assistance &&SERVICETEXT&& This site provides searchable databases of technotes, solutions, and e-fixes. Information on contacting the WebSphere Support team is also provided. |
Problem | Found NULL when looking up classname in ptable in encode_objref() |
User response | For assistance &&SERVICETEXT&&. This site provides searchable databases of technotes, solutions, and e-fixes. Information on contacting the WebSphere Support team is also provided. |
Problem | 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 |
Problem | The ORBid keyword to ORB_init() must be specified with a value. |
User response | Specify a valid value for ORBid |
Problem | The ORBsrvname keyword to ORB_init() must be specified with a value. |
User response | Specify a valid value for ORBsrvname |
Problem | The ORBType keyword to ORB_init() must be specified with a value. |
User response | Specify a valid value for ORBType |
Problem | During initialization of a WebSphere Application Server 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 |
Problem | The RRS address space must be up and initialized for WebSphere Application Server 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 Application Server for z/OS servers. |
User response | Make sure RRS is started and restart the server |
Problem | 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 |
Problem | 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 |
Problem | A Stop command was entered for the WebSphere Application Server 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. |
Problem | When a Stop command is issued for the WebSphere Application Server 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. |
Problem | The modified MVS Stop command has been issued against a WebSphere Application Server for z/OS address space. |
User response | None. |
Problem | The MVS Modify command has been issued to cancel a WebSphere Application Server for z/OS address space requesting ARM restart. |
User response | None. |
Problem | 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. |
Problem | The address space for where the PC was targeted has ended. This is an informational message. |
User response | None. |
Problem | When WebSphere Application Server 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. |
Problem | 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. |
Problem | 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. |
Problem | 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. |
Problem | WebSphere Application Server 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. |
Problem | WebSphere Application Server 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. |
Problem | 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. |
Problem | 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 Application Server 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. |
Problem | 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 Application Server for z/OS server names to ensure that they are unique in a sysplex. In a non-datasharing sysplex where more than one WebSphere Application Server for z/OS image is started ARM cannot be used. |
Problem | WebSphere Application Server 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. |
Problem | WebSphere Application Server 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 |
Problem | WebSphere Application Server 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. |
Problem | 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. |
Problem | 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 |
Problem | 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. |
Problem | 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. |
Problem | WebSphere Application Server 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 |
Problem | WebSphere Application Server 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 |
Problem | 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. |
Problem | 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 |
Problem | JVM abort API has been driven. |
User response | Look for other accompanying error messages in the error log. |
Problem | Threads of a type restarted 5 or more times. |
User response | None. |
Problem | WebSphere Application Server 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. |
Problem | WebSphere Application Server 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. |
Problem | During initialization of a WebSphere Application Server 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. |
Problem | 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. |
Problem | WebSphere Application Server 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. |
Problem | 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. |
Problem | WebSphere Application Server 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. |
Problem | 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. |
Problem | WebSphere Application Server 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. |
Problem | WebSphere Application Server 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. |
Problem | 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. |
Problem | 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. |
Problem | 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 |
Problem | 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 |
Problem | 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. |
Problem | 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. |
Problem | 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. |
Problem | 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. |
Problem | 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 |
Problem | 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 |
Problem | 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 |
Problem | 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. |
Problem | This message acts as a header for the response to the DISPLAY,SERVERS command. |
User response | None |
Problem | 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 |
Problem | 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 |
Problem | 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 |
Problem | 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 |
Problem | This message is issued in response to the DISPLAY,SERVERS command when there are no servers active besides the Daemon. |
User response | None |
Problem | 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 |
Problem | 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 |
Problem | 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 |
Problem | 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 |
Problem | 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 |
Problem | 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 |
Problem | 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 |
Problem | 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 |
Problem | 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 |
Problem | 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 |
Problem | 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. |
Problem | 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. |
Problem | 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. |
Problem | 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 |
Problem | 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 |
Problem | 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. |
Problem | 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 |
Problem | 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. |
Problem | 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. |
Problem | 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. |
Problem | 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. |
Problem | 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 |
Problem | You must specify either YES or NO to turn tracing to sysprint on or off. |
User response | Provide a valid value |
Problem | 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. |
Problem | A value for TRACEALL, TRACEBASIC or TRACEDETAIL was specified which is not valid. |
User response | Specify valid values for the indicated variable. |
Problem | 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. |
Problem | The message consists of the header for the indicated trace point as written to sysprint. |
User response | None. |
Problem | The specified product was successfully registered with the IFAED service, as described in publication SA22-7604. |
User response | None. |
Problem | The specified product failed to register with the IFAED service. |
User response | See publication SA22-7604 for an explanation of the return code. |
Problem | 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 Application Server for z/OS InfoCenter, access to which can be obtained through the WebSphere Application Server for z/OS library Web site http:www.ibm.com/software/webservers/appserv/zos_os390/library.html. |
Problem | 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 InfoCenter, access to which can be obtained through the WebSphere Application Server for z/OS library Web site http:www.ibm.com/software/webservers/appserv/zos_os390/library.html. |
Problem | 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 InfoCenter, access to which can be obtained through the WebSphere Application Server for z/OS library Web site http:www.ibm.com/software/webservers/appserv/zos_os390/library.html. |
Problem | 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 InfoCenter, access to which can be obtained through the WebSphere Application Server for z/OS library Web site http:www.ibm.com/software/webservers/appserv/zos_os390/library.html. |
Problem | 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 |
Problem | 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 |
Problem | In order for the WebSphere Application Server 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. |
Problem | In order for the WebSphere Application Server 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. |
Problem | In order for the WebSphere Application Server 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. |
Problem | WebSphere Application Server for z/OS could not @TUC 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. |
Problem | During initialization of a WebSphere Application Server 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. |
Problem | During initialization of a WebSphere Application Server 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. |
Problem | 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. |
Problem | 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. |
Problem | Indicates the number of worker threads present in the servant process. |
User response | None |
Problem | 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 |
Problem | In response to a shutdown of Unix System Services, the DAEMON is stopped. |
User response | None. |
Problem | The WebSphere Application Server for z/OS daemon address space is starting with cell long name/ node long name /server long name |
User response | None. |
Problem | The WebSphere Application Server for z/OS application control process address space is starting with cell long name/ node long name/server long name |
User response | None. |
Problem | The WebSphere Application Server for z/OS application servant process address space is starting with cell long name/ node long name /server long name |
User response | None. |
Problem | You must specify either YES or NO to turn tracing to trcfile on or off. |
User response | Provide a valid value |
Problem | Could not open specified jvm_logfile. |
User response | Correct the variable setting and re-start WebSphere Application Server for z/OS. |
Problem | 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. |
Problem | 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. |
Problem | 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. |
Problem | WebSphere Application Server 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. |
Problem | Initialization is complete for the WebSphere Application Server for z/OS daemon indicated. The process name strings are cell name, node name, cluster name, server name. |
User response | None. |
Problem | Initialization is complete for the WebSphere Application Server for z/OS control process address space indicated. This address space is defined as a server instance in the WebSphere Application Server for z/OS Administration end-user interface. The process name strings are cell name, node name, cluster name, server name. |
User response | None. |
Problem | Initialization is complete for the WebSphere Application Server for z/OS application servant address space indicated. The process name strings are cell name, node name, cluster name, server name. |
User response | None. |
Problem | The post installer detected that the configured root is at a higher service level than the installation root for the product listed. This occurs when SMP/E is used to restore off to a previous service level without first running the backoutPTF.sh shell script against the listed product. |
User response | To fix this error, Use SMP/E to return to the level specified in the message and then run the backoutPTF.sh script, specifying the target product and target level. Next, rexecute an SMP/E restore off to return to the original target level. |
Problem | The multi-product PTF post installer detected warning(s) issued during the application of post install service for the product listed. The application of service was successful, but the warning message(s) should be examined. The warning messages are listed in the log file in the HFS file specified in the message. |
User response | None |
Problem | The multi-product PTF post installer encountered a fatal error while installing service for the product 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 | None |
Problem | 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 | None |
Problem | 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. |
Problem | 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. |
Problem | 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 |
Problem | 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 |
Problem | 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 |
Problem | 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 |
Problem | 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 |
Problem | 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 |
Problem | 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 |
Problem | 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 |
Problem | 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 |
Problem | 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 |
Problem | This message shows the total number of requests being processed currently by the servant whose jobid preceeds the colon. |
User response | None |
Problem | 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 |
Problem | 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 |
Problem | 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 |
Problem | 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. |
Problem | Controller could not read entire HTTP request, input buffer exceeded. |
User response | Increase the value specified on the protocol_http_large_data_inbound_buffer variable and re-start the server. If installing an application, try installing locally from the server. |
Problem | Controller needed the HTTP Large data input buffer to read in a large HTTP request but it was currently in use for another request. |
User response | Try request again. |
Problem | WebSphere Application Server for z/OS was unable to open the file specified by the environment variable protocol_https_default_cert_label. |
User response | Make sure the file is correctly specified and the permissions are correct. |
Problem | WebSphere Application Server for z/OS detected parse errors in the file specified by the environment variable protocol_https_default_cert_label. |
User response | Check the WebSphere Application Server for z/OS error log for details. |
Problem | WebSphere Application Server for z/OS detected a syntax error with the SSLServerCert entry at the specified line of the file specified by the environment variable protocol_https_default_cert_label. |
User response | Correct the syntax error and restart server. |
Problem | A call to create_proxy returned a NULL |
User response | Ensure that the DLL for the class is in the steplib or linklist |
Problem | The multi-product PTF installer has has detected that there are post SMP/E install actions to be completed for WebSphere Application Server for z/OS or for an installed WebSphere extension product. |
User response | None. |
Problem | WebSphere for z/OS Multi-Product PTF installer has completed it's actions and has ended normally. |
User response | None. |
Problem | The multi-product PTF post installer detected warning(s)issued during the application of post install service. The warning(s) may have been issued during post install application of service for the WebSphere Applicaton Server for z/OS product, or any of the WebSphere extension products that might be installed. A "BBOO0250W" message will have been previously issued for each product that encountered warnings during application of post install service. |
User response | Reply with 'CONTINUE' to continue starting the Application Server. Reply with 'CANCEL' to cancel starting the Application Server. Note the next time the server is restarted, the multi-product PTF post installer will not run again because service was already completed. |
Problem | Reply to a previous message was not valid. The previous message is reissued. |
User response | Issue a valid reply to the reissued message. |
Problem | This is the header message for informational messages showing useage counts for work classification rules |
User response | none |
Problem | Shows information about a particular rule in work classification. Each time the message is issued it shows the number of times this rule was examined, the number of times this rule matched the request, the number of times this rule was actually used (vs. an inner rule), the cost to use this rule (number of compares required to determine this is the correct rule), and finally the descriptive text from the classification rule so you can tell which one we are talking about. |
User response | none |
Problem | Shows totals for all the classification rules for the indicated type of work. The first number is the total number of requests that were classified using the classification rules. The second number is the result of taking the number of times each rule was used multipled by the cost (number of rule compares done) of using that rule and adding those up across all the rules. If you take the weighted total cost and divide by the total number of requests classified, you get a number that you can use as a 'cost' of using the table. The closer that value is to '1', the lower the cost of using the defined rules (1 means there is just the default classification so all requests match it). |
User response | none |
Problem | A display,work command was issued to display statistics for request of type string. However, statistics are not currently being gathered for requests of type string. |
User response | If statistics are desired for requests of type string, then enable statistics gathering by using the f <server>,<string>stats command (e.g. "f bbos001,mdbstats,enable"). |
Problem | The WebSphere Application Server for z/OS adjunct address space for server "string" is starting. This address space is defined as an adjunct in the WebSphere Application Server for z/OS Administration end-user interface. The process name strings are cell name, node name, cluster name, server name. |
User response | None. |
Problem | The WebSphere Application Server for z/OS adjunct address space for server "string" has ended normally. This address space is defined as an adjunct in the WebSphere Application Server for z/OS Administration end-user interface. |
User response | None. |
Problem | The WebSphere Application Server for z/OS adjunct process address space for server "string" has ended abnormally. This address space is defined as an adjunct in the WebSphere Application Server 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. |
Problem | Initialization is complete for the WebSphere Application Server for z/OS adjunct address space for the server indicated. |
User response | None. |
Problem | Initialization is complete for the WebSphere Application Server for z/OS adjunct address space indicated. The process name strings are cell name, node name, cluster name, server name. |
User response | None. |
Problem | The WebSphere Application Server for z/OS adjunct address space is starting with cell long name/ node long name /server long name |
User response | None. |
Problem | The WebSphere Application Server 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 Application Server for z/OS Administration end-user interface. A "START" was issued for another server instance. The "hstring" is the return code from this "START" request. |
User response | None. |
Problem | The value specified to the ORB_init() function for the REC=(N|Y) parameter is invalid. The only acceptable values are REC=N and REC=Y. |
User response | Specify a valid value for REC=(N|Y) |
Problem | The target address space for which the Program Call (PC) was targeted has ended. This is an informational message. |
User response | None. |
Problem | A modify command was issued to manipulate the state of the communication listeners. The communication listeners are currently being modified by either a previous command or for a configured recovery action. The server name strings are cell name, node name, and server name. |
User response | If this message was due to a previous outstanding modify command, then re-issue the command when the previous command has finished. If the target server is configured to "pause/stop" the listeners when it has detected that no servants exist to process work, then re-issue the modify command after the recovery for this state has completed. |
Problem | The server has detected that its last servant has terminated. Work targeted to a servant will be rejected. The server name strings are cell name, node name, and server name. |
User response | None. The server will allow servant work once an available servant is detected. |
Problem | The server had previously detected that its last servant had terminated. It has now detected a sufficient number of ready servants to process work. Work is no longer being rejected. The server name strings are cell name, node name, and server name. |
User response | None. |
Problem | The server has detected that its last servant has terminated. The server has attempted a number of times to modify itself to reject work until a sufficient number of ready servants are detected. The automatic rejection and resumption of work for this occurrence has been aborted. The server name strings are cell name, node name, and server name. |
User response | None. The server is actively processing another event that requires the same manipulation of the server. |
Problem | Various Local Data Area storage info. |
User response | None. |
Problem | Provides additional information for a request that experienced a timeout. For a HTTP request, the additional information is the target URI. For a MDB request, the additional information is the source message listener port name. |
User response | None. |
Problem | The server could not retrieve the JVMExtension interface from the JavaVM. |
User response | None. |
Problem | During initialization of a WebSphere Application Server 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 is not in common storage. 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. |
Problem | Displays the addressing mode of the executing process |
User response | None |
Problem | Displays the addressing mode of the executing process |
User response | None |
Problem | Displays the addressing mode of the executing process |
User response | None |
Problem | Displays the addressing mode of the executing process |
User response | None |
Problem | A timeout has been detected. The servant with the asid and stoken will be abended in the specified number of seconds. Number of seconds to delay is controlled by the control_region_timeout_delay environment variable. |
User response | None. |
Problem | A timeout has been detected. The servant with the asid and stoken is being abended. |
User response | Look for other messages, errors and dumps to help determine the cause of the timeout. |
Problem | The use of the specified configuration variable has been deprecated. |
User response | Please refer to the WebSphere Application Server for z/OS InfoCenter, access to which can be obtained through the WebSphere Application Server for z/OS library Web site http:www.ibm.com/software/webservers/appserv/zos_os390/library.html for more information. |
Problem | The display session commands have been replaced with a similar set of display connections commands. |
User response | None |
Problem | This message is issued in response to the DISPLAY,LISTENERS command. It is the header for the response. It identifies the cell, node generic and specific server names for the control process which received the command. |
User response | None |
Problem | This message repeats as the body of the reply to the DISPLAY,LISTENERS command. Each line indicates the connection instance name, the associated IP Address and listening port number. |
User response | None |
Problem | This message is issued in response to the DISPLAY,CONNECTIONS command. It is the header for the response. It identifies the cell, node generic and specific server names for the control process which received the command. |
User response | None |
Problem | This message repeats as the body of the reply to the DISPLAY,CONNECTIONS command. Each line indicates the connection instance name and a count of the number of connections. |
User response | None |
Problem | This message is the body of the reply to the DISPLAY,CONNECTIONS,NAME= command when the specified name could not be found. |
User response | Ensure the name was entered properly. If the name contains lower case characters put the name in single quotes. example NAME='lowercase' |
Problem | This message repeats in the body of the reply to the DISPLAY,CONNECTIONS,LIST command. Each line indicates the connection instance name. |
User response | None |
Problem | This message repeats in the body of the reply to the DISPLAY,CONNECTIONS,LIST command. Each line indicates remote host information of the connection. |
User response | None |
Problem | This message is the body of the reply to the DISPLAY,CONNECTIONS,LIST,NAME= command when the specified name could not be found. |
User response | Ensure the name was entered properly. If the name contains lower case characters put the name in single quotes. example NAME='lowercase' |
Problem | The server has begun to throttle the accepting of new connections for the listening socket. This limit is configurable. As existing connections are closed, new ones will be accepted. Once this message is issued, it will not be issued again until the total number of connections is below 85% the maximum. |
User response | None |
Problem | The server was unable to create the tcp/ip listening socket for the specified host/port. Look for prior error messages indicating specific failure. Make sure the host and port are correct. Server may fail to initialize. |
User response | None |
Problem | The server will bind specifically to one IP address, but the hostname resolved to multiple addresses. The server picked one address to bind to. |
User response | Make sure that the host value is correct on the endpoint. If it was intended to listen on all addresses then a '*' should be used for the port value. |
Problem | Provides additional information for a request that experienced a timeout. The first string indicates the type of request. The other fields are defined below. (servant hexadecimal ASID): (request id): (internal information): (servant tcb address): (servant job id or job name): (time request received in controller): (time request queued to wlm): (time request dispatched in servant): (class name): (method name): (string indicating the origin of the request): (future data): (future data): (request type specific information) For a IIOP request, the last field is not used. For a HTTP request, the last field is the target URI. For a MDB request, the last field is the source message listener port name. Servant tcb address and servant ASID are zeros when the request did not make it to the servant. Time request dispatched in servant is not filled in when the request did not make it to the servant. |
User response | None. |
Problem | GIOP reply message was received, but no corresponding request could be found. |
User response | Look for other messages, errors and dumps to help determine the cause of this message. This may be a "normal" event if a BBOO0325W message is found with a matching SessionHandle and Request ID. A Request/Reply is uniquely identified by the SessionHandle and Request ID. |
Problem | The server cannot be started using 31-bit addressing mode. |
User response | If you did not intend to start a 31-bit server, please restart the server in 64-bit mode (with the AMODE=64 parameter). |
Problem | The server cannot be started using 64-bit addressing mode. |
User response | If you did not intend to start a 64-bit server, please restart the server in 31-bit mode (without the AMODE=64 parameter). |
Problem | Displays the configured MEMLIMIT for the address space, and the source from where the MEMLIMIT configuration was obtained. The MEMLIMIT CONFIGURATION SOURCE is one of the following values: "SMF" MEMLIMIT set by SMF either in SMFPRMxx or by use of SMF default value=0 "JCL" MEMLIMIT set by the JCL "REG0" MEMLIMIT Unlimited based on REGION=0 specification "USI" MEMLIMIT set by IEFUSI "OMVS" MEMLIMIT set by UNIX OMVS segment "SETR" MEMLIMIT set by UNIX setrlimit "SPW" MEMLIMIT set by UNIX spawn "SETO" MEMLIMIT set by UNIX SETOMVS command "AUTH" MEMLIMIT set by authorized application modification "URG" MEMLIMIT set in IEFSMFIE (IEFUSI set REGION size) "UNKNOWN" MEMLIMIT set by unknown source "BAD" Error setting MEMLIMIT |
User response | None. |