SYSM Modernization Guide
SYSM is a email product by H&W Computer Systems. Explore technical details, modernization strategies, and migration paths below.
Product Overview
SYSM is an application that brings email and calendar functionality into the CICS environment.
Organizations that rely on CICS for transaction processing and want to integrate email and calendar functions should consider SYSM.
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 SYSM do?
SYSM provides email and calendar functionality within a CICS environment. It also includes support for electronic forms using SYSM Smart E-forms, enabling users to manage communications and workflows directly from their CICS terminals.
Is this a system, application, or tool?
SYSM is an application that extends the capabilities of CICS to include email and calendar functions. It provides a user interface and set of tools for managing email, scheduling appointments, and creating and processing electronic forms.
What types of organizations use this?
Organizations that rely heavily on CICS for transaction processing and want to integrate email and calendar functionality directly into their CICS environment would benefit from SYSM. This includes businesses in finance, insurance, and retail that use CICS for core operations.
When should we consider SYSM?
A company should consider SYSM when they need to provide email and calendar access to users working within a CICS environment. It is particularly useful when integrating email-based workflows with existing CICS applications and data.
What are the alternatives to SYSM?
Alternatives to SYSM include other CICS-based email solutions or integrating CICS with external email systems using custom programming. Organizations could also migrate CICS applications to more modern platforms with built-in email capabilities.
Technical
What infrastructure is required?
SYSM requires a z/OS environment with CICS Transaction Server. It integrates directly with CICS resources and uses CICS facilities for transaction management and security.
For mainframe products: Does this run in an LPAR?
SYSM runs within a z/OS LPAR and is dependent on the CICS subsystem. It utilizes CICS APIs and services for its core functionality.
What databases are used?
SYSM likely uses VSAM datasets or DB2 tables for storing email messages, calendar entries, and form definitions. The specific database depends on the configuration and version of SYSM.
How does SYSM handle security?
SYSM integrates with CICS security to control access to email and calendar functions. It likely supports RACF or other z/OS security managers for user authentication and authorization.
Business Value
What is the business value of SYSM?
SYSM provides email and calendar functionality within the CICS environment, reducing the need for users to switch between different systems. The Smart E-forms feature streamlines data collection and processing, improving efficiency.
How does SYSM improve efficiency?
By integrating email and forms processing within CICS, SYSM can improve data accuracy and reduce manual effort. This can lead to faster turnaround times and better customer service.
Does SYSM help with compliance?
SYSM can help organizations maintain compliance with data retention policies by storing email and form data within the CICS environment, where it can be managed and audited according to established procedures.
Security
How does SYSM handle authentication?
SYSM leverages CICS security features for authentication, typically supporting RACF, ACF2, or Top Secret. Access to specific functions and data is controlled through CICS resource definitions and security profiles.
What access control model is used?
SYSM uses an access control model based on CICS resource security. Access to transactions, programs, and datasets is controlled through CICS security definitions, which can be tailored to specific user roles and responsibilities.
What audit/logging capabilities exist?
SYSM's audit and logging capabilities are integrated with CICS. Security events and transaction activity are logged to CICS system logs, which can be analyzed for security monitoring and compliance purposes.
Operations
How is SYSM deployed?
SYSM is typically deployed on-premise within a z/OS environment. It requires experienced CICS systems programmers for installation, configuration, and ongoing maintenance.
What are the ongoing operational requirements?
Ongoing operational requirements include monitoring CICS regions for SYSM-related errors, managing user access and security profiles, and performing regular backups of SYSM data.
What are common implementation challenges?
Common implementation challenges include integrating SYSM with existing CICS applications, configuring security settings to meet organizational requirements, and ensuring adequate performance within the CICS environment.
Ready to Start Your Migration?
Download our comprehensive migration guide for SYSM or calculate your ROI.