jsr352

When a job is restarted, only the failed partitions are run again. How do i run a successfully completed job again? Is there a difference between submitting a job again and restarting the job? i am using IBM's implementation of JSR 352 on Websphere Liberty. Java Batch is designed so that when you restart a job instance, execution continues where you left off (in the previous failed or stopped execution). So typically this means two things: Within the job, you begin at the previously-failing step (or the step at which the job was stopped). Within the step, you begin by positioning the input

I have 10 records in my source table and I am having item count as 3. I have 2 partitions to process these 10 records(i.e first 5 records will be processed in first partition and remaining records processed in 2nd partition while processing records in 2nd partition I am throwing an exception so job will be failed at 2nd chunk of 2nd partition.when I am restarting the job ,failed partition is processing all the records again(that is first chunk and 2nd chunk). Restarting the job should only process from last failed chunk records but not all the records in that partition.Can you please guide me

I am reading data from DB2 table and dumping it into a file. I execute my simple select query in the chunk listener's beforeChunk() and use the step context to get it in itemreader. In the chunk i set the checkpoint policy as item and itemcount as 5. The output is the first 5 records being read and written over and over again. In this sample java batch code from IBM's site they have start and end parameters in the query. Is it necessary to have start and end parameters in your query? Is there no other way to make sure that when the query is run again it reads the next chunk of data and not the