BBOJ0011I | JVM Build is string. |
Explanation: An informational message issued during initialization of a server region that indicates the build level the JVM that is being started.
BBOJ0015I | EJB Role Service is inactive. |
Explanation: An informational message issued the first time the EJB role service is accessed if the service is found to be inactive.
User Response: Activate EJB Role Service, if required.
BBOJ0021E | Error encountered while reading "com.ibm.websphere.preconfiguredCustomServices" Java property. |
Explanation: A WebSphere for z/OS server encountered an exception while trying to read the "com.ibm.websphere.preconfiguredCustomServices" Java property. The exception will be in the SYSPRINT along with a traceback in the SYSOUT.
User Response: This error could happen if the xml filenames are not correctly specified in the "com.ibm.websphere.preconfiguredCustomServices" Java property. Check to see that the names are correctly specified with the correct delimiter between them.
BBOJ0022E | Internal error encountered within Custom Services. |
Explanation: A WebSphere for z/OS server encountered an internal error within the Custom Service process. The exception will be in the SYSPRINT along with a traceback in the SYSOUT.
User Response: Contact the IBM Support Center.
BBOJ0023W | No Custom Services found in xml file [xml filename]. |
Explanation: No Custom Services were found in the specified Custom Service xml file.
User Response: Check the specified xml file.
BBOJ0024W | Custom Service class [classname] not defined in xml file. |
Explanation: No Custom Service class was given in the xml file that defined the Custom Service.
User Response: Check the Custom Services xml file for class definition.
BBOJ0025E | Error encountered initializing Custom Service [servicename]. |
Explanation: A WebSphere for z/OS server encountered an exception while running the "initialize" method on the specified Custom Service. The exception will be in the SYSPRINT along with a traceback in the SYSOUT.
User Response: Check the implementation of the specified Custom Service.
BBOJ0026E | Error encountered creating instance of Custom Service [servicename]. |
Explanation: A WebSphere for z/OS server encountered an exception while creating an instance of the specified Custom Service to be installed. The exception will be in the SYSPRINT along with a traceback in the SYSOUT.
User Response: Check the implementation of the specified Custom Service class.
BBOJ0027I | Custom Service [servicename] was not enabled. |
Explanation: The Custom Service is not enabled. The specified custom Service will not be installed because it is not enabled.
BBOJ0028E | Error encountered reading Custom Service xml file [xml filename]. |
Explanation: A WebSphere for z/OS server encountered an exception while reading the specified xml file.The exception will be in the SYSPRINT along with a traceback in the SYSOUT.
User Response: Check to see if the xml file is correctly qualified, that the file exists and the file is a good xml file.
BBOJ0029E | Error encountered shutting down Custom Service [servicename]. |
Explanation: A WebSphere for z/OS server encountered an exception while attempting to run the implementation of Shutdown on the specified Custom Service. The exception will be in the SYSPRINT along with a traceback in the SYSOUT.
User Response: Check the trace back to see if the error occurred in the implementation of the specified custom Service or in.
BBOJ0031I | WebSphere for z/OS [info message here]. |
Explanation: An informational message to indicate that Global Security Custom Property "security_EnableRunAsIdentity" to enableSyncOSThread is set to false.
User Response: None, if this is the desired mode. If this is NOT the desired setting, set the Global Security Custom Property "security_EnableRunAsIdentity" to true and rerun the application.
BBOJ0050I | string |
Explanation: This message contains the trace specification for java tracing. The message is issued in response to the DISPLAY,TRACE,JAVA modify command.
User Response: None.
BBOJ0051I | PROCESS INFORMATION: string1/string2, ASID=string3, PID=string4 |
Explanation: This message provides the job identifier (jsabpref) and jobname (jsabjbnm), the address space id (ASID), and USS process id in decimal(hex).
User Response: None.
BBOJ0052E | TRACE SPECIFICATION NOT VALID: string |
Explanation: The trace specification string was not valid. The fill in message provides more details.
User Response: Correct the syntax and set the trace specification again.
BBOJ0053I | Transformer is writing to: file |
Explanation: C2N: The transformer is writing a file to this path.
User Response: None.
BBOJ0054I | Transformer symlink - Already Linked: |
Explanation: C2N: The transformer is not regenerating the symlink, the current one is correct.
User Response: None.
BBOJ0055I | Transformer symlink - Linking: file a points at file b |
Explanation: C2N: The transformer is generating a symlink file a points at file b.
User Response: None.
BBOJ0056I | Transformer Processing Complete, RC=0 |
Explanation: C2N: The transformer has completed.
User Response: None.
BBOJ0057E | Transformer symlink - Symlink not created properly: file a to file b |
Explanation: C2N: The transformer for whatever reason did not complete the symlink properly.
User Response: Check the symlink, ensure it has been created.
BBOJ0058I | Transformer Looking: file |
Explanation: C2N: The transformer looked for the file to transform but did not find it.
User Response: None, the file may not be necessary for the given transformation.
BBOJ0059I | Transforming: file |
Explanation: C2N: The transformer is transforming this file.
User Response: None
BBOJ0060E | Transformer Exception: |
Explanation: C2N: The transformer threw this exception.
User Response: The message should contain a file and line number of the failure. Check the XML file for invalid characters or call IBM support.
BBOJ0061I | Transformer Usage: |
Explanation: Usage guide for the wsc2n.sh script.
User Response: Change the parameters passed to the script.
BBOJ0062I | \t wsc2n.sh -s <CELL_NAME> [-trace] |
Explanation: Usage guide for the wsc2n.sh script.
User Response: Change the parameters passed to the script.
BBOJ0063I | \t wsc2n.sh -s <CELL_NAME> <NODE_NAME> [-trace] |
Explanation: Usage guide for the wsc2n.sh script.
User Response: Change the parameters passed to the script.
BBOJ0064I | \t wsc2n.sh -s <CELL_NAME> <NODE_NAME> <SERVER_NAME> [-trace] |
Explanation: Usage guide for the wsc2n.sh script.
User Response: Change the parameters passed to the script.
BBOJ0065I | \t wsc2n.sh -d <CELL_NAME> <NODE_NAME> <SERVER_NAME> |
Explanation: Usage guide for the wsc2n.sh script.
User Response: Change the parameters passed to the script.
BBOJ0066I | \t wsc2n.sh -X [-trace]\t\t |
Explanation: Usage guide for the wsc2n.sh script.
User Response: Change the parameters passed to the script.
BBOJ0067E | Transformer Processing Complete, Errors Occured, RC=8 |
Explanation: C2N: The transformer ended badly.
User Response: An error has occured, call IBM support.
BBOJ0068I | Transformer symlink - Deleting: file a to file b |
Explanation: C2N: The transformer is deleting a symbolic link, which pointed from file a to file b.
User Response: None.
BBOJ0069I | Transformer symlink - Deleting: link |
Explanation: C2N: The transformer is deleting a dead symbolic link linkname, which did not point anywhere.
User Response: None.
BBOJ0077I | Message |
Explanation: This message is used to display JVM system properties at JVM startup.
User Response: None.