CWWKY

CWWKY0001I: Issuing stop for job execution {0} because the batch component is deactivating.
CWWKY0002I: The batch component is deactivating. Stop requests have been issued for all active job executions. The following job executions were still running at the time of deactivation: {0}.
CWWKY0003E: The JSL (Job XML document) at URL {0} is not valid according to the Job XML schema. The first validation error logged by JAXB validator was: {1}.
CWWKY0004E: The JSL (Job XML document) name: {0} was not found at the location: {1} within the application archive.
CWWKY0005I: The batch {0} persistence service is {1}.
CWWKY0006W: The batch job recovery service is unable to correct the batch status for a previously running job instance {0} that has terminated. The correction failed due to exception {1}.
CWWKY0007W: The batch job recovery service is unable to correct the batch status for previously running jobs that have terminated. The correction failed due to exception {0}.
CWWKY0008I: The batch feature is using persistence type {0}.
CWWKY0009I: Job {0} started for job instance {1} and job execution {2}.
CWWKY0010I: Job {0} ended with batch status {1} and exit status {2} for job instance {3} and job execution {4}.
CWWKY0011W: Job {0} failed with batch status {1} and exit status {2} for job instance {3} and job execution {4}.
CWWKY0012I: Partition {0} started for step {1} for job instance {2} and job execution {3}.
CWWKY0013I: Partition {0} ended with batch status {1} and exit status {2} for step {3} for job instance {4} and job execution {5}.
CWWKY0014W: Partition {0} failed with batch status {1} and exit status {2} for step {3} for job instance {4} and job execution {5}.
CWWKY0015I: Flow {0} started for job instance {1} and job execution {2}.
CWWKY0016I: Flow {0} ended for job instance {1} and job execution {2}.
CWWKY0017W: Flow {0} failed for job instance {1} and job execution {2}.
CWWKY0018I: Step {0} started for job instance {1} and job execution {2}.
CWWKY0019W: Step {0} failed with batch status {1} and exit status {2} for job instance {3} and job execution {4}.
CWWKY0020I: Step {0} ended with batch status {1} and exit status {2} for job instance {3} and job execution {4}.
CWWKY0021I: A new chunk was started for step {0} in job instance {1} and job execution {2}. Step metrics = {3}
CWWKY0022I: The chunk successfully ended for step {0} in job instance {1} and job execution {2}. Step metrics = {3}
CWWKY0024W: The current chunk was rolled back to the previous checkpoint for step {0} in job instance {1} and job execution {2}. Step metrics = {3}
CWWKY0025W: Processing rollback for current chunk after a retryable exception for step {0} in job instance {1} and job execution {2}. Step metrics = {3}
CWWKY0026I: The item reader for step {0} was opened.
CWWKY0027I: The item reader for step {0} was closed.
CWWKY0028I: The item writer for step {0} was opened.
CWWKY0029I: The item writer for step {0} was closed.
CWWKY0030I: An exception occurred while running the step {0}. {1}
CWWKY0031I: An exception occurred while running the final portion of step {0}. {1}
CWWKY0032I: An exception occurred while trying to persist step execution status and related data. {0}
CWWKY0033I: An exception occurred while executing the job. {0}
CWWKY0034I: An exception occurred while running the final portion of the job. {0}
CWWKY0035I: An exception occurred while trying to persist job execution status and related data. {0}
CWWKY0036E: Invalid job instance id value {0} generated as the primary key value for a batch table. The id value must be a positive integer. {1}
CWWKY0037E: Invalid job execution id value {0} generated as the primary key value for a batch table. The id value must be a positive integer. {1}
CWWKY0038E: Invalid step execution id value {0} generated as the primary key value for a batch table. The id value must be a positive integer. {1}
CWWKY0039W: The batch job recovery service is unable to correct the batch status for a previously running partition {0} that has terminated. The correction failed due to exception {1}.
CWWKY0040I: The batch runtime will publish events to JMS topic root {0}.
CWWKY0101I: Job {0} with instance ID {1} has been submitted.
CWWKY0102I: A restart request has been submitted for job {0} with instance ID {1}.
CWWKY0103I: Job {0} with instance ID {1} has stopped. Batch status: {2}. Exit status: {3}
CWWKY0104I: A stop request has been submitted for job {0} with instance ID {1}.
CWWKY0105I: Job {0} with instance ID {1} has finished. Batch status: {2}. Exit status: {3}
CWWKY0106I: JobInstance:{0}
CWWKY0107I: JobExecution:{0}
CWWKY0108I: Waiting for termination of JobExecution:{0}
CWWKY0109I: Waiting for the latest job execution for job with instance ID {0}
CWWKY0110I: Waiting for the next job execution after JobExecution:{0}
CWWKY0111I: The joblog was written to file {0}
CWWKY0112I: A request for the batch manager at {0} failed. Forwarding the request to the batch manager at {1}. The failure was: {2}
CWWKY0113I: The joblog for job {0} with instance ID {1} will be downloaded when the job completes. In the meantime, you may view the joblog by following the links here: {2}
CWWKY0114I: The joblog for job {0} with instance ID {1} is being downloaded via {2}.
CWWKY0115I: Job {0} with instance ID {1} has been successfully purged.
CWWKY0116I: The client utility was shut down while waiting for job {0} with instance ID {1} to finish.
CWWKY0117I: Attempt to purge job with instance id {0} returned status: {1}. Message: {2} RedirectUrl: {3}
CWWKY0118I: The final set of job parameters are {0}
CWWKY0119I: The final set of control properties are {0}
CWWKY0120W: Property {0} cannot be used in a control properties file and will be ignored. Property {0} can only be used on the command line.
CWWKY0151E: No job instance found for instance id {0}.
CWWKY0152E: The batch management REST API invocation URL is not supported for in-memory batch persistence.
CWWKY0153E: The job repository database doesn't support search or delete by job parameters because no JOBPARAMETER table exists in database.
CWWKY0200W: The {0} message type of this batch JMS message is not supported. This request will not be processed. The content of this message is {1}
CWWKY0201W: The {0} operation is an unsupported operation of a batch JMS message. This request will not be processed. The content of this message is {1}
CWWKY0202W: The message endpoint for the batch {0} JMS listener cannot be activated because the batch {1} activation specification does not exist in the server configuration. The message endpoint will not receive batch messages until the batch activation specification becomes available.
CWWKY0203W: The message endpoint for the batch {0} JMS listener cannot be activated because the {1} destination queue does not exist. The message endpoint will not receive batch JMS messages until the destination queue becomes available.
CWWKY0204W: The batch JMS dispatcher cannot be started because the {0} connection factory does not exist. The batch JMS dispatcher will not send batch JMS messages until the connection factory becomes available.
CWWKY0205W: The batch JMS dispatcher cannot be started because the {0} queue does not exist. The batch JMS dispatcher will not send batch JMS messages until the queue becomes available.
CWWKY0206E: The batch JMS dispatcher encountered an exception when dispatching the start request for job instance {0} and was unable to rollback the operation. The exception is {1}.
CWWKY0207E: The batch JMS dispatcher encountered an exception when dispatching the restart request job execution {0} and was unable to rollback the operation. The exception is {1}.
CWWKY0208E: The batch JMS listener encountered an exception when processing message {0}. The exception is {1}.
CWWKY0209E: The batch JMS listener encountered an exception when processing the start job operation for job instance {0}. The exception is {1}.
CWWKY0210E: The batch JMS listener encountered an exception when processing the restart job operation for job execution {0}. The exception is {1}.
CWWKY0211W: The batch runtime cannot publish event to topic {0} for object {1}. The exception is {2}.
CWWKY0212E: Unable to create JMS resource for batch events publisher. The exception is {0}.
CWWKY0213E: Unable to create JMS resource for batch dispatcher. The exception is {0}
CWWKY0214W: Discarding message with associated job execution id {0} since it was not the newest execution.
CWWKY0215E: The batch partition could not be started due to an exception. The exception is {0}.
CWWKY0216E: Unable to create JMS Connection factory for executing remote partitions. The exception is {0}
CWWKY0217E: Unable to activate JMS Executor on endpoint due to an exception {0}
CWWKY0218I: The batch runtime will publish events to JMS topic root {0}.
CWWKY0250I: The batch listener for z/OS Local Adapter (WOLA) requests has been activated and is registered with JNDI name {0}
CWWKY0251I: The batch listener for z/OS Local Adapter (WOLA) requests has been deactivated.
CWWKY0300I: Batch security is enabled.
CWWKY0301I: Batch security is disabled.
CWWKY0302W: User {0} is not authorized to perform batch operations associated with job instance {1}.
CWWKY0303W: User {0} is not authorized to perform any batch operations.
CWWKY0304W: User {0} is not authorized to start batch jobs.
CWWKY0350E: The batch container is not activated. Ensure that batch persistence has been configured via the configuration element {0}.
CWWKY0400E: Batch job logging did not start for job {0}, job instance {1}, job execution {2}, due to exception. {3}
CWWKY0401W: Batch job logging did not create additional log part files due to exception. {0} Batch job logging will attempt to continue with current file.
CWWKY0402W: Batch job logging did not read the log part file due to exception. {0}
CWWKY0403W: Batch job logging did not delete the following log part file or directory: {0}.