Latest Fault Analyzer for z/OS Service Information

Technote (FAQ)


Question

What is the latest PTF level for Fault Analyzer and how do I determine my current Fault Analyzer PTF service level?

Answer

NOTE: Make sure you review the Preventive Service Planning (PSP) information here and specify FAULTANALYZE as the Upgrade Name for the PSP bucket. The PSP bucket provides the following information:

  • Installation information
  • Documentation changes
  • General information
  • Service recommendations
  • Cross product dependencies

How can I sign up to automatically receive email notification when a new PTF is available?


For Version 13 PTFs click here
For Version 12 PTFs click here
For Version 11 PTFs click here
For Version 10 PTFs click here

All available Version 13 Fault Analyzer PTFs and associated APARs (most recent first):

English Base Component
Japanese Feature
Korean Feature
PTF Download links
UI17255 Download PTF UI17255
UI14757 Download PTF UI14757
UI13465 Download PTF UI13465
UI12445 Download PTF UI12445

PTF
Availability date
Prerequisite PTFs
Supercedes these PTFs
APAR(s) this PTF fixes
English:
UI17255
2 May 2014 UI14757 PI11055
PI11288
PI16310
PI16311
PI16312
PI16313
PI16314
PI16315
PI16316
PI16317
PI16318
PI16464
English:
UI14757
7 Feb 2014 UI12445
UI13465
PI08456
PI10664
PI10665
PI10666
PI10667
PI10668
PI10669
PI10670
PI10671
PI10672
PI10673
PI10674
PI10699
English:
UI13465
2 Jan 2014 UI12445 PI06353
PI07744
PI07745
PI07746
PI07747
PI07748
PI07749
PI07750
PI07751
PI07753
PI07754
PI07755
PI07756
PI07857
English:
UI12445
16 Nov 2013 PI05467
PI05468
PI05469
PI05470
PI05471
PI05472
PI05570
PM99413
APAR PI11055 Fixes and Enhancements
Problem
Description
Fix
Complete APAR information
1 Incorrect Compiler Listing display pseudo assembler instructions default setting. The product default, when the user has not yet selected either "Add Pseudo Assembler Instructions" or "Remove Pseudo Assembler Instructions" from the action-bar View pull-down menu, is to show the pseudo assembler instructions. This is incorrect according to the documentation. The product default has been changed to not include the pseudo assembler instructions in the Compiler Listing display. PI11288
2 Abend S0C4 in IDIXDCAP with messages IDI0012S and IDI0013S. A zero value while looping through a set of data was not being correctly allowed for. A zero value is now correctly handled. PI16310
3 Fault Analyzer loop when trying to display Java event. If a Java source file can not be successfully opened, then the code might loop. The code has been corrected to prevent the loop. PI16311
4 CICS formatted trace entries are missing location information following the colon, as in "Called-from-address <address> : <location>". 64-bit addresses were not handled correctly. 64-bit addresses are now being handled correctly. PI16312
5 Too many allocations of the Fault Analyzer history file. A frequently used system service is causing dynamic allocation. The system service is now called using pre-allocation. PI16313
6 Console flooded with IDI0088E messages. Storage abend during ESTAE recovery while invoking the Binder program. The ESTAE is now cancelled before activity requiring virtual storage occurs. PI16314
7 CICS SDUMP PI Domain panels display incorrect information. CICS has changed the offsets of some fields within the PI domain control blocks. Fault Analyzer has been changed to use correct offsets for the PI domain. PI16315
8 Fault Analyzer IMS BMP user ID wrong. The user ID reported by Fault Analyzer for a BMP might be the program name instead of the user ID. The code has been corrected to ensure the input IOPCB user ID is only used for IMS message processing regions. PI16316
9 Message IDI0131W Waiting for history-file($$INDEX) SPFEDIT ENQ when ENQ is held by a TSO user. Abend in a TSO screen running Fault Analyzer might leave the $$INDEX ENQ outstanding until the TSO session is logged off. Code added to help DEQ processing in the case of Fault Analyzer abending in TSO/ISPF. PI16317
10 IMS MPP terminating but does not end. The MPP termination was held up by Fault Analyzer processing that had stalled. Monitor task added to ensure the IDIDA TCB attaches and runs successfully. PI16318
11 CICS abend ASRA in XEIIN GLUE with CICS/TS 3.2. An incorrect CICS XPI command was being used with CICS/TS 3.2. The XPI command has been corrected. PI16464
APAR PI08456 Fixes and Enhancements
Problem
Description
Fix
Complete APAR information
1 When processing CICS Trace entries to determine source line #, the mismatch pop-up is presented, even though the COBOL SYSDEBUG file matches. DEBUGINF is not in the minidump. DEBUGINF added to minidump during COBOL CLLE discovery. PI10664
2 Cursor scrolling not working correctly on the CICS Internal Trace display, Saved Report display and Compiler Listing display. The saved cursor position was being retrieved from an incorrect variable. The saved cursor position is now retrieved from the correct variable. PI10665
3 Error message "Not a history file" when specifying a migrated data set name on the Fault Entry List display. The check for expected history file attributes failed when the data set was migrated. An additional check for a migrated data set has been added, prior to the attribute check. PI10666
4 IMS region shutdown held up by Fault Analyzer abend processing when initial abend TCB is holding LE MSGFILE ENQ. The IMS region would not shut down or cancel because the Fault Analyzer IDIDA analysis task was in an ENQ deadlock with the abending TCB, which had abended in LE code while holding the LE MSGFILE ENQ. Code has been added to break the deadlock. PI10667
5 Fault Analyzer IDIS subsystem might get recursive IDI0144E and IDI0124E messages. If the XCF message chain pointer is overlayed, the IDIS subsystem might get recursive abends with messages IDI0144E and IDI0124E. The logic has been updated to resolve the chaining error. PI10668
6 Blank saved report displayed with 'V' or 'S' line command if history file specified using single quotes in a View member. The single quotes were not expected and caused fopen of the fault entry member to fail without an error message being issued. An error message will be issued if failing to open the fault entry member and specification of single quotes around View member history file names has been supported. PI10669
7 Plugin history file MODULE column shows information that differs from the equivalent column displayed with the Fault Analyzer ISPF interface. The plugin history file MODULE column value is showing the module name associated with the initial abend as opposed to the point of failure. The plugin history file MODULE column is now showing the point-of-failure module name. PI10670
8 Fault Analyzer report for IMS Java might show an additional incorrect LE U4038 abend in the event summary. IMS with Java and CEEPIPI might cause Fault Analyzer to add a historical CIB event incorrectly in the report. The condition has been catered for in the code. PI10671
9 Fault Analyzer might produce more than one RFR dump for one abend when short on storage. Recursion of S878 conditions during Recovery Fault Recording (RFR) processing can cause more than one SDUMP to be taken for the one initial abend. Code has been added to stop additional SDUMPs against one fault entry. PI10672
10 More than one fault entry might be created if the IDIS subsystem is experiencing Cross-System Coupling Facility (XCF) message delays. With XCF message delays in the IDIS subsystem, the recovery process might cause more than one fault entry to be created for the same abend job and timestamp. Code added to stop assignment of a new fault ID if one already exists for the same job and timestamp. PI10673
11 Message IDI0095 IDICABND:1415 CSVQUERY error. Some Fault Analyzer analysis jobs might get IDI0095W unexpected condition, CSVQUERY error. Code added to accommodate provider field request getting rc=4. PI10674
12 Message IDI0092S Time 32 minutes for analysis exceeded. Loop in code at entry point cDDfCloseP. The code has been fixed to prevent the loop from occurring. PI10699
APAR PI06353 Fixes and Enhancements
Problem
Description
Fix
Complete APAR information
1 FAISPFopts(InitHist(View(xxx))) option not taking effect. A check for an initialized default view name failed to recognize blanks as an uninitialized name. The check for an initialized default view name has been corrected. PI07744
2 Abend S23E after successful Fault Analyzer analysis of a CICS transaction abend. For LE transactions running on a L9 TCB, control was being returned to the Fault Analyzer invocation exit on the L9 TCB. A DETACH call could potentially be issued, which is not valid from the L9 TCB. The DETACH is now only attempted when running on the QR TCB. PI07745
3 MATCH CSR not working if help text is enabled, the display has been scrolled to hide the help text, and the cursor is placed in a field near the bottom of the display. The check for the cursor position within the ISPF dynamic area failed to correctly cater for the hidden help text. The problem has been corrected. PI07746
4 Extraneous subscript when formatting multi-dimension COBOL tables. Dimension not decremented correctly. Dimension decremented corrected. PI07747
5 Fault Analyzer IDIS subsystem IDI0095W ENQ ECB status error and IDI0131WENQ delay lockout on history file. When XCF message delays occur, the IDIS subsystem recovery might get an ENQ status error that causes recurring IDI0131W messages until the IDIS subsystem is restarted. ENQ processing changed to accommodate the timing issues. PI07748
6 Storage overlay in fileLANGX() while processing scope records. Scope slot index is out of bounds. Scope slot index corrected. PI07749
7 Fault Analyzer gets a S0C4 abend at entry point pp_tctse_main when analyzing a dump. A storage overlay in the customer environment caused control blocks to contain invalid values. A text string was missing the terminating character, causing Faukt Analyzer to get a S0C4. The code was modified to limit the length of the string processed. PI07750
8 Abend S0C4 from entry point ProcHistDA statement 6965 offset X'81BA' when pressing Enter after selecting an empty history file for display. The determination of display characteristics to be used for the re-display did not correctly handle the situation where the history file contains zero fault entries. The problem has been corrected. PI07751
9 Incorrect Fault Entry List display scroll down action under CICS, when help text is enabled and the top-most fault entry is displayed. The ZSCROLLA value returned by VGET in this environment was not blank-padded as expected. The ZSCROLLA value is now processed correctly, regardless of blank-padding after VGET. PI07746
10 Symbol substitution not working in the alternative parmlib data set name specified via the IDIOPTLM configuration-options module field CNFDSN. The symbol substitution service output buffer length was set too short. The buffer length has been set to the correct value. PI07753
11 The user ID of an IMS abend is not displayed in the history file, like it is for CICS. The user ID displayed is the one from the job's ACEE. If a user ID is found in an IMS IOPCB, then it will be shown instead of the job's ACEE user ID. PI07754
12 Message "ICH409I 282-020 ABEND DURING RACHECK PROCESSING" during analysis of Java dump. A valid history file data set name had not been set from the Fault Entry List display prior to the dump analysis, resulting in a blank history file data set name being checked for access authorization. A check has been added for the existence of a non-blank history file data set name prior to the RACHECK call. PI07755
13 Fault Analyzer empty report, no events from RFR dump after IDI0055S out of storage message. The RFR SDUMP after an out of storage IDI0055S message might not get a TCB selected for analysis. The code has bee updated to determine the TCB issuing the RFR call. PI07756
14 Fault Analyzer might generate more than one fault entry for the same event. The additional fault entries have no minidump or report content. More than one fault entry for the same job and timestamp if delays in XCF coupling facility messages cause retransmit of a fault ID assignment. The code has been updated to cater for the potential re-transmission of an assignment request via XCF. PI07857
APAR PM99413 Fixes and Enhancements
Problem
Description
Fix
Complete APAR information
1 Fault Analyzer RFR dump event list might be missing events. The DSA chaining back through linkage stack entries might fail when an invalid backchain address in encountered. The code has been updated. PI05467
2 New History File Allocation dialog not shown when copying fault entry to non-existing history file. A check for the existence of the target history file was missing. A check has been added for the existence of the target history file. PI05468
3 A Fault Analyzer user is analyzing a CICS SDUMP, and sees errors in the DS Domain panels. DS panels have incomplete information due to an arbitrary limit to the number of internal control blocks that can be created. Also, there is a problem in sorting some column contents. The number of internal control blocks which can be created has been increased. The panel column sort code has been fixed. PI05469
4 User is analyzing a CICS TS 3.1 SDUMP and gets an 0C4 abend in function pp_ke_stack. pp_ke_stack is processing a stack entry for CICS program DFHLEPTQ, which has an invalid (negative) iproc offset. This causes pp_ke_stack to abend. pp_ke_stack has been modified to handle the bad offset. PI05470
5 0C1/AKEA or ASRA abend in IDIXCX53 with CICS/TS 3.1 An XPI call was not correctly allowing for earlier version of CICS. The XPI has been corrected accordingly. PI05471
6 User gets DFHSR0622 because of abend 0C4 in CEECGEX. User has issued PURGE of CICS task. FA's IDIXCCEE issues EXEC CICS commands in CICSkey and enters WAIT_MVS. User issues KILL for task. CICS drives LE CEECGEX in USERkey with CICSkey DSA/RSA from IDIXCCEE. IDIXCCEE has been changed to percolate (defer) AEXY abends to FA CICS GLUEs, which do not issue EXEC CICS commands in a way that can cause the problem. PI05472
7 Fault Analyzer IDIS subsystem IDI0131W messsages ENQ lockout on history files. APAR PM97968 fixed the 100% CPU loop reported but the IDI0131W messages can still occur. This APAR addresses the IDI0131W ENQ message not clearing. Code added to correctly retest the ENQ status. PI05570
8 Occasionally, requests made in the web interface (such as downloading a large history file) will fail to return correctly. When parsing large responses in the web back-end, a check is made to determine whether a complete response has been received. In some cases, unrelated logging statements were being included in server communications, which interfered with this condition checking. Response parsing has been improved to handle unexpected messages being included in server communication. PI06134

All available Version 12 Fault Analyzer PTFs and associated APARs (most recent first):

English Base Component
Japanese Feature
Korean Feature
PTF Download links
UI17281 Download PTF UI17281
UI14758 Download PTF UI14758
UI13466 Download PTF UI13466
UI12501 Download PTF UI12501
UK98036 Download PTF UK98036
UK97174 Download PTF UK97174
UK96928 Download PTF UK96928
UK95217 Download PTF UK95217
UK93704 Download PTF UK93704
UK91859 Download PTF UK91859
UK83720 Download PTF UK83720
UK82439 Download PTF UK82439
UK80540 Download PTF UK80540
UK79416 Download PTF UK79416

