Space announcement


This space provides the same content as before, but the organization of the home page has changed. The content is now organized based on logical branches instead of legacy book titles. We hope that the new structure will help you quickly find the content that you need.

Fast Path Indexer/EP capabilities

Fast Path Indexer/EP lets you build and maintain indexes that are associated with primary DEDBs.

When IMS updates the database, Fast Path Indexer/EP updates the associated indexes. The product can also ensure that the database and its indexes remain synchronized if an IMS failure or database recovery occurs.

Fast Path Indexer/EP lets your applications perform the following functions:

  • partition an index

    You can build a partitioned index and include as many as 500 partitions in the index. Each partition can be up to 4 GB.

  • process an index as a stand-alone database

    You can process an index that was created with Fast Path Indexer/EP as a stand-alone database for retrievals. This processing method lets you retrieve information while improving system performance.

  • create 500 indexes

    Whether you choose the SHISAM structure or the HISAM structure, you can build up to 500 indexes. If you partition an index, you can include 500 partitions.

  • create index keys from five source fields

    You can use up to five fields from the primary DEDB segment to create the index key. You can use any field in the segment as the key in the index. If the primary DEDB data is not unique, you must use the subsequence field to force uniqueness.

  • create multiple index records

    You can create multiple index records from one source segment of an index.

  • store duplicate data

    You can include up to five duplicate data fields that you obtained from the primary DEDB segment in the index.

  • maintain indexes

    Fast Path Indexer/EP lets you populate the index only with data that meets specific criteria. For example, you can ignore records from the primary DEDB that contain blanks or zeros by using the NULLVAL keyword or the sparse indexing exit (secondary index database maintenance exit) routine.

  • use an inverted hierarchy

    Fast Path Indexer/EP supports an inversion of hierarchy up to the root segment. To use an alternate processing sequence, you must specify the PROCSEQ keyword.

Was this page helpful? Yes No Submitting... Thank you