What infrastructure is required?

SOLVE:EPS runs on the z/OS platform and requires the JES spool for managing print output. It also needs a TCP/IP network connection to communicate with the printers.

For mainframe products: Does this run in an LPAR?

Yes, SOLVE:EPS runs in an LPAR on z/OS. It is dependent on the z/OS operating system and its associated subsystems.

What configuration files are used?

SOLVE:EPS typically uses configuration files to define printer destinations, routing rules, and other parameters. These files are read during startup and can be modified to adjust the system's behavior.

What protocols does it use for communication?

SOLVE:EPS communicates with TCP/IP printers using standard protocols such as LPR/LPD or direct socket printing. The specific protocol used depends on the printer's capabilities and configuration.

How does SOLVE:EPS reduce costs?

SOLVE:EPS allows organizations to leverage existing TCP/IP printer infrastructure, reducing the need for specialized mainframe printers. This can lead to significant cost savings in terms of hardware, maintenance, and supplies.

How does SOLVE:EPS improve efficiency?

By centralizing printer management through SOLVE:EPS, organizations can simplify administration and improve control over print output. This can reduce the burden on IT staff and improve overall efficiency.

How does SOLVE:EPS integrate legacy systems?

SOLVE:EPS provides a bridge between the mainframe environment and modern printing technology, allowing organizations to integrate their legacy systems with current infrastructure. This can extend the life of mainframe applications and protect investments.

What audit logging capabilities exist?

SOLVE:EPS provides audit logging capabilities to track print activity, including user IDs, print jobs, and printer destinations. This information can be used for security monitoring and compliance purposes.

Does SOLVE:EPS encrypt print data?

SOLVE:EPS supports encryption of print data in transit to protect sensitive information from unauthorized access. This helps to maintain confidentiality and prevent data breaches.

How is SOLVE:EPS deployed?

SOLVE:EPS can be deployed on-premise within the z/OS environment. It requires technical expertise to configure and maintain the software, including knowledge of z/OS, TCP/IP networking, and printing protocols.

What are the ongoing operational requirements?

Ongoing operational requirements for SOLVE:EPS include monitoring system performance, managing printer configurations, and troubleshooting printing issues. This may require dedicated staff with mainframe and networking skills.

What are common implementation challenges?

Common implementation challenges for SOLVE:EPS include configuring network connectivity, resolving printer compatibility issues, and integrating with existing security systems. Careful planning and testing are essential for a successful deployment.

Are You a Vendor? Claim Your Listing

Take control of your product listings. Add verified information, showcase updates, and unlock a Claimed Vendor badge across the directory.

Claim Your Listing Now

SOLVE:EPS

Name: SOLVE:EPS
Availability: InStock

Broadcom Supported z/OS

Printing and Output Networks and Communication

Vendor

Broadcom

Product Overview

SOLVE:EPS provides a solution for printing from z/OS mainframe systems to TCP/IP printers. It acts as a bridge between the mainframe environment and modern printing infrastructure. The architecture involves components that intercept print output from the JES spool and virtual SNA printers, then route it to the appropriate TCP/IP printer based on defined rules.

SOLVE:EPS uses configuration files to define printer destinations, routing rules, and security settings. It communicates with printers using protocols like LPR/LPD or direct socket printing. The system integrates with z/OS security systems, such as RACF, ACF2, or Top Secret, to control access to printing resources.

Audit logging provides a record of print activity for security monitoring and compliance. Alternatives to SOLVE:EPS include Multiprint/VM, eSendIT, and Columbus Z. SOLVE:EPS simplifies mainframe printing and reduces costs.

Frequently Asked Questions

What does SOLVE:EPS do?

SOLVE:EPS is a software solution that enables z/OS users to print to TCP/IP printers connected to a local area network (LAN). It takes print output from the JES spool and virtual SNA printers and directs it to the appropriate TCP/IP printer.

Is this a system, application, or tool?

SOLVE:EPS is an application that resides on z/OS. It provides a bridge between the mainframe environment and the world of TCP/IP-based printing.

What types of organizations use this?

Organizations that rely on a z/OS mainframe for core business applications and need to print to modern, LAN-connected printers would benefit from SOLVE:EPS. This includes enterprises in industries like banking, insurance, and government.

When should we consider SOLVE:EPS?

A company should consider SOLVE:EPS when they want to leverage existing TCP/IP printer infrastructure for mainframe output, reduce printing costs, and simplify printer management.

What are the alternatives to SOLVE:EPS?

Alternatives to SOLVE:EPS include Multiprint/VM, eSendIT, and Columbus Z. These products offer similar functionality for routing mainframe output to TCP/IP printers.

Help Improve This Directory

Notice outdated information? Have insights about this product? Help the mainframe community stay informed with accurate, current data.

Report Issue Suggest Product Share Event

Are You a Vendor? Claim Your Listing

Take control of your product listings. Add verified information, showcase updates, and unlock a Claimed Vendor badge across the directory.

Claim Your Listing Now

Are You a Vendor? Claim Your Listing

SOLVE:EPS

Product Overview

Frequently Asked Questions

What does SOLVE:EPS do?

Is this a system, application, or tool?

What types of organizations use this?

When should we consider SOLVE:EPS?

What are the alternatives to SOLVE:EPS?

What infrastructure is required?

For mainframe products: Does this run in an LPAR?

What configuration files are used?

What protocols does it use for communication?

How does SOLVE:EPS reduce costs?

How does SOLVE:EPS improve efficiency?

How does SOLVE:EPS integrate legacy systems?

How does SOLVE:EPS control access to printing resources?

What audit logging capabilities exist?

Does SOLVE:EPS encrypt print data?

How is SOLVE:EPS deployed?

What are the ongoing operational requirements?

What are common implementation challenges?

Related Products

More from Broadcom

AcceleREXX

ACF2

Allocate DASD Space and Placement

Auditor for z/OS

Automation Point

Bind Analyzer for Db2

Similar Products

_beta doc|z plus

_beta doc|z transform

$avers

2cIP

2cSNA

3770Link

Help Improve This Directory

Are You a Vendor? Claim Your Listing