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 13 users. * **************************************************************** * PROBLEM DESCRIPTION: 01. MSGIDI0103I when LLA managed load * * module part of analysis. * * APAR PI74277 * * 02. ABEND0C4 in IDISAMAN after S222. * * APAR PI74105 * * 03. "Data set is not a history file" * * message issued incorrectly. * * APAR PI74743 * * 04. Excessive CPU used when processing * * PL/I SYSDEBUG that has many * * structure assignments. * * APAR PI78883 * * 05. CEE0802C Heap storage control * * information was damaged. From entry * * point CFREE at statement 362 at * * compile unit offset +00000410 at * * entry offset +00000410. * * APAR PI75241 * * 06. No CICS USER or CICS 64-bit storage * * displayed in CICS storage summary * * section of FA report. * * APAR PI75686 * * 07. Abend S0C4 at xmemmove + X'29C88'. * * APAR PI76036 * * 08. FA does not report COBOL V5/V6 * * Working Storage when NORENT * * compiler option in effect. * * APAR PI76037 * * 09. Loop in IDIXDCAP processing a * * system abend in CICS address space. * * It is also possible to experience * * an ABEND0C1 in IDIXDCAP with this * * problem. * * APAR PI76210 * * 10. Message IDI0005S out-of-storage * * conditions in the Fault Analyzer * * ISPF interface (IDIPDDIR). * * APAR PI76302 * * 11. Incorrect source line reported * * when COBOL V5/V6 program * * re-compiled with TEST option and * * source changes. * * APAR PI78885 * * 12. IDI0005S when processing COBOL * * listing. * * APAR PI76914 * * 13. Redundant messages for LANG(JPN) * * APAR PI77528 * * 14. IDIALLOC DEST allocates DUMMY * * APAR PI77888 * **************************************************************** * RECOMMENDATION: Apply the provided PTF. * **************************************************************** 01. When an LLA managed load module is part of analysis then a bad concatenation number is used to locate the module data set for the binder. 02. Register not initialized correctly. 03. A migrated data set is part of a VIEW. Attempting to use the VIEW results in a "data set is not a history file" message. 04. Structure assignments result in many automonitor entries causing bad performance when creating xref entries. 05. LOOKUP command causes LE heap storage corruption. 06. This data had not been included when 64 bit storage was added to CICS API. 07. Incorrect length used when moving a character string. 08. NORENT static expected from IGZXAPI, but gives rc = -5. 09. Code that sets a base register was bypassed leading to an incorrect branch. 10. An increased amount of storage was required per fault entry displayed. 11. There is no mechanism for checking that the DWARF in deferred load segments matches the program CSECT in the fault entry. 12. One of the processing routines was not FREEing all storage that had been getmained during its processing. 13. Duplicate messages are being output when LANG(JPN) is used. 14. Internal field was too small to receive the specification and triggered a dummy allocation.
Problem conclusion
01. BLDL is used to identify the correct data set for the binder. 02. Register is initialized before referencing storage. 03. Fault Analyzer will now recall the data set before testing the data set characteristics when the data set is defined to a VIEW. 04. New xref info in SYSDEBUG now used for EPLI V4R1 on. 05. The LE heap storage corruption problem has been addressed. 06. USER64 and CICS64 storage now included in report. 07. The length has been corrected. 08. NORENT static address retrieved from PPA4. 09. Base register is set properly. 10. The Fault Entry List display has been redesigned to require less storage. 11. RFE87874 introduces an md5 checksum into both the program CSECT and the DWARF. 12. All storage is now FREEd. 13. Duplicate messages have been removed. 14. IDIALLOC is corrected to allocate the SYSOUT DEST file.
Temporary fix
Comments
APAR Information
APAR number
PI74739
Reported component name
FAULT ANALYZER
Reported component ID
5655Q1100
Reported release
D10
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
YesSpecatt / CST / Xsystem
Submitted date
2017-01-10
Closed date
2017-03-28
Last modified date
2017-04-19
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UI45945
Modules/Macros
HADQD10J IDICABND IDICADYN IDICASUB IDICCFND IDICOPYR IDICRXDX IDICRXEI IDICRXET IDICRXHC IDICSMF IDICSPC IDICSV15 IDICUXCS IDICUXWR IDIDA IDIDATST IDIGMAIN IDIGUOPT IDIHPMSG IDIJAGNQ IDIJAGNT IDIMCICS IDINDEX IDIPDA IDIPDDIR IDIPDSCU IDISAMAN IDISCJST IDISDB2P IDISDB2S IDISFPEX IDISIFND IDISJL IDISJLD IDISJLDQ IDISJLOG IDISJLQ IDISLKUP IDISLOG IDISLRAC IDISMAIN IDISREG IDISRFRD IDISROPT IDISTIME IDISUOPT IDISUPDI IDISVIEW IDISWRAP IDISWRAQ IDIUOPT IDIUTIL IDIVPCOB IDIXDCAP IDIXLINK IDIXOPT
Fix information
Fixed component name
FAULT ANALYZER
Fixed component ID
5655Q1100
Applicable component levels
RD10 PSY UI45945
UP17/03/31 P F703
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":"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":"D10","Edition":"","Line of Business":{"code":"LOB35","label":"Mainframe SW"}}]
Document Information
Modified date:
19 April 2017