PI56077: DFSUPNT0 DOESN'T FORMAT ALL THE PHIDAM PARTITIONS DESPITE USING INITALL OPTION

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• DFSUPNT0 doesn't format all the PHIDAM partitions despite put
  INITALL option, after change the HIGHKEY from the partition 1.
  Customer changed the HIGH KEY from the partition 1 from one
  PHIDAM db with 5 partitions, that it has also and PSINDEX, to
  distribute better the keys belonging to the partition 1 and the
  partition 2. The DFSUPNT0 step with the INITALL option only
  initialized the partitions with the partition initialization
  flag set and ignored the partitions which did not have the
  flags set. The subsequent load step completed with a DFS0730I
  message "UNABLE TO OPEN  DATA SET" for reason A,10,09.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: Users of IMS V13 HALDB Partition Data Set    *
  *                 Initialization utility (DFSUPNT0) who        *
  *                 specify DFSOVRDS DD INITALL in the JCL are   *
  *                 affected.                                    *
  ****************************************************************
  * PROBLEM DESCRIPTION: User received the following message:    *
  *                      DFS0730I UNABLE TO OPEN DATA SET WITH   *
  *                      DDNAME xxxxxxxx FOR REASON A,10,09      *
  *                      in the load job after specifying        *
  *                      DFSOVRDS DD INITALL in the prior        *
  *                      DFSUPNT0 job.                           *
  ****************************************************************
  * RECOMMENDATION: INSTALL CORRECTIVE SERVICE FOR APAR/PTF      *
  ****************************************************************
  User did a delete/redefine of existing HALDB data sets,
  followed by changing the high key of partition #1.
  After running DFSUPNT0 utility with INITALL, user's database
  load job received the DFS0730I UNABLE TO OPEN DATA SET message
  for partition #3, because only partitions #1 and #2 were
  initialized by DFSUPNT0.
  
  When INITALL is specified by the DFSUPNT0 utility, all
  partitions of a HALDB should be initialized, regardless of the
  setting of their PARTITION INIT NEEDED= flag in the RECON.
  
  Due to a logic error in module DFSUPNT1, when INITALL was
  specified, only those partitions that had
  PARTITION INIT NEEDED=YES were initialized.  As a result, user
  received the DFS0730I UNABLE TO OPEN DATA SET message for the
  first partition that had PARTITION INIT NEEDED=NO during a
  database load job.
  

Problem conclusion

• GEN:
  KEYWORDS:
  
  *** END IMS KEYWORDS ***
  Module DFSUPNT1 has been updated to resolve the data set open
  failure.  The InitAll variable is now set to true if the
  DFSOVRDS DD statement contains INITALL.
  
  This indicates to module DFSUPNT1 to skip calling DBRC to get
  a list of partitions with PARTITION INIT NEEDED=YES,
  and to go ahead and initialize all partitions of the database
  listed in the utility's SYSIN control card.
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

  PI56097 012AC3Ÿ PI56101 UI35364

Modules/Macros

•    DFSUPNT1
  

Fix information

• Fixed component name

  IMS V13

• Fixed component ID

  5635A0400

Applicable component levels

• R300 PSY UI35364

     UP16/02/19 P F602

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.