IBM Support

Updates to IMS Database Solution Pack V2.2: IMS HALDB Toolkit User's Guide (SC27-9038-02)

Release Notes


Abstract

Updates that apply to IMS Database Solution Pack V2.2: IMS HALDB Toolkit User's Guide (SC27-9038-02).

Content

The most recent updates appear at the top of the list.

Update 2
Date of change: January 2021
Change description: Documentation changes by APAR PH32843.
Topic: HALDB utilities >  Using the HALDB Analyzer

”About this task” has been changed as follows.

About this task

  :

Partition selection
        A root segment in a partition is not found in the same partition when searched by partition selection.
Randomizer error
        A call to the randomizer using an existing root segment does not return a zero return code. This warning is performed for the standard IMS randomizer (DFSHDCnn) only.
ILKs in error
        The ILK of a segment is invalid.
Duplicate ILKs
        There should not be any duplicate ILKs.
Missing ILEs
        EPS pointer requires pointer healing, but there is no corresponding ILE.

A return code of 8 is set when any of these situations is detected.

start of change

Invalid ILKs
        The ILK of a segment is invalid.       

A return code of 4 is set when invalid ILKs are detected.

When invalid ILKs are detected:  

  • Run IMS High Performance Pointer Checker as necessary and make sure that no errors are detected. 
  • Invalid ILKs do not immediately indicate the database failure. If no errors other than invalid ILKs are detected, you can continue to use the database because invalid ILKs do not cause immediate problems. However, if you continuously reorganize the database or run the HTK MAINTAIN function as is, ILKs might become duplicated. To prevent duplicated ILKs, consider performing the following tasks:  

 1) Resolve invalid ILKs. 

To resolve invalid ILKs, use either of the following methods to reset ILKs:  

  • Method 1: Unload and reset ILKs by using the HTK RESETILK function, then reload. For more information about the HTK RESETILK function, see "Recovering by using the ILK reset utility".   
  • Method 2: Unload all partitions, then reload by IMS HP Load with the REPAIRILK=YES option. For more information about the REPAIRILK=YES option of IMS HP Load, see the IMS High Performance Load User's Guide.   

You must process all partitions in either method. Also, you must rebuild the PSINDEX.    

 2) Specify the REORGV parameter on the INIT.RECON command or the CHANGE.RECON command.  

Invalid ILKs might be detected if the database was being used without the HALDB reorganization number verification function of IMS and if you changed, by using functions such as HTK MAINTAIN, a high key that defines a boundary between partitions of the HALDB. If you need to change a high key for partitions, it is recommended that you specify the REORGV parameter on the INIT.RECON command or the CHANGE.RECON command to prevent invalid ILKs.   

The HALDB reorganization number verification function of IMS is activated by specifying the REORGV parameter on the INIT.RECON command or the CHANGE.RECON command. If the REORGV parameter is not specified on these commands, the default (the HALDB reorganization number verification function of IMS deactivated) is used.

  • If ILK validation is not required, specify VERIFYILK(N). However, consider validating ILKs by specifying VERIFYILK(Y) if either or both of the following conditions are met:   

 1) If a HALDB has secondary indexes (PSINDEXes).

 2) If the database was being used without the HALDB reorganization number verification function of IMS. Also, after performing one or more of the following tasks:  

  • Initialized the partitions of the HALDB after the partitions were used
  • Added partitions to the HALDB
  • Changed a high key that defines a boundary between partitions of the HALDB

When duplicated ILKs are detected:  

  •  To resolve duplicate ILKs, reset ILKs. For details on how to reset ILKs, see the explanations for invalid ILKs.     

end of change

Performance and administration parameters allow you to set threshold levels for the components being monitored by the HALDB Analyzer.
  ...


Update 1
Date of change: December 2020
Change description: Documentation changes by APAR PH30210. This APAR enhances IMS HALDB Toolkit to support encrypted OSAM database data sets.
Topics: Changes apply to multiple topics.

------------------------------

Topic: Introduction to IMS HALDB Toolkit > IMS HALDB Toolkit overview > Usage and restrictions

"Restrictions for OSAM LDSs" has been added after "Database limitations":

Database limitations

...

The MAINTAIN function processes PSINDEXes only when the PSINDEXes are offline.

start of change

Restrictions for OSAM LDSs

end of change
------------------------------

Topic: Converting to a HALDB > Converting to HALDB using CONVERT > CONVERT command parameters

