A fix is available
APAR status
Closed as program error.
Error description
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: Users of IBM IMS Database Utility Solution * * V1.1 IMS HALDB Toolkit * **************************************************************** * PROBLEM DESCRIPTION: Forward fit of DBSP V2.1 IMS HALDB * * Toolkit APAR PI66737 and PI72202. * **************************************************************** * RECOMMENDATION: Apply the maintenance for this APAR. * **************************************************************** I This APAR fixes the following problems (FF of PI66737): 1. When running COPYDBRC with DFDSS(Y), an incorrect RENUNC statement can be generated. 2. When running MAINTAIN with ONLINE(Y) and NOOSAM8G(Y) for a HALDB registered as OSAM8G in the RECON data sets, the database access can be failed after MAINTAIN. 3. When running the split unload file utility (IHCUSPLT) with multiple input files, each partition unload file can contain multiple trailer records. 4. When running ISPF MAINTAIN with PARTSIZE >= 4096 for a HALDB using VSAM, and total amount of data exceeds 4 giga bytes, reload can be failed. 5. When running ISPF CONVERT with PARTSIZE >= 4096 for a non-HALDB using VSAM, INIT.DB can be failed. 6. When IHCUAPI INIT call is issued, partition selection API fails with RC=16, RSN=513. 7. When IHCRRC00 is used instead of DFSRRC00, loading logical children fails with ABENDS806. 8. When running MAINTAIN or CONVERT with HP Load utility and a partition selection exit other than IHCPSEL0 is used, HP Load can be failed with U3770. 9. When IMS Library Integrity Utilities load module library is included in the STEPLIB of CONVERT or MAINTAIN job, temporary log data sets are unnecessarily registered in the RECON data sets. II This APAR fixes the following problems (FF of PI72202): 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 Utility Solution for z/OS Version 1 Release 1 IMS High Availability Large Database Toolkit for z/OS User's Guide (SC27-9007-00) ---------------------------------------------------------------- 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
PI73540
Reported component name
IMS HA DB TOOLK
Reported component ID
5655DBU01
Reported release
110
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2016-12-09
Closed date
2017-01-10
Last modified date
2017-02-01
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UI43769
Modules/Macros
HIHC110J IHCEDBRC IHCEDBRI IHCPTIL7 IHCSCOUN IHCSCVDS IHCUANAA IHCUANA0 IHCUANA1 IHCUANA2 IHCUANA3 IHCUANA4 IHCUANA5 IHCUANA6 IHCUANA7 IHCUANA8 IHCUANA9 IHCUAPI IHCUDFSH IHCULEV0 IHCUTIB0 IHCUTIC0 IHCUUOW0 IHCUUOW1 IHCUUOW2 IHCUUOW3 IHCUUOW9 IHCWANA4 IHCWCPY0 IHCWDBL0 IHCWDSN0 IHCWLOD2 IHCWMIAU IHCWMI00 IHCWMI20 IHCWPROJ IHCWPRUP IHCWRC00 IHCWSEL1 IHCWSEL4 IHCWSPLT IHCWTDB0 IHCWTDB1 IHCWTDB8 IHCWWANA IHCYASLK IHCYCCDF IHCYDBD0 IHCYDBD4 IHCYDBR0 IHCYDXMT IHCYLGDB IHCYLIU0 IHCYSVLS
SC27900700 |
Fix information
Fixed component name
IMS HA DB TOOLK
Fixed component ID
5655DBU01
Applicable component levels
R110 PSY UI43769
UP17/01/12 P F701
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":"SSCBQAP","label":"IMS HALDB Toolkit"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"1.1.0"}]
Document Information
Modified date:
20 October 2020