WSCL

WSCL0001I: Command line, property file, and system property arguments resolved to:

File to launch = {0}

CC Property File = {1}

Client Jar File = {2}

Alternate DD = {3}

BootstrapHost = {4}

BootstrapPort = {5}

Trace enabled = {6}

Tracefile = {7}

Init only = {8}

Classpath Parameter = {9}
WSCL0002I: Setting DataSource Property {0} to value {1} on DataSource {2}.
WSCL0003I: Establish a setter method on the DataSource {0} for the Property {1}.
WSCL0004I: Setting resource Property {0} to value {1}.
WSCL0005I: JMS resource using supplied JNDI binding mechanism: {0}.
WSCL0006I: JMS resource using an indirectly supplied JNDI binding mechansim: {0}.
WSCL0007I: Loading the default resource binders.
WSCL0008I: Adding binder {0} from the properties file.
WSCL0009I: No binders were found in the properties file.
WSCL0010I: Resource binders loaded successfully.
WSCL0011I: Stack Trace: {0}
WSCL0012I: Processing command line arguments.
WSCL0013I: Initializing the Java EE Application Client Environment.
WSCL0014I: Invoking the Application Client {0}
WSCL0015I: Processing the Application Client archive file: {0}.
WSCL0016I: Using temporary directory {0}.
WSCL0017I: Loading the Main class {0} for the Application Client jar file {1}.
WSCL0018I: Processing Resource Provider factory: {0}.
WSCL0019I: Found Resource Provider factory of type: {0}.
WSCL0020I: Processed Resource Provider of type: {0}.
WSCL0021I: Opening archive file: {0}.
WSCL0022I: Searching for the resource respository.
WSCL0023I: The resource respository was not found. Creating a new repository: {0}
WSCL0024I: Adding {0} {1} to the JNDI table.
WSCL0025I: Binding EJB reference object:

JNDI name: {0}

Description: {1}
WSCL0026I: Adding EJB references defined in the properties file.
WSCL0027I: No EJB references defined in the properties file.
WSCL0028I: Binding environment entry:

JNDI name: {0}

Type: {1}

Value: {2}

Description: {3}
WSCL0029I: Binding resource reference object:

JNDI name: {0}

Type: {1}

