MFAST/ES Modernization Guide
MFAST/ES is a tools and utilities product by H&M System Software. Explore technical details, modernization strategies, and migration paths below.
Product Overview
MFAST/ES is a tool designed to streamline CICS application development by simplifying the creation of CICS screens.
Once defined, these screens can be easily incorporated into your CICS applications.
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 MFAST/ES do?
MFAST/ES is a tool that allows developers to create CICS screens without writing BMS (Basic Mapping Support) code. It simplifies the screen definition process, making it faster and easier to develop CICS applications. This tool helps bridge the gap between application logic and the presentation layer in CICS environments.
Is this a system, application, or tool?
MFAST/ES is a toolset designed to streamline CICS application development. It provides a user-friendly interface for designing and creating CICS screens, abstracting away the complexities of BMS coding. By simplifying screen creation, it enhances developer productivity and reduces the time required to build CICS applications.
What types of organizations use this?
Organizations that rely on CICS for their core business applications, particularly those with a need to rapidly develop and deploy new screens or maintain existing ones, would benefit from MFAST/ES. This includes enterprises in industries such as banking, finance, insurance, and retail, where CICS is commonly used for transaction processing and application hosting.
When should we consider MFAST/ES?
A company should consider using MFAST/ES when they need to accelerate CICS application development, reduce the complexity of screen design, and improve developer productivity. If an organization is struggling with the intricacies of BMS coding or needs to quickly create and modify CICS screens, MFAST/ES can provide a streamlined solution.
What are the alternatives to MFAST/ES?
Alternatives to MFAST/ES include other screen definition tools for CICS, such as CICS/Mapr II, Screen Definition Facility II, SCRDEF for VSEn, and Ivory BMS/TS. These tools offer similar functionality for creating CICS screens, but may differ in terms of user interface, features, and integration capabilities.
Technical
What infrastructure is required?
MFAST/ES requires a CICS environment to run. It is designed to operate on z/OS and zVSE/VSEn platforms. The tool integrates with CICS to provide screen definition capabilities. It does not require specific subsystems beyond the standard CICS environment.
For mainframe products: Does this run in an LPAR?
MFAST/ES runs within an LPAR (Logical Partition) on z/OS or zVSE/VSEn. It leverages the CICS subsystem for screen management and application integration. The product enhances the CICS environment by providing a more efficient way to define and create screens.
How is MFAST/ES typically deployed?
MFAST/ES is typically deployed on-premise, within the organization's mainframe environment. It integrates directly with the CICS subsystem. The implementation involves installing the MFAST/ES components and configuring them to work with the existing CICS regions.
How does MFAST/ES integrate with CICS?
MFAST/ES integrates with CICS using standard CICS interfaces. It leverages CICS APIs for screen definition and management. The tool generates CICS-compatible screen definitions that can be used by CICS applications.
Business Value
What is the business value of MFAST/ES?
MFAST/ES reduces the time and effort required to develop CICS screens, leading to faster application development cycles. It simplifies screen maintenance and modification, reducing the cost of application ownership. By improving developer productivity, it allows organizations to deliver CICS applications more efficiently.
What would happen if an organization did NOT use this product?
Without MFAST/ES, organizations would need to rely on manual BMS coding or other screen definition tools, which can be time-consuming and error-prone. This can lead to slower application development, increased costs, and reduced developer productivity. MFAST/ES provides a more efficient and user-friendly alternative.
How does MFAST/ES improve business agility?
MFAST/ES helps organizations streamline their CICS application development processes, allowing them to respond more quickly to changing business requirements. It enables developers to create and modify screens more efficiently, reducing the time required to implement new features and enhancements. This agility can provide a competitive advantage in today's fast-paced business environment.
Security
How does MFAST/ES handle security?
MFAST/ES leverages the security features of the underlying CICS environment. It relies on CICS security mechanisms for user authentication and authorization. Access to MFAST/ES functions and resources can be controlled through CICS security profiles.
What access control model is used?
MFAST/ES integrates with CICS security systems to control access to screen definitions and development functions. It supports role-based access control (RBAC), allowing administrators to assign specific roles and permissions to users. This ensures that only authorized personnel can create, modify, or deploy CICS screens.
What audit/logging capabilities exist?
MFAST/ES relies on the auditing and logging capabilities of the CICS environment. It logs user activity and system events to provide an audit trail of screen definition changes and deployments. These logs can be used to track user actions and identify potential security issues.
Operations
What level of technical expertise is required to implement it?
Implementing MFAST/ES requires technical expertise in CICS and mainframe environments. Administrators need to be familiar with CICS configuration and security settings. Developers need to understand CICS application development principles and screen design concepts.
What ongoing operational requirements exist?
Ongoing operational requirements for MFAST/ES include monitoring system performance, managing user access, and maintaining screen definitions. Regular backups of screen definition libraries are essential to ensure data recovery in case of system failures. Administrators should also monitor CICS logs for any errors or security issues.
What are common implementation challenges?
Common implementation challenges for MFAST/ES include integrating with existing CICS applications, migrating existing BMS code to MFAST/ES format, and ensuring compatibility with different CICS versions. Careful planning and testing are essential to avoid disruptions to existing CICS applications.
Ready to Start Your Migration?
Download our comprehensive migration guide for MFAST/ES or calculate your ROI.