TWSeasy Modernization Guide
TWSeasy is a tools and utilities product by APS ENTERprise. Explore technical details, modernization strategies, and migration paths below.
Product Overview
TWSeasy is a set of tools and utilities designed to enhance Tivoli Workload Scheduler (TWS) environments on z/OS mainframes.
The application definition and planning tools simplify the process of defining and scheduling jobs.
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 TWSeasy do?
TWSeasy is a set of tools and utilities designed to enhance the functionality of Tivoli Workload Scheduler (TWS) on z/OS. It provides capabilities for database management, application definition, job scheduling, and JCL simulation with variable substitution. The tools aim to simplify and automate TWS-related tasks.
Is this a system, application, or tool?
TWSeasy is a tool set designed to extend and simplify the use of Tivoli Workload Scheduler. It provides utilities for managing the TWS database, defining applications, scheduling jobs, and simulating JCL with TWS variables. It is not a standalone system or application, but rather a collection of tools that enhance an existing TWS environment.
What types of organizations use this?
Organizations that rely on Tivoli Workload Scheduler for batch processing and job scheduling on z/OS mainframes are the typical users. This includes enterprises in industries such as banking, finance, insurance, and retail that require robust and automated workload management.
When should we consider TWSeasy?
A company should consider using TWSeasy when they need to streamline TWS database management, simplify application definition and job scheduling, or improve the accuracy of JCL execution through variable simulation. It is particularly useful when dealing with mass changes or deletions in the TWS database.
What are the alternatives to TWSeasy?
Alternatives to TWSeasy include other TWS enhancement tools or custom-developed scripts and utilities. Some organizations may also consider upgrading to newer workload automation platforms that offer similar functionality. Specific competing products include VISUALjob EPD, Rocket OpsCentral, and Workload Planner.
Technical
What infrastructure is required?
TWSeasy requires an existing Tivoli Workload Scheduler (TWS) environment running on z/OS. It leverages TWS infrastructure and databases. It also requires access to z/OS datasets and JCL libraries.
For mainframe products: Does this run in an LPAR?
Yes, TWSeasy is z/OS dependent and runs within an LPAR on a mainframe system. It interacts directly with z/OS datasets and requires access to TWS subsystems.
Does this extend/enhance another product?
TWSeasy extends the functionality of Tivoli Workload Scheduler (TWS) by providing tools for database management, application definition, and JCL simulation. It enhances TWS capabilities and simplifies common tasks.
Business Value
How does TWSeasy provide business value?
TWSeasy simplifies TWS database management by providing tools to load and unload the database to/from sequential datasets, enabling mass changes and deletions. It also streamlines application definition and job scheduling processes. The JCL simulation feature helps to reduce errors and improve job execution.
What would happen if an organization did NOT use this product?
Without TWSeasy, organizations may face challenges in efficiently managing the TWS database, defining applications, and scheduling jobs. Mass changes and deletions in the TWS database may become cumbersome and error-prone. JCL errors may lead to job failures and delays.
Security
How does TWSeasy handle security?
TWSeasy leverages the security features of z/OS and Tivoli Workload Scheduler. Access to TWSeasy functions and data is controlled through z/OS security mechanisms, such as RACF or ACF2. Specific authentication methods depend on the z/OS security configuration.
What access control model is used?
TWSeasy integrates with z/OS security systems like RACF or ACF2 to control access to its functions and data. The access control model is typically based on assigning users or groups to specific roles or permissions within the z/OS environment.
Operations
How is TWSeasy typically deployed?
TWSeasy is typically deployed on-premise, within the z/OS environment where Tivoli Workload Scheduler is running. It requires technical expertise in z/OS, TWS, and JCL. Ongoing operational requirements include monitoring job execution, maintaining the TWS database, and applying updates to TWSeasy.
What level of technical expertise is required to implement it?
Implementing TWSeasy requires expertise in z/OS, Tivoli Workload Scheduler, and JCL. Common challenges include configuring TWSeasy to work with the existing TWS environment, ensuring proper security settings, and training users on the new tools and utilities.
What ongoing operational requirements exist?
Ongoing operational requirements for TWSeasy include monitoring job execution, maintaining the TWS database, applying updates to TWSeasy, and providing user support. Regular backups of the TWS database are also essential.
Ready to Start Your Migration?
Download our comprehensive migration guide for TWSeasy or calculate your ROI.