A fix is available
APAR status
Closed as program error.
Error description
An ABEND0C4 occurred in module DFSCM7V0 routine CM7VVGR when an invalid ECB address (RPLECB) is passed to VTAM module ISTAICI2 on a CHANGE ENDAFFIN call. The ABEND occurred in an environment with VGR active. The invalid address was passed to VTAM in R10 and appears in R8 at ABEND. The logs show a DFS3201 MAXIMUM SESSIONS REACHED message was issued for the MSC link immediately before the ABEND. The output RPL for the MSC link is being used to issue the RPLCHNG call, but it has not been initialized yet resulting in the ABEND0C4.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All IMS V13 users using MSC VTAM links * * and VTAM Generic Resources. * **************************************************************** * PROBLEM DESCRIPTION: An ABENDS0C4 occurred in module * * DFSCM7V0 routine CM7VVGR due to a * * residual value in RPLECB. * * * * This is a forward-fit of APAR PM80478. * **************************************************************** * RECOMMENDATION: INSTALL CORRECTIVE SERVICE FOR APAR/PTF * **************************************************************** An ABEND0C4 occurs in module DFSCM7V0 due to an invalid ECB (RPLECB) address. The problem occurs as follows: 1. A cold MSC session is initiated via a /RST LINK command. 2. Due to maximum sessions reached, a MSGDFS3201 message is issued. As a result of this, DFSCM7A0 does not initialize the RPL in the output buffer. CTB7INIT is not set to indicate that the RPL has been initialized. 3. DFSCM7V0 gets control and issues a CHANGE ENDAFFNF request to VTAM. Since the RPL has not been initialized, residual data in RPLECB results in the abend.
Problem conclusion
GEN: KEYWORDS: *** END IMS KEYWORDS *** DFSCM7V0 has been modified to run the LXB chain to determine if the current LLB exists. If the LLB exists in the LXB chain, RPLECB will be updated with the Send ECB from the LXB.
Temporary fix
********* * HIPER * *********
Comments
APAR Information
APAR number
PM81764
Reported component name
IMS V13
Reported component ID
5635A0400
Reported release
302
Status
CLOSED PER
PE
NoPE
HIPER
YesHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2013-01-30
Closed date
2013-02-14
Last modified date
2013-10-04
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UK91687
Modules/Macros
DFSCM7V0
Fix information
Fixed component name
IMS V13
Fixed component ID
5635A0400
Applicable component levels
R302 PSY UK91687
UP13/02/20 P F302
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"},"Platform":[{"code":"PF054","label":"z Systems"}],"Version":"302","Line of Business":{"code":"","label":""}}]
Document Information
Modified date:
14 December 2020