CWWSY
- CWWSY0100E: Unable to run the {0} command.
Explanation An exception occurred when the command ran. The exception is usually caused by incorrect parameter entry. Action Correct the input parameters and rerun the command. - CWWSY0101E: The {0} required parameter is null or is of zero length.
Explanation The required parameter for a command was set to null or is of zero length. Action Verify that all the required parameters are getting set and re-issue the command. - CWWSY0102E: Target with name {0} was not found.
Explanation No target was found with given target name. Action Verify that all the target names identify registered targets. - CWWSY0103E: Duplicate target name or UUID. {0}
Explanation A target with the same node name or UUID is already registered with this JobManager. Action Retry the registration using an alias for new target. - CWWSY0104E: Job manager {0} is null. This operation will fail.
Explanation Job manager profileKey returned null, this operation will fail. 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: https://ibm.biz/BdztgV WebSphere Application Server for z/OS Support page: https://ibm.biz/Bdqd4J . - CWWSY0105E: All the members of a group need to be of type {0}.
Explanation All group members must be of the same type. Action Verify that all members are of the same type and the group supports that type. - CWWSY0106E: The group {0} members length cannot be less than the number to be deleted.
Explanation The Number of devices to be deleted is more than the number available in the group. Action Verify that number of devices to be deleted is less than or equal to the number available in the group. - CWWSY0107E: {0} is not a known group.
Explanation An unknown group name was passed. The delete operation failed. Action Verify that all the groups to be deleted are valid groups. - CWWSY0108E: Duplicate group name {0}.
Explanation A group with similar name already exists on this job manager. Action Use a unique group name to create a group on this job manager. - CWWSY0109E: Only one parameter can be set {0}.
Explanation Only one parameter needs to be set for this command. Action Verify that only one parameter is set for this command. - CWWSY0110E: Only one target can be specified for job submission.
Explanation Only one target can be specified for job submission. Action Verify that only one target is specified for job submission. - CWWSY0111E: At least one target needs to be specified for the job {0}.
Explanation At least one of the target needs to be specified for the job to be submitted. Action Verify that only one target is specified for job submission. - CWWSY0112E: No group with name {0} was found.
Explanation No group was found with the provided group name. Action Verify that the name identifies a valid group. - CWWSY0113E: No information is available for target {0}.
Explanation No information is available for the target. Action Verify that the name identifies a valid target. - CWWSY0114E: The query has unknown properties defined {0}.
Explanation The query has unknown keys. Action Verify that the keys for the query are correct. - CWWSY0115E: The backup location {0} already exists.
Explanation The backup location is not empty or not writeable. Action Provide a new location to backup the job manager data or use the force option to overwrite the file. - CWWSY0116E: The backup file location is not valid: {0}.
Explanation The backup location is not readable. No valid backup file was provided to restore from. Action Provide a valid backup file to restore the job manager from. - CWWSY0117E: No valid backup file location was provided to restore from {0}.
Explanation Backup file location is was empty. Backup file location is a required field. Action Provide a valid backup file to restore from. - CWWSY0118E: Maximum return size for the query is not valid: {0}.
Explanation Maximum return size for the query is not valid. Action Provide a valid maximum return size for the query. - CWWSY0119E: Job manager has no information regarding job type {0}.
Explanation Job manager has no information regarding the provided job type. Action Provide a valid registered job type. - CWWSY0120E: Duplicate key {0} with incompatible type.
Explanation Value for the key are of incompatible type. Action Provide valid value types of same key. - CWWSY0121E: Error during execution of query.
Explanation This error is usually received if the query is not valid or is not formatted correctly. Action Inspect the query and make sure it is valid. - CWWSY0122E: Error received: {0}.
Explanation Internal exception was received while processing users request. Action Make sure that a valid input is provided. - CWWSY0123I: JobToken: {0} completed.
Explanation Message header sent in the email after the job completion. Action None. - CWWSY0124I: JobToken={0}; Status=Completed; Summary (Total={1}, Success={2}, Partial Success = {3}, Failed={4}, Rejected={5}).
Explanation Message sent in the email after the job completion. Action None. - CWWSY0125E: The maxResult attribute must be less than or equal to {0}.
Explanation maxResult for the query has been reached. Action Make sure that a valid input is provided. - CWWSY0126E: Managed Resource with {0} identifier was not found.
Explanation Managed Resource with the provider identifier was not found in the database. Action Make sure that a valid input is provided. - CWWSY0127E: No {0} specified for corresponding {1}.
Explanation Missing corresponding data for either user name or password Action Make sure user name and password are both present during job submission. - CWWSY0128E: Security information for this job is not valid.
Explanation The job is being rejected because security information is not valid. Action Make sure correct security information is provided for this job. - CWWSY0129I: Usage: restoreJobManager -location <location>
- location: includes the database name.
- CWWSY0130I: Starting JobManager restore ....
Explanation Message before starting the JobManager restore of the command. Action No action is needed from user. - CWWSY0131I: Restore completed successfully.
Explanation Message after successful restore of JobManager. Action No action is needed from user. - CWWSY0132E: Exception received during execution of restore command.
- Root Cause: {0}
- CWWSY0133E: Access denied during command execution
Explanation The current user does not have the appropriate credential to run this command. Action Supply appropriate user id and password to this command. - CWWSY0134E: Query key {0} does not support {1} as value.
Explanation Not supported value provided for a valid query key. Action Modify the query to support valid values only. - CWWSY0135E: The system clock of the new target {0} is not synchronized with that of the job manager.
Explanation The system clocks for all the systems that communicate with each other and have WebSphere Application Server installed must be synchronized. Otherwise, you might experience errors, such as security tokens no longer being valid. Action To change the system clock, first stop all the servers on the system. After you stop the servers, change the system clock, and then restart the servers. If you change the system clock on one system, ensure the clocks on all systems that communicate with each other and have WebSphere Application Server installed are synchronized. - CWWSY0136E: Specify the {0} required property.
Explanation A required property for the command was not specified. Action Resubmit the command with the required property. - CWWSY0137E: Only one of these properties can be set: {0}, {1}.
Explanation These properties are mutually exclusive. Action Resubmit the command with only one of the properties. - CWWSY0138E: The use of the {0} property requires that the {1} property also be specified.
Explanation The property is not used without its associated property. Action Specify both properties in the command. - CWWSY0139E: Specify either the {0} or {1} property.
Explanation One of these properties is required. Action Resubmit the command with the required property. - CWWSY0140E: When a username is specified, you must also specify a password.
Explanation To specify a non-default user credential, specify either a username and password or a username and keyfile path. Action Specify either a password or keyfile path along with a username. - CWWSY0141E: When a password, keyfile path, pass phrase or sudo parameter is specified, you must also specify a username.
Explanation To specify a non-default user credential, a username is required. Action Do not specify a password, keyfile path, pass phrase or sudo parameters without a username. - CWWSY0142E: Password and keyfile path cannot both be specified.
Explanation To specify a non-default user credential, specify either a username and password with optional sudo parameters or a username and keyfile path. Action With a username already specified, only specify either a password with optional parameters or a keyfile path. - CWWSY0143E: Pass phrase can only be specified along with keyfile path.
Explanation A pass phrase is an optional part of a security scheme that uses a keyfile path. Action Do not specify a pass phrase without a keyfile path. - CWWSY0144E: When a sudo parameter is specified, you must also specify a value for -password.
Explanation The sudo parameters can not be specified unless -password is also specified. Action Either remove all sudo parameters, or specify a value for -password. - CWWSY0145E: You can not specify both sudo parameters and keyfile path.
Explanation Either use sudo parameters or keyfile path. Action Either remove all sudo parameters or remove keyfile path. - CWWSY0146E: Query Parser does not know how to parse query of type {0}.
Explanation Invalid type of resource passed to Query Parser. Action This is an internal error. No User action is required. - CWWSY0147E: Query String {0} has unmatched paranthesis.
Explanation Opening and closing paranthesis does not match in query string. Action Match the paranthesis in query string and issue the command again. - CWWSY0148E: Unexpected paranthesis before WITH or WITHOUT token in the query string {0}.
Explanation Nested query operation for queryManagedNodes command should only start after WITH or WITHOUT statement. Action Fix the query string and issue the command again. - CWWSY0149I: The client disabled remote host jobs.
Explanation The client has disabled remote host jobs by setting cell custom property com.ibm.websphere.management.disableRemoteHostJobs to true. Action To enable remote host jobs, delete the com.ibm.websphere.management.disableRemoteHostJobs property or set the property to false. - CWWSY0200E: Unable to locate extension point {0}
Explanation Unable to locate the required extension point to process a job. Action Contact IBM Support. - CWWSY0201E: Unable to locate Java handler class for extension point {0}
Explanation Unable to locate the required Java handler class for the extension point. Action Contact IBM Support. - CWWSY0202E: Unable to locate payload properties
Explanation Payload properties are passed from the job manager to the job agent in a JobContext object during the execution of a distribution job. Payload distribution job cannot proceed without these properties. Action Contact IBM Support. - CWWSY0203E: Missing required job parameter {0}
Explanation Job execution can not proceed without the required job parameter. Action Resubmit job with the required parameter. - CWWSY0204E: Payload distribution provider not specified.
Explanation A payload distribution provider is required to process a payload distribution job. The provider may be specified as part of the payload"s properties, as part of the job agent"s default payload distribution provider configuration, or as a parameter during job submission. Action Ensure the payload distribution provider is available before submitting a payload distribution job. - CWWSY0205E: Payload distribution provider {0} not found.
Explanation The payload distribution provider is the name of the extension point that is used to transfer payload between the job manager and job agent, or between the job manager and a remote machine. The name of the provider may be specified as part of the payload"s properties in the Payload Registry, as part of the job agent"s default payload distribution provider configuration, or as a parameter during job submission. Action Ensure the name of the payload distribution provider is spelled correctly. - CWWSY0206E: Exception while processing a job: {0}
Explanation An exception was encountered while processing a job. Action Examine the exception message and take corrective action as appropriate. - CWWSY0207E: A managed node with UUID {0} already exists.
Explanation A managed node with the given UUID already exists. Action Choose a different UUID for the managed node. - CWWSY0208E: Unable to locate a managed node with UUID {0}
Explanation Unable to locate a managed node with the specified UUID. Action Specify the UUID of an existing managed node. - CWWSY0209E: Attempt to change UUID of managed node {0} is disallowed.
Explanation The UUID of a managed node may not be changed. Action Do not change UUID of a managed node. - CWWSY0210E: Unable to locate an extension that implements job {0}.
Explanation The system is unable to run the job because there is no registered extension that implements the job. Action Verify that the job name is entered correctly. - CWWSY0300E: Problem while processing {0} operation. Message: {1}
Explanation Internal problem during the execution of the job. Action Check the error message to diagnose the problem. - CWWSY0301E: Server name parameter was not provided for job: {0}
Explanation Server name parameter is required. Action Resubmit the job with a server name parameter. - CWWSY0302E: Application name parameter was not provided for job: {0}
Explanation Application name parameter is required. Action Resubmit the job with an application name parameter - CWWSY0303E: Unable to locate Properties file at path: {0}
Explanation Unable to find the file specificed by the path. Action Check to see if the Properties file is located at the path specified. If correct file is located at desired path, then double check the supplied path parameter. - CWWSY0304E: Cluster name, {0}, is not a valid parameter
Explanation Clusters are not supported in a base Application Server environment. Action Resubmit the job without a cluster name parameter. - CWWSY0305E: Application {0} was not found for job: {1}
Explanation The application could not be located on the managed node. The application needs to be installed. Action Install the application on the managed node before resubmitting the job. - CWWSY0306E: Unable to locate server {0} on node {2} for job {1}. Either the server does not exist, or you do not have permission to access the server.
Explanation The server could not be located on the managed node. The server may not exist, or you may not have permission to access the server. Action Ensure you have permission to the server, or create the server before resubmitting the job. - CWWSY0307E: Properties file path parameter was not provided for job: {0}
Explanation Properties file path is a required parameter Action Resubmit the job with a correct Properties file path parameter. - CWWSY0308E: Delete parameter is not valid for job {0}
Explanation Delete parameter has to be either true, false, or not provided. Action Resubmit the job with a valid delete parameter. - CWWSY0309E: Incorrect parameter provided for job {0}. Incorrect parameter(s): {1}
Explanation The incorrect parameter is not needed for the job. Action Validate the parameters and resubmit the job. - CWWSY0310I: Application {0} was installed
Explanation This informational message indicates that the application was installed. Action No user action required. - CWWSY0311I: Application {0} was uninstalled
Explanation This informational message indicates that the application was uninstalled. Action No user action required. - CWWSY0312I: Application {0} was updated
Explanation This informational message indicates that the application was updated. Action No user action required. - CWWSY0313E: Application {0} was already installed
Explanation The application has already been installed. Action Do not install an application that is already installed. Try updating the application, or uninstall the application first. - CWWSY0314I: Application {0} was started
Explanation This informational message indicates that the application was started. Action No user action required. - CWWSY0315I: Application {0} was stopped
Explanation This informational message indicates that the application was stoppped. Action No user action required. - CWWSY0316I: Application {0} cannot be found
Explanation This informational message indicates that the application cannot be found. Action No user action required. - CWWSY0317I: Application {0} does not exist
Explanation This informational message indicates that the application does not exist. Action No user action required. - CWWSY0318I: Application server {0} already exists on node {1}
Explanation This informational message indicates that the application server already exists on the specified node. Action No user action required. - CWWSY0319I: Application server {0} does not exist on node {1}
Explanation This informational message indicates that the application server does not exist on the specified node. Action No user action required. - CWWSY0320I: Successful execution of configureProperties with Properties file located at {0}
Explanation This informational message indicates that the server with configured with a properties file. Action No user action required. - CWWSY0321I: Application server {0} was created on node {1}
Explanation This informational message indicates that the application server was created on the specifed node. Action No user action required. - CWWSY0322I: Application server {0} was deleted on node {1}
Explanation This informational message indicates that the application server was deleted from the specified node. Action No user action required. - CWWSY0323I: Proxy server {0} already exists
Explanation This informational message indicates that the proxy server already exists. Action No user action required. - CWWSY0324I: Proxy server {0} does not exist
Explanation This informational message indicates that the proxy server does not exist. Action No user action required. - CWWSY0325I: Proxy server {0} was created
Explanation This informational message indicates that the proxy server was created. Action No user action required. - CWWSY0326I: Proxy server {0} was deleted
Explanation This informational message indicates that the proxy server was deleted. Action No user action required. - CWWSY0327I: This job is only available in a secure proxy or dmgr profile
Explanation This informational message indicates that the selected job is not available in the current profile. Action No user action required. - CWWSY0328I: Server {0} was started on node {1}
Explanation This informational message indicates that the server was started on the specified node. Action No user action required. - CWWSY0329I: Server {0} is already running on node {1}
Explanation This informational message indicates that the server is already running on the specified node. Action No user action required. - CWWSY0330I: Server {0} was stopped on node {1}
Explanation This informational message indicates that the server was stopped on the specified node. Action No user action required. - CWWSY0331E: Server {0} was already stopped on node {1}
Explanation The server was already stopped on the specified node. Action No user action required. - CWWSY0333E: Server {0} was not started in the allotted time on node {1}
Explanation Server was not started in the allotted time. The server start operation will continue, but may not succeed. Action Check server status to determine whether it has been started. - CWWSY0334E: Unable to locate node agent MBean when processing job {0} for server {2} on node {1}
Explanation Node agent MBean required to process the job can not be located. Action Ensure that the node agent is running. - CWWSY0335E: Unable to locate Server MBean when processing job {0} for server {2} on node {1}
Explanation Server MBean required to process the job can not be located. Action Check that the server is running, and reachable from either deployment manager or admin agent. - CWWSY0336E: Problem while processing job {0} on node {1}: {2}
Explanation Unable to process the job due to exceptions. Action Check the exception message. - CWWSY0337E: genUniquePorts parameter is malformed for job {0}. Provided genUniquePorts parameter: {1}
Explanation Unable to process the job due to exceptions. Action Check the exception message. - CWWSY0338E: Cluster {0} status is unknown.
Explanation The cluster returned an unknown state. Action Check the status of the cluster again. - CWWSY0339E: Cluster {0} remains in stopped state.
Explanation The cluster has not started. Action Check the status of the cluster again. - CWWSY0340E: Cluster {0} remains in started state.
Explanation The cluster has not stopped. Action Check the status of the cluster again. - CWWSY0341W: Cluster {0} was partially started. The current cluster status at the end of the timeout is {1} of {2} cluster members are running: {3}
Explanation Not all the members in the cluster have started. Action Check the status of the cluster again. - CWWSY0342W: Cluster {0} was partially stopped. The current cluster status at the end of the timeout is {1} of {2} cluster members are stopped: {3}
Explanation Not all the members in the cluster have stopped Action Check the status of the cluster again. - CWWSY0343E: Application {0} was partially started. {1} of {2} targets are started: {3}.
Explanation Not all the targets have started the application. Action Check the status of the application again. - CWWSY0344E: Application {0} was partially stopped. {1} of {2} targets are stopped: {3}.
Explanation Not all the targets have stopped the application. Action Check the status of the application again. - CWWSY0400E: Managed node UUID is not valid: {0}
Explanation The ID is not known to this system. Action Check if the ID has typos or other errors in it. - CWWSY0401E: Job manager UUID is not valid: {0}
Explanation This is not a valid job manager ID with which any of the managed nodes is registered. Action Check if the ID has typos or other errors in it. - CWWSY0402E: Unable to connect to job manager due to exception: {0}
Explanation JMX connection could not be established with the job manager. Possible causes include job manager not started; connector data supplied is not correct; authentication failed. Action Ensure the server is running and the connection data are correct. - CWWSY0403E: Registration failed due to exception from job manager: {0}
Explanation The cause may be revealed by the embedded job manager exception. Action Analyze the job manager exception and enable job manager trace for further investigation. - CWWSY0404E: Unregistration failed due to exception from job manager: {0}
Explanation The cause may be revealed by the embedded job manager exception. Action Analyze the job manager exception and enable job manager trace for further investigation. - CWWSY0405E: Managed node to register, {0}, is not a registered managed node.
Explanation The managed node to register is not in the list returned by command listRegisteredNodes, and this agent can only use registered managed nodes. Action Register the managed node first. - CWWSY0406E: Registration failed due to empty result returned from job manager
Explanation Registration call to the job manager returned empty result. Action Enable trace in the job manager and analyze the output. - CWWSY0407E: Unregistration failed due to empty result returned from job manager
Explanation Unregistration call to the job manager returned empty result. Action Enable trace in the job manager and analyze the output. - CWWSY0409E: Could not validate managed node ID {0} due to failed call to command listRegisteredNodes
Explanation Call to command listRegisteredNodes failed. Action Analyze admin agent trace to see why the call failed. - CWWSY0410E: Managed node UUID {0} is not known to this agent, thus cannot be registered through this agent
Explanation The managed node is not registered through this agent. Action Ensure the managed node UUID supplied is correct. - CWWSY0411W: Failed to get System property user.install.root; will create the devicestores in the current directory instead.
Explanation System property user.install.root is not defined. Action No user action required. - CWWSY0412E: Directory {0} is not created due to Throwable {1}; will not be able to persist registered managed node data.
Explanation A directory cannot be created, probably due to a system constraint. Action Find the cause and correct it. - CWWSY0413W: Managed node persistent store {0} is probably corrupted; all existing registration data are lost.
Explanation The file for the persistent store is corrupted. Action Find out why the file is corrupted and correct the condition, so in the future the managed nodes can be persisted. - CWWSY0414W: Failed to retrieve account data due to exception {0}; the returned Properties will be empty.
Explanation The ID used to retrieve the data is probably wrong. Action Ensure correct ID is used. - CWWSY0415E: Unexpected error, {0}, happened during the forever job dispatching loop.
Explanation This is probably due a system failure. Action Find the cause and correct it. - CWWSY0416E: An error, {0}, occurred during a session with the job manager.
Explanation It can be a connection issue or job manager malfunction. Action Ensure the job manager is working normally, and the connection link is sound. - CWWSY0417E: An error occurred during a session with the job manager; the error message is: {0}.
Explanation It can be a connection issue or job manager malfunction. Action Ensure the job manager is working normally, and the conection link is sound. - CWWSY0418W: The ID, {0}, supposedly represents an existing managed node, but it failed to restore at server restart due to exception {1}.
Explanation Could not restore a registered managed node due to unexpected error. Action Find the cause of the error and correct it. - CWWSY0419E: As managed node {0} is unregistered from job manager {1}, an error arose from locating the SessionDispatcher or from shutting it down: {2}.
Explanation The unregistration will continue, but it might not be cleanly done. Action Find the cause of the error and correct it. - CWWSY0420E: As managed node {0} is unregistered from job manager {1}, an error arose from cleaning up the job manager data: {2}.
Explanation The unregistration will continue, but it might not be cleanly done. Action Find the cause of the error and correct it. - CWWSY0421E: No managed node found with UUID {0}; registration entry for job manager {1} cannot be added or removed.
Explanation A managed node with the given UUID does not exist in the system configuration, or its configuration file has been corrupted. Action Check system configuration for the managed node. - CWWSY0422E: Adding or removing a configuration entry failed, due to exception {0}
Explanation Unexpected error occurred. Action Report to IBM tech support. - CWWSY0423E: The name {0} does not represent an existing managed node
Explanation There is not a managed node with the given name in the configuration. Action Check if wrong name was entered. - CWWSY0424E: Managed node {0} has no corresponding UUID
Explanation The managed node does not have the UUID property defined. Action Examine the managed node configuration and ensure it has the UUID property defined. - CWWSY0425E: No specific job manager UUID can be determined from the input data
Explanation User-entered job manager URL host name, port number, or managed node name may not be valid. Action Reenter the correct data - CWWSY0426E: An error occured when trying to create the managed node configuration for the deployment manager.
Explanation An error occurred when trying to create the managed node configuration for the deployment manager. Action See the wrapped exception for the cause of the error. - CWWSY0427I: The job manager at the {0} host and {1} port cannot be contacted.
Explanation A connection cannot be established with the job manager. This connection problem most often occurs because the job manager is not running. Job manager polling will continue and any pending information will be exchanged after communication is re-established. Action Ensure that the job manager server is running and the connection information is correct. - CWWSY0428E: The job manager at the {0} host and {1} port is at an older level than the node. The job manager version must be equal to or greater than the node version. No jobs are retrieved for this node from the job manager.
Explanation A node cannot communicate with a job manager that is at an earlier version. Polling with this job manager is stopped. Action Upgrade the job manager to be the same level or higher than the node. After upgrading the job manager, use the startPollingJobManager command from the deployment manager or admin agent to restart job polling. - CWWSY0601E: Problem while processing job {0}.
Explanation Internal error occurred during job processing. Action Make sure that the deployment manager"s federated nodes are running. - CWWSY0602E: Parameter {0} is not valid for job {1}.
Explanation The job could not be completed due to the parameter. Action Try the command again with valid parameters. - CWWSY0603E: Required Parameter {0} was missing while processing job {1}.
Explanation The job could not be completed due to the missing required parameter. Action Try the command again with the required parameter. - CWWSY0604E: Job {0} is only available at a Deployment Manager.
Explanation The job can only be executed at a Deployment Manager in a WebSphere Network Deployment environment. Action Try the job on a Deployment Manager target. - CWWSY0605E: Problem while executing job {0}. Cause: {1}.
Explanation Internal error occurred during job execution. Action Verify that the job parameters have the correct content and type. - CWWSY0606E: Could not find cluster {0} while executing job {1}.
Explanation The job could not be completed because the cluster could not be found. Action Verify that the cluster name is correct. - CWWSY0607I: Job {0} succeeded because {1} already existed.
Explanation The submitted job was successfully executed. Action Read the message and explanation. - CWWSY0608I: Job {0} failed because {1} was not found.
Explanation The submitted job was not successfully executed. Action Read the message and explanation. - CWWSY0609I: Job {0} succeeded.
Explanation The submitted job was successfully executed. Action Read the message and explanation. - CWWSY0610I: Job {0} succeeded because {1} was already in the {2} state.
Explanation The submitted job was successfully executed. Action Read the message and explanation. - CWWSY0611E: Job {0} could not be completed because the value for parameter {1} is not valid. Acceptable Values: {2}.
Explanation The submitted job had a parameter with a value that is not valid. Action Provide a correct value for the job parameter. - CWWSY0612E: Job {0} script execution failed. Return code was {1}. Last messages: {2}
Explanation The job failed because there was an error in the script execution. Action Inspect the SystemOut for errors. - CWWSY0613E: Job {0} failed because script file could not be found.
Explanation The script to run could not be located. Action Provide the correct script file path. - CWWSY0614E: Job {0} failed because cluster {1} does not contain a member with name {2} on a node named {3}.
Explanation The cluster member can not be found. Action Ensure you have permission to the cluster, or that the cluster member exists. - CWWSY0615I: Job {0} failed because cluster {1} was not found. Either the cluster does not exist, or you do not have permission.
Explanation Cluster can not be found. Either the cluster does not exist, or you do not have permission to access the cluster. Action Ensure the cluster exists, and that you have permission to the cluster. - CWWSY0616I: Job {0} script execution succeeded.
Explanation The job succeeded. Action Inspect the log file for output from script execution. - CWWSY0617I: Job {0} script execution succeeded. Last messages: {1}
Explanation The job succeeded. Action Inspect the log file for output from script execution. - CWWSY0618I: Queuing job {0} for target {1}.
Explanation The job was received from the job manager and waiting in a queue to be dispatched to the target. Action No user action required. - CWWSY0619I: Dispatching {0} job {1} to target {2}.
Explanation The job started running on the target. Action No user action required. - CWWSY0620I: Completed {0} job {1} on target {2} with job status {3}.
Explanation The job completed running on the target. Action No user action required. - CWWSY0700E: Access denied. The following administrative role in at least one authorization group is required: {0}.
Explanation The user must be assigned the given role either at the cell level, or in at least one authorization group. Action Assign the user the required role for the cell, or in at least one authorization group. - CWWSY0701E: Permission denied accessing file {0}. The following administrative role is required: {1}.
Explanation The job failed due to insufficient permission to access a file. Action Assign the user the required permission. - CWWSY0702E: Problem while processing {0} operation with following message: Unable to find {1}.
Explanation Cannot find the MBean for Application Manager on the server. Action Restart the server and make sure the Application Manager MBean starts. - CWWSY0801I: Job {0} is marked as failed because the job manager stopped processing.
Explanation The job manager stopped after the job was dispatched,but before the job completed. Because the job manager can no longer track the current job status, the job is marked as failed. Action Check the accurate status of the job on the remote host to which the job was dispatched. - CWWSY0802E: Operation {0} is not a valid operation for server {1}
Explanation The job manager prevented the operation because it is not a valid operation for the server that was chosen. Action Perform the operation on an application server of a managed node. - CWWSY1000E: Unable to retrieve job manager RSA certificate due to exception {0}
Explanation There is a problem retreiving the job manager""s RSA certificate. Job manager clients are unable to securely connect to the job manager without the RSA certificate. Action Refer to the exception. Check FFDC for certificate related problems. Check the job manager""s RSA certificate, and update if it has expired. - CWWSY1001E: Failed to get ChannelFrameworkService due to {0}; Status listener port will not be available
Explanation At the point the status listener port is to get initialized and started, the channel framework is not available yet. Action Verify the channel framework is initialized correctly. - CWWSY1002E: ChannelFrameworkService is unavailable at this point; status listener port will not be available
Explanation At the point the status listener port is to get initialized and started, the channel framework is not available yet. Action Verify the channel framework is initialized correctly. - CWWSY1003E: Failed to initialize or start channel chain {0} due to exception {1}
Explanation A channel framework chain for the status listener port failed to initialize or start. Action Verify the channel framework is functioning correctly. - CWWSY1004I: The status listener port is available at port {0}
Explanation This informational message indicates the availability of the status listener port. Action No action is required. - CWWSY1005E: Failed to stop channel chain {0} due to exception {1}
Explanation A channel framework chain for the status listener port failed to stop. Action Verify the channel framework is functioning correctly. - CWWSY1006W: Unable to configure resource {0} to report status due to exception {1}
Explanation A resource could not be configured to report status due to an exception. Action Refer to the exception. Check FFDC for related problems. - CWWSY1007W: Configuration of resources to report status prevented by an exception {0}
Explanation Resources could not be configured to report status due to an exception before the configuration is attempted. Action Refer to the exception. Check FFDC for related problems. - CWWSY1008E: Unable to delete keystore {0} due to exception {1}
Explanation The obsolete keystore used for resource configuration could not be deleted. Action Manually delete the keystore. - CWWSY1009I: Status configuration successfully deployed to resource {0}
Explanation The configuration necessary for the resource to report status has been installed on the resource. Action No action is required.