PTF
Availability date
Prerequisite PTFs
Supercedes these PTFs
APAR(s) this PTF fixes
English:
UI17281
2 May 2014 UI14758 PI11056
PI12474
PI14986
PI16210
PI16212
PI16216
PI16308
PI16309
PI16319
PI16320
PI16321
PI16322
PI16465
English:
UI14758
7 Feb 2014 UI12501
UI13466
UK79416
UK80540
UK82439
UK83720
UK91859
UK93704
UK95217
UK96928
UK97174
UK98036
PI08017
PI08081
PI08457
PI09075
PI09306
PI10568
PI10569
PI10570
PI10572
PI10573
PI10574
PI10575
PI10698
English:
UI13466
2 Jan 2014 UI12501
UK79416
UK80540
UK82439
UK83720
UK91859
UK93704
UK95217
UK96928
UK97174
UK98036
PI05961
PI06354
PI06731
PI06856
PI07106
PI07405
PI07740
PI07742
PI07743
PI07757
PI07758
PI07759
PI07760
PI07784
English:
UI12501
16 Nov 2013 UK79416
UK80540
UK82439
UK83720
UK91859
UK93704
UK95217
UK96928
UK97174
UK98036
PI04718
PI05253
PI05466
PI05571
PM98460
PM98853
PM98998
PM99268
PM99489
PM99772
English:
UK98036
3 Oct 2013 UK79416
UK80540
UK82439
UK83720
UK91859
UK93704
UK95217
UK96928
UK97174
PM94889
PM96029
PM96373
PM96423
PM97404
PM97479
PM97964
PM97966
PM97967
PM97968
English:
UK97174
6 Sep 2013 UK95217 UK96928 PM95842
PM96144
PM96147
English:
UK96928
30 Aug 2013 UK95217 PM91555
PM92323
PM92577
PM92984
PM93127
PM93221
PM95067
PM95323
PM95324
PM95325
PM95326
PM95327
English:
UK95217
21 Jun 2013 UK79416
UK80540
UK82439
UK83720
UK91859
UK93704
PM87461
PM88084
PM88223
PM89702
PM89900
PM91068
PM91069
PM91070
PM91071
PM91251
English:
UK93704
25 Apr 2013 UK79416
UK80540
UK82439
UK83720
UK91859
PM83447
PM83725
PM83748
PM83917
PM84239
PM86443
PM87064
PM87065
PM87074
PM87125
PM87189
PM87303
PM87423
PM87457
PM87458
PM87459
PM87460
PM87463
PM87464
PM87465
PM87466
PM87467
PM87468
PM87469
PM87478
PM87576
English:
UK91859
4 Mar 2013 UK79416
UK80540
UK82439
UK83720
PM77622
PM78349
PM79946
PM79983
PM80077
PM80461
PM80858
PM81759
PM81847
PM81864
PM81915
PM81980
PM81981
PM82060
PM82061
PM82062
PM82063
PM82496
PM82554
PM82756
PM83908
English:
UK83720
2 Jan 2013 UK79416
UK80540
UK82439
PM74985
PM75980
PM77003
PM77093
PM77640
PM77672
PM77673
PM77674
PM77675
PM77676
PM77677
PM77678
PM77679
PM77680
PM77681
PM77682
PM77683
English:
UK82439
1 Nov 2012 UK79416
UK80540
PM70210
PM72786
PM72792
PM72796
PM72797
PM72799
PM72800
PM72801
PM72802
PM73772
PM74209
PM74212
PM74214
English:
UK80540
7 Aug 2012 UK79416 PM67619
PM68989
PM68991
PM68993
PM68994
PM68995
PM68996
PM69468
PM69469
English:
UK79416
25 Jun 2012 PM64218
PM64341
PM65401
PM65402
PM65403
PM65404
PM65405
PM65406
PM66966
PM67216
APAR PI11056 Fixes and Enhancements
Problem
Description
Fix
Complete APAR information
1 Incorrect Compiler Listing display pseudo assembler instructions default setting. The product default, when the user has not yet selected either "Add Pseudo Assembler Instructions" or "Remove Pseudo Assembler Instructions" from the action-bar View pull-down menu, is to show the pseudo assembler instructions. This is incorrect according to the documentation. The product default has been changed to not include the pseudo assembler instructions in the Compiler Listing display. PI16319
2 Abend S0C4 in IDIXDCAP with messages IDI0012S and IDI0013S. A zero value while looping through a set of data was not being correctly allowed for. A zero value is now correctly handled. PI16210
3 Fault Analyzer loop when trying to display Java event. If a Java source file can not be successfully opened, then the code might loop. The code has been corrected to prevent the loop. PI16212
4 CICS formatted trace entries are missing location information following the colon, as in "Called-from-address <address> : <location>". 64-bit addresses were not handled correctly. 64-bit addresses are now being handled correctly. PI12474
5 Too many allocations of the Fault Analyzer history file. A frequently used system service is causing dynamic allocation. The system service is now called using pre-allocation. PI16320
6 Console flooded with IDI0088E messages. Storage abend during ESTAE recovery while invoking the Binder program. The ESTAE is now cancelled before activity requiring virtual storage occurs. PI16321
7 CICS SDUMP PI Domain panels display incorrect information. CICS has changed the offsets of some fields within the PI domain control blocks. Fault Analyzer has been changed to use correct offsets for the PI domain. PI14986
8 Fault Analyzer IMS BMP user ID wrong. The user ID reported by Fault Analyzer for a BMP might be the program name instead of the user ID. The code has been corrected to ensure the input IOPCB user ID is only used for IMS message processing regions. PI16216
9 IDILANGX ends with CEE0802C at entry point LSMMFREE. Max locates records causes write buffer overrun. Max locates records reduced to fit write buffer. PI16322
10 Message IDI0131W Waiting for history-file($$INDEX) SPFEDIT ENQ when ENQ is held by a TSO user. Abend in a TSO screen running Fault Analyzer might leave the $$INDEX ENQ outstanding until the TSO session is logged off. Code added to help DEQ processing in the case of Fault Analyzer abending in TSO/ISPF. PI16308
11 IMS MPP terminating but does not end. The MPP termination was held up by Fault Analyzer processing that had stalled. Monitor task added to ensure the IDIDA TCB attaches and runs successfully. PI16309
12 CICS abend ASRA in XEIIN GLUE with CICS/TS 3.2. An incorrect CICS XPI command was being used with CICS/TS 3.2. The XPI command has been corrected. PI16465
APAR PI08457 Fixes and Enhancements
Problem
Description
Fix
Complete APAR information
1 When processing CICS Trace entries to determine source line #, the mismatch pop-up is presented, even though the COBOL SYSDEBUG file matches. DEBUGINF is not in the minidump. DEBUGINF added to minidump during COBOL CLLE discovery. PI08017
2 Cursor scrolling not working correctly on the CICS Internal Trace display, Saved Report display and Compiler Listing display. The saved cursor position was being retrieved from an incorrect variable. The saved cursor position is now retrieved from the correct variable. PI08081
3 Error message "Not a history file" when specifying a migrated data set name on the Fault Entry List display. The check for expected history file attributes failed when the data set was migrated. An additional check for a migrated data set has been added, prior to the attribute check. PI10568
4 IMS region shutdown held up by Fault Analyzer abend processing when initial abend TCB is holding LE MSGFILE ENQ. The IMS region would not shut down or cancel because the Fault Analyzer IDIDA analysis task was in an ENQ deadlock with the abending TCB, which had abended in LE code while holding the LE MSGFILE ENQ. Code has been added to break the deadlock. PI10572
5 Fault Analyzer IDIS subsystem might get recursive IDI0144E and IDI0124E messages. If the XCF message chain pointer is overlayed, the IDIS subsystem might get recursive abends with messages IDI0144E and IDI0124E. The logic has been updated to resolve the chaining error. PI10569
6 Blank saved report displayed with 'V' or 'S' line command if history file specified using single quotes in a View member. The single quotes were not expected and caused fopen of the fault entry member to fail without an error message being issued. An error message will be issued if failing to open the fault entry member and specification of single quotes around View member history file names has been supported. PI09075
7 Plugin history file MODULE column shows information that differs from the equivalent column displayed with the Fault Analyzer ISPF interface. The plugin history file MODULE column value is showing the module name associated with the initial abend as opposed to the point of failure. The plugin history file MODULE column is now showing the point-of-failure module name. PI09306
8 Fault Analyzer report for IMS Java might show an additional incorrect LE U4038 abend in the event summary. IMS with Java and CEEPIPI might cause Fault Analyzer to add a historical CIB event incorrectly in the report. The condition has been catered for in the code. PI10570
9 Fault Analyzer might produce more than one RFR dump for one abend when short on storage. Recursion of S878 conditions during Recovery Fault Recording (RFR) processing can cause more than one SDUMP to be taken for the one initial abend. Code has been added to stop additional SDUMPs against one fault entry. PI10573
10 More than one fault entry might be created if the IDIS subsystem is experiencing Cross-System Coupling Facility (XCF) message delays. With XCF message delays in the IDIS subsystem, the recovery process might cause more than one fault entry to be created for the same abend job and timestamp. Code added to stop assignment of a new fault ID if one already exists for the same job and timestamp. PI10574
11 Message IDI0095 IDICABND:1415 CSVQUERY error. Some Fault Analyzer analysis jobs might get IDI0095W unexpected condition, CSVQUERY error. Code added to accommodate provider field request getting rc=4. PI10575
12 Message IDI0092S Time 32 minutes for analysis exceeded. Loop in code at entry point cDDfCloseP. The code has been fixed to prevent the loop from occurring. PI10698
APAR PI06354 Fixes and Enhancements
Problem
Description
Fix
Complete APAR information
1 FAISPFopts(InitHist(View(xxx))) option not taking effect. A check for an initialized default view name failed to recognize blanks as an uninitialized name. The check for an initialized default view name has been corrected. PI05961
2 Abend S23E after successful Fault Analyzer analysis of a CICS transaction abend. For LE transactions running on a L9 TCB, control was being returned to the Fault Analyzer invocation exit on the L9 TCB. A DETACH call could potentially be issued, which is not valid from the L9 TCB. The DETACH is now only attempted when running on the QR TCB. PI07757
3 MATCH CSR not working if help text is enabled, the display has been scrolled to hide the help text, and the cursor is placed in a field near the bottom of the display. The check for the cursor position within the ISPF dynamic area failed to correctly cater for the hidden help text. The problem has been corrected. PI07758
4 Fault Analyzer IDIS subsystem IDI0095W ENQ ECB status error and IDI0131WENQ delay lockout on history file. When XCF message delays occur, the IDIS subsystem recovery might get an ENQ status error that causes recurring IDI0131W messages until the IDIS subsystem is restarted. ENQ processing changed to accommodate the timing issues. PI06731
5 Extraneous subscript when formatting multi-dimension COBOL tables. Dimension not decremented correctly. Dimension decremented corrected. PI07759
6 Storage overlay in fileLANGX() while processing scope records. Scope slot index is out of bounds. Scope slot index corrected. PI06856
7 Fault Analyzer gets a S0C4 abend at entry point pp_tctse_main when analyzing a dump. A storage overlay in the customer environment caused control blocks to contain invalid values. A text string was missing the terminating character, causing Faukt Analyzer to get a S0C4. The code was modified to limit the length of the string processed. PI07743
8 Abend S0C4 from entry point ProcHistDA statement 6965 offset X'81BA' when pressing Enter after selecting an empty history file for display. The determination of display characteristics to be used for the re-display did not correctly handle the situation where the history file contains zero fault entries. The problem has been corrected. PI07106
9 Incorrect Fault Entry List display scroll down action under CICS, when help text is enabled and the top-most fault entry is displayed. The ZSCROLLA value returned by VGET in this environment was not blank-padded as expected. The ZSCROLLA value is now processed correctly, regardless of blank-padding after VGET. PI07758
10 Symbol substitution not working in the alternative parmlib data set name specified via the IDIOPTLM configuration-options module field CNFDSN. The symbol substitution service output buffer length was set too short. The buffer length has been set to the correct value. PI07405
11 The user ID of an IMS abend is not displayed in the history file, like it is for CICS. The user ID displayed is the one from the job's ACEE. If a user ID is found in an IMS IOPCB, then it will be shown instead of the job's ACEE user ID. PI07760
12 Message "ICH409I 282-020 ABEND DURING RACHECK PROCESSING" during analysis of Java dump. A valid history file data set name had not been set from the Fault Entry List display prior to the dump analysis, resulting in a blank history file data set name being checked for access authorization. A check has been added for the existence of a non-blank history file data set name prior to the RACHECK call. PI07740
13 Fault Analyzer empty report, no events from RFR dump after IDI0055S out of storage message. The RFR SDUMP after an out of storage IDI0055S message might not get a TCB selected for analysis. The code has bee updated to determine the TCB issuing the RFR call. PI07742
14 Fault Analyzer might generate more than one fault entry for the same event. The additional fault entries have no minidump or report content. More than one fault entry for the same job and timestamp if delays in XCF coupling facility messages cause retransmit of a fault ID assignment. The code has been updated to cater for the potential re-transmission of an assignment request via XCF. PI07784
APAR PM98460 Fixes and Enhancements
Problem
Description
Fix
Complete APAR information
1 Fault Analyzer RFR dump event list might be missing events. The DSA chaining back through linkage stack entries might fail when an invalid backchain address in encountered. The code has been updated. PI04718
2 New History File Allocation dialog not shown when copying fault entry to non-existing history file. A check for the existence of the target history file was missing. A check has been added for the existence of the target history file. PM99268
3 A Fault Analyzer user is analyzing a CICS SDUMP, and sees errors in the DS Domain panels. DS panels have incomplete information due to an arbitrary limit to the number of internal control blocks that can be created. Also, there is a problem in sorting some column contents. The number of internal control blocks which can be created has been increased. The panel column sort code has been fixed. PM99489
4 User is analyzing a CICS TS 3.1 SDUMP and gets an 0C4 abend in function pp_ke_stack. pp_ke_stack is processing a stack entry for CICS program DFHLEPTQ, which has an invalid (negative) iproc offset. This causes pp_ke_stack to abend. pp_ke_stack has been modified to handle the bad offset. PM99772
5 When Eclipse/RDz/CICS Explorer is running in French, some text elements in the plug-in UI are shown as *PLACEHOLDER*. French translation support that was being added to a new release was included, but not updated, in the previous v12 service stream. French translations were backported to provide basic support in the v12 plug-in. PM98998
6 0C1/AKEA or ASRA abend in IDIXCX53 with CICS/TS 3.1 An XPI call was not correctly allowing for earlier version of CICS. The XPI has been corrected accordingly. PI05466
7 When using the Fault Analyzer plug-in and adding a view, an error dialog is shown that states "Software caused connection abort: recv failed". When sending multiple concurrent requests to the PD Tools Common Server, the Fault Analyzer plug-in might attempt to use the same socket more than once. This will cause a connection error and all current requests to fail. Server connections have been set to better handle multiple concurrent requests by synchronising and handling each request to avoid collisions. PM98853
8 User gets DFHSR0622 because of abend 0C4 in CEECGEX. User has issued PURGE of CICS task. FA's IDIXCCEE issues EXEC CICS commands in CICSkey and enters WAIT_MVS. User issues KILL for task. CICS drives LE CEECGEX in USERkey with CICSkey DSA/RSA from IDIXCCEE. IDIXCCEE has been changed to percolate (defer) AEXY abends to FA CICS GLUEs, which do not issue EXEC CICS commands in a way that can cause the problem. PI05253
9 Fault Analyzer IDIS subsystem IDI0131W messsages ENQ lockout on history files. APAR PM97968 fixed the 100% CPU loop reported but the IDI0131W messages can still occur. This APAR addresses the IDI0131W ENQ message not clearing. Code added to correctly retest the ENQ status. PI05571
APAR PM96423 Fixes and Enhancements
Problem
Description
Fix
Complete APAR information
1 Fault Analyzer report has 'no data' in the event list. If the MVS RB chain can not be traced because of a missing page in the minidump, the available list of events was not displayed. Code updated to better handle the next RB not being available. PM97966
2 The user is analyzing a CICS SDUMP and is seeing an incorrect task state in the DS Domain Task Summary panel. Task State is shown as "R" when it should be "A". FA CICS SDUMP analysis is interpreting a CICS status byte incorrectly. IDIECDS has been changed to interpret the task status byte correctly. PM96029
3 Cursor is placed on the Fault Entry List display command line after deletion of fault entry if option to confirm deletion is in effect. The original cursor position is not saved prior to displaying the delete confirmation panel. The cursor is now positioned correctly. PM96373
4 Fault entry duplicate count on the Fault Entry List display shows a negative or decreasing value. The duplicate count is held in a signed halfword which is displayed as a negative value if more than 32,767 duplicates have occurred, or a decreasing value if more than 65,535 duplicates have occurred. The duplicate count field is treated as unsigned, which allows for up to 65,535 duplicates. Once this limit is reached, the count will remain unchanged at its maximum instead of wrapping. PM97967
5 When refreshing a fault entry that does not contain a minidump, many error dialogs will be displayed. The missing minidump will cause a number of issues during the refresh, preventing it from properly completing. This error propagates, causing an error dialog to be created at each point of failure. Additional error handling was included to consolidate and simplify the error reporting when a minidump is not available. PM94889
6 Abend S282-20 when exiting interactive MVS dump analysis. The Fault Analyzer ISPF interface was invoked with a history file name set to a non-existing data set. A check has been added for the existence of the target history file to prevent the abend S282-20 from occurring. PM97479
7 IDI0047S from Fault Analyzer in MAPLMOD processing. Intermittent abend S0C4 in Fault Analyzer IDIDA MAPLMOD causing IDI0047S and an RFR dump to be created for recovery processing of the fault entry. The MAPLMOD processing updated to correctly test the return from GETDSVOL processing. PM97404
8 Fault Analyzer IDIS subsystem loop with IDI0131W message and high CPU. Under some XCF recovery conditions, the IDIS subsystem might loop causing high CPU usage. Code changed to handle the potential XCF recovery timing condition. PM97968
9 Message "ERROR: IactLEabend() can't be invoked from IDIPDDIR!" issued when looking up abend code explanation from Fault Entry List display. This is a diagnostic message that was incorrectly left as a message to the user rather than being written to a trace data set. The message is no longer displayed to the user and is only written to the trace data set. PM97964
APAR PM95842 Fixes and Enhancements
Problem
Description
Fix
Complete APAR information
1 Unable to Uninstall or Install CICS exits using CFA transaction for CICS/TS 4.2 and 5.1. The EXIT program name was being incorrectly set for CICS/TS 4.2 and 5.1. The EXIT program name is now correctly set for CICS/TS 4.2 and 5.1. PM96144
2 Abend S0C4 in IDIXCM68 when CICS LIBRARY in use. Incorrect addressing of a 64-bit control block. Addressing of the 64-bit control block has been corrected. PM96147
APAR PM91555 Fixes and Enhancements
Problem
Description
Fix
Complete APAR information
1 IBM Fault Analyzer IDI0095W Unexpected condition IDIDODSN:360 when exiting interactive analysis of an MVS dump. When completing an interactive reanalysis of an MVS SVC or SYSMDUMP, the write minidump process might issue IDI0095W from IDIDODSN:360. The logic has been changed to handle the allocation condition. PM95324
2 IDI0095W Unexpected condition found in IDISUPDI:1426: IDISUPDI:1851 :1426 dup time precedes fault entry. IBM Fault Analyzer CICS fast duplicate processing might record a vendor altered start time rather than the wall-clock time, even when the UseIDISTime option is set. Code updated to accommodate date/time alteration test products in the CICS fast duplicate recording process. PM95325
3 Listing exit issues IDISF messages when exit returns a SYSDEBUG dsn. Listing exit fails to process a SYSDEBUG, then attempts to process it as a compiler listing. Listing exit now correctly processes SYSDEBUG files. PM95326
4 COBOL ODO table has incorrect stride. ODO recalibration includes redefinitions which causes data item length to be added again. Only the original definition is inlcuded in recalibration of ODO tables. PM92323
5 After scrolling Fault Entry List display right, abend code explanation is shown instead of processing line command. When a point-and-shoot field, such as the "Abend" column field, is scrolled to logically overlap with the line command field, then the point-and-shoot field is incorrectly processed instead of the line command. An error determining the line offset in displays with a non-scrollable section on the left has been fixed. PM92577
6 Language Environment heap analysis errors not indicated in the Synopsis section of the report. The specific Language Environment heap analysis errors found in this case had not been made eligible for identification in the report Synopsis. All Language Environment heap analysis errors are now being identified in the Synopsis with a reference to detailed information about the errors in the Language Environment heap analysis section of the report. PM92984
7 Changes in CICS parm TRTRANSZ for CICS/TS 4.2 and 5.1 does not increase number of trace entries gathered by Fault Analyzer. The value of TRTRANSZ was being incorrectly determined and hence a default value of 64K was always being used by Fault Analyzer. The correct value of TRTRANSZ is now determined and used accordingly. PM95327
8 Lock flag incorrectly reset after fault entry interactive reanalysis when Enter is pressed on exit to save changes to user data. The fault entry lock flag was being managed, both in the fault entry member, and in the history file cache, causing incorrect updates. The fault entry lock flag is now only being managed in the history file cache. PM93221
9 Loop during abend analysis leading to IDI0005S message. FA code was not allowing for an LE CIB next pointer to be pointing to itself. Hence, FA went into a loop which eventually exhaused all storage and gave a IDI0005S message. Loop detection code added. PM95067
10 Fault Analyzer's CICS SDUMP "SM ECDSA Subpool Summary" panel displays some incorrect or unclear values, Some values are being obtained from the wrong place. Some values are correct but are displayed in hex, while the CICS VerbExit displays them in decimal. Fault Analyzer has been changed to display the correct values, and to display both hex and decimal values where appropriate. PM93127
11 Abend S0C4 in formatSummary at statement 531 compile unit offset X'199E'. An uninitialized variable was used. A check has been added to prevent the use of the uninitialized variable. PM95323
APAR PM88084 Fixes and Enhancements
Problem
Description
Fix
Complete APAR information
1 Analysis Control user exit ENV.IMS_PROGRAM_NAME blank when Fault Analyzer is invoked for an IMS user abend. The code which obtains the IMS program name was not executed due to NoDup(ImageFast(...)) processing being bypassed. The IMS program name is now obtained regardless of whether NoDup(ImageFast(...)) processing is bypassed or not. PM88223
2 The Language Environment STORAGE option was not being reported correctly. LE added a new value to the LE STORAGE option in z/OS V1R13. Updated our processing to handle all the new LE options and values added in z/OS V1R13. PM91069
3 IDIUTIL IMPORT function abend SE37 on target history file. IDIUTIL IMPORT does not honor SetMaxFaultEntries setting. IDIUTIL IMPORT now honors SetMaxFaultEntries setting. PM87461
4 Missing source level information for a COBOL event. Although a compiler listing was provided, it was not being used to determine the source level information for the event due to incorrect signature determination. The signature determination problem has been fixed. PM91070
5 XMIT (X) line command not working from Fault Entry List display Processing of the 'X' line command had been disabled inadvertently. Processing of the 'X' line command has been re-enabled. PM89702
6 When opening the properties window for a Fault Entry, the duplicates tab becomes too large to fit on the user's screen when there are a large number of duplicates. The duplicate properties tab increases the size of the window to fit all of the duplicates. This can be problematic when there is a very large number of duplicates for a Fault Entry as the window can not be resized. The properties window has been made resizable and now contains scollbars, so that the user can adjust the size of the window as needed. PM91068
7 Abend S0C4 in ProcHistDA following message IDI0005S during implicit generation of saved report for 'V' or 'S' line command issued against a DeferredReport fault entry. Incorrect attempt to contunue processing following an out-of-space condition. IDIPDDIR will now terminate following a condition resulting in message IDI0005S being issued. PM89900
8 Report does not show any user code before abend. It appears that an abend after a call to IGZCLNK, and before the next DSA is created, will cause an old DSA to be overlayed. The user code event is no longer in the DSA chain. The broken DSA event is now included if it is a call to IGZCLNK. PM91071
9 DFHAP0701 An abend (code 0C4/AKEA) has occurred in exit program IDIXCX53 at exit point XPCABND. Fault Analyzer running with CICS and OPEN TCB's might get abend S0C4 indicated from IDIXCX53. Key 9 OPEN TCB exit processing has been updated. PM91251
10 Message 'ERROR: SYSDEBUG process must run against a single member of this PDS(E)' issued during interactive re-analysis. Processing incorrectly failed to add an IDITRACE record. IDITRACE record added to prevent the error message. PM90641
APAR PM83917 Fixes and Enhancements
Problem
Description
Fix
Complete APAR information
1 Records are missing from the CICS Auxiliary Trace display. These records are mainly missing at the beginning and end of the trace. The file descriptor (pointer) used to read the contents of the trace was being incremented by the initial while() loop condition. This caused the record to appear invalid as it was missing key information. It also caused records at the end to be skipped to avoid buffer overrun. The pointer to the file content was set to one less than the current position, so that it always begins at zero/the start. The code for skipping the end records was also removed. PM83725
2 Abend S0C4 in PrtHdg() when reporting assembler CSECT storage. Bad return code incorrectly processed as register causing storage overlay. Only valid base registers are now processed. PM83447
3 Attempting to sort a column in the Recovery Manager Link Summary page causes an abend in FA. The Recovery Manager adds line breaks between records of a different type, to group similar entries. This conflicts with the table sorting as it artificially increases the number of rows the table believes it needs to sort. The perceived last row is beyond the table range. The code that was adding line breaks between records has been removed, as it no longer appears after table sorting. This code appears to have been a holdover from before the table sorting logic was added. PM83748
4 Table headings in the CICS Bridge Domain are missing their first letter. Table heading labels are sometimes included in heading highlighting. The width of the columns was one character short for the last column. This was causing columns to not align as intended and for characters to be hidden in the display. The heading group labels were included after the beginning of some tables, causing them to appear in the table. The table column heading widths were adjusted to match the required values and the heading group labels were moved above the table to avoid being included in the formatting. PM83748
5 Storage Manager EDSA Limit and Total vales are incorrectly converted from Bytes to Megabytes. The EDSA Limit/Total values are presented in Megabytes, by dividing the number of bytes by 1024 * 1000. This should actually be divided by 1024 * 1024 to get the correct value. The value used in the division has been modified to accurately perform the conversion. PM87125
6 User is running CICS transaction under EDF. The transaction abends. EDF shows FA EXEC CICS commands. Also, resolve AZTS abends in FA. Some EXEC CICS commands in the FA Exits are translated with the EDF option. Also, CICS is abending some FA tasks with AZTS. FA's exit commands have been changed to set the NOEDF bit. FA has been changed to prevent AZTS abends from occuring during FA processing. PM84239
7 Parameters on call to IDISNAP from PL/I program are not being used. PL/I usage of a pointer to a pointer reference was not being correctly catered for. Pointer to pointer references corrected. PM87065
8 FA CICS Transaction Abend exit suffers AZTS abend during EXEC CICS RECEIVE BUFFER due to problems with MRO connection. FA issues RECEIVE BUFFER to an MRO terminal, but for some reason the TOR fails to complete the RECEIVE and issues Abend AZTS, causing further problems for the failing task. FA has been changed to tell CICS not to abend the task AZTS. Instead, CICS returns TERMERR to FA, which is handled. PM87457
9 Fault Analyzer errors, such as IDI0095W Unexpected condition found in IDICUSUB:2347: IDICUSUB:2253, when a corrupt fault entry is copied to a history file. If a fault entry is copied in ASCII rather than binary, and placed into a history file using ISPF, then processing errors will occur trying to read the member. Protection code has been added. PM87458
10 In the PD Tools FA plugin, the user is receiving an error message about their options data set not being found. The username displayed does not match their own. The username is being retrieved based upon the user account UID value. This value is not necessarily unique in some customer environments, leading to a mismatch in username values. The username is now retrieved based upon the current MVS user account. This should always be unique and accurate. PM87074
11 Abend U2100 in load module IDIXDCAP. Insufficient storage to perform required module initialization. A check for available storage has been added, and if insufficient, message IDI0007S is issued. PM87459
12 CICS System Dump Analysis fails with IDI0005S. Dump contains a large number of 'inactive' COBOL programs, which are being discovered unnecessarily. Procedures now not called when processing CICS System Dump. PM87460
13 FA loops or issues IDI0005S when processing a large CICS SVC dump that has storage overlays. Bad RB contains an invalid CDE pointer. CDE pointer in RB now checked before use. PM87463
14 Fault Analyzer calling EQAUEDAT exit compiled with COBOL SSRANGE might get IGZ0073S length zero then U4038 IDI0115E and IDI0120S messages. If the first operand to EQAUEDAT compiled with COBOL SSRANGE has zero length, then IGZ0073S is issued from COBOL causing Fault Analyzer IDI0115E LE enclave abend U4038 message, followed by IDI0120S IBM Fault Analyzer internal abend U4038. If the first parm for EQAUEDAT is null, then it will be changed to the string "NULLFILE", so that COBOL SSRANGE is not triggered if the exit is compiled with COBOL. PM87464
15 IDI0011S no storage for IDIDA start or IDI0005S when application has //CEEUOPT ALL31(OFF). Use of LE //CEEUOPT DD with ALL31(OFF) when an abend calling Fault Analyzer occurs might get IDI0011S or IDI0005S messages trying to run Fault Analyzer below the line. The LE option has been overridden for the ATTACH of the IDIDA TCB. PM87465
16 User has difficulty installing and using the Fault Analyzer web interface due to the required directory permissions in the USS environment. In some host setups, the necessary directory permissions (775) were not available after extracting the web interface code into USS. This prevented the HTTP server from being able to display pages in some cases. The sample installation job will now automatically set directory permissions to allow the HTTP server to access the web interface files. PM87064
17 The user enters the CFA transaction in CICS. CFA reports that the LE Exit is inactive, even though it is active. CFA is failing to find IDIXCCEE in CEECCICS due to an offset error. Hence, CFA is reporting that the exit is inactive. This problem occurs in CICS TS 5.1 only. CFA has been changed to locate IDIXCCEE in CEECCICS correctly when running under CICS TS 5.1. PM87466
18 Message IDI0105S when empty history file is displayed with IDIPDDIR. Changes related to recent interactive reanalysis storage constraint relief improvements caused an error allocating zero bytes of storage when no fault entries exist in the history file. The storage allocation error has been corrected. PM86443
19 Fault Analyzer showing abend PSW in the Debug Tool Exec Area when an abend on an instruction in the Exec Area occurs. Abends occuring on instructions being executed in the D/T Exec Area when using overlay hooks, should be logically relocated to the corresponding application code instruction. Code has been added to do the relocation. PM87478
20 Abend S0C4 at entry point pHexDumpAsc. During formatting of hex-dumped storage areas in the analysis report, the current storage area being processed was FREEMAINed outside of Fault Analyzer's control. The formatting of hex-dumped storage areas in the analysis report has been ESTAE protected to allow recovery in case of abends during real-time processing. PM87467
21 Fault Analyzer IDIUTIL RC=4, then RC=0 when the job is rerun. Doing an IDIUTIL run from a low activity system might first give return code 4, but on rerun be OK with RC=0. Logic changed to ensure subsystem cache is refreshed. PM87468
22 NoDup(Normal(...)) processing is not recognizing duplicate fault if point-of-failure CSECT or program offset is zero. A zero offset was being interpreted as a missing value. A zero offset is now being processed as a valid value if the point-of-failure CSECT or program name has been determined. PM87469
23 MSG IDI0095W logic error if a DSN supplied via EQAUEDAT is not found. If an EQAUEDAT exit supplies an alternative data set name for a side file, but that data set or member does not exist, then an IDI0095W message will be issued. The IDI0095W situation is converted to a "data set not found" condition in the IDITRACE output. PM87189
24 In the plug-in and web interface, opening an empty history file would return an error message saying that the requested history file was 'not a history file'. The server incorrectly assumed that an empty result from the history file $$INDEX cache lookup meant that it did not exist. The cache lookup logic was modified to differentiate between a non-existant history file and one that is simply empty. Opening/refreshing an empty history file will now display an empty fault entry list. PM87303
25 When issuing the 'V' or 'S' line command against a fault entry without a saved report, one is generated but a different or no saved report is finally shown. Following the release of storage during implicit interactive reanalysis, and the subsequent rebuilding of this data, information pertaining to the current fault entry had been overwritten with that of another fault entry. Information about the current fault entry, following implicit interactive reanalysis, has now been restored correctly. PM87423
26 Once a Dump Registration Analysis Control user exit has set CTL.EXCLUDE to Y, then this becomes the new default. The variable containing the CTL.EXCLUDE setting was initialized only once and did not cater for situations where options processing was invoked repeatedly under the same TCB. The variable containing the CTL.EXCLUDE setting is now initialized correctly each time options processing is invoked. PM87576
APAR PM78349 Fixes and Enhancements
Problem
Description
Fix
Complete APAR information
1 CICS log reports message DFHAP1212 for program IDIXCCEE. Fault Analyzer's sample CICS program definitions do not match what CICS thinks is inside the program. IDISCICS sample member has been changed to remove the LANGUAGE() keywords from FA programs. This stops CICS from reporting a mismatch. PM82060
2 MSG IDI0005S IDIDODSN:2646 Storage allocation failed. Fault Analyzer analysis "file" menu option 5 of an SVC DUMP. During analysis of an SVC or SYSMDUMP containing COBOL, the process might run out of storage with message IDI0005S. The storage managemant for Base Locator logic has been changed to reduce the storage required for analysis. PM77622
3 The CICS Domain Manager screen displays an incorrect Phase value. Values of -F900 are shown instead of -0700, for example. The Phase value was being incorrectly interpreted, leading to incorrect negative values. The Phase value is now correctly interpreted. PM81864
4 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. FA is obtaining the Transaction Id from a place which does not always have the ID. FA has been changed to obtain the Transaction Id from a more reliable location. PM80461
5 Abend code blank in report generated by IDIUTIL LISTHF with LISTHF user exit. ENV.ABEND_CODE was not initialized correctly for an EXEC CICS DUMP fault. ENV.ABEND_CODE is now initialized correctly for an EXEC CICS DUMP fault. PM82061
6 IDI0115E LE enclave abend S002 and IDI0120S IBM Fault Analyzer internal abend S002 U0000. A record exceeding the maximum history file LRECL of 10000 bytes was attempted written to the fault entry. The data written is now split into multiple records if necessary. PM79983
7 SYSIDIDA.SYSOUT GRS resource contention due to a large number of abending TCBs attempting to invoke Fault Analyzer simultaneously. 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. 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. PM80077
8 Fault Analyzer runs out of memory when processing a large inactive COBOL program's working-storage. Re-allocation of BLW storage as base locators are processed requires an unnecessary large amount of duplicated memory. Working-storage is now allocated as a single area. PM80858
9 User cannot find descriptions for Side File option data sets in Fault Analyzer Eclipse Plug-in. Fault Analyzer Eclipse Plug-in is missing documentation for the Side File option data sets used in the Fault Entry refresh process. Documentation has been added to describe what each Side File option data set is. These descriptions have been added to help documentation page named "Browsing reports" under the "Tasks" section of the Eclipse Help Contents. PM81981
10 In the eclipse plug-in, refreshing a fault report will not have any effect. The user cannot view source by providing side files and refreshing, they get an old report. The Fault Analyzer Eclipse plug-in is displaying a cached version of a fault entry report after a refresh, causing the user to always receive the original version of the report. There is an issue with a request being unsupported on the host, causing issues during the report download. The fault report caching problem has been resolved and the possibly unsupported requests are now handled gracefully. The user should now always receive the new report after refreshing a fault entry. PM81980
11 CICS file owning region might get storage overlay SM0102 with Fault Analyzer running. A CICS region with many open files might get storage overlay with IBM Fault Analyzer active. The code has been corrected. PM82062
12 Message IDI0047S abend S0C4 and CICS region abend S40D reason code X'18'. The Fault Analyzer IDIDA TCB was attached with the wrong program protection key. The Fault Analyzer IDIDA TCB is now attached with the correct program protection key. PM82063
13 Message IDI0047S abend S0C4 at entry point CompMsgs. A message was issued prior to required initialization having been performed. A check has been added for the required initialization. PM81915
14 Loop during analysis in dfhs_afcb. The end of the EXCI trace blocks was not being correctly identified and hence caused a loop. The end of the EXCI trace blocks is now correctly detected. PM81847
15 Various CICS abends during the capture of the 3270 buffer. 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. 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. PM81759
16 User could not perform analysis on a large CICS system dump that included overlayed storage, displaying an internal S0C4 abend when loading. The large CICS system dump included storage that had been overlayed, causing Fault Analyzer to read invalid values when calculating the memory position of Kernel Stack entry data. Instead of reading the correct table length and label offset values, it found "4040" in hex instead. A boundary check has been added to terminate kernel stack entry processing, if the memory reference falls outside the bounds of allocated storage. PM82756
17 Abend in DFHSUEX when a CICS task is purged during FA analysis. 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. Purge protection has been placed around the invocation exit execution. PM82554
18 Batch reanalysis JCL error when original abending job included JOBLIB DD statement. The JOBLIB DD statement was placed incorrectly in the generated JCL. Any JOBLIB data sets in the original fault are now included in the generated batch reanalysis JCL as STEPLIB data sets. PM82496
19 Recycle of CICS required to pick up new copy of FA CICS invocation exit program IDIXCMnn. 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. The NEWCOPY process provided in the CFA transaction has been extended to also refresh the IDIXCMnn module. PM79946
20 In the General Purpose Registers display under the Fault Analyzer Eclipse plug-in, the source/statement line number is truncated. The buffer used to store the line number text was being terminated one character too early. When terminating the line number buffer, the position at which a null terminator is added has been increased by one. PM83908
APAR PM74985 Fixes and Enhancements
Problem
Description
Fix
Complete APAR information
1 User selects CICS SDUMP for analysis. Fault Analyzer abends in pp_ke_stack. pp_ke_stack is processing a stack entry for DFHPISN. DFHPISN is so big that its offsets appear as negative when held in a C short variable. pp_ke_stack has been changed to use an UNSIGNED short variable. PM77672
2 Dump Storage display not formatted using 32 bytes per line when it should be. Despite the setting of an adequate preferred formatting width, and the use of a logical screen size which also permits storage formatting using 32 bytes per line, the Dump Storage display was formatted using only 16 bytes per line. The determination of sufficient width to allow for 32 bytes per line formatting has been corrected. PM77673
3 CICS Transaction Dump statistics might be wrong if Fault Analyzer is active in the CICS region. Even with the Fault Analyzer RetainCICSdump(ALL) option, the CEMT I TRD statistics might be affected by Fault Analyzer. The Fault Analyzer CICS suppress dump return code processing has been updated. PM77674
4 IDI0144E error IDISFPEX abend S0C4 in Fault analyzer IDIS subsystem. The IDIS subsystem might get IDI0144E from IDISFPEX abend S0C4 when the Fault Analyzer options have a long EXCLUDE option. Saving of the OPTION statement has been updated to accomodate any input length. PM77675
5 RDz dead process=721405 exited in exit code=137/9/160 or other errors after Fault Analyzer called for abend processing. In a UNIX DUBBED environment Fault Analyzer being called to handle an abend might cause LE envar_array pointed to from the EDB to be corrupted. The use of putenv() has been removed and replaced with an MVS name/token solution. PM77676
6 User enters CFA transaction and then uses PF9 to view the IVP screen. PROG753 is issued at the terminal intermittently. The CFA program IDIXFA is not initializing the IVP map as often as it should. IDIXFA has been changed to initialize the map before sending it. PM77677
7 Abend S0C4 at entry point PrtUDATA when passing back records with more than 256 characters from a Message and Abend Code Explanation user exit using 'IDIWRITE '. The long records were saved in XPL.DATA_BUFFER, which is only a 256 character field, causing overlays and corruption of data. Other symptoms than the S0C4 in PrtUDATA might be possible, depending on the record data and length. A separate dynamically allocated buffer is now being used, which is capable of handling record lengths up to 32K. PM77678
8 Abend S0C4 in translate() when processing C/C++ DWARF. Subprograms and lexical blocks might have high_pc = 0 which is problematic when creating scoping blocks. Subprograms and lexical blocks with high_pc = 0 are now ignored (they are of no value). PM75980
9 CICS gets DFHSM0002 X'0D0A' when customized DFHPEP issues TC SEND command. Fault Analyzer is "stacking" TCTTEDA, and CICS is freemaining it while it is stacked. Fault Analyzer will no longer stack TCTTEDA. PM77679
10 CICS SDUMP Kernel Stack display has incorrect lines for "int" subroutine calls. CICS TS 4.1 increased the size of the R14 store from 4 bytes to 8 bytes. FA's display needs to be updated to use 8-byte fields. FA has been changed to use 8-byte fields when processing SDUMPs for CICS 4.1 and above. PM77093
11 CICS U4038 abends on an L9 open TCB are not captured by Fault Analyzer No fault entry created for LE U4038 abends that occur on an open TCB running in key 9. Code updated to handle the key 9 processing. PM77680
12 With bad JCL in the IDIS subsystem causing an abend, and automated operations restarting it, the system LX entries can be depleted causing the need to IPL. The Fault Analyzer IDIS subsystem if continually restarted can cause depletion of the SYSTEM LX pool, requireing an IPL. The LX for IDIS is now reconnected so that restarts do not cause additional system LX values to be used. PM77681
13 AB/S00C4 004 IDIXDCAP IDIXDCAP IEAVTABD REGS/0B2FC FFFFF TTL: ABDUMP ERROR, COMPON=ABDUMP, COMPID=5752-SCDMP, ISSUER=IEAVTABD SVC dump taken from IEAVTABD when Fault Analyzer installed and a KEY 7 TCB abends. Processing for abends not in KEY 8 or 9 has been updated to generate IDI0123S Unsupported Environment message. PM77003
14 CICS SDUMP analysis AP domain task facility type and ID blank in some instances. A facility ID was only being determined when the facility type flag was 02. In this instance, the type flag was 01 but a facility ID was still available. Code enhanced to specifically check for a valid facility ID, even if the facility type is 01. PM77640
15 Abend SA78 in load module IDIXDCAP CSECT IDIXOPTC + X'C46'. An invalid address was used to FREEMAIN a work area. The correct address is now being used to FREEMAIN the work area. PM77682
16 SCRT not finding Fault Analyzer SMF89 records. Fault Analyzer SMF89 records might have invalid product data, stopping them being recognized by SCRT. Blank-padding has been added to the identity strings. PM77683
APAR PM70210 Fixes and Enhancements
Problem
Description
Fix
Complete APAR information
1 Connections column in MRO Conversations panel display cannot be sorted. The column definition was incorrect. The column definition has been corrected. PM72796
2 IDIUTIL LISTHF report shows blank abend code for CICS dump code fault entries. Support for CICS dump codes was missing. Support for CICS dump codes has been added. PM72797
3 IDILANGX fails to process a PL/I struct if its name is used for a struct member elsewhere. (Problem only occurs when the member name is declared first). IDILANGX fails to create a symbol for the struct. IDILANGX now creates a new symbol for the struct. PM72798
4 Fault Analyzer Recovery Fault Recording process might fail with IDI0011S message. The RFR dump process might get a secondary 0C4 abend in IDIXALG offset X'5B2' with R9 address invalid. R9 setup is corrected. PM72792
5 IDI0092S Time 2 minutes for analysis exceeded. A loop occurred during scanning of storage for an eyecatcher due to an incorrect address parameter. The incorrect address parameter has been corrected. PM72799
6 EUDSA PAM display incorrect. The incorrect page size was being used when building the PAM display. Code has been added to dynamically check which page size to use. PM72800
7 Message IDI0115E and IDI0120S due to abend S002 in Fault Analyzer. Possibly also message IEC036 002-18. A fault entry EX segment length exceeded the history file LRECL of 10000 bytes. EX segments exceeding 10000 bytes have been split into multiple shorter segments. PM72801
8 Abend S0C9 at entry point displayISPF statement 3782 offset X'1CE1A' during MVS dump analysis. A value had not been initialized. The required value has now been initialized. PM72802
9 ABEND0C4-4 in DUBBEDER at offset X'D4' when Fault Analyzer called for an abend in a TCB not running in key 8. If a TCB not running in key 8 abends, and Fault analyzer is called, a secondary 0C4 can occur in DUBBEDER causing an SVC dump with title TITLE=ABDUMP ERROR,COMPON=ABDUMP, COMPID=5752-SCDMP,ISSUER=IEAVTABD. The DUBBEDER code has been changed for TCBs not running in storage protect key 8. PM72786
10 Fault Analyzer problem report notes a recovered LE event as the point of failure. When an LE condition occurs, and is recovered from, then Fault Analyzer might incorrectly report the event that was recovered as the point of failure. The logic has been changed. PM73772
11 IDI0034I Fault analysis skipped due to: Abend S0C4 and SVC dump with title COMPON=JES3 ALLOCATION, COMPID=SC1BA, ISSUER=IATSIAI-RELENQ Following invocation for a S1FB abend, an abend S0C4 occurred in load module IATSIAI offset X'182' during dynamic allocation for a C run-time fopen() call. The cause of the problem being that Fault Analyzer was invoked during unconditional logoff processing for a TSO user. Fault Analyzer will no longer attempt to analyze abends which occur in the job scheduler IEESB605 TCB but will instead issue message IDI0123S. PM74209
12 An IDILANGX data set, which was specified through options when a fault entry was created, is not being found during subsequent fault entry reanalysis. The automatic inclusion of data sets specified during real-time processing, for use by fault entry reanalysis, only included the first data set for any side file or compiler listing DDname. All data sets specified during real-time execution are automatically included with any other data sets from current options when performing reanalysis of a fault entry. PM74212
13 Abend S0C4 in FindSymAddr when processing Enterprise PL/I parameter variables. Parameter storage accessibility not checked. Parameter storage accessibility now checked. PM74214
APAR PM67619 Fixes and Enhancements
Problem
Description
Fix
Complete APAR information
1 Fault Analyzer reporting U4038 as the point of failure when a later abend (S0C7 or other) was the real cause. An earlier exception, such as IGZ0014W from IGZEOPT that is recovered, might be incorrectly reported as the point of failure. Tests for earlier abends updated. PM68991
2 Storage not accessible when reporting COBOL storage using SYSDEBUG side file and OPT(FULL) compiler option. OPT(FULL) removes unreferenced data items but they are still found in the SYSDEBUG attribute table, and when processed attempt to consume unavailable storage. Unreferenced data items in the SYSDEBUG attribute table are now ignored. PM68993
3 The user is viewing CICS TS 4.2 SM domain panels and is seeing subpools displayed in the wrong DSA. CICS TS 4.2 changed an array, but the FA panel script was not updated, so it is getting subpool information from the wrong place. FA script panels for the SM domain have been updated to use the new format array whan processing 4.2 SDUMPS. PM68994
4 The user is viewing CICS SDUMP panels, looking at TCP MRO information and is seeing things such as session names in the wrong place. The Fault Analyzer panel is incorrectly sorting the information that it is displaying, leading to data being shown in the wrong place. The panel sort mechanism has been fixed. PM68995
5 Abend S0C4 in IDIXDCAP+2FF6 DUBBEDER+2F8 with reg 9 at a bad address. Intermittent abend S0C4 in IDIXDCAP after Fault Analyzer has been called to capture an abend. The ESTAEX regester restore for R9 has been corrected. PM68989
6 Message IDAI1001E.PUT FAILED, ERROR FOUND WHILE UPDATING THE INDEX issued by the IDIS subsystem shortly after start-up. An automatic update of the Fault Analyzer IDIVSENU VSAM message and abend code explanation repository, during start-up of the IDIS subsystem, caused the KSDS index to become corrupted due to using POINT with only a partial key prior to using PUT when inserting records. The full key is now being used with POINT prior to PUT. PM68996
7 The user is looking at a CICS 4.2 transaction abend analysis and finds that the CICS trace does not contain the entries which lead up to the abend. The Fault Analyzer code which captures CICS 4.2 trace entries is calculating the start/size/end of the trace capture incorrectly. Fault Analyzer has been changed to calculate the start/size/end of the captured trace entries correctly, as happened with previous CICS versions. PM69468
8 A user who is analyzing a CICS SDUMP sees FA abend 0C4 in PP_LG_STREAM_SUMM. FA is analyzing a CICS SDUMP which has severely corrupted LG Domain control blocks. The analysis code abends because it doesn't handle the corrupted control block chains. IDIECLG PP_LG_STREAM_SUMM has been changed to terminate analysis of the LG control block chain if it is corrupted. PM69469
APAR PM64218 Fixes and Enhancements
Problem
Description
Fix
Complete APAR information
1 IDI0095W Unexpected condition found in IDIDODSN:1004: Process error. A CDE data area size was incorrectly set to 40 bytes. The CDE data area size has been changed to 32 bytes. PM65401
2 Excessive time taken to analyze COBOL abend when many base locators are processed. DSA address not passed to COBOL side file functions causes slow running entry point detection. DSA address now passed to COBOL side file functions. PM65402
3 Unable to change fault entry prefix using the Fault Analyzer ISPF interface File->Change Fault History File Settings action-bar pull-down option. Although the display accepts the change, the history file is not being updated. The history file is now being updated. PM64341
4 CICS SDUMP panel displays Kernel Error registers incorrectly if they are flagged as containing 64-bit values. Fault Analyzer does not check the flag which indicates that registers contain 64-bit values, and therefore formats them as if they contained 32-bit values. Fault Analyzer has been changed to use 64-bit formatting when the 64-bit flag is set. PM65403
5 CICS SDUMP panel displays PPTE CONCURRENY values incorrectly in CICS 4.2 dumps. CICS 4.2 added a new CONCURRENCY option. Fault Analyzer was not updated to show that new option value. Fault Analyzer has been changed to present the correct CONCURENCY value - QUASIRENT/THREADSAFE/ REQUIRED. PM65404
6 Abend S0C4 in IEAVENLU+50 when Fault Analyzer IDICSVCR is FREEMAINed at TCB DETACH. An S0C4 abend can occur if the Fault Analyzer router SVC is FREEMAINed when the TCB that loads it is DETACHed. The CDE use count error is corrected. PM65405
7 KE_NUM column all 0000 in KE error display with a CICS/TS 4.2 dump. The required data is now referenced by a 64-bit pointer and this was not being correctly allowed for. The 64-bit pointer is now correctly allowed for. PM65406
8 Abend S0C4 at offset x'5E8' in Fault Analyzer IDIXASUB with GPR 3 bad. Intermittent S0C4 in Fault Analyzer IDIXASUB module IDIXDCAP or IDIXCEE. There might also be an SVC dump with title: ABDUMP ERROR, COMPON=ABDUMP, COMPID=5752-SCDMP, ISSUER=IEAVTABD. Fixed incorrect offset in TCT addressing. PM66966
9 IDI0078E Open of fault history file failed, write access is denied. IDI0095W Unexpected condition found in IDICUSUB:2872: no member set IDI0095W IDICUSUB:2872 no member set message might occur when creating a Fault Analyzer fault entry in an XFACILIT-protected history file from an SVC dump. User ID and Group field input when working from an SVC dump has been corrected. PM67216

