MultSess Modernization Guide
MultSess is a sharing product by Dell Computer Corporation. Explore technical details, modernization strategies, and migration paths below.
Product Overview
MultSess is a 3270 session manager designed for z/OS environments.
It improves user productivity by simplifying session management and reducing the time spent connecting and disconnecting from different systems.
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 MultSess do?
MultSess is a 3270 session manager that allows users to connect to multiple 3270 VTAM applications from a single 3270 session. It simplifies access to different mainframe applications without requiring multiple dedicated sessions.
Is this a system, application, or tool?
MultSess is an application that enhances 3270 terminal access. It provides a way to manage and switch between multiple VTAM applications within a single terminal session, improving user efficiency.
What types of organizations use this?
Organizations that rely on mainframe applications accessed through 3270 terminals can benefit from MultSess. This includes enterprises in industries such as banking, finance, insurance, and government, where multiple mainframe applications are used daily.
When should we consider MultSess?
A company should consider using MultSess when its users need to access multiple 3270 applications frequently and want to avoid the overhead of managing multiple terminal sessions. It is especially useful when users switch between applications regularly.
What are the alternatives to MultSess?
Alternatives to MultSess include CL/Supersession, Multiterm/MVS, and InterSession. These products offer similar functionality for managing multiple 3270 sessions, but may differ in features, performance, and integration capabilities.
Technical
For mainframe products: Does this run in an LPAR?
MultSess runs on the z/OS platform. It is dependent on the VTAM subsystem for managing 3270 terminal connections. It typically runs within an LPAR on the mainframe.
What infrastructure is required?
MultSess requires a z/OS environment with VTAM configured for 3270 terminal access. It also needs sufficient system resources, such as memory and CPU, to handle multiple concurrent sessions.
Does this replace existing 3270 access methods?
MultSess enhances the functionality of existing 3270 terminal access methods. It does not replace them but provides a layer of session management to improve user experience and efficiency.
How is MultSess typically deployed?
MultSess is typically deployed on-premise within the z/OS environment. It requires configuration of VTAM and the MultSess application itself. Implementation involves defining application profiles and user access rights.
Business Value
How does MultSess improve business value?
MultSess improves user productivity by allowing them to switch between multiple mainframe applications without disconnecting and reconnecting. This reduces the time spent managing sessions and increases overall efficiency.
What happens if an organization does not use MultSess?
Without MultSess, users would need to manage multiple 3270 terminal sessions, which can be time-consuming and cumbersome. This can lead to reduced productivity and increased frustration for users who frequently switch between applications.
Can MultSess reduce operational costs?
MultSess can reduce operational costs by streamlining access to mainframe applications. It simplifies session management, which can lead to fewer support requests and reduced administrative overhead.
Security
What authentication methods are supported?
MultSess supports various authentication methods, including standard z/OS security protocols. Specific methods include RACF, ACF2, and Top Secret. These methods ensure that only authorized users can access mainframe applications.
What access control model is used?
MultSess uses an access control model based on user roles and application profiles. This allows administrators to define which users can access specific mainframe applications. The access control model is typically role-based access control (RBAC).
What audit/logging capabilities exist?
MultSess provides audit logging capabilities to track user access and application usage. These logs can be used to monitor security events and identify potential security breaches. The logs typically include user IDs, timestamps, and application names.
Operations
What ongoing operational requirements exist?
Ongoing operational requirements for MultSess include monitoring system performance, managing user access, and maintaining application profiles. Regular maintenance is needed to ensure the system runs smoothly and securely.
What administrative interfaces are available?
Administrative interfaces for MultSess typically include a command-line interface (CLI) and potentially a web-based console. The CLI is used for configuration and management tasks, while the web console provides a user-friendly interface for monitoring and reporting.
What are common implementation challenges?
Common implementation challenges for MultSess include configuring VTAM correctly, defining appropriate application profiles, and managing user access rights. Careful planning and testing are essential for a successful implementation.
Ready to Start Your Migration?
Download our comprehensive migration guide for MultSess or calculate your ROI.