Name: e-Control
Availability: InStock

Question 1

What does e-Control do?

Accepted Answer

e-Control is a TCP/IP monitor designed for z/OS environments. It allows administrators to observe and analyze network traffic, providing insights into performance and potential issues. It supports both Interlink's TCPaccess and IBM's TCP/IP stacks.

Question 2

Is this a system, application, or tool?

Accepted Answer

e-Control is best described as a system monitoring tool. It provides real-time and historical data about network performance, helping to identify bottlenecks and optimize resource utilization. It is not an application in itself, but rather a tool to manage and observe other applications.

Question 3

What types of organizations used this?

Accepted Answer

e-Control was useful for organizations that relied heavily on TCP/IP communication within their z/OS environments. These were typically larger enterprises in industries such as banking, finance, and insurance, where mainframe systems played a critical role. Any organization needing detailed monitoring of TCP/IP traffic on z/OS could benefit.

Question 4

When should an organization have considered e-Control?

Accepted Answer

An organization might have considered e-Control when they needed granular visibility into their TCP/IP network traffic on z/OS. This could be due to performance issues, security concerns, or a general desire to optimize network resource usage. It was particularly relevant when using Interlink's TCPaccess alongside IBM's TCP/IP.

Question 5

What are the alternatives to e-Control?

Accepted Answer

Alternatives to e-Control include products like Rocket TMON for TCP/IP, NetMaster Network Management for SNA, and VitalSigns for VTAM. These tools offer similar network monitoring capabilities for z/OS environments, providing insights into TCP/IP traffic and overall network performance. Some of these alternatives may offer broader monitoring capabilities beyond just TCP/IP.

Question 6

What infrastructure is required?

Accepted Answer

e-Control operated within the z/OS environment, requiring a mainframe system. It was dependent on the presence of either Interlink's TCPaccess or IBM's TCP/IP stack. The product likely ran within an LPAR (Logical Partition) on the mainframe, leveraging z/OS subsystems for its operation.

Question 7

How was e-Control typically deployed?

Accepted Answer

e-Control was deployed on-premise within the z/OS environment. This involved installing the software on the mainframe system and configuring it to monitor the desired TCP/IP traffic. The implementation required a good understanding of z/OS, TCP/IP networking, and the specific environment being monitored.

Question 8

What are some common commands used with e-Control?

Accepted Answer

The specific commands and syntax used with e-Control are not available. However, typical monitoring tools for z/OS would involve commands to start and stop monitoring sessions, define filters to capture specific traffic, and generate reports. Configuration files would likely be used to define monitoring parameters and thresholds.

Question 9

Does e-Control have an API?

Accepted Answer

Details on e-Control's API and integration capabilities are not available. However, it is possible that it exposed APIs for retrieving monitoring data or integrating with other systems management tools. The specific API types (REST, SOAP, etc.) and protocols used would depend on the product's design.

Question 10

What business value did e-Control provide?

Accepted Answer

e-Control provided business value by enabling organizations to optimize their TCP/IP network performance on z/OS. By monitoring traffic and identifying bottlenecks, it helped to improve application response times and reduce network congestion. This led to increased productivity and a better user experience.

Question 11

What would happen without e-Control?

Accepted Answer

Without a tool like e-Control, organizations would have limited visibility into their TCP/IP network traffic on z/OS. This could lead to difficulty in diagnosing performance problems, identifying security threats, and optimizing resource utilization. It would be harder to ensure reliable and efficient network communication.

Question 12

What was the licensing model for e-Control?

Accepted Answer

The licensing model for e-Control is not available. However, it is likely that it was a perpetual license with annual maintenance fees. The total cost of ownership would include the initial license fee, maintenance fees, and the cost of staff required to implement and operate the product.

Question 13

What security features did e-Control have?

Accepted Answer

Details on e-Control's security features are not available. However, it is likely that it provided some level of access control to restrict who could view monitoring data or configure the system. It may have also integrated with z/OS security systems like RACF to authenticate users and authorize access.

Question 14

What encryption was used?

Accepted Answer

Specific encryption methods used by e-Control are not known. However, it is possible that it used encryption to protect sensitive monitoring data in transit or at rest. The type of encryption used would depend on the product's design and the security requirements of the environment.

Question 15

What audit/logging capabilities existed?

Accepted Answer

Audit and logging capabilities would have been essential for a monitoring tool like e-Control. It would likely have logged user activity, configuration changes, and any security-related events. These logs could be used for auditing purposes, troubleshooting problems, and detecting security breaches.

Question 16

What ongoing operational requirements existed?

Accepted Answer

Ongoing operational requirements for e-Control would include monitoring the system to ensure it is functioning correctly, performing regular maintenance tasks, and applying any necessary updates or patches. Staff with expertise in z/OS, TCP/IP networking, and the e-Control product itself would be required.

Question 17

What administrative interfaces were available?

Accepted Answer

Administrative interfaces for e-Control likely included a command-line interface (CLI) and possibly a graphical user interface (GUI) or web console. The CLI would be used for performing configuration tasks and running monitoring commands. A GUI or web console would provide a more user-friendly interface for viewing monitoring data and managing the system.

Question 18

How was user management handled?

Accepted Answer

User management in e-Control would involve creating user accounts, assigning roles and permissions, and managing user access to the system. It may have integrated with z/OS security systems like RACF to authenticate users and authorize access to specific functions or data.

Share Your Product Experience

e-Control

Product Overview

Frequently Asked Questions

What does e-Control do?

Is this a system, application, or tool?

What types of organizations used this?

When should an organization have considered e-Control?

What are the alternatives to e-Control?

What infrastructure is required?

How was e-Control typically deployed?

What are some common commands used with e-Control?

Does e-Control have an API?

What business value did e-Control provide?

What would happen without e-Control?

What was the licensing model for e-Control?

What security features did e-Control have?

What encryption was used?

What audit/logging capabilities existed?

What ongoing operational requirements existed?

What administrative interfaces were available?

How was user management handled?

Related Products

More from Interlink Computer Sciences

Interlink

TurboAPI

TurboFTP

TurboTelnet

Similar Products

2cIP

2cSNA

3770Link

3780Link

4Tune

ABARS/Assist

Help Improve This Directory

Are You a Vendor? Claim Your Listing