A fix is available
APAR status
Closed as program error.
Error description
In attempting to free a BSB after an INOP, ISTTSCBG finds that the BSB is still on the Rex queue, and so it takes abend 0a9 with reason FF14.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All using VTAM boundary function. * **************************************************************** * PROBLEM DESCRIPTION: ABEND0A9 FF14 issued from ISTTSCBG * **************************************************************** * RECOMMENDATION: * **************************************************************** Problem is summarized as follows: 1) A local channel attached connection is being cleaned up by VTAM as a result of an INOP or deactivation command. 2) Module ISTTSCRX is called as a part of the cleanup to terminate any sessions with an UNBIND 08. The session is marked reset at this time. 3) The UNBIND requests are fowarded to the next node for processing. 4) It is assumed that the UNBIND responses will be received and processed by SESSER prior to a BFGEN DEALLOC being issued for this channel connection. 5) There is no synchronization for this to occur. 6) In this case, the BFGEN DEALLOC was issued and ISTTSCBG processed the command before all UNBIND rsps were processed by Sesser (for this connection). 7) Module ISTTSCBG found a BSB with the BSBONHSQ bit on and issued an ABEND0A9 FF14. Since this timing situation can occur, and the channel is cleaning up all control blocks, the BSB should simply be removed from the HSQ and continue processing.
Problem conclusion
To accomplish this, module ISTTSCBG has been changed to add a new subroutine, RMVHSQ. This subroutine will be called to remove a BSB from the HSQ by calling ISTTSCRQ. Cleanup will continue if the BSB is successfully removed. An ABEND0A9 will still be issued by ISTTSCBG if the BSB is not removed from the HSQ. Module ISTTSCRQ has been changed to set the TSCBPTR to zero if the TSPL is not passed via the RPHWEA. When ISTTSCBG calls ISTTSCRQ, a TSPL is not created. An inefficiency existed in module ISTTSCRQ when calling subroutine QUIKSRCH. QUIKSRCH is called to find only FMCBs, but there were instances where it would be called when processing a BSB. This was inefficient as the subroutine's only intent is to process FMCBs. Module ISTBSCRT is included for maintenance purposes.
Temporary fix
Comments
APAR Information
APAR number
OW37678
Reported component name
VTAM V4 MVS/ESA
Reported component ID
569511701
Reported release
401
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
1999-02-15
Closed date
1999-03-02
Last modified date
1999-04-05
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UW57018 UW57019 UW57020 UW57021
Modules/Macros
ISTBSCRT ISTTSCBG ISTTSCRQ
Fix information
Fixed component name
VTAM V4 MVS/ESA
Fixed component ID
569511701
Applicable component levels
R401 PSY UW57018
UP99/03/26 P F903
R411 PSY UW57019
UP99/03/26 P F903
R501 PSY UW57020
UP99/03/26 P F903
R701 PSY UW57021
UP99/03/26 P F903
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":"401","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":"401","Edition":"","Line of Business":{"code":"","label":""}}]
Document Information
Modified date:
05 April 1999