BookManager Modernization Guide

BookManager was a software product used for creating and viewing softcopy books online. It allowed users to create books from BookMaster and DCF documents, making them accessible across different platforms.

BookManager consisted of two main components: BookManager Build, which was used to create BookManager books, and BookManager Read, which was used to read them. These components were available for various platforms, including z/OS and z/VM.

BookManager books created on one platform could be read by BookManager on any other supported platform. This cross-platform compatibility was a key feature, allowing for seamless access to documentation across different environments.

IBM has discontinued support for BookManager as a separate product. However, BookManager Read is now included with z/OS, providing continued access to existing BookManager libraries for z/OS users.

BookManager Build was used to create books from BookMaster and DCF (Document Composition Facility) documents. It provided the tools necessary to format and structure these documents into a BookManager-compatible format.

BookManager Read allowed users to view BookManager books online. It provided a user interface for navigating and reading the content, with features such as search and table of contents.

BookManager BookServer products were available for AIX, Linux, and Windows. These products allowed organizations to host BookManager book libraries on these platforms, providing centralized access to documentation.

BookManager Build for MVS Release 3 had the Product ID 5695-045, and BookManager Read for MVS Release 3 had the Product ID 5695-046. BookManager Build for z/OS and BookManager Read for z/OS do not have product IDs.

BookManager provided a centralized solution for managing and distributing documentation, potentially reducing printing and distribution costs. By making documentation available online, organizations could improve access and reduce the need for physical copies.

By providing easy access to documentation, BookManager could improve user productivity and reduce the time spent searching for information. This could lead to increased efficiency and better decision-making.

While BookManager itself may no longer be actively supported, migrating to modern documentation solutions can provide even greater ROI through improved features, better integration with other systems, and reduced maintenance costs.

Organizations using BookManager should assess their current documentation needs and explore modern alternatives that offer improved functionality and support. This may involve migrating existing BookManager libraries to a new format.

As a discontinued product, BookManager no longer receives security updates or patches. Organizations continuing to use BookManager should be aware of potential security risks and take appropriate mitigation measures.

BookManager may not meet current compliance requirements, especially regarding data security and access control. Organizations should evaluate whether BookManager aligns with their compliance obligations and consider alternatives if necessary.

Migrating to a modern documentation platform can improve security and compliance posture by providing features such as role-based access control, audit logging, and encryption.

Organizations should conduct a thorough security audit of their BookManager environment to identify potential vulnerabilities and implement appropriate security controls. This may include restricting access, monitoring activity, and patching known vulnerabilities.

Since BookManager is no longer supported, organizations must rely on internal expertise or third-party support for maintenance and troubleshooting. This can be challenging and costly.

Monitoring BookManager performance and availability is crucial to ensure continued access to documentation. Organizations should implement monitoring tools and procedures to detect and resolve issues promptly.

Creating and maintaining run-books for BookManager can help streamline operations and reduce the risk of errors. These run-books should document common tasks, troubleshooting steps, and escalation procedures.

Migrating to a modern documentation platform can simplify operations by providing centralized management, automated updates, and improved monitoring capabilities.

Organizations should develop a plan for migrating from BookManager to a modern documentation platform. This plan should include an assessment of current documentation needs, selection of a replacement platform, and a timeline for migration.

When selecting a replacement platform, organizations should consider factors such as features, integration capabilities, cost, and vendor support. It is important to choose a platform that meets their specific needs and budget.

The migration process may involve converting existing BookManager libraries to a new format. Organizations should plan for this conversion and ensure that the new platform supports the required features and functionality.

Organizations should communicate their migration plans to stakeholders and provide training on the new platform. This will help ensure a smooth transition and minimize disruption to users.