PM87663: HP LOAD CAN RELOAD HALDB OSAM WITH INCORRECT BLOCK SIZE.

Obtain the fix for this APAR.

APAR status

• Closed as unreproducible in next release.

Error description

• HP Load can reload HALDB OSAM with incorrect block size when all
  the following conditions are met:
  - An incorrect block size was specified in defining OSAM data
    set.
  - NOREORGV has been specified in RECON.
  - The first segment of the partition is moved from another
    partition by changing partition boundaries.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: All users of IBM IMS High Performance Load   *
  *                 for z/OS Version 2 Release 1 (FMID=H1IM210). *
  ****************************************************************
  * PROBLEM DESCRIPTION: HP LOAD CAN RELOAD HALDB OSAM WITH      *
  *                      INCORRECT BLOCK SIZE.                   *
  ****************************************************************
  * RECOMMENDATION: Apply the maintenance for this APAR.         *
  ****************************************************************
  HP Load can reload HALDB OSAM with incorrect block size when all
  the following conditions are met:
  - An incorrect block size was specified in defining OSAM data
    set.
  - NOREORGV has been specified in RECON.
  - The first segment of the partition is moved from another
    partition by changing partition boundaries.
  - partition is empty and PARTINIT=YES.
  
  This APAR prevents from reloading HALDB OSAM with incorrect
  block size. By applying this APAR, HP Load checks the block size
  of HALDB OSAM database data set, and issues ABENDU3660 when the
  actual BLKSIZE of a HALDB OSAM is not the same as that
  registered to the RECON.
  
  To avoid ABENDU3660, you must do one of the following:
  - Change the RECON definition from NOREORGV to REORGV.
  - If you explicitly specify block size for database data set in
    creating it, remove the specification or specify correct
    value.
  

Problem conclusion

Temporary fix

Comments

• HP Load has been modified to check the block size of HALDB OSAM
  database data set, and to issue ABENDU3660 when the actual
  BLKSIZE of a HALDB OSAM is not the same as that registered to
  the RECON.
  
  ========================
  = Documentation Change =
  ========================
  IMS High Performance Load for z/OS Version 2 Release 1 User's
  Guide SC18-9222-05 ( SC18922205 ) should be changed as follows:
  ================================================================
  7.1.4.1 IMS HP Load messages
  
  | HPSR3699W DBRC API FUNC= function,[TYPE=type,]RC=rc,RSN=rsn
  
  | Explanation:
  | HP Load received an error return code from the DBRC API
  | during DBRC processing. function is the function name of the
  | DBRC API, type is the type of the DBRC query request, rc is
  | the return code in decimal, and rsn is the reason code in
  | hexadecimal format.
  
  | System Action:
  | HP Load cannot check the block size of database data set
  | due to an error from the DBRC API.
  | Processing continues.
  
  | User Response:
  | You can ignore the message when you can verify whether the
  | block size of each database data set is correct by manually.
  | Otherwise, correct the error and rerun the job.
  | The meaning of the return code and reason code is described in
  | IMS System Programming APIs for the version of IMS that you
  | are using.
  | If necessary, contact IBM Software Support.
  
  
  | HPSR3659E DDN xxxxxxxx IS NOT FOUND IN THE RECON
  
  | Explanation:
  | HP Load checks the block size of each database dataset with
  | the size registered to RECON. However, the DDN xxxxxxx is not
  | found in the RECON data set.
  
  | System Action:
  | HP Load issues a user 3659 abend and a dump.
  
  | User Response:
  | Check if the DDN is correct ddname.
  | If necessary, contact IBM Software Support.
  
  
  | HPSR3660E THE BLKSIZE OF DDN=xxxxxxxx DOES NOT MATCH THE
  |           VALUE IN RECON
  
  | Explanation:
  | The block size of the database data set is not the same as
  | that registered to RECON
  
  | System Action:
  | HP Load issues a user 3660 abend and a dump.
  
  | User Response:
  | If you explicitly specify block size for database data set
  | in creating it, remove the specification or specify correct
  | value, and then rerun the job.
  | Or change the RECON definition from NOREORGV to REORGV to
  | reload with correct block size.
  | If necessary, contact IBM Software Support.
  
  
  HPSR3743W DYNALLOC FAILURE OCCURRED FOR xxxxxxxx: RETURN
            CODE=return_code REASON CODE=reason_code
  
  Explanation:
    An attempt to dynamically allocate data set xxxxxxxx failed.
  | xxxxxxxx is used for the DSG check or BLKSIZE check
    internally. Return_code and reason_code are the return code
    and the reason code from the SVC99 routine.
  
  System Action:
  | Processing continues; DSG check or BLKSIZE check was bypassed.
  | When DSG check is bypassed, the message HPSR3744W follows.
  | When BLKSIZE check is bypassed, the message HPSR3699W follows.
  
  User Response:
    If necessary, correct the error and rerun the job or contact
    IBM Software Support.
  
  ======================= End of Doc-Change ======================
  ž**** PE13/05/31 FIX IN ERROR. SEE APAR PM90229  FOR DESCRIPTION
  

APAR Information

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

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

  UK94664

Modules/Macros

• HPSRCE00 HPSRFCA0 HPSRGTI0 HPSRHALA HPSRHALB HPSRHAL2 HPSRHAL3
  HPSRHAL7 HPSRHAL8 HPSRHAL9 HPSRMSGT HPSRRLDA HPSRRLDB HPSRRLD2
  HPSRRLD3 HPSRRLD7 HPSRRLD8 HPSRRLD9 HPSRRXRT HPSRRXST
  

Fix information

• Fixed component name

  IMS HIGH PERF L

• Fixed component ID

  5655E0700

Applicable component levels

• R210 PSY UK94664

     UP13/05/31 P F305

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.