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. CICS log reports message * * DFHAP1212 for program IDIXCCEE. * * APAR PM82072 * * 02. MSG IDI0005S IDIDODSN:2646 Storage * * allocation failed. Fault Analyzer * * analysis "file" menu option 5 of an * * SVC DUMP. * * APAR PM82073 * * 03. The CICS Domain Manager screen * * displays an incorrect Phase value. * * Values of -F900 are shown instead * * of -0700, for example. * * APAR PM82074 * * 04. Abend code blank in report * * generated by IDIUTIL LISTHF with * * LISTHF user exit. * * APAR PM82075 * * 05. IDI0115E LE enclave abend S002 and * * IDI0120S IBM Fault Analyzer * * internal abend S002 U0000. * * APAR PM82076 * * 06. SYSIDIDA.SYSOUT GRS resource * * contention due to a large number of * * abending TCBs attempting to invoke * * Fault Analyzer simultaneously. * * APAR PM82077 * * 07. Fault Analyzer runs out of memory * * when processing a large inactive * * COBOL program's working-storage. * * APAR PM82078 * * 08. Debug Tool customer using HLASM * * LANGX can have bad R0 and R4 values * * displayed because EQALANGX can end * * up incorrectly putting label flag * * on some registers. * * APAR PM81983 * * 09. CICS file owning region might get * * storage overlay SM0102 with Fault * * Analyzer running. * * APAR PM82079 * * 10. Message IDI0047S abend S0C4 and * * CICS region abend S40D reason code * * X'18'. * * APAR PM82080 * * 11. Message IDI0047S abend S0C4 at * * entry point CompMsgs. * * APAR PM82081 * * 12. An abend (code 0C4/AKEA) has * * occurred at offset X'00005BA0' in * * module IDIXCX53. * * APAR PM81910 * * 13. Loop during analysis in dfhs_afcb. * * APAR PM82082 * * 14. Various CICS abends during the * * capture of the 3270 buffer. * * APAR PM82083 * * 15. IDILANGX RC=1051 when processing * * PL/I compiler listing with many * * external variables. * * APAR PM82084 * * 16. Abend in DFHSUEX when a CICS * * task is purged during FA analysis. * * APAR PM82865 * * 17. In the General Purpose Registers * * display under the Fault Analyzer * * Eclipse plug-in, the * * source/statement line number is * * truncated. * * APAR PM83909 * **************************************************************** * RECOMMENDATION: Apply the provided PTF. * **************************************************************** 01. Fault Analyzer's sample CICS program definitions do not match what CICS thinks is inside the program. 02. During analysis of an SVC or SYSMDUMP containing COBOL, the process might run out of storage with message IDI0005S. 03. The Phase value was being incorrectly interpreted, leading to incorrect negative values. 04. ENV.ABEND_CODE was not initialized correctly for an EXEC CICS DUMP fault. 05. A record exceeding the maximum history file LRECL of 10000 bytes was attempted written to the fault entry. 06. Serializing Fault Analyzer IDIDA execution between abending TCBs in an address space using the SYSIDIDA.SYSOUT GRS resource name is in accordance with the current design. 07. Re-allocation of BLW storage as base locators are processed requires an unnecessary large amount of duplicated memory. 08. D/T monitor function might show wrong information for some registers when debugging HLASM programs because EQALANGX data is wrong. 09. A CICS region with many open files might get storage overlay with IBM Fault Analyzer active. 10. The Fault Analyzer IDIDA TCB was attached with the wrong program protection key. 11. A message was issued prior to required initialization having been performed. 12. A field used to address an offset in the TCTTE was not being correctly initialised and hence could cause an exception du e to an invalid storage reference. 13. The end of the EXCI trace blocks was not being correctly identified and hence caused a loop. 14. CICS is abending the task when we would prefer it to return TERMERR condition. FA is trying to capture when the customer tells us that he knows there is no buffer to capture. 15. IDILANGX has a maximum of 1024 CSECTs. 16. A CICS task purge during FA's execution of an API command in the invocation exits did not allow for the subsequent restore of the application's API state. 17. The buffer used to store the line number text was being terminated one character too early.
Problem conclusion
01. IDISCICS sample member has been changed to remove the LANGUAGE() keywords from FA programs. This stops CICS from reporting a mismatch. 02. The storage managemant for Base Locator logic has been changed to reduce the storage required for analysis. 03. The Phase value is now correctly interpreted. 04. ENV.ABEND_CODE is now initialized correctly for an EXEC CICS DUMP fault. 05. The data written is now split into multiple records if necessary. 06. A change has been made to not wait for a current IDIDA execution in the same address space to complete, but instead issue message IDI0123S and exit without performing analysis. 07. Working-storage is now allocated as a single area. 08. The code for setting the label flag has been updated. 09. The code has been corrected. 10. The Fault Analyzer IDIDA TCB is now attached with the correct program protection key. 11. A check has been added for the required initialization. 12. The field is now correctly initialised. 13. The end of the EXCI trace blocks is now correctly detected. 14. A new DD switch called IDINOCBR has been implemented in the CICS invocation exits, such that if there is an IDINOCBR DD card, no attempt will be made to capture the 3270 buffer. 15. Number of CSECT slots increased to 2048. 16. Purge protection has been placed around the invocation exit execution. 17. When terminating the line number buffer, the position at which a null terminator is added has been increased by one.
Temporary fix
Comments
APAR Information
APAR number
PM78351
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
2012-12-04
Closed date
2013-02-24
Last modified date
2013-04-02
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UK91960
Modules/Macros
HADQA10J IDI@HCRE IDI@HOTL IDI@HOTP IDICAASM IDICABND IDICADYN IDICAFAT IDICALE IDICALOC IDICASUB IDICBD ***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 UK91960
UP13/03/04 P F303
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:
02 April 2013