PM25283: ABEND0C7 WHEN RUNNING HD POINTER CHECKER IN THE ULU REGION WITH A DBD NAME IN THE EXEC STATEMENT

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• HD Pointer Checker get ABEND0C7 when the following conditions
  are met:
    - The DBALLABOVE statement is specified in the DFSVSAMP DD.
    - The database data sets are dynamically allocated.
    - HD Pointer Checker(HDPC) is run in the ULU region with a DBD
  name in the EXEC statement, or HDPC is run in the DLI or the DBB
  region.
  
      SYSTEM COMPLETION CODE=0C7  REASON CODE=00000000
      DATA AT PSW  0027F0F2 - FCF7D16A  D18A95E7  50984770
  

Local fix

• N/A
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: IBM IMS High Performance Pointer Checker for *
  *                 z/OS Version 3 Release 1 (FMID=HPC2310)      *
  *                 users who run HD Pointer Checker (HDPC).     *
  ****************************************************************
  * PROBLEM DESCRIPTION: When the DBALLABOVE statement is        *
  *                      specified in the DFSVSAMP data set,     *
  *                      some problems occur in HDPC.            *
  ****************************************************************
  * RECOMMENDATION: Apply the maintenance for this APAR.         *
  ****************************************************************
  When running HDPC in the ULU region with a DBD name in the EXEC
  statement, in the DLI region, or in the DBB region as a stand-
  alone job, dynamically allocating the database data sets, and
  specifying the DBALLABOVE statement in the DFSVSAMP data set,
  the following problems may occur in HDPC:
  
  - HDPC gets ABENDS0C7 in the FABPESTM module when HDPC tries to
    process a VSAM data set of a non-HALDB and the MERGINnn DD
    statement is specified in the JCL, because HDPC cannot get the
    TIOT address correctly.
  - HDPC incorrectly issues MSGFABP2079E when HDPC tries to
    process a VSAM data set of a non-HALDB and the MERGINnn DD
    statement is not specified in the JCL, because HDPC cannot get
    the TIOT address correctly.
  - HDPC gets ABENDS0C9 in the FABPAWDS module when HDPC tries to
    process an OSAM data set of a non-HALDB. HDPC should issue
    appropriate error message.
  

Problem conclusion

• The FABPUADR module is modified to get TIOT address by using
  GETDSAB macro.
  The FABPSDA0 module is modified to issue MSGFABP3605E and
  ABENDU3605 when MSGIEC133I is issued.
  
  Documentation Changes:
  Note: The section numbers are those of the BookManager (BKMGR)
  book.
  The documentation is modified as follows:
  ================================================================
    IMS High Performance Pointer Checker for z/OS, V3R1,
    User's Guide (SC19240101)
  ================================================================
  ----------------------------------------------------------------
  8.1.1         HD Pointer Checker
  8.1.1.3       Messages
  8.1.1.3.421   FABP3605E
  ----------------------------------------------------------------
   FABP3605E OPEN FAILED FOR DDNAME: ddname
  
   Explanation: In issuing an OPEN macro to open the data set
   associated with the specified ddname, the ABEND exit routine
   was called.
  
   The following causes are possible for a tape data set:
    - Tape BLKSIZE is over 32760. There is a restriction that you
      have to make the block size of the image copy data set to be
      equal to or less than 32760.
    - DCB is not specified on the DD statement of a non-label (NL)
      tape. DCB is required for an NL tape.
  
   System Action: The HD Pointer Checker issues a USER 3605 abend.
  
   User Response: Correct the error and rerun the HD Pointer
   Checker job.
  |If the DBALLABOVE statement in the DFSVSAMP DD is specified and
  |the message IEC133I appears in the joblog, remove the
  |DBALLABOVE statement from the DFSVSAMP DD. The DBALLABOVE
  |statement is not allowed for OSAM data sets.
  
   Problem Determination: Make sure that the ddname indicated in
   the DD statement is specifying the proper data set.
  

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:

  UK61936

Modules/Macros

•    FABPSDA0 FABPUADR
  

Fix information

• Fixed component name

  IMS POINTER CHE

• Fixed component ID

  5655E0900

Applicable component levels

• R310 PSY UK61936

     UP10/11/06 P F011

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.