CWLRB

CWLRB1000E: [Long Running Job Container RAS failure] [caller {0}] [probe {1}] [bundle {2}]: Missing Resource Bundle
CWLRB1020E: [Long Running Job Container RAS failure] [caller {0}] [probe {1}] [bundle {2}]: Key not found
CWLRB1040E: [Long Running Job Container RAS failure] [caller {0}] [probe {1}] [bundle {2}]: Invalid property in Resource Bundle
CWLRB1060E: [Long Running Job Container RAS failure]: {1}
CWLRB1080E: Long Running Job Container Batch Data Stream Manager unable to get xJCL definitions for job {0}
CWLRB1100E: [Long Running Job Container Batch Data Stream Manager initialize state failed] [step {0}] [name {1}]: {2}
CWLRB1120E: [Long Running Job Container Batch Data Stream Manager get Batch Data Stream {0} failed]: {1}
CWLRB1140E: [Long Running Job Container close input Batch Data Stream {0} failed]: {1}
CWLRB1160E: [Long Running Job Container open input Batch Data Stream {0} failed]: {1}
CWLRB1180E: [Long Running Job Container close output Batch Data Stream {0} failed]: {1}
CWLRB1200E: [Long Running Job Container open output Batch Data Stream {0} failed]: {1}
CWLRB1220E: [Long Running Job Container put to output Batch Data Stream {0} failed]: {1}
CWLRB1240E: Batch Configuration File {0} does not exist
CWLRB1260E: Invalid checkpoint algorithm count {0} in Batch Configuration File {1}
CWLRB1280E: Invalid results algorithm count {0} in Batch Configuration File {1}
CWLRB1300E: Batch Configuration File {0} defines no default checkpoint algorithm
CWLRB1320E: Batch Configuration File {0} defines no default results algorithm
CWLRB1340E: [Long Running Job Container Grid Job Execution Environment initialize homes failed]: {0}
CWLRB1360E: [Grid Job Execution Environment init failed config]: {0}
CWLRB1380E: [Grid Job Execution Environment init failed]: {0}
CWLRB1400I: Grid Job Execution Environment {0} is initialized
CWLRB1420E: [Long Running Job Container start {0} checkpoint failed]: {1}
CWLRB1440E: [Long Running Job Container stop {0} checkpoint failed]: {1}
CWLRB1460E: [Grid Execution Environment {0} checkpoint() failed]: {1}
CWLRB1480E: [Long Running Job Container initialize {0} checkpoint failed] [JobID {1}]: {2}
CWLRB1500E: [Long Running Job Container prepare for checkpoint failed]: {0}
CWLRB1520E: [Long Running Job Container [Batch Data Stream {0}] [job {1}] prepare for checkpoint failed]: {2}
CWLRB1540E: [Long Running Job Container rollback checkpoint failed]: {0}
CWLRB1560E: [Long Running Job Container condition evaluation failed for job {0}]: {1}
CWLRB1580E: [Long Running Job Container push message to local job log failed] [JobID {0}] [msg {1}]: {2}
CWLRB1590I: Found job status table entry with key: [bjeename {0}] [jobid {1}]: Job {1} is restarting
CWLRB1600E: [Long Running Job Container push message to global job log failed] [JobID {0}] [msg {1}]: {2}
CWLRB1620E: [Long Running Job Container job setup failed] [jobid {0}]: {1}
CWLRB1630I: Found checkpoint repository entry for key: [jobid {0}] [stepname {1}] [bdsname {2}]
CWLRB1640E: [Long Running Job Container job setup begin transaction failed] [jobid {0}]: {1}
CWLRB1650I: Created checkpoint repository table entry using key: [jobid {0}] [stepname {1}] [bdsname {2}]
CWLRB1660E: [Long Running Job Container job setup commit transaction failed] [jobid {0}]: {1}
CWLRB1670I: Creating abstract resources required by the job.
CWLRB1680E: [Long Running Job Container job restart failed] [jobid {0}]: failing step [{1}] not found in job status table
CWLRB1690I: No match found in job status table entry using key: [bjeename {0}] [jobid {1}]: Job {1} is not restarting.
CWLRB1700E: [Long Running Job Container job setup get job status failed] [jobid {0}]: {1}
CWLRB1710I: Job is restarting at step: {0}
CWLRB1720E: [Long Running Job Container job setup rollback transaction failed] [jobid {0}]: {1}
CWLRB1740I: {0} Job [{1}] is in job setup.
CWLRB1760I: {0} Job [{1}] is submitted for execution.
CWLRB1780I: {0} Job [{1}] job is cancelled.
CWLRB1800I: {0} Job [{1}] Step [{2}] skipped.
CWLRB1820E: [Long Running Job Container sequential step scheduling failed] [jobID {0}]: {1}
CWLRB1840E: failing step [{0}] is inconsistent with JobStepStatus table step [{1}] for job [{2}]
CWLRB1850I: Initializing for step dispatch using scheduling mode: {0}
CWLRB1860I: Dispatching Job [{0}] Step [{1}]
CWLRB1870I: Subscribing to job cancel or stop subject: {0}
CWLRB1880E: [Long Running Job Container teardown batch job failed] [JobID {0}]: {1}
CWLRB1890I: Unsubscribing from job cancel or stop subject: {0}
CWLRB1900E: [Long Running Job Container initialize Homes failed]: {0}
CWLRB1910I: Dispatching job {0}: job contains {1} step(s).
CWLRB1920E: [Long Running Job Container initialize job home failed] [JobID {0}]: {1}
CWLRB1940E: [Long Running Job Container create job step status failed] [JobID {0}] [Step {1}]: {2}
CWLRB1950I: Found job step status using key [JobID {0}] [Step {1}]: Job is restarting
CWLRB1960E: [Long Running Job Container update job step status failed] [JobID {0}] [Step {1}] [status {2}]: {3}
CWLRB1970I: Created job step status table entry using key [jobid {0}] [stepname {1}]
CWLRB1980E: [Long Running Job Container update job status failed] [jobid {0}]: {1}
CWLRB1990I: Found job results table entry matching on key: [jobid {0}]
CWLRB2000E: [Long Running Job Container get User Transaction failed] [jobid {0}]: {1}
CWLRB2010I: Created job results entry using key: [jobid {0}]
CWLRB2020E: [Long Running Job Container cancelBatchJob failed] [jobid {0}]: {1}
CWLRB2030I: Initialization for {0} step dispatch is complete.
CWLRB2040E: [Long Running Job Container setEndingStatus failed] [jobid {0}] [status {1}]: {2}
CWLRB2050I: Preparing to throw a runtime exception: {0}
CWLRB2060E: [Long Running Job Container job status update failed] [JobID {0}]: {1}
CWLRB2080E: [Long Running Job Container update global job status failed] [JobID {0}]: {1}
CWLRB2100E: [Long Running Job Container update global job status failed] [JobID {0}] [Status {1}]: {2}
CWLRB2120E: [Long Running Job Container JobStatusUpdate failed] [BJEE {0}] [JobID {1}]: {2}
CWLRB2140E: [Long Running Job Container create abstract resources failed] [JobID {0}]: {1}
CWLRB2160E: [Long Running Job Container teardown abstract resources failed] [JobID {0}]: {1}
CWLRB2180E: [Long Running Job Container create return code abstract resource failed] [JobID {0}] [step {1}]: {2}
CWLRB2200E: [Long Running Job Container create abstract resource initialize Homes failed]: {0}
CWLRB2210I: Job setup manager bean is setting up job: {0}
CWLRB2220E: [Long Running Job Container step setup failed] [Job {0}] [Step {1}]: {2}
CWLRB2230I: Job setup manager bean completed job {0} setup: return code: {1}
CWLRB2240E: [Grid Execution Environment step setup open Batch Data Stream failed] [jobid {0}]: {1}
CWLRB2250I: Job setup manager bean is breaking down job: {0}
CWLRB2260E: [Long Running Job Container step setup position Batch Data Stream failed] [jobid {0}]: {1}
CWLRB2270I: Job setup manager bean completed job {0} breakdown
CWLRB2280E: [Long Running Job Container step execution failed] [Job {0}] [Step {1}]: {2}
CWLRB2300E: [Long Running Job Container step setup close Batch Data Stream failed] [jobid {0}]: {1}
CWLRB2320I: Job [{0}] Step [{1}] was cancelled
CWLRB2340I: Job [{0}] Step [{1}] ended abnormally
CWLRB2360I: Job [{0}] Step [{1}] finished with return code {2}
CWLRB2380E: [Long Running Job Container fire results failed] [Job {0}] [rc {1}]: {2}
CWLRB2400E: [Long Running Container stop checkpoint failed] [Job {0}] [Step {1}]: {2}
CWLRB2420I: {0} Job [{1}] Step [{2}] is in step setup.
CWLRB2440I: {0} Job [{1}] Step [{2}] is dispatched.
CWLRB2460I: {0} Job [{1}] Step [{2}] is in step breakdown.
CWLRB2480E: [Long Running Job Container step breakdown failed] [Job {0}] [Step {1}]: {2}
CWLRB2500E: [Long Running Job Container fire results algorithm failed] [Job {0}] [Step {1}] [rc {2}]: {3}
CWLRB2520E: [Long Running Job Container update job step status failed] [Job {0}] [Step {1}] [status {2}]: {3}
CWLRB2540E: [Long Running Job Container update job step status rc failed] [Job {0}] [Step {1}] [rc {2}]: {3}
CWLRB2560I: {0} Job [{1}] Step [{2}] completed abnormally
CWLRB2580I: {0} Job [{1}] Step [{2}] completed [cancelled].
CWLRB2600I: {0} Job [{1}] Step [{2}] completed normally rc={3}.
CWLRB2620E: [Long Running Job Container step status update failed] [Job {0}] [Step {1}]: {2}
CWLRB2640E: [WebSphere Batch Container suspend processing failed] [Job {0}] [Step {1}]: {2}
CWLRB2660I: suspending job [{0}] in execution environment [{1}] until [{2}]
CWLRB2680I: {0} Job [{1}] Step [{2}] execution suspended until manually resumed.
CWLRB2700I: {0} Job [{1}] Step [{2}] execution suspended until [{3}].
CWLRB2720I: resuming job [{0}] in execution environment [{1}]
CWLRB2740I: {0} Job [{1}] Step [{2}] execution resumed by expired timer.
CWLRB2760I: {0} Job [{1}] Step [{2}] execution resumed by request.
CWLRB2780I: {0} Job [{1}] Step [{2}] suspend processing ended by cancel request.
CWLRB2800I: {0} Job [{1}] Step [{2}] execution resumed by InterruptedException.
CWLRB2820E: [Long Running Job Container open xJCL failed]: {0}
CWLRB2840E: [Long Running Job Container put xJCL failed]: {0}
CWLRB2860E: [Long Running Job Container get xJCL failed]: {0}
CWLRB2880E: [Long Running Job Container get connection failed]: {0}
CWLRB2900E: [Long Running Job Container GlobalJobID ejbCreate failed]: {0}
CWLRB2920W: [Long Running Job Scheduler] Scheduler Singleton <init>: XD EPS class not found
CWLRB2930W: [Long Running Job Scheduler] Scheduler Singleton <init>: XD EPS no class def found
CWLRB2940W: [Long Running Job Scheduler] Scheduler Singleton <init>: XD EPS invoke method not found
CWLRB2960W: [Long Running Job Scheduler] Scheduler Singleton <init>: XD EPS invoke method not accessible
CWLRB2980I: [Long Running Job Scheduler] Scheduler Singleton <init>: using SimpleEPSImpl
CWLRB3000E: Long Running Job Scheduler has not been initialized
CWLRB3020E: [Long Running Job Scheduler {0}] failed: {1}
CWLRB3040I: [Long Running Job Scheduler {0}] Current Status:

