Preference Modernization Guide

Preference is a software product designed to create and deliver online help and reference information within mainframe environments. It enables developers to build interactive help systems that can be accessed directly from applications running in VTAM, CA IDMS, CICS, IMS, and TSO.

Preference is best described as a tool set. It provides the tools and utilities necessary to create, format, and deliver help content within the specified mainframe environments.

Organizations that rely heavily on mainframe applications for their core business processes and need to provide users with readily accessible help and documentation are ideal candidates for Preference. This includes companies in industries such as banking, finance, insurance, and government.

A company should consider using Preference when they need to improve user productivity and reduce training costs by providing context-sensitive help directly within their mainframe applications. It is particularly useful when dealing with complex systems or a large user base.

Alternatives to Preference include manual documentation, generic help authoring tools not specifically designed for mainframe environments, or custom-built help systems. Competing products might include older mainframe-based documentation tools.

Preference runs on the z/OS platform and requires specific subsystems such as VTAM, CA IDMS, CICS, IMS, and TSO to be present. It operates within an LPAR on the mainframe.

Preference is typically deployed on-premise within the mainframe environment. It requires technical expertise in mainframe systems and the specific subsystems it integrates with.

Preference extends and enhances existing mainframe applications by providing a help system. It does not replace any core functionality but adds a layer of user assistance.

The exact commands and syntax for Preference would be found in the product's documentation. Common operations would include creating help topics, linking topics to application screens, and defining navigation paths.

Preference improves user productivity by providing immediate access to relevant help information. This reduces the need for users to consult external documentation or seek assistance from support staff, leading to faster task completion and fewer errors.

By providing integrated help, Preference can reduce training costs. Users can learn how to use the system more effectively through self-service, reducing the need for formal training programs.

The cost of not using Preference includes increased training expenses, lower user productivity, and higher support costs. Users may struggle to use the system effectively, leading to errors and delays.

Specific authentication methods supported by Preference would be detailed in the product's documentation. It likely integrates with existing mainframe security systems.

Preference likely uses an access control model that integrates with the mainframe's security system, such as RACF or ACF2, to control access to help topics and administrative functions.

Audit and logging capabilities would be essential for tracking access to help information and administrative changes. Specific details would be found in the product's documentation.

Ongoing operational requirements include monitoring the availability and performance of the help system, maintaining the help content, and managing user access. Mainframe systems programmers would typically handle these tasks.

Common implementation challenges include integrating Preference with existing mainframe applications, customizing the help system to meet specific user needs, and ensuring that the help content is accurate and up-to-date.

Administrative interfaces for Preference would likely include a combination of command-line interfaces (CLIs) and potentially ISPF panels for managing the help system and user access.