XPS Software z/OS zVSE/VSEn

PrintEx Modernization Guide

Printing and Output

PrintEx is a printing and output product by XPS Software. Explore technical details, modernization strategies, and migration paths below.

Product Overview

PrintEx is a software application designed to manage and transform mainframe print output.

This enables organizations to integrate mainframe print operations with distributed systems and modernize their output management processes.

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

PrintEx is a software solution that manages and transforms mainframe print output. It captures print streams from VTAM, JES, or POWER spools and routes them to various destinations, including LAN/UNIX printers, email, FTP servers, and other JES/POWER spools. It also provides data conversion capabilities, such as converting print output to PostScript or PCL formats.

Is this a system, application, or tool?

PrintEx is an application designed to manage and transform mainframe print output. It provides a comprehensive solution for capturing, routing, and converting print data, making it more versatile and accessible across different platforms and systems.

What types of organizations use this?

Organizations that rely on mainframe systems for critical business processes and generate large volumes of print output can benefit from PrintEx. This includes industries such as banking, insurance, healthcare, and government. Companies needing to distribute mainframe-generated reports and documents to a variety of destinations will find PrintEx useful.

When should we consider PrintEx?

A company should consider PrintEx when it needs to modernize its mainframe print operations, integrate mainframe output with distributed systems, or reduce the cost and complexity of managing mainframe print streams. If an organization is struggling to deliver mainframe reports to users in a timely and efficient manner, PrintEx can provide a solution.

What are the alternatives to PrintEx?

Alternatives to PrintEx include Infoprint Server and other mainframe output management solutions. Some open-source tools can handle basic print routing, but they may lack the advanced features and enterprise-level support offered by PrintEx. Natural Advanced Facilities is also a related product.

Technical

What infrastructure is required?

PrintEx runs on z/OS and zVSE/VSEn mainframe platforms. It can accept print output from JES or POWER spooling systems, as well as VTAM printers. It requires TCP/IP connectivity to route output to LAN/UNIX printers, FTP servers, and email systems.

For mainframe products: Does this run in an LPAR?

For mainframe products, PrintEx typically runs in an LPAR (Logical Partition) on z/OS or zVSE/VSEn. It integrates with the operating system's spooling and communication subsystems. It does not require specific databases but may use VSAM datasets for configuration and logging.

Can PrintEx accept print output as a VTAM printer?

PrintEx can accept print data as a VTAM printer. This allows applications to send print jobs directly to PrintEx as if it were a physical printer. PrintEx then processes and routes the output according to its configuration.

Does PrintEx support data conversion?

PrintEx includes facilities for data conversion to PostScript or PCL. This allows mainframe-generated reports and documents to be printed on a wider range of printers and viewed on different platforms. The conversion process can be customized to meet specific formatting requirements.

Business Value

What is the business value of PrintEx?

PrintEx helps organizations streamline their mainframe print operations, reduce costs, and improve the delivery of information. By routing mainframe output to a variety of destinations, it enables better collaboration and decision-making. The data conversion capabilities ensure that mainframe reports can be easily accessed and viewed by users on different platforms.

What would happen if an organization did NOT use this product?

Without PrintEx, organizations may face challenges in managing and distributing mainframe print output. This can lead to delays in information delivery, increased costs, and limited flexibility in how mainframe data is used. Users may be forced to rely on outdated methods for accessing mainframe reports, hindering productivity and collaboration.

How does PrintEx integrate with enterprise ecosystems?

PrintEx integrates with enterprise ecosystems by routing mainframe print output to various destinations, including email systems, FTP servers, and network printers. It can also be integrated with document management systems and other applications through its API. This allows mainframe data to be seamlessly incorporated into broader business processes.

Security

How does PrintEx handle security?

PrintEx leverages the security features of the underlying z/OS or zVSE/VSEn operating system. It supports authentication methods such as RACF, ACF2, and Top Secret. Access to print output can be controlled based on user roles and permissions. PrintEx also provides audit logging capabilities to track user activity and ensure compliance.

What access control model is used?

PrintEx uses an access control model based on user roles and permissions. This allows administrators to define which users can access specific print queues and output destinations. The access control model can be integrated with existing security systems, such as RACF or ACF2, to provide a centralized approach to security management.

What audit/logging capabilities exist?

PrintEx provides audit logging capabilities to track user activity and system events. The audit logs can be used to monitor access to print output, identify potential security breaches, and ensure compliance with regulatory requirements. The audit logs can be stored in VSAM datasets or other storage mechanisms for long-term retention.

Operations

How is PrintEx typically deployed?

PrintEx is typically deployed on-premise, running on z/OS or zVSE/VSEn mainframe systems. Implementation requires technical expertise in mainframe systems, print management, and network configuration. Ongoing operational requirements include monitoring system performance, managing print queues, and maintaining security settings.

What level of technical expertise is required to implement it?

Implementing PrintEx requires a team with expertise in mainframe systems, print management, and network configuration. Common implementation challenges include integrating PrintEx with existing security systems, configuring print queues and output destinations, and ensuring compatibility with different printer types and data formats.

What ongoing operational requirements exist?

Ongoing operational requirements for PrintEx include monitoring system performance, managing print queues, and maintaining security settings. Administrators need to ensure that PrintEx is properly configured to route print output to the correct destinations and that users have the appropriate access permissions. Regular maintenance and updates are also required to ensure system stability and security.

Ready to Start Your Migration?

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

Calculate ROI