Problem solve Get help with specific problems with your technologies, process and projects.

Reading VSAM data from different LPARs

In this mainframe tip, expert Robert Crawford discusses VSAM file-sharing options across LPARs.

Can we read data from a VSAM file that is on a different LPAR? If so are there any performance related issues?
A VSAM file's share options determine how it can be processed by multiple users. You can provide two numbers on the share option parameter. The first specifies the type of sharing allowed by address spaces on the same LPAR. The second number denotes cross-system sharing.

Share options of (2,3) allow one address space to update the dataset and any number to read it. However, it is the user's responsibility to provide read integrity. Reading without integrity can cause problems with stale data and incomplete pointers.

Share options of (3,4) allow a dataset to be read and written by any number of users. However, it is up to the application to provide read and write integrity using ENQ or RESERVCE macros to serialize access. Not only is this complicated, it's asking for trouble.

You may also be opening yourself up for performance problems if the dataset is heavily used. One "hot" system could keep other LPARs from getting to the file. However, with the new architecture of storage devices and the development of faster channels and parallel access volumes (PAVs), the days of moving datasets off of heavily used volumes are fading fast.

If you intend to share the dataset for read and write you will have to use the serialization techniques mentioned above. This could turn into a performance problem because enqueuing across LPARs is not cheap. You may also get into a situation where a program hangs up while holding the enqueue, thus shutting all the other readers and writers out.


VSAM basics (Oct. 31, 2006)
Virtual Storage Access Method (VSAM) still holds mountains of the world's data sets. This column explains how VSAM works.

CICS-VSAM tuning options
Expert Robert Crawford discusses a user's decreased system performance in relation to its VSAM stats.

Dig Deeper on IBM system z and mainframe systems

Start the conversation

Send me notifications when other members comment.

Please create a username to comment.