A fix is available
APAR status
Closed as new function.
Error description
This APAR provides the following functional enhancements to the IPR Driver: 1. NEWDBD=YES allows removing or adding secondary indexes of a non-HALDB in a new DBD. 2. NAMESWAP=YES is allowed for a non-HALDB with external logical relationships. 3. IC=YES is allowed for a non-HALDB that has no direct pointers in logical relationships.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All users of IPR Driver of IMS Parallel * * Reorganization for z/OS Version 3 Release 2 * * (FMID=H25N320) * **************************************************************** * PROBLEM DESCRIPTION: This APAR provides the functional * * enhancemsnts for IPR Driver. * **************************************************************** * RECOMMENDATION: Apply the maintenance for this APAR. * **************************************************************** This APAR provides the following functional enhancements : 1. IPR Driver allows the NEWDBD=ddname control statement and adding or deleleting secondary indexes in the new DBD. 2. IPR Driver allows the NAMESWAP=YES control statement to swap data set names of a non-HALDB that has external logical relationships. Users have to run IMS Prefix Resolution and Update utilities after the IPR Driver job steps. 3. IPR Driver allows the IC=YES control statement to take image copies for a non-HALDB that has logical relationships only by symbolic pointers. The database don't need IMS Prefix Resolution and Update. Both ICTYPE=A and B are available. The following minor changes are also added: 4. If PREFIXRES=YES is specified and the database has external logical relationships, IPR Driver ignores PREFIXRES=YES, continues the unload and reload processing, and returns the return code 4 with the message HPSG0379W: HPSG0379W PREFIX RESOLUTION AND UPDATE ARE NEEDED FOR DBD=dbdname Prefix Resolution and Update utilities are required after IPR Driver job steps. 5. If a VSAM component name is longer than 42 characters and NAMESWAP=YES is specified, IPR Driver issues the error message HPSG0348E and terminates before starting of the reorganization processing. Image copy or Pointer Checker might return a non-zero return code with the following messages: -DFS305A DBD/PSB LIBRARY DOES NOT CONTAIN DBD/PSB dbdname -FABP4006W DB: dbdname DB#: 00X WAS NOT SCANNED FOR LOGICALLY RELATED DB -FABP1995E MISMATCH BETWEEN THE NUMBER OF SEGMENTS IN SEG The errors will disappear after applying the following APARs: - PK42644 IMS High Performance Image Copy (FMID:H1J0410) - PK40389 IMS High Performance Pointer Checker (FMID:HPC2220)
Problem conclusion
Temporary fix
Comments
======================== = Documentation Change = ======================== IBM IMS Parallel Reorganization for z/OS User's Guide (SC18-9228-02) should be changed as follows: ================================================================ 2.2.2 Restrictions on Image Copy processing The following restrictions apply to the Image Copy processing: - The following database organizations are not supported: - HDAM or HIDAM databases that have external logical | relationships that need Prefix Resolution and Update. - HISAM databases that have logical relationships because IMS High Performance Prefix Resolution does not support such a database. For details, see "External logical relationships of HDAM and HIDAM" in topic 2.6.5.2, "Logical relationship of | HISAM" in topic 2.6.5.3, and "Logical relationships that do | not need Prefix Resolution and Update" topic 2.6.5.4. : ================================================================ 2.4.1 Parallel Reorganization of a non-HALDB : 3. Post-reorganization processing: The post-reorganization : D If the database has external relationships, you cannot D specify NAMESWAP=YES and you must do the post-reorganization D processing manually. For details, I For a database that has external relationships, see "Post-reorganization processing for database with logical relationships" in topic 2.9.5. ================================================================ 2.6.5.2 External logical relationships of HDAM and HIDAM If an HDAM or a HIDAM database has at least one external logical relationship, you cannot specify IC=YES, and : with logical relationships" in topic 2.9.5. | For the logical relationships that uses only symbolic | pointers, see "Logical relationships that do not need Prefix | Resolution and Update" in topic 2.6.5.4. ================================================================ | 2.6.5.4 Logical relationships that do not need | Prefix Resolution and Update | | For the following databases that have logical relationships, | you can specify IC=YES and either ICTYPE=A or B to take image | copies, because the prefix resolution and update utilities | are not needed: | - The logical parent database for which DBIL is not specified | in the Prereorganization utility. | - The logical child database that contains no direct logical | pointers. Only symbolic pointers are used. ================================================================ 2.6.6.1 Type-A Image Copy processing : | - HDAM, HIDAM, and HISAM that do not need Prefix Resolution and Update for logical relationships - SHISAM ================================================================ 2.7.8.12 IC control statement : You can specify IC=YES for a non-HALDB that has internal logical relationships and has no external logical relationship. For such a database, you must also specify PREFIXRES=YES. | For the databases with logical relationships, which do not | need Prefix Resolution and Update after the IPR Driver | job step, you can specify IC=YES. For the details, see | "Logical relationships that do not need Prefix Resolution and | Update" in topic 2.6.5.4. ================================================================ 2.7.8.18 NAMESWAP control statement : Notes: : | 2. Even if an HDAM or a HIDAM database that has logical | relationships, you can specify NAMESWAP=YES. | For external logical relationships, you have to run | IMS Prefix Resolution and Prefix Update utilities after | the IPR Driver job steps. For the post-reorganization processing for these databases, see "Post-reorganization processing for database with logical relationships" in topic 2.9.5. ================================================================ 2.7.8.20 NEWDBD control statement : Supported DBD changes: When using a new DBD for a non-HALDB, you can change any DBD parameters except the following: : D - adding or deleting secondary indexes : | If a new secondary index is added and you want to run | the IPR Driver job with DBRC=Y and NAMESWAP=YES, | you must issue the DBRC INIT.DB command to register | the new secondary index in advance. ================================================================ 2.7.8.25 PREFIXRES control statement The PREFIXRES control statement specifies whether the prefix resolution and prefix update are done in the IPR Driver job step for a HDAM or HIDAM that has internal logical relationships. | Note: If the database has external logical relationships, | PREFIXRES=YES is ignored. The prefix resolution and update | utilities are needed after the IPR Driver jobs. This control statement is optional. If you do not explicitly specify this control statement, PREFIXRES=NO will be used. : If PREFIXRES=YES is specified, and if the database is an HDAM or HIDAM and has internal logical relationships, the prefix resolution and prefix update are done | for the shadow data sets that have been reloaded. | After that, the Type-B Image Copy processing and the name swap | processing are done if IC=YES and NAMESWAP=YES are specified. | If PREFIXRES=YES is not specified, the logical relationship records are written in the DFSURWF1 | data set. You have to run the prefix resolution and update | utilities with the DFSURWF1 data set. ================================================================ 2.9.1 Automatic post-reorganization processing : If you specify NAMESWAP=YES, these tasks are done by Reorganization Manager automatically. | If you do not specify NAMESWAP=YES, you must perform these tasks manually. You must do these task manually also if any automatic post-reorganization processing fails. For details, see the next topic "Manual name swapping" in topic 2.9.2, and "Manual DBRC notification processing" in topic 2.9.3. If the database organization is one of the following types: - HDAM or HIDAM that has external logical relationships - HISAM that has internal or external logical relationships D you cannot specify NAMESWAP=YES, and the post-reorganization D processing cannot be done automatically. | you must run IMS Prefix Resolution and Prefix Update utilities | after the IPR Driver job step. For details, see "Post-reorganization processing for database with logical relationships" in topic 2.9.5. ================================================================ 2.9.5.2 External logical relationships If you are reorganizing an HDAM or a HIDAM database that has external logical relationships or an HISAM database that has internal or external logical relationships, | you must run IMS Prefix Resolution and Prefix Update | utilities after the IPR Driver job step. Follow these steps to complete post-reorganization processing for databases that are involved in such logical relationships: 1. Run IMS Database Prereorganization utility job. 2. Submit reorganization jobs to reorganize or scan each database. D In each job that uses the IPR Driver, NAMESWAP=NO must D be specified. You can use the IMS Database Scan utility or the IPR DB Scan utility to scan logically related databases that are not reorganized. For details about the IPR DB Scan utility, see "The IPR DB Scan utility" in topic 5.0. | 3. If NAMESWAP=YES is specified in the IPR Driver job step, | this step is not needed. | If NAMESWAP=YES is not specified, perform the name swapping manually for the databases and indexes that are reorganized or rebuilt by the IPR Driver. For details, see "Manual name swapping" in topic 2.9.2. | After that, issue the DBRC NOTIFY.REORG commands manually | to the databases and indexes. 4. Run IMS Prefix Resolution and Prefix Update utilities to complete logical relationship prefix processing. | 5. Take image copies by using any IMS Image Copy utility. | 6. Issue the DBRC CHANGE.DB AUTH READOFF commands | to the database and indexes manually. | | For details of the DBRC comannds, see "Manual DBRC | notification processing" n topic 2.9.3. ================================================================ 2.10.4 Reorganizing logically related databases The JCL statements used to reorganize a database that has external logical relationship by using the IPR Driver are the same as those used for a database that has no logical relationship, except D that you cannot use the NAMESWAP=YES option and that you must specify the DFSURCDS and DFSURWF1 DD statements. ================================================================ 10.3 Messages ---------------------------------------------------------------- HPSG0010W REORGANIZATION ENDED FOR DATABASE dbdname (RC=04, RSN=xxxxxxxx) (The reason code 40100012 is added.) |40100012 | PREFIXRES=YES is ignored because the external logical | relationships are defined in the non-HALDB. | Run IMS Prefix Resolution and Update utilities | after the IPR Driver job-step ---------------------------------------------------------------- HPSG0309E DATA SET NAME FOR DDNAME xxxxxxxx IS TOO LONG | Explanation: The data set name of the original DD name | xxxxxxxx is longer than 42 characters. If DYNALLOC=(xxx,YES) | or NAMESWAP=YES is specified, the name must be 42 or fewer | characters because IPR Driver appends two characters | to the name. System action: The IPR Driver ends with a return code of 8. | Programmer response: Make the name shorter or specify | DYNALLOC=(xxx,NO) and NAMESWAP=NO. If it is a secondary index, | specify DYNALLOC=(xxx,xxx,NO). For the details, see | "DYNALLOC control statement" and "NAMESWAP control statement". ---------------------------------------------------------------- HPSG0312W NAME SWAP CANNOT BE DONE: reason Explanation: The name swapping cannot be done because of the reason indicated by string reason. reason Description D EXTERNAL REFERENCE D The database has a logical relationship with another D database. LENGTH OF DATA SET NAME ... WARNING IN xxxxxx TASK ... ERROR IN IMGCPY TASK ... Programmer Response: D If the reason is EXTERNAL REFERENCE D and no error is found in the reorganization process, D perform the post-reorganization processing manually. D For details, see "Post-reorganization processing D for database with logical relationships" in topic 2.9.5. If the reason is LENGTH OF DATA SET NAME and ... ---------------------------------------------------------------- | HPSG0348E VSAM COMPONENT NAME IS TOO LONG: comp_name | Explanation: The name of a data component or an index | component of a VSAM data set is longer than 42 characters. | If NAMESWAP=YES is specified, the component name must | be 42 or fewer characters because IPR Driver appends | two characters to the name. | System action: The IPR Driver ends with a return code of 8. | Programmer response: Make the name shorter or specify | NAMESWAP=NO. For the details, see "NAMESWAP control | statement". ---------------------------------------------------------------- (The message type is changed: W -> I) | HPSG0376I IMAGE COPY NEEDED FOR DBDNAME=dbdname DDNAME=ddname : Programmer Response: Schedule an image copy operation before applications are scheduled to use the specified database data set. | You can specify IC=YES to take image copies | if the database has no external logical relationships. ---------------------------------------------------------------- HPSG0377I PREFIX RESOLUTION AND UPDATE ARE NEEDED FOR DBD=dbdname Explanation: The database dbdname has logical relationships. You have to run the prefix resolution and update utilities after this IPR job. D For internal relationships, you could D activate the prefix resolution and the update function D in the IPR step by the PREFIXRES=YES control statement. D System Action: Processing continues. Programmer Response: Run the prefix resolution and the prefix update utilities. | If the database has no external logical relationships, | specify PREFIXRES=YES control statement to activate | the prefix resolution and the update function in the IPR step. ---------------------------------------------------------------- | HPSG0378I PREFIX RESOLUTION AND UPDATE ARE NOT NEEDED | FOR DBD=dbdname | Explanation: The database dbdname has logical relationships, | which do not need to run Prefix Resolution and Update | utilities after the IPR Driver job step. | For the details of the reason, see "Logical relationships that | do not need Prefix Resolution and Update" in topic 2.6.5.4. | You can specify IC=YES and either ICTYPE=A or B to take image | copies in the IPR Driver job step for this database. | System Action: Processing continues. | Programmer Response: No ---------------------------------------------------------------- | HPSG0379W PREFIX RESOLUTION AND UPDATE ARE NEEDED | FOR DBD=dbdname | Explanation: PREFIXRES=YES is ignored because the database | dbdname has external logical relationships. | Prefix resolution and update are required after the IPR | Driver job step. | System Action: Processing continues. | Programmer Response: Run IMS Prefix Resolution and Update | utilities after the IPR Driver job step. ---------------------------------------------------------------- ================= End of Documentation Change ==================
APAR Information
APAR number
PK43275
Reported component name
IMS PARALLEL RE
Reported component ID
5655F7400
Reported release
320
Status
CLOSED UR1
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2007-04-13
Closed date
2007-04-27
Last modified date
2007-05-02
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UK24508
Modules/Macros
HPSGBBLA HPSGBBL8 HPSGBBL9 HPSGCM20 HPSGGDIB HPSGGIOB HPSGGIO0 HPSGGRGB HPSGGRG0 HPSGGRMB HPSGGVT0 HPSGMSGT HPSGRA00 HPSGRD00 HPSGRM00 HPSGRP00 HPSGRS00 HPSGRX00 HPSGTJ00 HPSGTM00 HPSGTY00 HPSGUBBL
| SC18922082 |
Fix information
Fixed component name
IMS PARALLEL RE
Fixed component ID
5655F7400
Applicable component levels
R320 PSY UK24508
UP07/04/28 P F704
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":"320","Edition":"","Line of Business":{"code":"LOB35","label":"Mainframe SW"}}]
Document Information
Modified date:
06 January 2023