Lozen, Record Level Sharing (RLS), and Transactional VSAM (TVS)

In a prior blog, we discussed how we designed Lozen™ to leverage the robust data integrity options provided by VSAM on the mainframe.  With Lozen, you have the identical levels of access and integrity you would have if your application were running natively on z/OS.  This includes support for Record Level Sharing (RLS) and Transactional VSAM (TVS), which we cover in more detail here.

VSAM RLS provides concurrent read-write access, but it does not include transactional recovery (commit/rollback) like CICS.  Because of this, customers sharing VSAM RLS files with CICS systems will tend to limit non-CICS applications to read-only access.  In most configurations, when updates need to occur, the files would either be marked “read only” to CICS or put offline to CICS.  Lozen operates under these same rules.

If a higher degree of integrity is required, the typical solution would be to leverage “Transactional VSAM” (TVS), which provides full transactional logging and capabilities that make it practical to have read-write sharing with CICS systems within a sysplex.

The caveat is that applications not designed around any type of transaction processing may need to be reviewed to ensure they are not inadvertently retaining record locks.  TVS normally locks records from the time they are accessed until either the file is closed or until the application issues a COMMIT (or rollback).  Applications updating many records may thus retain record locks for a lengthy amount of time until the file is closed.

To help with this, Lozen has an optional capability that can automatically commit record updates on VSAM TVS files, if desired. When this option is set, Lozen automatically commits record updates (thus releasing any retained record locks) after every “n” updates, where “n” is a customer-selected record count that can be any arbitrary number from 1 (that is, commit after every update) to some larger number.

Applications can also be upgraded to include a more intelligent transaction management approach, but such an approach would require application changes.

Summary

Lozen is VirtualZ Computing’s revolutionary solution that unlocks the power of real-time, read-write data access — from any platform, anytime, anywhere.

By design, Lozen leverages the robust data integrity options provided by VSAM on the mainframe, including support for RLS and TVS.

Learn More

To learn more about how to unlock the power of real-time, read-write IBM zSystems data access with Lozen:

Latest Blog Posts

Deploying Lozen in a Sysplex

Deploying Lozen in a Sysplex

Designed with flexibility in mind, Lozen™ can be deployed in a variety of ways to suit your needs — including in a sysplex to provide load balancing and fault tolerance. There are several possible approaches to this, depending on the degree of fault tolerance you are...

Lozen + MuleSoft: A Powerful Combination

Lozen + MuleSoft: A Powerful Combination

MuleSoft is one of the most popular integration platforms available, with thousands of customers worldwide. In this blog, we describe the features and benefits of the Lozen™ MuleSoft Connector, which provides no-code access to mainframe data from within MuleSoft’s...

Zaac Use Cases

Zaac Use Cases

Zaac is coming soon! When we talk with customers about Lozen, they often ask, “Do you also have the reverse? A solution that allows my applications on the mainframe to consume data residing in Amazon S3, Dell, or other storage devices?” The answer is YES! Today, your...