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 11 users. * **************************************************************** * PROBLEM DESCRIPTION: 01. CICS log reports message * * DFHAP1212 for program IDIXCCEE. * * APAR PM80560 * * 02. MSG IDI0005S IDIDODSN:2646 Storage * * allocation failed. Fault Analyzer * * analysis "file" menu option 5 of an * * SVC DUMP. * * APAR PM82064 * * 03. The CICS Domain Manager screen * * displays an incorrect Phase value. * * Values of -F900 are shown instead * * of -0700, for example. * * APAR PM82065 * * 04. User is analyzing a CICS SDUMP and * * displaying the RM Domain Unit Of * * Work summary. In certain * * situations, TranId is blank when it * * should have a TranId. * * APAR PM82066 * * 05. Abend code blank in report * * generated by IDIUTIL LISTHF with * * LISTHF user exit. * * APAR PM80346 * * 06. IDI0115E LE enclave abend S002 and * * IDI0120S IBM Fault Analyzer * * internal abend S002 U0000. * * APAR PM80521 * * 07. SYSIDIDA.SYSOUT GRS resource * * contention due to a large number of * * abending TCBs attempting to invoke * * Fault Analyzer simultaneously. * * APAR PM82067 * * 08. Fault Analyzer runs out of memory * * when processing a large inactive * * COBOL program's working-storage. * * APAR PM82068 * * 09. 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 PM81982 * * 10. CICS file owning region might get * * storage overlay SM0102 with Fault * * Analyzer running. * * APAR PM80829 * * 11. Message IDI0047S abend S0C4 and * * CICS region abend S40D reason code * * X'18'. * * APAR PM80860 * * 12. Message IDI0047S abend S0C4 at * * entry point CompMsgs. * * APAR PM82069 * * 13. Loop during analysis in dfhs_afcb. * * APAR PM82070 * * 14. IDILANGX RC=1051 when processing * * PL/I compiler listing with many * * external variables. * * APAR PM81680 * * 15. Various CICS abends during the * * capture of the 3270 buffer. * * APAR PM82071 * * 16. Abend in DFHSUEX when a CICS * * task is purged during FA analysis. * * APAR PM82864 * * 17. Recycle of CICS required to pick up * * new copy of FA CICS invocation exit * * program IDIXCMnn. * * APAR PM83211 * * 18. In the General Purpose Registers * * display under the Fault Analyzer * * Eclipse plug-in, the * * source/statement line number is * * truncated. * * APAR PM81064 * **************************************************************** * 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. FA is obtaining the Transaction Id from a place which does not always have the ID. 05. ENV.ABEND_CODE was not initialized correctly for an EXEC CICS DUMP fault. 06. A record exceeding the maximum history file LRECL of 10000 bytes was attempted written to the fault entry. 07. 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. 08. Re-allocation of BLW storage as base locators are processed requires an unnecessary large amount of duplicated memory. 09. D/T monitor function might show wrong information for some registers when debugging HLASM programs because EQALANGX data is wrong. 10. A CICS region with many open files might get storage overlay with IBM Fault Analyzer active. 11. The Fault Analyzer IDIDA TCB was attached with the wrong program protection key. 12. A message was issued prior to required initialization having been performed. 13. The end of the EXCI trace blocks was not being correctly identified and hence caused a loop. 14. IDILANGX has a maximum of 1024 CSECTs. 15. 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. 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. Existing logic in the CFA transaction issued a NEWCOPY command for IDIXCX53. However, this program subsequently invoked IDIXCMnn, which was not being refreshed. As such, a recycle of CICS was required to pick up a new IDIXCMnn module. 18. 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. FA has been changed to obtain the Transaction Id from a more reliable location. 05. ENV.ABEND_CODE is now initialized correctly for an EXEC CICS DUMP fault. 06. The data written is now split into multiple records if necessary. 07. 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. 08. Working-storage is now allocated as a single area. 09. The code for setting the label flag has been updated. 10. The code has been corrected. 11. The Fault Analyzer IDIDA TCB is now attached with the correct program protection key. 12. A check has been added for the required initialization. 13. The end of the EXCI trace blocks is now correctly detected. 14. Number of CSECT slots increased to 2048. 15. 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. 16. Purge protection has been placed around the invocation exit execution. 17. The NEWCOPY process provided in the CFA transaction has been extended to also refresh the IDIXCMnn module. 18. 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
PM78350
Reported component name
FAULT ANALYZER
Reported component ID
5655W4600
Reported release
B10
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2012-12-04
Closed date
2013-02-22
Last modified date
2013-03-04
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UK91900
Modules/Macros
HADQB10J IDIALLOC IDICAASM IDICABND IDICALE IDICALOC IDICASUB IDICCFND IDICISA IDICNF00 IDICNOTR IDICOP ***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
5655W4600
Applicable component levels
RB10 PSY UK91900
UP13/02/28 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"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"B10","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":"B10","Edition":"","Line of Business":{"code":"LOB35","label":"Mainframe SW"}}]
Document Information
Modified date:
04 March 2013