All available Version 11 Fault Analyzer PTFs and associated APARs (most recent first):

English Base Component
Japanese Feature
Korean Feature
PTF Download links
UI17320 Download PTF UI17320
UI14783 Download PTF UI14783
UI13511 Download PTF UI13511
UI12508 Download PTF UI12508
UK98099 Download PTF UK98099
UK97277 Download PTF UK97277
UK96932 Download PTF UK96932
UK95249 Download PTF UK95249
UK93741 Download PTF UK93741
UK91900 Download PTF UK91900
UK83847 Download PTF UK83847
UK82503 Download PTF UK82503
UK80578 Download PTF UK80578
UK79450 Download PTF UK79450
UK78540 Download PTF UK78540
UK76660 Download PTF UK76660
UK76888 Download PTF UK76888
UK76889 Download PTF UK76889
UK74578 Download PTF UK74578
UK71656 Download PTF UK71656
UK70024 Download PTF UK70024
UK68814 Download PTF UK68814
UK65276 Download PTF UK65276
UK63632 Download PTF UK63632
UK62719 Download PTF UK62719
UK62204 Download PTF UK62204

PTF
Availability date
Prerequisite PTFs
Supercedes these PTFs
APAR(s) this PTF fixes
English:
UI17320
2 May 2014 UI14783 PI11057
PI16213
PI16215
PI16218
PI16323
PI16324
PI16325
PI16326
PI16327
PI16328
PI16329
English:
UI14783
7 Feb 2014 UI12508
UI13511
UK62204
UK62719
UK65276
UK68814
UK70024
UK71656
UK74578
UK76660
UK78540
UK79450
UK80578
UK82503
UK83847
UK91900
UK93741
UK95249
UK96932
UK97277
UK98099
PI08458
PI10675
PI10676
PI10677
PI10678
PI10679
PI10680
PI10681
PI10682
PI10683
PI10684
PI10700
English:
UI13511
2 Jan 2014 UI12508
UK62204
UK62719
UK65276
UK68814
UK70024
UK71656
UK74578
UK76660
UK78540
UK79450
UK80578
UK82503
UK83847
UK91900
UK93741
UK95249
UK96932
UK97277
UK98099
PI06355
PI06368
PI07155
PI07594
PI07732
PI07761
PI07762
PI07763
PI07764
PI07765
PI07766
PI07767
PI07858
English:
UI12508
19 Nov 2013 UK62204
UK62719
UK65276
UK68814
UK70024
UK71656
UK74578
UK76660
UK78540
UK79450
UK80578
UK82503
UK83847
UK91900
UK93741
UK95249
UK96932
UK97277
UK98099
PI05473
PI05474
PI05475
PI05476
PI05477
PI05568
PM98461
English:
UK98099
3 Oct 2013 UK62204
UK62719
UK65276
UK68814
UK70024
UK71656
UK74578
UK76660
UK78540
UK79450
UK80578
UK82503
UK83847
UK91900
UK93741
UK95249
UK96932
UK97277
PM95415
PM96377
PM96424
PM97481
PM97969
PM97970
PM97971
PM97972
PM97973
PM97974
English:
UK97277
6 Sep 2013 UK93741
UK95249
UK96932 PM95843
PM96151
PM96152
English:
UK96932
30 Aug 2013 UK93741
UK95249
PM91256
PM91556
PM92285
PM95036
PM95083
PM95328
PM95329
PM95330
PM95331
PM95332
PM95333
English:
UK95249
23 Jun 2013 UK93741 PM87966
PM88085
PM89680
PM91065
PM91066
PM91072
PM91073
PM91252
English:
UK93741
24 Apr 2013 UK62204
UK62719
UK65276
UK68814
UK70024
UK71656
UK74578
UK76660
UK78540
UK79450
UK80578
UK82503
UK83847
UK91900
PM81618
PM83188
PM83918
PM85245
PM85417
PM85488
PM86093
PM86827
PM87011
PM87066
PM87075
PM87113
PM87115
PM87145
PM87146
PM87471
PM87472
PM87473
PM87474
PM87476
PM87477
PM87479
PM87480
PM87527
English:
UK91900
4 Mar 2013 UK62204
UK62719
UK65276
UK68814
UK70024
UK71656
UK74578
UK76660
UK78540
UK79450
UK80578
UK82503
UK83847
PM78350
PM80346
PM80521
PM80560
PM80829
PM80860
PM81064
PM81680
PM81982
PM82064
PM82065
PM82066
PM82067
PM82068
PM82069
PM82070
PM82071
PM82864
PM83211
English:
UK83847
2 Jan 2013 UK62204
UK62719
UK65276
UK68814
UK70024
UK71656
UK74578
UK76660
UK78540
UK79450
UK80578
UK82503
PM74986
PM75028
PM75368
PM75675
PM76163
PM76168
PM76169
PM76229
PM76777
PM76823
PM76928
PM77563
PM77671
PM77684
PM77685
PM77686
English:
UK82503
1 Nov 2012 UK62204
UK62719
UK65276
UK68814
UK70024
UK71656
UK74578
UK76660
UK78540
UK79450
UK80578
PM68795
PM69665
PM70211
PM70382
PM70634
PM71543
PM72087
PM72088
PM72653
PM72787
PM72791
PM72794
PM72795
PM72807
PM73774
PM73984
PM74207
English:
UK80578
4 Sep 2012 UK62204
UK62719
UK65276
UK68814
UK70024
UK71656
UK74578
UK76660
UK78540
UK79450
PM65723
PM65777
PM66372
PM67620
PM68808
PM68869
PM68870
PM68997
PM69465
PM69466
English:
UK79450
2 Jul 2012 UK62204
UK62719
UK65276
UK68814
UK70024
UK71656
UK74578
UK76660
UK78540
PM63291
PM64048
PM64219
PM64413
PM64788
PM65220
PM65354
PM66967
PM67217
English:
UK78540
3 Jun 2012 UK71656
UK74578
UK76660
PM59882
PM60755
PM60788
PM62263
PM63989
PM63991
PM63994
PM63995
English:
UK76660
3 Apr 2012 UK71656
UK74578
PM54422
PM55077
PM56533
PM57926
PM59058
PM59060
PM59061
PM59062
Japanese:
UK76888
3 Apr 2012 PM54422
Korean:
UK76889
3 Apr 2012 PM54422
English:
UK74578
1 Jan 2012 UK71656 PM47309
PM47919
PM49599
PM50154
PM50349
PM51689
PM51892
PM52232
PM52562
PM52564
PM53162
PM53167
PM53168
PM53169
PM53170
PM53171
PM53172
PM53229
PM53508
PM53603
English:
UK71656
3 Oct 2011 UK62204
UK62719
UK65276
UK68814
UK70024
PM44693
PM45362
PM45449
PM46049
PM46050
PM47171
English:
UK70024
1 Aug 2011 UK62204
UK62719
UK65276
UK68814
PM42267
PM43677
PM44247
PM44248
PM44249
PM44250
PM44251
English:
UK68814
5 Jul 2011 UK62204
UK62719
UK65276
PM32189
PM34295
PM35223
PM35891
PM37324
PM37944
PM38906
PM38931
PM40247
PM41007
PM41008
PM41009
PM41010
PM41011
PM41012
PM41013
PM41014
PM41015
PM41886
English:
UK65276
4 Apr 2011 UK62204
UK62719
PM28208
PM33404
PM33405
PM33406
PM33407
PM33408
PM33409
PM33410
PM33411
PM33591
Japanese:
UK63632
1 Feb 2011 PM29741
English:
UK62719
3 Jan 2011 UK62204 PM27281
PM28246
English:
UK62204
1 Dec 2010 PM26282
PM26303
PM26306
PM26307
PM26905
PM26906
PM26994
PM26995
APAR PI11057 Fixes and Enhancements
Problem
Description
Fix
Complete APAR information
1 Incorrect Compiler Listing display pseudo assembler instructions default setting. The product default, when the user has not yet selected either "Add Pseudo Assembler Instructions" or "Remove Pseudo Assembler Instructions" from the action-bar View pull-down menu, is to show the pseudo assembler instructions. This is incorrect according to the documentation. The product default has been changed to not include the pseudo assembler instructions in the Compiler Listing display. PI16323
2 Abend S0C4 in IDIXDCAP with messages IDI0012S and IDI0013S. A zero value while looping through a set of data was not being correctly allowed for. A zero value is now correctly handled. PI16324
3 Fault Analyzer loop when trying to display Java event. If a Java source file can not be successfully opened, then the code might loop. The code has been corrected to prevent the loop. PI16325
4 CICS formatted trace entries are missing location information following the colon, as in "Called-from-address <address> : <location>". 64-bit addresses were not handled correctly. 64-bit addresses are now being handled correctly. PI16326
5 Too many allocations of the Fault Analyzer history file. A frequently used system service is causing dynamic allocation. The system service is now called using pre-allocation. PI16213
6 Console flooded with IDI0088E messages. Storage abend during ESTAE recovery while invoking the Binder program. The ESTAE is now cancelled before activity requiring virtual storage occurs. PI16215
7 Fault Analyzer IMS BMP user ID wrong. The user ID reported by Fault Analyzer for a BMP might be the program name instead of the user ID. The code has been corrected to ensure the input IOPCB user ID is only used for IMS message processing regions. PI16327
8 IDILANGX ends with CEE0802C at entry point LSMMFREE. Max locates records causes write buffer overrun. Max locates records reduced to fit write buffer. PI16218
9 IMS MPP terminating but does not end. The MPP termination was held up by Fault Analyzer processing that had stalled. Monitor task added to ensure the IDIDA TCB attaches and runs successfully. PI16328
10 Message IDI0131W Waiting for history-file($$INDEX) SPFEDIT ENQ when ENQ is held by a TSO user. Abend in a TSO screen running Fault Analyzer might leave the $$INDEX ENQ outstanding until the TSO session is logged off. Code added to help DEQ processing in the case of Fault Analyzer abending in TSO/ISPF. PI16329
APAR PI08458 Fixes and Enhancements
Problem
Description
Fix
Complete APAR information
1 When processing CICS Trace entries to determine source line #, the mismatch pop-up is presented, even though the COBOL SYSDEBUG file matches. DEBUGINF is not in the minidump. DEBUGINF added to minidump during COBOL CLLE discovery. PI10675
2 Cursor scrolling not working correctly on the CICS Internal Trace display, Saved Report display and Compiler Listing display. The saved cursor position was being retrieved from an incorrect variable. The saved cursor position is now retrieved from the correct variable. PI10676
3 Error message "Not a history file" when specifying a migrated data set name on the Fault Entry List display. The check for expected history file attributes failed when the data set was migrated. An additional check for a migrated data set has been added, prior to the attribute check. PI10677
4 IMS region shutdown held up by Fault Analyzer abend processing when initial abend TCB is holding LE MSGFILE ENQ. The IMS region would not shut down or cancel because the Fault Analyzer IDIDA analysis task was in an ENQ deadlock with the abending TCB, which had abended in LE code while holding the LE MSGFILE ENQ. Code has been added to break the deadlock. PI10678
5 Fault Analyzer IDIS subsystem might get recursive IDI0144E and IDI0124E messages. If the XCF message chain pointer is overlayed, the IDIS subsystem might get recursive abends with messages IDI0144E and IDI0124E. The logic has been updated to resolve the chaining error. PI10679
6 Blank saved report displayed with 'V' or 'S' line command if history file specified using single quotes in a View member. The single quotes were not expected and caused fopen of the fault entry member to fail without an error message being issued. An error message will be issued if failing to open the fault entry member and specification of single quotes around View member history file names has been supported. PI10680
7 Fault Analyzer report for IMS Java might show an additional incorrect LE U4038 abend in the event summary. IMS with Java and CEEPIPI might cause Fault Analyzer to add a historical CIB event incorrectly in the report. The condition has been catered for in the code. PI10681
8 Fault Analyzer might produce more than one RFR dump for one abend when short on storage. Recursion of S878 conditions during Recovery Fault Recording (RFR) processing can cause more than one SDUMP to be taken for the one initial abend. Code has been added to stop additional SDUMPs against one fault entry. PI10682
9 More than one fault entry might be created if the IDIS subsystem is experiencing Cross-System Coupling Facility (XCF) message delays. With XCF message delays in the IDIS subsystem, the recovery process might cause more than one fault entry to be created for the same abend job and timestamp. Code added to stop assignment of a new fault ID if one already exists for the same job and timestamp. PI10683
10 Message IDI0095 IDICABND:1415 CSVQUERY error. Some Fault Analyzer analysis jobs might get IDI0095W unexpected condition, CSVQUERY error. Code added to accommodate provider field request getting rc=4. PI10684
11 Message IDI0092S Time 32 minutes for analysis exceeded. Loop in code at entry point cDDfCloseP. The code has been fixed to prevent the loop from occurring. PI10700
APAR PI06355 Fixes and Enhancements
Problem
Description
Fix
Complete APAR information
1 Abend S23E after successful Fault Analyzer analysis of a CICS transaction abend. For LE transactions running on a L9 TCB, control was being returned to the Fault Analyzer invocation exit on the L9 TCB. A DETACH call could potentially be issued, which is not valid from the L9 TCB. The DETACH is now only attempted when running on the QR TCB. PI07732
2 MATCH CSR not working if help text is enabled, the display has been scrolled to hide the help text, and the cursor is placed in a field near the bottom of the display. The check for the cursor position within the ISPF dynamic area failed to correctly cater for the hidden help text. The problem has been corrected. PI07155
3 Fault Analyzer IDIS subsystem IDI0095W ENQ ECB status error and IDI0131WENQ delay lockout on history file. When XCF message delays occur, the IDIS subsystem recovery might get an ENQ status error that causes recurring IDI0131W messages until the IDIS subsystem is restarted. ENQ processing changed to accommodate the timing issues. PI07761
4 Extraneous subscript when formatting multi-dimension COBOL tables. Dimension not decremented correctly. Dimension decremented corrected. PI06368
5 Storage overlay in fileLANGX() while processing scope records. Scope slot index is out of bounds. Scope slot index corrected. PI07762
6 Fault Analyzer gets a S0C4 abend at entry point pp_tctse_main when analyzing a dump. A storage overlay in the customer environment caused control blocks to contain invalid values. A text string was missing the terminating character, causing Faukt Analyzer to get a S0C4. The code was modified to limit the length of the string processed. PI07763
7 Abend S0C4 from entry point ProcHistDA statement 6965 offset X'81BA' when pressing Enter after selecting an empty history file for display. The determination of display characteristics to be used for the re-display did not correctly handle the situation where the history file contains zero fault entries. The problem has been corrected. PI07764
8 Incorrect Fault Entry List display scroll down action under CICS, when help text is enabled and the top-most fault entry is displayed. The ZSCROLLA value returned by VGET in this environment was not blank-padded as expected. The ZSCROLLA value is now processed correctly, regardless of blank-padding after VGET. PI07155
9 Symbol substitution not working in the alternative parmlib data set name specified via the IDIOPTLM configuration-options module field CNFDSN. The symbol substitution service output buffer length was set too short. The buffer length has been set to the correct value. PI07765
10 The user ID of an IMS abend is not displayed in the history file, like it is for CICS. The user ID displayed is the one from the job's ACEE. If a user ID is found in an IMS IOPCB, then it will be shown instead of the job's ACEE user ID. PI07594
11 Message "ICH409I 282-020 ABEND DURING RACHECK PROCESSING" during analysis of Java dump. A valid history file data set name had not been set from the Fault Entry List display prior to the dump analysis, resulting in a blank history file data set name being checked for access authorization. A check has been added for the existence of a non-blank history file data set name prior to the RACHECK call. PI07766
12 Fault Analyzer empty report, no events from RFR dump after IDI0055S out of storage message. The RFR SDUMP after an out of storage IDI0055S message might not get a TCB selected for analysis. The code has bee updated to determine the TCB issuing the RFR call. PI07767
13 Fault Analyzer might generate more than one fault entry for the same event. The additional fault entries have no minidump or report content. More than one fault entry for the same job and timestamp if delays in XCF coupling facility messages cause retransmit of a fault ID assignment. The code has been updated to cater for the potential re-transmission of an assignment request via XCF. PI07858
APAR PM98461 Fixes and Enhancements
Problem
Description
Fix
Complete APAR information
1 Fault Analyzer RFR dump event list might be missing events. The DSA chaining back through linkage stack entries might fail when an invalid backchain address in encountered. The code has been updated. PI05473
2 New History File Allocation dialog not shown when copying fault entry to non-existing history file. A check for the existence of the target history file was missing. A check has been added for the existence of the target history file. PI05474
3 A Fault Analyzer user is analyzing a CICS SDUMP, and sees errors in the DS Domain panels. DS panels have incomplete information due to an arbitrary limit to the number of internal control blocks that can be created. Also, there is a problem in sorting some column contents. The number of internal control blocks which can be created has been increased. The panel column sort code has been fixed. PI05475
4 User is analyzing a CICS TS 3.1 SDUMP and gets an 0C4 abend in function pp_ke_stack. pp_ke_stack is processing a stack entry for CICS program DFHLEPTQ, which has an invalid (negative) iproc offset. This causes pp_ke_stack to abend. pp_ke_stack has been modified to handle the bad offset. PI05476
5 User gets DFHSR0622 because of abend 0C4 in CEECGEX. User has issued PURGE of CICS task. FA's IDIXCCEE issues EXEC CICS commands in CICSkey and enters WAIT_MVS. User issues KILL for task. CICS drives LE CEECGEX in USERkey with CICSkey DSA/RSA from IDIXCCEE. IDIXCCEE has been changed to percolate (defer) AEXY abends to FA CICS GLUEs, which do not issue EXEC CICS commands in a way that can cause the problem. PI05477
6 Fault Analyzer IDIS subsystem IDI0131W messsages ENQ lockout on history files. APAR PM97968 fixed the 100% CPU loop reported but the IDI0131W messages can still occur. This APAR addresses the IDI0131W ENQ message not clearing. Code added to correctly retest the ENQ status. PI05568
APAR PM96424 Fixes and Enhancements
Problem
Description
Fix
Complete APAR information
1 Debug Tool analysis of HLASM might fail to display some field data. The use of USING (Dsect,DsectEnd),R10 form rather than traditional USING Dsect,R10 will cause a problem with EQALANGX respecify record data. The code has been updated to correct the problem. PM97969
2 Fault Analyzer report has 'no data' in the event list. If the MVS RB chain can not be traced because of a missing page in the minidump, the available list of events was not displayed. Code updated to better handle the next RB not being available. PM95415
3 The user is analyzing a CICS SDUMP and is seeing an incorrect task state in the DS Domain Task Summary panel. Task State is shown as "R" when it should be "A". FA CICS SDUMP analysis is interpreting a CICS status byte incorrectly. IDIECDS has been changed to interpret the task status byte correctly. PM97970
4 Cursor is placed on the Fault Entry List display command line after deletion of fault entry if option to confirm deletion is in effect. The original cursor position is not saved prior to displaying the delete confirmation panel. The cursor is now positioned correctly. PM97971
5 Fault entry duplicate count on the Fault Entry List display shows a negative or decreasing value. The duplicate count is held in a signed halfword which is displayed as a negative value if more than 32,767 duplicates have occurred, or a decreasing value if more than 65,535 duplicates have occurred. The duplicate count field is treated as unsigned, which allows for up to 65,535 duplicates. Once this limit is reached, the count will remain unchanged at its maximum instead of wrapping. PM96377
6 Abend S282-20 when exiting interactive MVS dump analysis. The Fault Analyzer ISPF interface was invoked with a history file name set to a non-existing data set. A check has been added for the existence of the target history file to prevent the abend S282-20 from occurring. PM97972
7 IDI0047S from Fault Analyzer in MAPLMOD processing. Intermittent abend S0C4 in Fault Analyzer IDIDA MAPLMOD causing IDI0047S and an RFR dump to be created for recovery processing of the fault entry. The MAPLMOD processing updated to correctly test the return from GETDSVOL processing. PM97973
8 Fault Analyzer IDIS subsystem loop with IDI0131W message and high CPU. Under some XCF recovery conditions, the IDIS subsystem might loop causing high CPU usage. Code changed to handle the potential XCF recovery timing condition. PM97481
9 Message "ERROR: IactLEabend() can't be invoked from IDIPDDIR!" issued when looking up abend code explanation from Fault Entry List display. This is a diagnostic message that was incorrectly left as a message to the user rather than being written to a trace data set. The message is no longer displayed to the user and is only written to the trace data set. PM97974
APAR PM95843 Fixes and Enhancements
Problem
Description
Fix
Complete APAR information
1 Unable to Uninstall or Install CICS exits using CFA transaction for CICS/TS 4.2 and 5.1. The EXIT program name was being incorrectly set for CICS/TS 4.2 and 5.1. The EXIT program name is now correctly set for CICS/TS 4.2 and 5.1. PM96151
2 Abend S0C4 in IDIXCM68 when CICSY LIBRARY in use. Incorrect addressing of a 64-bit control block. Addressing of the 64-bit control block has been corrected. PM96152
APAR PM91556 Fixes and Enhancements
Problem
Description
Fix
Complete APAR information
1 IBM Fault Analyzer IDI0095W Unexpected condition IDIDODSN:360 when exiting interactive analysis of an MVS dump. When completing an interactive reanalysis of an MVS SVC or SYSMDUMP, the write minidump process might issue IDI0095W from IDIDODSN:360. The logic has been changed to handle the allocation condition. PM91256
2 IDI0095W Unexpected condition found in IDISUPDI:1426: IDISUPDI:1851 :1426 dup time precedes fault entry. IBM Fault Analyzer CICS fast duplicate processing might record a vendor altered start time rather than the wall-clock time, even when the UseIDISTime option is set. Code updated to accommodate date/time alteration test products in the CICS fast duplicate recording process. PM95083
3 Listing exit issues IDISF messages when exit returns a SYSDEBUG dsn. Listing exit fails to process a SYSDEBUG, then attempts to process it as a compiler listing. Listing exit now correctly processes SYSDEBUG files. PM92285
4 After scrolling Fault Entry List display right, abend code explanation is shown instead of processing line command. When a point-and-shoot field, such as the "Abend" column field, is scrolled to logically overlap with the line command field, then the point-and-shoot field is incorrectly processed instead of the line command. An error determining the line offset in displays with a non-scrollable section on the left has been fixed. PM95328
5 COBOL ODO table has incorrect stride. ODO recalibration includes redefinitions which causes data item length to be added again. Only the original definition is inlcuded in recalibration of ODO tables. PM95329
6 Language Environment heap analysis errors not indicated in the Synopsis section of the report. The specific Language Environment heap analysis errors found in this case had not been made eligible for identification in the report Synopsis. All Language Environment heap analysis errors are now being identified in the Synopsis with a reference to detailed information about the errors in the Language Environment heap analysis section of the report. PM95330
7 Changes in CICS parm TRTRANSZ for CICS/TS 4.2 and 5.1 does not increase number of trace entries gathered by Fault Analyzer. The value of TRTRANSZ was being incorrectly determined and hence a default value of 64K was always being used by Fault Analyzer. The correct value of TRTRANSZ is now determined and used accordingly. PM95036
8 Fault Analyzer's CICS SDUMP "SM ECDSA Subpool Summary" panel displays some incorrect or unclear values, Some values are being obtained from the wrong place. Some values are correct but are displayed in hex, while the CICS VerbExit displays them in decimal. Fault Analyzer has been changed to display the correct values, and to display both hex and decimal values where appropriate. PM95331
9 Lock flag incorrectly reset after fault entry interactive reanalysis when Enter is pressed on exit to save changes to user data. The fault entry lock flag was being managed, both in the fault entry member, and in the history file cache, causing incorrect updates. The fault entry lock flag is now only being managed in the history file cache. PM95332
10 Loop during abend analysis leading to IDI0005S message. FA code was not allowing for an LE CIB next pointer to be pointing to itself. Hence, FA went into a loop which eventually exhaused all storage and gave a IDI0005S message. Loop detection code added. PM95333
APAR PM88085 Fixes and Enhancements
Problem
Description
Fix
Complete APAR information
1 When filtering history file columns in the plug-in, the filters would only match the (always uppercase values) if typed in uppercase. The plug-in column filtering is case sensitive, meaning that all filter values must be typed in uppercase to match column fields. The column filter value is now case-insensitive. Typing the filter in upper or lowercase will now match the column field values. PM91066
2 Analysis Control user exit ENV.IMS_PROGRAM_NAME blank when Fault Analyzer is invoked for an IMS user abend. The code which obtains the IMS program name was not executed due to NoDup(ImageFast(...)) processing being bypassed. The IMS program name is now obtained regardless of whether NoDup(ImageFast(...)) processing is bypassed or not. PM91072
3 The Language Environment STORAGE option was not being reported correctly. LE added a new value to the LE STORAGE option in z/OS V1R13. Updated our processing to handle all the new LE options and values added in z/OS V1R13. PM87966
4 IDIUTIL IMPORT function abend SE37 on target history file. IDIUTIL IMPORT does not honor SetMaxFaultEntries setting. IDIUTIL IMPORT now honors SetMaxFaultEntries setting. PM85028
5 Missing source level information for a COBOL event. Although a compiler listing was provided, it was not being used to determine the source level information for the event due to incorrect signature determination. The signature determination problem has been fixed. PM89680
6 Abend S0C4 in ProcHistDA following message IDI0005S during implicit generation of saved report for 'V' or 'S' line command issued against a DeferredReport fault entry. Incorrect attempt to contunue processing following an out-of-space condition. IDIPDDIR will now terminate following a condition resulting in message IDI0005S being issued. PM91073
7 Report does not show any user code before abend. It appears that an abend after a call to IGZCLNK, and before the next DSA is created, will cause an old DSA to be overlayed. The user code event is no longer in the DSA chain. The broken DSA event is now included if it is a call to IGZCLNK. PM91065
8 DFHAP0701 An abend (code 0C4/AKEA) has occurred in exit program IDIXCX53 at exit point XPCABND. Fault Analyzer running with CICS and OPEN TCB's might get abend S0C4 indicated from IDIXCX53. Key 9 OPEN TCB exit processing has been updated. PM91252
APAR PM83918 Fixes and Enhancements
Problem
Description
Fix
Complete APAR information
1 Records are missing from the CICS Auxiliary Trace display. These records are mainly missing at the beginning and end of the trace. The file descriptor (pointer) used to read the contents of the trace was being incremented by the initial while() loop condition. This caused the record to appear invalid as it was missing key information. It also caused records at the end to be skipped to avoid buffer overrun. The pointer to the file content was set to one less than the current position, so that it always begins at zero/the start. The code for skipping the end records was also removed. PM87471
2 Attempting to sort a column in the Recovery Manager Link Summary page causes an abend in FA. The Recovery Manager adds line breaks between records of a different type, to group similar entries. This conflicts with the table sorting as it artificially increases the number of rows the table believes it needs to sort. The perceived last row is beyond the table range. The code that was adding line breaks between records has been removed, as it no longer appears after table sorting. This code appears to have been a holdover from before the table sorting logic was added. PM87066
3 Table headings in the CICS Bridge Domain are missing their first letter. Table heading labels are sometimes included in heading highlighting. The width of the columns was one character short for the last column. This was causing columns to not align as intended and for characters to be hidden in the display. The heading group labels were included after the beginning of some tables, causing them to appear in the table. The table column heading widths were adjusted to match the required values and the heading group labels were moved above the table to avoid being included in the formatting. PM87066
4 Storage Manager EDSA Limit and Total vales are incorrectly converted from Bytes to Megabytes. The EDSA Limit/Total values are presented in Megabytes, by dividing the number of bytes by 1024 * 1000. This should actually be divided by 1024 * 1024 to get the correct value. The value used in the division has been modified to accurately perform the conversion. PM87472
5 User is running CICS transaction under EDF. The transaction abends. EDF shows FA EXEC CICS commands. Also, resolve AZTS abends in FA. Some EXEC CICS commands in the FA Exits are translated with the EDF option. Also, CICS is abending some FA tasks with AZTS. FA's exit commands have been changed to set the NOEDF bit. FA has been changed to prevent AZTS abends from occuring during FA processing. PM87473
6 Parameters on call to IDISNAP from PL/I program are not being used. PL/I usage of a pointer to a pointer reference was not being correctly catered for. Pointer to pointer references corrected. PM87474
7 FA CICS Transaction Abend exit suffers AZTS abend during EXEC CICS RECEIVE BUFFER due to problems with MRO connection. FA issues RECEIVE BUFFER to an MRO terminal, but for some reason the TOR fails to complete the RECEIVE and issues Abend AZTS, causing further problems for the failing task. FA has been changed to tell CICS not to abend the task AZTS. Instead, CICS returns TERMERR to FA, which is handled. PM83188
8 Fault Analyzer errors, such as IDI0095W Unexpected condition found in IDICUSUB:2347: IDICUSUB:2253, when a corrupt fault entry is copied to a history file. If a fault entry is copied in ASCII rather than binary, and placed into a history file using ISPF, then processing errors will occur trying to read the member. Protection code has been added. PM87146
9 Abend S0C4 in PrtHdg() when reporting assembler CSECT storage. Bad return code incorrectly processed as register causing storage overlay. Only valid base registers are now processed. PM87476
10 Abend S0C4 in ADD_XREF_ELEM when IDILANGX processes a COBOL compiler listing that has more than 64K references to a data item. IDILANGX XREF record cannot accommodate more than 64K references. A new IDILANGX XREF type 2 record has been introduced to accommodate more than 64K references to a data item. PM81618
11 Abend U2100 in load module IDIXDCAP. Insufficient storage to perform required module initialization. A check for available storage has been added, and if insufficient, message IDI0007S is issued. PM85245
12 CICS System Dump Analysis fails with IDI0005S. Dump contains a large number of 'inactive' COBOL programs, which are being discovered unnecessarily. Procedures now not called when processing CICS System Dump. PM85417
13 FA loops or issues IDI0005S when processing a large CICS SVC dump that has storage overlays. Bad RB contains an invalid CDE pointer. CDE pointer in RB now checked before use. PM85488
14 Fault Analyzer calling EQAUEDAT exit compiled with COBOL SSRANGE might get IGZ0073S length zero then U4038 IDI0115E and IDI0120S messages. If the first operand to EQAUEDAT compiled with COBOL SSRANGE has zero length, then IGZ0073S is issued from COBOL causing Fault Analyzer IDI0115E LE enclave abend U4038 message, followed by IDI0120S IBM Fault Analyzer internal abend U4038. If the first parm for EQAUEDAT is null, then it will be changed to the string "NULLFILE", so that COBOL SSRANGE is not triggered if the exit is compiled with COBOL. PM87145
15 IDI0011S no storage for IDIDA start or IDI0005S when application has //CEEUOPT ALL31(OFF). Use of LE //CEEUOPT DD with ALL31(OFF) when an abend calling Fault Analyzer occurs might get IDI0011S or IDI0005S messages trying to run Fault Analyzer below the line. The LE option has been overridden for the ATTACH of the IDIDA TCB. PM87113
16 The user enters the CFA transaction in CICS. CFA reports that the LE Exit is inactive, even though it is active. CFA is failing to find IDIXCCEE in CEECCICS due to an offset error. Hence, CFA is reporting that the exit is inactive. This problem occurs in CICS TS 5.1 only. CFA has been changed to locate IDIXCCEE in CEECCICS correctly when running under CICS TS 5.1. PM86093
17 Message IDI0105S when empty history file is displayed with IDIPDDIR. Changes related to recent interactive reanalysis storage constraint relief improvements caused an error allocating zero bytes of storage when no fault entries exist in the history file. The storage allocation error has been corrected. PM87477
18 Fault Analyzer showing abend PSW in the Debug Tool Exec Area when an abend on an instruction in the Exec Area occurs. Abends occuring on instructions being executed in the D/T Exec Area when using overlay hooks, should be logically relocated to the corresponding application code instruction. Code has been added to do the relocation. PM87115
19 Abend S0C4 at entry point pHexDumpAsc. During formatting of hex-dumped storage areas in the analysis report, the current storage area being processed was FREEMAINed outside of Fault Analyzer's control. The formatting of hex-dumped storage areas in the analysis report has been ESTAE protected to allow recovery in case of abends during real-time processing. PM86827
20 Fault Analyzer IDIUTIL RC=4, then RC=0 when the job is rerun. Doing an IDIUTIL run from a low activity system might first give return code 4, but on rerun be OK with RC=0. Logic changed to ensure subsystem cache is refreshed. PM87075
21 NoDup(Normal(...)) processing is not recognizing duplicate fault if point-of-failure CSECT or program offset is zero. A zero offset was being interpreted as a missing value. A zero offset is now being processed as a valid value if the point-of-failure CSECT or program name has been determined. PM87011
22 Message EDC6006E raise() issued for SIGABORT from entry point CMALLOC when IDILANGP is used against a SYSDEBUG file for a large program. IDILANGP issues a raise() condition when there is insufficient storage available in the TSO region to perform the required processing. IDILANGP now issues message IDI0005S if there is insufficient storage available in the TSO region to perform the required processing. PM87479
23 When issuing the 'V' or 'S' line command against a fault entry without a saved report, one is generated but a different or no saved report is finally shown. Following the release of storage during implicit interactive reanalysis, and the subsequent rebuilding of this data, information pertaining to the current fault entry had been overwritten with that of another fault entry. Information about the current fault entry, following implicit interactive reanalysis, has now been restored correctly. PM87480
24 Once a Dump Registration Analysis Control user exit has set CTL.EXCLUDE to Y, then this becomes the new default. The variable containing the CTL.EXCLUDE setting was initialized only once and did not cater for situations where options processing was invoked repeatedly under the same TCB. The variable containing the CTL.EXCLUDE setting is now initialized correctly each time options processing is invoked. PM87527
APAR PM78350 Fixes and Enhancements
Problem
Description
Fix
Complete APAR information
1 CICS log reports message DFHAP1212 for program IDIXCCEE. Fault Analyzer's sample CICS program definitions do not match what CICS thinks is inside the program. IDISCICS sample member has been changed to remove the LANGUAGE() keywords from FA programs. This stops CICS from reporting a mismatch. PM80560
2 MSG IDI0005S IDIDODSN:2646 Storage allocation failed. Fault Analyzer analysis "file" menu option 5 of an SVC DUMP. During analysis of an SVC or SYSMDUMP containing COBOL, the process might run out of storage with message IDI0005S. The storage managemant for Base Locator logic has been changed to reduce the storage required for analysis. PM82064
3 The CICS Domain Manager screen displays an incorrect Phase value. Values of -F900 are shown instead of -0700, for example. The Phase value was being incorrectly interpreted, leading to incorrect negative values. The Phase value is now correctly interpreted. PM82065
4 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. FA is obtaining the Transaction Id from a place which does not always have the ID. FA has been changed to obtain the Transaction Id from a more reliable location. PM82066
5 Abend code blank in report generated by IDIUTIL LISTHF with LISTHF user exit. ENV.ABEND_CODE was not initialized correctly for an EXEC CICS DUMP fault. ENV.ABEND_CODE is now initialized correctly for an EXEC CICS DUMP fault. PM80346
6 IDI0115E LE enclave abend S002 and IDI0120S IBM Fault Analyzer internal abend S002 U0000. A record exceeding the maximum history file LRECL of 10000 bytes was attempted written to the fault entry. The data written is now split into multiple records if necessary. PM80521
7 SYSIDIDA.SYSOUT GRS resource contention due to a large number of abending TCBs attempting to invoke Fault Analyzer simultaneously. 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. 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. PM82067
8 Fault Analyzer runs out of memory when processing a large inactive COBOL program's working-storage. Re-allocation of BLW storage as base locators are processed requires an unnecessary large amount of duplicated memory. Working-storage is now allocated as a single area. PM82068
9 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. D/T monitor function might show wrong information for some registers when debugging HLASM programs because EQALANGX data is wrong. The code for setting the label flag has been updated. PM81982
10 CICS file owning region might get storage overlay SM0102 with Fault Analyzer running. A CICS region with many open files might get storage overlay with IBM Fault Analyzer active. The code has been corrected. PM80829
11 Message IDI0047S abend S0C4 and CICS region abend S40D reason code X'18'. The Fault Analyzer IDIDA TCB was attached with the wrong program protection key. The Fault Analyzer IDIDA TCB is now attached with the correct program protection key. PM80860
12 Message IDI0047S abend S0C4 at entry point CompMsgs. A message was issued prior to required initialization having been performed. A check has been added for the required initialization. PM82069
13 Loop during analysis in dfhs_afcb. The end of the EXCI trace blocks was not being correctly identified and hence caused a loop. The end of the EXCI trace blocks is now correctly detected. PM82070
14 IDILANGX RC=1051 when processing PL/I compiler listing with many external variables. IDILANGX has a maximum of 1024 CSECTs. Number of CSECT slots increased to 2048. PM81680
15 Various CICS abends during the capture of the 3270 buffer. 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. 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. PM82071
16 Abend in DFHSUEX when a CICS task is purged during FA analysis. 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. Purge protection has been placed around the invocation exit execution. PM82864
17 Recycle of CICS required to pick up new copy of FA CICS invocation exit program IDIXCMnn. 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. The NEWCOPY process provided in the CFA transaction has been extended to also refresh the IDIXCMnn module. PM83211
18 In the General Purpose Registers display under the Fault Analyzer Eclipse plug-in, the source/statement line number is truncated. The buffer used to store the line number text was being terminated one character too early. When terminating the line number buffer, the position at which a null terminator is added has been increased by one. PM81064
APAR PM74986 Fixes and Enhancements
Problem
Description
Fix
Complete APAR information
1 User selects CICS SDUMP for analysis. Fault Analyzer abends in pp_ke_stack. pp_ke_stack is processing a stack entry for DFHPISN. DFHPISN is so big that its offsets appear as negative when held in a C short variable. pp_ke_stack has been changed to use an UNSIGNED short variable. PM76169
2 Dump Storage display not formatted using 32 bytes per line when it should be. Despite the setting of an adequate preferred formatting width, and the use of a logical screen size which also permits storage formatting using 32 bytes per line, the Dump Storage display was formatted using only 16 bytes per line. The determination of sufficient width to allow for 32 bytes per line formatting has been corrected. PM75368
3 CICS Transaction Dump statistics might be wrong if Fault Analyzer is active in the CICS region. Even with the Fault Analyzer RetainCICSdump(ALL) option, the CEMT I TRD statistics might be affected by Fault Analyzer. The Fault Analyzer CICS suppress dump return code processing has been updated. PM75028
4 IDI0144E error IDISFPEX abend S0C4 in Fault analyzer IDIS subsystem. The IDIS subsystem might get IDI0144E from IDISFPEX abend S0C4 when the Fault Analyzer options have a long EXCLUDE option. Saving of the OPTION statement has been updated to accomodate any input length. PM75675
5 User enters CFA transaction and then uses PF9 to view the IVP screen. PROG753 is issued at the terminal intermittently. The CFA program IDIXFA is not initializing the IVP map as often as it should. IDIXFA has been changed to initialize the map before sending it. PM76163
6 Abend S0C4 at entry point PrtUDATA when passing back records with more than 256 characters from a Message and Abend Code Explanation user exit using 'IDIWRITE '. The long records were saved in XPL.DATA_BUFFER, which is only a 256 character field, causing overlays and corruption of data. Other symptoms than the S0C4 in PrtUDATA might be possible, depending on the record data and length. A separate dynamically allocated buffer is now being used, which is capable of handling record lengths up to 32K. PM76229
7 CICS gets DFHSM0002 X'0D0A' when customized DFHPEP issues TC SEND command. Fault Analyzer is "stacking" TCTTEDA, and CICS is freemaining it while it is stacked. Fault Analyzer will no longer stack TCTTEDA. PM76168
8 CICS SDUMP Kernel Stack display has incorrect lines for "int" subroutine calls. CICS TS 4.1 increased the size of the R14 store from 4 bytes to 8 bytes. FA's display needs to be updated to use 8-byte fields. FA has been changed to use 8-byte fields when processing SDUMPs for CICS 4.1 and above. PM77684
9 RDz dead process=721405 exited in exit code=137/9/160 or other errors after Fault Analyzer called for abend processing. In a UNIX DUBBED environment Fault Analyzer being called to handle an abend might cause LE envar_array pointed to from the EDB to be corrupted. The use of putenv() has been removed and replaced with an MVS name/token solution. PM76777
10 CICS U4038 abends on an L9 open TCB are not captured by Fault Analyzer No fault entry created for LE U4038 abends that occur on an open TCB running in key 9. Code updated to handle the key 9 processing. PM76823
11 With bad JCL in the IDIS subsystem causing an abend, and automated operations restarting it, the system LX entries can be depleted causing the need to IPL. The Fault Analyzer IDIS subsystem if continually restarted can cause depletion of the SYSTEM LX pool, requireing an IPL. The LX for IDIS is now reconnected so that restarts do not cause additional system LX values to be used. PM76928
12 AB/S00C4 004 IDIXDCAP IDIXDCAP IEAVTABD REGS/0B2FC FFFFF TTL: ABDUMP ERROR, COMPON=ABDUMP, COMPID=5752-SCDMP, ISSUER=IEAVTABD SVC dump taken from IEAVTABD when Fault Analyzer installed and a KEY 7 TCB abends. Processing for abends not in KEY 8 or 9 has been updated to generate IDI0123S Unsupported Environment message. PM77685
13 CICS SDUMP analysis AP domain task facility type and ID blank in some instances. A facility ID was only being determined when the facility type flag was 02. In this instance, the type flag was 01 but a facility ID was still available. Code enhanced to specifically check for a valid facility ID, even if the facility type is 01. PM77686
14 Abend SA78 in load module IDIXDCAP CSECT IDIXOPTC + X'C46'. An invalid address was used to FREEMAIN a work area. The correct address is now being used to FREEMAIN the work area. PM77563
15 SCRT not finding Fault Analyzer SMF89 records. Fault Analyzer SMF89 records might have invalid product data, stopping them being recognized by SCRT. Blank-padding has been added to the identity strings. PM77671
APAR PM70211 Fixes and Enhancements
Problem
Description
Fix
Complete APAR information
1 Connections column in MRO Conversations panel display cannot be sorted. The column definition was incorrect. The column definition has been corrected. PM72791
2 IDIUTIL LISTHF report shows blank abend code for CICS dump code fault entries. Support for CICS dump codes was missing. Support for CICS dump codes has been added. PM70382
3 IDILANGX fails to process a PL/I struct if its name is used for a struct member elsewhere. (Problem only occurs when the member name is declared first). IDILANGX fails to create a symbol for the struct. IDILANGX now creates a new symbol for the struct. PM68795
4 IDILANGX does not recognize 'Object-Ref' types in data division map section. 'Object-Ref' not recognized. 'Object-Ref' now recognized and resolved to pointer type. PM72795
5 Fault Analyzer Recovery Fault Recording process might fail with IDI0011S message. The RFR dump process might get a secondary 0C4 abend in IDIXALG offset X'5B2' with R9 address invalid. R9 setup is corrected. PM72807
6 IDI0092S Time 2 minutes for analysis exceeded. A loop occurred during scanning of storage for an eyecatcher due to an incorrect address parameter. The incorrect address parameter has been corrected. PM70634
7 EUDSA PAM display incorrect. The incorrect page size was being used when building the PAM display. Code has been added to dynamically check which page size to use. PM72794
8 Message IDI0115E and IDI0120S due to abend S002 in Fault Analyzer. Possibly also message IEC036 002-18. A fault entry EX segment length exceeded the history file LRECL of 10000 bytes. EX segments exceeding 10000 bytes have been split into multiple shorter segments. PM71543
9 Abend S0C9 at entry point displayISPF statement 3782 offset X'1CE1A' during MVS dump analysis. A value had not been initialized. The required value has now been initialized. PM72653
10 ABEND0C4-4 in DUBBEDER at offset X'D4' when Fault Analyzer called for an abend in a TCB not running in key 8. If a TCB not running in key 8 abends, and Fault analyzer is called, a secondary 0C4 can occur in DUBBEDER causing an SVC dump with title TITLE=ABDUMP ERROR,COMPON=ABDUMP, COMPID=5752-SCDMP,ISSUER=IEAVTABD. The DUBBEDER code has been changed for TCBs not running in storage protect key 8. PM72787
11 IDILANGX ends with rc=310 when processing VS COBOL II Rel 2.0 compile listing. IDILANGX does not support VS COBOL II Rel 2.0. Support for VS COBOL II Rel 2.0 added. PM72088
12 IDILANGX 0C4 in LINE_TO_STMT() when processing OS VS/COBOL compiler listing. Line_Acc_Info overlayed following multiple valid_info entries. Only one valid_info entry should be collected (working- storage length). Extraneous adds of valid_info removed. PM72087
13 IDILANGX of HLASM SYSADATA gets RC=0310. IDISF8231S Missing ENTRY ESD information. IDISF8233S Unable to determine identity of unnamed PC section. RC=0310 when the assembly uses an unnamed CSECT or START statement. The code has been changed to deal with the unnamed section. PM69665
14 Fault Analyzer problem report notes a recovered LE event as the point of failure. When an LE condition occurs, and is recovered from, then Fault Analyzer might incorrectly report the event that was recovered as the point of failure. The logic has been changed. PM73774
15 IDI0034I Fault analysis skipped due to: Abend S0C4 and SVC dump with title COMPON=JES3 ALLOCATION, COMPID=SC1BA, ISSUER=IATSIAI-RELENQ Following invocation for a S1FB abend, an abend S0C4 occurred in load module IATSIAI offset X'182' during dynamic allocation for a C run-time fopen() call. The cause of the problem being that Fault Analyzer was invoked during unconditional logoff processing for a TSO user. Fault Analyzer will no longer attempt to analyze abends which occur in the job scheduler IEESB605 TCB but will instead issue message IDI0123S. PM74207
16 Abend S0C4 in FindSymAddr when processing Enterprise PL/I parameter variables. Parameter storage accessibility not checked. Parameter storage accessibility now checked. PM73984
APAR PM67620 Fixes and Enhancements
Problem
Description
Fix
Complete APAR information
1 Fault Analyzer reporting U4038 as the point of failure when a later abend (S0C7 or other) was the real cause. An earlier exception, such as IGZ0014W from IGZEOPT that is recovered, might be incorrectly reported as the point of failure. Tests for earlier abends updated. PM65723
2 Storage not accessible when reporting COBOL storage using SYSDEBUG side file and OPT(FULL) compiler option. OPT(FULL) removes unreferenced data items but they are still found in the SYSDEBUG attribute table, and when processed attempt to consume unavailable storage. Unreferenced data items in the SYSDEBUG attribute table are now ignored. PM66372
3 IDILANGX issues message IDISF8158T when processing Enterprise COBOL compiler listing. Source line grid margin character '!' instead of expected '|'. IDILANGX accepts '!' as grid right margin character. PM65777
4 The user is viewing CICS TS 4.2 SM domain panels and is seeing subpools displayed in the wrong DSA. CICS TS 4.2 changed an array, but the FA panel script was not updated, so it is getting subpool information from the wrong place. FA script panels for the SM domain have been updated to use the new format array whan processing 4.2 SDUMPS. PM68869
5 The user is viewing CICS SDUMP panels, looking at TCP MRO information and is seeing things such as session names in the wrong place. The Fault Analyzer panel is sorting the information that it is displaying incorrectly, leading to data being displayed in the wrong place. The panel sort mechanism has been fixed. PM68870
6 Abend S0C4 in IDIXDCAP+2FF6 DUBBEDER+2F8 with reg 9 at a bad address. Intermittent abend S0C4 in IDIXDCAP after Fault Analyzer has been called to capture an abend. The ESTAEX regester restore for R9 has been corrected. PM68997
7 Message IDAI1001E.PUT FAILED, ERROR FOUND WHILE UPDATING THE INDEX issued by the IDIS subsystem shortly after start-up. An automatic update of the Fault Analyzer IDIVSENU VSAM message and abend code explanation repository, during start-up of the IDIS subsystem, caused the KSDS index to become corrupted due to using POINT with only a partial key prior to using PUT when inserting records. The full key is now being used with POINT prior to PUT. PM68808
8 The user is looking at a CICS 4.2 transaction abend analysis and finds that the CICS trace does not contain the entries which lead up to the abend. The Fault Analyzer code which captures CICS 4.2 trace entries is calculating the start/size/end of the trace capture incorrectly. Fault Analyzer has been changed to calculate the start/size/end of the captured trace entries correctly, as happened with previous CICS versions. PM69465
9 A user who is analyzing a CICS SDUMP sees FA abend 0C4 in PP_LG_STREAM_SUMM. FA is analyzing a CICS SDUMP which has severely corrupted LG Domain control blocks. The analysis code abends because it doesn't handle the corrupted control block chains. IDIECLG PP_LG_STREAM_SUMM has been changed to terminate analysis of the LG control block chain if it is corrupted. PM69466
10 Message IDI0095W Unexpected condition found in IDICUSUB:3174 HIST DEQ Error. Fault Analyzer IDIS subsystem or IDIUTIL might get IDI0095W IDICUSUB:3174 Hist DEQ error when processing History files. The DEQ check condition has been corrected.
APAR PM64219 Fixes and Enhancements
Problem
Description
Fix
Complete APAR information
1 IDI0095W Unexpected condition found in IDIDODSN:1004: Process error. A CDE data area size was incorrectly set to 40 bytes. The CDE data area size has been changed to 32 bytes. PM64413
2 CICS SDUMP panel displays PPTE CONCURRENCY values incorrectly in CICS 4.2 dumps. CICS 4.2 added a new CONCURRENCY option. Fault Analyzer was not updated to show that new option value. Fault Analyzer has been changed to present the correct CONCURENCY value - QUASIRENT/THREADSAFE/ REQUIRED. PM65354
3 CICS SDUMP panel displays Kernel Error registers incorrectly if they are flagged as containing 64-bit values. Fault Analyzer does not check the flag which indicates that registers contain 64-bit values, and therefore formats them as if they contained 32-bit values. Fault Analyzer has been changed to use 64-bit formatting when the 64-bit flag is set. PM65220
4 KE_NUM column all 0000 in KE error display with a CICS/TS 4.2 dump. The required data is now referenced by a 64-bit pointer and this was not being correctly allowed for. The 64-bit pointer is now correctly allowed for. PM64048
5 Abend S0C4 in IEAVENLU+50 when Fault Analyzer IDICSVCR is FREEMAINed at TCB DETACH. An S0C4 abend can occur if the Fault Analyzer router SVC is FREEMAINed when the TCB that loads it is DETACHed. The CDE use count error is corrected. PM64788
6 Excessive time taken to analyze COBOL abend when many base locators are processed. DSA address not passed to COBOL side file functions causes slow running entry point detection. DSA address now passed to COBOL side file functions. PM63291
7 Abend S0C4 at offset x'5E8' in Fault Analyzer IDIXASUB with GPR 3 bad. Intermittent S0C4 in Fault Analyzer IDIXASUB module IDIXDCAP or IDIXCEE. There might also be an SVC dump with title: ABDUMP ERROR, COMPON=ABDUMP, COMPID=5752-SCDMP, ISSUER=IEAVTABD Fixed incorrect offset in TCT addressing. PM66967
8 IDI0078E Open of fault history file failed, write access is denied. IDI0095W Unexpected condition found in IDICUSUB:2872: no member set IDI0095W IDICUSUB:2872 no member set message might occur when creating a Fault Analyzer fault entry in an XFACILIT-protected history file from an SVC dump. User ID and Group field input when working from an SVC dump has been corrected. PM67217
APAR PM60755 Fixes and Enhancements
Problem
Description
Fix
Complete APAR information
1 Explanations not available for VS COBOL II messages. VS COBOL II message explanations missing from the Fault Analyzer message repository. VS COBOL II message explanations have been added to the Fault Analyzer message repository. PM59882
2 IDILANGX abend S0C4 in ADD_XREF_ELEM when processing Enterprise COBOL 4.1 compiler listing. 7-digit LineID used in source and data xref sections. IDILANGX now accommodates the 7-digit LineID in source and data xref sections. PM60788
3 The user receives message IDI0113W when IPV is abended due to RTIMOUT. IDIXIPV issues message IDI0113W for all errors, including this trivial problem. IDIXIPV has been changed to suppress IDI0113W in the RTIMOUT situation. PM63989
4 Abend S0C4 when using Fault Analyzer to analyze a Recovery Fault Recording (RFR) dump. The RFR conditions might set an environment where a Fault Analyzer internal buffer is exceeded, causing an overlay and abend S0C4 in Fault Analyzer. The buffer pointer position has been correctly set when the RFR input only had the invocation exit buffer. PM63994
5 CICS IVP test 4 from CFA transaction not selectable when using Rumba terminal emulator. The attribute used on the panel was acceptable by IBM PCOMMS but not with Rumba. The attribute has been changed to allow correct operation on both emulators. PM63991
6 Fault Analyzer IDI* messages might be written to a HFS file if stderr not correctly set to FD2. If a job is using HFS files but not running under a Shell (such as BPXBATCH) or OMVS, then the Unix File Descriptor 2 might not have been set to stderr and WTO messages meant for stderr might be written to an incorrect HFS file. If Unix dubbed and the LE stderr(MSGFILE) file pointer does not have FD2 assigned, then the write of IDI* messages will not be directed to FD2 stderr. PM63995
7 Fault Analyzer abend S0C4 in BldLX when processing Enterprise PL/I abend which had the GONUMBER(SEP) compiler option in effect. Incorrect fixup and processing of multiple sections in statement number table. Fixup and processing of multiple sections in statement number table corrected. PM62263
APAR PM54422 Fixes and Enhancements
Problem
Description
Fix
Complete APAR information
1 The user has specified EXCLUDE for a dumpcode. FA is excluding FA processing, but CICS goes on to take a transaction dump. The customer does not want this. Fault Analyzer is not passing the result of EXCLUDE processing to CICS. Fault Analyzer has been changed so that EXCLUDE processing will pass UERCBYP (bypass this transaction dump) if the abend code is excluded. PM59060
2 Fault Analyzer terminates with abend S0C4. Trying to access protected stortage based on an offset to a CICS response code that doesn't exist in a table. New CICS response codes added. PM55077
3 Abend 0C4 in pp_ke_stack when processing CICS SDUMP. pp_ke_stack is attempting to format LIFO entries when it should not. Logic in pp_ke_stack has been changed to prevent the abend situation from occurring. PM57926
4 Unable to display CICS transaction abend code explanation from the Fault Entry List display. The CICS transaction abend code was incorrectly being processed as a CICS dump code. The CICS transaction abend explanation can now be displayed by selecting the abend code point-and-shoot field from the Fault Entry List display. PM56533
5 Fault Analyzer ISPF interface does not check product ENABLE/DISABLE status in IFAPRDxx. The check to see if Fault Analyzer had been disabled in IFAPRDxx had only been made for real-time analysis. The ISPF interface now checks IFAPRDxx. PM59058
6 Message IDI0144E Fault Analyzer IDIS subsystem error when //CEEOPT DD with HEAPPOOLS(ON) is used. The cross memory call to the IDIS subsystem will fail with message IDI0144E if HEAPPOOLS(ON) is set. The HEAPPOOLS(OFF) option is now set in the start of IDIDA. PM59061
7 IDIMAPS data set not found during CICS start up. Configuration module IDICNFUM was not being used correctly during Fault Analyzer's CICS startup processing. IDICNFUM is now being used correctly. PM59062
APAR PM47919 Fixes and Enhancements
Problem
Description
Fix
Complete APAR information
1 "Invalid command" message received from ISPF interface when using MATCH command for numerical column and specifying a value which includes a percent sign. Support for percent sign (%) in MATCH command values was not supported for columns containing numerical data, although the documentation indicated that this should be valid. Support for percent signs in numerical column MATCH command values has been added as per the current documentation. PM53167
2 IDI0145I IDIS subtask IDISCJST terminated ECB=400C4000 and IDI0144E IDIS IDISAMAN:990 Unexpected condition. The Fault Analyzer IDIS subsystem may have intermittent failure producing IDISCJST and IDISAMAN ECB=400C4000 and termination. Correct unchaining of the Queue element under task termination has been added. PM52562
3 IBM Fault Analyzer not using the EPIE in a U4036 abend to report the original problem. Under some conditions, the EPIE address from R2 for a U4036 abend is not used to report the initial abend. The code has been updated. PM53168
4 Abend S0C4 during CICS system dump analysis. An invalid stack entry was being processed. Invalid stack entries are now ignored. PM49599
5 During transaction DUMP analysis, Fault Analyzer abends with ATCV and CICS terminates with DFHPC0409. Fault Analyzer is not reacting to a TERMERR condition and is continuing to use the terminal. Fault Analyzer has been changed to detect the TERMERR condition and prevent further use of Terminal Control. PM53169
6 IDISF8130S File not found "SYSLOGIC *" when calling IDILANGX with PARM= *PL( When the EXEC PGM=IDILANGX PARM= has a program name ending with PL, and is immediately followed by an opening bracket, then the error will occur. A space prior to the bracket will circumvent the problem. Misinterpretation of the "*PL(" sequence for PermitLangx option has been corrected. PM52564
7 PL/I decimal floating point (DFP) variables show incorrect values. FA does not support PL/I DFP variables. Support for PL/I DFP variables has been added. PM50154
8 Listing exit not called when COBOL program is compiled with TEST(NOSEP). Listing exit not called for PROGSUM compiler listings. Listing exit now called for PROGSUM compiler listings. PM53170
9 Incorrect program name for PL/I procedures included from package. Packaged procedure used to form mangled CSECT name is not known. Code to determine which procedure was used to name the CSECT added. This code requires that a procedure with the same name as the package is available. PM47309
10 PL/I SYSDEBUG file not used. CUI fixup table not in minidump when DEFERREDREPORT option is in effect. Code to locate CUI fixup pages in minidump added. PM50349
11 Message IEC036I abend S002-18. A fault entry record used for saving a DB2 SQLDA data area exceeded the maximum logical record length of 10000 bytes. The DB2 SQLDA data area is now saved across multiple records if necessary. PM53171
12 Enterprise PL/I does not report defined structure types or anonymous unions. Defined structure types or anonymous unions were not supported. Support has been added for defined structure types and anonymous unions. PM51689
13 RESET or MATCH ALL from Fault Entry List display does not always result in the original list being shown. The Fault Entry List display was reformatted using the current array of fault entry information, which might have been modified due to sorting or matching. The current array of fault entry information is now being rebuilt from the last obtained history file cache. PM52232
14 ICH408I messages for JESSPOOL when using Fault Analyzer IVP interface under CICS. Unintentional use of fflush function which under IPV was causing the JESSPOOL SAF check. The fflush usage has been corrected. PM53162
15 When a program terminates with an SQLCODE=-805, the wrong DB2 package information is shown. When a DBRM is contained in many packages, and an attempt is made to display the package information, then the wrong information is being shown. Fixed the call for package information to only show packages that are bound to the associated plan. PM53172
16 Abend S0C4 in pp_ke_stack when analyzing CICS system dump. Processing continues past the end of the label-names table. Processing now ends once the end of the label-names tables has been reached. PM51892
17 Fault Analyzer IDI0131W Waiting for History File SPFEDIT ENQ messages from the IDIS subsystem. IDI0131W ENQ contention followed by IDI0130E time-out problems might occur in the IDIS subsystems in a sysplex. ENQ timing window error corrected. PM53508
18 Error when processing CICS TS 4.2 auxiliary trace. Auxiliary trace header record 4.2 extension gave wrong offset to trace entries. Offset to trace entries in auxiliary trace data set corrected. PM53603
19 Message IDI0092S and RFR dump after a loop in Fault Analyzer. Under CICS and Debug Tool, a S0C4 abend and loop is possible with a CIB pointing to itself, causing IDI0092S Fault Analyzer time-out. The code now detects the potential CIB loop at this point of execution. PM53229

APAR PM44693 Fixes and Enhancements
Problem
Description
Fix
Complete APAR information
1 Fault Analyzer incorrectly reports COBOL compiler options TRUNC and CICS. Incorrect bit interpretation for TRUNC sub-options. CICS option cannot be reported without a compiler listing having been provided since info byte flag is not set. TRUNC sub-options corrected. Reporting of CICS option removed unless compiler listing has been provided for source level support. PM46050
2 PL/I overflow exceptions do not occur after call to IDISNAP. The PSW program mask was not saved and restored across the IDISNAP call. The PSW program mask is now saved and restored across the IDISNAP call. PM45362
3 The ENV.TCB_ADDRESS user exit data area field is always zero. The ENV.TCB_ADDRESS field was initialized using the high-word of a 64-bit address. The ENV.TCB_ADDRESS field is now initialized as the low-word of a 64-bit address. PM45449
4 Poor CICS abend analysis performance. Large number of loaded CICS programs was causing performance problems when analysing. Internal processing of large number of loaded programs has been enhanced to reduce performance overheads. PM46049
5 User "steps" through program with CEDF and issues PF12 (abend), User gets EXEC CICS ADDRESS ACEE screen from Fault Analyzer, which affects further abend processing. Fault Analyzer's EXEC CICS ADDRESS ACEE command does not set the NOEDF bit to suppress EDF processing Fault Analyzer has been changed to set the NOEDF bit on its EXEC CICS ADDRESS ACEE command. PM47171
APAR PM42267 Fixes and Enhancements
Problem
Description
Fix
Complete APAR information
1 Format XML data option not always displayed correctly in interactive reanalysis. The detection mechanism of formatable XML data was not correctly allowing for ASCII data. ASCII data is now correctly accounted for. PM43677
2 IDI0047S exception in getVarStg1. Invalid storage was not being correctly allowed for. Storage check has now been inserted. PM44247
3 Plug-in user cannot authenticate when adding new history file. Plug-in uppercases passwords before authentication, which causes problems with RACF mixed-case password policies. Plug-in leaves the password alone and sends it as is. PM44248
4 Abend when processing multi-line COBOL statements that reference table elements. Source parse buffer too small. Source parse buffer size corrected. PM44249
5 FA incorrectly reports COBOL storage as not accessible. DCB in Working-Storage causes FA to 'trim' base locator storage. ACB/DCBs located in COBOL storage areas no longer affect base locator storage lengths. PM44250
6 Fault Analyzer IDIS subsystem high CPU usage. The IDIS subsystem can start using high amounts of CPU after an XCF slowdown. The code has been updated to recognise the problem and correct it. PM44251
APAR PM34295 Fixes and Enhancements
Problem
Description
Fix
Complete APAR information
1 Listing prompt not issued when compiler listing not found for COBOL program compiled with TEST(NOSEP). Listing prompt not issued for TEST(NOSEP). Listing prompt now issued when compiler listing not found for COBOL programs compiled with TEST(NOSEP). PM32189
2 Abend S0C4 in PliSepRec4 when PL/I SYSDEBUG side file source has include files. %INCLUDE statement has unexpected record length. Variable length source records now supported. PM41007
3 Abend S0C9 from entry point displayISPF when analyzing CICS SDUMP. Incorrect detection of CICS SDUMP was causing inappropriate code to be called. CICS SDUMP is now detected correctly. PM41008
4 Unable to apply action to user note on User Note List display if one or more notes are against 64-bit addresses. The address field is picked up from the display incorrectly The address field is now picked up from the display correctly. PM35223
5 Getting IDI0005S message indicating "lack of storage". The problem is caused by a recursive loop in the CICS Name Token Entry Chain. 1. Limit the number of entries in the CICS "Name Token Entr Chain" that are displayed (1000 entries). 2. Report how many entries have been shown. 3. Raise a "Severity 2 Observation" to indicate the possibility of a loop. PM41009
6 CICS ASCII container data is displayed as EBCDIC. The need to present the data in ASCII had been overlooked. CICS transaction analysis has been changed to present ASCII container data in ASCII. PM41886
7 Message "IDI0089I Subsystem IDISFPEX RC=4 (or RC=92), Rsn=7FFFFFFF . . .*" (non-printable characters appended) issued incorrectly. The message was incorrectly being passed back from a call t the IDIS subsystem. The message has been suppressed. PM41010
8 Abend S0C4 when Fault Analyzer attempts to process an invalid compiler listing from the 'Compiler Listing Not Found' pop-up. Code assumed compiler listing had been successfully processed into IDILANGX. Code checks IDILANGX format is valid. PM41011
9 DWARF/MDBG data set name not passed to EQAUEDAT for C/C++ programs. Data set name not passed to EQAUEDAT. DWARF/MDBG data set or path name now passed to EQAUEDAT. PM35891
10 Loop issuing message IDI0005S and finally running out of space with abend S878. The attempt to log message IDI0005S required additional storage, which in turn re-invoked the same code to issue message IDI0005S. Additional storage has been made available for the logging of the initial IDI0005S message. PM41012
11 Previous MATCH not reset when selecting View from View List display. An implicit reset of all MATCH values was missing. An implicit reset of all MATCH values has been added. PM37324
12 Unintended deletion of Fault Analyzer history file entries using IDIUTIL DELETE control statement or incorrect LISTHF output. Incorrect date conversion when using ABEND_DATE and TODAY-n with DELETE or LISTHF control statements. The date conversion problem has been fixed. PM37944
13 Hex-dumped storage not shown in batch report for inactive COBOL programs when PrintInactiveCOBOL option in effect. Incorrect condition for registering hex-dumped storage. Condition corrected. PM41013
14 Incorrect ENV data area layout. Supplied sample mappings for Assembler, COBOL, C and PL/I o the ENV data area were incorrect from the POF_LOADED_FROM field at offset X'204' and onwards. The ENV data area has been changed to match the documented layout and sample mapping members. PM38906
15 Abend S0C4 in function pp_sm_task_sca during interactive analysis of CICS SDUMP. A 'null' value for a storage management control block was not being allowed for. Check added for 'null' pointer. PM40247
16 Some user exit character format data area fields contain binary zeroes. Trailing binary zeroes in user exit character format data area fields had not been removed. Trailing binary zeroes in user exit character format data area fields have been removed. PM38931
17 Loop in Fault Analyzer IDIS subsystem. The Fault Analyzer IDIS subsystem might loop in CSECT IDISXCFA after XCF error recovery. Code added to detect and prevent the condition. PM41014
18 Abend S0C4 in IDILANGX when processing HLASM SYSADATA. The HLASM SYSADATA from a PLX compilation might cause a S0C4 in IDILANGX entry name RESOLVE_USING_INFO. Code has been added to detect a zero CSECT ID error. PM41015

APAR PM28208 Fixes and Enhancements
Problem
Description
Fix
Complete APAR information
1 CICS transaction waits indefinitely for Fault Analyzer processing. The potential existed for two Fault Analyzer tasks to wait on the same ECB, and hence only one would be posted out of the wait. The dual ECB usage has been modified. PM33404
2 Message IDI0063W deletion of fault entry failed when using the V line command to generate a saved report and XFACILIT access is UPDATE. A check for XFACILIT ALTER access was incorrectly being made. The check for XFACILIT ALTER access has been eliminated as part of the fault entry refresh processing. PM33405
3 IDI0011S abend U4093 (X'FFD') reason code X'90' when calling IDISNAP. Fault Analyzer was being invoked in a POSIX(ON) LE environment. POSIX(OFF) has been added to the Fault Analyzer invocation. PM33406
4 Abend S0C4 when processing truncated COBOL SYSDEBUG side file. Freed storage pointers not reset causing subsequent free to abend S0C4. Freed storage pointers now reset. PM33407
5 Abend S0C2 in module IDIXCEE entry point JOBINFO at offset X'476'. In a Websphere Application Server Control Region running storage protect KEY 2, if IBM Fault Analyzer has not been excluded from the region and an abend occurs causing Fault Analyzer to be called, it will get S0C2 trying to set KEY 8 execution mode from its IDIXCEE invocation exit. Code has been added to detect the call in KEY 2 and abort the analysis with message IDI0123S. PM33408
6 CFA transaction cannot be executed during CICS shutdown due to SHUTDOWN(DISABLE) setting. CICS default setting for SHUTDOWN status was being used. SHUTDOWN(ENABLED) has been added to the CFA transaction definition. PM33409
7 Source line not reported when using ISPF packed Enterprise PL/I compiler listing. The 'back-end' sections of an EPLI compiler listing require right-shifting since the ASA character '1' is not present. The right-shifting is not performed when using an ISPF-packed compiler listing. The right-shifting is now performed when using an ISPF-packed EPLI compiler listing. PM33410
8 Fault Analyzer receives abend AZTS while processing application abend AD2W. Fault Analyzer is attempting to capture the 3270 terminal buffer, but the MRO connection is no longer active, so Fault Analyzer suffers a Terminal Control abend. Fault Analyzer has been changed to suppress the 3270 buffer capture if the CICS connection has suffered an AD2W abend. PM33411
9 Abend S0C4 at entry point FormatXMLData offset X'4CE'. The buffer was too small to handle large amounts of XML data. Made buffer large enough to handle large XML data. PM33591
APAR PM29741 Fixes and Enhancements
Problem
Description
Fix
Complete APAR information
1 The V10.1 version of the Fault Analyzer User's Guide and Reference was shipped with the V11.1 GA level of the Japanese feature. The Japanese translation of the V11.1 Fault Analyzer User's Guide and Reference was not available at the V11.1 Japanese feature GA date. The Japanese translation of the V11.1 Fault Analyzer User's Guide and Reference is now available. PM29741

APAR PM27281 Fixes and Enhancements
Problem
Description
Fix
Complete APAR information
1 Installation of PTF UK62204 causes IEW2456E 9207 SYMBOL RX2LE016 UNRESOLVED. MEMBER COULD NOT BE INCLUDED FROM THE DESIGNATED CALL LIBRARY. The GA base component SMP/E RELFILEs were incomplete. The missing updates from the GA base component have been provided. PM27281

APAR PM26282 Fixes and Enhancements
Problem
Description
Fix
Complete APAR information
1 Abend S0C4 in Fault Analyzer CICS LE invocation exit, IDIXCCEE. Storage overlay and subsequent abend S0C4 in Fault Analyzer IDIXCCEE after VSMLIST returns a buffer containing a block count of zero. The logic is updated to detect and handle the block count of zero. PM26303
2 Abend S0C4 when attempting to show the SAA of the running task in a CICS system dump. A string field was too short, causing corruption of following fields. The size of the string field has been increased. PM26306
3 IDI0034I analysis skipped when '*' is specified as EXCLUDE option value for a suboption which is not applicable to the current fault. A value for a non-applicable suboption was being tested and found to match. Non-applicable suboptions are no longer tested for matching INCLUDE/EXCLUDE option values. PM26307
4 Abend S0C4 in CheckLangx() when IDILANGX file does not contain a CSECT name record. CheckLangx() does not test pointer to CSECT name record, which will be invalid if no CSECT name record was read from the data set. The CSECT name record is mandatory. The side file will be rejected and message IDI0095W issued. PM26994
5 Abend S0C1 at entry point VSAMPT following message IDI0006E open error. A VSAM POINT macro was executed without first checking for successful OPEN of the VSAM data set. A check for successful OPEN has been added. PM26995
6 Abend S0C4 at entry point cob_file_error when processing COBOL abend. Storage containing the FCB number was not available, but processing continued. File not processed by cob_file_error if FCB number not available (file might still be reported in system-wide section). PM26905
7 Abend S0C4 when using Compiler Listing Read user exit with LST data area field DATA_BUFFER_DSN = 'Y'. The Compiler Listing Read user exit performs extraneous IDIWRITE of listing data set name to a temporary data set, even though LST data area field DATA_BUFFER_DSN = 'Y'. This might result in an S0C4 abend. LST data area field DATA_BUFFER_DSN = 'Y' is now checked and the "one record at a time" code is not executed. PM26906
8 IDI0011S abend U4093 (X'FFD') reason code X'90' when Fault Analyzer is invoked though IDIXDCAP or IDIXCEE with POSIX(ON). Fault Analyzer was being invoked in a POSIX(ON) LE environment. POSIX(OFF) has been added to the Fault Analyzer invocation. PM27990


All available Version 10 Fault Analyzer PTFs and associated APARs (most recent first):

English Base Component
Japanese Feature
Korean Feature
PTF Download links
UI17443 Download PTF UI17443
UI14784 Download PTF UI14784
UI13512 Download PTF UI13512
UI12554 Download PTF UI12554
UK98120 Download PTF UK98120
UK96964 Download PTF UK96964
UK95273 Download PTF UK95273
UK93744 Download PTF UK93744
UK91960 Download PTF UK91960
UK83898 Download PTF UK83898
UK82537 Download PTF UK82537
UK80689 Download PTF UK80689
UK79482 Download PTF UK79482
UK78560 Download PTF UK78560
UK76704 Download PTF UK76704
UK74641 Download PTF UK74641
UK71798 Download PTF UK71798
UK70115 Download PTF UK70115
UK68854 Download PTF UK68854
UK68120 Download PTF UK68120
UK68121 Download PTF UK68121
UK65177 Download PTF UK65177
UK62342 Download PTF UK62342
UK59774 Download PTF UK59774
UK56713 Download PTF UK56713
UK55782 Download PTF UK55782
UK54542 Download PTF UK54542
UK53012 Download PTF UK53012
UK53023 Download PTF UK53023
UK52832 Download PTF UK52832

PTF
Availability date
Prerequisite PTFs
Supercedes these PTFs
APAR(s) this PTF fixes
English:
UI17443
2 May 2014 UI14784 PI11058
PI16330
PI16331
PI16332
PI16333
PI16334
PI16335
PI16336
PI16337
PI16338
English:
UI14784
7 Feb 2014 UI12554
UI13512
UK52832
UK54542
UK55782
UK56713
UK59774
UK62342
UK65177
UK68854
UK70115
UK71798
UK74641
UK76704
UK78560
UK79482
UK80689
UK82537
UK83898
UK91960
UK93744
UK95273
UK96964
UK98120
PI08460
PI10685
PI10686
PI10687
PI10688
PI10689
PI10690
PI10691
PI10692
PI10693
PI10701
English:
UI13512
2 Jan 2014 UI12554
UK52832
UK54542
UK55782
UK56713
UK59774
UK62342
UK65177
UK68854
UK70115
UK71798
UK74641
UK76704
UK78560
UK79482
UK80689
UK82537
UK83898
UK91960
UK93744
UK95273
UK96964
UK98120
PI06356
PI07768
PI07769
PI07770
PI07771
PI07772
PI07773
PI07774
PI07775
PI07859
English:
UI12554
19 Nov 2013 UK52832
UK54542
UK55782
UK56713
UK59774
UK62342
UK65177
UK68854
UK70115
UK71798
UK74641
UK76704
UK78560
UK79482
UK80689
UK82537
UK83898
UK91960
UK93744
UK95273
UK96964
UK98120
PI05478
PI05564
PI05565
PI05566
PI05572
PM98462
English:
UK98120
5 Oct 2013 UK52832
UK54542
UK55782
UK56713
UK59774
UK62342
UK65177
UK68854
UK70115
UK71798
UK74641
UK76704
UK78560
UK79482
UK80689
UK82537
UK83898
UK91960
UK93744
UK95273
UK96964
PM95844
PM97975
PM97976
PM97977
PM97978
PM97979
PM97980
PM97981
PM97982
PM97983
English:
UK96964
30 Aug 2013 UK93744
UK95273
PM91557
PM95334
PM95335
PM95336
PM95337
PM95338
PM95339
PM95340
PM95341
PM95342
English:
UK95273
23 Jun 2013 UK93744 PM87489
PM88086
PM91074
PM91075
PM91076
PM91077
PM91078
PM91079
PM91253
English:
UK93744
24 Apr 2013 UK52832
UK54542
UK55782
UK56713
UK59774
UK62342
UK65177
UK68854
UK70115
UK71798
UK74641
UK76704
UK78560
UK79482
UK80689
UK82537
UK83898
UK91960
PM83919
PM87067
PM87481
PM87482
PM87483
PM87484
PM87485
PM87486
PM87487
PM87488
PM87490
PM87491
PM87492
PM87493
PM87494
PM87495
PM87496
PM87497
PM87498
PM87499
PM87500
PM87501
PM87577
English:
UK91960
4 Mar 2013 UK52832
UK54542
UK55782
UK56713
UK59774
UK62342
UK65177
UK68854
UK70115
UK71798
UK74641
UK76704
UK78560
UK79482
UK80689
UK82537
UK83898
PM78351
PM81910
PM81983
PM82072
PM82073
PM82074
PM82075
PM82076
PM82077
PM82078
PM82079
PM82080
PM82081
PM82082
PM82083
PM82084
PM82865
PM83909
English:
UK83898
2 Jan 2013 UK52832
UK54542
UK55782
UK56713
UK59774
UK62342
UK65177
UK68854
UK70115
UK71798
UK74641
UK76704
UK78560
UK79482
UK80689
UK82537
PM74987
PM77687
PM77688
PM77689
PM77690
PM77691
PM77692
PM77693
PM77694
PM77695
PM77696
PM77697
PM77698
PM77699
English:
UK82537
1 Nov 2012 UK52832
UK54542
UK55782
UK56713
UK59774
UK62342
UK65177
UK68854
UK70115
UK71798
UK74641
UK76704
UK78560
UK79482
UK80689
PM70212
PM72788
PM72808
PM72809
PM72810
PM72811
PM72812
PM72813
PM72814
PM72815
PM72816
PM72817
PM72818
PM72819
PM73775
PM74210
PM74215
English:
UK80689
4 Sep 2012 UK52832
UK54542
UK55782
UK56713
UK59774
UK62342
UK65177
UK68854
UK70115
UK71798
UK74641
UK76704
UK78560
UK79482
PM67621
PM68998
PM68999
PM69000
PM69001
PM69002
PM69470
PM69471
English:
UK79482
2 Jul 2012 UK52832
UK54542
UK55782
UK56713
UK59774
UK62342
UK65177
UK68854
UK70115
UK71798
UK74641
UK76704
UK78560
PM64220
PM65407
PM65408
PM65409
PM66968
English:
UK78560
3 Jun 2012 UK71798
UK74641
UK76704
PM60756
PM63990
PM63992
PM63996
PM63998
PM63999
PM64000
PM64008
English:
UK76704
3 Apr 2012 UK71798
UK74641
PM54423
PM57765
PM59057
PM59059
PM59063
English:
UK74641
1 Jan 2012 UK71798 PM46859
PM47920
PM49311
PM50898
PM52599
PM53163
PM53166
PM53173
PM53174
PM53175
PM53176
PM53177
PM53178
PM53179
PM53180
PM53181
PM53182
PM53857
English:
UK71798
3 Oct 2011 UK52832
UK54542
UK55782
UK56713
UK59774
UK62342
UK65177
UK68854
UK70115
PM44694
PM45593
PM46051
PM46052
PM47172
English:
UK70115
1 Aug 2011 UK59774 UK62342
UK65177
UK68854
PM42268
PM44246
PM44252
PM44253
PM44254
PM44255
PM44256
English:
UK68854
5 Jul 2011 UK59774 UK62342
UK65177
PM34271
PM34296
PM35360
PM35887
PM35904
PM36413
PM38414
PM39420
PM40245
PM41016
PM41017
PM41018
PM41245
PM41246
PM41247
PM41248
PM41249
Japanese:
UK68120
1 Jun 2011 PM34390
Korean:
UK68121
1 Jun 2011 PM34391
English:
UK65177
4 Apr 2011 UK59774 UK62342 PM27330
PM28357
PM33401
PM33412
PM33413
PM33414
PM33415
PM33416
PM33417
PM33592
English:
UK62342
1 Dec 2010 UK59774 PM21096
PM21303
PM21816
PM24007
PM24531
PM25308
PM25988
PM26052
PM26053
PM26066
PM26147
PM26148
PM26149
PM26154
PM26156
PM26163
PM26806
PM26810
PM26817
PM26925
English:
UK59774
1 Sep 2010 UK52832
UK54542
UK55782
UK56713
PM14420
PM14672
PM15920
PM17201
PM17250
PM19316
PM19570
PM19729
PM19803
PM19823
PM19825
PM19827
PM19864
PM19925
PM20010
PM20666
English:
UK56713
2 Jun 2010 UK55782 PM11905
PM13386
PM13683
PM13685
PM13687
PM13694
PM13887
PM13894
PM14007
English:
UK55782
4 May 2010 UK52832
UK54542
PM08932
PM09208
PM09443
PM09480
PM10154
PM11410
PM11513
English:
UK54542
1 Mar 2010 UK52832 PM03974
PM05169
PM06413
PM06477
PM07465
PM07707
PM07720
PM08038
PM08053
Japanese:
UK53012
1 Feb 2010 PM02649
Korean:
UK53023
1 Feb 2010 PM02650
English:
UK52832
5 Jan 2010 PM00092
PM03532
PM03535
PM03538
PM03544
PM03547
PM03551
PM03552
PM03554
PM03558
PM03561
PM03565
PM03566
PM03569
PM03573
PM03577
PM03579
PM03582
PM03586
APAR PI11058 Fixes and Enhancements
Problem
Description
Fix
Complete APAR information
1 Incorrect Compiler Listing display pseudo assembler instructions default setting. The product default, when the user has not yet selected either "Add Pseudo Assembler Instructions" or "Remove Pseudo Assembler Instructions" from the action-bar View pull-down menu, is to show the pseudo assembler instructions. This is incorrect according to the documentation. The product default has been changed to not include the pseudo assembler instructions in the Compiler Listing display. PI16330
2 Abend S0C4 in IDIXDCAP with messages IDI0012S and IDI0013S. A zero value while looping through a set of data was not being correctly allowed for. A zero value is now correctly handled. PI16331
3 Fault Analyzer loop when trying to display Java event. If a Java source file can not be successfully opened, then the code might loop. The code has been corrected to prevent the loop. PI16332
4 CICS formatted trace entries are missing location information following the colon, as in "Called-from-address <address> : <location>". 64-bit addresses were not handled correctly. 64-bit addresses are now being handled correctly. PI16333
5 Too many allocations of the Fault Analyzer history file. A frequently used system service is causing dynamic allocation. The system service is now called using pre-allocation. PI16334
6 Console flooded with IDI0088E messages. Storage abend during ESTAE recovery while invoking the Binder program. The ESTAE is now cancelled before activity requiring virtual storage occurs. PI16335
7 IDILANGX ends with CEE0802C at entry point LSMMFREE. Max locates records causes write buffer overrun. Max locates records reduced to fit write buffer. PI16336
8 Message IDI0131W Waiting for history-file($$INDEX) SPFEDIT ENQ when ENQ is held by a TSO user. Abend in a TSO screen running Fault Analyzer might leave the $$INDEX ENQ outstanding until the TSO session is logged off. Code added to help DEQ processing in the case of Fault Analyzer abending in TSO/ISPF. PI16337
9 IMS MPP terminating but does not end. The MPP termination was held up by Fault Analyzer processing that had stalled. Monitor task added to ensure the IDIDA TCB attaches and runs successfully. PI16338
APAR PI08460 Fixes and Enhancements
Problem
Description
Fix
Complete APAR information
1 When processing CICS Trace entries to determine source line #, the mismatch pop-up is presented, even though the COBOL SYSDEBUG file matches. DEBUGINF is not in the minidump. DEBUGINF added to minidump during COBOL CLLE discovery. PI10685
2 Cursor scrolling not working correctly on the CICS Internal Trace display, Saved Report display and Compiler Listing display. The saved cursor position was being retrieved from an incorrect variable. The saved cursor position is now retrieved from the correct variable. PI10686
3 Error message "Not a history file" when specifying a migrated data set name on the Fault Entry List display. The check for expected history file attributes failed when the data set was migrated. An additional check for a migrated data set has been added, prior to the attribute check. PI10687
4 Fault Analyzer IDIS subsystem might get recursive IDI0144E and IDI0124E messages. If the XCF message chain pointer is overlayed, the IDIS subsystem might get recursive abends with messages IDI0144E and IDI0124E. The logic has been updated to resolve the chaining error. PI10688
5 Blank saved report displayed with 'V' or 'S' line command if history file specified using single quotes in a View member. The single quotes were not expected and caused fopen of the fault entry member to fail without an error message being issued. An error message will be issued if failing to open the fault entry member and specification of single quotes around View member history file names has been supported. PI10689
6 Fault Analyzer report for IMS Java might show an additional incorrect LE U4038 abend in the event summary. IMS with Java and CEEPIPI might cause Fault Analyzer to add a historical CIB event incorrectly in the report. The condition has been catered for in the code. PI10690
7 Fault Analyzer might produce more than one RFR dump for one abend when short on storage. Recursion of S878 conditions during Recovery Fault Recording (RFR) processing can cause more than one SDUMP to be taken for the one initial abend. Code has been added to stop additional SDUMPs against one fault entry. PI10691
8 More than one fault entry might be created if the IDIS subsystem is experiencing Cross-System Coupling Facility (XCF) message delays. With XCF message delays in the IDIS subsystem, the recovery process might cause more than one fault entry to be created for the same abend job and timestamp. Code added to stop assignment of a new fault ID if one already exists for the same job and timestamp. PI10692
9 Message IDI0095 IDICABND:1415 CSVQUERY error. Some Fault Analyzer analysis jobs might get IDI0095W unexpected condition, CSVQUERY error. Code added to accommodate provider field request getting rc=4. PI10693
10 Message IDI0092S Time 32 minutes for analysis exceeded. Loop in code at entry point cDDfCloseP. The code has been fixed to prevent the loop from occurring. PI10701
APAR PI06356 Fixes and Enhancements
Problem
Description
Fix
Complete APAR information
1 MATCH CSR not working if help text is enabled, the display has been scrolled to hide the help text, and the cursor is placed in a field near the bottom of the display. The check for the cursor position within the ISPF dynamic area failed to correctly cater for the hidden help text. The problem has been corrected. PI07768
2 Fault Analyzer IDIS subsystem IDI0095W ENQ ECB status error and IDI0131WENQ delay lockout on history file. When XCF message delays occur, the IDIS subsystem recovery might get an ENQ status error that causes recurring IDI0131W messages until the IDIS subsystem is restarted. ENQ processing changed to accommodate the timing issues. PI07769
3 Extraneous subscript when formatting multi-dimension COBOL tables. Dimension not decremented correctly. Dimension decremented corrected. PI07770
4 Storage overlay in fileLANGX() while processing scope records. Scope slot index is out of bounds. Scope slot index corrected. PI07771
5 Abend S0C4 from entry point ProcHistDA statement 6965 offset X'81BA' when pressing Enter after selecting an empty history file for display. The determination of display characteristics to be used for the re-display did not correctly handle the situation where the history file contains zero fault entries. The problem has been corrected. PI07772
6 Incorrect Fault Entry List display scroll down action under CICS, when help text is enabled and the top-most fault entry is displayed. The ZSCROLLA value returned by VGET in this environment was not blank-padded as expected. The ZSCROLLA value is now processed correctly, regardless of blank-padding after VGET. PI07768
7 Symbol substitution not working in the alternative parmlib data set name specified via the IDIOPTLM configuration-options module field CNFDSN. The symbol substitution service output buffer length was set too short. The buffer length has been set to the correct value. PI07773
8 Message "ICH409I 282-020 ABEND DURING RACHECK PROCESSING" during analysis of Java dump. A valid history file data set name had not been set from the Fault Entry List display prior to the dump analysis, resulting in a blank history file data set name being checked for access authorization. A check has been added for the existence of a non-blank history file data set name prior to the RACHECK call. PI07774
9 Fault Analyzer empty report, no events from RFR dump after IDI0055S out of storage message. The RFR SDUMP after an out of storage IDI0055S message might not get a TCB selected for analysis. The code has bee updated to determine the TCB issuing the RFR call. PI07775
10 Fault Analyzer might generate more than one fault entry for the same event. The additional fault entries have no minidump or report content. More than one fault entry for the same job and timestamp if delays in XCF coupling facility messages cause retransmit of a fault ID assignment. The code has been updated to cater for the potential re-transmission of an assignment request via XCF. PI07859
APAR PM98462 Fixes and Enhancements
Problem
Description
Fix
Complete APAR information
1 Fault Analyzer RFR dump event list might be missing events. The DSA chaining back through linkage stack entries might fail when an invalid backchain address in encountered. The code has been updated. PI05478
2 New History File Allocation dialog not shown when copying fault entry to non-existing history file. A check for the existence of the target history file was missing. A check has been added for the existence of the target history file. PI05564
3 A Fault Analyzer user is analyzing a CICS SDUMP, and sees errors in the DS Domain panels. DS panels have incomplete information due to an arbitrary limit to the number of internal control blocks that can be created. Also, there is a problem in sorting some column contents. The number of internal control blocks which can be created has been increased. The panel column sort code has been fixed. PI05565
4 User gets DFHSR0622 because of abend 0C4 in CEECGEX. User has issued PURGE of CICS task. FA's IDIXCCEE issues EXEC CICS commands in CICSkey and enters WAIT_MVS. User issues KILL for task. CICS drives LE CEECGEX in USERkey with CICSkey DSA/RSA from IDIXCCEE. IDIXCCEE has been changed to percolate (defer) AEXY abends to FA CICS GLUEs, which do not issue EXEC CICS commands in a way that can cause the problem. PI05566
5 Fault Analyzer IDIS subsystem IDI0131W messsages ENQ lockout on history files. APAR PM97968 fixed the 100% CPU loop reported but the IDI0131W messages can still occur. This APAR addresses the IDI0131W ENQ message not clearing. Code added to correctly retest the ENQ status. PI05572
APAR PM95844 Fixes and Enhancements
Problem
Description
Fix
Complete APAR information
1 Debug Tool analysis of HLASM might fail to display some field data. The use of USING (Dsect,DsectEnd),R10 form rather than traditional USING Dsect,R10 will cause a problem with EQALANGX respecify record data. The code has been updated to correct the problem. PM97975
2 Fault Analyzer report has 'no data' in the event list. If the MVS RB chain can not be traced because of a missing page in the minidump, the available list of events was not displayed. Code updated to better handle the next RB not being available. PM97976
3 The user is analyzing a CICS SDUMP and is seeing an incorrect task state in the DS Domain Task Summary panel. Task State is shown as "R" when it should be "A". FA CICS SDUMP analysis is interpreting a CICS status byte incorrectly. IDIECDS has been changed to interpret the task status byte correctly. PM97977
4 Cursor is placed on the Fault Entry List display command line after deletion of fault entry if option to confirm deletion is in effect. The original cursor position is not saved prior to displaying the delete confirmation panel. The cursor is now positioned correctly. PM97978
5 Fault entry duplicate count on the Fault Entry List display shows a negative or decreasing value. The duplicate count is held in a signed halfword which is displayed as a negative value if more than 32,767 duplicates have occurred, or a decreasing value if more than 65,535 duplicates have occurred. The duplicate count field is treated as unsigned, which allows for up to 65,535 duplicates. Once this limit is reached, the count will remain unchanged at its maximum instead of wrapping. PM97979
6 Abend S282-20 when exiting interactive MVS dump analysis. The Fault Analyzer ISPF interface was invoked with a history file name set to a non-existing data set. A check has been added for the existence of the target history file to prevent the abend S282-20 from occurring. PM97980
7 IDI0047S from Fault Analyzer in MAPLMOD processing. Intermittent abend S0C4 in Fault Analyzer IDIDA MAPLMOD causing IDI0047S and an RFR dump to be created for recovery processing of the fault entry. The MAPLMOD processing updated to correctly test the return from GETDSVOL processing. PM97981
8 Fault Analyzer IDIS subsystem loop with IDI0131W message and high CPU. Under some XCF recovery conditions, the IDIS subsystem might loop causing high CPU usage. Code changed to handle the potential XCF recovery timing condition. PM97982
9 Message "ERROR: IactLEabend() can't be invoked from IDIPDDIR!" issued when looking up abend code explanation from Fault Entry List display. This is a diagnostic message that was incorrectly left as a message to the user rather than being written to a trace data set. The message is no longer displayed to the user and is only written to the trace data set. PM97983
APAR PM91557 Fixes and Enhancements
Problem
Description
Fix
Complete APAR information
1 IBM Fault Analyzer IDI0095W Unexpected condition IDIDODSN:360 when exiting interactive analysis of an MVS dump. When completing an interactive reanalysis of an MVS SVC or SYSMDUMP, the write minidump process might issue IDI0095W from IDIDODSN:360. The logic has been changed to handle the allocation condition. PM95334
2 IDI0095W Unexpected condition found in IDISUPDI:1426: IDISUPDI:1851 :1426 dup time precedes fault entry. IBM Fault Analyzer CICS fast duplicate processing might record a vendor altered start time rather than the wall-clock time, even when the UseIDISTime option is set. Code updated to accommodate date/time alteration test products in the CICS fast duplicate recording process. PM95335
3 Listing exit issues IDISF messages when exit returns a SYSDEBUG dsn. Listing exit fails to process a SYSDEBUG, then attempts to process it as a compiler listing. Listing exit now correctly processes SYSDEBUG files. PM95336
4 After scrolling Fault Entry List display right, abend code explanation is shown instead of processing line command. When a point-and-shoot field, such as the "Abend" column field, is scrolled to logically overlap with the line command field, then the point-and-shoot field is incorrectly processed instead of the line command. An error determining the line offset in displays with a non-scrollable section on the left has been fixed. PM95337
5 COBOL ODO table has incorrect stride. ODO recalibration includes redefinitions which causes data item length to be added again. Only the original definition is inlcuded in recalibration of ODO tables. PM95338
6 Language Environment heap analysis errors not indicated in the Synopsis section of the report. The specific Language Environment heap analysis errors found in this case had not been made eligible for identification in the report Synopsis. All Language Environment heap analysis errors are now being identified in the Synopsis with a reference to detailed information about the errors in the Language Environment heap analysis section of the report. PM95339
7 Fault Analyzer's CICS SDUMP "SM ECDSA Subpool Summary" panel displays some incorrect or unclear values, Some values are being obtained from the wrong place. Some values are correct but are displayed in hex, while the CICS VerbExit displays them in decimal. Fault Analyzer has been changed to display the correct values, and to display both hex and decimal values where appropriate. PM95340
8 Lock flag incorrectly reset after fault entry interactive reanalysis when Enter is pressed on exit to save changes to user data. The fault entry lock flag was being managed, both in the fault entry member, and in the history file cache, causing incorrect updates. The fault entry lock flag is now only being managed in the history file cache. PM95341
9 Loop during abend analysis leading to IDI0005S message. FA code was not allowing for an LE CIB next pointer to be pointing to itself. Hence, FA went into a loop which eventually exhaused all storage and gave a IDI0005S message. Loop detection code added. PM95342
APAR PM88086 Fixes and Enhancements
Problem
Description
Fix
Complete APAR information
1 When filtering history file columns in the plug-in, the filters would only match the (always uppercase values) if typed in uppercase. The plug-in column filtering is case sensitive, meaning that all filter values must be typed in uppercase to match column fields. The column filter value is now case-insensitive. Typing the filter in upper or lowercase will now match the column field values. PM91074
2 Analysis Control user exit ENV.IMS_PROGRAM_NAME blank when Fault Analyzer is invoked for an IMS user abend. The code which obtains the IMS program name was not executed due to NoDup(ImageFast(...)) processing being bypassed. The IMS program name is now obtained regardless of whether NoDup(ImageFast(...)) processing is bypassed or not. PM91075
3 The Language Environment STORAGE option was not being reported correctly. LE added a new value to the LE STORAGE option in z/OS V1R13. Updated our processing to handle all the new LE options and values added in z/OS V1R13. PM91076
4 IDIUTIL IMPORT function abend SE37 on target history file. IDIUTIL IMPORT does not honor SetMaxFaultEntries setting. IDIUTIL IMPORT now honors SetMaxFaultEntries setting. PM87489
5 Missing source level information for a COBOL event. Although a compiler listing was provided, it was not being used to determine the source level information for the event due to incorrect signature determination. The signature determination problem has been fixed. PM91077
6 Abend S0C4 in ProcHistDA following message IDI0005S during implicit generation of saved report for 'V' or 'S' line command issued against a DeferredReport fault entry. Incorrect attempt to contunue processing following an out-of-space condition. IDIPDDIR will now terminate following a condition resulting in message IDI0005S being issued. PM91078
7 Report does not show any user code before abend. It appears that an abend after a call to IGZCLNK, and before the next DSA is created, will cause an old DSA to be overlayed. The user code event is no longer in the DSA chain. The broken DSA event is now included if it is a call to IGZCLNK. PM91079
8 DFHAP0701 An abend (code 0C4/AKEA) has occurred in exit program IDIXCX53 at exit point XPCABND. Fault Analyzer running with CICS and OPEN TCB's might get abend S0C4 indicated from IDIXCX53. Key 9 OPEN TCB exit processing has been updated. PM91253
APAR PM83919 Fixes and Enhancements
Problem
Description
Fix
Complete APAR information
1 Records are missing from the CICS Auxiliary Trace display. These records are mainly missing at the beginning and end of the trace. The file descriptor (pointer) used to read the contents of the trace was being incremented by the initial while() loop condition. This caused the record to appear invalid as it was missing key information. It also caused records at the end to be skipped to avoid buffer overrun. The pointer to the file content was set to one less than the current position, so that it always begins at zero/the start. The code for skipping the end records was also removed. PM87481
2 Attempting to sort a column in the Recovery Manager Link Summary page causes an abend in FA. The Recovery Manager adds line breaks between records of a different type, to group similar entries. This conflicts with the table sorting as it artificially increases the number of rows the table believes it needs to sort. The perceived last row is beyond the table range. The code that was adding line breaks between records has been removed, as it no longer appears after table sorting. This code appears to have been a holdover from before the table sorting logic was added. PM87067
3 Table headings in the CICS Bridge Domain are missing their first letter. Table heading labels are sometimes included in heading highlighting. The width of the columns was one character short for the last column. This was causing columns to not align as intended and for characters to be hidden in the display. The heading group labels were included after the beginning of some tables, causing them to appear in the table. The table column heading widths were adjusted to match the required values and the heading group labels were moved above the table to avoid being included in the formatting. PM87067
4 Storage Manager EDSA Limit and Total vales are incorrectly converted from Bytes to Megabytes. The EDSA Limit/Total values are presented in Megabytes, by dividing the number of bytes by 1024 * 1000. This should actually be divided by 1024 * 1024 to get the correct value. The value used in the division has been modified to accurately perform the conversion. PM87482
5 User is running CICS transaction under EDF. The transaction abends. EDF shows FA EXEC CICS commands. Also, resolve AZTS abends in FA. Some EXEC CICS commands in the FA Exits are translated with the EDF option. Also, CICS is abending some FA tasks with AZTS. FA's exit commands have been changed to set the NOEDF bit. FA has been changed to prevent AZTS abends from occuring during FA processing. PM87483
6 Parameters on call to IDISNAP from PL/I program are not being used. PL/I usage of a pointer to a pointer reference was not being correctly catered for. Pointer to pointer references corrected. PM87484
7 FA CICS Transaction Abend exit suffers AZTS abend during EXEC CICS RECEIVE BUFFER due to problems with MRO connection. FA issues RECEIVE BUFFER to an MRO terminal, but for some reason the TOR fails to complete the RECEIVE and issues Abend AZTS, causing further problems for the failing task. FA has been changed to tell CICS not to abend the task AZTS. Instead, CICS returns TERMERR to FA, which is handled. PM87485
8 Fault Analyzer errors, such as IDI0095W Unexpected condition found in IDICUSUB:2347: IDICUSUB:2253, when a corrupt fault entry is copied to a history file. If a fault entry is copied in ASCII rather than binary, and placed into a history file using ISPF, then processing errors will occur trying to read the member. Protection code has been added. PM87486
9 Abend S0C4 in PrtHdg() when reporting assembler CSECT storage. Bad return code incorrectly processed as register causing storage overlay. Only valid base registers are now processed. PM87487
10 Abend U2100 in load module IDIXDCAP. Insufficient storage to perform required module initialization. A check for available storage has been added, and if insufficient, message IDI0007S is issued. PM87488
11 CICS System Dump Analysis fails with IDI0005S. Dump contains a large number of 'inactive' COBOL programs, which are being discovered unnecessarily. Procedures now not called when processing CICS System Dump. PM87490
12 FA loops or issues IDI0005S when processing a large CICS SVC dump that has storage overlays. Bad RB contains an invalid CDE pointer. CDE pointer in RB now checked before use. PM87491
13 Fault Analyzer calling EQAUEDAT exit compiled with COBOL SSRANGE might get IGZ0073S length zero then U4038 IDI0115E and IDI0120S messages. If the first operand to EQAUEDAT compiled with COBOL SSRANGE has zero length, then IGZ0073S is issued from COBOL causing Fault Analyzer IDI0115E LE enclave abend U4038 message, followed by IDI0120S IBM Fault Analyzer internal abend U4038. If the first parm for EQAUEDAT is null, then it will be changed to the string "NULLFILE", so that COBOL SSRANGE is not triggered if the exit is compiled with COBOL. PM87492
14 IDI0011S no storage for IDIDA start or IDI0005S when application has //CEEUOPT ALL31(OFF). Use of LE //CEEUOPT DD with ALL31(OFF) when an abend calling Fault Analyzer occurs might get IDI0011S or IDI0005S messages trying to run Fault Analyzer below the line. The LE option has been overridden for the ATTACH of the IDIDA TCB. PM87493
15 Message IDI0105S when empty history file is displayed with IDIPDDIR. Changes related to recent interactive reanalysis storage constraint relief improvements caused an error allocating zero bytes of storage when no fault entries exist in the history file. The storage allocation error has been corrected. PM87494
16 Fault Analyzer showing abend PSW in the Debug Tool Exec Area when an abend on an instruction in the Exec Area occurs. Abends occuring on instructions being executed in the D/T Exec Area when using overlay hooks, should be logically relocated to the corresponding application code instruction. Code has been added to do the relocation. PM87495
17 Abend S0C4 at entry point pHexDumpAsc. During formatting of hex-dumped storage areas in the analysis report, the current storage area being processed was FREEMAINed outside of Fault Analyzer's control. The formatting of hex-dumped storage areas in the analysis report has been ESTAE protected to allow recovery in case of abends during real-time processing. PM87496
18 Fault Analyzer IDIUTIL RC=4, then RC=0 when the job is rerun. Doing an IDIUTIL run from a low activity system might first give return code 4, but on rerun be OK with RC=0. Logic changed to ensure subsystem cache is refreshed. PM87497
19 NoDup(Normal(...)) processing is not recognizing duplicate fault if point-of-failure CSECT or program offset is zero. A zero offset was being interpreted as a missing value. A zero offset is now being processed as a valid value if the point-of-failure CSECT or program name has been determined. PM87498
20 Message EDC6006E raise() issued for SIGABORT from entry point CMALLOC when IDILANGP is used against a SYSDEBUG file for a large program. IDILANGP issues a raise() condition when there is insufficient storage available in the TSO region to perform the required processing. IDILANGP now issues message IDI0005S if there is insufficient storage available in the TSO region to perform the required processing. PM87499
21 Abend S0C4 in ADD_XREF_ELEM when IDILANGX processes a COBOL compiler listing that has more than 64K references to a data item. IDILANGX XREF record cannot accommodate more than 64K references. A new IDILANGX XREF type 2 record has been introduced to accommodate more than 64K references to a data item. PM87500
22 When issuing the 'V' or 'S' line command against a fault entry without a saved report, one is generated but a different or no saved report is finally shown. Following the release of storage during implicit interactive reanalysis, and the subsequent rebuilding of this data, information pertaining to the current fault entry had been overwritten with that of another fault entry. Information about the current fault entry, following implicit interactive reanalysis, has now been restored correctly. PM87501
23 Once a Dump Registration Analysis Control user exit has set CTL.EXCLUDE to Y, then this becomes the new default. The variable containing the CTL.EXCLUDE setting was initialized only once and did not cater for situations where options processing was invoked repeatedly under the same TCB. The variable containing the CTL.EXCLUDE setting is now initialized correctly each time options processing is invoked. PM87577
APAR PM78351 Fixes and Enhancements
Problem
Description
Fix
Complete APAR information
1 CICS log reports message DFHAP1212 for program IDIXCCEE. Fault Analyzer's sample CICS program definitions do not match what CICS thinks is inside the program. IDISCICS sample member has been changed to remove the LANGUAGE() keywords from FA programs. This stops CICS from reporting a mismatch. PM82072
2 MSG IDI0005S IDIDODSN:2646 Storage allocation failed. Fault Analyzer analysis "file" menu option 5 of an SVC DUMP. During analysis of an SVC or SYSMDUMP containing COBOL, the process might run out of storage with message IDI0005S. The storage managemant for Base Locator logic has been changed to reduce the storage required for analysis. PM82073
3 The CICS Domain Manager screen displays an incorrect Phase value. Values of -F900 are shown instead of -0700, for example. The Phase value was being incorrectly interpreted, leading to incorrect negative values. The Phase value is now correctly interpreted. PM82074
4 Abend code blank in report generated by IDIUTIL LISTHF with LISTHF user exit. ENV.ABEND_CODE was not initialized correctly for an EXEC CICS DUMP fault. ENV.ABEND_CODE is now initialized correctly for an EXEC CICS DUMP fault. PM82075
5 IDI0115E LE enclave abend S002 and IDI0120S IBM Fault Analyzer internal abend S002 U0000. A record exceeding the maximum history file LRECL of 10000 bytes was attempted written to the fault entry. The data written is now split into multiple records if necessary. PM82076
6 SYSIDIDA.SYSOUT GRS resource contention due to a large number of abending TCBs attempting to invoke Fault Analyzer simultaneously. 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. 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. PM82077
7 Fault Analyzer runs out of memory when processing a large inactive COBOL program's working-storage. Re-allocation of BLW storage as base locators are processed requires an unnecessary large amount of duplicated memory. Working-storage is now allocated as a single area. PM82078
8 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. D/T monitor function might show wrong information for some registers when debugging HLASM programs because EQALANGX data is wrong. The code for setting the label flag has been updated. PM81983
9 CICS file owning region might get storage overlay SM0102 with Fault Analyzer running. A CICS region with many open files might get storage overlay with IBM Fault Analyzer active. The code has been corrected. PM82079
10 Message IDI0047S abend S0C4 and CICS region abend S40D reason code X'18'. The Fault Analyzer IDIDA TCB was attached with the wrong program protection key. The Fault Analyzer IDIDA TCB is now attached with the correct program protection key. PM82080
11 Message IDI0047S abend S0C4 at entry point CompMsgs. A message was issued prior to required initialization having been performed. A check has been added for the required initialization. PM82081
12 An abend (code 0C4/AKEA) has occurred at offset X'00005BA0' in module IDIXCX53. 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. The field is now correctly initialised. PM81910
13 Loop during analysis in dfhs_afcb. The end of the EXCI trace blocks was not being correctly identified and hence caused a loop. The end of the EXCI trace blocks is now correctly detected. PM82082
14 Various CICS abends during the capture of the 3270 buffer. 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. 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. PM82083
15 IDILANGX RC=1051 when processing PL/I compiler listing with many external variables. IDILANGX has a maximum of 1024 CSECTs. Number of CSECT slots increased to 2048. PM82084
16 Abend in DFHSUEX when a CICS task is purged during FA analysis. 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. Purge protection has been placed around the invocation exit execution. PM82865
17 In the General Purpose Registers display under the Fault Analyzer Eclipse plug-in, the source/statement line number is truncated. The buffer used to store the line number text was being terminated one character too early. When terminating the line number buffer, the position at which a null terminator is added has been increased by one. PM83909
APAR PM74987 Fixes and Enhancements
Problem
Description
Fix
Complete APAR information
1 Dump Storage display not formatted using 32 bytes per line when it should be. Despite the setting of an adequate preferred formatting width, and the use of a logical screen size which also permits storage formatting using 32 bytes per line, the Dump Storage display was formatted using only 16 bytes per line. The determination of sufficient width to allow for 32 bytes per line formatting has been corrected. PM77687
2 CICS Transaction Dump statistics might be wrong if Fault Analyzer is active in the CICS region. Even with the Fault Analyzer RetainCICSdump(ALL) option, the CEMT I TRD statistics might be affected by Fault Analyzer. The Fault Analyzer CICS suppress dump return code processing has been updated. PM77688
3 IDI0144E error IDISFPEX abend S0C4 in Fault analyzer IDIS subsystem. The IDIS subsystem might get IDI0144E from IDISFPEX abend S0C4 when the Fault Analyzer options have a long EXCLUDE option. Saving of the OPTION statement has been updated to accomodate any input length. PM77689
4 User enters CFA transaction and then uses PF9 to view the IVP screen. PROG753 is issued at the terminal intermittently. The CFA program IDIXFA is not initializing the IVP map as often as it should. IDIXFA has been changed to initialize the map before sending it. PM77690
5 Abend S0C4 at entry point PrtUDATA when passing back records with more than 256 characters from a Message and Abend Code Explanation user exit using 'IDIWRITE '. The long records were saved in XPL.DATA_BUFFER, which is only a 256 character field, causing overlays and corruption of data. Other symptoms than the S0C4 in PrtUDATA might be possible, depending on the record data and length. A separate dynamically allocated buffer is now being used, which is capable of handling record lengths up to 32K. PM77691
6 CICS gets DFHSM0002 X'0D0A' when customized DFHPEP issues TC SEND command. Fault Analyzer is "stacking" TCTTEDA, and CICS is freemaining it while it is stacked. Fault Analyzer will no longer stack TCTTEDA. PM77692
7 RDz dead process=721405 exited in exit code=137/9/160 or other errors after Fault Analyzer called for abend processing. In a UNIX DUBBED environment Fault Analyzer being called to handle an abend might cause LE envar_array pointed to from the EDB to be corrupted. The use of putenv() has been removed and replaced with an MVS name/token solution. PM77693
8 CICS U4038 abends on an L9 open TCB are not captured by Fault Analyzer No fault entry created for LE U4038 abends that occur on an open TCB running in key 9. Code updated to handle the key 9 processing. PM77694
9 With bad JCL in the IDIS subsystem causing an abend, and automated operations restarting it, the system LX entries can be depleted causing the need to IPL. The Fault Analyzer IDIS subsystem if continually restarted can cause depletion of the SYSTEM LX pool, requireing an IPL. The LX for IDIS is now reconnected so that restarts do not cause additional system LX values to be used. PM77695
10 AB/S00C4 004 IDIXDCAP IDIXDCAP IEAVTABD REGS/0B2FC FFFFF TTL: ABDUMP ERROR, COMPON=ABDUMP, COMPID=5752-SCDMP, ISSUER=IEAVTABD SVC dump taken from IEAVTABD when Fault Analyzer installed and a KEY 7 TCB abends. Processing for abends not in KEY 8 or 9 has been updated to generate IDI0123S Unsupported Environment message. PM77696
11 CICS SDUMP analysis AP domain task facility type and ID blank in some instances. A facility ID was only being determined when the facility type flag was 02. In this instance, the type flag was 01 but a facility ID was still available. Code enhanced to specifically check for a valid facility ID, even if the facility type is 01. PM77697
12 Abend SA78 in load module IDIXDCAP CSECT IDIXOPTC + X'C46'. An invalid address was used to FREEMAIN a work area. The correct address is now being used to FREEMAIN the work area. PM77698
13 SCRT not finding Fault Analyzer SMF89 records. Fault Analyzer SMF89 records might have invalid product data, stopping them being recognized by SCRT. Blank-padding has been added to the identity strings. PM77699
APAR PM70212 Fixes and Enhancements
Problem
Description
Fix
Complete APAR information
1 Connections column in MRO Conversations panel display cannot be sorted. The column definition was incorrect. The column definition has been corrected. PM72808
2 IDIUTIL LISTHF report shows blank abend code for CICS dump code fault entries. Support for CICS dump codes was missing. Support for CICS dump codes has been added. PM72809
3 IDILANGX fails to process a PL/I struct if its name is used for a struct member elsewhere. (Problem only occurs when the member name is declared first). IDILANGX fails to create a symbol for the struct. IDILANGX now creates a new symbol for the struct. PM72810
4 IDILANGX does not recognize 'Object-Ref' types in data division map section. 'Object-Ref' not recognized. 'Object-Ref' now recognized and resolved to pointer type. PM72811
5 Fault Analyzer Recovery Fault Recording process might fail with IDI0011S message. The RFR dump process might get a secondary 0C4 abend in IDIXALG offset X'5B2' with R9 address invalid. R9 setup is corrected. PM72812
6 IDI0092S Time 2 minutes for analysis exceeded. A loop occurred during scanning of storage for an eyecatcher due to an incorrect address parameter. The incorrect address parameter has been corrected. PM72813
7 EUDSA PAM display incorrect. The incorrect page size was being used when building the PAM display. Code has been added to dynamically check which page size to use. PM72814
8 Message IDI0115E and IDI0120S due to abend S002 in Fault Analyzer. Possibly also message IEC036 002-18. A fault entry EX segment length exceeded the history file LRECL of 10000 bytes. EX segments exceeding 10000 bytes have been split into multiple shorter segments. PM72815
9 Abend S0C9 at entry point displayISPF statement 3782 offset X'1CE1A' during MVS dump analysis. A value had not been initialized. The required value has now been initialized. PM72816
10 ABEND0C4-4 in DUBBEDER at offset X'D4' when Fault Analyzer called for an abend in a TCB not running in key 8. If a TCB not running in key 8 abends, and Fault analyzer is called, a secondary 0C4 can occur in DUBBEDER causing an SVC dump with title TITLE=ABDUMP ERROR,COMPON=ABDUMP, COMPID=5752-SCDMP,ISSUER=IEAVTABD. The DUBBEDER code has been changed for TCBs not running in storage protect key 8. PM72788
11 IDILANGX ends with rc=310 when processing VS COBOL II Rel 2.0 compile listing. IDILANGX does not support VS COBOL II Rel 2.0. Support for VS COBOL II Rel 2.0 added. PM72817
12 IDILANGX 0C4 in LINE_TO_STMT() when processing OS VS/COBOL compiler listing. Line_Acc_Info overlayed following multiple valid_info entries. Only one valid_info entry should be collected (working- storage length). Extraneous adds of valid_info removed. PM72818
13 IDILANGX of HLASM SYSADATA gets RC=0310. IDISF8231S Missing ENTRY ESD information. IDISF8233S Unable to determine identity of unnamed PC section. RC=0310 when the assembly uses an unnamed CSECT or START statement. The code has been changed to deal with the unnamed section. PM72819
14 Fault Analyzer problem report notes a recovered LE event as the point of failure. When an LE condition occurs, and is recovered from, then Fault Analyzer might incorrectly report the event that was recovered as the point of failure. The logic has been changed. PM73775
15 IDI0034I Fault analysis skipped due to: Abend S0C4 and SVC dump with title COMPON=JES3 ALLOCATION, COMPID=SC1BA, ISSUER=IATSIAI-RELENQ Following invocation for a S1FB abend, an abend S0C4 occurred in load module IATSIAI offset X'182' during dynamic allocation for a C run-time fopen() call. The cause of the problem being that Fault Analyzer was invoked during unconditional logoff processing for a TSO user. Fault Analyzer will no longer attempt to analyze abends which occur in the job scheduler IEESB605 TCB but will instead issue message IDI0123S. PM74210
16 Abend S0C4 in FindSymAddr when processing Enterprise PL/I parameter variables. Parameter storage accessibility not checked. Parameter storage accessibility now checked. PM74215
APAR PM67621 Fixes and Enhancements
Problem
Description
Fix
Complete APAR information
1 Fault Analyzer reporting U4038 as the point of failure when a later abend (S0C7 or other) was the real cause. An earlier exception, such as IGZ0014W from IGZEOPT that is recovered, might be incorrectly reported as the point of failure. Tests for earlier abends updated. PM68998
2 Storage not accessible when reporting COBOL storage using SYSDEBUG side file and OPT(FULL) compiler option. OPT(FULL) removes unreferenced data items but they are still found in the SYSDEBUG attribute table, and when processed attempt to consume unavailable storage. Unreferenced data items in the SYSDEBUG attribute table are now ignored. PM68999
3 IDILANGX issues message IDISF8158T when processing Enterprise COBOL compiler listing. Source line grid margin character '!' instead of expected '|'. IDILANGX accepts '!' as grid right margin character. PM69000
4 Abend S0C4 in IDIXDCAP+2FF6 DUBBEDER+2F8 with reg 9 at a bad address. Intermittent abend S0C4 in IDIXDCAP after Fault Analyzer has been called to capture an abend. The ESTAEX regester restore for R9 has been corrected. PM69001
5 Message IDAI1001E.PUT FAILED, ERROR FOUND WHILE UPDATING THE INDEX issued by the IDIS subsystem shortly after start-up. An automatic update of the Fault Analyzer IDIVSENU VSAM message and abend code explanation repository, during start-up of the IDIS subsystem, caused the KSDS index to become corrupted due to using POINT with only a partial key prior to using PUT when inserting records. The full key is now being used with POINT prior to PUT. PM69002
6 The user is looking at a CICS 4.2 transaction abend analysis and finds that the CICS trace does not contain the entries which lead up to the abend. The Fault Analyzer code which captures CICS 4.2 trace entries is calculating the start/size/end of the trace capture incorrectly. Fault Analyzer has been changed to calculate the start/size/end of the captured trace entries correctly, as happened with previous CICS versions. PM69470
7 A user who is analyzing a CICS SDUMP sees FA abend 0C4 in PP_LG_STREAM_SUMM. FA is analyzing a CICS SDUMP which has severely corrupted LG Domain control blocks. The analysis code abends because it doesn't handle the corrupted control block chains. IDIECLG PP_LG_STREAM_SUMM has been changed to terminate analysis of the LG control block chain if it is corrupted. PM69471
APAR PM64220 Fixes and Enhancements
Problem
Description
Fix
Complete APAR information
1 IDI0095W Unexpected condition found in IDIDODSN:1004: Process error. A CDE data area size was incorrectly set to 40 bytes. The CDE data area size has been changed to 32 bytes. PM65407
2 Abend S0C4 in IEAVENLU+50 when Fault Analyzer IDICSVCR is FREEMAINed at TCB DETACH. An S0C4 abend can occur if the Fault Analyzer router SVC is FREEMAINed when the TCB that loads it is DETACHed. The CDE use count error is corrected. PM65408
3 Excessive time taken to analyze COBOL abend when many base locators are processed. DSA address not passed to COBOL side file functions causes slow running entry point detection. DSA address now passed to COBOL side file functions. PM65409
4 Abend S0C4 at offset x'5E8' in Fault Analyzer IDIXASUB with GPR 3 bad. Intermittent S0C4 in Fault Analyzer IDIXASUB module IDIXDCAP or IDIXCEE. There might also be an SVC dump with title: ABDUMP ERROR, COMPON=ABDUMP, COMPID=5752-SCDMP, ISSUER=IEAVTABD Fixed incorrect offset in TCT addressing. PM66968
APAR PM60756 Fixes and Enhancements
Problem
Description
Fix
Complete APAR information
1 Explanations not available for VS COBOL II messages. VS COBOL II message explanations missing from the Fault Analyzer message repository. VS COBOL II message explanations have been added to the Fault Analyzer message repository. PM63996
2 IDILANGX abend S0C4 in ADD_XREF_ELEM when processing Enterprise COBOL 4.1 compiler listing. 7-digit LineID used in source and data xref sections. IDILANGX now accommodates the 7-digit LineID in source and data xref sections. PM64008
3 The user receives message IDI0113W when IPV is abended due to RTIMOUT. IDIXIPV issues message IDI0113W for all errors, including this trivial problem. IDIXIPV has been changed to suppress IDI0113W in the RTIMOUT situation. PM63998
4 Abend S0C4 when using Fault Analyzer to analyze a Recovery Fault Recording (RFR) dump. The RFR conditions might set an environment where a Fault Analyzer internal buffer is exceeded, causing an overlay and abend S0C4 in Fault Analyzer. The buffer pointer position has been correctly set when the RFR input only had the invocation exit buffer. PM63990
5 CICS IVP test 4 from CFA transaction not selectable when using Rumba terminal emulator. The attribute used on the panel was acceptable by IBM PCOMMS but not with Rumba. The attribute has been changed to allow correct operation on both emulators. PM63999
6 Fault Analyzer IDI* messages might be written to a HFS file if stderr not correctly set to FD2. If a job is using HFS files but not running under a Shell (such as BPXBATCH) or OMVS, then the Unix File Descriptor 2 might not have been set to stderr and WTO messages meant for stderr might be written to an incorrect HFS file. If Unix dubbed and the LE stderr(MSGFILE) file pointer does not have FD2 assigned, then the write of IDI* messages will not be directed to FD2 stderr. PM63992
7 Fault Analyzer abend S0C4 in BldLX when processing Enterprise PL/I abend which had the GONUMBER(SEP) compiler option in effect. Incorrect fixup and processing of multiple sections in statement number table. Fixup and processing of multiple sections in statement number table corrected. PM64000
APAR PM54423 Fixes and Enhancements
Problem
Description
Fix
Complete APAR information
1 The user has specified EXCLUDE for a dumpcode. FA is excluding FA processing, but CICS goes on to take a transaction dump. The customer does not want this. Fault Analyzer is not passing the result of EXCLUDE processing to CICS. Fault Analyzer has been changed so that EXCLUDE processing will pass UERCBYP (bypass this transaction dump) if the abend code is excluded. PM59057
2 Fault Analyzer ISPF interface does not check product ENABLE/DISABLE status in IFAPRDxx. The check to see if Fault Analyzer had been disabled in IFAPRDxx had only been made for real-time analysis. The ISPF interface now checks IFAPRDxx. PM59063
3 Message IDI0144E Fault Analyzer IDIS subsystem error when //CEEOPT DD with HEAPPOOLS(ON) is used. The cross memory call to the IDIS subsystem will fail with message IDI0144E if HEAPPOOLS(ON) is set. The HEAPPOOLS(OFF) option is now set in the start of IDIDA. PM57765
4 IDIMAPS data set not found during CICS start up. Configuration module IDICNFUM was not being used correctly during Fault Analyzer's CICS startup processing. IDICNFUM is now being used correctly. PM59059
APAR PM47920 Fixes and Enhancements
Problem
Description
Fix
Complete APAR information
1 "Invalid command" message received from ISPF interface when using MATCH command for numerical column and specifying a value which includes a percent sign. Support for percent sign (%) in MATCH command values was not supported for columns containing numerical data, although the documentation indicated that this should be valid. Support for percent signs in numerical column MATCH command values has been added as per the current documentation. PM46859
2 IDI0145I IDIS subtask IDISCJST terminated ECB=400C4000 and IDI0144E IDIS IDISAMAN:990 Unexpected condition. The Fault Analyzer IDIS subsystem may have intermittent failure producing IDISCJST and IDISAMAN ECB=400C4000 and termination. Correct unchaining of the Queue element under task termination has been added. PM53173
3 IBM Fault Analyzer not using the EPIE in a U4036 abend to report the original problem. Under some conditions, the EPIE address from R2 for a U4036 abend is not used to report the initial abend. The code has been updated. PM49311
4 Abend S0C4 during CICS system dump analysis. An invalid stack entry was being processed. Invalid stack entries are now ignored. PM53174
5 During transaction DUMP analysis, Fault Analyzer abends with ATCV and CICS terminates with DFHPC0409. Fault Analyzer is not reacting to a TERMERR condition and is continuing to use the terminal. Fault Analyzer has been changed to detect the TERMERR condition and prevent further use of Terminal Control. PM52599
6 Fault Analyzer IDI0131W Waiting for History File SPFEDIT ENQ messages from the IDIS subsystem. IDI0131W ENQ contention followed by IDI0130E time-out problems might occur in the IDIS subsystems in a sysplex. ENQ timing window error corrected. PM53166
7 Listing exit not called when COBOL program is compiled with TEST(NOSEP). Listing exit not called for PROGSUM compiler listings. Listing exit now called for PROGSUM compiler listings. PM53175
8 Incorrect program name for PL/I procedures included from package. Packaged procedure used to form mangled CSECT name is not known. Code to determine which procedure was used to name the CSECT added. This code requires that a procedure with the same name as the package is available. PM53176
9 PL/I decimal floating point (DFP) variables show incorrect values. FA does not support PL/I DFP variables. Support for PL/I DFP variables has been added. PM53177
10 PL/I SYSDEBUG file not used. CUI fixup table not in minidump when DEFERREDREPORT option is in effect. Code to locate CUI fixup pages in minidump added. PM53178
11 Message IEC036I abend S002-18. A fault entry record used for saving a DB2 SQLDA data area exceeded the maximum logical record length of 10000 bytes. The DB2 SQLDA data area is now saved across multiple records if necessary. PM50898
12 Enterprise PL/I does not report defined structure types or anonymous unions. Defined structure types or anonymous unions were not supported. Support has been added for defined structure types and anonymous unions. PM53179
13 RESET or MATCH ALL from Fault Entry List display does not always result in the original list being shown. The Fault Entry List display was reformatted using the current array of fault entry information, which might have been modified due to sorting or matching. The current array of fault entry information is now being rebuilt from the last obtained history file cache. PM53180
14 ICH408I messages for JESSPOOL when using Fault Analyzer IVP interface under CICS. Unintentional use of fflush function which under IPV was causing the JESSPOOL SAF check. The fflush usage has been corrected. PM53181
15 When a program terminates with an SQLCODE=-805, the wrong DB2 package information is shown. When a DBRM is contained in many packages, and an attempt is made to display the package information, then the wrong information is being shown. Fixed the call for package information to only show packages that are bound to the associated plan. PM53163
16 IDISF8130S File not found "SYSLOGIC *" when calling IDILANGX with PARM= *PL( When the EXEC PGM=IDILANGX PARM= has a program name ending with PL, and is immediately followed by an opening bracket, then the error will occur. A space prior to the bracket will circumvent the problem. Misinterpretation of the "*PL(" sequence for PermitLangx option has been corrected. PM53182
17 Message IDI0092S and RFR dump after a loop in Fault Analyzer. Under CICS and Debug Tool, a S0C4 abend and loop is possible with a CIB pointing to itself, causing IDI0092S Fault Analyzer time-out. The code now detects the potential CIB loop at this point of execution. PM53857
APAR PM44694 Fixes and Enhancements
Problem
Description
Fix
Complete APAR information
1 Fault analyzer incorrectly reports COBOL compiler options TRUNC and CICS. Incorrect bit interpretation for TRUNC sub-options. CICS option cannot be reported without a compiler listing having been provided since info byte flag is not set. TRUNC sub-options corrected. Reporting of CICS option removed unless compiler listing has been provided for source level support. PM45593
2 PL/I overflow exceptions do not occur after call to IDISNAP. The PSW program mask was not saved and restored across the IDISNAP call. The PSW program mask is now saved and restored across the IDISNAP call. PM46051
3 Poor CICS abend analysis performance. Large number of loaded CICS programs was causing performance problems when analysing. Internal processing of large number of loaded programs has been enhanced to reduce performance overheads. PM46052
4 User "steps" through program with CEDF and issues PF12 (abend), User gets EXEC CICS ADDRESS ACEE screen from Fault Analyzer, which affects further abend processing. Fault Analyzer's EXEC CICS ADDRESS ACEE command does not set the NOEDF bit to suppress EDF processing Fault Analyzer has been changed to set the NOEDF bit on its EXEC CICS ADDRESS ACEE command. PM47172
APAR PM42268 Fixes and Enhancements
Problem
Description
Fix
Complete APAR information
1 Format XML data option not always displayed correctly in interactive reanalysis. The detection mechanism of formatable XML data was not correctly allowing for ASCII data. ASCII data is now correctly accounted for. PM44252
2 IDI0047S exception in getVarStg1. Invalid storage was not being correctly allowed for. Storage check has now been inserted. PM44253
3 Plug-in user cannot authenticate when adding new history file. Plug-in uppercases passwords before authentication, which causes problems with RACF mixed-case password policies. Plug-in leaves the password alone and sends it as is. PM44246
4 Abend when processing multi-line COBOL statements that reference table elements. Source parse buffer too small. Source parse buffer size corrected. PM44254
5 FA incorrectly reports COBOL storage as not accessible. DCB in Working-Storage causes FA to 'trim' base locator storage. ACB/DCBs located in COBOL storage areas no longer affect base locator storage lengths. PM44255
6 Fault Analyzer IDIS subsystem high CPU usage. The IDIS subsystem can start using high amounts of CPU after an XCF slowdown. The code has been updated to recognise the problem and correct it. PM44256
APAR PM34296 Fixes and Enhancements
Problem
Description
Fix
Complete APAR information
1 Listing prompt not issued when compiler listing not found for COBOL program compiled with TEST(NOSEP). Listing prompt not issued for TEST(NOSEP). Listing prompt now issued when compiler listing not found for COBOL programs compiled with TEST(NOSEP). PM41016
2 Abend S0C4 in PliSepRec4 when PL/I SYSDEBUG side file source has include files. %INCLUDE statement has unexpected record length. Variable length source records now supported. PM34271
3 Abend S0C9 from entry point displayISPF when analyzing CICS SDUMP. Incorrect detection of CICS SDUMP was causing inappropriate code to be called. CICS SDUMP is now detected correctly. PM40245
4 Abend S0C4 in PliSepRec4 when PL/I SYSDEBUG side file source has include files. %INCLUDE statement has unexpected record length. Variable length source records now supported. PM34271
5 Unable to apply action to user note on User Note List display if one or more notes are against 64-bit addresses. The address field is picked up from the display incorrectly. The address field is now picked up from the display correctly. PM41017
6 Getting IDI0005S message indicating "lack of storage". The problem is caused by a recursive loop in the CICS Name Token Entry Chain. 1. Limit the number of entries in the CICS "Name Token Entry Chain" that are displayed (1000 entries). 2. Report how many entries have been shown. 3. Raise a "Severity 2 Observation" to indicate the possibility of a loop. PM35360
7 Message "IDI0089I Subsystem IDISFPEX RC=4 (or RC=92), Rsn=7FFFFFFF . . .*" (non-printable characters appended) issued incorrectly. The message was incorrectly being passed back from a call to the IDIS subsystem. The message has been suppressed. PM35904
8 Abend S0C4 when Fault Analyzer attempts to process an invalid compiler listing from the 'Compiler Listing Not Found' pop-up. Code assumed compiler listing had been successfully processed into IDILANGX. Code checks IDILANGX format is valid. PM35887
9 DWARF/MDBG data set name not passed to EQAUEDAT for C/C++ programs. Data set name not passed to EQAUEDAT. DWARF/MDBG data set or path name now passed to EQAUEDAT. PM41018
10 Loop issuing message IDI0005S and finally running out of space with abend S878. The attempt to log message IDI0005S required additional storage, which in turn re-invoked the same code to issue message IDI0005S. Additional storage has been made available for the logging of the initial IDI0005S message. PM36413
11 Previous MATCH not reset when selecting View from View List display. An implicit reset of all MATCH values was missing. An implicit reset of all MATCH values has been added. PM41245
12 Hex-dumped storage not shown in batch report for inactive COBOL programs when PrintInactiveCOBOL option in effect. Incorrect condition for registering hex-dumped storage. Condition corrected. PM38414
13 Incorrect ENV data area layout. Supplied sample mappings for Assembler, COBOL, C and PL/I of the ENV data area were incorrect from the POF_LOADED_FROM field at offset X'204' and onwards. The ENV data area has been changed to match the documented layout and sample mapping members. PM41246
14 Abend S0C4 in function pp_sm_task_sca during interactive analysis of CICS SDUMP. A 'null' value for a storage management control block was not being allowed for. Check added for 'null' pointer. PM41247
15 Some user exit character format data area fields contain binary zeroes. Trailing binary zeroes in user exit character format data area fields had not been removed. Trailing binary zeroes in user exit character format data area fields have been removed. PM41248
16 Loop in Fault Analyzer IDIS subsystem. The Fault Analyzer IDIS subsystem might loop in CSECT IDISXCFA after XCF error recovery. Code added to detect and prevent the condition. PM41249
17 Abend S0C4 in IDILANGX when processing HLASM SYSADATA. The HLASM SYSADATA from a PLX compilation might cause a S0C4 in IDILANGX entry name RESOLVE_USING_INFO. Code has been added to detect a zero CSECT ID error. PM39420
APAR PM34390 Fixes and Enhancements
Problem
Description
Fix
Complete APAR information
1 Updates to Japanese feature translations. n/a n/a PM34390
APAR PM34391 Fixes and Enhancements
Problem
Description
Fix
Complete APAR information
1 Updates to Korean feature translations. n/a n/a PM34391
APAR PM27330 Fixes and Enhancements
Problem
Description
Fix
Complete APAR information
1 CICS transaction waits indefinitely for Fault Analyzer processing. The potential existed for two Fault Analyzer tasks to wait on the same ECB, and hence only one would be posted out of the wait. The dual ECB usage has been modified. PM33412
2 Message IDI0063W deletion of fault entry failed when using the V line command to generate a saved report and XFACILIT access is UPDATE. A check for XFACILIT ALTER access was incorrectly being made. The check for XFACILIT ALTER access has been eliminated as part of the fault entry refresh processing. PM33413
3 IDI0011S abend U4093 (X'FFD') reason code X'90' when calling IDISNAP. Fault Analyzer was being invoked in a POSIX(ON) LE environment. POSIX(OFF) has been added to the Fault Analyzer invocation. PM33414
4 Abend S0C4 when processing truncated COBOL SYSDEBUG side file. Freed storage pointers not reset causing subsequent free to abend S0C4. Freed storage pointers now reset. PM33415
5 Abend S0C2 in module IDIXCEE entry point JOBINFO at offset X'476'. In a Websphere Application Server Control Region running storage protect KEY 2, if IBM Fault Analyzer has not been excluded from the region and an abend occurs causing Fault Analyzer to be called, it will get S0C2 trying to set KEY 8 execution mode from i Code has been added to detect the call in KEY 2 and abort the analysis with message IDI0123S. PM33401
6 CFA transaction cannot be executed during CICS shutdown due to SHUTDOWN(DISABLE) setting. CICS default setting for SHUTDOWN status was being used. SHUTDOWN(ENABLED) has been added to the CFA transaction definition. PM28357
7 Fault Analyzer receives abend AZTS while processing application abend AD2W. Fault Analyzer is attempting to capture the 3270 terminal buffer, but the MRO connection is no longer active, so Fault Analyzer suffers a Terminal Control abend. Fault Analyzer has been changed to suppress the 3270 buffer capture if the CICS connection has suffered an AD2W abend. PM33416
8 Source line not reported when using ISPF packed Enterprise PL/I compiler listing. The 'back-end' sections of an EPLI compiler listing require right-shifting since the ASA character '1' is not present. The right-shifting is not performed when using an ISPF-packed compiler listing. The right-shifting is now performed when using an ISPF-packed EPLI compiler listing. PM33417
9 Abend S0C4 at entry point FormatXMLData offset X'4CE'. The buffer was too small to handle large amounts of XML data. Made buffer large enough to handle large XML data. PM33592
APAR PM21096 Fixes and Enhancements
Problem
Description
Fix
Complete APAR information
1 Message CEE3204S abend 0C4 protection exception running IDILANGX if using SYSADATA input from a HLASM step that did not complete with return code zero. When the SYSADATA output from assembler (HLASM), that did not get a clean return code because of "USING" statement errors, is used as input to IDILANGX, then an abend 0C4 may occur at label Resolve_Using_Info +340. An additional check for SYSADATA input validity has been added. PM26147
2 Panel 'IDIPDIRL' error. Invalid .CSRPOS or .CSRROW value found while processing panel. The cursor position following a scroll operation was incorrect. The cursor position has been corrected. PM21303
3 Insufficient access error message when attempting to use a history file which is in HSM migrated state. No consideration was given to history files in HSM migrated state when determining the existence of the data set and the user's access authorization level. HSM migrated history files are now handled correctly. PM21816
4 The wrong COLLID (Collection ID) is being shown against a DB2 PLAN. The offending DB2 call returned multiple rows in an unpredictable sequence. The DB2 call will be modified to return a single row with the correct COLLID. PM26148
5 Message IDI0005S storage allocation failure in IDIEDSA. The abending CICS task had an excessive number of TACBs, each of which was being processed by FA. This eventually led to a shortage of storage. Excessive TACBs are detected and the user is warned accordingly in the report synopsis. PM26149
6 Non-history file PDSE data set specified on the Fault Entry List display gets corrupted. The specified PDSE data set is assumed to be a valid history file. A check of the data set attributes has been added. PM26154
7 Wrong source line reported when using SYSDEBUG side file for optimized COBOL program. Multiple non-contiguous offsets for a given line are not handled. Multiple non-contiguous offsets are now handled. PM26156
8 Abend S0C4 when analyzing a CICS system dump. Fault Analyzer is not checking for a zero address. The address in question is now checked for a zero value before being used. PM26052
9 Abend S0C4 in Fault Analyzer IDIS subsystem during start-up when IDIVIEWS data set has large LRECL and is FB. Incorrect buffer size was being used for read operation. The buffer size has been corrected. PM26053
10 Abend S0C4 in CheckLangX() when GDG base data set specified in DATASETS option for IDILANGX. The GDG base data set is processed as the side file and might be recognized as a valid IDILANGX file, which subsequently results in a S0C4. When a GDG base data set is specified as a side file using the DATASETS option, then the generation data sets are now processed instead of the base data set. PM24007
11 FA plug-in not refreshing last history files referenced. FA plug-in not connecting to the FA server. FA plug-in changed to connect to the FA server every time the option is requested. PM24531
12 Message IRX0250E system abend code 0C4, reason code 00000004. A REXX ESTAE intercepted an S0C4 abend which occurred during the processing of a Formatting user exit EVALUATE command. The EVALUATE command processing has been protected by a Fault Analyzer ESTAE. PM26066
13 Abend S0C4 in Fault Analyzer CICS LE invocation exit, IDIXCCEE. Storage overlay and subsequent abend S0C4 in Fault Analyzer IDIXCCEE after VSMLIST returns a buffer containing a block count of zero. The logic is updated to detect and handle the block count of zero. PM26163
14 Abend S0C4 when attempting to show the SAA of the running task in a CICS system dump. A string field was too short, causing corruption of following fields. The size of the string field has been increased. PM25308
15 IDI0034I analysis skipped when '*' is specified as EXCLUDE option value for a suboption which is not applicable to the current fault. A value for a non-applicable suboption was being tested and found to match. Non-applicable suboptions are no longer tested for matching INCLUDE/EXCLUDE option values. PM25988
16 Abend S0C1 at entry point VSAMPT following message IDI0006E open error. A VSAM POINT macro was executed without first checking for successful OPEN of the VSAM data set. A check for successful OPEN has been added. PM26810
17 Abend S0C4 at entry point cob_file_error when processing COBOL abend. Storage containing the FCB number was not available, but processing continued. File not processed by cob_file_error if FCB number not available (file might still be reported in system-wide section). PM26817
18 Abend S0C4 when using Compiler Listing Read user exit with LST data area field DATA_BUFFER_DSN = 'Y'. The Compiler Listing Read user exit performs extraneous IDIWRITE of listing data set name to a temporary data set, even though LST data area field DATA_BUFFER_DSN = 'Y'. This might result in an S0C4 abend. LST data area field DATA_BUFFER_DSN = 'Y' is now checked and the "one record at a time" code is not executed. PM26925
19 Abend S0C4 in CheckLangx() when IDILANGX file does not contain a CSECT name record. CheckLangx() does not test pointer to CSECT name record, which will be invalid if no CSECT name record was read from the data set. The CSECT name record is mandatory. The side file will be rejected and message IDI0095W issued. PM26806
20 IDI0011S abend U4093 (X'FFD') reason code X'90' when Fault Analyzer is invoked though IDIXDCAP or IDIXCEE with POSIX(ON). Fault Analyzer was being invoked in a POSIX(ON) LE environment. POSIX(OFF) has been added to the Fault Analyzer invocation. PM27991
APAR PM14420 Fixes and Enhancements
Problem
Description
Fix
Complete APAR information
1 PL/I in-register variables are reported with incorrect values. There is no storage location for in-register variables but the compiler listing reports their location as r13 + 0, which is invalid. In-register variable values are no longer reported and a note identifying them now appears alongside the declaration. PM14672
2 Fault Analyzer terminated with abend S0C7 whilst analyzing a CICS system dump. Fault Analyzer was unable to determine the appropriate version of CICS that was running, so a default was assumed. The offsets of the fields in the SIT were incorrect, causing the formatting of the first DECIMAL field to terminate with abend S0C7. The syntax of DECIMAL fields will be interrogated before they are formatted for display. In the event of an error, the message "Not valid packed decimal" will be shown. PM15920
3 Fault Analyzer CICS trace table display might be truncated. The trace entries towards the end of a large CICS trace table in a CICS system dump analysis might be missing. The logic is changed to correctly read the additional trace entries from the MVS dump data set. PM19823
4 IDILANGX gives RC=310 when processing C/C++ compiler listing. When IDILANGX processes page headings, it expects a space between the compiler version info and the source data set name. This might not be the case when a long source data set name is used. The requirement for space between compiler version info and source data set name has been relaxed. PM17201
5 V (or S) line command incorrectly results in "No report or dump" message when a minidump or associated MVS dump is available. A saved report was implicitly generated, but could not be saved (and subsequently displayed) because of insufficient access authority to the fault entry. A different message is issued, explaining the reason for not displaying the saved report. PM19825
6 EDC6006E The raise() function was issued for SIGABRT from entry point getPrevDSAnEP. Messages IDI0047S and IDI0126I issued. Function getPrevDSAnEP at statement 7628 issues raise SIGABRT if a backchain pointer has -1 as the address. DSA validity check logic is changed to not cause the abend. PM17250
7 Message ICH408I and IDI0078E when using the "V" line command against a fault entry with no saved report and to which no UPDATE access is available. The saved report was attempted written although only READ access to the fault entry was available. Checking for UPDATE access prior to writing the saved report has been added. PM19827
8 Incorrect event displayed when selecting with cursor on event number from Event Summary display after scroll down and with help text enabled. The collapsed help text was not being accounted for correctly when determining the offset of the point-and-shoot field into the ISPF panel dynamic area. The collapsed help text is now being correctly accounted for. PM19316
9 Abend S0C4 in load module DSNALI offset X'382'. The DB2 CLI/ODBC SQLAllocConnect function was used with the current PSW storage protection key set to 8, while the job step TCB storage protection key was 7. A check has been added to skip DB2 CLI/ODBC usage if the job step TCB storage protection key is not 8. PM19570
10 IDI0095W Unexpected condition found in IDICUSUB:2192: IDICUSUB:2133 HDrealloc HD ERROR message. When sharing a history file with a much older level of Fault Analyzer (two years), error messages IDI0095W and IDI0144E might be issued from the IDIS subsystem. Code added to improve compatibility. PM19729
11 When performing fault entry refresh from RD/z or Eclipse client, a batch reanalysis report is written to SYSPRINT on the host server system. The refresh processing is performed through a fault entry batch reanalysis job on the host system, which normally writes a report to stdout (SYSPRINT). The host system batch reanalysis report has been suppressed when performing fault entry refresh processing from an RDz or Eclipse client. PM19864
12 Message IDI0144E from Fault Analyzer with S33E abend when CICS CEMT SHUT IMM issued. If Fault Analyzer is doing an abend analysis in CICS when CEMT PER SHUT IMM is issued, then a IDIS subsystem IDI0144E message for an S33E abend might occur. Code changed to not issue message IDI00144 if an abend S33E occurs in the IDIS subsystem xmem code during termination. PM19803
13 Abend SD23 during real-time analysis when the Fault Analyzer IDIS subsystem is not active. Incorrect WTO parameter list for message IDI0151W. The message IDI0151W parameter list has been corrected. PM20010
14 Abend S0C4 in PrtCobStg() when COBOL integrated translator compiler listing used as side file. Symbols generated by the translator do not have source declarations, resulting in zero length. This causes an S0C4 abend when attempting to report such symbols. Generated symbols are now assigned correct length and processed without requiring a source declaration. PM19925
15 Fault Analyzer loops when formatting large COBOL multi-dimension tables. Incorrect handling of table elements across unreferenced storage pages. Handling of table elements across unreferenced storage pages corrected. PM20666
APAR PM11905 Fixes and Enhancements
Problem
Description
Fix
Complete APAR information
1 Message IDI0005S after repeated refresh of the Fault Entry List display. Storage was allocated for the refresh, but never free'd. The storage leak has been fixed. PM13685
2 IDI0014E MTRACE error calling IEEMB879 for buffer accumulation, rc=C Uninitialized storage was causing an error in IEEMB879. The storage is now correctly initialized. PM13683
3 Side file is not used when processing SYSMDUMP containing Enterprise PL/I event. Binder API services might not be available when processing a SYSMDUMP. If not, CSECT information will be missing and is not synthesized for Enterprise PL/I. CSECT information now synthesized for Enterprise PL/I. PM13687
4 Fault Entry List display MATCH CSR command not matching on the correct value if the display is not at the top and help text is enabled. The collapsed help text was not being accounted for correctly. The collapsed help text is now being accounted for correctly. PM13386
5 A blank saved report is displayed when the "V" line command is used from the Fault Entry List display. The history file cache indicated the presence of a saved report, when in fact no saved report existed in the fault entry. If the saved report is missing, then it will be re-generated when the "V" line command is used. PM13694
6 Fault Analyzer not invoked for CICS abend on L9 TCB. Code was being executed which was not appropriate when running on a L9 TCB. L9 TCB abend processing has been modified to allow successful analysis. PM13894
7 Abend S0C4 in fxclose() when PROGRAM_NAME passed to listing exit contains invalid member name characters. Invalid member name caused file open and susbsequent close to fail. Valid member name characters used. PM13887
APAR PM08932 Fixes and Enhancements
Problem
Description
Fix
Complete APAR information
1 Abend S0C4 in EXTRACT_COBOL_MAP when IDILANGX processes COBOL listing with NUM compiler option in effect. 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. MAP section line number increased to 6 digits. PM09208
2 IS domain not selectable from CICS trace selection panel. Omitted IS domain added to valid list of domains PM09480
3 Message ICH409I 282-020 ABEND DURING RACHECK PROCESSING when entering a non-existing history file name from the Fault Entry List display. RACHECK processing was called for a non-existing history file name. The existence of the history file is determined prior to calling RACHECK processing. PM09443
4 Fault Analyzer only reports COBOL source lines preceding a comment when a multi-line statement has comments interspersed. Incorrect offset assigned to comment. Correct offset now assigned to comment. PM10154
5 Loop during CICS SDUMP analysis. A corrupt CICS control block was causing Fault Analyzer to loop when chaining through the control blocks. A validity check is now made on the control block pointers to prevent the loop. PM11513
6 Dump processing waiting on ENQ of SYSIDIDA minor SYSOUT from module IDIXDCAP. 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. The processing of concurrent abends from the IDIXDCAP exit within an address space has been changed to not wait on the ENQ. PM11410
APAR PM03974 Fixes and Enhancements
Problem
Description
Fix
Complete APAR information
1 Scroll activity in CICS system dump analysis report table displays might reset column attributes if help text is enabled. The display was reformatted in order to suppress help text above the table heading, resulting in the loss of any column attribute settings. The displays no longer require reformatting in order to suppress help text above a table heading. PM05169
2 Message IDI0063W deletion of fault entry failed due to insufficient access authority received when updating user data via the '?' line command. A check was incorrectly being made for ALTER access to the fault entry, when UPDATE access should have been sufficient. The access authorization check has been changed from ALTER access to UPDATE access. PM07720
3 Fault Analyzer calls EQAUEDAT with language code 10 for Enterprise PL/I when it should be 11. Incorrect language code passed to EQAUEDAT for Enterprise PL/I. Language code 11 now passed to EQAUEDAT for Enterprise PL/I. PM06477
4 IDI0050S Fault reanalysis attempted without FAULTID or DUMPDSN option specified. This is happening when analyzing the first fault entry in a newly allocated history file. The initial fault ID assigned in an empty history file that was allocated using the option "File->7. New Fault History File Allocation..." from the Fault Analyzer ISPF interface, was <prefix>00000. This is not a valid fault entry number. The first fault entry in an empty history file has been changed to <prefix>00001. PM07465
5 Corrupted "Column Attributes" display when using Fault Analyzer interactive under CICS. The initial Column Attributes display was corrupted due to the lack of stack-buffer-command support. An alternative method has been implemented. PM07707
6 Incorrect assembler CSECT address used with associated storage areas formatting. The same CSECT name existed in multiple load modules and the wrong one was used. A check has been added to ensure that the correct CSECT address is being used. PM08038
7 ICH408I RACF security violation when attempting to open "./IDIZZDBG". An incorrect return code was set when querying the existence of an environment variable which is used for debugging purposes only. The setting of the return code has been corrected. PM08053
8 Abend S0C4 in PliSepArray when processing Enterprise PL/I SYSDEBUG side file that contains UNAL CONTROLLED structure with multi-dimension arrays. Invalid structure/array descriptor encountered. Code now handles invalid descriptors.Code now handles invalid descriptors. PM06413
APAR PM02649 Fixes and Enhancements
Problem
Description
Fix
Complete APAR information
1 Fault Analyzer V10.1 User's Guide and Reference Japanese translation. n/a n/a PM34390
APAR PM02650 Fixes and Enhancements
Problem
Description
Fix
Complete APAR information
1 Fault Analyzer V10.1 User's Guide and Reference Korean translation. n/a n/a PM34390
APAR PM00092 Fixes and Enhancements
Problem
Description
Fix
Complete APAR information
1 IDI0128I RFR DUMP data set not deleted. Failure of RFR TDUMP deletion when the user has standard READ access but the ALTER access is only via the XFACILIT profile. The logic is corrected to correctly test the XFACILIT access when there is also access via the DSN profile. PM03538
2 Abend S0C4 at entry point getLocalPCBs statement 1656 offset X'3710'. If real-time, then message IDI0047S might also be issued. Invalid storage was being referenced. The correct storage address is now being used. PM03532
3 With Fault Analyzer CICS dump screening active, the CICS DFHDU0202 message always reported dump successful, even when a dump was not taken. A zero value was always passed back in register 15 to CICS. The correct register 15 value is now passed back. PM03535
4 Abend S0C4 after Fault Analyzer begins analysis, but suffers timeout. The symtom string reports abend S0C4 in DFP module IGWLHHLS, but the PSW points to an MVC instruction after label IDIXALOG in load module IDIDA+16E248. The STIMERM exit code has been fixed to correctly reload R3. PM03544
5 Message ICH408I and IEC150I abend S913-38 when using the X (XMIT) line command against a fault entry in a history file which is XFACILIT protected. The TSO XMIT was issued against the history file member, but there was no READ access to the history file data set outside of Fault Analyzer. When the history file fault entry is protected using the XFACILIT resource class, then the fault entry is copied to a temporary data set, which is subsequently used for the TSO XMIT. PM03552
6 Abend S878 with storage full of STKU LE heap storage from Fault Analyzer, when an application overlays free storage elements. An inital overlay of free storage elements, creating a chaining loop, was not detected by Fault Analyzer, causing recursive processing and storage depletion. Additional loop detection has been added to prevent the recursion. PM03547
7 Abend S0C4 in SetStride() when processing PL/I dynamic array using compiler listing. PL/I dynamic arrays are not supported by IDILANGX. Support added to Fault Analyzer for PL/I dynamic arrays. PM03551
8 Interactive reanalysis loop in the Dump Storage display when scrolling up. The ending address when scrolling up was calculated incorrectly. The ending address is now being calculated correctly. PM03554
9 IDILANGX return code 310 when processing Enterprise COBOL 4.2 compiler listing. Enterprise COBOL 4.2 compiler listings are not supported by IDILANGX. Support added for Enterprise COBOL 4.2 compiler listings. PM03558
10 Unable to allocate Recovery Fault Recording (RFR) data set under ACF2 when the data set name is less than 44 characters. A X'00' null-terminator was inserted after the data set name that is used as input to the RACROUTE service. The X'00' null-terminator has been replaced by a blank. PM03561
11 Abend S0C4 in ShiftSubs() when processing PL/I event. Subscript normalization occurred for an array passed as a parameter. Subscript normalization suppressed for parameter arrays. PM03565
12 Compiler Listing Read user exit fails to process SYSDEBUG side files. Compiler Listing Read user exit does not support SYSDEBUG side files. Support added for COBOL and PL/I SYSDEBUG side files. PM03573
13 Fault Analyzer loops when processing a COBOL abend in performed code in an optimized program. Perform traceback does not quit when a PVN cell points to a source line that does not contain a PERFORM statement. Perform traceback now quits if PVN cells do not point to a PERFORM statement. PM03566
14 Message IDI0047S abend S0C4 at entry point keyxadd offset X'2BE6'. A control block was being processed without ensuring that the control block address was valid. Validation of the control block has been added. PM03569
15 Incorrect PL/I V2R3 ONCODE point-of-failure event shown in report when there is a later COBOL The later COBOL abend is reflected in the library workspace for the calling PL/I V2R3 program, and then reported on as a separate error. PL/I ONCODE information is suppressed in the report for an LE application abend, when a user code LE CIB has already been reported on. PM03577
16 Abend S0C4 in IDITR640 when formatting CICS EXCI trace entry. An invalid trace entry was being passed to the trace formatting routine, which then caused the S0C4 abend. The trace entry is now validated prior to calling the formatting routine. PM03579
17 Abend S0C4 in IDILANGX when processing assembler SYSADATA USING statement. A halfword parameter was passed to the PUT_STRING routine, when it should have been a fullword. A fullword parameter is now being passed to PUT_STRING routine. PM03586
18 Message IDI0108I issued from the IDIS subsystem if a PDSE history file is accessed via an ALIAS name. The Fault Analyzer IDIS subsystem can issue message IDI0108I, saying that a history file is not a PDSE, if it is being accessed using an ALIAS name. The code to detect ALIAS data set names has been changed to correct the problem. PM03582



How to determine your current Fault Analyzer service level

To check your current Fault Analyzer service level, select About Fault Analyzer from the Help menu. Information similar to the following is displayed, indicating the current PTF level:


Copyright and General Usage Information


IBM Fault Analyzer for z/OS V11R1M0 (UK62719 2010/12/07)


Licensed materials - Property of IBM(*) 5655-W46


(C) Copyright IBM Corp. 2000, 2010.  All rights reserved.


US government users restricted rights - use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.


Materials displayed or reproduced by this program may be protected by copyright or contract restrictions of IBM and/or others.  The user is responsible for having permission to display or reproduce such materials and for including applicable copyright notices and legends.


If any IBM machine-readable documentation is accessed or reproduced by or through this program, IBM grants limited permission to licensees of the IBM machine-readable documentation to make hardcopy or other reproductions

  • IBM is a registered trademark of International Business Machines Corporation.

*** Bottom of data.

Related information

Order Service

Rate this page:

(0 users)Average rating

Add comments

Document information


More support for:

Fault Analyzer for z/OS

Software version:

10.1, 11.1, 12.1, 13.1

Operating system(s):

z/OS

Reference #:

1171963

Modified date:

2013-12-06

Translate my page

Machine Translation

Content navigation