Explanation | Displays the IBM copyright statement |
Action | None. |
Explanation | The WebSphere Application Server for z/OS control region 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, and server name. |
Action | None. |
Explanation | The WebSphere Application Server for z/OS control region 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. |
Action | None. |
Explanation | The WebSphere Application Server for z/OS control region 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. |
Action | "hstring" indicates a minor code that describes the specific failure that occurred. |
Explanation | The WebSphere Application Server for z/OS servant region 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, and server name. |
Action | None. |
Explanation | The WebSphere Application Server for z/OS servant region 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. |
Action | None. |
Explanation | 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. |
Action | "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. |
Explanation | The WebSphere Application Server for z/OS daemon address space is starting. The process name strings are cell name, node name, cluster name, and server name. |
Action | None. |
Explanation | The WebSphere Application Server for z/OS daemon address space has ended normally. |
Action | None. |
Explanation | The WebSphere Application Server for z/OS daemon address space has ended abnormally. |
Action | "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. |
Explanation | An abnormal situation raised the indicated CORBA system exception. |
Action | Look for additional messages to determine how the exception was handled, or search the information center for the given error code. |
Explanation | The indicated CORBA system exception was caught. |
Action | Look for additional messages to determine how the exception was handled, or search the information center for the given error code. |
Explanation | An abnormal situation raised the indicated CORBA user exception. |
Action | Look for additional messages to determine how the exception was handled. |
Explanation | The indicated CORBA user exception was caught. |
Action | Look for additional messages to determine how the exception was handled. |
Explanation | An unexpected exception was caught. This is caused by an application creating an exception that is not of the type CORBA::SystemException or CORBA::UserException. |
Action | Look for additional messages to determine how the exception was handled. |
Explanation | Initialization is complete for the WebSphere Application Server for z/OS daemon indicated. |
Action | None. |
Explanation | Missing ORBsrvname parameter or value for the current program. |
Action | Modify the program parameters passed to the program, passing ORBsrvname <value>. |
Explanation | WebSphere Application Server for z/OS received control in its signal handler and is attempting to retry the error. |
Action | None. |
Explanation | Initialization is complete for the WebSphere Application Server for z/OS control region address space indicated. This address space is defined as a server instance in the WebSphere Application Server for z/OS administration end-user interface. |
Action | None. |
Explanation | Initialization is complete for the WebSphere Application Server for z/OS servant region address space indicated. |
Action | None. |
Explanation | The above assertion failed. This is an internal programming error. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | A CORBA system exception was caught, logged, and re-thrown. |
Action | Look for additional messages to determine how the exception was handled, or search the information center for the given error code. |
Explanation | A CORBA user exception was caught, logged, and re-thrown. |
Action | Look for additional messages to determine how the exception was handled. |
Explanation | WebSphere Application Server for z/OS is using the indicated repository for logging errors. If a system logger stream has been specified, the log stream is used for logging errors. If no log stream was specified or if logging to the log stream cannot be done, then CERR is used for error logging. |
Action | None. |
Explanation | The indicated function failed while processing the indicated data set. The failure is errno. When there is an error log file failure, all error messages are routed to CERR (SYSOUT). |
Action | See the OS/390 C/C++ Library Reference for a description of this error. |
Explanation | WebSphere Application Server for z/OS could not use the specified language. The attempt to load a DLL by the name BBOxxxx, where xxxx is the language indicated by string, failed. The default language of ENUS is used instead. |
Action | None. |
Explanation | The specified function within the message DLL could not be loaded. |
Action | 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. |
Explanation | WebSphere Application Server for z/OS received control for a signal. |
Action | 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. |
Explanation | WebSphere Application Server for z/OS received control for a signal with accompanying information. This additional information is at least one of: original abend code (abendcode value), original abend reason code (rsncode value), signal code (si_code value in text and decimal), error number (si_errno value), or failing address (si_addr value). |
Action | 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. |
Explanation | WebSphere Application Server for z/OS is terminating the current thread within the current process (address space). |
Action | Look for previous messages to determine why the thread was terminated, or search the information center for the given reason code. |
Explanation | WebSphere Application Server for z/OS is terminating the current process (address space). |
Action | Look for previous messages to determine why the address space was terminated, or search the information center for the given reason code. |
Explanation | The indicated function failed with the given decimal return code. |
Action | 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. |
Explanation | The indicated function failed with the given decimal return code and hexadecimal reason code. |
Action | 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. |
Explanation | WebSphere Application Server for z/OS failed as indicated and that function completed with a decimal return code indicated by RC, a hexadecimal reason code indicated by REASON, and an extended hexadecimal reason code indicated by EXTENDED REASON. |
Action | 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. |
Explanation | 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. |
Action | 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. |
Explanation | 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. |
Action | 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. |
Explanation | 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. |
Action | 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. |
Explanation | 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. |
Action | 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. |
Explanation | 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. |
Action | See the OS/390 C++ Run-Time Library Reference for a description of the code. Correct the address information for the client. |
Explanation | WebSphere Application Server for z/OS experienced a communications error. |
Action | See the WebSphere Application Server for z/OS Error Codes for a description of the error. |
Explanation | WebSphere Application Server for z/OS failed with an internal error. |
Action | See the WebSphere Application Server for z/OS Error Codes for a description of the error. |
Explanation | WebSphere Application Server for z/OS failed with an internal error. |
Action | See the WebSphere Application Server for z/OS Error Codes for a description of the error. |
Explanation | 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. |
Action | 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. |
Explanation | 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. |
Action | Change your trace buffer size specification or your number of trace buffers specification for the next request. |
Explanation | Error occurred inside of Local IIOP processing. Additional information, including the message size, is appended to "[string]" when EMSGSIZE or ENOMEM errors are encountered during IIOP message send. This is an internal programming error. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | A non-zero result was returned from EXEC SQL. |
Action | Refer to DB2 reference books and perform the appropriate actions. |
Explanation | An attempt to FETCH the DSNTIAR module failed. Details of the SQL error code could not be obtained. |
Action | 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. |
Explanation | The data object was asked to update the data store but the KEY values had not been set. |
Action | none. |
Explanation | Class Manager failed to load the specified DLL. The data set containing the DLL might be missing from the STEPLIB for the servant process handling the request. This is an internal programming error. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | Class manager failed to find the specified class in the list of classes supported by the server. If the class not being found is a problem, then an exception is created by the caller of the class manager service. If the caller did create an exception then the application that contains this class might not be properly defined or installed on the server. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | Class Manager failed attempting to get an address for the factory function. This could be caused by improper installation of the class by the application provider. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | WebSphere Application Server for z/OS failed in the context service indicated and that service completed with a hexadecimal return code indicated. |
Action | See return codes for context services in the MVS Programming: Resource Recovery book. |
Explanation | 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. |
Action | See return codes for IXCARM services in the OS/390 MVS Programming: Sysplex Services Reference. |
Explanation | The dispatch method returned indicating that the operation was not executed. |
Action | 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. |
Explanation | 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. |
Action | Check that the application that contains the class name is correctly installed on that server. |
Explanation | The WebSphere Application Server for z/OS OLT DLL was loaded. |
Action | None. |
Explanation | 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. |
Action | 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. |
Explanation | Object Level Trace was enabled, but the DLL could not be loaded. |
Action | Check the installation and usage information for OLT and ensure the OLT DLL is available. |
Explanation | The object level trace (OLT) DLL was loaded but the system could not locate its init routine. OLT could not be started. This is an internal programming error. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | Methods on this class cannot be dispatched because the object was IDL compiled as localonly instead of remotable. |
Action | Recompile your object interface as a remotable object. |
Explanation | The Shasta Runtime was unable to find a class. |
Action | Determine if the desired class name is correct and if it should have been found. If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/ |
Explanation | The Shasta Runtime detected the condition described in this informational message. |
Action | none |
Explanation | The Shasta Runtime detected the condition described in this warning message. |
Action | Determine if this warning message is associated with the occurrence of an exception. If so, investigate the root cause of the exception and correct. |
Explanation | The Shasta Runtime detected the condition described in this error message. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | The Shasta Runtime detected an error while attempting to load a Java implementation class. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | The Shasta Runtime could not find the specified DLL for the Java virtual machine. |
Action | Verify that the LIBPATH environment variable specifies the correct path to the Java virtual machine DLL. |
Explanation | The Shasta Runtime could not establish function pointers required to enable its Java Native Interface (JNI) environment. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | The Shasta Runtime detected that the Java VM was not loaded and initialized. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | The Shasta Runtime has received the given stack trace from the Java VM |
Action | Analyze the exception from within the Java VM stack trace. Determine if the failing method within the Java VM stack trace was from user code, if it is a user application method correct coding errors and retry application. |
Explanation | An incorrect modify command was entered from the operator console. |
Action | 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. |
Explanation | An attempt was made to schedule work using the WLM application environment specified, however the application environment was stopped. |
Action | Determine why the application environment has stopped and if the problem which stopped it has been resolved. Restart it using the V WLM command. |
Explanation | WebSphere Application Server 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. |
Action | 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. |
Explanation | The servant process identified has been stopped and another servant process of the same type is 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. |
Action | None. Active transactions are completed before the space is recycled. The programmer should not see the results of this administrative action. |
Explanation | The servant process has attempted to recycle itself to reclaim storage. It has attempted to call WLM to perform the recycle function but received a return code that indicates that the function cannot be done. |
Action | None. |
Explanation | WebSphere Application Server for z/OS failed with an internal error. |
Action | Search the information center for a description of this error. If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/ |
Explanation | The LOGSTREAM value in the environment file has the following restrictions: 1. A logstream name is made up of 1 or more qualifiers separated by periods, up to the maximum of 26 characters 2. Each qualifier can contain up to 8 numeric, alphabetic, or national ($, #, or @) 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. |
Action | Value is ignored. If you wish to use the value, fix it in the environment file and restart the WebSphere Application Server for z/OS daemon address space. |
Explanation | The logstream name is retrieved from the Systems Management configuration if it is available. This message is issued to notify the user that changing the LOGSTREAMNAME environment variable will not affect where the output is written. Use the Systems Management Administration tool to modify the logstream being used. Remaining characters must be alphanumeric |
Action | None. |
Explanation | During the invocation of the specified system logger service, an error was encountered. The error is indicated by the hexadecimal return code and reason code. |
Action | 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. |
Explanation | The user did not specify a proper system logger stream name as the first parameter to the indicated program. |
Action | Rerun the program specifying the appropriate input. |
Explanation | The user did not specify a proper system logger stream name as the first parameter to the indicated program. Length must be less than or equal to 26 characters in length. |
Action | Rerun the program specifying the appropriate input. |
Explanation | The user did not specify a proper format option as the second parameter to the indicated program. Valid format option values are 80 and NOFORMAT. |
Action | Rerun the program specifying the appropriate input. |
Explanation | Error occurred attempting to open the log stream browse file. |
Action | Verify that the data set exists and is valid. |
Explanation | During the invocation of the specified system logger service, an error was encountered. The error is indicated by the hexadecimal return code and reason code. |
Action | 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. |
Explanation | Error occurred while writing to the log stream browse file. |
Action | Verify that the data set exists and is valid. |
Explanation | Error occurred in program BBORBLOG while processing a log stream. Output contained in the generated browse file might be incomplete. |
Action | Correct the error reported by error message issued previous to this message and rerun the browser program. |
Explanation | The log stream was not created with the required minimum BLKSIZE of 255. Error logging is directed to CERR. |
Action | Have the installation redefine the log stream to conform to the IBM recommended range of 255 to 4096. |
Explanation | CORBA::ImplRepository::find_impldef_by_alias was invoked to find a ImplementationDef for the input server alias but the server alias was not found in the implementation repository. |
Action | Ensure that the server is started before invoking CORBA::ImplRepository::find_impldef_by_alias. |
Explanation | CORBA::ImplRepository::find_impldef was invoked to find a ImplementationDef for the input implid but the implid was not found in the implementation repository. |
Action | Ensure that the server is started before invoking CORBA::ImplRepository::find_impldef. |
Explanation | WebSphere Application Server for z/OS server address spaces cannot start without an active WebSphere Application Server for z/OS 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. |
Action | Start the WebSphere Application Server for z/OS daemon on this system prior to starting other WebSphere Application Server for z/OS servers. |
Explanation | An attempt was made to start a WebSphere 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. |
Action | 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. |
Explanation | 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 already active. Only one Control process of a given specific server name can be active at one time. |
Action | Do not attempt to start two Control processes with the same specific server name at the same time. |
Explanation | 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. |
Action | Do not attempt to start two Control processes with the same specific server name at the same time. |
Explanation | When WebSphere Application Server for z/OS 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. |
Action | The system might be slow or there may be a problem which is preventing the indicated server from starting. You might be able to determine the cause of the problem and correct it before the timeout expires. |
Explanation | When WebSphere Application Server for z/OS 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. |
Action | The system might be slow or there may be a problem which is preventing the indicated server from starting. You might be able to determine the cause of the problem and correct it before the timeout expires. |
Explanation | When WebSphere Application Server for z/OS 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 might create exceptions and terminate other processing that required this server to start. |
Action | The system might 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. |
Explanation | This PPT entry must be specified to run the program. |
Action | 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. |
Explanation | This PPT entry should not be specified to run the program. |
Action | 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. |
Explanation | This entry is specified incorrectly to run the program. |
Action | 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. |
Explanation | This PPT entry must be specified to run the program. |
Action | 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. |
Explanation | This PPT entry should not be specified to run the program. |
Action | 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. |
Explanation | This entry is specified incorrectly to run the program. |
Action | 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. |
Explanation | During dispatch of a method, the WebSphere Application Server for z/OS ORB caught a system exception. |
Action | 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. |
Explanation | During dispatch of a method, the WebSphere Application Server for z/OS ORB caught a user exception. |
Action | 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. |
Explanation | During dispatch of a method, WebSphere Application Server for z/OS ORB caught something other than a system or user exception. |
Action | 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. |
Explanation | The logstream being browsed contains no data. |
Action | Verify the logstream name. |
Explanation | The user trying to browse the logstream does not have READ access to the logstream. |
Action | Issue the appropriate RACF commands to give the user READ access to the logstream. |
Explanation | The log stream name specified has not been defined in the LOGR policy. |
Action | Ensure that the required log stream name has been defined in the LOGR policy. |
Explanation | 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. |
Action | 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. |
Explanation | 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. |
Action | 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. |
Explanation | GIOP reply message was received, but no corresponding request could be found. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | Found NULL when looking up classname in ptable in encode_objref() |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | The value specified to the ORB_init() function for the ORBid keyword must be BOSS. No other value is accepted. |
Action | Specify a valid value for ORBid |
Explanation | The ORBid keyword to ORB_init() must be specified with a value. |
Action | Specify a valid value for ORBid |
Explanation | The ORBsrvname keyword to ORB_init() must be specified with a value. |
Action | Specify a valid value for ORBsrvname |
Explanation | The ORBType keyword to ORB_init() must be specified with a value. |
Action | Specify a valid value for ORBType |
Explanation | 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 HFS in the same directory used by the procedure to start the server. |
Action | Determine where the load module is. Update the procedure used to start the server and restart the server. |
Explanation | 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. |
Action | Make sure RRS is started and restart the server |
Explanation | The ORBCBI keyword to ORB_init() must be specified with a valid value (one of COLD, WARM, or HOT). |
Action | Specify a valid value for ORBCBI |
Explanation | The ORBCBI keyword to ORB_init() must be specified with a value (one of COLD, WARM, or HOT). |
Action | Specify a valid value for ORBCBI |
Explanation | 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. |
Action | Either the named server has simply already ended in which case no action is required or there is some problem with the server which might 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 might be. Specific server name is a parameter provided to the server when it is started. |
Explanation | 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. |
Action | None. |
Explanation | The modified MVS Stop command has been issued against a WebSphere Application Server for z/OS address space. |
Action | None. |
Explanation | The MVS Modify command has been issued to cancel a WebSphere Application Server for z/OS address space requesting ARM restart. |
Action | None. |
Explanation | The MVS Modify command has been issued to cancel without restart against a WebSphere Application Server for z/OS address space. |
Action | None. |
Explanation | A Stop command has been issued for the WebSphere Application Server for z/OS 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. |
Action | Once the daemon has stopped and has, if desired, been restarted, you might try again to start this server. |
Explanation | The address space for where the PC was targeted has ended. This is an informational message. |
Action | None. |
Explanation | When WebSphere Application Server for z/OS 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 is 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. |
Action | The system might be slow or there may be a long running transaction on the indicated server which is preventing the server from stopping. You might be able to determine the problem and allow the server to stop before the timeout expires. |
Explanation | When WebSphere Application Server for z/OS 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 is 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. |
Action | The system might be slow or there may be a long running transaction on the indicated server which is preventing the server from stopping. You might be able to determine the problem and allow the server to stop before the timeout expires. |
Explanation | When WebSphere Application Server for z/OS 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 is issued to indicate that more time has passed waiting for this server to stop that seems reasonable. WebSphere will give up waiting and might create exceptions and terminate other processing that required this server to stop. |
Action | The system might 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 or the server. |
Explanation | The indicated class contains the indicated method, which is not implemented. |
Action | Do not call this method for an instance of an object of this class. |
Explanation | 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. |
Action | See the OS/390 eNetwork Communication Server books for descriptions of the returned value and codes. |
Explanation | 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. |
Action | 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. |
Explanation | When ARM detects a failure it will restart the server. This message is informing you that an ARM restart is occurring. |
Action | No action is required. This message is just informational and might assist in debugging restart error scenarios. |
Explanation | During registration with ARM the ARM couple dataset has become full. The ARM registration fails and the server continues to come up. |
Action | Because WebSphere Application Server for z/OS has several address spaces registering with ARM you might 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. |
Explanation | During registration with ARM the name used was already registered somewhere else in the sysplex. The server continues to come up. |
Action | 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. |
Explanation | 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 might experience additional errors due to its dependent servers not being ready. |
Action | 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. |
Explanation | 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 might experience additional errors due to its dependent servers not being ready. |
Action | In general you should investigate what is causing the address spaces not being registered |
Explanation | 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 might experience additional errors due to its dependent servers not being ready. |
Action | 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. |
Explanation | The MVS STOP console command or the System Managment EUI STOP command has already been issued for this server. Subsequent commands are ignored. |
Action | Wait for the current stop processing to complete or escalate to an EUI Cancel or MVS console Modify Cancel command. |
Explanation | The MVS Modify Cancel console command or the System Managment EUI Cancel command has already been issued for this server. Subsequent commands are ignored. |
Action | Wait for the current cancel processing to complete |
Explanation | The MVS Stop and Modify commands are not supported by servant processes. You might shut down servant processes either by stopping their owning control process or through the use of the VARY WLM command. |
Action | The command is ignored, consider one of the alternatives described in the Explanation. |
Explanation | Before WebSphere Application Server for z/OS could successfully connect to the log stream, there were a number of messages to be recorded which had to be redirected to CERR. |
Action | Check job log for messages. |
Explanation | 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. |
Action | The most probable causes of this error are: a dataset in the STEPLIB of the daemon's proc is not in the APF list; or the PPT settings for the BBODAEMN load module are not correct. The PPT settings for the BBODAEMN load module should contain the settings listed in the BBOSCHED member in the CNTL dataset. The BBOSCHED member in the CNTL dataset is generated from the Customization Dialogs. The customization instructions for updating the SCHEDxx member in SYS1.PARMLIB are documented in BBOINSTR. |
Explanation | 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. |
Action | The most probable causes of this error are: a dataset in the STEPLIB of the controller's procedure is not in the APF list; or the PPT settings for the BPXBATA2 load module are not correct. |
Explanation | A message was issued that requires more than 10 lines. This message is issued to continue displaying the data for the indicated message 9 lines at a time. |
Action | None. |
Explanation | JVM exit API has been driven with the specified error code, indicating that the JVM is ending abnormally. |
Action | Look for other accompanying error messages in the error log |
Explanation | The JVM abort API has been driven. |
Action | Look for other accompanying error messages in the error log. |
Explanation | Threads of a type restarted 5 or more times. |
Action | None. |
Explanation | 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. |
Action | 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. |
Explanation | 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. |
Action | 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. |
Explanation | 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). |
Action | 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. |
Explanation | Failed attempting to get an address for the function. The load module does not contain the function. |
Action | 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. |
Explanation | 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. |
Action | 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. |
Explanation | ARM registration failed with a return code of 8 and a reason code of 5B8. The restart of the server exceeded the length of time that the ARM facility will wait for it. The restart of the server will continue; however the server is no longer registered with ARM. |
Action | If you want the server that issued this message to be restarted by ARM in the event of a failure, then you must stop and restart it. |
Explanation | WebSphere Application Server for z/OS servant process address spaces cannot start without the Control process they are associated with being active on the same system. The server that attempted to start was unable to find its owning Control process whose name is given in the message text. The servant process terminates. |
Action | 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. |
Explanation | The size of the response to be sent from the servant process back to the client exceeded the maximum length for local IIOP messages. |
Action | Try sending a smaller message. |
Explanation | 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. |
Action | This message is provided to document that the server was unable to respond to a client. This might be because the client has gone away, but it might 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. |
Explanation | 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. |
Action | 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 host name to find if a system exception was returned which might be related to the reported problem. |
Explanation | Signal handler invoked CEE3DMP which failed. |
Action | See CEE3DMP documentation for a description of the message number. Often the failure is caused by an incorrect option specified in the BBODUMP_CEE3DMP_OPTIONS environment variable. |
Explanation | Each control process is configured to run on a specific system in the sysplex. If a control process is started on a different system than it is configured to run on, then it is assumed to be attempting to release locks and resolve in doubt work caused by a failure of the system on which this control process normally runs. After that work is complete, the control process will automatically terminate. |
Action | 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. |
Explanation | Each control process is configured to run on a specific system in the sysplex. When a control process is started out-of-place it attempts to release locks and resolve in doubt work caused by a failure of the system on which it usually runs. It is not expected that a servant process would need to be started to do this processing, however servant processes are not prohibited from starting. This message is is issued simply to note the fact that one started. |
Action | None |
Explanation | This message is the response to the operator modify display command. The first two fill-in strings are the generic and specific server name for the server. The third fill-in string is the system name where the server is active. The fourth fill-in string is the IBM internal name for the code level the server is running. The fifth and final fill-in might 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 is blank. |
Action | None |
Explanation | Only a limited number (presently 100)of specific trace points might be turned on. More than that have been specified. This and any future specific trace points specified will not be activated. |
Action | Restart the control process or use the TRACENONE option to clear the specific trace points and start over. |
Explanation | Processing the TRACESPECIFIC option an open parenthesis was found indicating a list of trace points follows. However, no close parenthesis was found to indicate the end of the list. |
Action | Retry setting the trace value using a right parenthesis to close the list. |
Explanation | All trace points specified to TRACESPECIFIC must be eight digits long. End of data, a comma, or a close parenthesis was found before the final digit of a trace point was found. |
Action | Ensure all trace points specified contain eight hex digits. |
Explanation | All trace points specified to TRACESPECIFIC must be in hexadecimal. A non-hexadecimal value (i.e. not 0-9,A-F) was found processing a trace point value. |
Action | Ensure all trace points specified contain eight valid hex digits. |
Explanation | In response to a Modify or Display command requesting help with the syntax, this message is issued followed by the following message which lists all the valid keywords which might be placed at this point in the command. |
Action | None |
Explanation | This message is issued repeatedly in response to a Modify or Display command requesting help with the syntax. Each occurance identifies a valid keyword which might be issued at this point in the command. |
Action | None |
Explanation | The last keyword specified in the command shown is unrecognized. A list of valid keywords is shown in messages following this one. |
Action | Issue the command again using a valid keyword |
Explanation | The display command takes numerous options which are separated from the display keyword by commas. |
Action | Issue the command again with a comma following the 'display' keyword. |
Explanation | This message acts as a header for the response to the DISPLAY,SERVERS command. |
Action | None |
Explanation | This message repeats in response to the DISPLAY,SERVERS command, once per active server. The columns, as shown in the header, indicate the generic and specific server names, the ASID (in hex) of the server control process, the system name where the server is active, the code level of the server, and the current state of the server. The following is the list of the valid states: "ACTIVE" -- the server is up and running; "ENDING" -- the server has begun to terminate; "PAUSED/STOPPING" -- the server has a set of listeners in the paused state or is stopping; "RECOVERY" -- the server is running out of place for transaction recovery. |
Action | No action is required. |
Explanation | This message is issued in response to the DISPLAY,SERVANTS command to indicate that the control process which received the command has no active servant processes. |
Action | None |
Explanation | This message is issued in response to the DISPLAY,SERVANTS command to indicate the number of servant processes which are active under the control process which received the display command. The ASIDs (in hex) of the servant processes are then listed unless there are too many to list in which case text is placed in the message to indicate this. |
Action | None |
Explanation | The indicated command was issued with additional keywords provided beyond what is shown. These additional keywords are not required and should not be used. |
Action | Reissue the command without the extraneous keywords |
Explanation | This message is issued in response to the DISPLAY,SERVERS command when there are no servers active besides the daemon. |
Action | None |
Explanation | At the end of every display command, this message is issued to indicate completion of processing for the command. The purpose of this message is to enable automation to find the end of the output for a display command it issued. |
Action | None |
Explanation | This message is issued in response to the DISPLAY,SESSIONS or DISPLAY,SESSIONS,LISTENERS command. It is the header for the response and identifies the generic and specific server names for the control process which received the command. |
Action | None |
Explanation | This message repeats as the body of the reply to the DISPLAY,SESSIONS or DISPLAY,SESSIONS,LISTENERS command. Each line indicates the protocol and the port number on which this server listens for that protocol. |
Action | None |
Explanation | This message is issued in response to the DISPLAY,SESSIONS,SERVER command. It acts as the header for the response and identifies the generic and specific names for the control process which received the command. |
Action | None |
Explanation | This message repeats as the body of the reply to the DISPLAY,SESSIONS,SERVER command. Each line indicates a protocol and the number of server sessions which exist for that protocol. |
Action | None |
Explanation | This message is issued in response to the command DISPLAY,SESSIONS,SERVER,xxxx where xxxx is one of the valid protocols for which information can be requested. Use the DISPLAY,SESSIONS,SERVER,HELP command to get a list of valid protocols. This message identifies the generic and specific server names of the control process which received this command and the count of server sessions for the protocol. The protocol name specified is the final fill-in value. |
Action | None |
Explanation | This message 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 that received this command and the count of server sessions for the protocol. The protocol name specified is the final fill-in value. |
Action | None |
Explanation | This message repeats as the response to the command DISPLAY,SESSIONS,SERVER,xxxx,LIST where xxxx is one of the valid protocols for which information can be requested. Use the DISPLAY,SESSIONS,SERVER,HELP command to get a list of valid protocols. The message identifies the host name and port number of the client connected to this server session, or, in the case of local clients, the jobname and ASID. |
Action | None |
Explanation | This message acts as the header to the response to the DISPLAY,TRACE command. It identifies the generic and specific server names for the control process processing the command. |
Action | None |
Explanation | This message repeats as the body of the response to the DISPLAY,TRACE command. It might 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. |
Action | None |
Explanation | The Modify command was issued with a keyword which must be followed by an equal sign and some value. No equal sign was found. |
Action | Reissue the command with an equals sign following the keyword. |
Explanation | A modify command was issued with a keyword which required no additional keywords, however more text was supplied on the command. |
Action | Reissue the command without the extraneous text. |
Explanation | A modify command was issued with a keyword which requires an equal sign followed by some value. No value was found after the equal sign. Reissue the command specifying a value of HELP after the equal sign for a list of valid responses. |
Action | Reissue the command with a valid value after the equal sign. |
Explanation | This message acts as the header to the response to the DISPLAY,JVMHEAP command. It identifies the generic server name, the specific server name, and the JES job prefix for the control or servant process processing the command. |
Action | None |
Explanation | This message repeats as the body of the response to the DISPLAY,JVMHEAP command. The message displays information that is retrieved from the JNI method QueryGCStatus. |
Action | None |
Explanation | The Shasta runtime could not load the specified DLL for the Java virtual machine. |
Action | Verify that the LIBPATH environment variable specifies the correct path to the Java virtual machine DLL. Verify that the target DLL is APF authorized. |
Explanation | This message acts as the trailer to the response to the DISPLAY,JVMHEAP command. It identifies the generic server name, the specific server name, and the JES job prefix for the control or servant process processing the command. |
Action | None |
Explanation | When specifying trace points, a trace group name might 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 quotation marks. A single quotation mark was found indicating the beginning of the trace group name, but no matching closing single quotation mark was found to indicate the end of the trace group name. |
Action | Use a closing single quotation mark to indicate the end of the trace group name. |
Explanation | When specifying trace points, a trace group name might 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 quotation marks. 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 quotation mark 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. |
Action | The closing quotation mark of a trace group name must be followed by a comma or a closing parenthesis. |
Explanation | When specifying trace points, a trace group name might 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 quotation marks. The environment variable specified is either undefined or is defined to nothing (i.e. TGROUP1= ). |
Action | 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. |
Explanation | When specifying trace points, a trace group name might 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 might be defined. |
Action | Specify the trace points you want in fewer layers of groups or examine your trace group names for errors producing a circular list. |
Explanation | The display command syntax consists of keywords separated by commas. A command ending in a comma is not valid. Some valid keyword must follow the comma. |
Action | Provide a valid keyword after the comma |
Explanation | You must specify either YES or NO to turn tracing to sysprint on or off. |
Action | Provide a valid value |
Explanation | Trace related modify commands issue this message when processing in the control process is completed. If the command did not complete successfully, previous messages will indicate the error encountered. |
Action | None. |
Explanation | A value for TRACEALL, TRACEBASIC or TRACEDETAIL was specified which is not valid. |
Action | Specify valid values for the indicated variable. |
Explanation | The specified trace point has caused execution for the specified TCB to stop until this WTOR is responded to as the result of special trace options being set. |
Action | Respond to the WTOR when you are ready for the thread to continue. |
Explanation | The message consists of the header for the indicated trace point as written to sysprint. |
Action | None. |
Explanation | The specified product was successfully registered with the IFAED service, as described in the publication: z/OS V1R7.0-V1R8.0 MVS Product Registration, SA22-7604. |
Action | None. |
Explanation | The specified product failed to register with the IFAED service. |
Action | See the publication z/OS V1R7.0-V1R8.0 MVS Product Registration, SA22-7604, for an explanation of the return code. |
Explanation | WebSphere Application Server for z/OS was unable to open the file specified by the environment variable BBOC_HTTPALL_BBOC_HTTPALL_TCLASS_FILE. |
Action | Make sure the file is correctly specified and the permissions are correct. |
Explanation | WebSphere Application Server for z/OS detected parse errors in the file specified by the environment variable BBOC_HTTPALL_BBOC_HTTPALL_TCLASS_FILE. |
Action | Check the WebSphere Application Server for z/OS error log for details. |
Explanation | WebSphere Application Server for z/OS detected a syntax error with the TransClassMap entry at the specified line of the file specified by the environment variable BBOC_HTTPALL_BBOC_HTTPALL_TCLASS_FILE. |
Action | Make sure the file is correctly specified and the permissions are correct. |
Explanation | Java code ported from another platform might issue messages which do not conform to z/OS message conventions. In that case, error messages are wrapped with this message to ensure compliance. |
Action | For more information about this message, refer to the WebSphere Application Server Server for z/OS Information Center. |
Explanation | Java code ported from another platform might issue messages which do not conform to z/OS message conventions. In that case, warning messages are wrapped with this message to ensure compliance. |
Action | For more information about this message, refer to the WebSphere Application Server for z/OS Information Center. |
Explanation | Java code ported from another platform might issue messages which do not conform to z/OS message conventions. In that case, informational messages are wrapped with this message to ensure compliance. |
Action | For more information about this message, refer to the WebSphere Application Server for z/OS Information Center. |
Explanation | Java code ported from another platform might 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. |
Action | For more information about this message, refer to the WebSphere Application Server for z/OS Information Center. |
Explanation | This message acts as the header to the response to the DISPLAY,TRACE command. It identifies the generic and specific server namesand the JES job prefix for the control or servant process. |
Action | None |
Explanation | This message acts as the trailer to the response to the DISPLAY,TRACE command. It identifies the generic server name, the specific server name, and the JES job prefix for the control or servant process processing the command. |
Action | None |
Explanation | In order for the WebSphere Application Server for z/OS daemon to start properly, the daemon GROUP NAME environment variable must be set. |
Action | Set the DAEMON GROUP NAME environment variable. |
Explanation | In order for the WebSphere Application Server for z/OS server to start properly, the DAEMON GROUP NAME environment variable must be set. |
Action | Set the DAEMON GROUP NAME environment variable. |
Explanation | In order for the WebSphere Application Server for z/OS server to start properly, the daemon for the daemon group must be active. |
Action | Ensure the daemon for the daemon group is active before starting the server. |
Explanation | WebSphere Application Server for z/OS could not load the specified DLL. |
Action | 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. |
Explanation | 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. |
Action | Determine where the load module is and fix STEPLIB, LPA or Linklist so that the correct version is loaded. Restart the server after fixing the problem. |
Explanation | 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. |
Action | None. |
Explanation | A request has timed out that was associated with a servant process. The associated servant process is 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. |
Action | Examine the application for possible coding errors which might have lead to delays. |
Explanation | The system rejected the request to trace the SYSBBOSS component. The TRACE command specified options, but options are not allowed (except for option WTR). |
Action | Reenter the TRACE command specifying no options or the WTR option. |
Explanation | Indicates the number of worker threads present in the servant process. |
Action | None |
Explanation | Indicates the inet_addr function returned the value INADDR_NONE due to a bad IP address being supplied to the function. The IP address is taken from the IIOP listen IP address in the configuration. This error can occur if the specified address is not a valid dotted decimal address. |
Action | Verify the IIOP listener IP address is a valid IP address |
Explanation | In response to a shutdown of Unix System Services, the daemon is stopped. |
Action | None. |
Explanation | The WebSphere Application Server for z/OS daemon address space is starting with cell long name/ node long name /server long name |
Action | None. |
Explanation | The WebSphere Application Server for z/OS application control process address space is starting with cell long name/ node long name/server long name |
Action | None. |
Explanation | The WebSphere Application Server for z/OS application servant process address space is starting with cell long name/ node long name /server long name |
Action | None. |
Explanation | You must specify either YES or NO to turn tracing to trcfile on or off. |
Action | Provide a valid value |
Explanation | Could not open specified jvm_logfile. |
Action | Correct the variable setting and re-start WebSphere Application Server for z/OS. |
Explanation | Daemon / Control / Server region is starting and is delayed because GQSCAN returned RC=0xC, RSN=0xC so the region is unable to determine the state of required ENQs. Start of the region is delayed until GRS is able to provide an answer. See MVS Programming: Authorized Assembler Services Reference, Volume 2, for more information on the GQSCAN macro. |
Action | none. |
Explanation | Control region could not obtain storage for the HTTP large data input buffer. |
Action | 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. |
Explanation | Control region did not allocate a HTTP large data input buffer because the requested length is not greater than the large cpool cell size. |
Action | If the buffer is required, increase the value specified on the protocol_http_large_data_inbound_buffer variable and re-start the server. |
Explanation | WebSphere Application Server for z/OS issued the bind function which failed. Message BBOO0142E provides more details about the failure. The bind will retry once on a random available port. |
Action | 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 Application Server for z/OS servers across the entire sysplex. When the configured port is not available, WebSphere will attempt to use another available port, but this might 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. |
Explanation | Initialization is complete for the WebSphere Application Server for z/OS daemon indicated. The process name strings are cell name, node name, cluster name, and server name. |
Action | None. |
Explanation | 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, and server name. |
Action | None. |
Explanation | 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, and server name. |
Action | None. |
Explanation | 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. |
Action | 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. |
Explanation | 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. |
Action | None |
Explanation | The multi-product PTF post installer encountered an unrecoverable 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. |
Action | None |
Explanation | The post installer detected that there is "batch" service pending and the post installer was launched in "inline" mode. The applyPTF.sh shell script must be launched directly from the shell or from the BBOWAPLY job from a user id that has the proper authority. |
Action | None |
Explanation | Control region did not allocate a HTTP large data response buffer because the requested length is not greater than the default size. |
Action | If the buffer is required, increase the value specified on the protocol_http_large_data_response_buffer variable and re-start the server. |
Explanation | Control region could not obtain storage for the HTTP large data response buffer. |
Action | 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. |
Explanation | This message is part of the response to a display,work command. Subsequent messages might 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. |
Action | None |
Explanation | This message shows the total number of requests of type string received by the controller. The delta is the difference between the total shown here and the total at the time of the previous display,work command. Note that display,work command processing is not serialized with respect to running work so the calculated delta might not be the exact difference between the value shown here and on the previous display,work command. |
Action | None |
Explanation | This message shows the total number of requests of type string currently being processed by this server. The request might 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. |
Action | None |
Explanation | This message shows the number of requests of type string currently running in a servant of this server. Note that 'in dispatch' means 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. |
Action | None |
Explanation | This message shows the total number of requests of the indicated type received by the servant whose jobid preceeds the colon. The delta is approximately the difference in this value since the last display,work command was issued. Note that display,work command processing is not serialized with respect to running work so the calculated delta might not be the exact difference between the value shown here and on the previous display,work command. |
Action | None |
Explanation | This message shows the total number of requests of the indicated type being processed currently by the servant whose jobid preceeds the colon. |
Action | None |
Explanation | This message shows the total number of requests received by the controller. The delta is the difference between the total shown here and the total at the time of the previous display,work command. Note that display,work command processing is not serialized with respect to running work so the calculated delta might not be the exact difference between the value shown here and on the previous display,work command. |
Action | None |
Explanation | This message shows the total number of requests currently being processed by this server. The request might dispatch in a servant or might 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. |
Action | None |
Explanation | This message shows the number of requests currently dispatched in a servant of this server. 'IN DISPATCH' means 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 of a request's execution status. |
Action | None |
Explanation | This message shows the total number of requests received by the servant whose jobid preceeds the colon. The delta is approximately the difference in this value since the last display,work command was issued. Note that display,work command processing is not serialized with respect to running work so the calculated delta might not be the exact difference between the value shown here and on the previous display,work command. |
Action | None |
Explanation | This message shows the total number of requests being processed currently by the servant whose jobid preceeds the colon. |
Action | None |
Explanation | This message is issued in response to the DISPLAY ERRLOG command and contains a copy of a message written to the WebSphere Application Server for z/OS Error Log. The value in parenthesis is the job ID of either the controller or the servant where the message was issued. |
Action | None |
Explanation | This message shows the total number of requests of type string timed out. The delta is the difference between the total shown here and the total at the time of the previous DISPLAY,WORK command. Note that DISPLAY,WORK command processing is not serialized with respect to running work so the calculated delta might not be the exact difference between the value shown here and on the previous DISPLAY,WORK command. |
Action | None |
Explanation | This message shows the total number of requests timed out by the controller. The delta is the difference between the total shown here and the total at the time of the previous display,work command. Note that display,work command processing is not serialized with respect to running work so the calculated delta might not be the exact difference between the value shown here and on the previous display,work command. |
Action | None |
Explanation | This message is issued due to bind failure because the port was already in use. |
Action | Change the port number to one that is available. |
Explanation | Controller could not read entire HTTP request, input buffer exceeded. |
Action | 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. |
Explanation | Controller needed the HTTP Large data input buffer to read in a large HTTP request but it was currently in use for another request. |
Action | Try request again. |
Explanation | WebSphere Application Server for z/OS was unable to open the file specified by the environment variable protocol_https_default_cert_label. |
Action | Make sure the file is correctly specified and the permissions are correct. |
Explanation | WebSphere Application Server for z/OS detected parse errors in the file specified by the environment variable protocol_https_default_cert_label. |
Action | Check the WebSphere Application Server for z/OS error log for details. |
Explanation | 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. |
Action | Correct the syntax error and restart server. |
Explanation | A call to create_proxy returned a NULL |
Action | Ensure that the DLL for the class is in the steplib or linklist |
Explanation | The multi-product PTF installer has has detected that there are post SMP/E installation actions to be completed for WebSphere Application Server for z/OS or for an installed WebSphere extension product. |
Action | None. |
Explanation | WebSphere Application Server for z/OS Multi-Product PTF installer has completed it's actions and has ended normally. |
Action | None. |
Explanation | The multi-product PTF post installer detected warning(s)issued during the application of post-install service. The warning(s) might 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. |
Action | 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. |
Explanation | Reply to a previous message was not valid. The previous message is reissued. |
Action | Issue a valid reply to the reissued message. |
Explanation | This is the header message for informational messages showing useage counts for work classification rules |
Action | none |
Explanation | 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. |
Action | none |
Explanation | 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 total weighted cost of using the classification rules. The total weighted cost of the classification rules is equal to the sum of the weighted costs of all the rules. The weighted cost of an individual rule is calculated as the number of times the rule was used multiplied by the cost of using the rule. The cost of using a rule is equal to the number of rule comparisons required to classify a request with the rule. 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). |
Action | none |
Explanation | 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. |
Action | If statistics are desired for requests of type string, then enable statistics gathering by using the MODIFY STATS command (for example: F BBOS001,MDBSTATS,ENABLE). |
Explanation | The post installer detected that the configured root is at a higher service level than the installation root - message "BBOO0249E" will have been issued. |
Action | Reply with 'CONTINUE' to continue starting the Application Server even though the configured root is at a higher service level than the installation root. Reply with 'CANCEL' to cancel starting the Application Server. Normally, 'CANCEL' should be issued and the correct service level should be applied by following the "BBOO0249E" message instructions. |
Explanation | The post installer has detected one or more pending post-install actions that are backward incompatible. This means that, if you apply this service and then need to SMP/E back out, you must use the "backoutPTF.sh" shell script to back out the service prior to SMP/E restoring off. You might also save a backup copy of the current WebSphere Application Server for z/OS home HFS directory that you can restore after completing the SMP/E restore off and before starting the server. |
Action | Reply 'CONTINUE' to continue applying post- install service. Reply 'CANCEL' to cancel application of the post-install service, which also cancels the start of the Application Server. You must apply all post-install service before the server will start. This means you will receive this prompt every time you start the server until you either choose 'CONTINUE' or use SMP/E to return to the previous service level. |
Explanation | The server has been restarted on a system other than the one on which it was configured to run. The PTF level on this system and the configured system are different. The server might not be able to start on this system. |
Action | Reply CONTINUE to the WTOR if you are willing to accept the risk associated with starting the server on this system, or CANCEL if you would like the server to terminate. Refer to the documentation on Peer Restart and Recovery in the WebSphere Application Server Information Center for more information on the risks associated with starting the server out of place at mixed PTF levels. |
Explanation | 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, and server name. |
Action | None. |
Explanation | 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. |
Action | None. |
Explanation | 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. |
Action | "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. |
Explanation | Initialization is complete for the WebSphere Application Server for z/OS adjunct address space for the server indicated. |
Action | None. |
Explanation | 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, and server name. |
Action | None. |
Explanation | The WebSphere Application Server for z/OS adjunct address space is starting with cell long name/ node long name /server long name |
Action | None. |
Explanation | 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. |
Action | None. |
Explanation | The value specified to the ORB_init() function for the REC=(N|Y) parameter is not valid. The only acceptable values are REC=N and REC=Y. |
Action | Specify a valid value for REC=(N|Y) |
Explanation | The target address space for which the Program Call (PC) was targeted has ended. This is an informational message. |
Action | None. |
Explanation | The server has detected that its last servant has terminated. All servant work is rejected until a valid reply is received and a servant is available. The server name strings are cell name, node name, and server name. |
Action | Reply "CONTINUE" to indicate that the condition which caused the servant to terminate has been resolved. The server will allow servant work once an available servant is detected. |
Explanation | 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. |
Action | 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. |
Explanation | The server has detected that its last servant has terminated. Work targeted to a servant is rejected. The server name strings are cell name, node name, and server name. |
Action | None. The server will allow servant work once an available servant is detected. |
Explanation | 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. |
Action | None. |
Explanation | 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. All attempts have failed; further attempts have been canceled. The server name strings are cell name, node name, and server name. |
Action | None. The server is actively processing another event that requires the same manipulation of the server. |
Explanation | Various Local Data Area storage info. "REGION REQUESTED" is the storage region allocated to the address space, indicated in kilobytes. The "BELOW/ABOVE LINE" limits are given in megabytes. The "LINE" is the boundary between 24-bit and 31-bit storage addresses. The "BELOW/ABOVE" limits indicate the actual storage limits for addresses below the line (24-bit addresses) and addresses above the line (31-bit addresses). The "ABOVE BAR FREE/ALLOC ADDR" values are not meaningful and can be ignored. |
Action | None. |
Explanation | 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. |
Action | None. |
Explanation | The server could not retrieve the JVMExtension interface from the JavaVM. |
Action | None. |
Explanation | 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). |
Action | Determine where the load module is and whether it should be in a STEPLIB, LPA or Linklist, correct the problem and restart the server. |
Explanation | Displays the addressing mode of the executing process |
Action | None |
Explanation | Displays the addressing mode of the executing process |
Action | None |
Explanation | Displays the addressing mode of the executing process |
Action | None |
Explanation | Displays the addressing mode of the executing process |
Action | None |
Explanation | A timeout has been detected. The servant with the asid and stoken is abended in the specified number of seconds. Number of seconds to delay is controlled by the control_region_timeout_delay environment variable. |
Action | None. |
Explanation | A timeout has been detected. The servant with the asid and stoken is being abended. |
Action | Look for other messages, errors and dumps to help determine the cause of the timeout. |
Explanation | The use of the specified configuration variable has been deprecated. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | The display session commands have been replaced with a similar set of display connections commands. |
Action | None |
Explanation | This message is issued in response to the DISPLAY,LISTENERS command. It is the header for the response. It identifies the cell name, the node name, the generic server name, and the specific server name for the control region address space that received the command. |
Action | None |
Explanation | 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. |
Action | None |
Explanation | This message is issued in response to the DISPLAY,CONNECTIONS command. It is the header for the response. It identifies the cell name, the node name, the generic server name, and the specific server name for the control region address space that received the command. |
Action | None |
Explanation | 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. |
Action | None |
Explanation | This message is the body of the reply to the DISPLAY,CONNECTIONS,NAME= command when the specified name could not be found. |
Action | Ensure the name was entered properly. If the name contains lower case characters, then enclose the name in single quotation marks. For example: NAME='lowercase' |
Explanation | This message repeats in the body of the reply to the DISPLAY,CONNECTIONS,LIST command. Each line indicates the connection instance name. |
Action | None |
Explanation | This message repeats in the body of the reply to the DISPLAY,CONNECTIONS,LIST command. Each line indicates remote host information of the connection. |
Action | None |
Explanation | This message is the body of the reply to the DISPLAY,CONNECTIONS,LIST,NAME= command when the specified name could not be found. |
Action | Ensure the name was entered properly. If the name contains lower case characters, then enclose the name in single quotation marks. For example: NAME='lowercase' |
Explanation | 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 are accepted. Once this message is issued, it will not be issued again until the total number of connections is below 85% the maximum. |
Action | None |
Explanation | 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 might fail to initialize. |
Action | None |
Explanation | An outbound IIOP request or locate from a servant process has timed out. The "to" string identifies the target server for the request. For servers using TCP/IP the host name and port number will appear in the message. For a local server, this field contains the jobname and ASID of the server address space. A Request/Reply are uniquely identified by the SessionHandle and Request ID. |
Action | Examine the target server for possible errors which might have lead to delays. If a corresponding BBOO0328I message with matching SessionHandle and Request ID is found indicating that the response to the request was received after the request timed out, then the Request Timeout configuration value could be extended such that the response can be received within the Request Timeout period. |
Explanation | The server will bind specifically to one IP address, but the host name resolved to multiple addresses. The server picked one address to bind to. |
Action | 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. |
Explanation | 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. If the request was not dispatched to the servant, then the servant TCB address and servant ASID fields in the message are zero and the time request dispatched in servant field is empty. |
Action | None. |
Explanation | GIOP reply message was received, but no corresponding request could be found. |
Action | Look for other messages, errors and dumps to help determine the cause of this message. This might 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. |
Explanation | The server cannot be started using 31-bit addressing mode. |
Action | If you did not intend to start a 31-bit server, then restart the server in 64-bit mode (with the AMODE=64 parameter). |
Explanation | The server cannot be started using 64-bit addressing mode. |
Action | If you did not intend to start a 64-bit server, then restart the server in 31-bit mode (without the AMODE=64 parameter). |
Explanation | 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 |
Action | None. |
Explanation | The specified product was successfully registered with the IFAUSAGE service. |
Action | None. |
Explanation | The specified product failed to register with the IFAUSAGE service. |
Action | None. |
Explanation | During initialization of a WebSphere Application Server for z/OS server, CSVDYLPA was called to let the system know where in LPA the product module exists. The call to CSVDYLPA failed. The message contains the return code, hexadecimal reason code, error data and LpmeaOutputInfo returned by the CSVDYLPA service. LPMEAOUTPUTINFO is 2 bytes of flags followed by a 4 byte return and 4 byte reason code or 4 byte abend code and 4 byte abend reason code all in hexadecimal. The flags which are mapped by LpmeaOutputFLAGS indicate how to interpret the next 8 bytes which are mapped by the LpmeaStuff section of the CSVLPRET data area. The server terminates. |
Action | Determine why CSVDYLPA failed. Correct the problem and restart the server. |
Explanation | During initialization of a WebSphere Application Server for z/OS server, an attempt was made to load the product or jvm module whose name is in the message text. The load module was not found. The server terminates. The product load module should be in the HFS in the same directory used by the procedure to start the server. The jvm load module should be found in a subdirectory off the JAVA_HOME environment variable defined in was.env. The load service used is shown in the message text, along with the failing return code and reason code from that load service. |
Action | Use the return code and reason code from the listed load service to determine why the load failed, correct the problem and restart the server. |
Explanation | The server cannot be started using the requested addressing mode. |
Action | Restart the server with AMODE=31 for a server that is configured to run in 31 bit mode or AMODE=64 for a server that is configured to run in 64 bit mode or do not specify the AMODE= parameter to have the server start based on how it is configured. |
Explanation | A WebSphere Application Server for z/OS application process address space was started but the required libpath variable could not be found in was.env. The STDENV DD statement in the procedure used to start the process has the location of was.env. For a controller process control_region_libpath must be set in was.env. For a servant process server_region_libpath must be set. For an adjunct process adjunct_region_libpath must be set. |
Action | Correct the problem and restart the server. |
Explanation | A WebSphere Application Server for z/OS application process address space was started with an incorrect value for the AMODE= parameter. The value specified on the AMODE= parameter can only be 2 characters long. Valid values for the AMODE= parameter are 00, 31, or 64. |
Action | Restart the server with a valid value on the AMODE= parameter. |
Explanation | A WebSphere Application Server for z/OS application process address space was started without the correct number of parameters. The program name and amode must be specified. |
Action | Correct the problem with the procedure used to start the server and restart the server. |
Explanation | The WebSphere Application Server Version 7.0 announcements state that in a subsequent release, application servers running on the z/OS platform will not be able to run in 31-bit mode. The server you started is running in 31-bit mode. |
Action | You should start to update any applications that you run on the z/OS platform to enable them to execute on an application server that is running in 64-bit mode. You can find documentation on running application servers in 64-bit mode at: http:www.ibm.com/support/techdocs/atsmastr.nsf/WebIndex/WP100920 You can find documentation on converting native C/C++ applications at: http:www.ibm.com/support/techdocs/atsmastr.nsf/WebIndex/WP101095 |
Explanation | Provides various resource monitoring data retrieved from the kernel. The fields of the message are defined below: (maximum shared library region size in MB) (process level information (prli) shared library region size, if available) (reserved) (reserved) (reserved) (reserved) (reserved) (reserved) (reserved) (reserved) |
Action | None. |
Explanation | A modify command failed for the stated reason. The following is a list of known failures: COMMAND WLM_MIN_MAX, WLM DAE CONFIGURED SINGLE SERVER: The attempt to modify the WLM settings for MIN and MAX servants failed because the server is configured with dynamic application environments and for single server only. The relevant environment property setting is wlm_dynapplenv_single_server. COMMAND WLM_MIN_MAX, PARSE FAILURE - INCORRECT SYNTAX The modify command failed due to a parse error. The command contained incorrect syntax. |
Action | Address the failure and reissue the modify command. |
Explanation | This message displays the current WLM settings for the minimum and maximum number of servants. |
Action | None |
Explanation | This message is part of the response to a display,smf command. The state of the SMF120 SubType 9 enablement flag is shown, followed by the states of the flags for enabling the SMF120 SubType 9, CPU Usage, Timestamps, Security Info and Async sections. The SMF 120-9, CPU USAGE, TIMESTAMPS, SECURITY INFO and ASYNC sections of the message can have values of ON, OFF, FORCED_ON, or FORCED_OFF. For each section, a value of ON means that the corresponding environment variable listed below is set to 1. A value of OFF means that the corresponding environment variable listed below is set to 0. A value of FORCED_ON means that the corresponding f server,SMF,REQUEST[,CPU|TIMESTAMPS|SECURITY|ASYNC],ON command was issued. A value of FORCED_OFF means that the corresponding f server,SMF,REQUEST[,CPU|TIMESTAMPS|SECURITY|ASYNC],OFF command was issued. SMF 120-9: Flag: server_SMF_request_activity_enabled Command indicated by FORCED_[ON|OFF]: f server,SMF,REQUEST,[ON|OFF] CPU USAGE: Flag: server_SMF_request_activity_CPU_detail Command indicated by FORCED_[ON|OFF]: f server,SMF,REQUEST,CPU,[ON|OFF] TIMESTAMPS: Flag: server_SMF_request_activity_timestamps Command indicated by FORCED_[ON|OFF]: f server,SMF,REQUEST,TIMESTAMPS,[ON|OFF] SECURITY INFO: Flag: server_SMF_request_activity_security Command indicated by FORCED_[ON|OFF]: f server,SMF,REQUEST,SECURITY,[ON|OFF] ASYNC: Flag: server_SMF_request_activity_async Command indicated by FORCED_[ON|OFF]: f server,SMF,REQUEST,ASYNC,[ON|OFF] |
Action | No action is required. |
Explanation | This message is part of the response to a display,smf command. The time at which the last SMF120 SubType 9 record was written is shown, followed by the number of times these records succeeded and failed to be written. If no writes have failed, "NEVER" is displayed instead of a value. |
Action | None |
Explanation | This message is part of the response to a display,smf command. The time of the last failed attempt to write an SMF120 SubType 9 record is shown. If no writes have failed, "NEVER" will be displayed instead of a value. |
Action | None |
Explanation | The WebSphere Application Server failed to configure the FRCA cache because it did not have authority. The FRCA services can be protected with a SERVAUTH resource in RACF. |
Action | Issue the appropriate RACF commands to give the userid of the Controller read access to the FRCA resource in the SERVAUTH class. |
Explanation | The WebSphere Application Server failed to configure the FRCA cache because the required level of FRCA support is not available on this system. |
Action | Only attempt to activate FRCA on a system that is at the correct z/OS level and at the correct PTF level of TCP/IP. |
Explanation | The WebSphere Application Server failed to configure the FRCA cache for an unexpected reason. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | The server reached the configured maximum for the FRCA Cache. To be able to add an object to the cache it was necessary to remove existing objects to make room. This could lead to a thrashing scenario where objects are continually removed to make room for newer objects. This message will only be issued when on the first occurance of this condition. |
Action | The FRCA cache size should be increased to be able to contain all the objects that are configured to be FRCA cached. If the FRCA cache size cannot be increased, then a reduction of the number of objects that are configured to be eternally cacheable should be considered. The modify display FRCA command can be used to dislpay the number of times this event occured, and other information on the FRCA cache. |
Explanation | This message is part of the response to a display,frca command. Subsequent messages might 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. |
Action | None |
Explanation | This message is part of the response to a display,frca command. This message shows the current number of objects in the frca cache. |
Action | None |
Explanation | This message shows the total number of objects that have been put into the FRCA cache. The delta is the difference between the total shown here and the total at the time of the previous display,frca command. |
Action | None |
Explanation | This current size of the FRCA cache rounded to 1K bytes. |
Action | None |
Explanation | This message shows the total number of objects that have been pushed out of the FRCA cache to make room for other objects. This indicates the FRCA cache is not configured large enough to accommodate all the cacheable objects. This could lead to a thrashing condition where objects are continually removed and and then added back again. |
Action | If possible the FRCA cache should be made larger. If that is not possible than the number of FRCA cacheable objects should be reduced. |
Explanation | This message shows the current number of objects that are cached for the specified size range. |
Action | None |
Explanation | This message shows the size and URL for a cached object. |
Action | None |
Explanation | This message indicates that the list of currently cached objects will not be written to the console. They are written to the joblog to avoid flooding the console. |
Action | Look in joblog for the complete display output. |
Explanation | The WebSphere Application Server for z/OS server is configured for multi-cell mode, and is configured with an ephemeral IIOP listener port (port 0: dynamic port allocation). This is not a recommended configuration. |
Action | It is recommended that the IIOP listener port be configured with a static value. |
Explanation | The WebSphere Application Server for z/OS server Controller's multi_cell_mode configuration setting does not match the multi_cell_mode configuration setting of the WebSphere daemon. These configuration settings must match. |
Action | Correct the mismatched multi_cell_mode configuration setting between the WebSphere Application Server for z/OS Controller and the WebSphere daemon. |
Explanation | This message displays the current Dispatch Progress Monitor (DPM) settings for the server. |
Action | None |
Explanation | The SETOLATRACE command completed successfully. |
Action | None |
Explanation | The SETOLATRACE keyword expects an operand of 0 through 2. |
Action | Retry the command. |
Explanation | The SETOLATRACE RGE=xxxx...xx keyword specified an address that matches an RGE in the chain but the RGE seems corrupted. |
Action | Issue the OLATRACE command and recheck the extracted trace records to find a valid RGE address. If the target RGE continues to appear corruptedm this is a system error so contact IBM support. |
Explanation | This message is issued in response to the command DISPLAY,TRACERECORD. This message displays the current TRACERECORD setting. The TRACERECORD setting is one of the following values: "ON" Write all trace records. This will cause the classification_only_trace attributes in the Workload Classification file to be ignored. "OFF" Write no trace records. "RESET" Write trace records only for those requests whose classification in the Workload Classification file contains the attribute classification_only_trace equal to "1". If no request classifications contain the attribute classification_only_trace equal to "1", then write all trace records. |
Action | No action is required. |
Explanation | The user did not specify a proper value for the reclen= parameter to the indicated program. Valid values are from 80 to 32752. |
Action | Rerun the program specifying an appropriate value. |
Explanation | Displays the list of message IDs assigned to the indicated message routing location. |
Action | No action is required. |
Explanation | A servant region with the given ASIDX was not found in the servant region queue for this server. |
Action | Specify an ASIDX for a servant region associated with this server. |
Explanation | A EIO/3448 minor code indicates that TCP/IP has shut down. In response, the WebSphere Application Server deactivates its TCP listeners. The server will reactivate the listeners when TCP/IP is available. |
Action | No action is required. |
Explanation | A TCP listener has been deactivated. |
Action | No action is required. |
Explanation | A TCP listener that was deactivated has been reactivated. |
Action | No action is required. |
Explanation | The server has detected that a service update is only partially applied. In a mixed-cell environment, service updates applied to a node that is running at a lower level of the product, must also be applied to the daemon. |
Action | Apply the corresponding service update to the daemon, and restart the daemon. |
Explanation | The support to modify Optimized Local Adapter (OLA) trace levels via the SETOLATRACE=n commmand parameter is being moved from 'modify DISPLAY' to the modify command. The former support is deprecated. The new support is enabled. |
Action | Update procedures or automation directives to use the new command form, for example F BBOS001,SETOLATRACE=0,RGE=0123456789 |
Explanation | This information message shows the path and file name of the properties files containing the predefined trace levels for Optimized Local Adapter (OLA) registrations. This file is specified in environment variable 'ola_trace_file.' |
Action | None |
Explanation | While opening the Optimized Local Adapter (OLA) trace properties file shown in message BB000374I, an unexpected error occurred. Because of this, further reading of the trace specifications in the OLA trace file is halted. Any prior trace specifications remain in effect. The message displays the error code and stderror text. |
Action | Check that the file name and path as shown in BBOO0368I are correct. Make corrections if necessary to the name specified in environment variable ola_trace_file or to the name of the file itself. Correct the problem and re-issue F <server>,SETOLATRACEPROPS to retry the reading of the trace properties file. |
Explanation | Optimized Local Adapter (OLA) tracing has been set for registrations. At start up of the application server, these settings result from the processing of the OLA trace properties as shown in log message BB000368I and specified in environment variable ola_trace_file. Alernately, the requested trace settings could have come from the modifiy operator command that directed trace level settings for existing registrations via F servername,SETOLATRACE=n,REGNAME=namestring or F servername,SETOLATRACE=n,JOBNAME=namestring |
Action | No action is required. |
Explanation | This message is in response to an attempt to update the Optimized Local Adapter (OLA) trace properties files via a F server,SETOLAPROPS command. This command can only be targeted to the daemon. Setting the properties table is not done. |
Action | Reissue the modify command using the jobname of the damon as the target server. |
Explanation | The SETOLATRACE RGE=xxxx...xx keyword specified an address but that does not match any RGE in the RGE chain. Recheck Optimized Local Adapter (OLA) trace records for valid RGE addresses that represent a current registration: |
Action | Issue the OLATRACE command and recheck the extracted trace records to find a valid RGE address. |
Explanation | The SETOLATRACE keyword expects an operand that defines the registratons whose trace levels are updated. No operand was recognized.The expected operands are either: RGE=xxxxxxx to specify the address of a target OLA RGE, JOBNAME=ssssssss to specify a jobname, or REGNAME=ssssssss to specify a registration name. Note: The registration and job name can contain asterisk wildcard characters. It can also be delimited with single or double quotes. |
Action | Retry the command with one of the operands as noted above. |
Explanation | The Optimized Local Adapter (OLA) trace settings file shown in BBOO0374I contains a record that does not meet syntax requirements. Message BBOO380I indicates the problematic record number. |
Action | Examine the record pointed to in the OLA trace settings file and correct the syntax. Watch for mismatched single or double quoation marks around the registration name specification (the left side of the euqal sign.) The trace level should be unquoated and be on the right side of the equal sign. Examples of correct syntax are: REGNAME=2 MYREG*=1 "THISREG" = 0 'ALLCICSREG' = 1 Correct the trace properties file ands re-issue the modify SETOLATRACEPROPS command. |
Explanation | In previous PTFs the postinstaller created directories without group write permission enabled. This lack of permission causes problems when a user other than the owner tries to update those directories. |
Action | Run the script WAS_HOME/bin/fixGroupPerms.sh under a user that has enough authority to update the group permissions. |
Explanation | A WebSphere Application Server for z/OS application process address space was started but the required JAVA_HOME variable could not be found in was.env. The STDENV DD statement in the procedure used to start the process has the location of was.env. |
Action | Correct the problem and restart the server. |
Explanation | A WebSphere Application Server for z/OS application process address space was started but the required WAS_HOME variable could not be found in was.env. The STDENV DD statement in the procedure used to start the process has the location of was.env. |
Action | Correct the problem and restart the server. |
Explanation | An error occurred when writing to SYSOUT or SYSPRINT. |
Action | If SYSOUT or SYSPRINT is being directed to a file system, look for reasons why the file system can not be written to. For example, the file system might be out of space. |
Explanation | The property protocol_http_transport_class_mapping_file was found but is no longer supported and will be ignored. This function has been replaced with a workload classification XML document specified by the wlm_classification_file WebSphere environment variable. |
Action | Create a WLM Classification XML file to specify custom workload classifications. |
Explanation | The code page value specified by the customer for the variable "com.ibm.ws390.SystemOutErrCodepage" in the WebSphere Application Server custom properties on the admin console is not supported.The default Cp1047 encoding will be used. |
Action | Configure a valid code page value for the variable "com.ibm.ws390.SystemOutErrCodepage" in the WebSphere Application Server custom properties. |
Explanation | This message is part of the response to a display,smf command. The time at which the last SMF120 SubType 109 record was written is shown, followed by the number of times these records succeeded and failed to be written. If no writes have failed, "NEVER" is displayed instead of a value. |
Action | No action is required. |
Explanation | This message is part of the response to a display,smf command. The time of the last failed attempt to write an SMF120 SubType 10 record is shown. If no writes have failed, "NEVER" will be displayed instead of a value. |
Action | No action is required. |
Explanation | This message is part of the response to a display,smf command. The state of the SMF120 SubType 10 enablement flag is shown. SMF 120-10: A value of ON means that the server_SMF_outbound_enabled environment variable is set to 1. A value of OFF means that the server_SMF_outbound_enabled environment variable is set to 0. A value of FORCED_ON means that the f server,SMF,OUTBOUND,ON command was issued. A value of FORCED_OFF means that the f server,SMF,OUTBOUND,OFF command was issued. |
Action | No action is required. |
Explanation | This message shows the total number of async servlet requests currently being processed by this servant. |
Action | None |
Explanation | This message is part of the response to a display,smf,async command. The time at which the last SMF120 SubType 9 record was written for async work processed by the servant named in the first field is shown, followed by the number of times these records succeeded and failed to be written. If no writes have failed, "NEVER" is displayed instead of a value. |
Action | None |
Explanation | This message is part of the response to a display,smf,async command. The time of the last failed attempt to write an SMF120 SubType 9 record for async work is shown following the servant it was run on. If no writes have failed, "NEVER" will be displayed instead of a value. |
Action | None |