CoreTrouble
Batch fails because CICS holds the file
A batch job cannot open a VSAM file because a CICS region has it open for update.
Why it happens
A VSAM file open for update in CICS normally cannot also be updated by a batch job. This is the reason batch windows and file-close schedules exist.
Options, in order of preference
- Wait — is the job simply running outside its window? Check the schedule first.
- Close the file in CICS with CEMT SET FILE(name) CLOSED, following your site's procedure and approvals, then reopen after the batch step.
- Check whether the close should have been automated as part of the schedule and is missing.
- Where both genuinely need concurrent update, the site-level answer is VSAM record-level sharing (RLS).
Stuck on something else?
Ask the community or search the full course.