SMS Workbench Modernization Guide
SMS Workbench is a disk product by Interchip. Explore technical details, modernization strategies, and migration paths below.
Product Overview
SMS Workbench is a development environment designed to simplify the creation and management of SMS Automatic Class Selection (ACS) routines on z/OS mainframe systems.
It requires a good understanding of z/OS storage management concepts and SMS ACS routines.
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 SMS Workbench do?
SMS Workbench is a development environment designed to aid in the creation and management of SMS Automatic Class Selection (ACS) routines on z/OS mainframe systems. It provides tools and interfaces to simplify the process of defining storage classes, management classes, and data classes, which are essential for automated storage management. The product helps optimize storage utilization and enforce storage policies.
Is this a system, application, or tool?
SMS Workbench is primarily a toolset designed to enhance the development and management of SMS ACS routines. It is not a complete system or application in itself, but rather a set of utilities that integrate with the z/OS storage management subsystem. It provides a framework for creating, testing, and deploying ACS routines.
What types of organizations use this?
Organizations that rely on z/OS mainframe systems for critical data processing and storage management are the primary users of SMS Workbench. These typically include large enterprises in industries such as banking, finance, insurance, and government. Any organization that needs to automate and optimize its storage management policies on z/OS can benefit from this product.
When should we consider SMS Workbench?
A company should consider using SMS Workbench when they need to streamline the development and maintenance of their SMS ACS routines. This is particularly relevant when dealing with complex storage requirements, evolving business needs, or the need to enforce consistent storage policies across the enterprise. It is also useful when organizations want to reduce the risk of errors in ACS routine development.
What are the alternatives to SMS Workbench?
Alternatives to SMS Workbench include manual coding and testing of ACS routines, or using other third-party tools that provide similar functionality. Some organizations may also develop their own in-house tools for managing ACS routines. Competing products include BMC AMI Storage solutions and other storage management tools available for z/OS.
Technical
For mainframe products: Does this run in an LPAR?
SMS Workbench runs on the z/OS platform and requires access to the SMS subsystem. It typically operates within an LPAR (Logical Partition) on the mainframe. It needs the base z/OS operating system and the SMS component to be functional.
Does this extend/enhance another product?
SMS Workbench enhances the existing SMS functionality within z/OS. It does not replace SMS but provides a more user-friendly and efficient environment for developing and managing ACS routines. It requires SMS to be active and configured correctly.
How is this product typically deployed?
SMS Workbench is deployed on-premise, within the z/OS environment. It is not a cloud-based or SaaS solution. The software is installed on the mainframe system and accessed through ISPF panels or other z/OS interfaces.
What level of technical expertise is required to implement it?
Implementing SMS Workbench requires a good understanding of z/OS storage management concepts and SMS ACS routines. System programmers and storage administrators are typically responsible for installing, configuring, and using the product. Familiarity with ISPF and JCL is also beneficial.
Business Value
What business problem does it solve?
SMS Workbench helps organizations optimize their storage utilization, reduce manual effort in managing storage policies, and improve the consistency and accuracy of ACS routines. By automating storage management tasks, it can lead to cost savings and improved operational efficiency. It also reduces the risk of human errors in storage configuration.
What would happen if an organization did NOT use this product?
If an organization does not use SMS Workbench or a similar tool, they would likely rely on manual coding and testing of ACS routines, which can be time-consuming and error-prone. This can lead to inconsistent storage policies, inefficient storage utilization, and increased operational costs. It also increases the risk of data placement errors.
What existing infrastructure or systems does it require?
SMS Workbench integrates with the z/OS storage management subsystem, including DFSMS and related components. It also interacts with security systems like RACF, ACF2, or Top Secret for access control and auditing. It can integrate with other monitoring and reporting tools for storage performance analysis.
Security
What specific authentication methods are supported?
SMS Workbench leverages the security features of z/OS, including RACF, ACF2, and Top Secret, for authentication and authorization. Access to the product's functions and data is controlled through these security systems. It supports role-based access control (RBAC) to restrict access based on user roles.
What access control model is used?
The access control model used by SMS Workbench is primarily role-based access control (RBAC). Users are assigned roles that determine their level of access to different functions and data within the product. This allows administrators to manage user permissions efficiently.
What audit/logging capabilities exist?
SMS Workbench integrates with z/OS security systems to provide audit and logging capabilities. All actions performed within the product are logged, including user logins, configuration changes, and ACS routine modifications. These logs can be used for security auditing and compliance purposes.
Operations
What ongoing operational requirements exist?
Ongoing operational requirements for SMS Workbench include monitoring the product's performance, maintaining the underlying z/OS system, and ensuring the security of the environment. Regular backups of the SMS configuration and ACS routines are also essential. Staffing requirements include system programmers and storage administrators.
What administrative interfaces are available?
Administrative interfaces for SMS Workbench typically include ISPF panels and command-line interfaces (CLIs) within the z/OS environment. These interfaces allow administrators to configure the product, manage users, and monitor its performance. The specific interfaces may vary depending on the product version.
How is user management handled?
User management in SMS Workbench is typically handled through the z/OS security system (RACF, ACF2, or Top Secret). User accounts and permissions are defined within these systems, and SMS Workbench integrates with them to authenticate and authorize users. The product itself may provide additional user management features.
Ready to Start Your Migration?
Download our comprehensive migration guide for SMS Workbench or calculate your ROI.