In the example MultiResourceItemReader job, the resource pattern is hard coded in the job configuration (see multiResourceJob.xml). There should be a way to pass the resource pattern as a JobParameter. A solution could be something similar to StepExecutionResourceProxy. Also, the job should have a way to gracefully exit if the pattern returns an empty array of resource, i.e., the job should just return a success status with 0 item count in the job metadata. This is to cover a use case where it is acceptable for a scheduled job run to have an empty list of files to process.