A fix is available
APAR status
Closed as program error.
Error description
An application issues a request to VTAM using the APPC/VTAM interface. The request fails with RCPRI=002C and RCSEC=0002. This failure means invalid conversation identifier. The conversation identifier is provided to the application by VTAM and the application provides this identifier on future requests for a conversation. The application may then issue another request using the same conversation identifier and APPC/VTAM accepts the request.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All using VTAM APPC (APPC=YES on VTAM APPL * * statement). * **************************************************************** * PROBLEM DESCRIPTION: VTAM/APPC conversation hang soon * * after the conversation is started. * * May also manifest as: * * RCPRI 002C RCSEC 0002 on APPCCMD * **************************************************************** * RECOMMENDATION: * **************************************************************** The problem may be summarized as follows: 1. Two VTAM/APPC applications are running in a host. 2. One VTAM/APPC application is in a conversation, but that conversation is ending. 3. At roughly the same time as that conversation is ending, an FMH5 comes in for the second VTAM/APPC application to start a conversation. 4. The process that is ending the first conversation begins to release the conversation ID, but suspends before it is completely done. 5. The process that is starting the second conversation obtains the partially freed conversation ID and passes it to the second VTAM/APPC application. 6. That application issues APPCCMD RECEIVE using that conversation ID, but the command fails with a RCPRI/RCSEC combination of x'002C'/X'0002'. This is because the lock for the conversation ID's entry is still held by the suspended process. 7. Another symptom may be that the APPCCMD RECEIVE hangs because inbound data was discarded after an attempt to lock the conversation ID's entry fails due to the suspended process.
Problem conclusion
To resolve this problem, the following changes were made: 1. ISTNACVA was changed to not reuse a conversation ID whose lock is still held. 2. ISTNSCLR was included for maintenance purposes only.
Temporary fix
********* * HIPER * *********
Comments
APAR Information
APAR number
OA23264
Reported component name
VTAM V4 MVS/ESA
Reported component ID
569511701
Reported release
170
Status
CLOSED PER
PE
NoPE
HIPER
YesHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2007-11-20
Closed date
2007-11-28
Last modified date
2008-02-01
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UA38259 UA38260 UA38261
Modules/Macros
ISTNACVA ISTNSCLR
Fix information
Fixed component name
VTAM V4 MVS/ESA
Fixed component ID
569511701
Applicable component levels
R170 PSY UA38259
UP08/02/01 P F801
R180 PSY UA38260
UP08/02/01 P F801
R190 PSY UA38261
UP08/02/01 P F801
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":"170","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":"170","Edition":"","Line of Business":{"code":"","label":""}}]
Document Information
Modified date:
01 February 2008