DSI Document Systems z/OS

SysQManager Modernization Guide

CICSAdministrationTools and Utilities

SysQManager is a cics product by DSI Document Systems. Explore technical details, modernization strategies, and migration paths below.

Product Overview

SysQManager is a tool designed for z/OS CICS environments to dynamically create extrapartition Transient Data Queues (TDQs).

Key features include dynamic TDQ creation and the optional WordShrink feature, which reduces message sizes in the CSSL queue.

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 SysQManager do?

SysQManager is a tool that dynamically creates CICS extrapartition Transient Data Queues (TDQs). It allows you to redirect output TDQs, like CSSL, CEEMSG, and MSGUSER, to JES for processing without requiring a CICS shutdown.

Is this a system, application, or tool?

SysQManager is a tool designed to enhance CICS administration by providing dynamic TDQ creation capabilities.

What types of organizations use this?

Organizations that rely heavily on CICS for transaction processing and need to manage transient data queues efficiently are ideal users. This includes enterprises in finance, insurance, and retail.

When should we consider SysQManager?

Consider using SysQManager when you need to dynamically manage CICS TDQs, especially when you want to offload output queues to JES for processing without interrupting CICS operations.

What are the alternatives to SysQManager?

Alternatives include manual TDQ management, custom-built solutions, or other CICS management tools that offer TDQ capabilities. However, SysQManager specializes in dynamic creation and redirection to JES.

Technical

What infrastructure is required?

SysQManager requires a z/OS environment with CICS. It leverages JES for offloading output queues.

For mainframe products: Does this run in an LPAR?

SysQManager runs within a z/OS LPAR, dependent on the CICS subsystem. It requires JES to be available for processing redirected output.

Does this extend or enhance another product?

SysQManager enhances CICS by providing dynamic TDQ management. It works alongside CICS, leveraging its capabilities for transaction processing.

What other products or components must be present for this to work?

SysQManager requires CICS to be operational. It also needs JES to be configured to receive and process the redirected output from TDQs.

Business Value

How does SysQManager provide business value?

SysQManager helps organizations maintain CICS availability by allowing output processing to occur without shutting down CICS. The WordShrink feature reduces the size of messages, potentially saving storage and improving performance.

What happens if an organization does not use this product?

Without SysQManager, organizations might face CICS downtime for output processing or deal with larger message sizes, impacting performance and storage. Manual TDQ management can be time-consuming and error-prone.

When is this product a good fit?

SysQManager is a good fit when you need to dynamically manage TDQs, reduce CICS downtime, and optimize message sizes. It is particularly useful in high-volume transaction processing environments.

Security

How does SysQManager address security concerns?

SysQManager leverages the security features of z/OS and CICS. Access to TDQs and the ability to redirect output are controlled through CICS security mechanisms.

How does it integrate with existing security systems?

SysQManager integrates with CICS security to control access to TDQs. User management is handled through CICS RACF or similar security systems.

Operations

How is SysQManager typically deployed?

SysQManager is typically deployed on-premise within the z/OS environment. Implementation requires expertise in CICS and JES configurations.

What are the ongoing operational requirements?

Ongoing operational requirements include monitoring TDQ activity, ensuring JES is available, and maintaining CICS configurations. Staff with CICS and z/OS expertise are needed.

What are common implementation challenges?

Common implementation challenges include configuring CICS security for TDQ access, ensuring JES is properly configured to receive redirected output, and managing TDQ definitions.

Ready to Start Your Migration?

Download our comprehensive migration guide for SysQManager or calculate your ROI.

Calculate ROI