A fix is available
APAR status
Closed as program error.
Error description
ABENDS0C4 occurred in HPSRHDL8 in the reload task following a time-out in pipe OPEN wait in unload task.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All users of IPR Driver of IMS Parallel * * Reorganization for z/OS Version 3 Release 1 * * (FMID=H25N310) * **************************************************************** * PROBLEM DESCRIPTION: This APAR fixes the following problems * * in IPR Driver: * * * * 1. On a system where CPUs are busy, * * a time-out can occur while a subtask * * is waiting for the partner task to * * open a pipe. Although the maximum * * wait time in writing data to or * * getting data from a pipe can be * * changed by coding the PIPEWAIT * * control statement, the statement * * does not change the maximum wait * * time for pipe open. * * * * 2. IPR Driver does not stop processing * * even if the Index Builder task ended * * with a non-zero return code without * * building a (shadow) secondary index. * * As a result, if INDEXBLD=YES, * * IC=YES, and ICTYPE=B are specified * * and the above error occurs in the * * Index Builder task, a VSAM OPEN * * error with MSGIEC161I RC072 RSN053 * * occurs when the Image Copy task * * tries to open the (shadow) secondary * * index. * **************************************************************** * RECOMMENDATION: Apply the maintenance for this APAR. * **************************************************************** This APAR fixes several problems in IPR Driver: 1. Pipe open time-out with MSGHPSG2006E can occur on a system where CPUs are busy. Although the maximum wait time in writing data to or getting data from a pipe can be changed by coding the PIPEWAIT control statement in the REORG control statement block of the HPSIN DD statement, the PIPEWAIT statement does not change the maximum wait time in opening a pipe. The PIPEWAIT control statement should be applied to the maximum wait time for pipe open also, and the task waiting for the partner task to open the pipe should detect an error in the partner task promptly, if it occurs, and should exit the wait state promptly. 2. IPR Driver does not stop processing even if the Index Builder task ended with a non-zero return code without building a (shadow) secondary index. As a result, if INDEXBLD=YES, IC=YES, and ICTYPE=B are specified and the above error occurs in the Index Builder task, a VSAM OPEN error with MSGIEC161I RC072 RSN053 occurs when the Image Copy task tries to open the (shadow) secondary index.
Problem conclusion
The following modules have been modified so that the PIPEWAIT control statement can be applied to the maximum wait time for pipe open: HPSGCM00, HPSGCSC1, and HPSGTP00 The following modules have been modified so that the task waiting for the partner task to open pipe can detect an error in the partner task promptly: HPSGPMA0, HPSGPMC0, HPSGPMI0, HPSGPMO0, HPSGPMX0, HPSGTE00, HPSGTI00, HPSGTJ00, HPSGTP00, HPSGTR00, HPSGTU00, and HPSGTY00 The following module has been modified so that IPR Driver stop processing when it gets a non-zero return code from Index Builder task: HPSGTM30 *======================* * DOCUMENTATION CHANGE * *======================* The IMS Parallel Reorganization for z/OS Version 3 Release 1 User's Guide (Document Number: SC18-9228-00) will be modified as follows. * * * Chapter 2. IMS Parallel Reorganization Driver 2.7 Control Statements 2.7.8 Description of Control Statements for Reorganization Manager 2.7.8.21 PIPEWAIT Control Statement PIPEWAIT specifies the amount of time a writer or a reader of a pipe can remain in a wait state before IPR Driver issues a message and abends. ________________________________________________________ | | | | _,__1___ | | | >>__PIPEWAIT=__ _(____time____|________|__)_ _______>< | | | |_,__2___| | | | |_time_______________________| | | | |________________________________________________________| The first parameter time specifies how many of minutes, from 1 to 1440, a writer or a reader, connecting to the pipe that | is specified by the second parameter, can remain in a wait | state. The second parameter specifies a pipe ID. This control | statement applies to both a wait state in opening the pipe | and a wait state in getting a pipe block to write or read. | If IPR Driver remains in a wait state longer than the | specified interval, IPR issues a message and abends. For the valid pipe IDs, see "Notes on pipe ID" in topic 2.7.8.19. If no pipe ID is specified, pipe ID 1 is used for the second parameter. If only the time value is specified, | it applies to the pipe of pipe ID 1. For each pipe, the | default time value is 15 (minutes) for each pipe when the | data is read from or written to the pipe, and is 30 seconds | when a reader or writer task waits for the partner task to | open the pipe. Appendix E. Messages and Codes E.3 Messages E.3.2 HPSG Messages * -------------------------------------------------------------- E.3.2.161 HPSG2004E HPSG2004E TIME-OUT IN tttttt OF PIPE pppppppppppppppp; REASON=rrrrrrrr | Explanation: Time-out occurred while the writer or reader task, which is indicated by tttttt, of the pipe pppppppppppppppp was waiting for the pipe. Reason code | rrrrrrrr shows the reason of the error. For the meaning of | the reason code, see the table of reason flags in Explanation | of the message HPSG2005E. System Action: Message HPSG2006E follows and the task abends. | Programmer Response: If the CPUs were busy on the system at | the time when the time-out occurred, code the PIPEWAIT | control statement. For details of the statement, see | "PIPEWAIT Control Statement" in topic 2.7.8.21. If the | time-out still occurs even if the PIPEWAIT control statement | is coded, contact IBM Software Support. * -------------------------------------------------------------- E.3.2.162 HPSG2005E HPSG2005E PIPE SERVICE ERROR IN tttttt OF PIPE pppppppppppppppp; REASON=rrrrrrrr Explanation: A pipe service requested by the reader or 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 2005. Programmer Response: Identify the cause of the error. If the cause is not found, contact IBM Software Support. * -------------------------------------------------------------- E.3.2.163 HPSG2006E HPSG2006E PIPE SERVICE REQUESTED BY tttttt IS ABORTED FOR PIPE pppppppppppppppp; REASON=rrrrrrrr Explanation: A pipe service requested by the reader or writer task tttttt, of pipe pppppppppppppppp is aborted due to an error in the partner task. The hexadecimal reason code rrrrrrrr shows the reason of the error and the status of the | pipe at the time the error occurred. For the meaning of the | reason code, see the table of reason flags in Explanation of | the message HPSG2005E. * 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.
Temporary fix
Comments
APAR Information
APAR number
PK07891
Reported component name
IMS PARALLEL RE
Reported component ID
5655F7400
Reported release
310
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2005-06-23
Closed date
2005-07-11
Last modified date
2005-08-02
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UK05274
Modules/Macros
HPSCOPTS HPSGCM00 HPSGCSC1 HPSGGPAB HPSGGSTB HPSGPBCB HPSGPIPE HPSGPMA0 HPSGPMC0 HPSGPMI0 HPSGPMO0 HPSGPMX0 HPSGPXEB HPSGTE00 HPSGTI00 HPSGTJ00 HPSGTM30 HPSGTP00 HPSGTR00 HPSGTU00 HPSGTY00
| SC18922800 |
Fix information
Fixed component name
IMS PARALLEL RE
Fixed component ID
5655F7400
Applicable component levels
R310 PSY UK05274
UP05/07/12 P F507
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.
[{"Line of Business":{"code":"LOB35","label":"Mainframe SW"},"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSVL5Q","label":"IMS Database Reorganization Expert for z\/OS"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"310"}]
Document Information
Modified date:
06 January 2023