A fix is available
APAR status
Closed as program error.
Error description
After a system abend522 access to the coupling facility structure is hung in VTAM waiting on VTAMs internal lock. The process that is waiting on the lock is also holding the lock.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: * * All users that connect to TCP/IP coupling facility * * structures EZBEPORT. * * SYSPLEXDS * **************************************************************** * PROBLEM DESCRIPTION: * * VTAM processes waiting on a VTAM coupling facility structure * * VTAM lock. * **************************************************************** * RECOMMENDATION: * * Apply the PTF when it is available. * **************************************************************** This problem may be described as follows: 1. TCPIP application was using sysplexports. 2. TCPIP issued VTAM request to use the port. 3. ISTFSVPC received control to process the request. It issued SETFRR request to setup the FRR to set up the recovery environment. It also issued SETVRR to put the retry routine FSVPC_VRR on stack. It issued GETLOCK to obtain the EZBEPORT structure lock. 4. ISTFSVLG received control to obtain the lock. It obtained the SSVCBLCK lock with the exclusive option. ISTAPCSU received control to suspend this process. It cleared the CRA recovery parameter list before suspending this process. 5. The suspended process of the step 4 got timed out and received the ABEND522. 6. ISTAPCFR received control to process the ABEND522 without any CRA parameter list. It did not release any VTAM SSVCBLCK structure lock. 7. Other processes needed the SSVCBLCK lock. They were waiting in a queue for the SSVCBLCK lock. This caused a wait for all TCPIP applications which wanted to use sysplexports.
Problem conclusion
ISTAPCSU and ISTAPCTW were changed to not clear the CRA parameter list before suspending the process. They will allow ISTAPCFR to release all locks and recover from the ABEND.
Temporary fix
Comments
APAR Information
APAR number
OA46221
Reported component name
VTAM V4 MVS/ESA
Reported component ID
569511701
Reported release
210
Status
CLOSED PER
PE
NoPE
HIPER
YesHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2014-10-10
Closed date
2014-10-16
Last modified date
2015-01-02
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
OA46249 UA74845 UA74897
Modules/Macros
ISTAPCSU ISTAPCTW
Fix information
Fixed component name
VTAM V4 MVS/ESA
Fixed component ID
569511701
Applicable component levels
R210 PSY UA74845
UP14/12/06 P F412
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":"210","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":"210","Edition":"","Line of Business":{"code":"","label":""}}]
Document Information
Modified date:
02 January 2015