BBOM0001I | %23s: string. |
Explanation: Indicates SCO Config variable setting.
User Response: None.
BBOM0002E | BBOENV FAILURE. |
Explanation: BBOENV failure.
User Response: Ensure that the BBOENV is correct.
BBOM0003E | FCLOSE FAILURE. |
Explanation: FCLOSE failed while checking BBOENV.
User Response: Ensure that the BBOENV is correct.
BBOM0004I | BBOENV IS NOT VARIABLE LENGTH. |
Explanation: This message is informational and indicates that BBOENV is not variable length. C++ requires NULL for a string copy.
User Response: Change BBOENV from fixed to variable length.
BBOM0005E | FLDATA failure, rc=dstring. |
Explanation: FLDATA failed while checking BBOENV.
User Response: Ensure that the BBOENV is correct.
BBOM0006W | BBOENV FOPEN failure. |
Explanation: FOPEN failed for BBOENV DD.
User Response: Ensure that the BBOENV DD is correct. CB will default the environment variables and attempt to continue.
BBOM0007I | CURRENT CB SERVICE LEVEL IS string. |
Explanation: Shows the current WebSphere service level. This is an IBM Internal value (not a PTF number) that might be requested when you contact IBM service.
User Response: None.
BBOM0008W | ENVIRONMENT VARIABLE DAEMON_IPNAME IS NOT FULLY
QUALIFIED. |
Explanation: The DAEMON_IPNAME environment variable is not fully domain qualified. This may cause problems in a multiple sysplex configuration.
User Response: If the Daemon IP Name should be fully domain qualified, change the DAEMON_IPNAME environment variable to reflect the fully qualified name and run the Systems Management Bootstrap again.
BBOM0009W | NON-NUMERIC VALUE SPECIFIED FOR ENVIRONMENT VARIABLE
string. THE DEFAULT VALUE dstring IS TAKEN. |
Explanation: An invalid value was specified for the given variable in the environment file. The value must be numeric. The default value is taken instead.
User Response: Correct the variable setting and re-start WebSphere for z/OS.
BBOM0010W | VALUE OF ENVIRONMENT VARIABLE string TRUNCATED. LENGTH
MUST NOT EXCEED dstring CHARACTERS. |
Explanation: An invalid value was specified for the given variable in the environment file. There is a length limitation for the string value. The specified string was truncated.
User Response: Correct the variable setting and re-start WebSphere for z/OS.
BBOM0011W | INVALID VALUE 'string' SPECIFIED FOR ENVIRONMENT
VARIABLE string. THE DEFAULT VALUE string IS
TAKEN. |
Explanation: An invalid value was specified for the given variable in the environment file. The default value specified is taken instead.
User Response: Correct the variable setting and re-start WebSphere. The legal settings are described in the WebSphere for z/OS Installation and Customization Guide.
BBOM0012E | CB SERIES UNABLE TO CONTINUE SINCE RRS IS UNAVAILABLE. |
Explanation: WebSphere for z/OS cannot be started since RRS is unavailable.
User Response: Start RRS and re-start WebSphere for z/OS.
BBOM0013E | INVALID FUNCTION LEVEL FOR CONTROL REGION
string. |
Explanation: a backlevel server has been started. As all replicated servers already operate at a higher function level, the server must be abended.
User Response: Upgrade server to new function level.
BBOM0014E | MSG_BBOUENUS_SM_INVALID_BOOTSTRAP_STATE:
dstring |
Explanation: An invalid state was detected during SM bootstrap An exception is thrown and bootstrap processing terminates.
User Response: None MSG_BBOMENUS_MSG00015 deleted 25777D
BBOM0016E | MSG_BBOUENUS_SM_ENVVAR_RANGE_CHECK: var=string
value=dstring (min=dstring,max=dstring) |
Explanation: An environment variable was assigned a value which exceeds the valid value range.
User Response: None
BBOM0017E | MSG_BBOUENUS_SM_ENVVAR_VALIDATION_FAILED:
var=string value=string |
Explanation: An environment variable was assigned a value which is invalid. See accompanying messages for details.
User Response: None
BBOM0018E | MSG_BBOUENUS_SM_INVALID_ENVVAR_INDEX:
index=dstring, maxValidIndex=dstring |
Explanation: An attempt was made to access a internally maintained copy of an environment using an invalid index.
User Response: None
BBOM0019E | MSG_BBOUENUS_SM_ENVIRONMENT_INIT_FAILED |
Explanation: The internal WebSphere enviroment could not initialize; see accompanying messages for details.
User Response: None
BBOM0020I | CURRENT SERVER SETTINGS: |
Explanation: This message introduces the print out of server parameter settings. These settings are displayed if the env. variable SHOW_SERVER_SETTINGS is set in the BBOENV file.
User Response: None.
BBOM0021I | %38s: string. |
Explanation: Indicates server parameter setting. (See also: BBOM0020I)
User Response: None.
BBOM0022E | MSG_BBOUENUS_SM_UNABLE_TO_OBTAIN_SYSTEM_PARAMETER |
Explanation: During bootstrap execution an obtain of an system parameter failed. See accompanying messages for details.
User Response: None
BBOM0023E | Environment import error. Could not find sysplex object
'string' |
Explanation: During an initial bootstrap the initial set of environment variables is stored in the environment section of the sysplex object. While trying to do so the sysplex object could not be found. Suggested Action: This is either caused by an undetected error in a previous phase of the bootstrap or it is internal error. Please check for other error messages to give an indication for previous failures.
User Response: None
BBOM0024E | WRITE ENVIRONMENT FILES FAILED DURING BOOTSTRAP |
Explanation: writing the environment files during bootstrap failed.
User Response: Check permissions of the environment file directory CBCONFIG/controlinfo/envfile. Be sure that SYSPLEX_NAME is set appropriately.
BBOM0025I | WS BOOTSTRAP STEP string HAS BEEN ROLLED BACK. |
Explanation: This message is informational and indicates that the specified phase of the SM bootstrap has been rolled back.
User Response: Check console messages and job log for further information on the error.
BBOM0026E | CB SERIES SMF DATA GATHERING IN SERVER string HAS
STOPPED. |
Explanation: The WebSphere for z/OS control region address space indicated by "string" encountered a problem while trying to gather data for the SMF records. Data gathering has been stopped.
User Response: Look in the WebSphere for z/OS error log for the specific reason why data gathering was stopped. This is probably an internal programming error. For further information on resolving this error, please consult the IBM WebSphere Application Server for z/OS Support website at: http:www-3.ibm.com/software/webservers/appserv/zos_os390/support.html This site provides searchable databases of technotes, solutions, and e-fixes. Information on contacting the WebSphere Support team is also provided.
BBOM0027E | Could not create a dataspace buffer pool needed for SMF data
gathering. RC=dstring |
Explanation: The WebSphere for z/OS control region address space encountered a problem while trying to create a dataspace pool that is needed to gather data to produce SMF records. RC is a return code indicating the reason for the error.
User Response: This is an internal programming error. For further information on resolving this error, please consult the IBM WebSphere Application Server for z/OS Support website at: http:www-3.ibm.com/software/webservers/appserv/zos_os390/support.html This site provides searchable databases of technotes, solutions, and e-fixes. Information on contacting the WebSphere Support team is also provided.
BBOM0028E | NAMING REGISTRATION FAILED FOR SERVER string |
Explanation: Naming registration failed for the specified server. As applications installed on the server do not work properly without being registered in naming, the server must be abended.
User Response: Check accompanying messages in the job log of the System Management server region that processed naming registration for more details.
BBOM0029I | NAMING REGISTRATION STARTED FOR SERVER string |
Explanation: Naming registration started for the specified server. Message BBOM0030I will be issued when the processing is complete. In the meantime, the server is not fully operational. No client requests should be driven until naming registration is complete.
User Response: None. This message is for information only. Use CAPS for NLS Ttranlation
BBOM0030I | NAMING REGISTRATION COMPLETED FOR SERVER string |
Explanation: Naming registration completed for the specified server. The server is fully operational now.
User Response: None. This message is for information only. Use CAPS for NLS Ttranlation
BBOM0031I | REGISTERING HOME string FOR SERVER
string |
Explanation: The specified home is registered in naming for the specified server.
User Response: None. This message is for information only. Use CAPS for NLS Ttranlation
BBOM0032I | REGISTERING COMPONENT string FOR SERVER
string |
Explanation: The specified component is registered in naming for the specified server.
User Response: None. This message is for information only. Use CAPS for NLS Ttranlation
BBOM0033I | REGISTERING SERVER string |
Explanation: The specified server is registered in naming.
User Response: None. This message is for information only. Use CAPS for NLS Ttranlation
BBOM0034I | DEREGISTERING HOME string FOR SERVER
string |
Explanation: The specified home is deregistered from naming for the specified server.
User Response: None. This message is for information only. Use CAPS for NLS Ttranlation
BBOM0035I | DEREGISTERING COMPONENT string FOR SERVER
string |
Explanation: The specified component is deregistered from naming for the specified server.
User Response: None. This message is for information only. Use CAPS for NLS Ttranlation
BBOM0036I | DEREGISTERING SERVER string |
Explanation: The specified server is deregistered from naming.
User Response: None. This message is for information only.
BBOM0037W | Naming registration encountered already bound object
string |
Explanation: Naming registration tried to register an object that is already bound in name space. This might happen for two reasons: 1. Naming registration for the server has failed previously and is retried. 2. The same name as home/name as factory or JNDI name, respectively, has been used for different objects. The first case is part of normal operation and does not cause any problems. The second case is a problem and might show up as application failures when trying to resolve homes, create or narrow objects. It is strongly recommended to use the unique home/factory names Object Builder creates, or the unique JNDI name the SM administration EUI creates during reference resolution.
User Response: None. In case of subsequent application failures check name as home/factory and/or JNDI names for uniqueness.
BBOM0038E | Bootstrap error. Could not create default administrator |
Explanation: During bootstrap, create of the Systems Management default administrator failed.
User Response: Check console messages and job log for further information on the error.
BBOM0039E | Bootstrap error. Could not import configuration XML file |
Explanation: During bootstrap, import of the configuration xml file failed.
User Response: Check console messages and job log for further information on the error.
BBOM0040E | Bootstrap error. Could not create initial references |
Explanation: During bootstrap, create of the Systems Management initial references failed.
User Response: Check console messages and job log for further information on the error.
BBOM0041E | Bootstrap error. Could not commit the imported
configuration |
Explanation: During bootstrap, commit of the configuration imported from XML failed.
User Response: Check console messages and job log for further information on the error.
BBOM0042E | Bootstrap error. Could not process previously installed EAR
files |
Explanation: During bootstrap, processing of previously installed EAR files failed.
User Response: Check console messages and job log for further information on the error.
BBOM0043E | Bootstrap error. Could not create the Systems Management name
space |
Explanation: During bootstrap, create of the Systems Management name space failed.
User Response: Check console messages and job log for further information on the error.
BBOM0044E | Bootstrap error. Could not create naming registration
entries |
Explanation: During bootstrap, create of the naming registration entries for the imported configuration failed.
User Response: Check console messages and job log for further information on the error.
BBOM0045E | Bootstrap error. Could not register CB servers in naming |
Explanation: During bootstrap, registration of the CB owned servers failed.
User Response: Check console messages and job log for further information on the error.
BBOM0046E | Bootstrap error. Could not cleanup configuration |
Explanation: As last step of bootstrap, some housekeeping and cleanup is done in the Systems Management data base. This step failed.
User Response: Check console messages and job log for further information on the error.
BBOM0047E | Bootstrap error. Could not get Systems Management server region
SMO |
Explanation: Building a direct, non transactional server region object for Systems Management failed.
User Response: Check console messages and job log for further information on the error.
BBOM0048E | Bootstrap error. Could not create upper tree structure for WS
naming |
Explanation: During bootstrap, create of the upper tree structure for WS naming failed.
User Response: Check console messages and job log for further information on the error.
BBOM0049I | NAMING REGISTRATION: NOTHING TO DO FOR SERVER
string |
Explanation: Naming registration started for the specified server, but nothing needs to be registered.
User Response: None. This message is for information only.
BBOM0050E | FOR ENVIRONMENT VARIABLE string DEFINED OUTPUT LOCATION =
string IS NOT CORRECT |
Explanation: When specifying trace output location in an environment variable, a valid trace name must be specified.
User Response: Specify a valid trace output location name in the environment variable
BBOM0051E | FOR ENVIRONMENT VARIABLE string DEFINED RAS MINORCODE =
string IS NOT CORRECT |
Explanation: When specifying RAS minor code type in an environment variable, a valid name must be specified.
User Response: Specify a valid minor code type in the environment variable
BBOM0052E | FOR ENVIRONMENT VARIABLE string DEFINED PROFILE TYPE =
string IS NOT CORRECT |
Explanation: When specifying workload profile type in an environment variable, a valid type name must be specified.
User Response: Specify the valid workload type name in the environment variable
BBOM0053E | FOR ENVIRONMENT VARIABLE string A VALUE MUST BE
ASSIGNED |
Explanation: When specifying workload profile type in an environment variable, a valid type name must be specified.
User Response: Specify a valid workload type name in the environment variable MSG_BBOMENUS_MSG00054 deleted 25777D
BBOM0055E | FOR ENVIRONMENT VARIABLE string DEFINED GIOP LEVEL =
string IS NOT SUPPORTED |
Explanation: When specifying environment variable, a GIOP level within a supported range must be supplied. The default value will be used instead.
User Response: Specify a valid GIOP level for environment variable
BBOM0056E | FOR ENVIRONMENT VARIABLE string DEFINED SERVER TYPE =
string IS NOT SUPPORTED |
Explanation: When specifying environment variable server_type, an unsupported type was specified. The default of AppServer will be used.
User Response: Specify a valid server type.
BBOM0057W | DEFAULT VALUE OF ENVIRONMENT VARIABLE string USED. LENGTH
MUST NOT EXCEED dstring CHARACTERS. |
Explanation: An invalid value was specified for the given variable in the environment file. There is a length limitation for the string value. The default value is used.
User Response: Correct the variable setting and re-start WebSphere for z/OS.