A fix is available
APAR status
Closed as new function.
Error description
Enable IPR Unload utility to process migration unload to a HALDB and fallback unload from a HALDB.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All users of IMS Database Reorganization * * Expert for z/OS Version 4 Release 1 * * (FMID=H25N410), who use the IPR Unload * * utility. * **************************************************************** * PROBLEM DESCRIPTION: This APAR enables IPR Unload utility * * to process migration and fallback * * unload. * **************************************************************** * RECOMMENDATION: Apply the maintenance for this APAR. * **************************************************************** This APAR enables IPR Unload utility to process migration unload to a HALDB and fallback unload from a HALDB. To use the new function, the following maintenance is required: - APAR PM51942 for IMS High Performance Unload (FMID=H1IN120)
Problem conclusion
Temporary fix
Comments
======================== = Documentation Change = ======================== The IBM IMS Database Reorganization Expert for z/OS User's Guide Version 4 Release 1 (SC19-1137-02) should be changed as follows: ================================================================ 4.0 Unloading a database 4.1 IPR Unload utility 4.1.2 IPR Unload features This topic introduces the features of the IPR Unload utility. Fast unloading of IMS databases The IPR Unload utility performs fast unloading of IMS databases, which can increase the efficiency of the database reorganization process. This function is provided by HSSR Engine of IMS HP Unload. : | Migration and fallback unload functions for HALDB | | IPR Unload utility can unload a database to migrate an HIDAM | or HDAM database to a PHIDAM database or a PHDAM database. IPR | Unload utility can also unload a database to do fallback from | a PHIDAM or PHDAM database to an HIDAM or HDAM database. The | unloaded data set created is compatible with the unloaded data | set created by IMS HD Reorganization Unload utility. Dynamic allocation of database data sets : 4.1.4 Restrictions and considerations for IPR Unload The IPR Unload utility has certain restrictions. Restrictions -Database organizations other than HDAM, HIDAM, PHDAM, PHIDAM, HISAM, and SHISAM are not supported. DELETE: | -Migration unload to a HALDB and fallback unload from a HALDB | are not supported. DELETE: | -Migration unload of the secondary index is not supported. | -Migration unload of the HISAM database is not supported. | -If PTR=H or PTR=HB is defined as the parent segment of | virtual logical child, IPR Unload utility does not support | the migration unload of the database. | -Fallback unload of the partitioned secondary index (PSINDEX) | is not supported. -If either of the following segment occurrences is skipped ... : 4.3 IPR Unload JCL statements 4.3.1 JCL requirements for IPR Unload 4.3.1.2 DD statements : DFSVSAMP DD : You must, however, specify DL/I buffers in DFSVSAMP in the following cases: -When you specify BLDLPCK=YES in the HPSIN data set. This is because a DL/I call is issued internally to build an LPCK in that case. | -When you do a migration unload of a database in which a | logical child is defined. In this case, HSSR Engine issues | DL/I calls internally to get information to be written in | the header of the unload record of the logical child. -When APISET=3 is specified in the HPSIN data set or in ... : 4.3.1.3 Using JCL for IMS HD Reorganization Unload 4.3.1.3.3 Restrictions : DELETE: | -If MIGRATE or FALLBACK is specified in the SYSIN data set, | the FABHURG1 unload utility of IMS HP Unload is invoked | instead of the IPR Unload utility. DELETE: 4.3.2.3 Control statements for unload function : Table 25. Control statements for unload function +-----------+------------+--------+--------------------------+ |Keyword |Acceptable |Default |Description | | |values | | | +-----------+------------+--------+--------------------------+ : : : : : |+-----------+------------+--------+--------------------------+ ||FALLBACK |YES or NO |NO |Specifies whether to | || | | |fallback unload of HALDB | || | | |or not. | |+-----------+------------+--------+--------------------------+ : : : : : |+-----------+------------+--------+--------------------------+ ||MIGRATE |YES or NO |NO |Specifies whether to | || | | |migration unload of | || | | |non-HALDB or not. | |+-----------+------------+--------+--------------------------+ : |4.3.2.3.5a FALLBACK control statement | | This optional control statement is used to initiate the | fallback unload of a partitioned database. | _______________________________________________________ | | __NO ________ | | | >>__FALLBACK=_____|__YES_________|_________________>< | | |_______________________________________________________| | | NO | no perform the fallback unload of a partitioned database. | | YES | perform the fallback unload of a partitioned database. | | Notes: | 1.FALLBACK=YES cannot be specified with a control statement of | PARTITION or MIGRATE=YES. | 2.If FALLBACK=YES is specified, multiple OUTPUT control | statements cannot be specified. | 3.If FALLBACK=YES is specified, the unloaded data format for | the OUTPUT control statement must be *HD. | 4.The input database must be either a PHIDAM or a PHDAM. : |4.3.2.3.8a MIGRATE control statement | | This optional control statement is used to make IPR Unload | perform the migration unload of a nonpartitioned database. | _______________________________________________________ | | __NO ________ | | | >>__MIGRATE=_____|__YES_________|__________________>< | | |_______________________________________________________| | | NO | no perform the migration unload of a nonpartitioned database | . | YES | perform the migration unload of a nonpartitioned database. | | Notes: | 1.MIGRATE=YES cannot be specified with a control statement of | PARTITION or FALLBACK=YES. | 2.If MIGRATE=YES is specified, multiple OUTPUT control | statements cannot be specified. | 3.If MIGRATE=YES is specified, the unloaded data format for | the OUTPUT control statement must be *HD. | 4.The input database must be either a HIDAM or an HDAM | database. If PTR=H or PTR=HB is defined as the parent | segment of virtual logical child, IPR Unload does not | support the migration unload of the database. Migration | unload of a secondary index or HISAM database is not | supported. | 5.If a logical child is defined in the input database, and | you want better performance, code an appropriate number of | IMS buffer pools in DFSVSAMP DD of your JCL. 4.3.2.3.9 OUTPUT control statement Specifies output characteristics of an IPR Unload utility job. If you want to use a user exit routine, specify the routine name and the type of user exit interface (A or B). | Notes: | 1. The IPR Unload utility supports two types of user exit interface. Unless your user exit was used for FABHFSU unload utility of IMS HP Unload, select the Type-B user exit interface by specifying OUTPUT=,,(rtnname,B). For more information, see "User exits for IPR Unload" in topic 4.6. | 2.If MIGRATE=YES or FALLBACK=YES is specified, multiple OUTPUT | control statements cannot be specified. : 4.3.2.3.10 PARTITION control statement : partlist : Note: If PARTITION=partlist is specified and one or more partitions of PHDAM or PHIDAM are in a HALDB OLR cursor-active status, the IPR Unload utility ends abnormally. | Note: This control statement cannot be specified with a | MIGRATE=YES or FALLBACK=YES control statement. 8.2 Messages and codes 8.2.3 Messages 8.2.3.6 HPSU messages | HPSU3030E xxxxxxxx AND yyyyyyyy STATEMENTS ARE MUTUALLY | EXCLUSIVE | | Explanation: The control statements xxxxxxxx and yyyyyyyy are | mutually exclusive. | System action: The IPR Unload utility issues message HPSU3360E | and ends its processing. | User Response: Correct the specification of the HPSIN DD | statement. If you use the JCL for IMS HD Reorganization Unload | , correct the specification of SYSIN DD statement. Then, rerun | the IPR Unload job. | HPSU3031E OUTPUT CANNOT BE SPECIFIED MORE THAN ONCE IF | MIGRATE=YES|FALLBACK=YES IS SPECIFIED | | Explanation: When the MIGRATE=YES or FALLBACK=YES control | statement is specified, two or more OUTPUT control statements | cannot be specified. | System action: The IPR Unload utility issues message HPSU3360E | and ends its processing. | User Response: Correct the specification of the HPSIN DD | statement. Then, rerun the IPR Unload job. | HPSU3032E INVALID UNLOAD FORMAT IS SPECIFIED WITH | MIGRATE=YES|FALLBACK=YES | | Explanation: A format other than *HD is specified on the | OUTPUT control statement, although the MIGRATE=YES or | FALLBACK=YES is specified. | System action: The IPR Unload utility issues message HPSU3360E | and ends its processing. | User Response: Specify the *HD format for the OUTPUT control | statement. Then, rerun the IPR Unload job. | HPSU3206E xxxxxxxx IS SPECIFIED FOR AN UNSUPPORTED DB TYPE | | Explanation: The xxxxxxxx control statement cannot be used | for this database. | System action: The IPR Unload utility ends abnormally. | User Response: Correct the control statement. =================== END OF DOC-CHANGE =======================
APAR Information
APAR number
PM51943
Reported component name
IMS DB REORG EX
Reported component ID
5655F7400
Reported release
410
Status
CLOSED UR1
PE
NoPE
HIPER
NoHIPER
Special Attention
YesSpecatt / New Function / Xsystem
Submitted date
2011-11-09
Closed date
2011-12-18
Last modified date
2012-01-01
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UK74939
Modules/Macros
HPSGCSC1
Fix information
Fixed component name
IMS DB REORG EX
Fixed component ID
5655F7400
Applicable component levels
R410 PSY UK74939
UP11/12/20 P F112
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.
[{"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSVL5Q","label":"IMS Database Reorganization Expert for z\/OS"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"4.1.0","Edition":"","Line of Business":{"code":"LOB35","label":"Mainframe SW"}}]
Document Information
Modified date:
06 January 2023