A fix is available
APAR status
Closed as program error.
Error description
IMS Connect ABEND0C6 in module BPELDCA0 near label LDCLCOM at offset x'01EC' during CLOSEHWS processing. A previous process which was supposed to cancel the TCP/IP socket was in error. This caused CLOSEHWS to be posted at the wrong time.
Local fix
There is no local fix for this problem.
Problem summary
**************************************************************** * USERS AFFECTED: All IMS V13 IMS Connect users. * **************************************************************** * PROBLEM DESCRIPTION: ABEND0C6 at offset x'1EC' into csect * * BPELDCA0 of module BPESTG00 after * * CLOSEHWS command. * * * * Forward-fit of PI09558 * **************************************************************** * RECOMMENDATION: INSTALL CORRECTIVE SERVICE FOR APAR/PTF * **************************************************************** ABEND0C6 Near at X'1EC' in csect BPELDCA0 of part BPESTG00 due to an invalid post of the thread ECB. The post is invalid as it is notification of the completion of an event triggered by prior use of the same thread control block. The prior thread has since terminated without cancelling the outstanding I/O. The failing instruction is '0DEF' (BASR r14,r15). The contents of R15 is assumed to be the address of BPETERM0 but instead contain the address of the SET control block. Analysis indicated that the thread control block which contains the ECB was inuse and in a BPEWAIT for completion of a TCP/IP socket READ request. While in the wait the thread was posted by the CLOSEHWS FORCE process with post code ' SST'. Logic added by PM28892 insured that the routine to cancel the outstanding I/O (READ request) was executed. However, the canceling of the I/O did not occur due to an invalid value in the AioBuffPtr field of the AIOCB passed on the cancel request. Therefore the thread was terminated without really cancelling the outstanding I/O. AioBuffPtr should contain the address of a the AIOB to to cancel, or zero to cancel all request on the socket. The HWS termination process creates a term thread session to complete the shutdown. In doing so it obtains an available thread control block. It happens that the available thread control block is the same one released by the prior session that terminated without cancelling the outstanding I/O. Eventually the shutdown thread executes then BPEWAITs for completion of a BPELOAD macro call to load part BPETERM0. It is during this wait that the I/O that was left outstanding from the prior use of the thread control block completes and posts the ECB. After the post, control resumes in BPELDCA0 which assumes that part BPETERM0 has been loaded. The abend occurs because the address to BPETERM0 had not been established as the BPELOAD event had not completed. Depending on the contents of R15 at time of error, an ABEND0C1 or ABEND0C6 can occur. Various other symptoms may occur due to unexpected posts of thread ECB's including ABENDS0C4, ABENDS0C3. Keyword(s): ABEND0C1 S0C1 0C1 ABEND0C6 S0C6 0C6 CMDCLO ABEND0C4 S0C4 0C4 ABEND0C3 S0C3 0C3
Problem conclusion
GEN: KEYWORDS: *** END IMS KEYWORDS *** The logic in part HWSSDRCV that prepares the AIOCB control block fields for the CANCELIO Unix System Services request has been corrected to insure that the value in AioBuffPtr is always set to zero (for cancelio). AioBuffPtr must be set to zero (cancel all outstanding request) or address of specific descriptor (cancel specific request). Setting AioBuffPtr to zeros correct the issue by letting the service know which request to cancel. The identical correction has been made to parts HWSGDRCV, HWSMDR HWSQDRCV and HWSTDRCV to correct the CANCELIO process for ODBM, ISC and connect-to-connect communication components.
Temporary fix
********* * HIPER * *********
Comments
APAR Information
APAR number
PI09672
Reported component name
IMS V13
Reported component ID
5635A0400
Reported release
300
Status
CLOSED PER
PE
NoPE
HIPER
YesHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2014-01-15
Closed date
2014-02-07
Last modified date
2014-03-03
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UI14937
Modules/Macros
HWSGDRCV HWSMDRCV HWSQDRCV HWSSDRCV HWSTDRCV
Fix information
Fixed component name
IMS V13
Fixed component ID
5635A0400
Applicable component levels
R300 PSY UI14937
UP14/02/12 P F402 ¢
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.
[{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M","label":"APARs - z\/OS environment"},"Platform":[{"code":"PF054","label":"z Systems"}],"Version":"300","Line of Business":{"code":"","label":""}}]
Document Information
Modified date:
14 December 2020