A fix is available
APAR status
Closed as program error.
Error description
A XCF PU is hung in state PDISC. An abend had occurred while trying to send data on this device. The CPNCB PC PAB is not cleaned up correctly by abend recovery. The PU is waiting for the cleanup to complete. The TRLE will also be hung in INACT state. ADDITIONAL SYMPTOMS: If the remote system is recycled, the TRLE will fail to set up with messages: IST2187I XCF SEND FAILURE ON TRLE ISTxxxxx MESSAGE TYPE: XID IST1684I RETURN CODE = 00000008 REASON CODE = 00000008 IST1578I DEVICE INOP DETECTED FOR ISTxxxxx BY ISTTSC8X CODE = 010 . The TCPIP XCF devices will fail to start with message EZZ4308I ERROR: CODE=8010002B DURING ACTIVATION OF DEVICE xxxx. DIAGNOSTIC CODE: 02
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All users of XCF connections. * **************************************************************** * PROBLEM DESCRIPTION: XCF device hung PDISC or PFDSC. * **************************************************************** * RECOMMENDATION: * **************************************************************** 1. XCF is being used for connectivity in a sysplex. 2. Data is sent out over an XCF connection. 3. The MPNCB PC PAB is dispatched to process the outbound data. At this point the running RPH has the RPHMAJCB set to the MPNCB address. 4. After the write device is selected, module ISTTSC8W sets the RPHMAJCB to point to the CPNCB for the read/write device. An abend then occurs in ISTTSC8W or one of the modules it calls. 4. The VRR in ISTTSC8W gets control and issues TPEXIT, but since RPHMAJCB is not pointing to the NCB of the PAB which was dispatched, TPEXIT attempts to exit the wrong PAB. 5. The PABs for the NCB are hung and this shows externally as the device being PDISC. 6. Later attempts to inactivate the device move its state to PFDSC.
Problem conclusion
ISTTSC8W has been updated to restore the RPHMAJCB in the VRR before exiting. ISTTSCMA and ISTTSC8E are included for maintenance purposes.
Temporary fix
********* * HIPER * *********
Comments
APAR Information
APAR number
OA32193
Reported component name
VTAM V4 MVS/ESA
Reported component ID
569511701
Reported release
1A0
Status
CLOSED PER
PE
NoPE
HIPER
YesHIPER
Special Attention
NoSpecatt
Submitted date
2010-03-05
Closed date
2010-03-18
Last modified date
2010-05-04
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UA53252 UA53251 UA53253
Modules/Macros
ISTTSCMA ISTTSC8E ISTTSC8W
Fix information
Fixed component name
VTAM V4 MVS/ESA
Fixed component ID
569511701
Applicable component levels
R1A0 PSY UA53251
UP10/04/20 P F004
R1B0 PSY UA53252
UP10/04/20 P F004
R190 PSY UA53253
UP10/04/20 P F004
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":"1A0","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":"1A0","Edition":"","Line of Business":{"code":"","label":""}}]
Document Information
Modified date:
04 May 2010