How does Help/Windows integrate with CICS applications?

Help/Windows provides online help for CICS applications without requiring modifications to the application code. It allows users to access documentation and support information directly within their CICS sessions. This enhances user productivity and reduces the need for external documentation.

What are the key benefits of using Help/Windows?

Help/Windows integrates with CICS applications by intercepting specific commands or key sequences defined within the system. When a user triggers the help function, Help/Windows displays the relevant documentation or support information. This integration is achieved without altering the application's source code.

Who originally developed Help/Windows?

Key benefits include improved user productivity, reduced training time, and consistent access to documentation. It streamlines the support process by providing immediate access to information within the CICS environment. It also reduces the workload on support staff by empowering users to find answers independently.

What platforms does Help/Windows support?

Help/Windows was originally developed by SofTouch Systems. UNICOM Systems acquired the product in 1998.

What is the syntax for basic operations?

Common commands include HELP, DISPLAY, SEARCH, and INDEX. These commands allow users to access help topics, view specific information, search for keywords, and browse the documentation index. The exact syntax varies based on the specific implementation and configuration.

What configuration files or interfaces are used?

Basic operations use commands followed by parameters. For example, HELP TOPIC 'CICS_TRANSACTIONS' displays help for CICS transactions. SEARCH 'error messages' searches for topics containing 'error messages'. DISPLAY INDEX shows the documentation index.

What are the main system components?

Help/Windows uses configuration files to define help topics, keywords, and application-specific information. These files are typically text-based and can be edited to customize the help system. Interfaces include the CICS command interface for user interaction and system-level interfaces for integration.

How do these components communicate?

The main components include the Help Engine, the Documentation Repository, and the User Interface. The Help Engine processes user requests and retrieves information. The Documentation Repository stores the help content. The User Interface provides the means for users to interact with the system.

What databases or storage mechanisms are used?

The Help Engine receives user requests through the CICS interface. It then queries the Documentation Repository to retrieve the relevant information. The User Interface displays the information to the user. Communication is primarily through internal system calls and data transfer within the z/OS or zVSE/VSEn environment.

What ports or network requirements exist?

Help/Windows uses file-based storage for the Documentation Repository. The help content and configuration data are stored in files accessible by the Help Engine. The specific file formats and storage mechanisms depend on the system configuration.

What administrative interfaces are available?

Help/Windows operates within the CICS environment and does not typically require external network ports. Communication occurs within the z/OS or zVSE/VSEn system. Network requirements are minimal, primarily for accessing shared file systems if the Documentation Repository is stored remotely.

How is user management handled?

Administrative interfaces are typically provided through CICS transactions and system commands. These interfaces allow administrators to configure the help system, manage user access, and update documentation. Specific commands and interfaces vary based on the implementation.

What are the main configuration parameters?

User management is handled through the CICS security mechanisms. Administrators can define user roles and permissions to control access to specific help topics and administrative functions. Integration with existing security systems is supported.

What monitoring/logging capabilities exist?

Main configuration parameters include the location of the Documentation Repository, the definition of help topics and keywords, and the settings for user access control. These parameters are typically set through configuration files or administrative interfaces.

What authentication methods are supported?

Monitoring and logging capabilities include logging user activity, error messages, and system events. Administrators can review logs to troubleshoot issues, monitor system performance, and track user interactions. Specific logging features vary based on the implementation.

What access control model is used?

Help/Windows leverages the CICS security features for authentication. The specific authentication methods supported depend on the CICS configuration. Common methods include user ID and password verification.

What encryption is used and where?

Help/Windows uses the access control model provided by CICS. This typically involves role-based access control (RBAC), where users are assigned roles that determine their access to resources and functions. Administrators define roles and assign users to them.

What audit/logging capabilities exist?

Encryption is primarily handled by the underlying CICS and z/OS security infrastructure. Data transmission within the CICS environment may be encrypted using standard security protocols. The specific encryption methods depend on the system configuration.

What are the main competing products?

Audit and logging capabilities are provided through the CICS and z/OS security features. These features allow administrators to track user activity, security events, and system changes. Audit logs can be used to monitor compliance and detect security breaches.

What does this product do that competitors do NOT?

Competing products include other CICS help systems and documentation tools. Specific competitors vary based on the environment and requirements. Some may offer similar functionality, while others may focus on different aspects of documentation management.

Share Your Product Experience

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

Share Your Experience

Help/Windows

UNICOM Systems Active z/OS zVSE/VSEn

Help Documentation and Training CICS

Vendor

UNICOM Systems

Product Overview

The Help/Windows architecture comprises three main components: the Help Engine, the Documentation Repository, and the User Interface. The Help Engine is responsible for processing user requests, retrieving relevant information, and managing the interaction with the Documentation Repository. The Documentation Repository stores the help content, organized in a file-based structure.

The User Interface provides the means for users to interact with the system through CICS commands. Communication between components occurs through internal system calls and data transfer within the z/OS or zVSE/VSEn environment. The system leverages CICS security for authentication and access control, using role-based permissions.

The Documentation Repository uses file-based storage, and the system does not typically require external network ports. The administrative interface is provided through CICS transactions and system commands. The system logs user activity, errors, and system events for monitoring and troubleshooting.

Help/Windows differentiates itself by providing a non-intrusive method for delivering help content, avoiding the need for application code modifications.

Frequently Asked Questions

Related Products

Tape Tools and Utilities

View Details →