A fix is available
APAR status
Closed as program error.
Error description
ABEND0C4 occurs in ISTTSCBG due to a freed BSB still residing on the REXX hash table.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All using local dependent LUs. * **************************************************************** * PROBLEM DESCRIPTION: ABEND0C4 in ISTTSCBG processing * * a freed BSB on the Rex hash table. * **************************************************************** * RECOMMENDATION: * **************************************************************** The problem is summarized as follows: 1) A BIND is being sent to a local SNA dependent LU off a local XCA LAN. 2) The BIND is being chased by a DACTLU request for the same LU. 3) The BIND request is processed by Sesser which involves allocating a BSB for the session. The BSB is also added to the Subarea hash tree (BSBSA ADD). 4) The BIND is then forwarded to the LSNCB (XCA) PC PAB to be processed. 5) Meanwhile, the Sesser PAB processes the DACTLU request. This involves sending UNBIND requests to all active and pending active sessions. The BSBs are also removed from the Rex hash table at this time. 6) The DACTLU request is then forwarded to the LSNCB (XCA) PC PAB to be processed. 7) The LSNCB PC PAB is dispatched to process the work. 8) The BIND request is processed first. The BSB for this session is located and the BSB is added to the Rex hash table for this PU (LSNCB). The BIND is then sent to the XCNCB to be sent out on the LAN. 9) The DACTLU is then processed and forwarded to the XCNCB to be sent out on the LAN. 10) The BIND and DACTLU requests are sent on the LAN. 11) The negative BIND response and a positive response to the DACTLU are received by VTAM. 12) Eventually, the DACTLU response arrives at Sesser for processing. 13) Sesser processes the DACTLU and finishes cleaning up the SSCP-LU and LU-LU BSBs. In this case, the LU-LU BSB is removed from the Subarea hash tree, but not from the Rex hash table. The BSB is then sent to ISTTSCBF to be freed. The BSB is not removed from the Rex hash table, since Sesser thinks it already removed all the BSBs for this LU in step 5. 14) Later, when the PU INOPs and is cleaned up, ISTTSCBG suffers an ABEND0C4 while processing a freed BSB on the Rex hash table.
Problem conclusion
ISTTSCYP - A new subroutine, BSBRXDEL, has been created to issue a BSBREX DELETE function. Subroutine RSSCPLU, has been changed call new subroutine BSBRXDEL when processing a DACTLU response. This will ensure the BSB is removed from the Rex hash table prior to freeing it. ISTBSCRT - Included for maintenance purposes.
Temporary fix
********* * HIPER * *********
Comments
APAR Information
APAR number
OA22911
Reported component name
VTAM V4 MVS/ESA
Reported component ID
569511701
Reported release
160
Status
CLOSED PER
PE
NoPE
HIPER
YesHIPER
Special Attention
NoSpecatt
Submitted date
2007-10-17
Closed date
2007-11-07
Last modified date
2008-01-02
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UA37896 UA37897 UA37898
Modules/Macros
ISTBSCRT ISTTSCYP
Fix information
Fixed component name
VTAM V4 MVS/ESA
Fixed component ID
569511701
Applicable component levels
R170 PSY UA37896
UP07/12/08 P F712
R180 PSY UA37897
UP07/12/08 P F712
R190 PSY UA37898
UP07/12/08 P F712
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"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"160","Edition":"","Line of Business":{"code":"","label":""}},{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SSCY4DZ","label":"DO NOT USE"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"160","Edition":"","Line of Business":{"code":"","label":""}}]
Document Information
Modified date:
02 January 2008