Start of change CICS VSAM Transparency for z/OS, Version 1.2


MRO considerations

In a typical MRO environment, the application runs in an AOR and VSAM files are defined as remote files in a separate region such as an FOR. CICS® VT supports access to remote VSAM files but there are operational implications to consider.

CICS VT checks that the file is available for processing. If the file is defined as remote, CICS VT is unable to check the file status and assumes it is available. If you need to be able to disable and enable access to a file that has been migrated, you must define the file in the same region as CICS VT.

There is an unnecessary path length overhead for remotely defined files that are migrated with CICS VT. Consider defining remote files as local to avoid function shipping. Remote files accessed from multiple AORs should be defined as local to each.





Last updated: December 6, 2013 20:43:14

Information Information

Feedback


Timestamp icon Last updated: Friday, 6 December 2013


http://pic.dhe.ibm.com/infocenter/cicsts/v5r1/topic///topics/cvtug_mro_considerations.html
End of change