What are some common commands and their syntax?

Common commands include START, STOP, ROUTE, and STATUS. The syntax varies depending on the operation, but generally follows a command-parameter structure. For example, to route a job, you might use the ROUTE command followed by the job ID and destination.

What configuration files or interfaces are used?

eSendIT uses configuration files to define output destinations, formats, and routing rules. These files are typically text-based and can be edited using standard text editors. The system also uses interfaces to interact with JES and POWER.

Does eSendIT offer an API for integration?

eSendIT does not expose a REST API. It uses native interfaces for integration with z/OS and zVSE/VSEn systems. These interfaces allow for interaction with JES and POWER subsystems to manage output.

What are the main system components?

The main components include the Output Router, the Format Processor, and the Destination Manager. The Output Router intercepts print jobs, the Format Processor handles output formatting, and the Destination Manager routes the output.

How does eSendIT improve business processes?

eSendIT streamlines output management by automating the routing of print jobs to various destinations. This reduces manual intervention and improves efficiency. It supports integration with CICS, allowing for direct printing from applications.

What are the cost-saving benefits of using eSendIT?

By automating output routing, eSendIT reduces the need for manual intervention, saving time and resources. It also minimizes errors associated with manual processes. The system's integration with CICS further enhances efficiency.

How does eSendIT improve communication and collaboration?

eSendIT's ability to route output to various destinations, including email and network shares, enhances communication and collaboration. It ensures that the right information reaches the right people quickly and efficiently.

How does eSendIT improve the user experience?

eSendIT's integration with CICS allows for direct printing from applications, improving the user experience. Users can print directly from their CICS sessions without needing to manually route output.

What authentication methods are supported?

eSendIT does not explicitly detail specific authentication methods. However, it relies on the underlying security of the z/OS and zVSE/VSEn systems. Access control is managed through the operating system's security features.

What access control model is used?

eSendIT leverages the access control mechanisms provided by the z/OS and zVSE/VSEn operating systems. This typically involves user authentication and authorization based on system-level security policies.

What encryption is used?

eSendIT does not explicitly detail encryption methods. Security relies on the underlying security features of the z/OS and zVSE/VSEn systems, which may include encryption for data transmission and storage.

What audit/logging capabilities exist?

eSendIT provides logging capabilities to track output routing and system events. These logs can be used for auditing purposes. The specific details of the logging depend on the configuration and the underlying system.

What administrative interfaces are available?

Administrative interfaces are typically provided through the z/OS and zVSE/VSEn system consoles. Configuration is managed through text-based configuration files. There is no specific GUI or web console mentioned.

How is user management handled?

User management is handled through the z/OS and zVSE/VSEn system's user management tools. eSendIT relies on the underlying operating system for user authentication and authorization.

What are the main configuration parameters?

Main configuration parameters include output destinations, routing rules, and format specifications. These parameters are typically defined in text-based configuration files. The specific parameters depend on the setup.

What monitoring/logging capabilities exist?

eSendIT provides logging of output routing and system events. This information can be used for monitoring the system's performance and troubleshooting issues. The level of detail in the logs is configurable.

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

eSendIT

MacKinney Systems Active z/OS zVSE/VSEn

Printing and Output Networks and Communication

Vendor

MacKinney Systems

Product Overview

The eSendIT architecture comprises several key components designed to manage and route output from z/OS and zVSE/VSEn systems. The Output Router is the central component, intercepting print jobs from JES and POWER. The Format Processor then handles the formatting of the output, converting it to the required format for the destination.

The Destination Manager is responsible for routing the output to the specified destinations, such as printers, email addresses, FTP servers, or network shares. Communication between these components is primarily internal, using system-level interfaces. Configuration files, typically text-based, define the routing rules, output formats, and destination details.

The system interacts with JES and POWER through native interfaces, allowing it to intercept and manage print jobs. There is no REST API. The system relies on the underlying z/OS and zVSE/VSEn security features for authentication and access control.

Logging is provided for auditing and troubleshooting. The system's design prioritizes efficiency and flexibility, allowing for easy integration with existing infrastructure and customization to meet specific output management needs. The system supports various output formats to ensure compatibility with different destinations.

Frequently Asked Questions

What is the primary function of eSendIT?

eSendIT routes JES and POWER output to various destinations. It supports output to CICS printers and application screens, as well as routing via FTP, email, and network drives. It also integrates with CICS/Fax.

How does eSendIT handle output from z/OS and zVSE/VSEn systems?

eSendIT processes output from JES and POWER subsystems. It intercepts print jobs and routes them based on configuration. It supports various output formats and destinations, including printers, email, and network shares.

Where can eSendIT route output?

eSendIT offers flexibility in output destinations. Users can route output to local or network printers, email recipients, FTP servers, and network file shares. The system supports various output formats to ensure compatibility.

How does eSendIT integrate with CICS?

eSendIT integrates with CICS printers and application screens. This allows for direct printing from CICS applications and the ability to display output on CICS terminals. It also supports CICS/Fax integration.

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

Share Your Product Experience

Help the community by sharing your experience with mainframe products. Your insights help others make informed decisions.

Share Your Experience