PK72387: HP LOAD API JOB RECEIVES ABEND0C4 WHEN TWO OR MORE DATABASES ARE LOADED.

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• This APAR provides the following fixes:
  1. When the ISRT calls to load two or more databases are
  processed by HP Load and IMS DL/I, ABEND0C4 occurs because HP
  Load updates the IMS DL/I buffers (PSTVOLWA and  PSBSEGWK).
  2. HP Load API issues the PIPE time-out error (HPSR2011E) when
  the RECON data sets are busy.
  

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: This APAR provides the fix for the      *
  *                      following problems of HP Load API:      *
  *                                                              *
  *                      1. ABEND0C4 is received because HP      *
  *                         Load updates the IMS DL/I buffers    *
  *                         while IMS DL/I is running            *
  *                         simultaneously.                      *
  *                                                              *
  *                      2  When RECON data sets are busy,       *
  *                         U4000 abend is issued in HP Load     *
  *                         API job step due to a PIPE time-out. *
  *                                                              *
  *                      3. HP Load API job step waits till      *
  *                         a PIPE time-out when the             *
  *                         initialization check failed.         *
  ****************************************************************
  * RECOMMENDATION: Apply the maintenance for this APAR.         *
  ****************************************************************
  This APAR provides the fix for the following problems of
  HP Load API:
  
  1. ABEND0C4 is received because HP Load updates the IMS DL/I
     buffers(PSTVOLWA and  PSBSEGWK) while IMS DL/I is processing
     simultaneously. This problem occurs when the ISRT calls are
     processed by HP Load API and IMS DL/I to load two or more
     databases.
  
  2  When RECON data sets are busy, MSGHPSR2011E and U4000 abend
     are issued in HP Load API job step due to a PIPE time-out.
     The wait time specified by the PIPEOWAIT control statement
     should not include the time to access the RECON data sets.
  
  3. When HP Load API detects an error in the initialization
     check, after that, the job waits the time specified
     by PIPEOWAIT control statement.
     HP Load should return the error just after the check.
  

Problem conclusion

• ========================
  = Documentation Change =
  ========================
  IMS High Performance Load for z/OS Version 2 Release 1 User's
  Guide SC18-9222-03 ( SC18922203 ) should be changed as follows:
  ================================================================
  4.0 Load API
  4.2 Operating instructions
  4.2.4 Input--Control statements
  4.2.4.4 PIPEOWAIT control statement
  :
  DEL:
  | Note: If the load process terminates abnormally before
  | the pipe is established internally between the application
  | analysis process and the load process, IMS High Performance
  | Load will stay in the wait state for the specified number
  | of seconds.
  DEL:
  
  ----------------------------------------------------------------
  APPENDIX1.3   Appendix C.  Messages and codes
   APPENDIX1.3.3 Messages
    APPENDIX1.3.3.1 High Performance Load messages
  
  
   HPSR2006E PIPE SERVICE REQUESTED BY tttttt IS ABORTED FOR PIPE
            pppppppppppppppp; REASON=rrrrrrrr
  
  Explanation: A pipe service requested by the reader or the
  writer task tttttt, of pipe pppppppppppppppp is aborted by an
  error in the task. The hexadecimal reason code rrrrrrrr shows
  the reason of the error and the status of the pipe at the time
  the error occurred. The reason code is the logical sum of
  the following reason flags:
  
      Flag (hex)   Meaning
     ------------  -----------------------------------------------
      80000000     The pipe has been requested to open
      40000000     The pipe has been requested to close
      20000000     PUT processing for the pipe has been requested
      10000000     GET processing for the pipe has been requested
      01000000     Pipe OPEN, CLOSE, PUT, or GET processing is in
                   progress
      00800000     The task has a lock
      00400000     The task is waiting for a lock
      00200000     The task is waiting for the partner task to put
                   data in the pipe or to get data from the pipe
      00100000     This flag is used internally
      00010000     The pipe is closed on this end
      00008000     An error in the partner task is detected
      00004000     The task is ending abnormally
  |   00002000     A time-out occurred while a pipe request was
                   being processed
      00001000     An error occurred during the setting up of a
                   recovery routine
      00000800     A record passed to a PUT request is too large
  |   00000400     The task stopped waiting for the partner task
  |                to open the pipe
      00000080     The partner task ended abnormally
      00000040     The partner task closed the pipe unexpectedly
  |   00000020     A time-out occurred while the task was waiting
                   for the partner task to open the pipe
  |   00000010     The partner task could not wait for the
  |                current task to open the pipe
  |   00000008     The task was requested to stop waiting for the
  |                partner task to open the pipe
  System Action: The task abends with a user completion code of
  2006.
  Programmer Response: Identify the cause of the error in the
  partner task. If the cause is not found, contact IBM Software
  Support.
  
  ----------------------------------------------------------------
   HPSR2011E TIME-OUT WHILE PIPE tttttt WAITING FOR PARTNER TO
            OPEN PIPE pppppppppppppppp
     Explanation: If the partner task does not opened the pipe
     within a minute, this message is issued from the task that
     issued the preceding message HPSR2008I for pipe
     pppppppppppppppp. Something is wrong in the partner task.
     System Action: Message HPSR2006E follows and the task abends.
  |  Programmer Response: You can code the PIPEOWAIT control
  |  statement to stay in the wait state until the session of
  |  the pipe connection is established completely. For details of
  |  the statement, see "PIPEOWAIT Control Statement" in topic
  |  4.2.4.4. If the time-out still occurs even if the PIPEOWAIT
  |  control statement is coded, contact IBM Software Support.
     Problem Determination: None.
  ----------------------------------------------------------------
  

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:

  UK40618

Modules/Macros

• HPSRAP0A HPSRAP00 HPSRAP07 HPSRAP08 HPSRAP09
  HPSRAT00 HPSRCMPA HPSRCMPR HPSRCMP7 HPSRCMP8 HPSRCMP9 HPSRDSCT
  HPSRHDLA HPSRHDLD HPSRHDL7 HPSRHDL8 HPSRHDL9 HPSRLAPB HPSRPBCB
  HPSRPIPE HPSRPI00 HPSRPMA0 HPSRPMC0 HPSRPMI0 HPSRPMO0 HPSRPMX0
  HPSRPXEB HPSRSRT0
  

Fix information

• Fixed component name

  IMS HIGH PERF L

• Fixed component ID

  5655E0700

Applicable component levels

• R210 PSY UK40618

     UP08/10/11 P F810

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.