Lattwein zVSE/VSEn

BACEMT Modernization Guide

BatchCICS

BACEMT is a batch product by Lattwein. Explore technical details, modernization strategies, and migration paths below.

Product Overview

BACEMT is a toolset that enables control of CICS environments directly from batch jobs.

Alternatives to BACEMT include BatchCICS-Connect and MacKinney Batch to CICS.

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

BACEMT enables control of CICS environments directly from batch jobs. It allows users to execute CICS CEMT commands, console commands, start CICS tasks with data transmission, execute CICS programs, and perform file transfers, all from batch processing.

Is this a system, application, or tool?

BACEMT is a toolset that bridges batch processing and CICS transaction processing. It provides a set of utilities and commands to manage and interact with CICS from batch environments.

What types of organizations use this?

Organizations that rely on both batch processing and CICS transaction processing, particularly those running z/VSE or VSEn environments, find BACEMT useful. These are often enterprises in industries like banking, insurance, and retail that need to automate CICS tasks from batch jobs.

When should we consider BACEMT?

A company should consider BACEMT when they need to automate CICS tasks from batch jobs, streamline operations between batch and CICS environments, or require centralized control over CICS regions from batch processing.

What are the alternatives to BACEMT?

Alternatives to BACEMT include BatchCICS-Connect and MacKinney Batch to CICS. These products also provide ways to control CICS from batch jobs, but may differ in features, ease of use, or integration capabilities.

Technical

What infrastructure is required?

BACEMT runs on z/VSE and VSEn platforms. It requires a CICS environment to manage and control. It operates within the constraints and capabilities of the z/VSE or VSEn operating system.

For mainframe products: Does this run in an LPAR?

BACEMT is designed to run on z/VSE and VSEn operating systems. It leverages the batch processing capabilities of these systems to interact with CICS regions.

Is this a standalone product or does it extend/enhance another product?

BACEMT extends the capabilities of CICS by allowing batch jobs to execute CICS commands and programs. It enhances the interaction between batch and CICS environments.

Business Value

How does BACEMT improve business value?

BACEMT streamlines operations by enabling batch jobs to manage CICS regions, automate tasks, and transfer data. This reduces manual intervention, improves efficiency, and ensures consistency in CICS operations.

What are the cost savings associated with BACEMT?

By automating CICS tasks from batch jobs, BACEMT reduces the need for manual intervention, minimizing the risk of human error and improving overall operational reliability. This leads to cost savings and better service levels.

Security

How does BACEMT address security concerns?

BACEMT leverages the security features of the underlying z/VSE and VSEn operating systems, as well as CICS security mechanisms. It integrates with existing security systems to control access to CICS resources and functions.

What access control model is used?

BACEMT integrates with existing security systems on z/VSE and VSEn to control access to CICS resources. It uses the access control mechanisms provided by the operating system and CICS to ensure that only authorized users and batch jobs can perform specific actions.

Operations

How is BACEMT typically deployed?

BACEMT is typically deployed on-premise within the z/VSE or VSEn environment. It requires technical expertise in both batch processing and CICS administration to implement and maintain.

What ongoing operational requirements exist?

Ongoing operational requirements for BACEMT include monitoring batch jobs that interact with CICS, maintaining the configuration of BACEMT, and ensuring compatibility with CICS and operating system upgrades.

What are common implementation challenges?

Common implementation challenges include configuring BACEMT to work with specific CICS regions, ensuring proper security settings, and resolving compatibility issues between BACEMT and other software components.

Ready to Start Your Migration?

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

Calculate ROI