Description: {2}
WSCL0030I: No resource provider references configured for this provider.
WSCL0031I: The object was bound successfully.
WSCL0032I: Loading the following URLs with the class loader: {0}
WSCL0033I: The main class was loaded with: {0}
WSCL0034I: Binding Enterprise Extension resource {0}
WSCL0035I: Initialization of the Java EE Application Client Environment has completed.
WSCL0036I: Parsing classpath: {0}
WSCL0100E: Exception received: {0}
WSCL0101E: An invalid or missing parameter on launchClient. See help message on launchClient.
WSCL0102E: Missing property value for -CC parameter: {0}.
WSCL0103E: An invalid -CC property value was specified: {0}.
WSCL0104E: The required parameter specifying the EAR file for the client application was null.
WSCL0105E: Cannot launch more than one Java EE application per Java Virtual Machine.
WSCL0106W: The parameter {0} has been deprecated and will not be used.
WSCL0120E: The JDBC property {0} is required.
WSCL0121E: The Class for DataSource {0} was not found: {1}
WSCL0122E: Received an IllegalAccessException while attempting to access or create DataSource {0}: {1}
WSCL0123E: Received an IllegalAccessException while attempting to access Property {0} on DataSource {1}: {2}
WSCL0124E: Received an InstantiationException while attempting to create DataSource {0}: {1}
WSCL0125E: Received an IllegalArgumentException while attempting to set the value for DataSource Property {0} on DataSource {1}. Unknown parameters are required. : {2}
WSCL0126E: Received an InvocationTargetException while attempting to set the value for DataSource Property {0} on DataSource {1}: {2}
WSCL0127W: Encountered an unsupported DataSource Property {0}: {1}
WSCL0128E: Unable to establish a setter method for Property {0} on DataSource {1}.
WSCL0129E: The DataSource classname {0} is not of the required type javax.sql.DataSource.
WSCL0130E: The specified object reference for creating of the DataSource is not of the required type javax.naming.Reference.
WSCL0131E: Received an IntrospectionException while attempting to introspect DataSource {1}: {2}
WSCL0150W: Unknown JMS resource type: {0}
WSCL0151W: The property value for Property {0} for the {1} Resource was set to an invalid value of {2}.
WSCL0152W: The Class for the JNDI binding mechanism {0} was not found.
WSCL0153W: The required constructor for the JNDI binding mechanism {0}(java.util.Properties) was not found: {1}
WSCL0154W: Unable to construct an instance of JNDI binding mechanism {0}(java.util.Properties)
WSCL0155W: The URL specification {0} is not valid.
WSCL0156W: Unable to create a URL resource because:
WSCL0157W: Unable to decode the password for resource {0} when attempting to set property {1}.
WSCL0158W: Unable to create a mail resource with properties: {0} because:
WSCL0159W: Unable to create a data source resource with properties: {0} because:
WSCL0160W: An unexpected classloader {0} was used to load class {1} for resource {2}.
WSCL0161E: The resource configuration information is not compatible with the resource type {0}. The object was not bound into the namespace.
WSCL0162W: The following classpath entries do not exist on the local system: {0}
WSCL0200E: The Enterprise Archive file {0} does not contain an Application Client jar file.
WSCL0201E: No manifest entry found in Application Client jar file {0}.
WSCL0202E: The manifest file for the Application Client jar file {0} located in the Enterprise Archive file {1} does not contain a Main-Class entry for the client application main class.
WSCL0203E: Unable to locate the Application Client jar file {0} in the Enterprise Archive file {1}.
WSCL0204W: Failed to start the process to remove the temporary directory {0}.
WSCL0205W: The incorrect class loader was used to load {0}
WSCL0206E: File {0} is not a valid Enterprise Archive file.
WSCL0207E: Jar file {0} in Enterprise Archive file {1} is not an Application Client jar file.
WSCL0208E: System property {0} cannot be set to a file.
WSCL0209E: Failed to create archive directory {0}.
WSCL0210E: The Enterprise archive file {0} could not be found.
WSCL0211E: The specified client jar file {0} is configured with multiple deployment descriptors. Use the -CCaltDD parameter to specify which one should be used.
WSCL0212E: The specified client jar file {0} with the specified alternate deployment descriptor {1} cannot be found in the Enterprise archive file.
WSCL0213E: The specified client jar file {0} with the specified alternate deployment descriptor {1} is not an application client archive module.
WSCL0220E: An unsuccessful attempt was made to find the resource configuration information for {0}.
WSCL0280W: An EJB object could not be created because the name is null.
WSCL0300W: An environment object could not be created for {0} because the value of {1} is not valid for type {2}.
WSCL0301W: An environment object could not be created for {0} because the type {1} is not supported.
WSCL0330W: Unable to update the classpath for resource {0} because the classpath {1} specified in the client resource configuration file is not in the correct format.
WSCL0331E: An unexpected error occurred while trying to create URL stream handler class {0} for protocol {1}.
WSCL0332E: The resource configuration file is at the incorrect version. Use the Application Client Resource Configuration Tool (clientConfig command) to migrate the resources.
WSCL0350W: Unable to create a resource for {0} because the following error occurred:
WSCL0351W: Unable to create a resource for {0} because the resource type {1} specified in the Application Client deployment descriptor is not supported. Verify the type specified on the <res-type> entry is one of the following: {2}
WSCL0370W: An unexpected error occurred while trying to bind an Enterprise Extension resource.
WSCL0400I: Binding resource environment reference object:

JNDI name: {0}

Type: {1}

Description: {2}
WSCL0401I: Binding message destination reference object:

JNDI name: {0}

Type: {1}

