A fix is available
APAR status
Closed as program error.
Error description
This APAR fixes the following problems of DBSP IMS HALDB Toolkit 1. The parameters 4GBWARN and SPACE for CHECK funtion do not support OSAM HALDB 8G databases. 2. SYSLMOD of Sample JCL IHCEDBRC and IHCEDBRI should be corrected. 3. When SYSPRINT DD for CONVERT or MAINTAIN is not specified, job fails with U0999. 4. When MACLIB DD for CONVERT is not specified, DBDGEN fails with RC=08. 5. When PSBLIB or IMSACB DD for CONVERT with ONLINE(Y) is not specified, ACBGEN fails with RC=16. 6. When DFSHALDB DD for IHCUDFSH is not specified, no error message is issued. 7. When IMSDALIB DD is not specified and original_dbds DD is specified for CONVERT or ANALYZEPART, job fails with U0999. 8. When SYSPRINT DD for HALDBCOPY is not specified, job fails with U0999. 9. When converting to HALDB under ISPF environment and IHCPSEL0 selection exit is used, CONVUNLOAD job fails with U0999. 10. When using the ISPF user interface with HALDB without DBRC function to convert non-HALDB DBDs to HALDB DBDs, ABENDS0C4 occurs. 11. FASTIC=N keyword for ICEIN control statement should be added.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: Users of IBM IMS Database Solution Pack V2.1 * * IMS HALDB Toolkit * **************************************************************** * PROBLEM DESCRIPTION: This APAR fixes various problems of * * DBSP IMS HALDB Toolkit. * **************************************************************** * RECOMMENDATION: * **************************************************************** This APAR fixes the following problems of DBSP IMS HALDB Toolkit. 1. CHECK function does not accept the value larger than 4095 for the SPACE parameter. 2. 8GBWARN parameter for CHECK function should be added. 3. SYSLMOD DD statement of Sample JCL IHCEDBRC and IHCEDBRI should be corrected. 4. When SYSPRINT DD statement for CONVERT or MAINTAIN is not specified, the job fails with U0999. 5. When MACLIB DD statement for CONVERT is not specified, DBDGEN fails with RC=08. 6. When PSBLIB or IMSACB DD statement for CONVERT with ONLINE(Y) is not specified, ACBGEN fails with RC=16. 7. When DFSHALDB DD statement for IHCUDFSH is not specified, no error message is issued. 8. When the original_dbds DD statement without IMSDALIB DD statement is specified for CONVERT or ANALYZEPART, the job fails with U0999. 9. When SYSPRINT DD statement for HALDBCOPY is not specified, the job fails with U0999. 10. When converting to HALDB under ISPF environment and IHCPSEL0 selection exit is used, CONVUNLOAD job fails with U0999. 11. When using the ISPF user interface with HALDB without DBRC function to convert non-HALDB DBDs to HALDB DBDs, ABENDS0C4 occurs. 12. FASTIC=N keyword for ICEIN control statement should be added.
Problem conclusion
Code has been changed to fix the issues described in this APAR. ======================== = DOCUMENTATION CHANGE = ======================== IBM IMS Database Solution Pack for z/OS Version 2 Release 1 IMS High Availability Large Database Toolkit for z/OS User's Guide (SC19-4102-01) ---------------------------------------------------------------- Chapter 6. Using the HALDB Analyzer Procedure 2. Edit the following parameters: has been changed as follows: Procedure : 2. Edit the following parameters: AVGFSE (lll,hhh) : 4GBWARN (llll,hhhh) The 4GBWARN parameter allows you to set the warning level for used space. None of the data sets can use more than 4 GB (gigabytes). When the data set tries to go beyond this limit, an abend 844 will occur. This is not the high allocation point, but rather the high use point. This point can be indicated by the threshold setting. | 4GBWARN and 8GBWARN are mutually exclusive. Values for both threshold settings (llll and hhhh) are numbers from 0 to 4095 that represent MB (megabytes). The first threshold value (llll) sets the low threshold. You will get a warning when this value is exceeded. If you specify a value of 0, this warning is suppressed. The second threshold value (hhhh) sets the high threshold. You will get a critical warning when this value is exceeded. If you specify a value of 0, this warning is suppressed. Usage: A recommended setting is: 4GBWARN(2500,3500) Resolution: When the partition grows too large, you should split it into two partitions. | 8GBWARN (llll,hhhh) | The 8GBWARN parameter allows you to set the warning level | for used space. None of the data sets can use more than | 8 GB (gigabytes). When the data set tries to go beyond | this limit, an abend 844 will occur. This is not the high | allocation point, but rather the high use point. This | point can be indicated by the threshold setting. | 4GBWARN and 8GBWARN are mutually exclusive. | Values for both threshold settings (llll and hhhh) are | numbers from 0 to 8191 that represent MB (megabytes). | The first threshold value (llll) sets the low threshold. | You will get a warning when this value is exceeded. If | you specify a value of 0, this warning is suppressed. | The second threshold value (hhhh) sets the high | threshold. You will get a critical warning when this | value is exceeded. If you specify a value of 0, this | warning is suppressed. | Usage: A recommended setting is: 8GBWARN(6500,7500) | Resolution: When the partition grows too large, you | should split it into two partitions. SPACE (llll,hhhh) The SPACE parameter allows you to set thresholds for partition size. This parameter can be used to make decisions about partitions. Values for both threshold settings (lllll and hhhh) are | numbers from 0 to 8191 that represent MB (megabytes). The first threshold value (llll) sets the lowest preferred partition size. You will get a warning when the partition size is lower than this value. If you specify a value of 0, this warning is suppressed. The second threshold value (hhhh) sets the high partition size. You will get a critical warning when this value is exceeded. If you specify a value of 0, this warning is suppressed. Usage: A recommended setting is: SPACE(512,3500) Resolution: When a partition is too small, you might want to combine it with the left or right (or both) neighboring partition. The IMS HALDB Toolkit provides the functionality to do this. When a partition becomes too large, it should be split into two partitions.
Temporary fix
Comments
APAR Information
APAR number
PI72202
Reported component name
IM DB SOLUTION
Reported component ID
5655S7700
Reported release
210
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2016-11-11
Closed date
2016-12-16
Last modified date
2017-01-03
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UI43432
Modules/Macros
HAHP210J IHCEDBRC IHCEDBRI IHCPTIL7 IHCSCOUN IHCSCVDS IHCUANAA IHCUANA0 IHCUANA1 IHCUANA2 IHCUANA3 IHCUANA4 IHCUANA5 IHCUANA6 IHCUANA7 IHCUANA8 IHCUANA9 IHCUDFSH IHCULEV0 IHCUTIB0 IHCUTIC0 IHCUUOW0 IHCUUOW1 IHCUUOW2 IHCUUOW3 IHCUUOW9 IHCWANA4 IHCWMI20 IHCWSEL1 IHCWTDB0 IHCWTDB8 IHCYASLK IHCYCCDF IHCYDXMT
SC19410201 |
Fix information
Fixed component name
IM DB SOLUTION
Fixed component ID
5655S7700
Applicable component levels
R210 PSY UI43432
UP16/12/20 P F612
Fix is available
Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.
[{"Line of Business":{"code":null,"label":null},"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSCV358","label":"IMS Database Solution Pack"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"2.1.0"}]
Document Information
Modified date:
23 October 2020