What's new in IMS Index Builder
This topic summarizes the technical changes for this edition.
New and changed information is denoted by carets (
and 
) at the beginning and end of the new or changed information. Editorial
changes that have no technical significance are not noted.
Revision markers follow these general conventions:
- Only technical changes are marked; style and grammatical changes are not marked.
- If part of an element, such as a paragraph, syntax diagram, list item, task step, or figure is changed, the entire element is marked with revision markers, even though only part of the element might have changed.
- If a topic is changed by more than 50%, the entire topic is marked with revision markers (so it might seem to be a new topic, even though it is not).
Revision markers do not necessarily indicate all the changes made to the information because deleted text and graphics cannot be marked with revision markers.
SC18-9101-09 (April 2024)
| Description | Related APARs |
|---|---|
| Updated the description of PROC control statement. When a job requests that all secondary indexes be rebuilt but IMS Index Builder does not find any secondary indexes, IMS Index Builder issues a warning message and ends the job with return code 4. | N/A |
SC18-9101-08 (October 2021)
| Description | Related APARs |
|---|---|
| Support for encrypted IMS OSAM databases. The following topic is updated: ZIIPMODE control statement | PH21514 |
SC18-9101-07 (July 2018)
| Description | Related APARs |
|---|---|
| Support for IMS 15. | PI92715, PI88851, PI83668, PI77681, PI73092, PI72375, PI65714, PI61398, PI59810 |
| New control statement, PROGMON, to specify the interval for issuing load progress messages. For more information, see PROGMON control statement. | |
| Enhancement to support the PARTNAME control statement when building PSINDEX databases. For more information, see PARTNAME control statement. | |
| Support for update mode, to update only the existing records in PSINDEX databases. For more information, see PROC control statement. | |
| Enhancement to support retrieving DBDs from the IMS catalog directory data sets instead of DBD libraries. For more information, see Using the IMS catalog. | |
| New control statement, ZIIPMODE, to offload eligible workloads to zIIP processors. For more information, see ZIIPMODE control statement. | |
| Restrictions for using IMS exit routines documented in IMS Index Builder restrictions. |
SC18-9101-06 (March 2016)
| Description | Related APARs |
|---|---|
| Support for IMS 14. | PI58843, PI56192, PI51722, PI48799, PI32727, PI28218, PI27638 |
| Support for HALDB 8 GB OSAM data sets. | |
| New control statement, COMPAUTH. See COMPAUTH control statement. | |
| Security improvement. All the libraries concatenated to the STEPLIB and JOBLIB must be APF-authorized without exception. The DFSRESLB DD statement is no longer needed in IMS Index Builder JCL. |
SC18-9101-05
| Description | Related APARs |
|---|---|
| Support for IMS 13. | PI24092, PI21471, PI18256, PI15217, PI10953, PI06319, PI05347, PM97423, PM94114, PM92801, PM89774, PM86783, PM78145, PM76131, PM75258, PM74179 |
| When IMS Index Builder builds a HALDB primary index or an ILDS, it issues database authorization requests with EXCLUSIVE access intent for the HALDB partition instead of READ access intent. See DBAUTH control statement. | |
| If the DBAUTH YES,RECOV control statement is specified, IMS Index Builder issues the CHANGE.DBDS RECOV command to turn on the RECOVERY_NEEDED flag before requesting database authorization. See DBAUTH control statement. | |
| New control statements for overriding the job name of subordinate address space and the volume count for each sort stripe data set. See the following topics: | |
| Support for the IMS Tools Online System Interface of IBM® IMS Tools Base for z/OS®. By using the interface, IMS Index Builder can automatically issue IMS commands (/DBD, /DBR, and /STA) so that you do not need to issue these IMS commands manually. See the following topics: | |
| New parameter *NO for ITKBLOAD and ITKBSRVR control statements. When ITKBLOAD *NO is specified, the IMS Tools Knowledge Base library that is concatenated to the STEPLIB DD is not used. See the following topics: | |
| Revised installation and operational prerequisites. See Hardware and software requirements. |
SC18-9101-04
| Description | Related APARs |
|---|---|
| Supports parallel sorting of PSINDEXes. You can sort the partitions in parallel to improve the performance of building PSINDEXes. For more information, see MAXTASKS control statement. | PM68881, PM66456, PM64823, PM60941, PM56986, PM53350, PM49636, PM49620, PM46957, PM46849 |
| New reason codes (901, 902, and 903) and an error message (IIUB080E) have been added to alert when block size is zero. | |
| ILDS control statement, which specifies to initialize Indirect List Data Sets (ILDSs) without loading ILE records, has been added. For more information, see ILDS control statement. | |
| A new message (IIUB081I) to alert when the processed HALDB has logical relationships and ILE records need attention. | |
| WFP output files of IMS High Performance Load can be used as input for building PSINDEXes. For more information, see Building partitioned secondary indexes using HPSRWFP as input. | |
| Configuration steps for enabling the DBRC command authorization have been added. For more information, see Configuring for DBRC command authorization. | |
| Indexes and indirect list data sets (ILDS) for IMS catalog databases can be built. For more information, see Building indexes and ILDSs for IMS catalog databases. |
SC18-9101-03
| Description | Related APARs |
|---|---|
| Support for IMS 12. | PM42233 PM37987, PM37055, PM34562, PM31946, PM30368, PM27122, PM26050, PM23498, PM23259, PM22120, PM21662, PM19218, PM17740, PM17738 |
| The CLASS control statement specifies the high-level qualifier of stripe data sets. For more information, see CLASS control statement. | |
| The ITKBLOAD control statement specifies the name of the load module library for IMS Tools Knowledge Base. For more information, see ITKBLOAD control statement. | |
| The DBAUTH control statement specifies whether IMS Index Builder issues the IMS DBRC authorization request for the prime database and the indexes to prevent transactions and programs from updating the database. The IMS DBRC authorization request can be issued in IMS 10 and later. For more information, see DBAUTH control statement. | |
| The SVCDUMP control statement specifies whether IMS Index Builder requests an SVC dump file after a system abend or a user abend. For more information, see SVCDUMP control statement. | |
| The IIURDFLT MAXTASKS entry of the runtime option module (IIURPRMS) customizes the IMS Index Builder run. For more information, see IIURDFLT MAXTASKS entry. | |
| The IIUB062I message is added to indicate a dynamic allocation failure of a stripe data set and its cause. | |
| Restrictions for using IMS Index Builder are now documented in IMS Index Builder restrictions. | N/A |
| IMS Index Builder does not support shared secondary indexes. Information about this limitation is added to IMS Index Builder restrictions. | N/A |
| Revised the instructions to activate IMS Index Builder. See Activating IMS Index Builder. | N/A |
SC18-9101-02
| Description | Related APARs |
|---|---|
| Description about the sequential scan technology that was introduced in IMS Index Builder 3.1 and the instruction to change the scan methods are added. For more information, see Selecting the scan method. | PM13947, PM12486, PM10758, PM06592, PM05407, PM04978, PM04676, PM01565, PM01160, PK98315, PK98192, PK90640, PK89282, PK84777 |
| The SIDXBUF control statement enables you to specify the number of buffers that are to be used in the load process for each secondary index. For more information, see SIDXBUF control statement. | |
| The TMRWAIT control statement enables you to specify the IIUTMRXT timeout value. For more information, see TMRWAIT control statement. | |
| The VIC control statement specifies whether IMS Index Builder issues the DBRC NOTIFY.UIC command to turn off the IC NEEDED flag. For more information, see VIC control statement. | |
| A JCL sample is provided to replace the runtime option module (IIURPRMS). Also, several entries are added to the IIURPRMS module table. For more information, see Defining runtime parameters. | |
| The verification function of IMS Index Builder verifies that the number of records that were loaded to each index matches the number of the scanned occurrences of the prime database. For more information, see IMS Index Builder verification phase failure reason codes. | |
| Diagnostics Aid is supported for diagnosing and reporting IMS Index Builder problems. For more information about using the Diagnostics Aid, see Diagnostics Aid. |
SC18-9101-01
| Description | Related APARs |
|---|---|
| Instruction to migrate from IMS Index Builder 2.3 to IMS Index Builder 3.1 is added. See Migrating from IMS Index Builder 2.3 to IMS Index Builder 3.1. | PK84520, PK82341, PK73802, PK73601, PK73170, PK72674 |
| Support for IMS 11. | |
| The SORTFSZ control statement is used to support heavy sort loads, which is different from IMS Index Builder 2.3. For more information, see IMS Index Builder input control statements. | |
| SORTFSZ triggers striped sort mode. | |
| Run time optimized code (race code) is applied by default in IMS Index Builder encoding routines. | |
| A standard, single subordinate address space procedure, started task is invoked by job name. | |
| Runtime parameters have changed. For more information, see Defining runtime parameters. | |
| The number of STCs can be controlled with the MAXTASKS control statement. | |
| Stripe data sets have been introduced to enhance communications with subordinate address space. Stripes are internal work files with specific HLQ. | |
| Index records with duplicate keys are stored in stripes with LLQ "DUPLKEYS." Duplicate keys stripes are not deleted at termination. | |
| IMS Index Builder does not shadow the index data sets, so the CATLG statement is obsolete. However, in the DDEFPDS functionality, user catalogs are required to be supported by DD statements. |
SC18-9101-00
| Description | Related APARs |
|---|---|
| Support for enabling the IMS Tools Knowledge Base has been added. The IMS Tools Knowledge Base is a central repository for automatically collecting output reports that are generated. For more information, see IMS tools product integration and the ITKBSRVR statement definition in IMS Index Builder input control statements. | N/A |
| This release supports routing WTOs and messages from the subordinate address space to the master address space. For more information, see the IIUCAPT DD statement definition in IMS Index Builder JCL. | N/A |
| The IMS Index Builder load library is no longer needed in the IMS concatenation. For more information, see the STEPLIB DD statement definition in IMS Index Builder JCL. | N/A |
| Allocation contention problems have been resolved in this release. The ALTER statement is no longer needed. | N/A |
| Support for indirect list data sets (ILDS) is provided in this release with the BLD_ILDS keyword. For more information, see the PROC statement definition in IMS Index Builder input control statements. | N/A |
| Support for rebuilding selected PSINDEX partitions has been added. For more information, see the INDEX statement definition in IMS Index Builder input control statements. | N/A |
| The scope of sequential scan has been extended to allow for rebuilding of ILDS, primary indexes, and some secondary indexes. For more information, see Defining the subordinate address space procedure. | N/A |
| The RACF profile is now passed from the master address space to the subordinate address space. For more information, see Defining the subordinate address space procedure. | N/A |
| IMS Index Builder will correctly process indexes with non-unique keys. | N/A |
| This release of IMS Index Builder can process an unlimited number of PSINDEX partitions. | N/A |
The following DD statement is no longer supported:
|
N/A |
The following control statements are no longer supported. If they are used,
warning messages are issued that the statement is no longer
supported, and IMS
Index Builder
continues processing.
|
N/A |
| IDCAMS processing of the data sets is completed in the initialization and registration phases, before building the processing structures. IIUB053E is introduced to denote IDCAMS processing failure in the data set description block. IIUB100E reason 109 at initialization phase ends if IDCAMS failures have been encountered. In the registration phase, IIUB029E is used. | N/A |
| DEL/DEF support is integrated to data set IDCAMS processing. See the DDEFPDS DD statement. | N/A |
| Data set initializations are processed entirely during the initialization phase. | N/A |
| The index load report has been enhanced. Separate report blocks are provided at data set/partition level, and a summary block is introduced at secondary index/PSINDEX level. The rejected records are reported in the summary block, and for PSINDEXes, the sum of the partition records is provided. | N/A |
| IMS Index Builder will always use DBRC for HALDB databases. If the INPUT control statement specified DBRC=N, no notification is issued, regardless of the database type. In prior IMS Index Builder versions, notifications were always issued for HALDB databases. | N/A |
| BLD_SECONDARY specifies that secondary index databases must be built. If the prime database does not have secondary indexes, an error is indicated, and IMS Index Builder stops at the initialization phase. In prior IMS Index Builder versions, an error was not indicated. | N/A |