Shai Hess z/OS

MFNetDisk Modernization Guide

DiskEmulationTape

MFNetDisk is a disk product by Shai Hess. Explore technical details, modernization strategies, and migration paths below.

Product Overview

MFNetDisk emulates mainframe disk and tape devices (specifically 3380/3390 disks and 3490 tapes) on a PC, enabling a PC to function as a virtual mainframe storage system.

This reduces mainframe MIPS consumption and simplifies data access.

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 MFNetDisk do?

MFNetDisk emulates mainframe disk and tape devices on a PC, allowing the PC to act as a virtual mainframe storage system. It uses TCP/IP to communicate between the mainframe and the PC. The PC software can also read mainframe datasets directly, without mainframe processing.

Is this a system, application, or tool?

MFNetDisk is a system that provides disk and tape emulation. It presents itself as physical devices to the mainframe, while the actual storage resides on the PC.

What types of organizations use this?

Organizations that rely on mainframe systems and need to modernize their storage infrastructure or reduce mainframe processing costs can benefit from MFNetDisk. This includes companies in banking, insurance, and government sectors.

When should we consider MFNetDisk?

Consider MFNetDisk when you need to replace aging mainframe disk or tape hardware, reduce mainframe MIPS consumption, or provide easier access to mainframe data from a PC environment.

Technical

What infrastructure is required?

MFNetDisk requires a TCP/IP network connection between the mainframe and the PC. The mainframe must be able to communicate with the PC using standard TCP/IP protocols. The PC requires sufficient disk space to emulate the mainframe storage.

For mainframe products: Does this run in an LPAR?

MFNetDisk runs on a PC, while the mainframe component interacts with z/OS. It does not require specific z/OS subsystems but needs TCP/IP connectivity.

What mainframe devices does it emulate?

MFNetDisk emulates 3380/3390 disk and 3490 tape devices. These are standard mainframe storage devices.

What operating systems are supported?

The PC component of MFNetDisk typically runs on a Windows operating system. The mainframe component interacts with z/OS through TCP/IP.

Business Value

How does MFNetDisk provide business value?

MFNetDisk reduces mainframe MIPS consumption by offloading storage operations to a PC. It also provides easier access to mainframe data from a PC environment, potentially eliminating the need for mainframe-based data extraction processes.

How does it reduce storage costs?

By emulating mainframe storage on a PC, MFNetDisk can significantly reduce the cost of mainframe storage hardware and maintenance. It also allows for more flexible and scalable storage options.

What are the alternatives to MFNetDisk?

Alternatives include other mainframe disk and tape virtualization solutions, as well as traditional mainframe storage hardware. Consider the specific requirements of your environment when evaluating alternatives.

Security

How does MFNetDisk address security concerns?

MFNetDisk leverages standard TCP/IP protocols for communication, which can be secured using standard network security measures. Access to mainframe datasets is controlled through the MFNetDisk software.

What authentication methods are supported?

MFNetDisk can be configured to use various authentication methods for accessing mainframe datasets. The specific methods supported depend on the configuration of the MFNetDisk software and the mainframe environment.

What audit/logging capabilities exist?

Audit logging capabilities exist within the MFNetDisk software to track access to mainframe datasets and other system events. These logs can be used for security monitoring and compliance purposes.

Operations

How is MFNetDisk typically deployed?

MFNetDisk is typically deployed on-premise, with the PC component residing within the organization's network. Implementing MFNetDisk requires technical expertise in both mainframe and PC environments.

What ongoing operational requirements exist?

Ongoing operational requirements include monitoring the health and performance of the MFNetDisk software, as well as maintaining the network connection between the mainframe and the PC. Regular backups of the emulated storage are also recommended.

What are common implementation challenges?

Common implementation challenges include configuring the network connection between the mainframe and the PC, ensuring compatibility between the MFNetDisk software and the mainframe environment, and migrating data from existing mainframe storage to the emulated storage.

Ready to Start Your Migration?

Download our comprehensive migration guide for MFNetDisk or calculate your ROI.

Calculate ROI