Description: {2}
WSCL0500E: Exception received: {0}
WSCL0500I: Creating security callback handler class: {0}
WSCL0501E: Could not encrypt the password, because an unknown error occurred.
WSCL0501I: Security callback handler created successfully.
WSCL0502E: Security callback handler class could not be created because:
WSCL0503E: The configured callback handler class {0} cannot be used because it does not implement the {1} interface.
WSCL0504E: Error opening ear file:

{0}

Be sure the file is in proper format and try again
WSCL0505E: Error saving to archive:

{0}

Be sure the file is not in use by another program and try again
WSCL0506E: The resource already exists

Choose a different name for this resource
WSCL0507E: Values missing for the required fields labeled with a red asterisk.
WSCL0508E: Passwords do not match
WSCL0510E: The port value must be a positive numeric value <= 2147483647
WSCL0511E: The password entered in field {0} does not match the Re-Enter Password field.
The Re-Enter password field can be found right below the {0} field.
WSCL0512E: The CCSID value must be a numeric value between -2147483648 and 2147483647
WSCL0514E: A long value greater than 0 must be entered

into the specified expiry field.
WSCL0515E: An integer value between 0 and 9 must be entered

into the specified priority field.
WSCL0516E: A long value greater than or equal to 0 must be entered

into the specified time to live field.
WSCL0517E: The polling interval value must be a positive numeric value <= 2147483647
WSCL0518E: The cleanup interval value must be a positive numeric value <= 9223372036854775807
WSCL0519E: The pub ack interval value must be a positive numeric value <= 2147483647
WSCL0520E: Received an ClassNotFoundException while attempting to

start the Application Client Resource Configuration Tool
WSCL0521E: Received an UnsupportedLookAndFeelException while attempting to

start the Application Client Resource Configuration Tool
WSCL0522E: Received an IllegalAccessException while attempting to

start the Application Client Resource Configuration Tool
WSCL0523E: Received an InstantiationException while attempting to

start the Application Client Resource Configuration Tool
WSCL0530E: An error occurred while saving to archive:

{0}

A temporary file containing the current state of the tree has been created.

It is recommended that you close all instances of the

Application Client Resource Configuration Tool

and load the file again.
WSCL0531E: An error occurred while saving to archive:

{0}

It is recommended that you close all instances of the

Application Client Resource Configuration Tool

and load the file again.
WSCL0532E: The queue manager port value must be a numeric value between -2147483648 and 2147483647
WSCL0533E: A browser could not be launched to display help
WSCL0534E: Please provide at least one protocol provider
WSCL0535E: The resource information for the Application Client

modules in this ear file cannot be used because they

were created in a previous version of WebSphere.

In order to use this ear file on this version of WebSphere

the resources must be migrated using the stand alone Client Upgrade migration tool or

the resource information must be removed and reconfigured.


Would you like to close this ear file and return to the main panel so you can run the migration tool?


Press the Yes button to close this ear file and return to main panel.

Once the Client Upgrade migration tool has been run on this ear file, reopen the migrated ear file.

Press the No button to remove the current resource configuration information and reconfigure the

resources. Pressing this button removes all the current configuration information.
WSCL0536E: This protocol provider is used by a mail session.

Please unselect the protocol in the mail session and try again.
WSCL0537W: You have selected to remove all the client resource configuration information from this ear file.

If you have more than one Application Client module, the client resource configuration information is removed from

all the Application Client modules. A backup copy of this information is made, however this tool does not provide a mechanism

to restore the backup.


Would you like to continue and remove the all the client resource configuration information?
WSCL0538E: File {0} could not be found.


Select a different file and try again.
WSCL0539I: The old resource configuration was successfully backed up and the ear file was successfully saved.
WSCL0540E: The status refresh interval value must be a positive numeric value <= 2147483647
WSCL0541E: The proxy port value must be a numeric value between -2147483648 and 2147483647
WSCL0542E: The rescan interval value must be a numeric value between -2147483648 and 2147483647
WSCL0543E: The connection name list value must be of the form "host(port),host(port)", where port is optional and defaults to 1414. For example: "hostname1(1414),hostname2".
WSCL0544E: The client reconnect interval must be a positive numeric value greater than or equal to 2147483647.
WSCL0550E: Help file {0} was not found
WSCL0551E: Help file {0} may be corrupt
WSCL0552E: Could not start browser with command {0}
WSCL0560W: The new Default Messaging Provider cannot be created. This may be

