IBM Support

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

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

English Base Component
Japanese Feature
Korean Feature
PTF Download links
UI39095 Download PTF UI39095
UI37893 Download PTF UI37893
UI35734 Download PTF UI35734
UI33673 Download PTF UI33673
UI32440 Download PTF UI32440
UI31227 Download PTF UI31227
UI30209 Download PTF UI30209
UI30212 Download PTF UI30212
UI29962 Download PTF UI29962
UI27593 Download PTF UI27593
UI27380 Download PTF UI27380
UI25080 Download PTF UI25080
UI23573 Download PTF UI23573
UI22346 Download PTF UI22346
UI20632 Download PTF UI20632
UI18641 Download PTF UI18641
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:
UI39095
6 Jul 2016 UI33673
UI35734
UI37893
PI62332
PI62407
PI62668
PI62767
PI64233
PI65152
PI65158
English:
UI37893
2 Jun 2016 UI33673
UI35734
PI56847
PI57103
PI58357
PI58441
PI59807
PI60166
PI60246
PI60372
PI60431
PI61430
PI62509
PI62510
English:
UI35734
3 Mar 2016 UI33673 PI52923
PI54261
PI55016
PI55028
PI55148
PI55196
PI55740
PI56547
PI56722
PI57921
English:
UI33673
12 Dec 2015 UI12445
UI13465
UI14757
UI17255
UI18641
UI20632
UI22346
UI23573
UI25080
PI51864
PI52322
PI53064
PI53175
PI53177
PI53871
PI53877
PI53878
PI53879
English:
UI32440
3 Nov 2015 UI31227 PI48923
PI50355
PI51358
PI51368
English:
UI31227
2 Oct 2015 UI12445
UI13465
UI14757
UI17255
UI18641
UI20632
UI22346
UI23573
UI25080
UI27380
UI27593
UI29962
PI45773
PI46839
PI47149
PI48914
PI48915
Japanese:
UI30209
18 Aug 2015 UI29962 PI40802
Korean:
UI30212
18 Aug 2015 UI29962 PI40802
English:
UI29962
18 Aug 2015 UI14757
UI17255
UI18641
UI20632
UI22346
UI23573
UI25080
UI27380
UI27593 PI27960
PI40802
PI42010
PI42147
PI43086
PI43225
PI44013
PI44727
PI45212
PI45886
PI46107
PI46108
PI46112
PI46113
PI46114
PI46115
PI46116
English:
UI27593
1 Jun 2015 UI27380 PI39682
English:
UI27380
12 May 2015 UI14757
UI18641
UI20632
UI22346
UI23573
UI25080
PI34600
PI34649
PI35015
PI35276
PI35460
PI35786
PI36160
PI36221
PI36261
PI36590
PI37268
PI37632
PI38972
PI39108
PI39109
PI39110
PI39543
PI40499
PI40500
PI40501
English:
UI25080
3 Mar 2015 UI14757
UI20632
UI22346
UI23573
PI31258
PI31281
PI31383
PI32066
PI32260
PI33502
PI34754
PI34756
PI34757
PI34758
PI34759
PI34760
English:
UI23573
8 Dec 2014 UI14757
UI18641
UI20632
UI22346
PI28040
PI28247
PI28281
PI28783
PI28912
PI29334
PI29899
PI30031
PI30505
PI30647
PI30649
PI30650
English:
UI22346
24 Oct 2014 UI14757
UI20632
PI24419
PI24512
PI27868
PI27956
PI27957
PI27958
PI27959
PI27960
PI27961
PI27962
PI27963
PI27964
PI27965
English:
UI20632
3 Sep 2014 UI14757
UI17255
UI18641
PI19883
PI21123
PI21479
PI22236
PI23407
PI23641
PI23642
PI23643
PI23644
PI23645
PI23646
PI23647
PI23869
English:
UI18641
1 Jul 2014 UI14757
UI17255
PI17012
PI17309
PI17905
PI18319
PI18440
PI19156
PI19157
PI19158
PI19159
PI19160
PI19161
PI19162
PI19163
PI19164
PI19165
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 PI62767 Fixes and Enhancements
Problem
Description
Fix
Complete APAR information
1 Specification of NULLFILE high-level qualifier for the IDIOPTLM RFRDSN data set name resulted in SDUMP RFR dumps also being disabled. The IDIOPTLM RFRDSN data set name NULLFILE high-level qualifier disabled both TDUMP and SDUMP RFR dumps. Only TDUMPs are now disabled. PI62668
2 LE abend U4038 during analysis. An array was being used beyond its allocated size in the LE heap, resulting in storage corruption. The erroneous usage of the array beyond its maximum size has been eliminated. PI62332
3 Accounting data is not formatted. Accounting data contains non printable data and therefore FA did not format the information. Non printable accounting data is converted to dots. The raw data is still available in the env control block presented to FA exits. PI65158
4 0C4 during COBOL sidefile processing. An inaccurate method for counting tokens on a COBOL source line was leading to a storage overlay. The counting code has been modifed accordingly. PI62407
5 Sample program definitions for programs IDIXCE69 and IDIXCE70 missing from IDISCICS sample The definitions had been missed Missing definitions have been added PI65152
6 IDIXDCAP has bad freemain Bad conditional freemain in IDIXDCAP does not free SP132 Conditional freemain in IDIXDCAP is corrected PI64233
7 0C4 in stack_op() when processing COBOL DWARF debugging information. Stack minidump flag not reset. Stack minidump flag now reset. PI64350
APAR PI58441 Fixes and Enhancements
Problem
Description
Fix
Complete APAR information
1 0C4 in entry point klcompare during Fault Analyzer's gathering of DB2 information. A length check was not being performed on a data area and hence a subsequent copy of the data was causing a storage overlay. The returned data length is now checked before the data move. PI62510
2 ABEND0C4 during message lookup. Long Java entry point name causes storage overlay. Entry point name is truncated to maximum buffer length. PI56847
3 An event for the Fault Analyzer invocation exit IDIXDCAP was incorrectly being included and flagged as point of failure. The event was not correctly identified as being one to suppress. The event is now suppressed. PI57103
4 ABEND0C4 during Java analysis. Array bounds are exceeded during Java analysis. Bounds of the array are checked properly. PI58357
5 With RETAINCICSDUMP(AUTO) specified the CICS transaction dump was not being suppressed after FA analysis. A check to see if FA was installed in the XDUREQ exit was incorrect and hence the transaction dump suppression was being delayed but not subsequently actioned. The exit check has been corrected. PI62509
6 A deadlock situation occurred between the abending task and the IDIS subsystem involving the SYSZRAC2 resource. The abending task was in a PC call to the IDIS subsystem which never completed. The reason being that the abending task owned the SYSZRAC2 resource, while the IDIS subsystem waited for shared access before it could process the request. The code already handles potential hang conditions during this particular PC call. However, due to TCBFX set on, this did not perform as expected. The particular IDIS PC call will be conditioned on TCBFX not being set. PI59807
7 ABENDS0C4 in pBatchReport + X'ED10'. A buffer was reallocated but an old copy of the buffer address was used. The current buffer address is now always used. PI60431
8 IDIDATST inconsitently finding matching sidefile. Storage usage on repeated iterations of IDIDATST caused invalid storage reference. Storage reference fixed. PI60166
9 FA loops while reporting COBOL table with out of bounds OCCURS DEPENDING ON variable. Table high bound not set to maximum when ODO variable is out of bounds. Table high bound set to maximum when ODO variable is out of bounds and noted in Storage Areas report. PI60246
10 ISPF error "panel IPVPI004 not found" when selecting the IDILANGP Side File Formatting Utility option from the Services pull-down menu. IDISISPF sample ISPF data set allocation exec does not include the required Common Component data sets. The required Common Component data sets have been added to the IDISISPF sample ISPF data set allocation exec. PI60372
11 ABENDS0C4 in routine IECPRLTV at offset X'36'. Routine IECPRLTV was called with an invalid DEB address. The problem has been eliminated. PI61430
APAR PI54261 Fixes and Enhancements
Problem
Description
Fix
Complete APAR information
1 Formatted DSECT command address always zero regardless of initial displayed storage address. The character format address ISPF variable failed to convert to a binary value due to missing string null-terminator. The string null-terminator has been added to ensure correct conversion to a binary value. PI55016
2 When using File Manager interface with a GDG generation data set, Fault Analyzer does not use the base name as an alternative means of locating the template. This was not supported. Fault Analyzer now attempts to locate a template using the GDG base name if there is no template for the generation data set. PI55028
3 The Event Summary does not distinguish between normal events and events for which the execution environment is no longer valid (historical events). No attempt was made to identify historical events in the Event Summary. Historical events have been separated out from normal events in the Event Summary. PI55148
4 IDICZSVC New IDICSVCR not found IDICZSVC does not cater for presence of abend code. IDICZSVC treats the presence of ABEND16D code as null entry. PI55196
5 Fault Analyzer reports COBOL V5 table index values as byte offsets into the table, not as the table occurrence. Table stride not available so index occurrence calculation was not possible. Table stride now available, table indexes reported as both byte offset into table and occurrence. For example, if stride is 8 bytes and byte offset (index value) is 32 then occurrence is 5. PI52923
6 IDIDA 0C4 abend processing COBOL V5 DWARF when variable has many substring references. String buffer overrun. String buffer size increased. PI55740
7 MSGIDI0063W DDfMdelt() rc=00100E37 During space management there is insufficient space for dfSMS to update PDSE internal control blocks. This is seen as ABENDx37 either updating $$INDEX or during stow delete of a fault entry. Improve space management to increase the amount of free space so that PDSE directory activity can occur. PI56722
8 Fault Analyzer abends with 0C4 in dwarf_offdie() while processing COBOL V5 program containing tables. Previous call to CDA API dwarf_formref() fails. dwarf_formref() calls replaced by dwarf_global_formref(). PI56547
9 When a java class or file name associated with an abend is very long, it can be truncated causing unpredictable errors including "Java class path length error". This problem occurs when the java class or file name is very long, and does not fit within a fixed size buffer. When the name exceeds the internal buffer size it can cause truncation or even storage overlay. The internal buffer size for handling java class and file names has been increased. Problems with very long class and file names associated with an abending task should no longer cause any problems. PI57921
APAR PI51864 Fixes and Enhancements
Problem
Description
Fix
Complete APAR information
1 IDI0005s processing LE dump Application dump contains a huge LE HANC control block. FA limits the amount of LE data that it will process. PI53877
2 DBCS data being sent to the console. Some WTO processing causes DBCS data to be sent to the console. The WTO processing path is updated to only send non-DBCS data to the console. PI53878
3 Fault Analyzer does not show HANDLE type variables in associated storage when analyzing an EPLI program abend with side files. Fault Analyzer does not correctly load the data value of HANDLE type variables when processing associated SYSBEDUG file, and does not show HANDLE type variables at all when processing an IDILANGX side file. Fault Analyzer processing has been corrected to correctly display HANDLE type variables in associated storage when the side file is SYSDEBUG or IDILANGX. PI53879
4 Fault Analyzer internally abending when entering Interactive Reanalysis When processing a CEE3ABD abend from COBOL with no LANGX side file generation, a logic error caused an internal abend. Additional validation added to ensure correct execution. PI53932
5 Storage for BLW not accessible message appears in Static storage display. BLW was not found due to a duplicate event near the required storage. The algorithm for finding the BLW was updated. PI53064
6 Mismatching LANGX side file is used for inactive COBOL/5 program. LANGX mismatch checks not performed for inactive COBOL/5 programs. LANGX mismatch checks now performed for inactive COBOL/5 programs. PI53177
7 Unrelated program in CICS event list. Incorrect register values picked up from CICS control blocks. Additional validation of register values incorporated. PI52322
8 0C4 in lineF() from COBOL Level 88 hotspot during interactive re-analysis. Level 88 items not available for suppressed copybook. Level 88 hotspot removed for suppressed copybooks. PI53175
APAR PI48923 Fixes and Enhancements
Problem
Description
Fix
Complete APAR information
1 For Enterprise PL/I, parameters passed to the main procedure are not visible in the associated storage listing during interactive re-analysis. For Enterprise PL/I abends, Fault Analyzer for z/OS does not correctly handle parameter variables passed to the main procedure and consequently, they are not displayed correctly in the Associated Storage listing during interactive re-analysis. Fault Analyzer for z/OS now correctly handles parameter variables passed to EPLI main procedures and displays them correctly in the Associated Storage listing during interactive re-analysis. PI51358
2 File open error description does not appear in synopsis for Cobol5. DCB conflict error code was not checked during synopsis report processing. DCB conflict error code is checked and reported in synopsis. PI50355
3 IDI0005S error message when using the Fault Analyzer plug-in. Logs explain that storage allocation failed. The Language Environment HEAP parameters provided as part of the Fault Analyzer plug-in back-end were not taking priority over user supplied values. This meant that insufficient or invalid storage could be used instead. The Language Environment parameters are now provided in such a way that they will always take priority over system/user supplied values. This will ensure that sufficient storage is available to the Fault Analyzer plug-in back-end program. PI51368
APAR PI46839 Fixes and Enhancements
Problem
Description
Fix
Complete APAR information
1 Static storage missing for Cobol5 Static storage for inactive Cobol5 program is missing. The Cobol5 program is mapped to provide static information PI45773
2 Abend ATCV using Fault Analyzer under CICS to view a CICS SDUMP A status popup panel did not have a specific ISPF keylist and hence was causing random data to be displayed which led to a terminal error. A specific keylist has been added to the status panel PI48914
3 Working-Storage Section not formatted for COBOL/5 program. There is a second CLLE for the program at a different address which stops the correct one being used. CLLE discovery changed to exclude duplicate CLLEs. PI47149
4 IDIUTIL IMPORT with no fault ID specification always fails with "No entries to Import" message. The source history file cache was not obtained during access checking. The source history file cache is now being obtained correctly. PI48915
APAR PI40802 Fixes and Enhancements
Problem
Description
Fix
Complete APAR information
1 When Fault Analyzer for z/OS writes the $$INDEX file to a history file an x37 abend may occur, even though the history file is auto space managed. This problem occurs when there is insufficient space in the history file for the $$INDEX file. Fault Analyzer for z/OS now determines if an x37 abend has occurred while writing the $$INDEX file, and if the history file is a PDSE and auto space managed, space is freed by deleting the oldest fault entry from the history file to provide sufficient space for the $$INDEX file. PI44013
2 Java events are missing from the Fault Analyzer Event Summary display. The JVM is making calls into native/JNI code multiple times, confusing the process of mapping the user's Java stack trace with the native JVM calls. Java event insertion is now more robust and can handle more complex program flows in and out of the JVM. PI46112
3 With the FA CICS LE exit (IDIXCCEE) and CICSDUMPTABLEEXCLUDE option, a CICS SDUMP is not being taken when specified on the CICS transaction dump table entry. If FA skips analysis due to the CICSDUMPTABLEEXCLUDE option (message IDI0101I) the CICS transaction dump is suppressed. However this should not happen if the SYSDUMP option has also been specified on the transaction dump table entry. Prior to setting the transaction dump suppress flag the CICS transaction dump table entry is checked to see if the SYSDUMP option has also been specified and if so the transaction dump is not suppressed. PI42010
4 Field ENV_ABEND_REASON_CODE is not populated correctly for a S04E abend. Special code for a S04E abend was not correctly setting field ABEND_REASON_CODE in the env structure. ABEND_REASON_CODE is now correctly set. PI46113
5 Abend0c4 in dwarf api Bad call to storage management routines resulted in ABEND0C4 Call to dwarf storage management routine is corrected PI42147
6 Event summary COBOL/5 event shown as all "n/a". The event was not recognized as a COBOL event due to an unexpected stub routine. The event is now recognized as a COBOL event. PI46108
7 Abendx37 does not recover space Space recovery calculations after abendx37 are not correct. Space recovery is calculations are corrected. PI46114
8 Cobol5 program is missing from the inactive program list. Cobol5 program is missing from the inactive program list when non-Cobol5 programs are present. The inactive program list is changed to show Cobol5 programs PI43086
9 CICS LM domain summary not being displayed for CICS 690 SDUMP An eyecatcher validity check is no longer valid for CICS 690 . The validity check has been modified for CICS 690 PI46107
10 First program name in ErrorHandler option list ignored. The ErrorHandler program name list was processed incorrectly. The ErrorHandler program name list is now processed correctly. PI43225
11 Abend0c9 in FA Interactive Reanalysis. Divide by zero occurs processing a dynamic array. Code changed to prevent the divide by zero. PI46115
12 COBOL Explorer shows COBOL/5 Working-Storage base locators ending with 'storage not accessible'. COBOL/5 MemId not set. COBOL/5 MemId now set (Working-Storage is addressed via static not BLWs). PI44727
13 User gets unending loop in function dfhs_tcpopl when analyzing CICS SDUMP dfhs_tcpopl is finding surrogate TCTTEs in the SDUMP and is not handling them correctly. dfhs_tcpopl has been changed to handle surrogate TCTTEs. PI45212
14 Parameters may not be reported for Enterprise PL/I program. Internal names used for parameters not checked correctly sometimes resulting in parameter being ignored. Internal parameter name check corrected. PI27960
15 When RENT compiler option is in effect, Enterprise PL/I STATIC and EXTERNAL variables are sometimes reported at the wrong address. When the PL/I error handler gets control, LE swaps the WSA address but does not swap back if an abend is issued. LE swap back implemented. PI46116
16 Fault Analyzer rejects side file for an assembler language program. Side file instruction check fails because op codes in executable code have been changed to SVC145 (Debug Tool hook). SVC145 instructions not checked. PI45886
APAR PI39682 Fixes and Enhancements
Problem
Description
Fix
Complete APAR information
1 n/a Development support n/a PM39682
APAR PI35460 Fixes and Enhancements
Problem
Description
Fix
Complete APAR information
1 Display of CICS channels and containers is not displaying all data. The presentation code of the channels and containers was ending before all data had been displayed. The early termination has been rectified and all data is now displayed. PI37632
2 The selection of ASCII or EBCDIC for a CICS container display was incorrectly picking ASCII. The incorrect data was being used when determining ASCII or EBCDIC. The correct data reference is now used. PI35276
3 COBOL/5 runtime routine IGZXAPI abends when called by Fault Analyzer to obtain open files. User's COBOL program has overlayed static storage in the caller program by updating Linkage Section data items when Linkage Section in the called program is larger than the caller's storage area. Fault Analyzer traps the IGZXAPI abend and prints a note in the report. PI39108
4 Fault Analyzer abends in AddXref() at stmt 3019 when processing COBOL/5 DWARF info. Processing of cross reference item DIEs incorrect. Processing of cross reference item DIEs corrected. PI34649
5 IDIROBOT exhausts tiot. IDIUTIL import processing does not free allocations. IDIUTIL is changed to free history file allocations. PI34600
6 CICS region experienced SM0102 storage violation during Fault Analyzer analysis of a transaction abend. It appears that a storage violation occurred during comitsg processing of the CICS Trace. We have been unable to find a cause of the violation, but are adding some defensive code which would prevent a violation from occurring in the future. PI35015
7 ABEND0C4 anaylyzing kernel stack. Dump contains a very large kernel stack which causes an internal array to exceed its bounds. Array is now getmained based on kernel stack size. PI35786
8 Point of failure is missing for a fault entry containing java information. The JVM has caused an abend but is being hidden in the event list. When populating a fault entry event list with the actual Java events (instead of the underlying JVM calls) the point of failure can be hidden if it was caused by the JVM implementation itself. If the JVM has been found to be the point of failure, the relevant native calls are preserved so that the abend can be investigated. PI40499
9 Fault Analyzer does not report COBOL qualified name usage and only one instance is reported. Fault Analyzer design never incorporated this. Fault Analyzer now reports qualfied names when they are used in the COBOL program. PI39109
10 When COBOL/5 TEST option is in effect, picture edited data items are missing from the report. Picture edited DWARF types were incorrectly processed. Picture edited DWARF types processing corrected. PI36160
11 MSGIDI0005S followed by MSGIDI0120S Dump contains a very large LE Hanc structure and FA exhausts storage attempting to format it. The amount of LE Heap Storage formatted is now limited. PI36221
12 Fault Analyzer plug-in connection fails with error message "connection reset". Logs show IDI0005S IDIGMAN Storage allocation failed message. CEEUOPT options were being read from a provided CEEPRMxx member instead of the intended CEEUOPT CSECT. This meant that the required HEAP settings could be overridden and the amount of storage available could be set lower than required. CEEUOPT options are now defined in such a way that they will take priority over a user supplied CEEPRMxx member. This will ensure that the required amount and location of HEAP storage is sufficient. PI36261
13 Incorrect nested group item offsets reported for COBOL/5 when using TEST option (DWARF). Group item stack incorrect. Group item stack corrected. PI36590
14 CICS region suffers abend999 (precursor to runaway / AICA) and possible hang with trace lock held when processing huge trace table. CICS has been configured with a large CICS trace table (TRTABSZ) and a low CPU runaway value (ICVR) and Fault Analyzer runs out of CPU time while processing the table during transaction fault analysis. Code has been added to protect FA from such an abend. PI40500
15 During Java analysis for a fault entry, an 0c4 abend occurs in module IDISJL. A function returns a pointer to a locally defined character array. After the return of this function, the memory can be reused, which is what appears to be happening. This causes an 0c4 abend when we attempt to use the values from this array. The function now takes in an argument which points to storage that can safely be used and will not be released. PI39110
16 Some COBOL/5 compiler options not reported. More COBOL/5 compiler options are available in the siginfo area but FA was unaware of them. FA now reports compiler options added to siginfo area. PI40501
17 User is analyzing a CICS SDUMP with Fault Analyzer and is looking at the CICS File Control Domain. The field RIDFLD in a FC panel is incorrect. Fault Analyzer is displaying data from an incorrect location. Fault Analyzer has been changed to locate RIDFLD from the correct place. PI37268
18 Sites activate 5655-PDS with a very generic product enablement policy but need to use 5655-Q11 Product enablement capability did not cater for a very generic product enablement policy. Product enablement capability is changed to cater for a highly generic policy. PI38972
19 Security violation accessing FA history file with XFACILIT rules. Code that was introduced to allow access to history file is not suitable in an ACF2 environment. Code updated to suit ACF2 requirements. PI39543
APAR PI31258 Fixes and Enhancements
Problem
Description
Fix
Complete APAR information
1 CICS suffers ABENDATNI in IDIXCM53 during RECEIVE BUFFER IDIXCM53 wants CICS to suppress the ATNI abend, but uses an incorrect control block offset. IDIXCM53 has been changed to use the correct ccontrol block offset. PI34756
2 0C4 when processing COBOL TEST option data for program compiled OPT(STD). Labels not in offset sequence due to optimization. Labels now processed without regard to sequence. PI31281
3 CICS SDUMPS/TRDUMPS are suppressed incorrectly. There is an error in the LE exit (IDIXCCEE). The SDUMP setting of a transaction dump table entry is not being correctly checked and hence the transaction dump is being incorrectly suppressed and the SDUMP isn't being taken. The CICS invocation exits have been changed to scan the CICS dump table and take the correct action. PI31383
4 User is analyzing a CICS SDUMP and is looking at the CQ domain, but is finding that there are no CQ Trace entries to display. CICS has moved the CQ Trace above the bar. FA has been corrected to access the CQ trace above the bar. PI32066
5 When there is more than one instance of an inactive COBOL program, working-storage for one instance may be confused with another. Base locators are related to the CSECT (code) not to a data instance. Base locators now related to CLLE which occurs for each data instance. PI34757
6 FA user is analyzing a CICS SDUMP and wants to display DS domain open TCBs, but FA reports that there are no open TCBs, even though some are present in the CICS region. FA is failing to find open TCBs due to structure changes within CICS. FA has been changed to locate and report open TCBs. PI32260
7 IDI0002 contains DBCS data. CICS ABEND AEIV is generating DBCS data for IDI0002. CICS ABEND analysis honors the LANGUAGE processing option. PI34758
8 MSGIDI0161W issued with bad DBCS data. Multi-line WTO is formatted incorrectly when history data set name is exactly 19 bytes long and DBCS data present. Multi-line WTO with DBCS is now formatted correctly. PI34759
9 COBOL Explorer erroneously issues "source line not executable" messages. Source line no_code flag set incorrectly. Set source no_code flag correctly. PI33502
10 MSGIDI0010E issued for PCC4STAK. Binder call is being issued for load module that failed BLDL. Binder call is no longer issued. PI34760
11 Source not reported when using COBOL/5 Developer Trial (5655-TRY). Fault Analyzer does not recognise 5655-TRY. Fault Analyzer now recognises 5655-TRY. PI34754
12 IDILANGX uses excessive CPU when processing large OS VS/COBOL compiler listing. Sequential source search to locate symbol. Map section and source now matched sequentiallyas both are in sequence. PI35351
APAR PI28247 Fixes and Enhancements
Problem
Description
Fix
Complete APAR information
1 DD DUMMY allocation is being freed A DD DUMMY allocation is being freed that was not allocated Allocation of preallocated dd dummy no longer occurs PI28040
2 Listing prompt panel loops with quit command When quit is entered on the listing prompt panel Fault Analyzer loops Quit command is corrected to exit interactive analysis PI30647
3 Fault entry list not updated Fault entry list is not updated by import from IDIROBOT Import processing now causes the cache to be updated PI30649
4 Fault Analyzer ISPF interface unable to allocate new history file when copying fault entry using the 'C' line command to a history file that doesn't exist. A check for the existence of the specified history file was not working correctly. The check for existence of the history file has corrected. PI28281
5 Point-of-failure event details not shown in batch report with Detail(S) or Detail(M) option, if point-of-failure event follows the first or only abend event. The design assumed the point-of-failure event would never follow the first abend event. The situation where the point-of-failure event follows the first abend event is now handled correctly. PI28783
6 CheckMaxCurr option not working correctly when analysis performed by CICS LE exit IDIXCCEE The CheckMaxCurr check was being deferred to subsequent processing however it was too late to allow the analysis to be skipped. The CheckMaxCurr check is now made at the appropriate place to allow for successful skipping of analysis. PI30505
7 User is getting INVREQ on EXEC CICS RELEASE because DT's XEIIN GLUE return code is being overridden by FA's XEIIN GLUE FA's XEIIN GLUE - IDIXCE68, for example - is not propagating the GLUE return code from previous XEIIN GLUEs. FA's XEIIN GLUEs have been modified to propagate the return code correctly. PI28912
8 Receive message "Internal Server Error" when "Downloading report" (opening a fault entry) in the Fault Analyzer plug-in. When refreshing a fault entry using the Fault Analyzer plug- in that contains an empty/invalid CICS trace entry (or batch using DETAIL=LONG) the reanalysis will fail. Reanalysis now checks for the validity of the CICS trace storage before attempting to extract information using DETAIL=LONG. PI28247
9 Enterprise PL/I STATIC EXTERNAL variables reported incorrectly when RENT option in effect. WSA not used in STATIC EXTERNAL addressing. WSA and STATIC offset Qcons now used for addressing when RENT option in effect. The LIST option is also required to correctly report these variables. PI30650
10 The user is analyzing a CICS SDUMP and is looking at the IS Domain. FA formats information about the IS domain incorrectly. Changes in CICS have not been reflected in the script that FA uses to format the IS Domain. FA has been updated to reflect the changes in CICS. PI29334
11 COBOL Explorer duplicates source line when 'Expand all' is used. Some source line ranges not terminated. Source line range now terminated with last source line number. PI30031
12 COBOL Explorer loops following initial dialog. Program contains 'recursive' GO TOs. GO TO recursion recognised and branch analysis ignores additional branches. PI29899
13 IDIS subsystem IDI0082E SQLAllocConnect error messages with reason codes 00f30002, 00f30006 or 00f30012. Fault entry reanalysis was performed on a different MVS image to where it was created, and without the same DB2 system being active. A check has been added to determine if the reason for the DB2 connection error during reanalysis is that the DB2 system is not active on the current MVS image, and if so suppress the IDI0082E message. PI33113
APAR PI24512 Fixes and Enhancements
Problem
Description
Fix
Complete APAR information
1 CICS S878 abend after high level of IDI0066I duplicate abends. Fault Analyzer processing of IDI0066I duplicate message can leave SSIB/SSOB control blocks in storage causing S878. The FREEMAIN process for the fast duplicate test has been corrected. PI24419
2 Recursive IDI0011S messages from Fault Analyzer if IGWFAMS takes an abend. Fault Analyzer calling IGWFAMS for a PDSE space check can give recursive IDI0011S messages if IGWFAMS gets an abend. Code added to protect against recursion if IGWFAMS gets an abend when called for a PDSE space check. PI27956
3 ENQ hang after Fault Analyzer IDI0092S timeout message. If Fault Analyzer IDI0092S timeout processing occurs during an ENQ delay the RFR process could cause an ENQ deadlock. Code has been added to detect the potential deadlock and delay the RFR processing until after the IDIDA TCB is detached. PI27957
4 Abend S0C4 at entry point TbHdr offset X'4A4'. A string was processed beyond the ending null terminator. Processing no longer performed beyond the ending null terminator. PI27958
5 CICS transaction abend analysis suffers ABENDATNI while issuing SEND CONTROL Fault Analyzer issues SEND CONTROL to flush the 3270 buffer out to the terminal. We are advised that this is not needed as FA's RECEIVE BUFFER will cause data to be flushed, and that if there is a problem then RECEIVE BUFFER will get TERMERR and not be abended with ATNI. The SEND CONTROL code has been deleted. PI27959
6 0C4 in PrtPliStg() when processing variables in unreferenced pages in static storage. Invalid minidump page is de-referenced. Unreferenced minidump addresses checked before de-reference. PI27960
7 Fault analyzer user analyzing a CICS SDUMP receives an abend in pp_ts_model_summary The CICS region is not fully initialised, and so does not have a TS Domain anchor, causing the abend, The function pp_ts_model_summary has been changed to check that the TS Domain anchor exists before looking for any models. PI27961
8 POF not identified correctly for a waiting TSO batch job The TSO TCB is not being identified correctly during realtime processing Code is changed to identify a waiting TSO step correctly PI27868
9 Incomplete DB2 information when plan is bound using PKLIST(*.xxxxxxxx.*). When using BIND PLAN with PKLIST(*.xxxxxxxx.*), the SYSPKLIST.LOCATION value changes from blank to '*', which was not handled correctly. The changed value in SYSPKLIST.LOCATION is now being handled correctly. PI27962
10 Fault Analyzer report shows S0CA decimal overflow that was a recoverable event. The Fault Analyzer event list has a S0CA abend event but the decimal overflow is historical and was recovered. The recovered event is removed from the event list. PI27963
11 MSGIDI0053I sends DBCS data to the console. Fault Analyzer is formatting DBCS data with MSGIDI0053I MSGIDI0053I is only issued in English PI27964
12 ABEND0C4 processing CICS DU domain Abend0c4 in pp_cics_summary using zero pointer. pp_cics_summary is changed to not use a zero pointer PI27965
APAR PI19883 Fixes and Enhancements
Problem
Description
Fix
Complete APAR information
1 0C4 in GetStgMem when processing PL/I AUTO/STATIC storage. AUTO/STATIC storage not checked for accessibility. AUTO/STATIC storage now checked for accessibility. PI23641
2 S201 abend in IDISLEEP. An invalid ECB reference was being used, leading to S201 abend. The invalid reference has been removed. PI23642
3 S0C4 when using Fault Analyzer XEIIN GLUE. The FA XEIIN code was not correctly allowing for a failed GETMAIN due to CICS being SOS. A failed GETMAIN is now correctly handled. PI23643
4 Abend S0C4 at entry point CFREE when exiting interactive reanalysis of fault entry. A control block was attempted free'd, which had already been free'd. The problem has been corrected. PI22236
5 When formatting COBOL/5 Associated Storage Areas, variable declarations appear as 'IDENTIFICATION DIVISION' or some other inappropriate value. DWARF does not have a decl_line attribute for internally generated variables (eg. SQL---PLIST). Declared line # set to 1, which indicates an internally generated variable. PI21123
6 SSIB storage not being FREEMAINed. The check for an IDIOFF DD, or a DD as specified in the AdditionalIDIOffDD option, causes an IDIS subsystem call. Due to incorrect register usage, the SSIB storage area was not being FREEMAINed. The incorrect register usage has been fixed so the SSIB will now be correctly FREEMAINed. PI23644
7 ISPF dialog error when specifying two or more adjacent asterisks in the Fault Entry List display history file name field. The specified history file name was not adequately checked for valid syntax before calling the ISPF LMDINIT service. The history file name syntax checking has been improved to prevent the problem. PI21479
8 IDI0144E IDIS error 0C4 when high activity. Fault Analyzer IDIS subsystem message IDI0144E 0C4 abend after Coupling Facility XCF message delays. The XCF recovery code has been updated to ensure delayed messages are still valid to process. PI23645
9 IDI0005S IDIUTIL:524 Storage allocation for 88 (X'58') bytes failed - processing terminated. A loop occurred due to the absence of a SYSIN DD statement. A SYSIN DD statement is no longer required when all control statements are passed to IDIUTIL via the PARM field. PI23646
10 Use of Fault Analyzer XEIIN exit can cause short on storage conditions. Storage areas GETMAINed by XEIIN code were not being explictly FREEMAINed, which for long running tasks could lead to short on storage conditions. All storage areas are correctly FREEMAINed. PI23407
11 IDI0144E IDIS error detected at IDIXDCAP:371: TCB 8B0738 S0CA Fault Analyzer IDIS subsystem message IDI0144E followed by IDI0145I IDIS subtask for: IDISCJST terminated. Requesting regions may then hang until the IDIS subsystem is stopped and restarted. Code added to insure the IDISCJST termination cause IDIS to terminate. PI23647
12 After access to a fault entry has been attempted, but rejected by the IDIXFXIT exit, subsequent attempts to access other fault entries are incorrectly rejected. The rejected access was incorrectly being remembered for other fault entries, for which access should have been granted. The access to individual fault entries is now being determined correctly. PI23869
APAR PI17012 Fixes and Enhancements
Problem
Description
Fix
Complete APAR information
1 Fault Analyzer message IDI0151W for a partial SVC dump not correct. The return and reason code processing for SDUMP is not always correctly reported when issued from IBM Fault Analyzer. Reason code processing corrected. PI19156
2 Abend S0C4 in PliSepStruct when processing constants in SYSDEBUG side file. Constants have a structure parent which can cause them to be processed as structure members. Constants no longer processed as structure members. PI19157
3 Fault Analyzer event list info for NORENT assembler not useful. NORENT programs with DSAs imbedded in the CSECT, and often using non-standard linkage, are getting no event information. Code added to detect the static DSA and at least show load module and CSECT data in the event list. PI19158
4 The application's last CICS 3270 buffer is not being formatted correctly. The user has a 3270 emulator which, when given a 'F2' or "Read Buffer" command, returns a data stream which contains SBA orders. FA did not have code to handle those SBAs. Fault Analyzer has been altered to handle SBA orders in the Read Buffer data stream. PI19159
5 Intermittent problem leads to abend S0C4 during execution of Formatting user exit. Fault Analyzer is not correctly handling the abend, which might be expected during normal processing. Fault Analyzer is now handling the abend. PI19160
6 User is performing CICS SDUMP analysis and looking at the CQ Domain. Values in the panels are incorrect. Fault Analyzer is using incorrect control block offsets to obtain the values. Fault Analyzer has been updated to use the correct offsets. PI19161
7 FA reports incorrect compiler options for COBOL/5.1.1. New compiler options added. New compiler options recognized. PI18319
8 Fault Analyzer ErrorHandler option names might not get honoured if input from an MVS dump. When an MVS dump is used as input to Fault Analyzer to get a fault report on the dump, the ErrorHandler program names might not get recognized correctly because MVS dump input does not trigger FA Binder mapping of modules. The ErrorHandler code will also check entry point name, if program name has not been determined for an event. PI19162
9 Reported assembler DSECT has missing fields. DSECT has more fields than can be contained in single LANGX structure record, but only the first LANGX record is processed. Multiple LANGX structure records now processed for large assembler DSECTs. PI19163
10 Fault Analyzer interactive analysis Listing/Side File Mismatch panel ENTER action for COBOL does not force use of the side file. The pop-up panel reporting Listing/Side File Mismatch indicates ENTER will accept a current COBOL SYSDEBUG file, but it is ignored and no source for that program is presented. The code has been updated to accept the side file when possible. PI17309
11 CICS Container data incorrectly being displayed in ASCII rather than EBCDIC. The count of ASCII and EBCDIC characters was incorrect. The count of ASCII and EBCDIC characters has been corrected. PI17905
12 FA formats too many CICS trace entries. FA processes all the trace entries in a particular trace block. FA is changed to stop formatting once the current timestamp is less than the previous timestamp. PI19164
13 Abend S0C4 in CobCdaSym() when processing DWARF in COBOL/5 load module. Storage re-allocation did not reset pointer into area. Symbol lookup pointer reset when storage area re-allocated. PI18440
14 Message IDI0089I Subsystem IDISLOG RC=8 Rsn=63 IDI0159I SDUMP usage error. Fault Analyzer RFR recovery after IDI0005 storage shortage can get IDI0089I Subsystem IDISLOG RC=8 Rsn=63 SDUMP usage error attempting to do a second SDUMP. The logic is corrected to determine if the RFR dump has already been taken. PI19165
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
UI39096 Download PTF UI39096
UI35733 Download PTF UI35733
UI33672 Download PTF UI33672
UI32542 Download PTF UI32542
UI31231 Download PTF UI31231
UI30210 Download PTF UI30210
UI30213 Download PTF UI30213
UI29961 Download PTF UI29961
UI27381 Download PTF UI27381
UI25081 Download PTF UI25081
UI23575 Download PTF UI23575
UI22345 Download PTF UI22345
UI20672 Download PTF UI20672
UI18643 Download PTF UI18643
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:
UI39096
6 Jul 2016 UI31231
UI32542
UI33672
UI35733
PI58440
PI61531
PI62522
PI62523
PI62524
PI62525
PI62526
PI62527
PI62528
PI65159
PI65160
PI65161
PI65162
PI65163
English:
UI35733
3 Mar 2016 UI31231
UI32542
UI33672
PI54260
PI58191
PI58192
PI58193
PI58195
PI58196
PI58197
PI58198
PI58199
English:
UI33672
15 Dec 2015 UI31231
UI32542
PI49842
PI51863
PI53872
PI53873
PI53880
PI53881
PI53882
PI53883
English:
UI32542
5 Nov 2015 UI31231 PI48922
PI48924
PI51359
PI51369
English:
UI31231
2 Oct 2015 UI12501
UI13466
UI14758
UI17281
UI18643
UI20672
UI22345
UI23575
UI25081
UI27381
UI29961
UK79416
UK80540
UK82439
UK83720
UK91859
UK93704
UK95217
UK96928
UK97174
UK98036
PI46007
PI46838
PI48916
PI48917
PI48918
Japanese:
UI30210
18 Aug 2015 UI29961 PI40801
Korean:
UI30213
18 Aug 2015 UI29961 PI40801
English:
UI29961
18 Aug 2015 UI14758
UI17281
UI18643
UI20672
UI22345
UI23575
UI25081
UI27381
PI27968
PI40801
PI43011
PI44077
PI46106
PI46109
PI46117
PI46118
PI46119
PI46120
PI46121
PI46122
PI46123
PI46124
PI46125
PI46126
English:
UI27381
12 May 2015 UI14758
UI18643
UI20672
UI22345
UI23575
UI25081
PI35461
PI36317
PI36917
PI39112
PI40502
PI40503
PI40504
PI40505
PI40506
PI40507
PI40508
PI40509
PI40510
PI40511
PI40512
English:
UI25081
3 Mar 2015 UI20672
UI22345
UI23575
PI20842
PI31257
PI32310
PI32478
PI34761
PI34762
PI34763
PI34764
PI34765
PI34766
PI34767
PI34768
English:
UI23575
8 Dec 2014 UI14758
UI20672
UI22345
PI27137
PI28238
PI28248
PI30651
PI30652
PI30653
PI30654
PI30655
PI30656
English:
UI22345
24 Oct 2014 UI20672 PI22844
PI23253
PI24513
PI25989
PI26163
PI27861
PI27866
PI27869
PI27870
PI27966
PI27967
PI27968
PI27969
English:
UI20672
3 Sep 2014 UI14758
UI17281
UI18643
PI19884
PI20506
PI22420
PI22526
PI23405
PI23406
PI23638
PI23648
PI23649
PI23650
PI23651
PI23652
PI23653
PI23654
PI23870
English:
UI18643
1 Jul 2014 UI14758
UI17281
PI15010
PI15843
PI16631
PI17013
PI17241
PI17568
PI18082
PI18986
PI19146
PI19150
PI19151
PI19166
PI19167
PI19168
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 PI58440 Fixes and Enhancements
Problem
Description
Fix
Complete APAR information
1 0C4 in entry point klcompare during Fault Analyzer's gathering of DB2 information. A length check was not being performed on a data area and hence a subsequent copy of the data was causing a storage overlay. The returned data length is now checked before the data move. PI62522
2 An event for the Fault Analyzer invocation exit IDIXDCAP was incorrectly being included and flagged as point of failure. The event was not correctly identified as being one to suppress. The event is now suppressed. PI62523
3 With RETAINCICSDUMP(AUTO) specified the CICS transaction dump was not being suppressed after FA analysis. A check to see if FA was installed in the XDUREQ exit was incorrect and hence the transaction dump suppression was being delayed but not subsequently actioned. The exit check has been corrected. PI62524
4 A deadlock situation occurred between the abending task and the IDIS subsystem involving the SYSZRAC2 resource. The abending task was in a PC call to the IDIS subsystem which never completed. The reason being that the abending task owned the SYSZRAC2 resource, while the IDIS subsystem waited for shared access before it could process the request. The code already handles potential hang conditions during this particular PC call. However, due to TCBFX set on, this did not perform as expected. The particular IDIS PC call will be conditioned on TCBFX not being set. PI62525
5 ABENDS0C4 in pBatchReport + X'ED10'. A buffer was reallocated but an old copy of the buffer address was used. The current buffer address is now always used. PI62526
6 IDIDATST inconsistently finding matching sidefile. Storage usage on repeated iterations of IDIDATST caused invalid storage reference. Storage reference fixed. PI62527
7 Abend0c4 during Java analysis. Array bounds are exceeded during Java analysis. Bounds of the array are checked properly. PI62528
8 Accounting data is not formatted. Accounting data contains non printable data and therefore FA did not format the information. Non printable accounting data is converted to dots. The raw data is still available in the env control block presented to FA exits. PI61531
9 Specification of NULLFILE high-level qualifier for the IDIOPTLM RFRDSN data set name resulted in SDUMP RFR dumps also being disabled. The IDIOPTLM RFRDSN data set name NULLFILE high-level qualifier disabled both TDUMP and SDUMP RFR dumps. Only TDUMPs are now disabled. PI65159
10 LE abend U4038 during analysis. An array was being used beyond its allocated size in the LE heap, resulting in storage corruption. The erroneous usage of the array beyond its maximum size has been eliminated. PI65160
11 0C4 during COBOL sidefile processing. An inaccurate method for counting tokens on a COBOL source line was leading to a storage overlay. The counting code has been modifed accordingly. PI65161
12 Sample program definitions for programs IDIXCE69 and IDIXCE70 missing from IDISCICS sample The definitions had been missed Missing definitions have been added PI65162
13 IDIXDCAP has bad freemain Bad conditional freemain in IDIXDCAP does not free SP132 Conditional freemain in IDIXDCAP is corrected PI65163
14 0C4 in stack_op() when processing COBOL DWARF debugging information. Stack minidump flag not reset. Stack minidump flag now reset. PI65592
APAR PI54260 Fixes and Enhancements
Problem
Description
Fix
Complete APAR information
1 When using File Manager interface with a GDG generation data set, Fault Analyzer does not use the base name as an alternative means of locating the template. This was not supported. Fault Analyzer now attempts to locate a template using the GDG base name if there is no template for the generation data set. PI58191
2 The Event Summary does not distinguish between normal events and events for which the execution environment is no longer valid (historical events). No attempt was made to identify historical events in the Event Summary. Historical events have been separated out from normal events in the Event Summary. PI58192
3 IDICZSVC New IDICSVCR not found IDICZSVC does not cater for presence of abend code. IDICZSVC treats the presence of ABEND16D code as null entry. PI58193
4 Fault Analyzer reports COBOL V5 table index values as byte offsets into the table, not as the table occurrence. Table stride not available so index occurrence calculation was not possible. Table stride now available, table indexes reported as both byte offset into table and occurrence. For example, if stride is 8 bytes and byte offset (index value) is 32 then occurrence is 5. PI58195
5 IDIDA 0C4 abend processing COBOL V5 DWARF when variable has many substring references. String buffer overrun. String buffer size increased. PI58196
6 MSGIDI0063W DDfMdelt() rc=00100E37 During space management there is insufficient space for dfSMS to update PDSE internal control blocks. This is seen as ABENDx37 either updating $$INDEX or during stow delete of a fault entry. Improve space management to increase the amount of free space so that PDSE directory activity can occur. PI58197
7 Fault Analyzer abends with 0C4 in dwarf_offdie() while processing COBOL V5 program containing tables. Previous call to CDA API dwarf_formref() fails. dwarf_formref() calls replaced by dwarf_global_formref(). PI58198
8 When a java class or file name associated with an abend is very long, it can be truncated causing unpredictable errors including "Java class path length error". This problem occurs when the java class or file name is very long, and does not fit within a fixed size buffer. When the name exceeds the internal buffer size it can cause truncation or even storage overlay. The internal buffer size for handling java class and file names has been increased. Problems with very long class and file names associated with an abending task should no longer cause any problems. PI58199
APAR PI51863 Fixes and Enhancements
Problem
Description
Fix
Complete APAR information
1 IDI0005S processing LE dump Application dump contains a huge LE HANC control block. FA limits the amount of LE data that it will process. PI52509
2 Prevent DBCS data from being sent to console. Some WTO processing causes DBCS data to be sent to the console. The WTO processing path is updated to only send non-DBCS data to the console. PI53873
3 Storage for BLW not accessible message appears in Static storage display. BLW was not found due to a duplicate event near the required storage. The algorithm for finding the BLW was updated. PI53880
4 Mismatching LANGX side file is used for inactive COBOL/5 program. LANGX mismatch checks not performed for inactive COBOL/5 programs. LANGX mismatch checks now performed for inactive COBOL/5 programs. PI53881
5 Unrelated program in CICS event list. Incorrect register values picked up from CICS control blocks. Additional validation of register values incorporated. PI53882
6 Fault Analyzer does not show HANDLE type variables in associated storage when analyzing an EPLI program abend with side files. Fault Analyzer does not correctly load the data value of HANDLE type variables when processing associated SYSBEDUG file, and does not show HANDLE type variables at all when processing an IDILANGX side file. Fault Analyzer processing has been corrected to correctly display HANDLE type variables in associated storage when the side file is SYSDEBUG or IDILANGX. PI49842
7 0C4 in lineF() from COBOL Level 88 hotspot during interactive re-analysis. Level 88 items not available for suppressed copybook. Level 88 hotspot removed for suppressed copybooks. PI53883
APAR PI48922 Fixes and Enhancements
Problem
Description
Fix
Complete APAR information
1 For Enterprise PL/I, parameters passed to the main procedure are not visible in the associated storage listing during interactive re-analysis. For Enterprise PL/I abends, Fault Analyzer for z/OS does not correctly handle parameter variables passed to the main procedure and consequently, they are not displayed correctly in the Associated Storage listing during interactive re-analysis. Fault Analyzer for z/OS now correctly handles parameter variables passed to EPLI main procedures and displays them correctly in the Associated Storage listing during interactive re-analysis. PI48924
2 File open error description does not appear in synopsis for Cobol5. DCB conflict error code was not checked during synopsis report processing. DCB conflict error code is checked and reported in synopsis. PI51359
3 IDI0005S error message when using the Fault Analyzer plug-in. Logs explain that storage allocation failed. The Language Environment HEAP parameters provided as part of the Fault Analyzer plug-in back-end were not taking priority over user supplied values. This meant that insufficient or invalid storage could be used instead. The Language Environment parameters are now provided in such a way that they will always take priority over system/user supplied values. This will ensure that sufficient storage is available to the Fault Analyzer plug-in back-end program. PI51369
APAR PI46838 Fixes and Enhancements
Problem
Description
Fix
Complete APAR information
1 Static storage missing for Cobol5 Static storage for inactive Cobol5 program is missing. The Cobol5 program is mapped to provide static information PI48916
2 Abend ATCV using Fault Analyzer under CICS to view a CICS SDUMP A status popup panel did not have a specific ISPF keylist and hence was causing random data to be displayed which led to a terminal error. A specific keylist has been added to the status panel PI46007
3 Working-Storage Section not formatted for COBOL/5 program. There is a second CLLE for the program at a different address which stops the correct one being used. CLLE discovery changed to exclude duplicate CLLEs. PI48917
4 IDIUTIL IMPORT with no fault ID specification always fails with "No entries to Import" message. The source history file cache was not obtained during access checking. The source history file cache is now being obtained correctly. PI48918
APAR PI40801 Fixes and Enhancements
Problem
Description
Fix
Complete APAR information
1 When Fault Analyzer for z/OS writes the $$INDEX file to a history file a x37 abend may occur, even though the history file is auto space managed. This problem occurs when there is insufficient space in the history file for the $$INDEX file. Fault Analyzer for z/OS now determines if an x37 abend has occurred while writing the $$INDEX file, and if the history file is a PDSE and auto space managed, space is freed by deleting the oldest fault entry from the history file to provide sufficient space for the $$INDEX file. PI46117
2 With the FA CICS LE exit (IDIXCCEE) and CICSDUMPTABLEEXCLUDE option, a CICS SDUMP is not being taken when specified on the CICS transaction dump table entry. If FA skips analysis due to the CICSDUMPTABLEEXCLUDE option (message IDI0101I) the CICS transaction dump is suppressed. However this should not happen if the SYSDUMP option has also been specified on the transaction dump table entry. Prior to setting the transaction dump suppress flag the CICS transaction dump table entry is checked to see if the SYSDUMP option has also been specified and if so the transaction dump is not suppressed. PI46118
3 Field ENV_ABEND_REASON_CODE is not populated correctly for a S04E abend. Special code for a S04E abend was not correctly setting field ABEND_REASON_CODE in the env structure. ABEND_REASON_CODE is now correctly set. PI43011
4 Abend0c4 in dwarf api Bad call to storage management routines resulted in ABEND0C4 Call to dwarf storage management routine is corrected PI46119
5 Event summary COBOL/5 event shown as all "n/a". The event was not recognized as a COBOL event due to an unexpected stub routine. The event is now recognized as a COBOL event. PI46120
6 Abendx37 does not recover space Space recovery calculations after abendx37 are not correct. Space recovery is calculations are corrected. PI46109
7 Cobol5 program is missing from the inactive program list. Cobol5 program is missing from the inactive program list when non-Cobol5 programs are present. The inactive program list is changed to show Cobol5 programs PI46121
8 CICS LM domain summary not being displayed for CICS 690 SDUMP An eyecatcher validity check is no longer valid for CICS 690 . The validity check has been modified for CICS 690 PI46122
9 First program name in ErrorHandler option list ignored. The ErrorHandler program name list was processed incorrectly. The ErrorHandler program name list is now processed correctly. PI46123
10 Abend0c9 in FA Interactive Reanalysis. Divide by zero occurs processing a dynamic array. Code changed to prevent the divide by zero. PI44077
11 User gets unending loop in function dfhs_tcpopl when analyzing CICS SDUMP dfhs_tcpopl is finding surrogate TCTTEs in the SDUMP and is not handling them correctly. dfhs_tcpopl has been changed to handle surrogate TCTTEs. PI46124
12 Parameters may not be reported for Enterprise PL/I program. Internal names used for parameters not checked correctly sometimes resulting in parameter being ignored. Internal parameter name check corrected. PI27968
13 When RENT compiler option is in effect, Enterprise PL/I STATIC and EXTERNAL variables are sometimes reported at the wrong address. When the PL/I error handler gets control, LE swaps the WSA address but does not swap back if an abend is issued. LE swap back implemented. PI46125
14 Fault Analyzer rejects side file for an assembler language program. Side file instruction check fails because op codes in executable code have been changed to SVC145 (Debug Tool hook). SVC145 instructions not checked. PI46126
15 Java events are missing from the Fault Analyzer Event Summary display. The JVM is making calls into native/JNI code multiple times, confusing the process of mapping the user's Java stack trace with the native JVM calls. Java event insertion is now more robust and can handle more complex program flows in and out of the JVM. PI46106
APAR PI35461 Fixes and Enhancements
Problem
Description
Fix
Complete APAR information
1 Display of CICS channels and containers is not displaying all data. The presentation code of the channels and containers was ending before all data had been displayed. The early termination has been rectified and all data is now displayed. PI40502
2 The selection of ASCII or EBCDIC for a CICS container display was incorrectly picking ASCII. The incorrect data was being used when determining ASCII or EBCDIC. The correct data reference is now used. PI40503
3 IDIROBOT exhausts tiot. IDIUTIL import processing does not free allocations. IDIUTIL is changed to free history file allocations. PI40504
4 ABEND0C4 anaylyzing kernel stack. Dump contains a very large kernel stack which causes an internal array to exceed its bounds. Array is now getmained based on kernel stack size. PI40505
5 When COBOL/5 TEST option is in effect, picture edited data items are missing from the report. Picture edited DWARF types were incorrectly processed. Picture edited DWARF types processing corrected. PI40506
6 COBOL/5 runtime routine IGZXAPI abends when called by Fault Analyzer to obtain open files. User's COBOL program has overlayed static storage in the caller program by updating Linkage Section data items when Linkage Section in the called program is larger than the caller's storage area. Fault Analyzer traps the IGZXAPI abend and prints a note in the report. PI40507
7 Fault Analyzer abends in AddXref() at stmt 3019 when processing COBOL/5 DWARF info. Processing of cross reference item DIEs incorrect. Processing of cross reference item DIEs corrected. PI40508
8 MSGIDI0005S followed by MSGIDI0120S Dump contains a very large LE Hanc structure and FA exhausts storage attempting to format it. The amount of LE Heap Storage formatted is now limited. PI40509
9 Incorrect nested group item offsets reported for COBOL/5 when using TEST option (DWARF). Group item stack incorrect. Group item stack corrected. PI40510
10 CICS region suffers abend999 (precursor to runaway / AICA) and possible hang with trace lock held when processing huge trace table. CICS has been configured with a large CICS trace table (TRTABSZ) and a low CPU runaway value (ICVR) and Fault Analyzer runs out of CPU time while processing the table during transaction fault analysis. Code has been added to protect FA from such an abend. PI36917
11 User is analyzing a CICS SDUMP with Fault Analyzer and is looking at the CICS File Control Domain. The field RIDFLD in a FC panel is incorrect. Fault Analyzer is displaying data from an incorrect location. Fault Analyzer has been changed to locate RIDFLD from the correct place. PI40511
12 Some COBOL/5 compiler options not reported. More COBOL/5 compiler options are available in the siginfo area but FA was unaware of them. FA now reports compiler options added to siginfo area. PI39112
13 Point of failure is missing for a fault entry containing java information. The JVM has caused an abend but is being hidden in the event list. When populating a fault entry event list with the actual Java events (instead of the underlying JVM calls) the point of failure can be hidden if it was caused by the JVM implementation itself. If the JVM has been found to be the point of failure, the relevant native calls are preserved so that the abend can be investigated. PI36317
14 Security violation accessing FA history file with XFACILIT rules. Code that was introduced to allow access to history file is not suitable in an ACF2 environment. Code updated to suit ACF2 requirements. PI40512
APAR PI31257 Fixes and Enhancements
Problem
Description
Fix
Complete APAR information
1 CICS suffers ABENDATNI in IDIXCM53 during RECEIVE BUFFER IDIXCM53 wants CICS to suppress the ATNI abend, but uses an incorrect control block offset. IDIXCM53 has been changed to use the correct ccontrol block offset. PI34761
2 CICS SDUMPS/TRDUMPS are suppressed incorrectly. There is an error in the LE exit (IDIXCCEE). The SDUMP setting of a transaction dump table entry is not being correctly checked and hence the transaction dump is being incorrectly suppressed and the SDUMP isn't being taken. The CICS invocation exits have been changed to scan the CICS dump table and take the correct action. PI34762
3 0C4 when processing COBOL TEST option data for program compiled OPT(STD). Labels not in offset sequence due to optimization. Labels now processed without regard to sequence. PI34763
4 User is analyzing a CICS SDUMP and is looking at the CQ domain, but is finding that there are no CQ Trace entries to display. CICS has moved the CQ Trace above the bar. FA has been corrected to access the CQ trace above the bar. PI34764
5 FA user is analyzing a CICS SDUMP and wants to display DS domain open TCBs, but FA reports that there are no open TCBs, even though some are present in the CICS region. FA is failing to find open TCBs due to structure changes within CICS. FA has been changed to locate and report open TCBs. PI34765
6 IDI0002 contains DBCS data. CICS ABEND AEIV is generating DBCS data for IDI0002. CICS ABEND analysis honors the LANGUAGE processing option. PI32310
7 MSGIDI0161W issued with bad DBCS data. Multi-line WTO is formatted incorrectly when history data set name is exactly 19 bytes long and DBCS data present. Multi-line WTO with DBCS is now formatted correctly. PI32478
8 When there is more than one instance of an inactive COBOL program, working-storage for one instance may be confused with another. Base locators are related to the CSECT (code) not to a data instance. Base locators now related to CLLE which occurs for each data instance. PI20842
9 COBOL Explorer erroneously issues "source line not executable" messages. Source line no_code flag set incorrectly. Set source no_code flag correctly. PI34766
10 MSGIDI0010E issued for PCC4STAK. Binder call is being issued for load module that failed BLDL. Binder call is no longer issued. PI34767
11 Source not reported when using COBOL/5 Developer Trial (5655-TRY). Fault Analyzer does not recognise 5655-TRY. Fault Analyzer now recognises 5655-TRY. PI34768
APAR PI28248 Fixes and Enhancements
Problem
Description
Fix
Complete APAR information
1 DD DUMMY allocation is being freed A DD DUMMY allocation is being freed that was not allocated Allocation of preallocated dd dummy no longer occurs PI30651
2 Listing prompt panel loops with quit command When quit is entered on the listing prompt panel Fault Analyzer loops Quit command is corrected to exit interactive analysis PI27137
3 Fault entry list not updated Fault entry list is not updated by import from IDIROBOT Import processing now causes the cache to be updated PI28238
4 Fault Analyzer ISPF interface unable to allocate new history file when copying fault entry using the 'C' line command to a history file that doesn't exist. A check for the existence of the specified history file was not working correctly. The check for existence of the history file has corrected. PI30652
5 Point-of-failure event details not shown in batch report with Detail(S) or Detail(M) option, if point-of-failure event follows the first or only abend event. The design assumed the point-of-failure event would never follow the first abend event. The situation where the point-of-failure event follows the first abend event is now handled correctly. PI30653
6 User is getting INVREQ on EXEC CICS RELEASE because DT's XEIIN GLUE return code is being overridden by FA's XEIIN GLUE FA's XEIIN GLUE - IDIXCE68, for example - is not propagating the GLUE return code from previous XEIIN GLUEs. FA's XEIIN GLUEs have been modified to propagate the return code correctly. PI30654
7 Enterprise PL/I STATIC EXTERNAL variables reported incorrectly when RENT option in effect. WSA not used in STATIC EXTERNAL addressing. WSA and STATIC offset Qcons now used for addressing when RENT option in effect. The LIST option is also required to correctly report these variables. PI30655
8 The user is analyzing a CICS SDUMP and is looking at the IS Domain. FA formats information about the IS domain incorrectly. Changes in CICS have not been reflected in the script that FA uses to format the IS Domain. FA has been updated to reflect the changes in CICS. PI30656
9 IDIS subsystem IDI0082E SQLAllocConnect error messages with reason codes 00f30002, 00f30006 or 00f30012. Fault entry reanalysis was performed on a different MVS image to where it was created, and without the same DB2 system being active. A check has been added to determine if the reason for the DB2 connection error during reanalysis is that the DB2 system is not active on the current MVS image, and if so suppress the IDI0082E message. PI33116
APAR PI24513 Fixes and Enhancements
Problem
Description
Fix
Complete APAR information
1 CICS S878 abend after high level of IDI0066I duplicate abends. Fault Analyzer processing of IDI0066I duplicate message can leave SSIB/SSOB control blocks in storage causing S878. The FREEMAIN process for the fast duplicate test has been corrected. PI27966
2 Recursive IDI0011S messages from Fault Analyzer if IGWFAMS takes an abend. Fault Analyzer calling IGWFAMS for a PDSE space check can give recursive IDI0011S messages if IGWFAMS gest an abend. Code added to protect against recursion if IGWFAMS gets an abend when called for a PDSE space check. PI27861
3 ENQ hang after Fault Analyzer IDI0092S timeout message. If Fault Analyzer IDI0092S timeout processing occurs during an ENQ delay the RFR process could cause an ENQ deadlock. Code has been added to detect the potential deadlock and delay the RFR processing until after the IDIDA TCB is detached. PI27967
4 Abend S0C4 at entry point TbHdr offset X'4A4'. A string was processed beyond the ending null terminator. Processing no longer performed beyond the ending null terminator. PI27866
5 CICS transaction abend analysis suffers ABENDATNI while issuing SEND CONTROL Fault Analyzer issues SEND CONTROL to flush the 3270 buffer out to the terminal. We are advised that this is not needed as FA's RECEIVE BUFFER will cause data to be flushed, and that if there is a problem then RECEIVE BUFFER will get TERMERR and not be abended with ATNI. The SEND CONTROL code has been deleted. PI22844
6 Fault analyzer user analyzing a CICS SDUMP receives an abend in pp_ts_model_summary The CICS region is not fully initialised, and so does not have a TS Domain anchor, causing the abend, The function pp_ts_model_summary has been changed to check that the TS Domain anchor exists before looking for any models. PI23253
7 0C4 in PrtPliStg() when processing variables in unreferenced pages in static storage. Invalid minidump page is de-referenced. Unreferenced minidump addresses checked before de-reference. PI27968
8 POF not identified correctly for a waiting TSO batch job The TSO TCB is not being identified correctly during realtime processing Code is changed to identify a waiting TSO step correctly PI27969
9 Incomplete DB2 information when plan is bound using PKLIST(*.xxxxxxxx.*). When using BIND PLAN with PKLIST(*.xxxxxxxx.*), the SYSPKLIST.LOCATION value changes from blank to '*', which was not handled correctly. The changed value in SYSPKLIST.LOCATION is now being handled correctly. PI27869
10 Fault Analyzer report shows S0CA decimal overflow that was a recoverable event. The Fault Analyzer event list has a S0CA abend event but the decimal overflow is historical and was recovered. The recovered event is removed from the event list. PI27870
11 MSGIDI0053I sends DBCS data to the console. Fault Analyzer is formatting DBCS data with MSGIDI0053I MSGIDI0053I is only issued in English PI25989
12 ABEND0C4 processing CICS DU domain Abend0c4 in pp_cics_summary using zero pointer. pp_cics_summary is changed to not use a zero pointer PI26163
APAR PI19884 Fixes and Enhancements
Problem
Description
Fix
Complete APAR information
1 0C4 in GetStgMem when processing PL/I AUTO/STATIC storage. AUTO/STATIC storage not checked for accessibility. AUTO/STATIC storage now checked for accessibility. PI23648
2 S201 abend in IDISLEEP. An invalid ECB reference was being used, leading to S201 abend. The invalid reference has been removed. PI20506
3 S0C4 when using Fault Analyzer XEIIN GLUE. The FA XEIIN code was not correctly allowing for a failed GETMAIN due to CICS being SOS. A failed GETMAIN is now correctly handled. PI23405
4 Abend S0C4 at entry point CFREE when exiting interactive reanalysis of fault entry. A control block was attempted free'd, which had already been free'd. The problem has been corrected. PI23649
5 When formatting COBOL/5 Associated Storage Areas, variable declarations appear as 'IDENTIFICATION DIVISION' or some other inappropriate value. DWARF does not have a decl_line attribute for internally generated variables (eg. SQL---PLIST). Declared line # set to 1, which indicates an internally generated variable. PI23650
6 SSIB storage not being FREEMAINed. The check for an IDIOFF DD, or a DD as specified in the AdditionalIDIOffDD option, causes an IDIS subsystem call. Due to incorrect register usage, the SSIB storage area was not being FREEMAINed. The incorrect register usage has been fixed so the SSIB will now be correctly FREEMAINed. PI23651
7 ISPF dialog error when specifying two or more adjacent asterisks in the Fault Entry List display history file name field. The specified history file name was not adequately checked for valid syntax before calling the ISPF LMDINIT service. The history file name syntax checking has been improved to prevent the problem. PI23652
8 IDI0144E IDIS error detected at IDIXDCAP:371: TCB 8B0738 S0CA Fault Analyzer IDIS subsystem message IDI0144E followed by IDI0145I IDIS subtask for: IDISCJST terminated. Requesting regions may then hang until the IDIS subsystem is stopped and restarted. Code added to insure the IDISCJST termination cause IDIS to terminate. PI23653
9 IDI0144E IDIS error 0C4 when high activity. Fault Analyzer IDIS subsystem message IDI0144E 0C4 abend after Coupling Facility XCF message delays. The XCF recovery code has been updated to ensure delayed messages are still valid to process. PI23406
10 IDI0005S IDIUTIL:524 Storage allocation for 88 (X'58') bytes failed - processing terminated. A loop occurred due to the absence of a SYSIN DD statement. A SYSIN DD statement is no longer required when all control statements are passed to IDIUTIL via the PARM field. PI22526
11 Use of Fault Analyzer XEIIN exit can cause short on storage conditions. Storage areas GETMAINed by XEIIN code were not being explictly FREEMAINed, which for long running tasks could lead to short on storage conditions. All storage areas are correctly FREEMAINed. PI23654
12 IDISF8136S and IDISF8132S messages issued when LANGX processes XL C/C++ V2.R1 compiler listing. Component ID changed from 5694A01 to 5650ZOS. Component ID 5650ZOS now recognized. PI23638
13 IDILANGX issues message IDISF8154W when encountering COBOL data type DISP-NUM-EDIT. IDILANGX does not recognize the DISP-NUM-EDIT data type. IDILANGX now recognizes the DISP-NUM-EDIT data type. PI22420
14 After access to a fault entry has been attempted, but rejected by the IDIXFXIT exit, subsequent attempts to access other fault entries are incorrectly rejected. The rejected access was incorrectly being remembered for other fault entries, for which access should have been granted. The access to individual fault entries is now being determined correctly. PI23870
APAR PI17013 Fixes and Enhancements
Problem
Description
Fix
Complete APAR information
1 Fault Analyzer event list info for NORENT assembler not useful. NORENT programs with DSAs imbedded in the CSECT, and often using non-standard linkage, are getting no event information. Code added to detect the static DSA and at least show load module and CSECT data in the event list. PI19146
2 The application's last CICS 3270 buffer is not being formatted correctly. The user has a 3270 emulator which, when given a 'F2' or "Read Buffer" command, returns a data stream which contains SBA orders. FA did not have code to handle those SBAs. Fault Analyzer has been altered to handle SBA orders in the Read Buffer data stream. PI15843
3 Abend S0C4 in PliSepStruct when processing constants in SYSDEBUG side file. Constants have a structure parent which can cause them to be processed as structure members. Constants no longer processed as structure members. PI16631
4 Intermittent problem leads to abend S0C4 during execution of Formatting user exit. Fault Analyzer is not correctly handling the abend, which might be expected during normal processing. Fault Analyzer is now handling the abend. PI17241
5 User is performing CICS SDUMP analysis and looking at the CQ Domain. Values in the panels are incorrect. Fault Analyzer is using incorrect control block offsets to obtain the values. Fault Analyzer has been updated to use the correct offsets. PI15010
6 Fault Analyzer ErrorHandler option names might not get honoured if input from an MVS dump. When an MVS dump is used as input to Fault Analyzer to get a fault report on the dump, the ErrorHandler program names might not get recognized correctly because MVS dump input does not trigger FA Binder mapping of modules. The ErrorHandler code will also check entry point name, if program name has not been determined for an event. PI19150
7 Fault Analyzer interactive analysis Listing/Side File Mismatch panel ENTER action for COBOL does not force use of the side file. The pop-up panel reporting Listing/Side File Mismatch indicates ENTER will accept a current COBOL SYSDEBUG file, but it is ignored and no source for that program is presented. The code has been updated to accept the side file when possible. PI19166
8 Reported assembler DSECT has missing fields. DSECT has more fields than can be contained in single LANGX structure record, but only the first LANGX record is processed. Multiple LANGX structure records now processed for large assembler DSECTs. PI17568
9 CICS Container data incorrectly being displayed in ASCII rather than EBCDIC. The count of ASCII and EBCDIC characters was incorrect. The count of ASCII and EBCDIC characters has been corrected. PI19167
10 FA formats too many CICS trace entries. FA processes all the trace entries in a particular trace block. FA is changed to stop formatting once the current timestamp is less than the previous timestamp. PI18082
11 Abend S0C4 in CobCdaSym() when processing DWARF in COBOL/5 load module. Storage re-allocation did not reset pointer into area. Symbol lookup pointer reset when storage area re-allocated. PI19168
12 Message IDI0089I Subsystem IDISLOG RC=8 Rsn=63 IDI0159I SDUMP usage error. Fault Analyzer RFR recovery after IDI0005 storage shortage can get IDI0089I Subsystem IDISLOG RC=8 Rsn=63 SDUMP usage error attempting to do a second SDUMP. The logic is corrected to determine if the RFR dump has already been taken. PI19151
13 Fault Analyzer message IDI0151W for a partial SVC dump not correct. The return and reason code processing for SDUMP is not always correctly reported when issued from IBM Fault Analyzer. Reason code processing corrected. PI18986
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



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 V13R1M0 (UI25080 2015/02/11)


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


(C) Copyright IBM Corp. 2000, 2015.  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

Document information

More support for: Fault Analyzer for z/OS

Software version: 12.1, 13.1

Operating system(s): z/OS

Reference #: 1171963

Modified date: 2013-12-06