Production VSAM file on hold and causing prod jobs to fail

[Dicta Mitra]

Hi,

Good Day!

In the recent days, we have come across instances where developers ID holding prod VSAM files and prod jobs had failed.
This is happening while the VSAM files are opened in Fileaid mostly even it was opened in browse mode.

We are asked to close all the tools and logoff from TSO before logging off for the day.

Is this how it works at all the places? If not, what is the way to solve it.

Thanks!

[DB2 Guy]

I am not sure if 'browse by file-aid' creates a Job in background but your system team can set the priorities to cancel anything of this nature for production job execution. This is a pretty common scenario and I've not it happens in shops where I have been to.

[LalitKumar]

In my company, they say that our browse session will be canceled by someone from system

[Robert Sample]

The typical solution is to create test copies of production data sets and have the developers work with the test copies. In our shop, if a developer has a lock on a data set that a production batch job needs, we'll cancel the TSO user id.

[Dicta Mitra]

Is this cancel done manually? Or there is an automation behind it?

[Dicta Mitra]

I came to know that this cancel was done manually.