CONVERT command parameters have been modified as follows:

Table. CONVERT command parameters

(Table 9 in PDF)

Parameter Requirement Description
... ... ...
DATACLAS ... ...
start of changeDATACLSL
Optional

Specifies the name of the data class for the new SMS-managed ILDS data sets that IMS HALDB Toolkit dynamically allocates.

If the database data sets of the primary database, from which the ILDS data sets are created, are encrypted OSAM data sets and have the Extended Addressability attribute, you must specify a data class without the Extended Addressability attribute for the ILDS data sets.

If the database data sets, from which the ILDS data sets are created, do not have the Extended Addressability attribute, this parameter is ignored.

Format: (dataclas)
Default value:
If omitted, the default action is to copy from existing data sets. end of change

DBD ... ...
... ... ...
ICTRLR ... ...
start of changeICVOLCT Optional

Use this keyword to specify the number of volumes to allocate for image copy data sets.

If an image copy data set requires more space than is available on a single volume, specify a value larger than 1.

The ICVOLCT value is applied to all image copy data sets that are dynamically defined in the IMS HALDB Toolkit job. 

Format: (1-20)
Default value: end of change

IMSID ... ...
... ... ...

------------------------------

Topic: Maintaining HALDBs > Maintaining HALDB using MAINTAIN > MAINTAIN command parameters

MAINTAIN command parameters have been modified as follows:

Table. MAINTAIN command parameters

(Table 13 in PDF)

Parameter Requirement Description
... ... ...
ICTRLR ... ...
start of changeICVOLCT Optional

Use this keyword to specify the number of volumes to allocate for image copy data sets.

If an image copy data set requires more space than is available on a single volume, specify a value larger than 1.

The ICVOLCT value is applied to all image copy data sets that are dynamically defined in the IMS HALDB Toolkit job. 

Format: (1-20)

Default value: end of change

IMSID ... ...
... ... ...

------------------------------

Topic: Troubleshooting > Messages and codes > Batch messages

The following messages have been added as follows:

start of change

IHC01190I DSN: dsname has Extended Addressability attribute

Explanation: The database data sets of the primary database, from which the ILDS data sets are created, have the Extended Addressability attribute.

System action: Processing continues.

User response: None. This message is informational.

end of change

start of change

IHC01191I DATACLSL parameter specification is used for ILDS DATACLAS

Explanation: The DATACLSL parameter specification is used for the data class of the ILDS data sets.

System action: Processing continues.

User response: None. This message is informational.

end of change

start of change

IHC01192E Specify DATACLSL parameter for ILDS DATACLAS

Explanation: The database data sets of the primary database, from which the ILDS data sets are created, have the Extended Addressability attribute, but the DATACLSL parameter is not specified. You must specify a data class without the Extended Addressability attribute for the ILDS data sets.   

System action: Processing stops.

User response: Specify the DATACLSL parameter and rerun the job.

end of change

start of change

IHC01193E Both OSAM sequential data sets and OSAM LDSs are used as input DBDS

Explanation: The MAINTAIN function does not support the mixed use of OSAM sequential data sets and VSAM linear data sets (OSAM LDSs) as input DBDS.  

System action: Processing stops.

User response: Even when both OSAM physical sequential data sets and VSAM linear data sets (OSAM LDSs) are used in HALDB, you can run the MAINTAIN function if the PARTITION or PARTLIST parameter of the MAINTAIN function specifies either OSAM physical sequential data sets or VSAM linear data sets (OSAM LDSs), not both, as DBDS of the target partition. Rerun the job as necessary. 

end of change

  • The CONVERT and MAINTAIN functions do not support image copy of VSAM linear data sets (OSAM LDSs) to DASD when the CI size of the data sets is 32K. 
  • The MAINTAIN function does not support the mixed use of OSAM sequential data sets and VSAM linear data sets (OSAM LDSs) as input DBDS.   

Publication Number

SC27-9038-02

[{"Line of Business":{"code":"LOB35","label":"Mainframe SW"},"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SSS8QJ","label":"IMS Database Solution Pack for z\/OS"},"ARM Category":[{"code":"a8m0z000000cvYdAAI","label":"IMS High Availability Large Database (HALDB) Toolkit for z\/OS"}],"Platform":[{"code":"PF035","label":"z\/OS"}],"Version":"2.2.0"}]

Document Information

Modified date:
19 January 2021

UID

ibm16369571