Mainframe, MVS and zOS Discussion

Hi,

For one of the application which we support, I have observed that there is a transaction that goes in a 'dead state' every now and then  because one file or other, needed by the program, are in use by a batch program. Without having a monitoring tool on my disposal, can we identify which file is in contention at the moment? Please help.

The simplest answer is to find out from the person who closed / disabled the CICS file.  Depending on the site, there may be a message in the MSGUSR log for the CICS region -- but if your site uses MRO, the message would appear in the FOR, not the TOR.

Robert Sample wrote:The simplest answer is to find out from the person who closed / disabled the CICS file.  Depending on the site, there may be a message in the MSGUSR log for the CICS region -- but if your site uses MRO, the message would appear in the FOR, not the TOR.

Thanks for the reply Robert. I do not have much knowledge about FOR and TOR but I shall do research around them now.

I do not have much knowledge about FOR and TOR but I shall do research around them now.

I Googled cics mro and got back 27,100 hits.  Several of the links on the first page have tutorials on MRO so they would be a good place to start.

, yes there are many links. I might get back with some questions.

If you have questions, post them -- more likely than not, we'll be able to answer them (but sometimes the answer depends upon the site specifics, in which case all we can do is refer you to your site support group).