\ the result of a missing or incomplete installedConnectors directory. You can continue

\ and create resources for the other providers or exit the tool, fix the problem, and try again.


\ Details: {0}.
WSCL0600I: Binding HandleDelegate object.
WSCL0601E: The HandleDelegate could not be bound because:
WSCL0700E: The JMS classname {0} is not of the required type.
WSCL0701E: The specified object reference for creating the JMS object is not of the required type javax.naming.Reference.
WSCL0702E: Unable to establish a setter method for Property {0} on object {1}.
WSCL0703E: Received an IllegalAccessException while attempting to access Property {0} on object {1}: {2}
WSCL0704E: Received an IllegalArgumentException while attempting to set the value for Property {0} on object {1} : {2}
WSCL0705E: Received an InvocationTargetException while attempting to set the value for Property {0} on JMS object {1} : {2}
WSCL0800I: Creating security manager: {0}
WSCL0801I: Security manager created and enabled successfully.
WSCL0802W: A security manager is already enabled for this process. The specified security manager {0} will not be used.
WSCL0803E: Unable to continue because the specified security manager could not be created for the following reason:
WSCL0900I: Initializing and starting components.
WSCL0901I: Component initialization completed successfully.
WSCL0902I: Component initialization completed, however some components failed to initialize.
WSCL0903E: Component initialization failed for the following reason:
WSCL0910I: Initializing component: {0}
WSCL0911I: Component initialized successfully.
WSCL0912E: Component failed to initialize.
WSCL1001E: The Java EE Connector Architecture specification version must be, at a minimum, 1.5 for the resource adapter. The resource adapter is not installed
WSCL1002E: The resource adapter does not contain any outbound resource adapter definitions. The resource adapter is not installed.
WSCL1003E: Error extracting archive: directory {0} does not exist or is not a directory.
WSCL1101I: The specified installed connectors directory {0} does not exist.
WSCL1102W: The specified installed connectors directory {0} is not a directory.
WSCL1201E: The following injection exception occurred for the handling PostConstruct method: {0}
WSCL1202E: The following injection exception occurred for the handling PreDestroy method: {0}
WSCL1203W: More than one PostConstruct or PreDestroy method exists in the {1} class. The {0} PostConstruct or PreDestroy method will not be invoked by the container.
WSCL1204E: The container cannot create an EntityManagerFactory object in the {0} persistence unit for dependency injection. The persistence unit is in the {2} client module of the {1} application.
WSCL1205W: A duplicate binding entry found for {0} name {1}.
WSCL1206E: The NamingException occurred while trying to resolve a resource reference for: {0}
WSCL3001E: Neither the com.ibm.websphere.client.launcher.ear property, nor the com.ibm.websphere.client.launcher.main property is set.
WSCL3002E: WebSphere Application Client runtime installation root cannot be found.
WSCL3003E: The Java Runtime Environment is not valid.
WSCL3004E: Ear file not found: {0}
WSCL3005E: The orb.properties file cannot be found in the class path or in ${java.home}/lib.
WSCL3006E: Unknown I/O error.
WSCL3007E: Fail to setup system class path.
WSCL3100E: Unable to find the JAR file containing the license agreement panel classes in the class path.
WSCL3101E: Unable to display the license agreement panel, rc = {0}.
WSCL3102E: An unexpected error has occurred.
WSCL3103E: Unable to install the Application Client Container runtime.
WSCL3200E: Too many input arguments.
WSCL3201E: Too few input arguments.
WSCL3203E: The keystore file does not exist.
WSCL3204E: Keystore file error.
WSCL3205E: The alias name is not valid.