How are the Index Extractor and Index Builder invoked?

The Index Extractor and Index Builder are typically invoked via JCL (Job Control Language) on z/OS. These jobs specify the input data sets, control cards, and execution parameters.

How is the Secondary Index Call Interceptor integrated with IMS applications?

The Secondary Index Call Interceptor is link-edited with each IMS application. This allows it to intercept DL/I calls without requiring application changes.

What APIs does Secondary Index for IMS expose?

The product uses standard DL/I calls for interacting with IMS databases. There are no custom APIs exposed.

How do the components operate in terms of online/offline processing?

The Index Extractor and Index Builder operate offline, reading the IMS database sequentially and building the index structures. The Secondary Index Call Interceptor operates in real-time, intercepting DL/I calls.

How does Secondary Index for IMS improve application performance?

By automatically maintaining secondary indexes, the product improves application performance by optimizing data retrieval. This reduces the need for full database scans, leading to faster response times.

How does Secondary Index for IMS reduce operational costs?

The product reduces the need for manual index maintenance, freeing up database administrators to focus on other tasks. This automation streamlines operations and reduces operational costs.

How does Secondary Index for IMS simplify implementation?

The product's ability to create and maintain indexes without application changes reduces the risk associated with application modifications. This simplifies the implementation process and minimizes disruption.

How does Secondary Index for IMS leverage existing security features?

The product leverages the security features of z/OS and IMS. Access to the underlying data is controlled by IMS security mechanisms.

What authentication methods are supported?

The product does not introduce new authentication mechanisms. It relies on the existing IMS authentication methods.

What encryption is used and where?

The product does not perform encryption. Data is stored and transmitted using the existing IMS encryption settings.

What audit/logging capabilities exist?

The product logs index creation and maintenance activities. These logs can be used for auditing purposes.

How are the Index Extractor and Index Builder monitored?

The Index Extractor and Index Builder are managed through JCL. Monitoring involves tracking the execution of these jobs and reviewing the associated logs.

How is the Secondary Index Call Interceptor monitored?

The Secondary Index Call Interceptor operates within the IMS environment. Monitoring involves tracking IMS transaction performance and reviewing IMS logs.

Where are the configuration parameters defined?

Configuration parameters are defined in the configuration files used by the Index Extractor and Index Builder. These parameters control the index structure, source database, and processing options.

How is user management handled?

User management is handled through the existing IMS security mechanisms. The product does not introduce new user management features.

Share Your Product Experience

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

Share Your Experience

Secondary Index for IMS

Name: Secondary Index for IMS
Availability: InStock

Broadcom Active z/OS

IMS Administration Databases

Vendor

Broadcom

Product Overview

Secondary Index for IMS automates the creation and maintenance of secondary indexes for IMS DEDB databases. The architecture includes three main components: the Index Extractor, the Index Builder, and the Secondary Index Call Interceptor. The Index Extractor reads the database and extracts index data.

The Index Builder creates the index structures. The Secondary Index Call Interceptor intercepts DL/I calls from applications and performs secondary index processing as needed. The Index Extractor and Index Builder are invoked via JCL on z/OS.

These jobs specify the input data sets, control cards, and execution parameters. Configuration files define the index structure, source database, and processing parameters. The Secondary Index Call Interceptor is link-edited with IMS applications, allowing it to intercept DL/I calls without requiring application changes.

The product uses standard DL/I calls for interacting with IMS databases. Monitoring involves tracking the execution of JCL jobs and reviewing IMS logs. The product leverages existing IMS security mechanisms for access control.

Competing products may require manual index maintenance or application modifications.

Frequently Asked Questions

What is the primary function of Secondary Index for IMS?

Secondary Index for IMS automatically builds and maintains secondary indexes for IMS DEDB databases. It uses the Index Extractor and Index Builder to create and rebuild indexes offline, minimizing application impact.

What are the main components of Secondary Index for IMS?

The core components are the Index Extractor, which reads the database and extracts index data; the Index Builder, which creates the index structures; and the Secondary Index Call Interceptor, which intercepts DL/I calls.

How does the Secondary Index Call Interceptor work?

The Secondary Index Call Interceptor intercepts DL/I calls from applications. It determines if secondary index processing is required based on the call parameters and the index definitions.

What configuration files are used by Secondary Index for IMS?

Configuration files define the index structure, source database, and processing parameters. These files are used by the Index Extractor and Index Builder to create and maintain the indexes.

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

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

Share Your Product Experience

Secondary Index for IMS

Product Overview

Frequently Asked Questions

What is the primary function of Secondary Index for IMS?

What are the main components of Secondary Index for IMS?

How does the Secondary Index Call Interceptor work?

What configuration files are used by Secondary Index for IMS?

How are the Index Extractor and Index Builder invoked?

How is the Secondary Index Call Interceptor integrated with IMS applications?

What APIs does Secondary Index for IMS expose?

How do the components operate in terms of online/offline processing?

How does Secondary Index for IMS improve application performance?

How does Secondary Index for IMS reduce operational costs?

How does Secondary Index for IMS simplify implementation?

How does Secondary Index for IMS leverage existing security features?

What authentication methods are supported?

What encryption is used and where?

What audit/logging capabilities exist?

How are the Index Extractor and Index Builder monitored?

How is the Secondary Index Call Interceptor monitored?

Where are the configuration parameters defined?

How is user management handled?

Related Products

More from Broadcom

AcceleREXX

ACF2

Allocate DASD Space and Placement

Auditor for z/OS

Automation Point

Bind Analyzer for Db2

Similar Products

_beta access admin

_beta access audit

_beta access easy

_beta access monitor

3270 SUPEROPTIMIZER/IMS

Access Manager for CICS

Help Improve This Directory

Are You a Vendor? Claim Your Listing