DMS/CMS Modernization Guide
DMS/CMS is a tools and utilities product by IBM. Explore technical details, modernization strategies, and migration paths below.
Product Overview
DMS/CMS is a toolset designed for creating and displaying panels within the CMS environment on the z/VM operating system.
It integrates with the CMS environment, allowing applications to access CMS files and commands.
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 DMS/CMS do?
DMS/CMS is a tool for creating and displaying panels within the CMS environment on z/VM. It allows developers to design user interfaces and present information to users in a structured manner. It simplifies the process of building interactive applications on the CMS platform.
Is this a system, application, or tool?
DMS/CMS is primarily a toolset for application development. It provides the necessary commands and interfaces to design, create, and display panels. It is not a complete system or application on its own, but rather a utility that enhances the capabilities of the CMS environment.
What types of organizations use this?
Organizations that rely on the z/VM operating system and the CMS environment for application development can benefit from DMS/CMS. This includes enterprises in industries such as finance, insurance, and government that have a significant investment in mainframe technology. Any organization needing to create interactive, panel-based applications on CMS would find it useful.
When should we consider DMS/CMS?
A company should consider using DMS/CMS when they need to develop or maintain applications that require a panel-based user interface within the CMS environment. If the organization is already using CMS and needs a more efficient way to design and display panels, DMS/CMS can provide significant productivity gains.
What are the alternatives to DMS/CMS?
Alternatives to DMS/CMS include other panel management tools or custom-built solutions. Some organizations might opt to use more modern web-based technologies for new applications, but DMS/CMS remains relevant for maintaining existing CMS-based systems. Other tools might offer similar panel creation capabilities, but DMS/CMS is specifically designed for the CMS environment.
Technical
What infrastructure is required?
DMS/CMS requires the z/VM operating system and the CMS environment. It operates within the CMS environment and utilizes its file system and command processing capabilities. No specific subsystems are required beyond the standard CMS environment.
For mainframe products: Does this run in an LPAR?
DMS/CMS runs within a z/VM LPAR (Logical Partition). It is not directly dependent on z/OS, as it operates within the CMS environment provided by z/VM. It leverages the resources and services available within the z/VM environment.
What are some common commands?
Common commands include PANEL to define panel layouts, DISPLAY to show panels to users, and various CMS commands for file management and program execution. The exact syntax depends on the specific version of DMS/CMS being used. Configuration is typically done through CMS files.
What configuration files or interfaces are used?
DMS/CMS primarily uses CMS files for configuration and panel definitions. These files contain the layout and attributes of the panels. The interfaces are command-line based, using CMS commands to interact with DMS/CMS functions.
Business Value
What is the business value of DMS/CMS?
DMS/CMS provides a way to create user interfaces for applications running in the CMS environment. By using DMS/CMS, organizations can develop more user-friendly and interactive applications, which can improve user productivity and satisfaction. It streamlines the development process for panel-based applications.
What happens if an organization does not use DMS/CMS?
Without DMS/CMS, organizations would need to rely on more manual and time-consuming methods for creating and displaying panels. This could involve writing custom code or using less efficient tools. DMS/CMS provides a structured and streamlined approach, reducing development time and improving the maintainability of applications.
How does DMS/CMS integrate with other systems?
DMS/CMS integrates with the CMS environment, allowing applications to access CMS files, commands, and services. It can be used in conjunction with other CMS-based tools and utilities to build complete applications. It leverages the existing CMS infrastructure.
Security
How does DMS/CMS handle security?
DMS/CMS leverages the security features of the underlying z/VM and CMS environments. Access to panels and data is controlled through CMS security mechanisms. Specific authentication methods depend on the CMS configuration.
What access control model is used?
The access control model used by DMS/CMS is based on the CMS security mechanisms. This typically involves user IDs, passwords, and file permissions. Access to specific panels and data can be restricted based on user roles and privileges.
What audit/logging capabilities exist?
DMS/CMS relies on the audit and logging capabilities of the CMS environment. Events related to panel access and modification can be logged and monitored. The specific logging capabilities depend on the CMS configuration.
Operations
What are common implementation challenges?
Implementing DMS/CMS requires expertise in z/VM and the CMS environment. The implementation process involves installing the DMS/CMS software, configuring the CMS environment, and developing the panel definitions. Common challenges include ensuring compatibility with existing CMS applications and managing user access.
What ongoing operational requirements exist?
Ongoing operational requirements include monitoring the performance of DMS/CMS, maintaining the CMS environment, and managing user access. Regular maintenance is required to ensure the stability and security of the system. Staffing requirements depend on the size and complexity of the CMS environment.
What administrative interfaces are available?
Administrative interfaces are command-line based, using CMS commands to manage DMS/CMS functions. User management is handled through CMS user administration tools. Configuration parameters are stored in CMS files.
Ready to Start Your Migration?
Download our comprehensive migration guide for DMS/CMS or calculate your ROI.