A fix is available
APAR status
Closed as program error.
Error description
Miscellaneous bug fixes.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All Fault Analyzer Version 10 users. * **************************************************************** * PROBLEM DESCRIPTION: 01. Abend S0C4 in EXTRACT_COBOL_MAP * * when IDILANGX processes COBOL * * listing with NUM compiler option in * * effect. * * APAR PM09208 * * 02. IS domain not selectable from CICS * * trace selection panel. * * APAR PM09480 * * 03. Message ICH409I 282-020 ABEND * * DURING RACHECK PROCESSING when * * entering a non-existing history * * file name from the Fault Entry List * * display. * * APAR PM09443 * * 04. Fault Analyzer only reports COBOL * * source lines preceding a comment * * when a multi-line statement has * * comments interspersed. * * APAR PM10154 * * 05. Loop during CICS SDUMP analysis. * * APAR PM11513 * * 06. Dump processing waiting on ENQ of * * SYSIDIDA minor SYSOUT from module * * IDIXDCAP. * * APAR PM11410 * **************************************************************** * RECOMMENDATION: Apply the provided PTF. * **************************************************************** 01. NUM may cause 6-digit line numbers in MAP section of listing and IDILANGX only allows for 5, causing duplicates in the Line_To_Stmt data. 02. The IS domain had been omitted. 03. RACHECK processing was called for a non-existing history file name. 04. Incorrect offset assigned to comment. 05. A corrupt CICS control block was causing Fault Analyzer to loop when chaining through the control blocks. 06. With many TCBs abending concurrently in a large address space, the Fault Analyzer invocation exit IDIXDCAP can lock out the abend processing because of an ENQ on SYSIDIDA SYSOUT.
Problem conclusion
01. MAP section line number increased to 6 digits. 02. The IS domain has been added to list of valid domains. 03. The existence of the history file is determined prior to calling RACHECK processing. 04. Correct offset now assigned to comment. 05. A validity check is now made on the control block pointers to prevent the loop. 06. The processing of concurrent abends from the IDIXDCAP exit within an address space has been changed to not wait on the ENQ.
Temporary fix
Comments
APAR Information
APAR number
PM08932
Reported component name
FAULT ANALYZER
Reported component ID
5655V5100
Reported release
A10
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2010-03-04
Closed date
2010-04-07
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:
UK55782
Modules/Macros
CDISDTFJ CDISJL CDISWRAP GDIPFMIP GDIPH134 GDIPH144 GDIPH231 HADQA10J IDIAHSFM IDIASFM IDIAUSUA IDICAB ***This field was truncated. To obtain the full apar record, please contact your local support center.***
Fix information
Fixed component name
FAULT ANALYZER
Fixed component ID
5655V5100
Applicable component levels
RA10 PSY UK55782
UP10/04/10 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":"A10","Edition":"","Line of Business":{"code":"","label":""}},{"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSXJAJ","label":"Fault Analyzer for z\/OS"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"A10","Edition":"","Line of Business":{"code":"LOB35","label":"Mainframe SW"}}]
Document Information
Modified date:
04 May 2010