IBM z/VM

VM Pass-Through Facility Modernization Guide

3270Sharing

VM Pass-Through Facility is a 3270 product by IBM. Explore technical details, modernization strategies, and migration paths below.

Product Overview

VM Pass-Through Facility is a system that enables users on a z/VM system to access other mainframe systems, such as z/OS, z/VSE, and other z/VM instances, from their existing VM session.

It requires a z/VM environment and SNA connectivity to the target systems.

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 VM Pass-Through Facility do?

VM Pass-Through Facility allows users on a z/VM system to access other systems, such as z/OS, z/VSE, and other z/VM systems, from their VM session. It essentially provides a terminal emulation capability, enabling users to interact with multiple systems without needing separate terminals or sessions. The target system requires an SNA connection.

Is this a system, application, or tool?

VM Pass-Through Facility is a system that provides terminal emulation and session management capabilities. It is not merely an application or a simple tool, but a more comprehensive system that facilitates connectivity between different mainframe environments.

What types of organizations use this?

Organizations that rely on multiple mainframe systems, particularly those running z/VM, z/OS, and z/VSE, are prime candidates for VM Pass-Through Facility. These organizations typically need to provide users with seamless access to different environments for application development, testing, or production support. Industries such as banking, finance, insurance, and government often utilize such systems.

When should we consider VM Pass-Through Facility?

A company should consider VM Pass-Through Facility when they need to consolidate terminal access to multiple mainframe systems, streamline user workflows, and reduce the overhead associated with managing separate terminal sessions. It is particularly useful when users frequently switch between different mainframe environments.

What are the alternatives to VM Pass-Through Facility?

Alternatives to VM Pass-Through Facility include other terminal emulation products, session management tools, and potentially newer solutions that leverage TCP/IP-based connectivity instead of SNA. Examples include CL/Supersession, Multiterm/MVS, and InterSession. The specific choice depends on the organization's existing infrastructure and requirements.

Technical

What infrastructure is required?

VM Pass-Through Facility requires a z/VM environment and SNA connectivity to the target systems (z/OS, z/VSE, other z/VM). It operates within the z/VM environment and does not have specific dependencies on z/OS subsystems beyond the need for SNA connectivity. The target systems must be configured to accept SNA connections.

For mainframe products: Does this run in an LPAR?

VM Pass-Through Facility runs within a z/VM LPAR (Logical Partition). It leverages the z/VM operating system's capabilities for managing virtual machines and providing connectivity. It does not require specific z/OS subsystems, but relies on SNA for communication with target systems.

What are the most common commands/operations?

The most common operations involve establishing a connection to a target system, interacting with applications on that system, and disconnecting from the target system. Specific commands would depend on the version of VM Pass-Through Facility and the configuration, but generally involve specifying the target system's SNA LU name.

What protocols does it use for communication?

VM Pass-Through Facility relies on SNA protocols for communication. It uses LU (Logical Unit) names to identify and connect to target systems. The specific configuration files and interfaces used would depend on the version and the z/VM environment.

Business Value

What business problem does it solve?

VM Pass-Through Facility solves the business problem of providing users with seamless access to multiple mainframe systems from a single z/VM session. Without it, users would need separate terminals or sessions for each system, increasing complexity and reducing productivity.

What would happen if an organization did NOT use this product?

If an organization did not use VM Pass-Through Facility (or a similar product), users would face increased complexity in accessing multiple mainframe systems. This could lead to reduced productivity, increased training costs, and a less efficient workflow. Managing multiple terminals or sessions can be cumbersome and error-prone.

What is the primary business value?

The primary business value of VM Pass-Through Facility is increased user productivity and simplified access to multiple mainframe systems. By providing a single point of access, it reduces the time and effort required to switch between different environments. This can lead to significant cost savings and improved operational efficiency.

Security

How is security handled?

Security in VM Pass-Through Facility is typically handled through SNA security mechanisms and z/VM security features. Authentication methods would depend on the configuration of both the z/VM environment and the target systems. Access control is generally managed through z/VM user profiles and SNA LU assignments.

What access control model is used?

VM Pass-Through Facility leverages the access control model provided by z/VM and SNA. Access to target systems is controlled through LU assignments and user profiles within the z/VM environment. The specific model used depends on the configuration of the z/VM system and the SNA network.

What audit/logging capabilities exist?

Auditing and logging capabilities in VM Pass-Through Facility would typically be integrated with the z/VM system's auditing features. Specific events related to connections and disconnections could be logged for security and compliance purposes. The extent of logging depends on the configuration of the z/VM environment.

Operations

How is this product typically deployed?

Deployment of VM Pass-Through Facility typically involves configuring the z/VM environment and defining the SNA connections to the target systems. Ongoing operational requirements include monitoring the connections, managing user access, and ensuring the availability of the z/VM system. Technical expertise in z/VM and SNA is required.

What level of technical expertise is required to implement it?

Implementing VM Pass-Through Facility requires technical expertise in z/VM and SNA networking. Configuring the z/VM environment, defining SNA connections, and managing user access require a solid understanding of mainframe concepts and technologies. Troubleshooting connection issues also requires specialized skills.

What ongoing operational requirements exist?

Ongoing operational requirements include monitoring the availability of the z/VM system and the SNA connections, managing user access and security, and performing regular maintenance on the z/VM environment. Staffing requirements depend on the size and complexity of the mainframe environment.

Ready to Start Your Migration?

Download our comprehensive migration guide for VM Pass-Through Facility or calculate your ROI.

Calculate ROI