MapBlaster/PC Modernization Guide

MapBlaster/PC is a PC-based utility designed for developing CICS Basic Mapping Support (BMS) maps. It provides a graphical interface for designing and managing screen layouts for CICS applications. The tool simplifies the process of creating and maintaining BMS map definitions.

MapBlaster/PC is a tool set specifically designed to aid in application development for the CICS environment. It is not a complete system or application on its own, but rather a utility that enhances the development process for CICS applications.

Organizations that develop and maintain CICS applications on z/OS mainframes are the primary users of MapBlaster/PC. These organizations typically include enterprises in industries such as banking, finance, insurance, and retail, where CICS is used for transaction processing.

A company should consider using MapBlaster/PC when they need a more efficient and user-friendly way to create and maintain BMS maps for their CICS applications. It is particularly useful when the development team lacks deep expertise in manual BMS coding or when they need to accelerate the development process.

Alternatives to MapBlaster/PC include manual coding of BMS maps, other PC-based BMS map generators, or integrated development environments (IDEs) that offer BMS map design capabilities. Examples include CA Gener/OL and other similar tools.

MapBlaster/PC runs on a PC and is used to generate BMS map definitions that are then deployed to a z/OS mainframe running CICS. It requires a PC with a compatible operating system and sufficient resources to run the application.

MapBlaster/PC generates BMS map definitions that are used by CICS applications running in an LPAR on z/OS. It is z/OS dependent in the sense that the generated maps are specifically for the CICS environment on z/OS.

MapBlaster/PC is a standalone product, but it enhances the development process for CICS applications. It does not extend or enhance another specific product, but rather provides a utility for creating BMS map definitions that are used by CICS.

MapBlaster/PC requires a PC with a compatible operating system. The generated BMS map definitions are deployed to a z/OS mainframe running CICS. No other specific products or components are strictly required for MapBlaster/PC to function, but a CICS environment is needed to use the generated maps.

MapBlaster/PC improves developer productivity by providing a visual interface for designing BMS maps, reducing the time and effort required compared to manual coding. This leads to faster development cycles and reduced costs.

By simplifying the creation and maintenance of BMS maps, MapBlaster/PC reduces the risk of errors and inconsistencies in screen layouts. This leads to improved application quality and a better user experience.

MapBlaster/PC can help organizations reduce the total cost of ownership (TCO) for CICS applications by improving developer productivity, reducing errors, and simplifying maintenance. This leads to lower development and support costs.

MapBlaster/PC itself does not directly handle security. The security of the CICS applications that use the generated BMS maps is managed by CICS and z/OS security mechanisms, such as Resource Access Control Facility (RACF).

Access to the PC where MapBlaster/PC is installed should be controlled using standard PC security measures, such as password protection and access controls. The generated BMS map definitions should also be protected from unauthorized access.

MapBlaster/PC does not directly encrypt data. The encryption of data within CICS applications is handled by CICS and z/OS security features, such as data encryption and SSL/TLS for network communication.

MapBlaster/PC is typically deployed on individual developer PCs. The implementation involves installing the software and configuring it to generate BMS map definitions in the desired format.

Implementing MapBlaster/PC requires a moderate level of technical expertise. Developers need to be familiar with CICS, BMS, and the process of creating and deploying BMS maps.

Ongoing operational requirements for MapBlaster/PC include maintaining the software on developer PCs and ensuring that the generated BMS map definitions are compatible with the CICS environment. Regular backups of the map definitions are also recommended.

Common implementation challenges include ensuring that the generated BMS map definitions are compatible with the target CICS environment and that developers are properly trained on how to use the tool. Integration with existing development workflows may also pose a challenge.