A fix is available
APAR status
Closed as program error.
Error description
Multiple ABDUMP commands are entered for a BMP within the same second. This results in the scheduling of 2 SRB to request termination of the BMP. The first ABDUMP request is in progress and releasing storage areas when the second request begins. The second request can encounter an ABEND0C4 if a required storage area has been previously released. In the reported case, the released storage was the DFSECP pointed to by the TCB's first SAVEAREA in R1. . BMP/IFP regions do not check the SAPSABPR flag. If SAPSABPR would have been checked, a MSGDFS0559I would have resulted: . DFS0559I ABEND ALREADY SCHEDULED FOR REGION
Local fix
Do not issue multiple ABDUMP commands for a BMP region.
Problem summary
**************************************************************** * USERS AFFECTED: IMS V12 customers issuing multiple /STOP * * REGION X ABDUMP commands for the same region * * in rapid succession. * **************************************************************** * PROBLEM DESCRIPTION: ABEND0C4 in DFSSRB routine processing a * * /STOP REGION x ABDUMP command. * **************************************************************** * RECOMMENDATION: INSTALL CORRECTIVE SERVICE FOR APAR/PTF * **************************************************************** /STOP REG x ABDUMP is entered and in the process of terminating a dependent region when a second /STOP REGION x ABDUMP command is entered against the same region, most likely from an AOI due to the rapid succession of the commands. The first command processes far enough to free IMS storage when the second command attempts to use the same storage. ABEND0C4 results.
Problem conclusion
GEN: KEYWORDS: *** END IMS KEYWORDS *** Code was added to module DFSSTOP0 (/STO REG command processor) to detect that a /STO REGION x ABDUMP command is already in progress. DFS559 ABEND ALREADY SCHEDULED FOR REGION x is now issued when a prior /STOP REGION ABDUMP command is in progress.
Temporary fix
Comments
APAR Information
APAR number
PM79243
Reported component name
IMS V12
Reported component ID
5635A0300
Reported release
200
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2012-12-14
Closed date
2013-01-14
Last modified date
2013-02-04
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
PM79245 UK90776
Modules/Macros
DFSSTOP0
Fix information
Fixed component name
IMS V12
Fixed component ID
5635A0300
Applicable component levels
R200 PSY UK90776
UP13/01/15 P F301
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"}],"Line of Business":{"code":"","label":""}}]
Document Information
Modified date:
14 December 2020