CWLRB3060I: [{0}] [{1}] [{2}] [{3}] [{4}] [{5}] [{6}] [{7}] [{8}]
CWLRB3070I: JOBSTATUS table contains no jobs.
CWLRB3072I: Total number of jobs being recovered is {0}.
CWLRB3073I: Job {0} has been moved to the {1} state.
CWLRB3074W: The deletion of file {0} failed: {1}
CWLRB3080E: [Long Running Job Scheduler {0}] Dispatch failed [Job {1}] [Endpoint {2}]: {3}
CWLRB3090I: Job {0} is dispatched to endpoint {1}: result: {2}
CWLRB3100E: [Long Running Job Scheduler {0} failed] [Job {1}]: {2}
CWLRB3110E: Job {0} could not be dispatched. Application is not deployed in the Grid Execution Environment.
CWLRB3111E: Jod ID {0} could not be dispatched. Grid Utility jobs are not supported on z/OS.
CWLRB3112E: Job ID {0} could not be dispatched. Required Capability was not found in the Grid Execution Environment.
CWLRB3113E: Job {0} could not be dispatched due to a database exception.
CWLRB3114E: Job ID {0} could not be dispatched. Ambiguous editions are found in the Grid Execution Environment.
CWLRB3115E: Job ID {0} could not be dispatched. The specified edition is not installed or active in the Grid Execution Environment.
CWLRB3120E: [Long Running Job Scheduler {0}] {1} failed: {2}
CWLRB3140E: [Long Running Job Scheduler MBean registration failure]: {0}
CWLRB3220I: Long Running Job Scheduler is initialized
CWLRB3240E: Unable to get temp Job {0}
CWLRB3250E: {0} job document contains {1} error(s): {2}
CWLRB3260E: Unable to load job document: {0}
CWLRB3265E: Invalid Step {0}: both {1} and {2} elements are specified
CWLRB3267E: Step {0} invalid element: {1}: {2} was expected
CWLRB3268E: Step attribute(s) {0} may only be specified with job type {1}
CWLRB3270E: Invalid job element {0}: {1} was expected
CWLRB3275E: Conflicting step application types: [{0}: {1}] [{2}: {3}] [{4}: {5}]
CWLRB3280E: [Long Running Job Container xJCLMgr extractJob failed]: {0}
CWLRB3290E: Step attribute(s) {0} may only be specified with application type {1}
CWLRB3300I: Unrecognized job type
CWLRB3310E: Invalid job element: one of {0} was expected
CWLRB3320E: Long Running Job Container xJCLMgr detected {0} error(s) in job {1}: {2}
CWLRB3330E: Job contains no steps
CWLRB3340I: Unrecognized step scheduling mode: {0}
CWLRB3350E: Invalid Job Step {0}: {1} are mutually exclusive
CWLRB3360I: Duplicate resource definition: {0}
CWLRB3370E: Invalid Job Step {0}: one of {1} was expected
CWLRB3380I: Invalid resource type [{0} {1}]
CWLRB3390E: Invalid Job Step {0}: {1} may not both be specified across job steps
CWLRB3400I: Duplicate checkpoint algorithm name: {0}
CWLRB3410E: Invalid Step {0}: either step attribute {1} or step element {2} must be specified
CWLRB3420I: Duplicate resource algorithm name: {0}
CWLRB3440I: Illegal parameter value: [{0} {1}]
CWLRB3460I: Duplicate step name: {0}
CWLRB3480I: Illegal condition on first job step: {0}
CWLRB3500I: Step referenced by return code expression not found: {0}
CWLRB3520I: Unrecognized resource type: {0}
CWLRB3530E: Unable to find results algorithm {0} referenced by jobstep {1}
CWLRB3540E: Unable to find checkpoint algorithm {0} referenced by job {1}
CWLRB3542E: Required job element missing: {0}
CWLRB3544E: Illegal job element value: [{0} {1}]
CWLRB3545E: Job element {0} contains the value {1} but one of {2} is required
CWLRB3546E: Illegal step element value for step {0}: [{1} {2}]
CWLRB3560E: Long Running Job Dispatcher failed to get job xJCL definitions for [job {0}] [application {1}]: {2}
CWLRB3580E: Long Running Job Dispatcher failed to find a dispatcher for the {1} type of work submitted in job {0}
CWLRB3600E: Long Running Job Dispatcher failed to find the JNDI name {0} for the job submitted in job {0}
CWLRB3620E: Long Running Job Dispatcher failed to lookup the work manager {0} for job {1}
CWLRB3640E: Long Running Job Dispatcher received a WorkManager exception {1} when dispatching job {0}
CWLRB3660E: Grid Job Execution Environment {0} failed while instantiating the job management beans [job {1}]: {2}
CWLRB3680E: Grid Job Execution Environment {0} failed while instantiating the SetupManager Session Bean [job {1}]: {2}
CWLRB3700E: Grid Job Execution Environment {0} failed while instantiating the JobLogManager Session Bean [job {1}]: {2}
CWLRB3720E: [{0}] Grid Job Execution Environment {1} failed while while collecting statistics for job [{2}]: {3}
CWLRB3740E: Grid Job Execution Environment {0} failed while executing createNewJob() on the SetupManager Session Bean [job {1}]: {2}
CWLRB3760E: Grid Job Execution Environment {0} failed while while attempting to obtain local job status [job {1}]: {2}
CWLRB3780E: Grid Job Execution Environment {0} failed while executing breakDownJob() on the SetupManager Session Bean [job {1}]: {2}
CWLRB3800I: Job [{0}] ended normally.
CWLRB3810I: job [{0}] ended normally [cancelled].
CWLRB3820I: Job [{0}] ended abnormally [cancelled].
CWLRB3840W: Job [{0}] execution failed.
CWLRB3860W: Job [{0}] ended abnormally [and is restartable].
CWLRB3870W: Job [{0}] ended abnormally [and is not restartable].
CWLRB3880I: Job [{0}] ending status: {1}
CWLRB3900W: Cannot resume Job [{0}]: job state [{1}] is required but job state [{2}] was found
CWLRB3920W: Cannot resume job [{0}]: Job not found
CWLRB3940E: Long Running Job Dispatcher [{0}] failed while resuming job [{1}]: {2}
CWLRB3960W: Cannot suspend job [{0}]: Job ended on {1}
CWLRB3980W: Cannot suspend job [{0}]: Job cancelled on {1}
CWLRB4000W: Cannot suspend Job [{0}]: job ended abnormally on {2} [and is restartable]
CWLRB4020W: Cannot suspend job [{0}]: Job abnormally ended on {1} [and is not restartable]
CWLRB4040W: Cannot suspend job [{0}]: A prior cancel command for the job is being processed by {1}
CWLRB4060W: Cannot suspend job [{0}]: A prior suspend command for the job is being processed by {1}
CWLRB4080W: Cannot suspend job [{0}]: Job suspended on {1}
CWLRB4100W: Cannot suspend job [{0}]: Job state [{1}] is invalid
CWLRB4120W: Cannot suspend job [{0}]: Job not found
CWLRB4140E: Long Running Job Dispatcher [{0}] failed while suspending job [{1}]: {2}
CWLRB4160W: Cannot cancel job [{0}]: Job ended on {1}
CWLRB4180W: Cannot cancel job [{0}]: Job cancelled on {1}
CWLRB4200W: Cannot cancel Job [{0}]: job ended abnormally on {2} [and is restartable]
CWLRB4220W: Cannot cancel job [{0}]: Job abnormally ended on {1} [and is not restartable]
CWLRB4240W: Cannot cancel job [{0}]: A prior cancel command for the job is being processed by {1}
CWLRB4260W: Cannot cancel job [{0}]: Job state [{1}] is invalid
CWLRB4280I: cancelling job [{0}] in execution environment [{1}] Current job status: {2}
CWLRB4290I: Cancelling job [{0}]
CWLRB4300W: Cannot cancel job [{0}]: Job not found
CWLRB4304W: Cannot purge job [{0}]: Job state [{1}] is invalid
CWLRB4308W: Cannot purge job [{0}]: Job state [{1}] is invalid
CWLRB4312W: Cannot purge job [{0}]: Job is not found
CWLRB4316W: Cannot purge job [{0}]: Exception {1} encountered while looking up job status
CWLRB4318W: Grid Job Dispatcher {0} {1} failed: {2}
CWLRB4320E: Long Running Job Dispatcher [{0}] failed while cancelling job [{1}]: {2}
CWLRB4330E: Long Running Job Dispatcher [{0}] failed while purging job [{1}]: {2}
CWLRB4340E: Grid Job Execution Environment {0} failed while while updating the job log [job {1}]: {2}
CWLRB4360E: Long Running Job Dispatcher failed to find the JNDI name {0} for [job {1}] [application {2}]
CWLRB4380E: Long Running Job Dispatcher encountered an exception running [job {0}] [application {1}]: {2}
CWLRB4400E: [{0}] Grid Job Execution Environment {1} failed while executing createNewJob() on the SetupManager Session Bean [job {2}]: {3}
CWLRB4420E: Grid Job Execution Environment {0} failed while while attempting to obtain local job status [job {1}]: {2}
CWLRB4440E: [{0}] Grid Job Execution Environment {1} failed while executing breakDownJob() on the SetupManager Session Bean [job {2}]: {3}
CWLRB4460E: Grid Job Execution Environment {0} failed while while updating the job log [job {1}]: {2}
CWLRB4480E: [Long Running Job Endpoint Component {0}] failed: {1}
CWLRB4500I: Long Running Job Endpoint {0} stopped
CWLRB4510E: No.Host.Alias.For.Endpoint.Virtual.Host
CWLRB4520E: Long Running Job Endpoint Bulletin Board Manager {0} failed: {1}
CWLRB4540E: Long Running Job Endpoint Publisher failed: No Bulletin Board for subject {0}
CWLRB4560E: Long Running Job Endpoint List Listener failed: {0}
CWLRB4580E: Long Running Job Endpoint MBean {0} failed: {1}
CWLRB4600E: Long Running Job Endpoint MBean {0} start Job {1} failed: {2}
CWLRB4620E: Long Running Job Endpoint MBean {0} cancel Job {1} failed: {2}
CWLRB4640E: Long Running Job Endpoint MBean {0} pause Job {1} failed: {2}
CWLRB4660E: Long Running Job Endpoint MBean {0} resume Job {1} failed: {2}
CWLRB4680E: Long Running Job Endpoint MBean {0} deregister failed: {1}
CWLRB4700E: [Long Running Job Scheduler {0} {1} failed]: {2}
CWLRB4720E: [Long Running Job Scheduler {0} failed]: {1}
CWLRB4740E: Long Running Job Scheduler Component failed: No Bulletin Board for subject {0}
CWLRB4760E: [Long Running Job Scheduler Job Status Listener failed]: {0}
CWLRB4780I: Job [{0}] is cancelled
CWLRB4800W: Illegal property [{0} {1}] in {2} CheckpointAlgorithm [{3}]: default value of {4} is taken
CWLRB4820W: Missing property [{0}] in {1} CheckpointAlgorithm [{2}]: default value of {3} is taken
CWLRB4840E: {0} requires {1}
CWLRB4860E: extraneous arg(s) detected
CWLRB4880E: {0} failed:
{1}
CWLRB4900E: {0} and {1} are mutually exclusive
CWLRB4920W: The batch Job [{0}] cannot be restarted: current state [{1}] is invalid.
CWLRB4930W: The Long Running Execution Environment (LREE) that is currently running or previously ran job {0} is experiencing a Health Management condition. Try operation {1} at a later time.
CWLRB4940I: {0} : {1}
CWLRB4960I: {0} : {1} : Job [{2}] is submitted.
CWLRB4980I: {0} : {1} : OK
CWLRB5000I: {0} : {1} : response to {2}
CWLRB5020I: {0} : Job [{1}] has been submitted for execution.
CWLRB5040I: {0} : A cancel request is pending for Job [{1}].
CWLRB5060I: {0} : A suspend request is pending for Job [{1}].
CWLRB5080I: {0} : A resume request is pending for Job [{1}].
CWLRB5100I: {0} : Job [{1}] is executing.
CWLRB5120I: {0} : Job [{1}] execution is suspended.
CWLRB5140I: {0} : Job [{1}] has been cancelled.
CWLRB5160I: {0} : Job [{1}] execution has ended.
CWLRB5180I: {0} : Job [{1}] was cancelled or has failed execution but is restartable.
CWLRB5200I: {0} : Job [{1}] has failed execution and is not restartable.
CWLRB5210I: {0} : A submit request is pending for Job [{1}]
CWLRB5215I: {0} : A stop request is pending for Job [{1}].
CWLRB5220E: Submitter {0} is not authorized to perform the {2} job action on jobId = {1}.
CWLRB5240E: You are not authorized to perform the {1} job action on the listed job. The {1} job action can only be performed by the Long Running Job administrator or the submitter of job {0} . Please contact the Long Running Job administrator or the submitter of job {0} for assistance.
CWLRB5260E: Long Running Scheduler (LRS) failed to mark which jobs to restart on Long Running Execution Environment (LREE) {0}_{1} in the event of a Health Management condition.
CWLRB5270W: Long Running Scheduler (LRS) could not restart a batch job {2} that was previously running on LREE {0}_{1} because job {2} is not in restartable state.
CWLRB5280E: Long Running Scheduler (LRS) failed to restart job {2} on dynamic cluster instance {0}_{1}
CWLRB5290W: Long Running Scheduler (LRS) could not process operation {3} for job {2} because Long Running Execution Environment {0}_{1} is busy due to a Health Management condition.
CWLRB5300W: Illegal args passed to Long Running Batch Job Dispatcher {0}: [jobid {1}] [seq {2}]
CWLRB5310E: Long Running Batch Job Dispatcher {0} failed while attempting to send job log [job {1}] [seq {2}]: {3}
CWLRB5320W: [{0}] Job [{1}] has failed execution but is restartable: Grid Job Execution Environment {2} failed
CWLRB5330I: {0} Job [{1}] is restarting at Step [{2}]
CWLRB5340E: [Long Running Job Scheduler mbean {0}] failed: {1}
CWLRB5360E: [Long Running Job Endpoint CR Mbean {0}] failed: {1}
CWLRB5380E: [Grid Execution Environment {0} EndpointSRMbean] failed: {1}
CWLRB5400E: [Long Running Job Endpoint SR Mbean {0}] [Job {1}] failed: {2}
CWLRB5410E: [Long Running Job Scheduler Component {0} failed]: {1}
CWLRB5420E: [Long Running Job Scheduler CR Mbean {0}] failed: {1}
CWLRB5430I: [{0}] [{1}] [{2}] [{3}] [{4}]
CWLRB5440I: {0} : {1} : Recurring Request [{2}] is submitted.
CWLRB5450E: Submitter {0} is not authorized to perform the {2} recurring request action on request {1}.
CWLRB5460E: You are not authorized to perform the {1} recurring request action on request {0}. The {1} recurring request action can only be performed by the Long Running Job administrator or the submitter of request {0} . Please contact the Long Running Job administrator or the submitter of request {0} for assistance.
CWLRB5461E: User {0} is not authorized to perform Forced Cancel command.
CWLRB5470E: You are not authorized to perform the {0} recurring request action. The {0} recurring request action can only be performed by the Long Running Job administrator. Please contact the Long Running Job administrator for assistance.
CWLRB5480E: [WebSphere Batch Container Batch Logger unable to obtain JoblogManagerHome] [jobid {0}] [logmsg {1}]: {2}
CWLRB5490E: [WebSphere Batch Container Batch Logger unable to obtain JobStatusUpdateHome] [jobid {0}] [logmsg {1}]: {2}
CWLRB5500E: [WebSphere Batch Container Batch Logger unable to create LocalJobStatusUpdate] [jobid {0}] [logmsg {1}]: {2}
CWLRB5510I: [{0}] Job [{1}] Step [{2}] {3}
CWLRB5520E: [WebSphere Batch Container Batch Logger unable to add message to job log] [jobid {0}] [logmsg {1}]: {2}
CWLRB5530E: [WebSphere Batch Container job cancel listener failed] [Job {0}]: {1}
CWLRB5540E: duplicated arg(s) detected
CWLRB5542W: Cannot stop job [{0}]: Job ended on {1}
CWLRB5544W: Cannot stop job [{0}]: Job stopped on {1}
CWLRB5546W: Cannot stop Job [{0}]: job ended abnormally on {2} [and is restartable]
CWLRB5548W: Cannot stop job [{0}]: Job abnormally ended on {1} [and is not restartable]
CWLRB5550W: Cannot stop job [{0}]: A prior stop command for the job is being processed by {1}
CWLRB5552W: Cannot stop job [{0}]: Job state [{1}] is invalid
CWLRB5554I: stopping job [{0}] in execution environment [{1}] Current job status: {2}
CWLRB5556W: Cannot stop job [{0}]: Job not found
CWLRB5558E: Long Running Job Dispatcher [{0}] failed while stopping job [{1}]: {2}
CWLRB5560I: Job [{0}] Step [{1}] was stopped
CWLRB5562I: Job [{0}] ended abnormally [stopped].
CWLRB5564I: {0} Job [{1}] Step [{2}] completed [stopped].
CWLRB5566I: {0} Job [{1}] Step [{2}] suspend processing ended by stop request.
CWLRB5568I: {0} contains no symbolic variables
CWLRB5570I: {0} contains the following symbolic variables which have no default values:{1}
CWLRB5572I: {0} contains the following symbolic variables with default values: {1}
CWLRB5574E: Grid Job Execution Environment {0} {1} failed: Null xJCL passed to {2}
CWLRB5576E: Grid Job Execution Environment {0} {1} failed: Null jobID passed to {2}
CWLRB5578E: Grid Job Execution Environment {0} {1} failed: {2}
CWLRB5579E: Grid Job Execution Environment {0} {1} failed: unable to write file {2}: checkError returned true
CWLRB5580E: Grid Execution Environment {0} {1} failed: File {2} is not writable
CWLRB5582E: Grid Execution Environment {0} {1} failed: File {2} is not readable
CWLRB5584I: {0} xJCL for job {1}
CWLRB5586I: {0} {1}
CWLRB5588I: {0} Setting up j2ee job {1} for execution in Grid Execution Environment {2}: {3} {4} {5} {6} {7} {8} {9}
CWLRB5589I: {0} Setting up Grid Utility job {1} for execution in Grid Execution Environment {2}: {3} {4} {5} {6}
CWLRB5590I: {0} Grid Execution Environment {1} detected: {2}
CWLRB5592I: Execution complete: {0}
CWLRB5594I: Step {0} {1} is complete: {2}
CWLRB5596I: Grid Execution Environment {0} step processing complete: {1}
CWLRB5598I: Removing job abstract resources
CWLRB5600I: Removing job step status table entries
CWLRB5602I: Closing {0} batch data stream: {1}
CWLRB5604I: Freeing {0} batch data stream: {1}
CWLRB5606I: Destroying job step: {0}
CWLRB5607W: Job step {0} destroy completed with rc: {1} which is within the system application return code range
CWLRB5608I: Job step {0} destroy completed with rc: {1}
CWLRB5610I: Firing {0} results algorithm {1}: [RC {2}] [jobRC {3}]
CWLRB5612I: Positioning {0} batch data stream {1} using restart token: {2}
CWLRB5614I: Positioning {0} batch data stream {1} using initial checkpoint
CWLRB5616I: Setting step {0} batch data stream {1} properties: {2}
CWLRB5618I: Initializing step {0} batch data stream {1}
CWLRB5620I: Opening step {0} batch data stream {1}
CWLRB5622I: Loading job step bean for step {0} using jndi name: {1}
CWLRB5623I: Loading job step bean for step {0} using class name: {1}
CWLRB5624I: {0} step {1} {2} checkpoint. User transaction status: {3}
CWLRB5626I: {0} Received {1} post on subject {2}
CWLRB5627I: User has requested a Forced Cancel on the listed job. Servant Region will be forcibily terminated.
CWLRB5628I: Step {0}: {1} checkpoint taken [iteration {2}] {3}
CWLRB5629I: Forced cancel can not be processed in the Endpoint in which job {0} is running. However, job {0} will be canceled but WebSphere Application Server will not be terminated.
CWLRB5630I: Step {0} completes {1}: {2}
CWLRB5632E: Grid Job Execution Environment {0} {1} failed: [root {2}] file {3} exists and is not a directory
CWLRB5634E: Grid Job Execution Environment {0} {1} failed: Unable to make directories {2}
CWLRB5636E: Grid Job Execution Environment {0} {1} failed: root {2}: {3}
CWLRB5637E: Grid Job Execution Environment {0} {1} failed: root {2}: mkDirs returned false
CWLRB5638I: Grid Job Execution Environment {0} {1} failed: [root {2}] directory {3} is not writable
CWLRB5640I: Grid Job Execution Environment {0} {1} failed: [root {2}] directory {3} is not readable
CWLRB5642E: Grid Job Execution Environment {0} {1} failed: unable to parse job file root {2}
CWLRB5644E: {0} Grid Execution Environment {1} is unable to capture {2}: {3}
CWLRB5646E: {0} Grid Execution Environment {1} is unable to restore {2}: {3}
CWLRB5648I: {0} No substitution-props properties found in job xJCL
CWLRB5650I: {0} List of substitution-props properties found in job xJCL
CWLRB5652I: {0} No properties (name and value pairs) passed to job scheduler API: {1}
CWLRB5654I: {0} List of properties passed to job scheduler api: {1}
CWLRB5656I: {0} No properties to be applied to job xJCL
CWLRB5658I: {0} List of properties to be applied to job xJCL
CWLRB5660I: {0} Job xJCL before symbolic variable substitution
CWLRB5662I: Applying [property {0}] with [value {1}] to job xJCL
CWLRB5663I: Symbolic variable substitution for {0} is deferred to the execution endpoint
CWLRB5664I: {0} Applying [property {1}] with [value {2}] obtained from {3} to job xJCL
CWLRB5666I: Job xJCL at time of variable substitution failure
CWLRB5668I: Job xJCL variable substitution failure: {0}
CWLRB5670I: {0} {1}
CWLRB5671I: {0} Processing for job {1} started.
CWLRB5672I: {0} Processing xJCL symbolic variables: [API {1}]
CWLRB5674I: {0} Unable to load job document: {1}
CWLRB5676I: No symbolic variable found matching {0}
CWLRB5678I: Job xJCL after all symbolic variable substitutions performed
CWLRB5680E: Job scheduler {0} {1} failed: unable to rename {2} to {3}
CWLRB5682I: Job scheduler {0} {1} failed: unable to delete directory {2}
CWLRB5684I: Job {0} is queued for execution
CWLRB5685I: Job {0} is being requeued for execution because the job scheduler startup processing found the job in submitted state. The original job submission occurred at {1}.
CWLRB5686I: Grid Job Execution Environment {0} {1} failed: unable to remove file {2}
CWLRB5688I: Grid Job Execution Environment {0} {1} remove file {2} failed: {2} is a directory
CWLRB5690I: Grid Job Execution Environment {0} {1} failed: file {2} not found
CWLRB5692I: Grid Job Execution Environment {0} {1} failed: unable to create zip file {2} from source file {3}: {4}
CWLRB5694I: Grid Job Execution Environment {0} {1} failed: unable to close file {2}: {3}
CWLRB5696I: Grid Job Execution Environment {0} {1} failed while calculating the size of file {2}: {3}
CWLRB5698I: Grid Job Execution Environment {0} {1} failed while calculating the age of file {2}: {3}
CWLRB5700I: Grid Job Execution Environment {0} {1} failed writing to file {2}: {3}
CWLRB5702I: Grid Job Execution Environment {0} {1} failed reading from file {2}: {3}
CWLRB5703I: Grid Job Execution Environment {0} {1} failed reading from directory {2}: {3}
CWLRB5704I: {0} {1}: {2}
CWLRB5706I: {0} invalid xJCL:
CWLRB5708E: {0} Grid Execution Environment {1} failed opening {2}: {3}
CWLRB5710E: {0} Grid Execution Environment {1} failed closing {2}: {3}
CWLRB5712E: {0} Grid Execution Environment {1} failed reading {2}: {3}
CWLRB5714I: Applying [property {0}] with [value {1}]
CWLRB5716I: Applying [property {0}] with [value {1}] obtained from {2}
CWLRB5718I: xJCL data [line {0}]: before variable substitution: {1}
CWLRB5720I: xJCL data [line {0}]: after variable substitution: {1}
CWLRB5722I: xJCL data [line {0}]: applying {1}
CWLRB5724I: xJCL data [line {0}]: deferring symbolic variable substitution for {1} to the execution endpoint
CWLRB5726E: {0} Grid Execution Environment {1} is unable to capture {2}: {3} exists but is a regular file
CWLRB5728E: {0} Grid Execution Environment {1} is unable to capture {2}: unable to create directory {3}
CWLRB5730E: {0} Grid Execution Environment {1} is unable to capture {2}: unable to create regular file {3}: {4}
CWLRB5732E: Grid Job Execution Environment {0} {1} failed: unable to purge job log file(s) for job {2}: job log file(s) in directory {3} are in use
CWLRB5734E: Grid Job Execution Environment {0} {1} failed: unable to purge job log file(s) for job {2}: job state {3} is invalid
CWLRB5736E: Grid Job Execution Environment {0} {1} failed: unable to purge job log file(s) for job {2}: directory {3} not found
CWLRB5738W: Grid Job Execution Environment {0} {1} is unable to transfer remote file(s) for job {2}: unable to obtain XD agent for node {3}
CWLRB5740W: Grid Job Execution Environment {0} {1} cannot purge remote job log file(s): job status table entry not found for job {2}
CWLRB5742E: Grid Job Execution Environment {0} {1} failed: unable to obtain XD agent for node {2}
CWLRB5743E: Grid Job Execution Environment {0} {1} failed: unable to obtain XD agent for node {2}: {3}
CWLRB5744W: Grid Job Execution Environment {0} {1} is unable to purge job log file {2} for job {3}
CWLRB5746W: Grid Job Execution Environment {0} {1} is unable to delete job log directory {2} for job {3}
CWLRB5748E: Grid Job Execution Environment {0} {1} failed: unable to delete {2} on node {3}: {4}
CWLRB5750E: Grid Job Execution Environment {0} {1} failed: unable to list contents of directory {2} on node {3}: {4}
CWLRB5751E: Grid Job Execution Environment {0} {1} failed reading from directory {2} on node {3}: {4}
CWLRB5752I: Cancel request received for job {0}
CWLRB5754I: Beginning job {0} execution
CWLRB5756I: Beginning step {0} execution
CWLRB5758I: Step {0} execution execution ended: cancelled
CWLRB5760I: Step {0} execution execution ended: {1}
CWLRB5762I: Job {0} ended: cancelled
CWLRB5764I: Job {0} ended
CWLRB5766E: Unable to read job {0} {1} file {2}: {3}
CWLRB5768E: Unable to close job {0} {1} file {2}: {3}
CWLRB5770E: Unable to delete job {0} {1} file {2}: {3}
CWLRB5772I: {0} Grid Execution Environment job log output is quiesced: output limit is exceeded
CWLRB5774I: {0} Job log was purged by request
CWLRB5776E: Grid Job Execution Environment {0} {1} failed: unable to update job class list file {2}: {3}
CWLRB5777I: Job scheduler {0} is not accessible
CWLRB5778I: Job scheduler {0} is being brought down due to an health condition.
CWLRB5779I: Job scheduler {0} stopped.
CWLRB5780I: Job {0} taken over by scheduler {1}.
CWLRB5781I: Job {0} handed over to scheduler {1}.
CWLRB5782I: Job {0} take over failed.
CWLRB5783I: Job {0} hand over failed.
CWLRB5784I: Setting step SLSB property: {0}
CWLRB5785I: WebSphere Batch Container job {0} log file(s) are purged: maximum job log age limit exceeded.
CWLRB5786I: WebSphere Batch Container job {0} log file(s) are purged: maximum file system log size limit exceeded.
CWLRB5787I: WebSphere Batch Container job {0} log file(s) are purged: purged by user request.
CWLRB5788E: Grid Job Execution Environment {0} {1} is unable to purge job log file {2} for job {3}: {4}
CWLRB5789E: Invalid job validation schema: {0}: [schema {1}] [line {2}] [column {3}]: {4}
CWLRB5790E: [{5}] Invalid job validation schema: {0}: [schema {1}] [line {2}] [column {3}]: {4}
CWLRB5791E: [{5}] Job document validation {0}: [schema {1}] [line {2}] [column {3}]: {4}
CWLRB5792I: Schema validation may be disabled by setting the Grid Scheduler custom property schemaValidationEnabled=false. Consider using the migration utility jobDocumentMigration in {0} to migrate the job document.
CWLRB5793W: {0} System.Property {1} not found
CWLRB5794I: Job {0} has no output message persisted.
CWLRB5795E: {0} Grid Execution Environment {1} is unable to setup job {2}: {3}
CWLRB5796E: Unable to load jobclass [job [{0}] [class {1}]: {2}
CWLRB5797E: Unable to set CIControllerWork properties: {0}
CWLRB5798E: Unable to get CIControllerWork properties: {0}
CWLRB5799W: Error reporting statistics for start of job {0}: {1}
CWLRB5800E: Error running compute intensive job {0}: {1}
CWLRB5801W: Error reporting statistics for end of job {0}: {1}
CWLRB5802E: [WebSphere Batch Container Batch Data Stream Manager initialize state failed] [logicalName {0}]: {1}
CWLRB5804I: Job {0} will run at {1}.
CWLRB5805E: xJCL data [line {0}]: invalid xJCL: property [{1}] with value [{2}] is circular
CWLRB5806E: Invalid xJCL: property [{0}] with value [{1}] is circular
CWLRB5807E: Job {0} execution failed due to {1}
CWLRB5808E: Error occured stopping job {0}: {1}
CWLRB5809E: WebSphere Batch Container could not create step status for job {0}: {1}
CWLRB5810E: WebSphere Batch Container was unable to obtain job status {0}: {1}
CWLRB5812E: WebSphere Batch Container was unable to lookup the BatchControllerBean with JNDI Name {0} : {1}
CWLRB5813E: WebSphere Batch Container was unable to lookup the return code for job {0} and step {1} : {2}
CWLRB5814E: WebSphere Batch Container was unable to initialize the Transaction Manager for job {0} : {1}
CWLRB5815E: Job {0} cannot be dispatched when it is in {1} state
CWLRB5816I: Job {0} is cancelled or stopped..aborting execution.
CWLRB5817E: WebSphere Batch Container was unable to setProperties for job {0} during step Setup : {1}
CWLRB5820E: Exception initializing system logger : {0}
CWLRB5821E: IO Exception intializing system logger : {0}
CWLRB5822E: Services Manager not initialized
CWLRB5823E: Invalid JNDI name {0}
CWLRB5824E: Exception closing resultset, connection or statement : {0}
CWLRB5825E: Error getting Checkpoint data using key {0} : {1}
CWLRB5826E: Error getting step status using key {0} : {1}
CWLRB5827E: Error getting job status using key {0} : {1}
CWLRB5828E: Error updating table with query {0} : {1}
CWLRB5829E: Job {0} could not load CIWork class {1}
CWLRB5830E: Error loading Datasource using JNDI {0} : {1}
CWLRB5831E: Invalid step name {0} or Batch data stream name {1}
CWLRB5832I: Original XJCL
CWLRB5833I: Substituted XJCL
CWLRB5834I: The JobOperationAuthorizer SPI failed the [{0}] job operation that user [{1}] attempted for the [{2}] job.
CWLRB5835I: The JobOperationAuthorizer SPI failed the [{0}] job operation that user [{1}] attempted.
CWLRB5836E: The repository save operation failed because the audit string is not valid. The audit string is [{0}].
CWLRB5837I: The WebSphere Application Server Batch Feature is running under [{0}] security policy.
CWLRB5838E: The [{0}] job listener class could not be loaded. The job will end in the restartable state.
CWLRB5839I: The [{0}] job listener class is invoked for [{1}] processing.
CWLRB5840I: The [{0}] job listener class returned from [{1}] processing.
CWLRB5841E: The persistent context could not be saved for the {0} job due to the {1} exception.
CWLRB5842I: The {0} batch data stream skipped a record in the {1} step of the {2} job due to the {3} error.
CWLRB5843I: The {0} step for the {1} job is being tried again because of the {2} error.
CWLRB5844I: Job Step Batch Data Stream [{0}]: Metric = {1} Value = {2}
CWLRB5845I: Total CPU for the {0} job step: {1}
CWLRB5846I: Records processed per second for the {0} job step: {1}
CWLRB5847E: SMF 120 Subtype 9 job usage recording for batch jobs is not supported by the current level of WebSphere Application Server.
CWLRB5848E: SMF 120 Subtype 9 recording is currently DISABLED by WebSphere Application Server. No SMF 120 Subtype 9 job usage records will be written for batch job [{0}].
CWLRB5849E: The persistent context associated with the {0} key does not exist.
CWLRB5850I: Job {0} is delayed due to insufficient memory requirements. Required memory is {1}; available memory is {2}
CWLRB5851I: There are currently {0} jobs delayed due to insufficient memory. There are currently {1} active jobs in this endpoint consuming {2} memory
CWLRB5852I: Record skipped by batch data stream {0} in job {1} step {2} due to error {3}
CWLRB5853I: Retry started for job {0} step {1} due to error {2}
CWLRB5854I: Job Step [{0}]: Metric = {1} Value = {2}
CWLRB5855I: JobSchedulerMDB was initialized in {0} milliseconds.
CWLRB5856I: The {0} property has a value of {1}.
CWLRB5857I: JobWatcher detected that the {0} job ended with a status of {1} and a job scheduler return code of {2}.
CWLRB5858I: JobWatcher detected that the {0} job ended with a status of {1} and a wsgrid return code of {2}.
CWLRB5859I: Sent job end event for jobid[{0}],[correlator={1}].
CWLRB5860I: JobSchedulerMDB did not send the message because the [{0}] proxy ended.
CWLRB5861I: The proxy with correlator[{0}] ended. The {1} job is being cancelled.
CWLRB5862I: The proxy with correlator[{0}] ended. Job submission is being cancelled.
CWLRB5863I: Queuing early arrival notification for job {0} and notification type = {1}.
CWLRB5864I: Processing early arrival notification for job {0} and notification type = {1}.
CWLRB5865I: The submitter password is not encoded. The password will be used as specified.
CWLRB5866I: The password encoding algorithm is not supported. The password will be used as specified.
CWLRB5867I: The Portable Grid Container is being configured on {0}.
CWLRB5868I: The Portable Grid Container has been configured on {0}.
CWLRB5869I: Failed to configure the Portable Grid Container on {0}.
CWLRB5870I: Failed to uninstall the Portable Grid Container from {0}.
CWLRB5871I: The GridConfigurator initialized successfully.
CWLRB5872I: The GridConfigurator failed initialization.
CWLRB5873I: The GridConfiguratorMBean was activated successfully.
CWLRB5874I: The GridDBConfigurator initialized successfully.
CWLRB5875I: Failed to create custom properties because no members were found in cluster {0}.
CWLRB5876I: Failed to create custom properties because cluster {0} was not found.
CWLRB5877I: Unable to match data source DB2 version to supported backend DB2 version.
CWLRB5878I: Using default DB2 version: {0}
CWLRB5879I: Data source lookup failed for JNDI name {0}.
CWLRB5880I: Failed to configure database {0} on node {1}. Server name cannot be found.
CWLRB5881I: Failed to configure database {0} on node {1}. Cannot find an active GridDBConfiguratorMBean.
CWLRB5882I: Failed to configure database {0} on node {1}: {2}
CWLRB5883I: {0}.{1} caught a StaleConnectionException and is unable to obtain a good connection after {2} tries: {3}
CWLRB5884I: Failed to activate JobSchedulerMBean Type=BatchGridScheduler : {0}
CWLRB5885I: Jobs for the {0} scheduler cannot be taken over by this scheduler. Exception: {1}
CWLRB5886I: {0} duplicate entry is ignored: jobid={1}, startTime={2}
CWLRB5887I: {0} duplicate entry is ignored: jobid={1}, message sequence={2}
CWLRB5888I: Unable to invoke the control region. Another attempt will be made in {0} seconds.
CWLRB5889I: Unable to invoke a servant region to update the status of job [{0}]. Another attempt will be made in {1} seconds.
CWLRB5890I: Job {0} is already in the final state. {1} Not updating schedulerOwns flag.
CWLRB5891I: Job submission encountered an error when transmitting SOAP envelope to the Endpoint.
CWLRB5892I: markFailedServerJobs does not change state of job: {0} because the current state is no longer a non-final state.
CWLRB5893I: DelayedSubmitJobMgrThread shutting down.
CWLRB5894I: getCurrentOutStandingJobs- entry already created for jobclass={0}.
CWLRB5895I: Grid Application Placement (GAP) was not able to locate job {0} in the foreign job table.
CWLRB5896I: number of jobs in submitted state to recover is {0}.
CWLRB5897I: Unable to recover jobs in submitted state.
CWLRB5898I: number of jobs in cancel_pending state to recover is {0}.
CWLRB5899I: Unable to recover jobs in cancel pending state.
CWLRB5900I: {0} is not a valid value for {1} custom property.
CWLRB5901I: Unable to get the unique identifier of user[{0}]. Will not be able to retrieve group membership.
CWLRB5902I: BatchSensorComponent initializing.
CWLRB5903I: BatchSensorComponent initialized successfully.
CWLRB5904I: BatchSensorComponent starting...
CWLRB5905I: Successfully activated GridEndpointSensorMBean.
CWLRB5906I: GridEndpointSensorMBean deactivated.
CWLRB5907I: PJMMBean was not found at {0}.
CWLRB5908I: Unable to create Java Management Extensions (JMX) administration client to {0}.
CWLRB5909I: Compute Grid Portable Endpoint: {0} registered successfully!
CWLRB5910I: New endpoint {0} was discovered. The endpoint is being registered.
CWLRB5911I: Endpoint {0} was reregistered. Status is being synchronized.
CWLRB5912I: No heart beat received from endpoint {0} since {1} which is greater than the tolerance interval of {2}.
CWLRB5913I: Unable to convert {0} to a value. Use default value of {1}.
CWLRB5914I: Unexpected exception when parsing com.ibm.websphere.batch.policy.EndJobWhenSchedulerEnds. Value will be set to false.
CWLRB5915I: {0} is not specified. Default value is true on z/OS.
CWLRB5916I: Unexpected exception when parsing {0}. Value will be set to {1} milliseconds.
CWLRB5917I: config service can not resolve {0}.
CWLRB5918I: creating SynchronizeWSGridJobWithSchedulerAlarm with period = {0}.
CWLRB5919I: EndJobWhenSchedulerEnds policy is enabled and scheduler SR owning this job is down. Cancelling job : {0}.
CWLRB5920I: Unable to set transport {0} state on endpoint {1}. Endpoint is not registered in Serverindex.
CWLRB5921I: ThreadUsageObserver thread was interrupted. Exiting...
CWLRB5922I: iSeries platform - {0} is not loaded.
CWLRB5923I: Unable to load {0}, error= {1}.
CWLRB6000E: xJCL for job {0} was not found in store, can not restart.
CWLRB6001E: Job {0} is not restartable: invalid state: {1}
CWLRB6003E: No match found in job status table for jobid {0} with bjeename {1}. Job {0} can not restart.
CWLRB6100E: Discard Message because of expired timestamp : [Timestamp={0}] [Correlator={1}] [Text={2}]
CWLRB6101E: Discard Message because proxy has been terminated: [Timestamp={0}] [Correlator={1}] [Text={2}]
CWLRB6102E: Caught exception in JobSchedulerMDB.onMessage: {0}
CWLRB6103E: MQ initialization failed.
CWLRB6104E: Failed to create JobScheduler EJB
CWLRB6105E: Exception during JobWatcher.checkIfJobEnded for jobid={0} Exception={1}
CWLRB6106E: Unable to cancel job {0}
CWLRB6107E: Unable to cancel job because of invalid jobid {0}
CWLRB6108E: Unable to cancel job because of scheduler exception {0}
CWLRB6109E: Caught exception in JobSchedulerMDB.JobWatcher.alarm: {0}
CWLRB6110E: Failure retrieving joblog for job {0} - no joblog returned from scheduler.
CWLRB6111E: Caught exception in JobSchedulerMDB.initJMS
CWLRB6112E: JobSchedulerMDB.getJobSchedulerMBean could not find JobSchedulerMBean
CWLRB6113E: Caught exception in JobSchedulerMDB.getJobSchedulerMBean: {0}
CWLRB6114E: Caught exception in JobSchedulerMDB.createMessage: {0}
CWLRB6115E: Caught exception in JobSchedulerMDB.close: {0}
CWLRB6116E: Error in JobSchedulerMDB.processMessage: unknown message type: {0}
CWLRB6117E: Error in JobSchedulerMDB.processMessage: null message type
CWLRB6118E: Error in JobSchedulerMDB.processMessage: unknown command type: {0}
CWLRB6119E: Error in JobSchedulerMDB.processMessage: null command type
CWLRB6120E: Error converting com.ibm.websphere.batch.jobwatcher.alarm.interval to numeric - using default value {0}.
CWLRB6121E: Unknown failure in job submission.
CWLRB6122E: Error converting com.ibm.websphere.batch.early.arrival.grace.period to numeric - using default value {0}
CWLRB6123E: Error converting com.ibm.websphere.batch.message.time.to.live.ms to numeric - using default value(ms) {0}
CWLRB6124E: Generating runtime error due to parse error in JobSchedulerMDB.submitJob. Parse return code: {0}
CWLRB6125E: Caught exception in JobSchedulerMDB.submitJob: {0}
CWLRB6126E: Caught exception in JobSchedulerMDB.cancelJob: {0}
CWLRB6127E: Error converting correlator: {0}
CWLRB6128E: Exception accessing JMS message: {0}
CWLRB6129E: Caught exception in WSGridParser.readInputProperties: {0}
CWLRB6130E: WSGridJob.parse: unknown key = {0}
CWLRB6131E: Caught exception in WSGrid.writeProps: {0}
CWLRB6132E: UtilityJob.parse: unknown key = {0}
CWLRB6133E: CIJob.parse: unknown key = {0}
CWLRB6134E: BatchJob.parse: unknown key = {0}
CWLRB6135E: Directory {0} could not be created.
CWLRB6136E: Directory {0}{1} could not be created.
CWLRB6137E: Could not create status listener for requeued job {0}
CWLRB6138E: scheduler node and/or server name cannot be null for this operation
CWLRB6139E: update [{0}] SQLException : {1}
CWLRB6140E: findByJobid [{0}] SQLException : {1}
CWLRB6141E: remove [{0}] SQLException : {1}
CWLRB6142E: emove [{0}] SQLException : {1}
CWLRB6143E: {0} {1}. Exception {2}
CWLRB6144E: Failed while waiting for the control region. {0}
CWLRB6145E: Failed to invoke a servant region : {0}
CWLRB6146E: Failed while waiting for a servant region. {0}
CWLRB6147E: getBootStrapAddresses failed to find bootstrap server info
CWLRB6148E: {0} cleanup operation failed on {1};{2};{3}
CWLRB6149E: Can not retrieve job log for job {0} during restart. Log results may be truncated.
CWLRB6150E: Error scheduling {0} to the batch/grid discriminator for job {1}
CWLRB6151E: Error updating recurring request""s {0} owning scheduler.
CWLRB6152E: Exception occurred while creating job status for existing jobs in system: {0}
CWLRB6153E: Failed to schedule delayed job {0} due to a {1}: {2}
CWLRB6154E: Failed to get xJCL for delayed job {0} due to an Exception: {1}
CWLRB6155E: Failed to commit job profile transaction for job class {0}
CWLRB6156E: Error creating job profile for job class {0}
CWLRB6157E: Error deleting job profile for job class {0}
CWLRB6158E: Could not create status listener for job {0}
CWLRB6159E: Error during schedule takeover {0}
CWLRB6160E: Unable to fetch xJCL from repository for job name: {0}
CWLRB6161E: Did not get an endpoint back for node: {0} and server: {1}
CWLRB6162E: {0} Shutting down the scheduler server {1} on node {2}.To override this default behaviour set the Scheduler custom property {3} to false
CWLRB6163E: {0} Could not shutdown the server due to an error getting Node Agent MBean.
CWLRB6164E: remove {0} SQLException : {1}
CWLRB6165E: findByJobid {0} SQLException : {1}
CWLRB6166E: Exception thrown while getting uniqueID: {0}
CWLRB6167E: Received a failure return code from the SMF write macro SMFWTM: 0x{0}. Some SMF120-20 records may have been dropped.
CWLRB6168E: Subjob {0} failed to call collector SPI due to {1}
CWLRB6169E: Exception initing ProxyCommunicationManager
CWLRB6170E: Could not synchronize job status with endpoint: {0} error: {1}
CWLRB6171E: Exception occured initializing the PGC Proxy {0}
CWLRB6172E: Could not find URL for Endpoint: {0}
CWLRB6173E: FAILED to create {0} Bulletin Board.
CWLRB6174E: FAILED to get create Bulletin Board scope.
CWLRB6175E: FAILED to activate {0} MBean : {1}
CWLRB6176E: Error obtaining EndpointSRMBean {0}
CWLRB6177E: Unable to get {0}/{1} adminClient : caught Exception {2}
CWLRB6178E: Failed to query MBean {0}
CWLRB6179E: FAILED to invoke EndpointCRMBean due to : {0}
CWLRB6180E: FAILED to activate {0} MBean : {1}
CWLRB6181E: GridEndpointSensorMBean is null
CWLRB6182E: Error invoking cancel operation. Exception = {0}
CWLRB6200W: Exception in JobScheduler.init()
CWLRB6201W: Unresolved symbols encountered: {0}
CWLRB6202W: could not obtain WebSphere variableMap
CWLRB6203W: could not resolve variable
CWLRB6204W: xJCL for job: {0} not found in cache
CWLRB6205W: Invalid JobstatusDO {0}
CWLRB6206W: Invalid schedulerName {0}
CWLRB6208W: The time stamp dir: {0} is empty on {1}
CWLRB6209W: Exception copying over job logs from down scheduler {0}
CWLRB6210W: Endpoint is unavailable, remote dir list cannot be obtained
CWLRB6211W: Unable to update status message for job {0}. Moving to next status message.
CWLRB6212W: called create with empty JMCUserPrefDO
CWLRB6213W: Unable to add {0} as a config change listener.
CWLRB6214W: {0} was not able to obtain a ServiceHandle.
CWLRB6215W: {0}() jobID {1} already exists in DB
CWLRB6216W: Invalid target {0}
CWLRB6217W: Could not obtain node agent for target machine
CWLRB6218W: The dir: {0} is empty on {1}
CWLRB6219W: Error closing inputstream!
CWLRB6220W: Error closing outputstream!
CWLRB6221W: Exception {0}
CWLRB6222W: Job {0} not found
CWLRB6223W: Job {0} is not {1}: invalid state: [{2}]
CWLRB6224W: Job {0} is not restartable: invalid state: [{1}]
CWLRB6225W: Job {0} purge failed: not elements found in persistent stores
CWLRB6227W: Job {0} is not suspendable: invalid state: [{1}]
CWLRB6228W: Job {0} is not resumeable: invalid state: [{1}]
CWLRB6229W: Could not read {0} from down scheduler {1}
CWLRB6230W: Invocation of stopProcess failed, trying to terminate the process
CWLRB6231W: {0} Scheduler custom property {1} set to false, no shutdown of server initiated
CWLRB6232W: WARNING : {0} : Sync to thread is NOT enabled. User applications will run under Server credential
CWLRB6233W: Unknown message..discarding {0}
CWLRB6234W: No such PGC Endpoint: {0}
CWLRB6235W: Could not mark jobs owned by {0} as restartable
CWLRB6236W: Invalid Heartbeat Tolerance Interval specified {0}
CWLRB6237W: Invalid Heartbeat Poll Interval specified {0}
CWLRB6238W: Endpoint {0} is unreachable command {1} may not be processed
CWLRB6239W: Could not find URL for Endpoint: {0} it may be deregistered because its unreachable
CWLRB6240W: Endpoint is unreachable {0}
CWLRB6241W: Could not load Endpoint reference {0}
CWLRB6242W: {0} Could not send status update message to: {1}
CWLRB6243W: unable to convert collectorData to byte array. Setting collector data to NULL
CWLRB6244W: Could not send explicit heart beat {0}
CWLRB6245W: Exception occured obtaining odcTree
CWLRB6246W: Unable to obtain transport state using defaults {0}
CWLRB6247W: Invalid heart beat interval: {0}
CWLRB6248W: Exception loading class {0} make sure it exists
CWLRB6249W: ClassNotFoundException loading class {0}
CWLRB6250W: Security Exception loading class {0}
CWLRB6251W: NoSuchMethodException loading class {0}
CWLRB6252W: IllegalArgumentException loading class {0}
CWLRB6253W: IllegalAccessException loading class {0}
CWLRB6254W: InvocationTargetException loading class {0}
CWLRB6255W: FAILED to load {0} : {1}
CWLRB6256W: {0} NOT FOUND. Due to {1}
CWLRB6257W: Could not obtain node agent for scheduler machine
CWLRB6258I: Possible job class capacity leak for {0} job class. Concurrent job count is {1}, number of jobs not in final state is {2}.
CWLRB6259I: Reset {0} job class, concurrent job count was change from {1} to {2}.
CWLRB6260I: Possible job class capacity excess for {0} job class. Concurrent job count is {1}, number of jobs not in final state is {2}.
CWLRB6261E: The job scheduler did not initialize because the job scheduler EJBs were not running when the job scheduler performed a context lookup.
CWLRB6262W: On the fowarded owning scheduler {0}, the purge operation for job {1} completed with exception {2}
CWLRB6263W: On the owning scheduler {0}, the purge operation for job {1} completed with exception {2}
CWLRB6264W: The purge operation for job {0} was not processed because the owning scheduler {1} was not active.
CWLRB6265W: The job scheduler encountered exception when attempting to purge joblog for job {0}. The exception is {1}
CWLRB6266I: {0} job log parts were written to the {1} directory.
CWLRB6267W: The value that is used to indicate the number of job log parts that must be written for a message to be issued is not valid: {0}. Set the JobLogCountAlert WebSphere variable to an integer value of 0 or greater.
CWLRB6270W: The job might need to be resubmitted because the scheduler server received an HTTP response code of {1} from the {0} endpoint server when the job was dispatched.
CWLRB6271E: The lrcmd tool failed to load SOAP client properties from {0}.
CWLRB6276I: Maximum job log part size is {0} bytes
CWLRB6277W: Invalid maximum job log part size: {0}. Default job logging settings will be used.
CWLRB6290E: Could not add correlator for job {0}: {1}
CWLRB6291E: Could not retrieve correlator for job {0}: {1}
CWLRB6292E: Could not send takeover message to WSGRID. Client takeover not available.
CWLRB6293E: Could not send job end message for the {0} job to WSGRID client.
CWLRB6300E: The job dispatch process timed out after {0} milliseconds while it waited for a response.
CWLRB6301E: Unable to connect to {0}/{1} adminClient : received Exception {2}
CWLRB6400W: The handling of the Java batch COBOL container log has timed out.
CWLRB6401W: The wait time for the COBOL job is invalid: {0}
CWLRB9900I: lrcmd Command Specific Usage:



Submit a grid job to the job scheduler where the job definition is located at

local file system.



   lrcmd

    -cmd=submit -xJCL=<xjcl_file>

    [<command options>]

    [<optional parameters>]

    [<general options>]



Submit a grid job to the job scheduler where the job definition is stored at

the job repository of the job scheduler.



   lrcmd

    -cmd=submit -job=<job_name>

    [<command options>]

    [<optional parameters>]

    [<general options>]



Command options:

   -xJCL=<xjcl_file>

    specifies the path of the job definition xJCL file which

    describes the grid job to be scheduled for execution.

   -job=<job_name>

    specifies the name to be used when submitting the job definition

    stored at the job repository, or adding the job definition xJCL

    from -xJCL=<xjcl_file> to the job repository.

   -add

    add the job definition xJCL to the job repository of the job

    scheduler using job_name from -job=<job_name> as the key.

   -replace

    replace (or add) the job definition xJCL to the job repository

    of the job scheduler using job_name from -job=<job_name> as

    the key.

   -startDate=<start_date>

    specifies the date in which the job should be submitted for

    execution where the required start_date format is yyyy-MM-dd.

    This parameter requires the -startTime parameter to be defined

    as well.

   -startTime=<start_time>

    specifies the time in which the job should be submitted for

    execution where the required start_time format is HH:mm:ss.

    This parameter requires the -startDate parameter to be defined

    as well.



Optional parameters:

   <name>=<value>

    name value pair to replace symbolics defined in the xJCL.

    i.e. Checkpoint=timebased means to replace instance(s) in the

    xJCL of "${Checkpoint}"



    <checkpoint-algorithm-ref name=""${Checkpoint}"" /> becomes

    <checkpoint-algorithm-ref name="timebased" /> when the job

    definition xJCL is processed.



    <value> may be any of:

    - self-defining values i.e., timebased

    - WebSphere Environment variables i.e., "${LOG_ROOT}"

    - or a JVM System property.



General options:

   To show the general options, use following command

    lrcmd -cmd=help



Examples:

   >> ./lrcmd.sh -cmd=submit -xJCL=C:\myXJCL -port=80

    -host=myodrhost.com



   >> ./lrcmd.sh -cmd=submit -xJCL=C:\myXJCL -add -job=MyJob

    -port=9080 -host=mygshost.com



   >> ./lrcmd.sh -cmd=submit -xJCL=C:\myXJCL -add -job=MyJob

    -port=80 -startDate=2007-01-25 -startTime=23:59:00



   >> ./lrcmd.sh -cmd=submit -xJCL=C:\myXJCL -port=80

    -host=myodrhost.com -userid=myname -password=mypassword



   >> ./lrcmd.sh -cmd=submit -xJCL=C:\myXJCL -port=80

    -host=mygshost.com Checkpoint=timebased interval=30

CWLRB9901I: lrcmd Command Specific Usage:

Restart the execution of a job. Only jobs in restartable state can be

restarted.



   lrcmd -cmd=restart -jobid=<job_id> [<general options>]



Command Option:

   -jobid=<job_id>

    is the job ID assigned to the job by the job scheduler. The job

    ID is returned by the lrcmd -cmd=submit command that initially

    submitted the job. The -cmd=status command can also be used to

    identify the job ID for a particular job.



General options:

   To show the general options, use following command

    lrcmd -cmd=help



Examples:

   >> ./lrcmd -cmd=restart -jobid=MyApp:1 -port=80 -host=myodrhost.com



   >> ./lrcmd -cmd=restart -jobid=MyApp:1 -port=9080 -host=mygshost.com

    -userid=myname -password=mypassword

CWLRB9902I: lrcmd Command Specific Usage:

Save the job definition xJCL into the job repository of the job

scheduler for the use by future.



   lrcmd

    -cmd=save -xJCL=<xjcl_file> -job=<job_name>

    [ -replace ]

    [<general options>]



Command options:

   -xJCL=<xjcl_file>

    specifies the path of the job definition xJCL file which

    describes the grid job.

   -job=<job_name>

    specifies the name to use when saving the job definition xJCL.

    The job name can be used on future

   -replace

    replaces the job definition xJCL if it exists.



General options:

   To show the general options, use following command

    lrcmd -cmd=help



Examples:

   >> ./lrcmd -cmd=save -xJCL=C:\myXJCL -job=MyJob -port=9080

    -host=mygshost.com



   >> ./lrcmd -cmd=save -xJCL=C:\myXJCL -job=MyJob -replace -port=80

    -host=myodrhost.com -userid=myname -password=mypassword

CWLRB9903I: lrcmd Command Specific Usage:

Show the symbolic variables which are referenced in the job definition

xJCL.



   lrcmd -cmd=getSymbolicVariables -xJCL=<xjcl_file> [<general options>]



   lrcmd

    -cmd=getSymbolicVariables -job=<job_name>

    [<general options>]



Command options:

   -xJCL=<xjcl_file>

    specifies the path of the job definition xJCL file which

    describes the grid job.

   -job=<job_name>

    specifies the job name which is a key in the job repository of

    the job scheduler.



General options:

   To show the general options, use following command

    lrcmd -cmd=help



Examples:

   >> ./lrcmd -cmd=getSymbolicVariables -xJCL=C:\myXJCL -port=9080

    -host=mygshost.com



   >> ./lrcmd -cmd=getSymbolicVariables -job=MyJob -port=80

    -host=myodrhost.com -userid=myname -password=mypassword

CWLRB9904I: lrcmd Command Specific Usage:

Remove the job definition from the job repository of the job scheduler.



   lrcmd -cmd=remove -job=<job_name> [<general options>]



Command option:

   -job=<job_name>

    specifies the job name which is a key in the job repository of

    the job scheduler.



General options:

   To show the general options, use following command

    lrcmd -cmd=help



Example:

   >> ./lrcmd -cmd=remove -job=MyJob -port=80 -host=myodrhost.com

    -userid=myname -password=mypassword

CWLRB9905I: lrcmd Command Specific Usage:

Show the content of a job definition from the job repository of the

job scheduler.



   lrcmd -cmd=show -job=<job_name> [<general options>]



Show the job name(s) from the job repository of the job scheduler.



   lrcmd

    -cmd=show -filter=<job_name_filter>

    [ -descending ]

    [<general options>]



Command options:

   -job=<job_name>

    specifies the job name which is a key in the job repository of

    the job scheduler.

   -filter=<job_name_filter>

    specifies the filter criteria of job name in the job repository

    of the job scheduler.

   -descending

    the result set is sorted in a descending sequence.



General options:

   To show the general options, use following command

    lrcmd -cmd=help



Examples:

   >> ./lrcmd -cmd=show -job=MyJob -port=80 -host=myodrhost.com



   >> ./lrcmd -cmd=show -filter=% -descending -port=80

    -host=myodrhost.com -userid=myname -password=mypassword

CWLRB9906I: lrcmd Command Specific Usage:

Cancel the execution of a previously-submitted job.



   lrcmd -cmd=cancel -jobid=<job_id> [<general options>]



Command Option:

   -jobid=<job_id>

    is the job ID assigned to the job by the job scheduler. The job

    ID is returned by the lrcmd -cmd=submit command that initially

    submitted the job. The -cmd=status command can also be used to

    identify the job ID for a particular job.



General options:

   To show the general options, use following command

    lrcmd -cmd=help



Examples:

   >> ./lrcmd -cmd=cancel -jobid=MyApp:1 -port=80 -host=myodrhost.com



   >> ./lrcmd -cmd=cancel -jobid=MyApp:1 -port=9080 -host=mygshost.com

    -userid=myname -password=mypassword

CWLRB9907I: lrcmd Command Specific Usage:

Stop the execution of a previously-submitted job when a checkpoint

happens.



   lrcmd -cmd=stop -jobid=<job_id> [<general options>]



Command Option:

   -jobid=<job_id>

    is the job ID assigned to the job by the job scheduler. The job

    ID is returned by the lrcmd -cmd=submit command that initially

    submitted the job. The -cmd=status command can also be used to

    identify the job ID for a particular job.



General options:

   To show the general options, use following command

    lrcmd -cmd=help



Examples:

   >> ./lrcmd -cmd=stop -jobid=MyApp:1 -port=80 -host=myodrhost.com



   >> ./lrcmd -cmd=stop -jobid=MyApp:1 -port=9080 -host=mygshost.com

    -userid=myname -password=mypassword

CWLRB9908I: lrcmd Command Specific Usage:

Suspend the execution of a batch job for the specified number of

seconds. Unless manually resumed (with lrcmd -cmd=resume, for example),

the job automatically resumes running after the specified number of

seconds.



   lrcmd

    -cmd=suspend -jobid=<job_id>

    [ -seconds=<seconds> ]

    [<general options>]



Command Options:

   -jobid=<job_id>

    is the job ID assigned to the job by the job scheduler. The job

    ID is returned by the lrcmd -cmd=submit command that initially

    submitted the job. The -cmd=status command can also be used to

    identify the job ID for a particular job.

   -seconds=<seconds>

    indicates for how many seconds job execution should be suspended.

    If not specified, the default value of 15 seconds is used.

    If -seconds=0 is specified, the job does not resume execution

    until manually resumed.



General options:

   To show the general options, use following command

    lrcmd -cmd=help



Examples:

   >> ./lrcmd -cmd=suspend -jobid=MyApp:1 -port=80 -host=myodrhost.com



   >> ./lrcmd -cmd=suspend -jobid=MyApp:1 -seconds=0 -port=9080

    -host=mygshost.com -userid=myname -password=mypassword

CWLRB9909I: lrcmd Command Specific Usage:

Resume execution of a previously suspended batch job.



   lrcmd -cmd=resume -jobid=<job_id> [<general options>]



Command Option:

   -jobid=<job_id>

    is the job ID assigned to the job by the job scheduler. The job

    ID is returned by the lrcmd -cmd=submit command that initially

    submitted the job. The -cmd=status command can also be used to

    identify the job ID for a particular job.



General options:

   To show the general options, use following command

    lrcmd -cmd=help



Examples:

   >> ./lrcmd -cmd=resume -jobid=MyApp:1 -port=80 -host=myodrhost.com



   >> ./lrcmd -cmd=resume -jobid=MyApp:1 -port=9080 -host=mygshost.com

    -userid=myname -password=mypassword

CWLRB9910I: lrcmd Command Specific Usage:

Purge job information from the job scheduler and execution

environments.



   lrcmd -cmd=purge -jobid=<job_id> [<general options>]



Command Option:

   -jobid=<job_id>

    is the job ID assigned to the job by the job scheduler. The job

    ID is returned by the lrcmd -cmd=submit command that initially

    submitted the job. The -cmd=status command can also be used to

    identify the job ID for a particular job.



General options:

   To show the general options, use following command

    lrcmd -cmd=help



Examples:

   >> ./lrcmd -cmd=purge -jobid=MyApp:1 -port=80 -host=myodrhost.com



   >> ./lrcmd -cmd=purge -jobid=MyApp:1 -port=9080 -host=mygshost.com

    -userid=myname -password=mypassword

CWLRB9911I: lrcmd Command Specific Usage:

Display the output generated by the job scheduler and execution

environment during the execution of the specified job.



   lrcmd -cmd=output -jobid=<job_id> [<general options>]



Command Option:

   -jobid=<job_id>

    is the job ID assigned to the job by the job scheduler. The job

    ID is returned by the lrcmd -cmd=submit command that initially

    submitted the job. The -cmd=status command can also be used to

    identify the job ID for a particular job.



General options:

   To show the general options, use following command

    lrcmd -cmd=help



Examples:

   >> ./lrcmd -cmd=output -jobid=MyApp:1 -port=80 -host=myodrhost.com



   >> ./lrcmd -cmd=output -jobid=MyApp:1 -port=9080 -host=mygshost.com

    -userid=myname -password=mypassword

CWLRB9912I: lrcmd Command Specific Usage:

Display status information about one or more jobs in the job scheduler

database.



   lrcmd -cmd=status [ -jobid=<job_id> ] [<general options>]



Command Option:

   -jobid=<job_id>

    is the job ID assigned to the job by the job scheduler. The job

    ID is returned by the lrcmd -cmd=submit command that initially

    submitted the job. The -cmd=status command can also be used to

    identify the job ID for a particular job.



General options:

   To show the general options, use following command

    lrcmd -cmd=help



Examples:

   >> ./lrcmd -cmd=status -port=80 -host=myodrhost.com



   >> ./lrcmd -cmd=status -jobid=MyApp:1 -port=9080 -host=mygshost.com

    -userid=myname -password=mypassword

CWLRB9913I: lrcmd Command Specific Usage:

Create a job schedule to the job scheduler. The job scheduler submits

jobs against the specified job definition at time intervals indicated

by the arguments.



   lrcmd

    -cmd=submitRecurringRequest

    -xJCL=<xjcl_file>

    -request=<request_name>

    -startDate=<start_date>

    -startTime=<start_time>

    -interval=<interval>

    [<optional parameters>]

    [<general options>]



   lrcmd

    -cmd=submitRecurringRequest

    -job=<job_name>

    -request=<request_name>

    -startDate=<start_date>

    -startTime=<start_time>

    -interval=<interval>

    [<optional parameters>]

    [<general options>]



Command Options:

   -xJCL=<xjcl_file>

    specifies the path of the job definition xJCL file which

    describes the grid job.

   -job=<job_name>

    specifies the job name which is a key in the job repository of

    the job scheduler.

   -request=<request_name>

    specifies the unique name of the request used to identify this

    job schedule.

   -startDate=<start_date>

    specifies the date in which the first job gets submitted for

    execution where the required format is yyyy-MM-dd.

   -startTime=<start_time>

    specifies the time in which the first job and all subsequent jobs

    get submitted for execution where the required format is

    HH:mm:ss.

   -interval=<interval>

    specifies the time period between two job submissions for this

    job scheudule where the supported time periods are

    - daily

    - weekly

    - monthly



Optional parameters:

   <name>=<value>

    name value pair to replace symbolics defined in the xJCL.

    i.e. Checkpoint=timebased means to replace instance(s) in the

    xJCL of "${Checkpoint}"



    <checkpoint-algorithm-ref name=""${Checkpoint}"" /> becomes

    <checkpoint-algorithm-ref name="timebased" /> when the job

    definition xJCL is processed.



    <value> may be any of:

    - self-defining values i.e., timebased

    - WebSphere Environment variables i.e., "${LOG_ROOT}"

    - or a JVM System property.



General options:

   To show the general options, use following command

    lrcmd -cmd=help



Examples:

   >> ./lrcmd -cmd=submitRecurringRequest -xJCL=C:\myXJCL

    -request=MyMonthlyReport -interval=monthly -startDate=2006-01-02

    -startTime=23:59:00 -port=80 -host=myodrhost.com



   >> ./lrcmd -cmd=submitRecurringRequest -job=WeeklyJob

    -request=MyWeeklyReport -interval=weekly -startDate=2006-01-02

    -startTime=23:59:00 -port=9080 -host=mygshost.com -userid=myname

    -password=mypassword



   >> ./lrcmd -cmd=submitRecurringRequest -job=DailyJob

    -request=MyDailyReport -interval=daily -startDate=2006-01-02

    -startTime=23:59:00 Checkpoint=timebased counter=30 -port=9080

    -host=mygshost.com

CWLRB9914I: lrcmd Command Specific Usage:

Modify an existing job schedule.



   lrcmd

    -cmd=modifyRecurringRequest

    -request=<request_name>

    <command options>

    [<optional parameters>]

    [<general options>]



Command Options:

   -request=<request_name>

    specifies the job schedule name to be modified.

   -xJCL=<xjcl_file>

    specifies the path of the job definition xJCL file which

    describes the grid job.

   -startDate=<start_date>

    specifies the date in which the first job gets submitted for

    execution where the required format is yyyy-MM-dd.

   -startTime=<start_time>

    specifies the time in which the first job and all subsequent jobs

    get submitted for execution where the required format is

    HH:mm:ss.

   -interval=<interval>

    specifies the time period between two job submissions for this

    job scheudule where the supported time periods are

    - daily

    - weekly

    - monthly



   Note that one of the following options must be defined for this

   command:

    -xJCL, -interval, (-startDate and -startTime),

    <optional parameters>



Optional parameters:

   <name>=<value>

    name value pair to replace symbolics defined in the xJCL.

    i.e. Checkpoint=timebased means to replace instance(s) in the

    xJCL of "${Checkpoint}"



    <checkpoint-algorithm-ref name=""${Checkpoint}"" /> becomes

    <checkpoint-algorithm-ref name="timebased" /> when the job

    definition xJCL is processed.



    <value> may be any of:

    - self-defining values i.e., timebased

    - WebSphere Environment variables i.e., "${LOG_ROOT}"

    - or a JVM System property.



General options:

   To show the general options, use following command

    lrcmd -cmd=help



Examples:

   >> ./lrcmd -cmd=modifyRecurringRequest -request=MyMonthlyReport

    -xJCL=C:\myXJCL -port=80 -host=myodrhost.com



   >> ./lrcmd -cmd=modifyRecurringRequest -request=MyReport

    -interval=weekly -port=80 -host=myodrhost.com



   >> ./lrcmd -cmd=modifyRecurringRequest -request=MyMonthlyReport

    -startDate=2006-01-02 -startTime=23:59:00 -port=80

    -host=myodrhost.com



   >> ./lrcmd -cmd=modifyRecurringRequest -request=MyDailyReport

    -xJCL=C:\myXJCL -interval=daily -startDate=2006-01-02

    -startTime=23:59:00 Checkpoint=timebased counter=30 -port=9080

    -host=mygshost.com -userid=myname -password=mypassword

CWLRB9915I: lrcmd Command Specific Usage:

Cancel an existing job schedule.



   lrcmd

    -cmd=cancelRecurringRequest

    -request=<request_name>

    [<general options>]



Command Option:

   -request=<request_name>

    specifies the job schedule name to be cancelled.



General options:

   To show the general options, use following command

    lrcmd -cmd=help



Example:

   >> ./lrcmd -cmd=cancelRecurringRequest -request=MyDailyReport

    -port=9080 -host=mygshost.com -userid=myname -password=mypassword

CWLRB9916I: lrcmd Command Specific Usage:

Show details of an existing job schedule.



   lrcmd

    -cmd=getRecurringRequestDetails

    -request=<request_name>

    [<general options>]



Command Option:

   -request=<request_name>

    specifies the job schedule name to be shown.



General options:

   To show the general options, use following command

    lrcmd -cmd=help



Example:

   >> ./lrcmd -cmd=getRecurringRequestDetails -request=MyDailyReport

    -port=9080 -host=mygshost.com -userid=myname -password=mypassword

CWLRB9917I: lrcmd Command Specific Usage:

List all existing job schedules.



   lrcmd -cmd=showAllRecurringRequests [<general options>]



General options:

   To show the general options, use following command

    lrcmd -cmd=help



Example:

   >> ./lrcmd -cmd=showAllRecurringRequests -port=9080

    -host=mygshost.com -userid=myname -password=mypassword

CWLRB9918I: lrcmd Command Specific Usage:

Show all jobs of a job schedule.



   lrcmd

    -cmd=showRecurringJobs

    -request=<request_name>

    [<general options>]



Command Option:

   -request=<request_name>

    specifies the job schedule name to be shown.



General options:

   To show the general options, use following command

    lrcmd -cmd=help



Example:

   >> ./lrcmd -cmd=showRecurringJobs -request=MyDailyReport

    -port=9080 -host=mygshost.com -userid=myname -password=mypassword

CWLRB9919I: lrcmd Command Specific Usage:

Display the overall return code produced by a batch job.

    0 - The job has been submitted for execution.

    1 - A cancel request is pending against the job.

    2 - A suspend request is pending against the job.

    3 - A resume request is pending against the job.

    4 - The job is executing.

    5 - Job execution is suspended.

    6 - The job has been cancelled.

    7 - Job execution has ended.

    8 - The job has failed execution but is restartable.

    9 - The job has failed execution and is not restartable.

   10 - The job is pending submission.

   11 - A stop request is pending against the job.



   lrcmd -cmd=getBatchJobRC -jobid=<job_id> [<general options>]



Command Option:

   -jobid=<job_id>

    is the job ID assigned to the job by the job scheduler. The job

    ID is returned by the lrcmd -cmd=submit command that initially

    submitted the job. The -cmd=status command can also be used to

    identify the job ID for a particular job.



General options:

   To show the general options, use following command

    lrcmd -cmd=help



Example:

   >> ./lrcmd -cmd=getBatchJobRC -jobid=MyApp:1 -port=9080

    -host=mygshost.com -userid=myname -password=mypassword

CWLRB9920I: lrcmd Command Specific Usage:

Display the job log associated with the requested job identifier.



   lrcmd -cmd=getJobLog -jobid=<job_id> [<general options>]



Command Option:

   -jobid=<job_id>

    is the job ID assigned to the job by the job scheduler. The job

    ID is returned by the lrcmd -cmd=submit command that initially

    submitted the job.



General options:

   To show the general options, use the command: lrcmd -cmd=help



Examples:

   >> ./lrcmd -cmd=getJobLog -jobid=MyApp:1 -port=80 -host=myodrhost.com



   >> ./lrcmd -cmd=getJobLog -jobid=MyApp:1

    -port=9080 -host=mygshost.com

    -userid=myname -password=mypassword

CWLRB9921I: lrcmd Command Specific Usage:

Display the job log meta-data for the requested job identifier. The

job log meta-data indicates the log time stamp(s) associated with the

requested job identifier. The meta-data ( or time stamp ) identifies

a unique instance of the job. Logs from multiple different jobs with

the same job number may exist.



   lrcmd -cmd=getLogMetaData -jobid=<job_id> [<general options>]



Command Option:

   -jobid=<job_id>

    is the job ID assigned to the job by the job scheduler. The job

    ID is returned by the lrcmd -cmd=submit command that initially

    submitted the job.



General options:

   To show the general options, use the command: lrcmd -cmd=help



Examples:

   >> ./lrcmd -cmd=getLogMetaData -jobid=MyApp:1

    -port=80 -host=myodrhost.com



   >> ./lrcmd -cmd=getLogMetaData -jobid=MyApp:1

    -port=9080 -host=mygshost.com

    -userid=myname -password=mypassword

CWLRB9922I: lrcmd Command Specific Usage:

Remove the job log associated with the requested job identifier.



   lrcmd

    -cmd=purgeJobLog -jobid=<job_id>

    -logTimeStamp=<logTimeStamp>

    [<general options>]



Command Option:

   -jobid=<job_id>

    is the job ID assigned to the job by the job scheduler. The job

    ID is returned by the lrcmd -cmd=submit command that initially

    submitted the job.

   -logTimeStamp=<logTimeStamp>

    indicates the time stamp (that is, sub-directory name) which

    identifies the job log whose part list information is to

    be returned. The time stamp is returned by -cmd=getLogMetaData.



General options:

   To show the general options, use the command: lrcmd -cmd=help



Examples:

   >> ./lrcmd -cmd=purgeJobLog -jobid=MyApp:1

    -logTimeStamp=20102006_155529 -port=80 -host=myodrhost.com



   >> ./lrcmd -cmd=purgeJobLog -jobid=MyApp:1

    -logTimeStamp=20102006_155529 -port=9080 -host=myodrhost.com

    -userid=myname -password=mypassword

CWLRB9923I: lrcmd Command Specific Usage:

Save the job log associated with the requested job identifier to the

local file system.



   lrcmd

    -cmd=saveJobLog -jobid=<job_id> -fileName=<fileName>

    [<general options>]



Command Options:

   -jobid=<job_id>

    is the job ID assigned to the job by the job scheduler. The job

    ID is returned by the lrcmd -cmd=submit command that initially

    submitted the job.

   -fileName=<fileName>

    indicates the name of a file on the local file system where the

    zipped job log data should be saved. The file will be replaced

    if it exists. The file name <fileName> may not contain embedded

    blanks.



General options:

   To show the general options, use the command: lrcmd -cmd=help



Examples:

   >> ./lrcmd -cmd=saveJobLog -jobid=MyApp:1

    -fileName=/tmp/myZippedJobLog -port=80 -host=myodrhost.com



   >> ./lrcmd -cmd=saveJobLog -jobid=MyApp:1

    -fileName=/tmp/mySavedJobLog -port=9080 -host=mygshost.com

    -userid=myname -password=mypassword

CWLRB9924I: lrcmd Command Specific Usage:

Display the job log part list associated with the requested job

identifier and log time stamp.



   lrcmd

    -cmd=getLogPartList -jobid=<job_id>

    -logTimeStamp=<logTimeStamp>

    [<general options>]



Command Options:

   -jobid=<job_id>

    is the job ID assigned to the job by the job scheduler. The job

    ID is returned by the lrcmd -cmd=submit command that initially

    submitted the job.

   -logTimeStamp=<logTimeStamp>

    indicates the time stamp (that is, sub-directory name) which

    identifies the job log whose part list information is to

    be returned. The time stamp is returned by -cmd=getLogMetaData.



General options:

   To show the general options, use the command: lrcmd -cmd=help



Examples:

   >> ./lrcmd -cmd=getLogPartList -jobid=MyApp:1

    -logTimeStamp=20102006_155529 -port=80 -host=myodrhost.com



   >> ./lrcmd -cmd=getLogPartList -jobid=MyApp:1

    -logTimeStamp=20102006_155529 -port=9080 -host=myodrhost.com

    -userid=myname -password=mypassword

CWLRB9925I: lrcmd Command Specific Usage:

Display the size of the job log associated with the requested job

identifier. The command returns the size of the job log in bytes.



   lrcmd

    -cmd=getLogSize -jobid=<job_id>

    -logTimeStamp=<logTimeStamp>

    [<general options>]



Command Options:

   -jobid=<job_id>

    is the job ID assigned to the job by the job scheduler. The job

    ID is returned by the lrcmd -cmd=submit command that initially

    submitted the job.

   -logTimeStamp=<logTimeStamp>

    indicates the time stamp (that is, sub-directory name) which

    identifies the job log whose part list information is to

    be returned. The time stamp is returned by -cmd=getLogMetaData.



General options:

   To show the general options, use the command: lrcmd -cmd=help



Examples:

   >> ./lrcmd -cmd=getLogSize -jobid=MyApp:1

    -logTimeStamp=20102006_155529 -port=80 -host=myodrhost.com



   >> ./lrcmd -cmd=getLogSize -jobid=MyApp:1

    -logTimeStamp=20102006_155529 -port=9080 -host=myodrhost.com

    -userid=myname -password=mypassword

CWLRB9926I: lrcmd Command Specific Usage:

Display the age of the job log associated with the requested job

identifier. The command returns the age of the job log in seconds

since it was last modified. The age is in milliseconds since the

standard base time known as "the epoch", January 1, 1970, 00:00:00 GMT



   lrcmd

    -cmd=getLogAge -jobid=<job_id>

    -logTimeStamp=<logTimeStamp>

    [<general options>]



Command Options:

   -jobid=<job_id>

    is the job ID assigned to the job by the job scheduler. The job

    ID is returned by the lrcmd -cmd=submit command that initially

    submitted the job.

   -logTimeStamp=<logTimeStamp>

    indicates the time stamp (that is, sub-directory name) which

    identifies the job log whose part list information is to

    be returned. The time stamp is returned by -cmd=getLogMetaData.



General options:

   To show the general options, use the command: lrcmd -cmd=help



Examples:

   >> ./lrcmd -cmd=getLogAge -jobid=MyApp:1

    -logTimeStamp=20102006_155529 -port=80 -host=myodrhost.com



   >> ./lrcmd -cmd=getLogAge -jobid=MyApp:1

    -logTimeStamp=20102006_155529 -port=9080 -host=myodrhost.com

    -userid=myname -password=mypassword

CWLRB9927I: lrcmd Command Specific Usage:

Display the job log part associated with the requested job identifier,

log time stamp, and log part.



   lrcmd

    -cmd=getLogPart -jobid=<job_id>

    -logTimeStamp=<logTimeStamp>

    -logPart=<logPart>

    [<general options>]



Command Options:

   -jobid=<job_id>

    is the job ID assigned to the job by the job scheduler. The job

    ID is returned by the lrcmd -cmd=submit command that initially

    submitted the job.

   -logTimeStamp=<logTimeStamp>

    indicates the time stamp (that is, sub-directory name) which

    identifies the job log whose part list information is to

    be returned. The time stamp is returned by -cmd=getLogMetaData.

   -logPart=<logPart>

    indicates the portion of the job log associated with the

    requested job identifier and time stamp to be returned. The log

    part information is returned by -cmd=getLogPartList.



General options:

   To show the general options, use the command: lrcmd -cmd=help



Examples:

   >> ./lrcmd -cmd=getLogPart -jobid=MyApp:1

    -logTimeStamp=20102006_155529 -logPart=part.9.log

    -port=80 -host=myodrhost.com



   >> ./lrcmd -cmd=getLogPart -jobid=MyApp:1

    -logTimeStamp=20102006_155529 -logPart=part.9.log

    -port=9080 -host=myodrhost.com

    -userid=myname -password=mypassword

CWLRB9928I: lrcmd Command Specific Usage:

Display information for job(s) associated with the requested job class.

The information returned contains the job directory structure.

It is of the form:

job_directory/time_stamp_directory

i.e., MyApp_1/20102006_155529



   lrcmd

    -cmd=getJobsByClass -jobid=<job_id> -class=<class>

    [<general options>]



Command Options:

   -jobid=<job_id>

    is the job ID assigned to the job by the job scheduler. The job

    ID is returned by the lrcmd -cmd=submit command that initially

    submitted the job.

   -class=<class>

    indicates the name of the job class whose job identifiers

    are to be returned.



General options:

   To show the general options, use the command: lrcmd -cmd=help



Examples:

   >> ./lrcmd -cmd=getJobsByClass -jobid=MyApp:1

    -class=Default -port=80 -host=myodrhost.com



   >> ./lrcmd -cmd=getJobsByClass -jobid=MyApp:1

    -class=Default -port=9080 -host=mygshost.com

    -userid=myname -password=mypassword

CWLRB9929I: lrcmd Command Usage:

Display information for job(s) associated with the requested job class.

The information returned contains the job directory structure and the

age of the job log in days.

It is of the form:

age job_directory/time_stamp_directory

i.e., 5 MyApp_1/20102006_155529



   lrcmd

    -cmd=getJobLogMetaDataByAgeForClass

    -jobid=<job_id> -class=<class>

    [<general options>]



Command Options:

   -jobid=<job_id>

    is the job ID assigned to the job by the job scheduler. The job

    ID is returned by the lrcmd -cmd=submit command that initially

    submitted the job.

   -class=<class>

    indicates the name of the job class whose information

    is to be returned.



General options:

   To show the general options, use the command: lrcmd -cmd=help



Examples:

   >> ./lrcmd -cmd=getJobLogMetaDataByAgeForClass -jobid=MyApp:1

    -class=Default -port=80 -host=myodrhost.com



   >> ./lrcmd -cmd=getJobLogMetaDataByAgeForClass -jobid=MyApp:1

    -class=Default -port=9080 -host=mygshost.com

    -userid=myname -password=mypassword

CWLRB9930I: lrcmd Command Usage:

Display information for job(s) associated with the requested job class.

The information returned contains the job directory structure and the

size of the job log in bytes.

It is of the form:

age job_directory/time_stamp_directory

i.e., 4096 MyApp_1/20102006_155529



   lrcmd

    -cmd=getJobLogMetaDataBySizeForClass

    -jobid=<job_id> -class=<class>

    [<general options>]



Command Options:

   -jobid=<job_id>

    is the job ID assigned to the job by the job scheduler. The job

    ID is returned by the lrcmd -cmd=submit command that initially

    submitted the job.

   -class=<class>

    indicates the name of the job class whose information

    is to be returned.



General options:

   To show the general options, use the command: lrcmd -cmd=help



Examples:

   >> ./lrcmd -cmd=getJobLogMetaDataBySizeForClass -jobid=MyApp:1

    -class=Default -port=80 -host=myodrhost.com



   >> ./lrcmd -cmd=getJobLogMetaDataBySizeForClass -jobid=MyApp:1

    -class=Default -port=9080 -host=mygshost.com

    -userid=myname -password=mypassword

CWLRB9931I: lrcmd Command Specific Usage:

Forcibly cancel the execution of a previously-submitted job.

Forced cancel is only supported for Batch and CI jobs running on z/OS

platform. If a forced cancel is issued against a Batch or CI job

running on distributed platform, the forced cancel command will have

the same effect as the cancel command.

Forced cancel command should be used with extreme caution, as it

forcibly terminates the Servant Region JVM in which the job is

running.



   lrcmd -cmd=forcedCancel -jobid=<job_id> [<general options>]



Command Option:

   -jobid=<job_id>

    is the job ID assigned to the job by the job scheduler. The job

    ID is returned by the lrcmd -cmd=submit command that initially

    submitted the job. The -cmd=status command can also be used to

    identify the job ID for a particular job.



General options:

   To show the general options, use following command

    lrcmd -cmd=help



Examples:

   >> ./lrcmd -cmd=forcedCancel -jobid=MyApp:1 -port=80

    -host=myodrhost.com



   >> ./lrcmd -cmd=forcedCancel -jobid=MyApp:1 -port=9080

    -host=mygshost.com -userid=myname -password=mypassword

CWLRB9999I: lrcmd General Usage:

Syntax:



lrcmd

   -cmd=<command>

   [<command options>]

   [<general options>]



Command:

   "command" is one of the following:

    cancel, help, output, purge, remove, restart, resume, save,

    show, status, stop, submit, suspend, forcedCancel

    submitRecurringRequest, modifyRecurringRequest,

    cancelRecurringRequest, showAllRecurringRequests,

    getRecurringRequestDetails, showRecurringJobs,

    getSymbolicVariables, saveJobLog, getJobLog, purgeJobLog,

    getLogMetaData, getLogPartList, getLogPart, getJobsByClass,

    getLogSize, getLogAge



Command options:

   To show the specific command options, use following command

    lrcmd -cmd=<command> -help



General options:

   -host=<host>

    specifies the On Demand Router (ODR) host or the job scheduler

    server host. Default is localhost.

   -port=<port>

    specifies the ODR proxy HTTP address or the job scheduler server

    HTTP port. Default is 80 (default ODR proxy HTTP address)

   -userid=<user_id>

    specifies the user ID required when the job scheduler server is

    running in secure mode.

   -password=<password>

    specifies the password required when the job scheduler server is

    running in secure mode.

   -debug

    results in a stack trace being printed if the command fails.

   -help

    shows the help information.



Examples:

   >> ./lrcmd.sh -cmd=help

   >> ./lrcmd.sh -cmd=submit -help

   >> ./lrcmd.sh -cmd=submit [options...] -host=mygshost.com -port=9080

    -userid=myname -password=mypassword



Note:

   Use the lrcmd.bat file for a Windows system, the lrcmd file for an

   IBM i system, and the lrcmd.sh file for an operating system such as

   AIX or Linux.