H&W Computer Systems z/OS

SYSB-II Modernization Guide

Files and Datasets (VSAM)SharingCICS

SYSB-II is a files and datasets (vsam) product by H&W Computer Systems. Explore technical details, modernization strategies, and migration paths below.

Product Overview

SYSB-II is a middleware solution that enables batch programs to access CICS VSAM files while they are in use by CICS.

It requires a z/OS environment with CICS and VSAM.

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 SYSB-II do?

SYSB-II allows batch programs to access CICS Virtual Storage Access Method (VSAM) files while they are actively being used by CICS. This eliminates the need to shut down CICS to perform batch processing, reducing downtime and improving data availability.

Is this a system, application, or tool?

SYSB-II is a middleware solution that sits between batch applications and CICS, facilitating data access and sharing. It provides a mechanism for batch jobs to read and update VSAM files without interfering with CICS operations.

What types of organizations use this?

Organizations that rely heavily on CICS for online transaction processing and also need to perform batch updates to the same VSAM files are ideal candidates for SYSB-II. These organizations are often in industries such as banking, insurance, and retail.

When should we consider SYSB-II?

A company should consider SYSB-II when they experience frequent downtime of CICS files due to batch processing requirements, or when they need to improve the availability of their CICS data for reporting and analysis.

What are the alternatives to SYSB-II?

Alternatives to SYSB-II include other VSAM sharing products like V-Share and DFSMStvs. Some organizations might also consider application program changes to avoid file contention, but this can be a more complex and time-consuming approach.

Technical

What infrastructure is required?

SYSB-II requires a z/OS environment with CICS and VSAM. It typically runs in an LPAR and integrates with existing CICS subsystems. No specific hardware is mandated beyond the standard mainframe environment.

How does SYSB-II work technically?

SYSB-II operates by intercepting VSAM requests from batch programs and coordinating access with CICS. It uses a combination of z/OS system services and its own internal logic to ensure data integrity and prevent conflicts.

How is SYSB-II deployed?

SYSB-II is deployed on-premise within the z/OS environment. It involves installing the SYSB-II components and configuring them to work with the existing CICS regions and VSAM datasets.

Does SYSB-II require changes to application programs?

SYSB-II uses standard VSAM calls and integrates with CICS through its resource definition online (RDO) definitions. It does not require modifications to existing application programs.

Business Value

What is the business value of SYSB-II?

SYSB-II reduces downtime of CICS files, allowing batch processes to run concurrently with online transactions. This improves data availability and reduces the impact of batch processing on CICS users.

How does SYSB-II improve efficiency?

By enabling concurrent access to VSAM files, SYSB-II can improve the efficiency of batch processing and reduce the overall processing time. This can lead to cost savings and improved resource utilization.

How does SYSB-II help meet SLAs?

SYSB-II helps organizations meet service level agreements (SLAs) by ensuring that CICS files are available for online transactions during batch processing windows. This improves customer satisfaction and reduces the risk of penalties for failing to meet SLAs.

Security

How does SYSB-II provide security?

SYSB-II leverages z/OS security features, such as Resource Access Control Facility (RACF), to control access to VSAM files. It integrates with existing security policies and procedures to ensure that only authorized users can access sensitive data.

What audit capabilities exist?

SYSB-II provides audit logging capabilities to track access to VSAM files. This allows organizations to monitor user activity and identify potential security breaches.

What authentication methods are supported?

SYSB-II supports various authentication methods, including RACF passwords and multi-factor authentication, to ensure that only authorized users can access the system.

Operations

What ongoing operational requirements exist?

SYSB-II requires ongoing monitoring to ensure that it is functioning correctly and that VSAM files are being accessed properly. This includes monitoring system logs, performance metrics, and security events.

What maintenance is required?

SYSB-II requires periodic maintenance to apply software updates and security patches. This helps to ensure that the system remains secure and performs optimally.

What level of technical expertise is required?

Implementing SYSB-II typically requires expertise in z/OS, CICS, and VSAM. Organizations may need to train existing staff or hire new staff with the necessary skills.

Ready to Start Your Migration?

Download our comprehensive migration guide for SYSB-II or calculate your ROI.

Calculate ROI