DSI Document Systems z/OS

VSAM-Direct Modernization Guide

Files and Datasets (VSAM)Legacy Application/Data Access

VSAM-Direct is a files and datasets (vsam) product by DSI Document Systems. Explore technical details, modernization strategies, and migration paths below.

Product Overview

VSAM-Direct is a middleware solution that provides a gateway for accessing VSAM data on z/OS systems.

VSAM-Direct is deployed on-premise and requires some technical expertise to configure network connectivity and security policies.

Modernization Strategies

Rehost

Timeline:
6-12 months

Lift-and-shift to cloud infrastructure with minimal code changes. Fast migration with lower risk.

Refactor (Recommended)

Timeline:
18-24 months

Optimize application architecture for cloud while preserving business logic. Best ROI long-term.

Replatform

Timeline:
3-5 years

Complete rewrite to cloud-native architecture with microservices and modern tech stack.

Frequently Asked Questions

General

What does VSAM-Direct do?

VSAM-Direct provides a gateway for applications to access VSAM data using standard protocols like TCP/IP, HTTP, XML, SOAP, and WSDL. It enables modern applications to interact with legacy VSAM data without requiring direct VSAM knowledge.

Is this a system, application, or tool?

VSAM-Direct is middleware. It sits between applications and VSAM data, translating requests and responses between different protocols and data formats.

What types of organizations use this?

Organizations that rely on VSAM data on z/OS and need to integrate this data with modern applications are ideal candidates. This includes enterprises in banking, insurance, retail, and government.

When should we consider VSAM-Direct?

Consider VSAM-Direct when you need to expose VSAM data to web services, modern applications, or distributed systems. It simplifies integration and reduces the need for specialized VSAM programming skills.

What are the alternatives to VSAM-Direct?

Alternatives include direct VSAM programming, custom-built integration solutions, or other VSAM access gateways. Direct programming requires specialized skills, while custom solutions can be costly to develop and maintain.

Technical

For mainframe products: Does this run in an LPAR?

VSAM-Direct runs on z/OS. It typically operates within an LPAR and relies on z/OS subsystems for resource management and security.

What infrastructure is required?

VSAM-Direct requires a TCP/IP stack for network communication. It also needs access to the VSAM datasets it will be serving. The specific requirements depend on the chosen protocols (HTTP, XML, SOAP, WSDL).

How does VSAM-Direct expose VSAM data?

VSAM-Direct exposes APIs using protocols like HTTP, XML, SOAP, and WSDL. Applications can send requests to VSAM-Direct using these protocols, and VSAM-Direct translates the requests into VSAM operations.

What are the main system components?

The main components include the listener, which accepts incoming requests; the translator, which converts requests to VSAM operations; and the data handler, which interacts with VSAM datasets.

Business Value

What is the business value of VSAM-Direct?

VSAM-Direct enables organizations to leverage their existing VSAM data assets in modern applications and architectures. This reduces the need for costly data migration or application rewrite projects.

How does VSAM-Direct simplify application development?

By providing a standard interface to VSAM data, VSAM-Direct simplifies application development and reduces the learning curve for developers who are not familiar with VSAM.

Does VSAM-Direct improve application performance?

VSAM-Direct can improve application performance by optimizing VSAM data access and reducing network latency. It also provides caching and other performance-enhancing features.

Security

What authentication methods are supported?

VSAM-Direct supports authentication methods such as LDAP, RACF, and Kerberos. It integrates with existing security systems to ensure that only authorized users can access VSAM data.

How does VSAM-Direct control access to VSAM data?

VSAM-Direct uses an access control model based on roles and permissions. Administrators can define roles and assign permissions to users or groups, controlling access to specific VSAM datasets and operations.

What encryption is used and where?

VSAM-Direct encrypts data in transit using SSL/TLS. It also supports encryption at rest using VSAM encryption features.

What audit/logging capabilities exist?

VSAM-Direct provides audit logging capabilities that track all access to VSAM data. These logs can be used for security monitoring and compliance purposes.

Operations

How is VSAM-Direct typically deployed?

VSAM-Direct is typically deployed on-premise, within the z/OS environment. It requires technical expertise in z/OS, VSAM, and networking.

What ongoing operational requirements exist?

Ongoing operational requirements include monitoring system performance, managing user access, and maintaining the VSAM datasets. Regular maintenance is required to ensure the system remains secure and reliable.

What are common implementation challenges?

Common implementation challenges include configuring network connectivity, setting up security policies, and optimizing VSAM data access. Thorough planning and testing are essential for a successful implementation.

Ready to Start Your Migration?

Download our comprehensive migration guide for VSAM-Direct or calculate your ROI.

Calculate ROI