|
|
 |
|
Software > Software Development >
|
|
|
|
Latest Fault Analyzer for z/OS Service Information
|
| | | | Answer | How can I sign up to automatically receive email notification when a new PTF is available?
NOTE: Make sure you review the Preventive Sevice 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
For Version 9 PTFs click here
For Version 8 PTFs click here
For Version 7 PTFs click here
For Version 6 PTFs click here
For Version 5 PTFs click here
NOTE: Service for Version 5 was withdrawn as of 4/30/2008.
All available Version 9 Fault Analyzer PTFs and associated APARs (most recent first):
APAR PK92822 Fixes and Enhancements |  | Problem | Description | Fix | Complete APAR information | | 1. | Job type incorrectly determined to be STC for TSO address space, resulting in incorrect Include/Exclude behaviour. | TSO was expected to run under the 3rd TCB in an address space in order for the job type to be set to TSU. | The search for TSO has been extended to all TCBs. |
| | 2. | IDI0047S, CEE3703I HANC Control block damaged. Fault Analyzer with C/C++ program and long names. | Programs using long internal names exceeding 64 characters can get message IDI0047S and CEE3703I HANC control block damage with Fault Analyzer termination. | The internal processing of element names from the Binder has been changed to accommodate maximum length names. | | | 3. | Missing DB2 information in the analysis report for some CICS transactions. | DB2 information was obtained for a different transaction and therefore discarded. | DB2 information is now being obtained for the correct CICS transaction and presented in the analysis report. | | | 4. | Address range invalid message appears for hex-dumped storage range in batch report, but storage is reported correctly by interactive re-analysis. | A storage range may be registered more than once and include descriptor entries that have a length of zero. When a descriptor entry is used to determine the end address of a range, the end address will be invalid (as it is one less than the start address). | Entries with a non-zero length are now used to determine the end address of a storage range. | | | 5. | CFA transaction IVP selection does not do anything. | The code was not allowing for a lower case S to be entered. | Both an upper and lower case S are now accepted | | | 6. | Abend S0C4 at entry point displayFP when displaying large hex-formatted storage section from the interactive reanalysis report. | Reformatting of the display attempted to clear the in-storage buffer to blanks, but the display had become file-paged, resulting in an invalid in-storage buffer being blanked out. | The display clearing has been changed to accommodate both normal and file-paged protocols. | | | 7. | Abend S0C4 at entry point PrtLeOpt offset X'33A'. | An invalid LE CEEOCB data area was being used for display of LE options in effect. | LE options are only displayed when a valid LE CEEOCB data area has been found. | | | 8. | The same PL/I ONCODE condition is shown against multiple PL/I events. | The check for the same PL/I Library Workspace did not allow for a PL/I routine to be calling another language, such as COBOL, before abending in another PL/I subroutine. A PL/I Library | Workspace is now only reported on once, regardless of any intermediate inter-language calls. | | | 9. | IDI0047S IBM Fault Analyzer internal abend 0C4 in CICTRINV. | A storage reference was unchecked and hence was subsequently used in error. | The storage reference is now correctly checked prior to use. | | | 10. | Fault Analyzer with IDISPLI or IDISPLIA usermod installed is incorrectly invoked for PL/I V2R3 ONCODE 4 conditions. | No special check was made for a PL/I ONCODE 4 condition, which should be ignored. | A check has been added to prevent Fault Analyzer from being invoked for a PL/I V2R3 ONCODE 4 condition. | |
APAR PK89333 Fixes and Enhancements | | Problem | Description | Fix | Complete APAR information | | 1. | Compiler listing or side file data sets specified in the pseudo JCL prompt during interactive reanalysis are not being used. | The ISPF LMINIT service failed to allocate a temporary file tailoring data set if the ISPCTLn DDname was pre-allocated due to a trailing null-character following the DDname passed to LMINIT. | Trailing nulls have been replaced by trailing blanks. | | | 2. | Incorrect PL/I or C/C++ source line for offset reported when multiple lines have same offset. | The first source line at the given offset was selected. | The last source line at the given offset is now selected. | | | 3. | Abend S0C4 in FmtPliData when PL/I defined variable is used in program with PUT LIST/DATA. | Symbol entries are located in the CSECT when PUT LIST/DATA is used in PL/I program (otherwise they are located in the SYSDEBUG side file). Symbol entries located in the CSECT must be explicitly located in the minidump storage. | Defined variable is now located in the minidump storage. | | | 4. | Message IDI0095W Unexpected condition found in IDIDODSN:2810: Process error, followed by message IDI0047S and possibly IDI0126I. | An error occurred during the processing of CICS transaction isolation address ranges. | An error in processing of CICS transaction isolation address ranges has been corrected. | | | 5. | Abend S0C4 in PliSepCheck when processing an Enterprise PL/I SYSDEBUG file. | A bad CUI gives invalid offset into debug tables name pool. | The name pool offset is now checked to determine if it is within the debug tables. | | | 6. | Abend S0C4 in load module IDIXDCAP at entry point DDfclose offset X'80'. | An invalid work area address was being used for data set close processing after a failure to open the CEE.SCEERUN LE run-time library. | A check has been added to not attempt closing the LE run-time library if it has not been opened successfully. | | | 7. | Fast Exclude processing of Fault Analyzer is not honoring the LETCB setting if invoked from the IDIXCEE exit. | When called from the IDIXCEE exit, the LETCB flag was not being set ready for Fast Exclude processing. | The code has been corrected to set the LETCB flag. | | | 8. | Abending event appears as first user event, when it should be the last. | Comparison using register 13 values gives wrong result because the hi-order bit is on. | The hi-order bit has been masked out for register comparison. | | | 9. | Message IDI0063W deletion failed, not authorized for faultID, when trying to use 'V' View line command against a fault entry. | When the 'V' line command is issued against a new fault entry, which was created with the DeferredReport option, by a user who has READ but not UPDATE access to the fault entry, they get message IDI0063W instead of the saved report being displayed. | The necessary access rules for generating the saved report for viewing have been changed. |
| | 10. | Wrong machine instruction is reported, even though the PSW gives correct instruction address. | Abend S0C4 program interruption codes 10 and 11 are not extracted from the SDWA, resulting in incorrect adjustment of the instruction address. | Abend S0C4 program interruption codes 10 and 11 are now extracted from the SDWA. | | | 11. | The EQAUEDAT exit is not called to obtain the name of a VS COBOL II compiler listing data set. | The EQAUEDAT exit was only called if the listing data set name was in PROGSUM (which it is not for VS COBOL II). | The EQAUEDAT exit is now called for VS COBOL II (language code 41). | | | 12. | CICS performance problem with Fault Analyzer message IDIS0126I taking IEATDUMP and then message IDI0092S time 4 minutes exceeded subtask canceling. | With large CICS systems and a problem with normal Fault Analyzer processing such as IDI0005S out of storage due to REGION size constraint, then RFR (Recover Fault Recording) TDUMP may time out with IDI0092S message. | The RFR processing has been extended to use SDUMP because of its superior performance over TDUMP. The SDUMP process is contolled by RACF XFACILIT class access. | |
| Problem | Description | Fix | Complete APAR information | | 1. | ISPF messages IDIM000 and IDIM001 not shown with correct text. | The ISPF message member IDIM00 contained old versions of the IDIM000 and IDIM001 messages. | The ISPF messages IDIM000 and IDIM001 have been updated to the current version. | PK89083
PK89085 |
APAR PK83693 Fixes and Enhancements | | Problem | Description | Fix | Complete APAR information | | 1 | Second and subsequent reanalyses of a Recovery Fault Recording (RFR) fault entry does not show the original abend TCB problem. | The Fault Analyzer TCB was being analyzed instead of the original abend TCB. | The original abend TCB is now being correctly determined. | PK83947 | | 2 | Abend in PliSibCheck35 when processing Enterprise PL/I SYSDEBUG side file. | DSA had bad SIF data. | SIB pointed to from SIF is checked, if check fails SIBs are located differently. | PK83939 | | 3 | IDISF8154W issued when COBOL compiler listing has USAGE NATIONAL data items. | Nat-xxxx tokens not recognized in MAP section. | Nat-xxxx tokens now recognized in MAP section. | PK88712 | | 4 | Listing prompt is issued for COBOL side file but source line is not located. | New member name is being used as program CSECT name when creating side file CSECT record. | Program CSECT name parameter corrected. | PK88673 | | 5 | When an invalid member name was supplied in the DSN field on the DSECT panel, no warning message was displayed. | The invalid member was being detected but the appropriate warning message was not being copied to the DSECT panel message field. | Warning message now correctly displayed on DSECT panel. | PK84613 | | 6 | Fault Analyzer SetMaxFaultEntries might fail to delete old entries causing additional entries and out of space on the history file. | An XFACILIT-managed history file, not being managed by the IDIS subsystem, may fail to auto delete via MaxFaultEntries, causing excessive fault entries and out of space problems with the history file. The auto delete authorization was not correctly checked for XFACILIT management. | The authorization check has been corrected. | PK88715 | | 7 | Incorrect highlighting of CICS Trace entries when using default interval (0.128). | The default interval was not explicitly set. | The default interval is now explicitly set. | PK88709 | | 8 | IDI0005S IDIECDOM:221 Storage allocation failed .. - processing terminated. | The length of the VSWA DSECT was not being validated prior to being used, and hence a negative length was used. | The length is now being validated. | PK88710 | | 9 | Fault Analyzer invoked when QUIT ABEND issued in Debug Tool. This does not happen under CICS where analysis is skipped. | The detection of the QUIT ABEND command was only being performed by the Fault Analyzer CICS LE exit. | Both the CICS and non-CICS LE exits now check for the QUIT ABEND command. | PK85988
| | 10 | Deleted fault entries remain shown on Fault Entry List display until the next refresh. | Already deleted fault entries were not being considered correctly when determining the rows to hide for subsequent deleted fault entries further down on the display. | All deleted fault entries are now being removed from the display immediately. | PK86081 | | 11 | IDI0047S IBM Fault Analyzer internal abend S230 and duplicate Recovery Fault Recording fault entries created. | An invalid DEQ is issued during Recovery Fault Recording processing, causing abend S230. The S230 abend causes Fault Analyzer RFR processing to be invoked a second time, resulting in two RFR fault entries instead of one. | The cause of the invalid DEQ has been corrected. | PK88682 | | 12 | Loop in function GetEPLISnt during real-time processing with the DeferredReport option in effect, causing IDI0092S time-out. | The end of a statement number table was not recognized correctly. | The end of the statement number table is now being determined correctly to prevent the loop. | PK88684 | | 13 | Message IDI0047S abend S0C4 in Fault Analyzer dxLocate64. | Possible abend S0C4 in function dxLocate64() during real-time analysis. | Code condition added to correctly manage a special storage pattern reference function and prevent the abend S0C4. | PK88686 | | 14 | No minidump is written to a new fault entry and no message is issued to explain why. | The number of minidump pages about to be written exceeded the expected number due to the use of an unsigned halfword instead of an integer to hold the count. The minidump was subsequently suppressed. | The minidump page count is now held in an integer to prevent the suppression of the minidump if the number of pages exceeds 65,535. | PK88689 | | 15 | IDILANGX gets abend U4000 when pre-allocating sequential output data set. | When the output file is opened, the default record length of 1024 is used because an explicit record length is not specified. | The output file is now opened with a record length of 1562 bytes. | PK86490 | | 16 | Abend S0C4 in dfhs_trace when processing CICS internal trace. | Trace anchor and internal trace blocks contain invalid pointers (possibly as a result of storage violations). | Additional sanity checks performed on pointers. | PK86988 | | 17 | ABEND (CODE 0C4/AKEJ) occurs in IDIXCX53 due to backlevel XPI call with CICS/TS 4.1. | Existing XPI calls in Fault Analyzer exit code not compatible with CICS/TS 4.1. | XPI calls changed to comply with CICS/TS 4.1. | PK88667 | | 18 | No source support when using Enterprise PL/I V3R8M0 compiler listing. | Enterprise PL/I V3R8M0 compiler listing not recognized. | Enterprise PL/I V3R8M0 compiler listing now recognized. | PK87577 | | 19 | Source line point-and-shoot fields locate wrong source line when source file # is not zero (primary source file). | Source display does not use file # when aligning source records. | Source display now uses file # when aligning source records. | PK87850 | | 20 | User is prompted for side file when event is system code. | System modules are not excluded from the side file prompt. | DSN*, IBM*, and IRT* modules explicitly excluded when prompting for assembler language side file. | PK87751 | | 21 | Fault Analyzer history file abend SD37. | History files with less than 20 fault entries and using the SetMaxFaultEntries(nnn,AUTO) automatic space management might get abend SD37 or SB14 when writing to the history file. | The AUTO space management process continues to manage when the number of entries in the history file is less then 20, but puts out a message to indicate that the number of entries is below 20. | PK88721 | | 22 | Abend S0C4 in BldLX when processing Enterprise PL/I SYSDEBUG file. | The address of the structure parent is taken but this changes when the symbol lookup table is reallocated to a larger area. | The offset of the structure parent is now used instead of the address to locate the symbol lookup table entry. | PK88680 | | 23 | Abend S0C4 in asm_rel_stg when assembler program has no in-scope DSECTs. | The DSECT info array pointer is not checked. | The DSECT info array pointer is now checked before processing. | PK88723 | | 24 | Abend S0C4 in Extract_COBOL_Map when processing COBOL compiler listing with IDILANGX. | Data items in MAP section with LineID of zero cause non-existent source record to be scanned for PIC declaration. | Data items in MAP section with LineID of zero are no longer scanned for PIC declarations. | PK88164 | | 25 | CEE3204S Code=0C4 in DSNALLOC compile unit offset +064A when using IDILANGP utility against a SYSDEBUG side file. | The IDILANGP print utility might get abend S0C4 in DSNALLOC +064A when attempting to allocate a SYSDEBUG side file because of an input parameter list mismatch. | The DSNALLOC() input parameter list has been corrected. | PK88263 | | 26 | SVC dump from IRAVTABD with S0C4 in Fault Analyzer routine SETFARBB. | The Fault Analyzer SETFARBB function was not clearing the high order byte of a register before inserting the 24 bit address of a CDE entry, consequently getting an intermittent 0C4 when testing the CDE name. | The high order byte has been cleared. | PK88731 | | 27 | Fault Analyzer messages might not display on TSO sessions.
| If CONSOLE00 DEFAULT ROUTCDE is set and does not include ROUTCDE=11, then Fault Analyzer messages, such as IDI0005S, will not show in the TSO session. | Explicit ROUTCDE=11 added to WTO to ensure TSO message display. | PK88864 |
APAR PK79442 Fixes and Enhancements | | Problem | Description | Fix | Complete APAR information | | 1 | Abend S0C4 in IDIXDCAP at offset X'9E70'. Might include DB2 abend S04E. | If Fault Analyzer is called for an abending TCB which is not running key 8, and LE is not available from LKNLST, then the DDFOPENR routine will get abend S0C4. | Tests added to detect non key 8 situation, and use the appropriate key for GETMAINs. | PK83204 | | 2 | Abend S0C4 in module IDIXDCAP entry point JOBINFO. | The JOBINFO function in IDIXDCAP might abend S0C4 if the LE anchor vector is overlayed. | LE check processing changed to withstand a storage overlay. | PK83213 | | 3 | Debug Tool abend S0C4 when calling Fault Analyzer via CALL %FA when //IDIOFF DD DUMMY is set. | The IDISNAP Fault Analyzer interface is not restoring R11 when //IDIOFF DD is set. | Correct restore of registers is now done when //IDIOFF DD is set. | PK83218 | | 4 | Although the interactive reanalysis option to display a panel to alter the allocated data sets is set to 'Y', no such panel is being displayed. | The ISPF EDIT service failed as it was being passed a tempopary data set from the ISPF FTOPEN service. | The ISPF LMINIT service is now used to assign a data ID based on the DDname from the temporary data set allocation, which is used instead of the data set name with the ISPF EDIT service. | PK79807 | | 5 | IDI0005S insufficient storage message from Fault Analyzer IDIS subsystem. | Message IDI0005S can occur from the IDIS subsystem due to a slow storage leak. | The XCF recovery logic storage free has been corrected. | PK83269 | | 6 | When re-analyzing a SVC dump containing a C program, Fault Analyzer does not process side files supplied via the IDILC DD, or prompt for them interactively. | When the binder is not available, Fault Analyzer does not have CSECT information, which is required for side file processing. | CSECT information for a C compilation unit is now synthesized when the binder is not available. | PK83273 | | 7 | IDILANGX return code 1551 for large listing. | A listing with a very large number of symbols might not be able to be processed by IDILANGX and get a return code of 1551. | The array growth algorithm has been changed. | PK83282 | | 8 | Abend S0C4 in module IDICBIMS at offset X'122C'. | The address of an IMS control block was not valid, causing abend S0C4 when attempting to access the storage. | Checks have been added for validation of the control block storage prior to accessing it. | PK83278 | | 9 | IDI0092S time out and performance problem if Fault Analyzer run with LE HEAPCHK(ON). | If an environment is set up with HEAPCHK(ON) as the default, then there might be siginficant performance overhead with Fault Analyzer execution. | Options in Fault Analyzer have been changed to suppress HEAPCHK(ON) for its execution. | PK83286 |
APAR PK74751 Fixes and Enhancements | | Problem | Description | Fix | Complete APAR information | | 1 | Abend S0C4 in PliSepSym when processing Enterprise PL/I SYSDEBUG side file. | PL/I PUT STRING statement causes symbol name pool to reside in program CSECT (instead of SYSDEBUG file), some of this storage might not be available. | Entire program and static CSECT storage now located. | PK77503
| | 2 | Fault Analyzer IDIS subsystem intermittent XCF request delays of around 15 seconds. | When activity for a history file $$INDEX cache in the IDIS subsystem resumes activity, there can be an unnecessary 15 second delay. | The task resume process with XCF active now correctly detects if another IDIS server currently has the member actively cached. | PK79058 | | 3 | CICS transaction RFR fault entry reanalysis results in "No abend could be determined--possible loop or wait situation" and unable to view saved report using "V". | When performing analysis of a CICS transaction abend Recovery Fault Recording (RFR) fault entry, then the original attributes of the fault are not being obtained correctly. | The correct attributes of the original fault are now being used to resume the interrupted real-time analysis. | PK77086 | | 4 | Abend S0C4 in IDILANGX function ADD_PLIST when processing Enterprise PL/I compiler listing. | The block info structure does not have a symbol ID specified, resulting in bad pointer. | The block info structure is now not processed if the symbol ID is not set. | PK79064 | | 5 | Abend S0C4 in GetEPLISnt when processing CICS transaction abend in Enterprise PL/I program, with DeferredReport option in effect. | Incorrect handling of statement number table sections (a large function might have multiple sections). | The statement number table section processing has been corrected. | PK79065 | | 6 | Fault Analyzer loops in function WhatsNext() when processing COBOL program abend. | WhatsNext() continually returns the same base locator when the highest address in the dictionary is a COBOL base locator. | WhatsNext() now checks for same base locator being returned. | PK79069 | | 7 | Message IDI0090E IRXEXEC rc=20 when attempting to run a REXX Notification user exit for IMS ImageFast duplicates in the IDIS subsystem. | The IDIEXEC DDname was not allocated. | The IDIEXEC DDname is now correctly being allocated prior to running the REXX user exit. | PK79070 | | 8 | Enterprise PL/I structure member has incorrect offset when variable with same name is used as a parameter. | When multiple instances of a variable name are declared in a block, an incorrect instance might be used. | The correct instance of the variable is now used. | PK79075 | | 9 | Enterprise PL/I BIN(63) and BIN(64) variables are reported as BIN(31). | IDILANGX does not recognize BIN(63) and BIN(64) data types. | IDILANGX now recognizes BIN(63) and BIN(64) data types. | PK79085 | | 10 | Incorrect source line is located from stmt# point-and-shoot field when Enterprise PL/I program is compiled with STMT and NONUMBER options. | The source info point-and-shoot field specifies both line# and stmt#, but only line# is used to align source records. When STMT and NONUMBER options are in effect, there could be multiple source lines with the same line#. | When both stmt# and line# are specified, both are checked when aligning source records. | PK79115 | | 11 | Cursor incorrectly positioned on second char of FIND argument when used from the Saved Report display. | The Saved Report display differs from other displays in that the leftmost column does not always contain an attribute or blank character. This exception was not being considered when the cursor was positioned for a successful FIND command. | The cursor is now being positioned at the first (or only) character of an argument specified on a successful FIND command. | PK79149 | | 12 | Abend S0C4 when reporting Enterprise PL/I EXTERNAL variables during re-analysis of fault created with DeferredReport in effect. | EXTERNAL variable's data not in minidump. | DeferredReported processing corrected for Enterprise PL/I EXTERNAL variables. | PK79155
| | 13 | Abend S0C4 while processing VS COBOL II event. | If there is no CLLE for VS COBOL II program, essential information about the TGT (eg. length) is unavailable, causing an abend S0C4. | Processing is bypassed when a VS COBOL II TGT is not available via the CLLE. | PK79156 | | 14 | Abend S0C1 or other random problems due to an overlay with data of x'40000000' after a Fault Analyzer IDIS subsystem hang. | If the IDIS Fault Analyzer subsystem is delayed or hung such that return x-memory POST processing gets abend S102 or other problems, it is possible, depending on requestor memory reuse, to get random storage overlays. CICS abend processing is susceptible to this with IDIS running. | Validation of the return x-memory POST conditions checked before return. | PK78818 | | 15 | DFHSR0606 Abend (23E/AKEB) detected after IDICALOC LOCFRESL DETACHing orphan TCB terminating CICS. | CICS DUMPCODE: SR0606 and termination after Fault Analyzer task management IDICALOC LOCFRESL DETACHing orphan TCB. The TCB address being detached is invalid. | Messages corrected to display the correct TCB=address and validation improved to prevent the condition. | PK78978 | | 16 | DFHAP0701 An abend (code 0C4/AKEA) has occurred in exit IDIXCX53 at exit point XPCABND. | The Fault Analyzer IDIXCX53 exit, when requesting CICS GETMAIN storage, did not correctly handle the not available condition and caused an abend S0C4 which can terminate CICS. | The GETMAIN return checking has been corrected. | PK79160 |
APAR PK78514 Fixes and Enhancements | | Problem | Description | Fix | Complete APAR information | | 1 | The Japanese translation of the V9.1 Fault Analyzer User's Guide and Reference, SC19-2538-00, was not available at the time of the V9.1 Japanese feature GA.
| The most current Japanese edition of the V8.1 Fault Analyzer User's Guide and Reference was shipped on the GA tape. | The Japanese translation of the V9.1 Fault Analyzer User's Guide and Reference GA edition, SC19-2538-00, is now provided in
IDI.SIDIDJPN(IDIUGPDF). | PK78514 |
APAR PK74114 Fixes and Enhancements | | Problem | Description | Fix | Complete APAR information | | 1 | 0C4 in SearchDS while processing Enterprise PL/I program. | SERVICE string is an odd number of characters requiring an additional byte for halfword alignment. | Halfword alignment added when processing SERVICE string and subsequent saved options string. | PK74205 | | 2 | CICS Storage Violation SM0102 with Program IDIXCX53. | A trailing SAA is overlayed by Fault Analyzer IDIXCX53 when CICS trace data gathering fills at a buffer boundary. | The boundary code has been corrected to allow for the additional halfword end of records field. | PK74204 |
APAR PK72608 Fixes and Enhancements | | Problem | Description | Fix | Complete APAR information | | 1 | Message IDI0144E IDIS error detected at IDIXCEE:241 TCB 9E5298 S0C4. | Intermittent message IDI0144E from Fault Analyzer IDIS subsystem due to XCF message buffer length exceeded, causing storage to be overwritten. | The buffer length checking has been corrected to prevent the overwrite. | PK73356 | | 2 | Dynamic allocation of dataset with HLQ of SILLY99 when Fault Analyzer is invoked. 3 runtime with ++USERMOD IDISPLI and executing in 24-bit mode. | The code which checks for a suitable operating environment was dynamically allocating data set SILLY99.DATA88.SET77.NAME66.CHECK55, which was unnecessary. | The dynamic allocation has been removed. | PK72608 | | 3 | When a structure parameter is passed to a PL/I program which was compiled with PL/I for MVS & VM, the structure member offsets in the called procedure are zero. | PL/I for MVS & VM does not provide mapping for structure parameters, offsets appear as "ADJ" and total lengths as "PARAM". | Basic structure mapping is now performed by IDILANGX for parameter structures. | PK73361 | | 4 | PL/I event shows empty Associated Storage Areas display. | No variables have been declared in an internal PL/I procedure. | New hotspot added to give access to caller's storage areas. | PK73305 | | 5 | IDIUTIL RefreshCache failed. rc=FFFFFFFF, message IDI0095W "Unexpected condition found in IDICUSUB:2653: Hist DEQ Error", and rc=2000 completion. | The use of a substitution variable in a history file input data set name can trigger a number of different errors, depending on the IDIUTIL commands being used, due to the late resolution of the real name. | The variable substitution is now resolved at input before continuing processing. | PK73305 | | 6 | Fault Analyzer loops when processing variably located data items in a COBOL program. | The variably located data (BLV) has a bad address (eg. 0xFFFFFFFC). | The code has been changed to handle invalid BLV addresses. | PK73360 | | 7 | Message IDI0020W issued if the NoErrorHandler option is specified. | The NoErrorHandler option is not recognized as a valid option. | The NoErrorHandler option is now recognized as a valid option. | PK73287 | | 8 | Fault Analyzer abends when processing PL/I external variables. | The static CSECT length had been determined incorrectly. | The static CSECT length is now being determined correctly. | PK73056 | | 9 | Message IDI0005S IDIKEY:553 Storage allocation failed. | Analyzing a SYSMDUMP of an LE abend, a bad pointer results in an incorrect storage allocation being attempted. | The call from DSAchain() had a bad KANCHOR pointer, which is now guarded against. | PK73357 | | 10 | On reanalysis of fault entry created during CICS system dump analysis, data is missing from the storage violation report. | CICS internal trace pages are not written to the minidump when a fault entry is created from the SVC dump. Should the dump subsequently be deleted, the trace pages are no longer available. | The internal trace table is now written to the minidump when the user creates a fault entry. | PK72608 | | 11 | IBM002I message when running PL/I | With Fault Analyzer usermod IDISPLI and the PL/I 2.3 runtime, an abend can occur giving message IBM002I if the execution mode is AMODE 24. | The usermod is updated to accomodate AMODE 24. | PK73283 |
All available Version 8 Fault Analyzer PTFs and associated APARs (most recent first):
PTF | AVAILABILITY DATE | PREREQUISITE PTFs | SUPERCEDES THESE PTFs | APAR(s) THIS PTF FIXES | | | | | | English:
UK50298 | 2009/09/25 | | UK48746 | PK92823 PK92825 PK96767 PK93721 PK93881 PK96771 PK94115 PK94658 PK96778 PK96781 | | | | | | English:
UK48746 | 2009/07/31 | | UK47455 UK45219 UK43372 UK41024 UK40617 UK39318 UK38412 UK36737 UK35659 UK35125 UK33904 UK30777 | PK89334 PK88877 PK92446 PK89829 PK91296 PK89965 PK89917 PK92461 PK92462 PK88546 PK92456 PK92098 PK92471 | | | | | | Japanese:
UK47748 | 2009/07/01 | UK38320 | | | Korean:
UK47751 | | | | | | | | English:
UK47455 | 2009/06/18 | UK45219 UK41024 | | PK83694 PK83943 PK88828 PK84438 PK84614 PK88708 PK88716 PK88720 PK88675 PK88677 PK86190 PK86192 PK86452 PK86545 PK88695 PK88699 PK88711 PK88705 PK87766 PK87879 PK88708 PK88707 PK86490 PK88727 PK88702 PK88730 PK88263 | | | | | | English:
UK45219 | 2009/03/31 | UK41024 | UK43372 | PK79443 PK77614 PK83217 PK79924 PK79808 PK83279 PK83287 PK83283 PK83233 | | | | | | English:
UK43372 | 2009/01/28 | UK41024 | | PK74745 PK74551 PK77504 PK77084 PK77502 PK77501 PK77331 PK77726 PK77833 PK77838 PK78220 PK79055 PK78503 PK78803 PK78975 PK79180 PK77834 PK79181 | | | | | | English:
UK41024 | 2008/10/29 | | UK40617 UK39318 UK38412 UK36737 UK35659 UK35125 UK33904 UK30777 | | | | | | | English:
UK40617 | 2008/10/15 | | UK39318 UK38412 UK36737 UK35659 UK35125 UK33904 UK30777 | PK72175 PK72408 PK70096 PK72372 PK73197 PK73058 PK73074 | | | | | | English:
UK39318 | 2008/09/03 | UK36737 UK35659 UK30777 | UK38412 | PK69687 PK69817 PK70037 PK69865 PK69788 PK70367 PK70564 | | | | | | English:
UK38412 | 2008/07/30 | UK36737 UK35659 UK30777 | | PK67040 PK67309 PK67425 PK67449 PK67517 PK69537 PK69556 PK69585 PK69589 PK69252 PK68983 PK65072 | Japanese:
UK38320 | | | | | | | | English:
UK36737 | 2008/05/31 | UK35659 UK30777 | | PK64683 PK66646 PK66644 PK66647 PK65639 PK66651 PK65764 PK65918 PK66669 PK66219 PK65842 PK66106 | | | | | | English:
UK35659 | 2008/04/22 | UK30777 | UK35125 UK33904 | PK64242 PK64603 PK64615 PK64462 PK64608 PK64619 PK64659 | | | | | | English:
UK35125 | 2008/04/08 | UK30777 | UK33904 | PK61873 PK63942 PK63785 PK63791 PK63802 PK63849 PK63862 PK63372 PK62476 PK62542 PK63706 PK63175 PK63318 PK63870 PK63709 PK63712 PK63722 PK63879 | | | | | | English:
UK33904 | 2008/02/29 | UK30777 | | PK56115 PK61604 PK61446 PK61456 PK61465 PK60745 PK61470 PK61471 PK57659 PK57853 PK57980 PK61525 PK61539 PK61549 PK58894 PK58959 PK59466 PK61568 PK61585 PK59783 PK60063 PK61591 PK61592 PK61178 PK60814 PK61593 | | | | | | English:
UK30777 | 2007/11/09 | | | PK53632 PK55099 PK55040 PK55108 PK55144 PK55163 PK55179 PK55120 PK55404 PK55431 PK55446 PK55480 PK55486 |
APAR PK92822 Fixes and Enhancements | | Problem | Description | Fix | Complete APAR information | | 1. | Several options selected from the Interactive Reanalysis Report display perform no action. | Unitialized automatic storage resulted in flags being set on which caused the functions invoked by the options to receive invalid data and therefore quit without displaying the expected report data. | The automatic storage variables affected have been initialized. | PK92825
| | 2. | Job type incorrectly determined to be STC for TSO address space, resulting in incorrect Include/Exclude behavior. | TSO was expected to run under the 3rd TCB in an address space in order for the job type to be set to TSU. | The search for TSO has been extended to all TCBs. | PK96767 | | 3. | Address range invalid message appears for hex-dumped storage range in batch report, but storage is reported correctly by interactive re-analysis. | A storage range may be registered more than one and include descriptor entries that have a length of zero. When a descriptor entry is used to determine the end address of a range, the end address will be invalid (as it is one less than the start address). | Entries with a non-zero length are now used to determine the end address of a storage range. | PK93721 | | 4. | Missing DB2 information in the analysis report for some CICS transactions. | DB2 information was obtained for a different transaction and therefore discarded. | DB2 information is now being obtained for the correct CICS transaction and presented in the analysis report. | PK93881 | | 5. | CFA transaction IVP selection does not do anything. | The code was not allowing for a lower case S to be entered. | Both an upper and lower case S are now accepted | PK96771 | | 6. | Abend S0C4 at entry point displayFP when displaying large hex-formatted storage section from the interactive reanalysis report. | Reformatting of the display attempted to clear the in-storage buffer to blanks, but the display had become file-paged, resulting in an invalid in-storage buffer being blanked out. | The display clearing has been changed to accommodate both normal and file-paged protocols. | PK94115 | | 7. | Abend S0C4 at entry point PrtLeOpt offset X'33A'. | An invalid LE CEEOCB data area was being used for display of LE options in effect. | LE options are only displayed when a valid LE CEEOCB data area has been found. | PK94658 | | 8. | The same PL/I ONCODE condition is shown against multiple PL/I events. | The check for the same PL/I Library Workspace did not allow for a PL/I routine to be calling another language, such as COBOL, before abending in another PL/I subroutine. | A PL/I Library Workspace is now only reported on once, regardless of any intermediate inter-language calls. | PK96778 | | 9. | Fault Analyzer with IDISPLI or IDISPLIA usermod installed is incorrectly invoked for PL/I V2R3 ONCODE 4 conditions. | No special check was made for a PL/I ONCODE 4 condition, which should be ignored. | A check has been added to prevent Fault Analyzer from being invoked for a PL/I V2R3 ONCODE 4 condition. | PK96781 |
APAR PK89334 Fixes and Enhancements | | Problem | Description | Fix | Complete APAR information | | 1. | Compiler listing or side file data sets specified in the pseudo JCL prompt during interactive reanalysis are not being used. | The ISPF LMINIT service failed to allocate a temporary file tailoring data set if the ISPCTLn DDname was pre-allocated due to a trailing null-character following the DDname passed to LMINIT. | Trailing nulls have been replaced by trailing blanks. | | | 2. | Incorrect PL/I or C/C++ source line for offset reported when multiple lines have same offset. | The first source line at the given offset was selected. | The last source line at the given offset is now selected. | | | 3. | Abend S0C4 in FmtPliData when PL/I defined variable is used in program with PUT LIST/DATA. | Symbol entries are located in the CSECT when PUT LIST/DATA is used in PL/I program (otherwise they are located in the SYSDEBUG side file). Symbol entries located in the CSECT must be explicitly located in the minidump storage. | Defined variable is now located in the minidump storage. | | | 4. | Message IDI0095W Unexpected condition found in IDIDODSN:2810: Process error, followed by message IDI0047S and possibly IDI0126I. | An error occurred during the processing of CICS transaction isolation address ranges. | An error in processing of CICS transaction isolation address ranges has been corrected. | | | 5. | Abend S0C4 in PliSepCheck when processing an Enterprise PL/I SYSDEBUG file. | A bad CUI gives invalid offset into debug tables name pool. | The name pool offset is now checked to determine if it is within the debug tables. | | | 6. | Abend S0C4 in load module IDIXDCAP at entry point DDfclose offset X'80'. | An invalid work area address was being used for data set close processing after a failure to open the CEE.SCEERUN LE run-time library. | A check has been added to not attempt closing the LE run-time library if it has not been opened successfully. | | | 7. | Fast Exclude processing of Fault Analyzer is not honoring the LETCB setting if invoked from the IDIXCEE exit. | When called from the IDIXCEE exit, the LETCB flag was not being set ready for Fast Exclude processing. | The code has been corrected to set the LETCB flag. | | | 8. | Abending event appears as first user event, when it should be the last. | Comparison using register 13 values gives wrong result because the hi-order bit is on. | The hi-order bit has been masked out for register comparison. | | | 9. | Message IDI0063W deletion failed, not authorized for faultID, when trying to use 'V' View line command against a fault entry. | When the 'V' line command is issued against a new fault entry, which was created with the DeferredReport option, by a user who has READ but not UPDATE access to the fault entry, they get message IDI0063W instead of the saved report being displayed. | The necessary access rules for generating the saved report for viewing have been changed. |
| | 10. | Wrong machine instruction is reported, even though the PSW gives correct instruction address. | Abend S0C4 program interruption codes 10 and 11 are not extracted from the SDWA, resulting in incorrect adjustment of the instruction address. | Abend S0C4 program interruption codes 10 and 11 are now extracted from the SDWA. | | | 11. | The EQAUEDAT exit is not called to obtain the name of a VS COBOL II compiler listing data set. | The EQAUEDAT exit was only called if the listing data set name was in PROGSUM (which it is not for VS COBOL II). | The EQAUEDAT exit is now called for VS COBOL II (language code 41). | | | 12. | CICS performance problem with Fault Analyzer message IDIS0126I taking IEATDUMP and then message IDI0092S time 4 minutes exceeded subtask canceling. | With large CICS systems and a problem with normal Fault Analyzer processing such as IDI0005S out of storage due to REGION size constraint, then RFR (Recover Fault Recording) TDUMP may time out with IDI0092S message. | The RFR processing has been extended to use SDUMP because of its superior performance over TDUMP. The SDUMP process is contolled by RACF XFACILIT class access. | |
| Problem | Description | Fix | Complete APAR information | | 1. | ISPF messages IDIM000 and IDIM001 not shown with correct text. | The ISPF message member IDIM00 contained old versions of the IDIM000 and IDIM001 messages. | The ISPF messages IDIM000 and IDIM001 have been updated to the current version. | PK89084
PK89086 |
APAR PK83694 Fixes and Enhancements | | Problem | Description | Fix | Complete APAR information | | 1 | Second and subsequent reanalyses of a Recovery Fault Recording (RFR) fault entry does not show the original abend TCB problem. | The Fault Analyzer TCB was being analyzed instead of the original abend TCB. | Problem Conclusion: 01. The original abend TCB is now being correctly determined. | PK83943
| | 2 | Abend in PliSibCheck35 when processing Enterprise PL/I SYSDEBUG side file. | DSA had bad SIF data. | SIB pointed to from SIF is checked, if check fails SIBs are located differently. | PK88828 | | 3 | Listing prompt is issued for COBOL side file but source line is not located. | New member name is being used as program CSECT name when creating side file CSECT record. | Program CSECT name parameter corrected. | PK84438 | | 4 | When an invalid member name was supplied in the DSN field on the DSECT panel, no warning message was displayed. | The invalid member was being detected but the appropriate warning message was not being copied to the DSECT panel message field. | Warning message now correctly displayed on DSECT panel. | PK84614 | | 5 | Fault Analyzer SetMaxFaultEntries might fail to delete old entries causing additional entries and out of space on the history file. | An XFACILIT-managed history file, not being managed by the IDIS subsystem, may fail to auto delete via MaxFaultEntries, causing excessive fault entries and out of space problems with the history file. The auto delete authorization was not correctly checked for XFACILIT management. | The authorization check has been corrected. | PK88708 | | 6 | Incorrect highlighting of CICS Trace entries when using default interval (0.128). | The default interval was not explicitly set. | The default interval is now explicitly set. | PK88716 | | 7 | IDI0005S IDIECDOM:221 Storage allocation failed .. - processing terminated. | The length of the VSWA DSECT was not being validated prior to being used, and hence a negative length was used. | The length is now being validated. | PK88720 | | 8 | Fault Analyzer invoked when QUIT ABEND issued in Debug Tool. This does not happen under CICS where analysis is skipped. | The detection of the QUIT ABEND command was only being performed by the Fault Analyzer CICS LE exit. | Both the CICS and non-CICS LE exits now check for the QUIT ABEND command. | PK88675 | | 9 | Deleted fault entries remain shown on Fault Entry List display until the next refresh. | Already deleted fault entries were not being considered correctly when determining the rows to hide for subsequent deleted fault entries further down on the display. | All deleted fault entries are now being removed from the display immediately. | PK88677 | | 10 | IDI0047S IBM Fault Analyzer internal abend S230 and duplicate Recovery Fault Recording fault entries created. | An invalid DEQ is issued during Recovery Fault Recording processing, causing abend S230. The S230 abend causes Fault Analyzer RFR processing to be invoked a second time, resulting in two RFR fault entries instead of one. | The cause of the invalid DEQ has been corrected. | PK86190 | | 11 | Loop in function GetEPLISnt during real-time processing with the DeferredReport option in effect, causing IDI0092S time-out. | The end of a statement number table was not recognized correctly. | The end of the statement number table is now being determined correctly to prevent the loop. | PK86192 | | 12 | Message IDI0047S abend S0C4 in Fault Analyzer dxLocate64. | Possible abend S0C4 in function dxLocate64() during real-time analysis. | Code condition added to correctly manage a special storage pattern reference function and prevent the abend S0C4. | PK86452 | | 13 | No minidump is written to a new fault entry and no message is issued to explain why. | The number of minidump pages about to be written exceeded the expected number due to the use of an unsigned halfword instead of an integer to hold the count. The minidump was subsequently suppressed. | The minidump page count is now held in an integer to prevent the suppression of the minidump if the number of pages exceeds 65,535. | PK86545 | | 14 | Abend S0C4 in dfhs_trace when processing CICS internal trace. | Trace anchor and internal trace blocks contain invalid pointers (possibly as a result of storage violations). | Additional sanity checks performed on pointers. | PK88695 | | 15 | ABEND (CODE 0C4/AKEJ) occurs in IDIXCX53 due to backlevel XPI call with CICS/TS 4.1. | Existing XPI calls in Fault Analyzer exit code not compatible with CICS/TS 4.1. | XPI calls changed to comply with CICS/TS 4.1. | PK88699 | | 16 | Fault Analyzer history file abend SD37. | History files with less than 20 fault entries and using the SetMaxFaultEntries(nnn,AUTO) automatic space management might get abend SD37 or SB14 when writing to the history file. | The AUTO space management process continues to manage when the number of entries in the history file is less then 20, but puts out a message to indicate that the number of entries is below 20. | PK88711 | | 17 | Source line point-and-shoot fields locate wrong source line when source file # is not zero (primary source file). | Source display does not use file # when aligning source records. | Source display now uses file # when aligning source records. | PK88705 | | 18 | 0C4 in BldLX when processing Enterprise PL/I SYSDEBUG file. | Address of structure parent taken but this changes when symbol lookup table is reallocated to larger area. | Offset of structure parent now used to locate symbol lookup table entry. | PK87766 | | 19 | Abend S0C4 in asm_rel_stg when assembler program has no in-scope DSECTs. | The DSECT info array pointer is not checked. | The DSECT info array pointer is now checked before processing. | PK87879 | | 20 | Fault Analyzer SetMaxFaultEntries might fail to delete old entries causing additional entries and out of space on the history file. | An XFACILIT-managed history file, not being managed by the IDIS subsystem, may fail to auto delete via MaxFaultEntries, causing excessive fault entries and out of space problems with the history file. The auto delete authorization was not correctly checked for XFACILIT management. | The authorization check has been corrected. | PK88708 | | 21 | IDISF8154W issued when COBOL compiler listing has USAGE NATIONAL data items. IDISF8154W issued when COBOL compiler listing has USAGE NATIONAL data items. | Nat-xxxx tokens not recognized in MAP section. | Nat-xxxx tokens now recognized in MAP section. | PK88707 | | 22 | IDILANGX gets abend U4000 when pre-allocating sequential output data set. | When the output file is opened, the default record length of 1024 is used because an explicit record length is not specified. | The output file is now opened with a record length of 1562 bytes. | PK86490 | | 23 | Abend S0C4 in Extract_COBOL_Map when processing COBOL compiler listing with IDILANGX. | Data items in MAP section with LineID of zero cause non-existent source record to be scanned for PIC declaration. | Data items in MAP section with LineID of zero are no longer scanned for PIC declarations. | PK88727 | | 24 | No source support when using Enterprise PL/I V3R8M0 compiler listing. | Enterprise PL/I V3R8M0 compiler listing not recognized. | Enterprise PL/I V3R8M0 compiler listing now recognized. | PK88702 | | 25 | SVC dump from IRAVTABD with S0C4 in Fault Analyzer routine SETFARBB. | The Fault Analyzer SETFARBB function was not clearing the high order byte of a register before inserting the 24 bit address of a CDE entry, consequently getting an intermittent 0C4 when testing the CDE name. | The high order byte has been cleared. | PK88730 | | 26 | CEE3204S Code=0C4 in DSNALLOC compile unit offset +064A when using IDILANGP utility against a SYSDEBUG side file. | The IDILANGP print utility might get abend S0C4 in DSNALLOC +064A when attempting to allocate a SYSDEBUG side file because of an input parameter list mismatch. | The DSNALLOC() input parameter list has been corrected. | PK88263 | | 27 | Fault Analyzer messages might not display on TSO sessions. | If CONSOLE00 DEFAULT ROUTCDE is set and does not include ROUTCDE=11, then Fault Analyzer messages, such as IDI0005S, will not show in the TSO session. | Explicit ROUTCDE=11 added to WTO to ensure TSO message display. | PK83694 |
APAR PK79443 Fixes and Enhancements | | Problem | Description | Fix | Complete APAR information | | 1 | Abend S0C4 in IDIXDCAP at offset X'9E70'. Might include DB2 abend S04E. | If Fault Analyzer is called for an abending TCB which is not running key 8, and LE is not available from LKNLST, then the DDFOPENR routine will get abend S0C4. | Tests added to detect non key 8 situation, and use the appropriate key for GETMAINs. |
| | 2 | Abend S0C4 in module IDIXDCAP entry point JOBINFO. | The JOBINFO function in IDIXDCAP might abend S0C4 if the LE anchor vector is overlayed. | LE check processing changed to withstand a storage overlay. | | | 3 | Debug Tool abend S0C4 when calling Fault Analyzer via CALL %FA when //IDIOFF DD DUMMY is set. | The IDISNAP Fault Analyzer interface is not restoring R11 when //IDIOFF DD is set. | Correct restore of registers is now done when //IDIOFF DD is set. | | | 4 | Although the interactive reanalysis option to display a panel to alter the allocated data sets is set to 'Y', no such panel is being displayed. | The ISPF EDIT service failed as it was being passed a tempopary data set from the ISPF FTOPEN service. | The ISPF LMINIT service is now used to assign a data ID based on the DDname from the temporary data set allocation, which is used instead of the data set name with the ISPF EDIT service. | | | 5 | Abend S0C4 in module IDICBIMS at offset X'122C'. | The address of an IMS control block was not valid, causing abend S0C4 when attempting to access the storage. | Checks have been added for validation of the control block storage prior to accessing it. | | | 6 | IDI0092S time out and performance problem if Fault Analyzer run with LE HEAPCHK(ON). | If an environment is set up with HEAPCHK(ON) as the default, then there might be siginficant performance overhead with Fault Analyzer execution. | Options in Fault Analyzer have been changed to suppress HEAPCHK(ON) for its execution. | | | 7 | IDILANGX return code 1551 for large listing. | A listing with a very large number of symbols might not be able to be processed by IDILANGX and get a return code of 1551. | The array growth algorithm has been changed. | | | 8 | IDI0005S insufficient storage message from Fault Analyzer IDIS subsystem. | Message IDI0005S can occur from the IDIS subsystem due to a slow storage leak. | The XCF recovery logic storage free has been corrected. | |
APAR PK74745 Fixes and Enhancements | | Problem | Description | Fix | Complete APAR information | | 1 | Dump Storage display FIND command loop. | An error caused the search for a specified string to re-start from address zero after not finding the string before the end of available storage. | The error has been corrected to prevent the search from wrapping. | | | 2 | Fault Analyzer IDIS subsystem intermittent XCF request delays of around 15 seconds. | When activity for a history file $$INDEX cache in the IDIS subsystem resumes activity, there can be an unnecessary 15 second delay. | The task resume process with XCF active now correctly detects if another IDIS server currently has the member actively cached. | | | 3 | CICS transaction RFR fault entry reanalysis results in "No abend could be determined--possible loop or wait situation" and unable to view saved report using "V". | When performing analysis of a CICS transaction abend Recovery Fault Recording (RFR) fault entry, then the original attributes of the fault are not being obtained correctly. | The correct attributes of the original fault are now being used to resume the interrupted real-time analysis. | | | 4 | Abend S0C4 in GetEPLISnt when processing CICS transaction abend in Enterprise PL/I program, with DeferredReport option in effect. | Incorrect handling of statement number table sections (a large function might have multiple sections). | The statement number table section processing has been corrected. | | | 5 | Fault Analyzer loops in function WhatsNext() when processing COBOL program abend. | WhatsNext() continually returns the same base locator when the highest address in the dictionary is a COBOL base locator. | WhatsNext() now checks for same base locator being returned. | | | 6 | Abend S0C4 in IDILANGX function ADD_PLIST when processing Enterprise PL/I compiler listing. | The block info structure does not have a symbol ID specified, resulting in bad pointer. | The block info structure is now not processed if the symbol ID is not set. | | | 7 | Message IDI0090E IRXEXEC rc=20 when attempting to run a REXX Notification user exit for IMS ImageFast duplicates in the IDIS subsystem. | The IDIEXEC DDname was not allocated. | The IDIEXEC DDname is now correctly being allocated prior to running the REXX user exit. | | | 8 | Incorrect source line is located from stmt# point-and-shoot field when Enterprise PL/I program is compiled with STMT and NONUMBER options. | The source info point-and-shoot field specifies both line# and stmt#, but only line# is used to align source records. When STMT and NONUMBER options are in effect, there could be multiple source lines with the same line#. | When both stmt# and line# are specified, both are checked when aligning source records. | | | 9 | Enterprise PL/I BIN(63) and BIN(64) variables are reported as BIN(31). | IDILANGX does not recognize BIN(63) and BIN(64) data types. | IDILANGX now recognizes BIN(63) and BIN(64) data types. |
| | 10 | Cursor incorrectly positioned on second char of FIND argument when used from the Saved Report display. | The Saved Report display differs from other displays in that the leftmost column does not always contain an attribute or blank character. This exception was not being considered when the cursor was positioned for a successful FIND command. | The cursor is now being positioned at the first (or only) character of an argument specified on a successful FIND command. | | | 11 | Abend S0C4 while processing VS COBOL II event. | If there is no CLLE for VS COBOL II program, essential information about the TGT (eg. length) is unavailable, causing an abend S0C4. | Processing is bypassed when a VS COBOL II TGT is not available via the CLLE. | | | 12 | Abend S0C4 when reporting Enterprise PL/I EXTERNAL variables during re-analysis of fault created with DeferredReport in effect. | EXTERNAL variable's data not in minidump. | DeferredReport processing corrected for Enterprise PL/I EXTERNAL variables. |
| | 13 | Abend S0C1 or other random problems due to an overlay with data of x'40000000' after a Fault Analyzer IDIS subsystem hang. | If the IDIS Fault Analyzer subsystem is delayed or hung such that return x-memory POST processing gets abend S102 or other problems, it is possible, depending on requestor memory reuse, to get random storage overlays. CICS abend processing is susceptible to this with IDIS running. | Validation of the return x-memory POST conditions checked before return. | | | 14 | DFHSR0606 Abend (23E/AKEB) detected after IDICALOC LOCFRESL DETACHing orphan TCB terminating CICS. | CICS DUMPCODE: SR0606 and termination after Fault Analyzer task management IDICALOC LOCFRESL DETACHing orphan TCB. The TCB address being detached is invalid. | Messages corrected to display the correct TCB=address and validation improved to prevent the condition. | | | 15 | Abend S0C4 in PliSepSym when processing Enterprise PL/I SYSDEBUG side file. | PL/I PUT STRING statement causes symbol name pool to reside in program CSECT (instead of SYSDEBUG file), some of this storage might not be available. | Entire program and static CSECT storage now located. | | | 16 | Enterprise PL/I structure member has incorrect offset when variable with same name is used as a parameter. | When multiple instances of a variable name are declared in a block, an incorrect instance might be used. | The correct instance of the variable is now used. | | | 17 | DFHAP0701 An abend (code 0C4/AKEA) has occurred in exit IDIXCX53 at exit point XPCABND. | The Fault Analyzer IDIXCX53 exit when requesting CICS GETMAIN storage did not correctly handle the not available condition and caused an 0C4 that can terminate CICS. | The GETMAIN return checking has been corrected. | |
APAR PK74115 Fixes and Enhancements | | Problem | Description | Fix | Complete APAR information | | 1 | 0C4 in SearchDS while processing Enterprise PL/I program. | SERVICE string is an odd number of characters requiring an additional byte for halfword alignment. | Halfword alignment added when processing SERVICE string and subsequent saved options string. | PK74188 | | 2 | CICS Storage Violation SM0102 with Program IDIXCX53. | A trailing SAA is overlayed by Fault Analyzer IDIXCX53 when CICS trace data gathering fills at a buffer boundary. | The boundary code has been corrected to allow for the additional halfword end of records field. | PK74096 |
APAR PK72175 Fixes and Enhancements | | Problem | Description | Fix | Complete APAR information | | 1 | IBM002I message when running PL/I | With Fault Analyzer usermod IDISPLI and the PL/I 2.3 runtime, an abend can occur giving message IBM002I if the execution mode is AMODE 24. | The usermod is updated to accommodate AMODE 24. | PK72175 | | 2 | 3 runtime with ++USERMOD IDISPLI and executing in 24-bit mode. IDI0144E message from IDIS Fault Analyzer subsystem. | Intermittent message from Fault Analyzer IDIS subsystem. IDI0144E IDIS error detected at IDIXCEE:241 TCB 9E5298 S0C4 When an XCF message buffer length is exceeded. | The buffer length checking has been corrected to prevent the overwrite. | PK72408 | | 3 | Message: "Report line threshold of 50000 lines reached - doubling the interval" being incorrectly displayed. | This message was supposed to be a diagnostic message for internal use only, and should not be displayed to the user. | This message has been correctly changed to an internal diagnostic message. | PK72175 | | 4 | Dynamic allocation for dataset with HLQ of SILLY99 when Fault Analyzer invoked. | The code which checks for a suitable operating environment was making an unnecessary dynamic allocation for data set SILLY99.DATA88.SET77.NAME66.CHECK55. | The dynamic allocation has been removed. | PK72175 | | 5 | When a structure parameter is passed to a PL/I program, which has been compiled with PL/I for MVS & VM, the structure member offsets in the called procedure are zero. | PL/I for MVS & VM does not provide mapping for structure parameters, offsets appear as "ADJ" and total lengths as "PARAM". | Basic structure mapping is now performed by IDILANGX for parameter structures. | PK70096 | | 6 | IDIUTIL failure when history file data set contains a substitution variable. | With version 8 Fault Analyzer, the use of a substitution variable in a history file input data set name can trigger a number of different errors depending on the IDIUTIL commands being used. | The variable substitution is resolved at input before continuing processing. | PK72372 | | 7 | Fault Analyzer loops when processing variably located data items in a COBOL program. | The variably located data (BLV) has a bad address (eg. 0xFFFFFFFC) which causes WhatsNext() to return the same IANCHOR as that passed to it. | WhatsNext() now checks that the returned IANCHOR has an address higher than the IANCHOR passed to it. | PK73197 | | 8 | Message IDI0020W issued if the NoErrorHandler option is specified. | The NoErrorHandler option is not recognized as a valid option. | The NoErrorHandler option is now recognized as a valid option. | PK73058 | | 9 | Fault Analyzer abends when processing PL/I external variables. | Incorrect static csect length causes dLocate failure. | dLocate issued for adjusted section length. | PK73074 | | 10 | Message IDI0005S IDIKEY:553 Storage allocation failed. | Analyzing a SYSMDUMP of an LE abend, a bad pointer results in an incorrect storage allocation to be attempted. | The call from DSAchain() had a bad KANCHOR pointer, which is now guarded against. | PK72175 | | 11 | On reanalysis of fault entry created during CICS system dump analysis, data is missing from the storage violation report. | PL/I for MVS & VM does not provide mapping for structure parameters, offsets appear as "ADJ" and total lengths as "PARAM". | The internal trace table is now written to the minidump when the user creates a fault entry. | PK72175 |
APAR PK69687 Fixes and Enhancements | | Problem | Description | Fix | Complete APAR information | | 1 | CICS trace selection panel error when running Fault Analyzer interactive analysis under CICS. | An increase in the length of the start and end sequence numbers had not been correctly reflected in the panel. | The panel has been corrected accordingly. | PK69817 | | 2 | 0C4 abend occurs when Fault Analyzer calls __fmwsa for DeferredReport processing. | __fmwsa callback function issues longjmp() but setjmp() has not been called. | setjmp() now called before __fnwsa. | PK70037 | | 3 | PrtSystemWideOpenFiles() abends with 0C4 when more than 20 CICS Open Files (FLABs) are encountered. | FLABs are collected into a fixed 20 element array. | Grow array implemented for FLABs. | PK69865 | | 4 | CICS region hang followed by Fault Analyzer IDI0130E time out message. | In Fault Analyzer version 8.1 the FastExclude processing via the IDIS subsystem, if interrupted by IDIS failures, can cause the CICS region to hang until the IDI0130E time out message displays. | Time out values changed for some CICS subsystem calls and related subsystem loop fixed. | PK69788 | | 5 | COBOL source line accessed from register display hotspot is a comment. | The first source line for a given offset is selected regardless of whether it is a comment. | When determining the COBOL source line for a register address (which translates to base locator + offset), any leading commentary source lines are ignored. | PK70367 | | 6 | High CPU task loop in IDIS Fault Analyzer subsystem after IDI0117E message. | After the cancel of an end user waiting in Fault Analyzer processing and an IDI0117S ABNED=602, the server TCB in the IDIS subsystem can loop. | The rechaining of the work element during recovery processing was corrected. | PK70564 |
APAR PK67040 Fixes and Enhancements | | Problem | Description | Fix | Complete APAR information | | 1 | IDI0047S internal abend S0C4. | Fault Analyzer report processing PrtAssociatedMessages() function can get S0C4 under conditions where message records have not been created. | Code changed to correctly check if message information is available. | | | 2 | V or S line command from Fault Entry List display is unable to show generated saved report for DeferredReport fault entry. | As a result of changes to refresh processing, flagging of the generated saved report had been lost. | The missing generated saved report flagging has been added. | | | 3 | Data sets specified on the pseudo-JCL panel for interactive reanalysis might not be used if an Analysis Control user exit is specified. | Following the change to allow the Analysis Control user exit to be run during reanalysis, as well as real-time, user-specified data sets entered on the pseudo-JCL panel were not being included in the re-determination of preallocated data sets following the user exit call. | The data sets specified by the user on the pseudo-JCL panel are now being included again following the call to an Analysis Control user exit. | | | 4 | Fault Analyzer abends with 0C7 after selecting terminal IDs for CICS Trace. | Fault Analyzer is expecting the TCTTE transaction number to be a valid packed decimal value when, if fact, it may not be (eg. it could be 0x00000000). | Fault Analyzer now handles the TCTTE transaction number as byte data. | | | 5 | Incorrect values in the ENV structure when a Notification user exit is invoked for CICS fast duplicates. | If the original fault entry, to which the fast duplicates refer, no longer existed, then the ENV structure was being populated from another cached fault entry, instead of being cleared. | If the original fault no longer exists, then the ENV structure is appropriately cleared. | | | 6 | Abend S0C4 at entry point DSAchainTCB offset X'5592'. | An assumed register save area which was being processed, was spanning two 4K pages with different storage protection keys. | A check has been added to ensure that the entire register save area is accessible. | | | 7 | Message IDI0101I, dump and analysis suppressed, even though running with NoCICSDumpTableExclude. | Exit program IDIXCCEE is losing addressability to a storage area which holds an indication of whether the CICSDumpTableExclude option is in effect. | Addressability to the storage area containing the CICSDumpTableExclude option is now maintained | | | 8 | Message IEC331I when viewing Recovery Fault Recording fault entry | When creating a realtime report for a Recovery Fault Recording fault entry, the fault entry is refreshed. Part of this refresh process issued a delete for the associated Recovery Fault Recording dump data set, which could lead to an IEC331 message. | The attempt to delete the Recovery Fault Recording dump data set is no longer being made. | | | 9 | CICS message DFHSR0606 showing abend S878 during CICS operation. | The S878 abend occurred in the IDIS subsystem due to insufficient storage. | The IDIS GETMAIN has been made conditional to prevent the S878 abend. | | | 10 | Message IDI00109E abend S0C4 in the IDIS subsystem. | The abending TCB for which Fault Analyzer was invoked was running key 7, but only key 8 was expected by the IDIS subsystem interface. | Support for TCBs running with keys, other than 8, has been added. | | | 11 | Unable to scroll horizontally tosee a message explanation which exceeds 80 columns. | The keylist used for the IDIPLOOK panel did not include settings of PF10 and PF11 to the LEFT and RIGHT commands respectively. | The LEFT and RIGHT commands have been added to the IDIPIKY8 keylist. | |
APAR PK64683 Fixes and Enhancements | | Problem | Description | Fix | Complete APAR information | | 1 | Associated Storage Areas missing with Enterprise COBOL 4.1 events. | Enterprise COBOL 4.1 product number (5655-S71) not recognized by Fault Analyzer. | Product number 5655-S71 has been added. | | | 2 | Abend S0C4 in PrtOptions at offset X'3F5C'. | Unallocated storage beyond the end of a character string was being referenced. | A check has been added to ensure that the storage past the character string is only referenced when it is known to have been allocated. | | | 3 | Abend S0C4 in generateDBRMKeyData offset X'257E'. | An SQL statement was obtained in ASCII from the SYSIBM.SYSDBRM DB2 table, when EBCDIC format was expected. This caused a search for host variable name colons to fail. | ASCII SQL statements are now converted to EBCDIC prior to processing the host variable names. | | | 4 | IDIXDCAP abend S0C4 at offset X'1AE4'. | An abend occurred in the MVS subsystem interface, causing the IDIXDCAP ESTAE exit to unexpectedly receive a SDWA in a storage key other than 8. | The code has been changed to handle a SDWA in any storage key. | | | 5 | Abend S0C4 in WriteMiniDump. | When Fault Analyzer is saving analysis of a system dump, it might get abend S0C4 in WriteMiniDump +7B6. | Code added to allow only 2K to be moved when low core is addressed. | | | 6 | Loop in Fault Analyzer when analyzing CICS Temporary Storage queue control blocks. | One or more digital tree nodes have been overwritten. Fault Analyzer needs to reference these nodes to identify temporary storage queues. | All 'down pointers' in the nodes are now checked for double word alignment. If this check fails, then processing of the nodes and queues is abandoned, and a new severity 2 message is displayed. | | | 7 | MSGIDI0109E PC Recovery abend S0C4. | IDI0109E PC recovery enters abend S0C4 when Fault Analyzer is called for an abend on a TCB which is not running key 8. | Code in the subsystem interface has been upgraded to handle calls when the TCB key is not 8. | | | 8 | DFHTC2507 issued when CFA transaction is invoked via a sequential terminal as part of CICS startup. | The CFA transaction (program IDIXFA) was not correctly detecting its principle facility, and hence was attempting to send a map to the sequential terminal. This caused the DFHTC2507 message, and hence no additional input was processed. | IDIXFA has been changed to correctly identify its principle facility. | | | 9 | Fault Analyzer S0C4 in GetStgMem() when re-analyzing PL/I abend with a side file. | If no side file is available at the time of the abend, then storage for based variables is not included in the minidump, and subsequent re-analysis using a side file might attempt to access this storage, possibly causing abend S0C4 in GetStgMem(). | Bad basing pointers (i.e., pointers to storage not in the minidump) are identified and reported in the Associated Storage Areas section. | | | 10 | Unable to change fault entry LOCK flag from ISPF interface. | The attempt to rewrite the updated fault entry failed due to an out-of-space condition on the history file (abend SD37). | Normal history file space management is now invoked prior to rewriting the fault entry in order to minimize the risk of exceeding the maximum size of the history file. | | | 11 | Message IDI0005S when using the Fault Analyzer ISPF interface to show history file fault entries. | A storage leak occurred when switching between different history files, or repeatedly pressing Enter to refresh the list of fault entries for a history file, causing insufficient storage to be available for subsequent actions. | The storage leak has been fixed. | |
APAR PK64242 Fixes and Enhancements | | Problem | Description | Fix | Complete APAR information | | 1 | Abend S0C4 in module IDIXCX53 at offset X'192F6'. | An incorrect return code check was being made and hence code was being executed which should not have been. | The return code check has been corrected. |
| | 2 | CICS Trace selection not working correctly with a large trace table when identifying all tasks for a specific terminal ID. | Incorrect processing of CICS trace sequence numbers and only the active task for a specific terminal was identified. | The sequence numbers are now processed correctly, and all tasks in the CICS trace table that have been started for a specific terminal are now being displayed. | | | 3 | Message IDI0057E Dynamic load of LE failed, when LE is not in LPA or LINKLIST, and no STEPLIB to the LE run-time data set has been provided. | An incorrect DCB address was used for the BLDL macro, when attempting to locate the LE load module in the LE run-time data set specified in the IDICEEDS CSECT. | The DCB address has been corrected. | | | 4 | Loop in Fault Analyzer IDIS subsystem after a previous task abend. | A pointer reset problem can cause a loop in the IDIS subsystem following recovery from an IDIS subtask abend. | Corrected clearing of the pointer has been added to the error recovery processing. | | | 5 | Message IDI0047S Fault Analyzer IDIS subsystem raise() condition in addDSS function. | The IDIS subsystem IDISUPDI program can get a raise() condition and task termination when adding duplicate subsegments after a deferred report has been saved for the same fault entry. | The fixed HD segment update has been corrected to retain the appropriate DSS offset value. | | | 6 | Abend S0C7 when an abending COBOL program has COMP-3 OCCURS DEPENDING ON variable of less than 3 bytes which contains invalid packed decimal data. | C built-in function decchk() returns DEC_VALUE_OK for 1 and 2-byte packed fields which contain bad data. | Packed decimal data of less that 3 bytes is promoted to 3 bytes before calling decchk(). | |
| Problem | Description | Fix | Complete APAR information | | 1 | Options on initial interactive reanalysis menu disappear after formatting event details. | A flag was being incorrectly set as part of the event formatting process, which caused the initial menu to be incorrectly re-displayed. | The flag is now correctly set and restored. | PK63785 | | 2 | Task is missing on the CICS system dump analysis Task Summary display. | Summary lines are built for each task which has a Task Control Area (TCA), but the missing task is terminating and no longer has a TCA. | The CICS Kernel and transaction manager control blocks are now used to build and display summary lines for tasks without a TCA. | PK63791 | | 3 | COBOL SIGN IS LEADING/TRAILING SEPARATE CHARACTER clause causes incorrect reporting of data field values. | The instruction operands, when processing these data fields, do not necessarily point to the start of the data (for example, the PACK instruction operand for LEADING points passed the SIGN byte). | The data field addresses have been corrected. | PK63802 | | 4 | IDILANGX issues messages IDISF8132S and IDISF8136S when processing Enterprise COBOL V4.1 compiler listing. | The Enterprise COBOL V4.1 compiler is not recognized by IDILANGX. | IDILANGX now recognizes the Enterprise COBOL V4.1 compiler. | PK63849 | | 5 | Copy to data set from the ISPF interface Services pull-down menu copies the visible display content only. | Implicit 'max down' missing to obtain lines beyond the visible screen depth. | Implicit 'max down' added. | PK63862 | | | | | | | 6 | Fault Analyzer IDIUTIL IMPORT or DELETE command might result in MSGIDI0095W or RefreshCACHE error message. | The IDIUTIL IMPORT or DELETE function might give incorrect results because of un-initialized storage. | The storage has been correctly cleared before use. | PK63372 | | 7 | Abend U2101-X'7202' in IDIXDCAP. | PSW storage protection key incorrectly set to 0 following Fast Exclude processing. | The PSW storage protection key is now correctly set to 8. | PK62476 | | 8 | Incorrect suppression of fault entries (message IDI0053I) when using both an Analysis Control user exit and an End Processing user exit. | The ENV data area IDIHIST field was incorrectly set to NULLFILE following the Analysis Control user exit call. | This value was later interpreted by the End Processing user exit as an intended change of the history file name. The ENV.IDIHIST field is now set correctly following the Analysis Control user exit call. | PK62542 | | 9 | Enterprise PL/I compiler listing created with RENT option in effect results in blank CSECT names in the IDILANGX X'0E' record. | The EXTERNAL SYMBOL DICTIONARY section of the compiler listing uses a single column, but the code expects two columns. | Code added to support 1 or 2 columns. | PK63706 | | 10 | Unable to perform reanalysis if history file is changed by Analysis Control user exit. | The Analysis Control user exit was able to change the history file name during reanalysis. | Any changes to the history file name by any user exit during reanalysis are now being ignored. | PK63175 | | | | | | | 11 | Unable to specify compiler listing or side file data set name on prompt during interactive reanalysis if no TSO prefix set. | When using TSO PROFILE NOPREFIX, the data set name specified on the prompt during interactive reanalysis was being processed incorrectly, causing the prompt to reject the specified data set name. | The specified compiler listing or side file data set name is now processed correctly, even when TSO PROFILE NOPREFIX is used. | PK63318 | | 12 | Information about CICS-managed files not provided in 'Open Files' section of the analysis report. | CICS file control data areas are not referenced during the creation of the 'Open Files' report. | For CICS transaction abend analysis, CICS file control data areas are now referenced. | PK63870 | | 13 | Message IDI0005S IDICCDB2:878, then message IDI0095W from the IDIS subsystem. | Intermittent attempt to allocate a very large buffer for an SQL statement causes message IDI0005S and IDI0095W in the Fault Analyzer IDIS subsystem. | Code added to detect the incorrect statement length. | PK63709 | | 14 | IDI0047S abend in IDIS subsystem with raise() function being called from addDss function. | An incorrect length check was being performed. | The incorrect length check has been corrected. | PK63712 | | 15 | IDIS subsystem hang during termination after subtask abend. | The IDIS subsystem did not terminate correctly after one of the subtasks had abended. | The IDIS subsystem termination has been corrected. | PK63722 | | 16 | Abend S0C4 at entry point DDfeof offset X'7C'. | The return code from opening the fault entry member was not being checked correctly and processing was allowed to continue using an invalid work area. | The return code is now being checked correctly to prevent an invalid work area from being used. | PK63879 |
| Problem | Description | Fix | Complete APAR information | | 1 | Message IDI0032W I/O error writing report: EDC5003I truncation of a record occurred during an I/O operation. | Invalid DB2 GRAPHIC type host variable data was not being adequately validated before attempted written to the report. | Improved validation has been added. | PK61446 | | 2 | Abend S0C4 in mapCsectEntryPoint() when analyzing a CICS system dump. | Invalid key data was being added. | The invalid key data has been corrected. | PK61456 | | 3 | IDI0095W Unexpected condition found in IDIDODSN:287 when creating a CICS system dump fault entry. | After analyzing a CICS system dump with Fault Analyzer, the fault entry save process can get an IDI0095W error from IDIDODSN:287. | The logic has been changed to correctly accommodate the failing page boundary condition. | PK61465 | | 4 | Message IDI0047S abend S0C4. | An invalid argument was passed to the sprintf C run-time function from formatSummary + X'E7E'. | The sprintf argument has been corrected. | PK60745 | | 5 | When formatting COBOL data division, a 'Storage range xxxxxxxx-xxxxxxx not accessible' message is issued. | The base locator dictionary item length is 'trimmed' by an assembler DSECT, which redefines COBOL storage. | DSECTs have been excluded from dictionary items that can 'trim' COBOL base locator storage lengths. | PK61470 | | | | | | | 6 | Out-of-scope assembler DSECT storage is formatted. | The DSECT scoping is incorrect when a base register is reused. | The code has been changed to use the statement number from the respecify record, rather than a register symbol. | PK61471 | | 7 | Message IDI0006E issued without a data set name. | The data set was eliminated from the associated DDname due to READ access checking wrongly assuming lack of access authorization, when in fact the data set did not exist. | If a data set does not exist, then it is left in the list of data sets for a DDname so that it is available if open error messages are issued. | PK57659 | | 8 | Incorrect length presented for second operand of an MVCL (Move Characters Long) instruction. | Bits 0-7 of the MVCL source length register represent a padding character. This was not being taken into account when presenting the length. | The length is now derived from bits 8-31 of the source length register. | PK57853 | | 9 | Fault Analyzer abends or produces incorrect results when CMPAT(V1) is used with Enterprise PL/I SYSDEBUG files. | Fault Analyzer does not support CMPAT(V1) descriptors. | Support for CMPAT(V1) descriptors has been added. | PK57980 | | 10 | Enterprise PL/I SYSDEBUG sidefile is rejected when OPTIMIZE is in effect. | Truncated PPA4 does not supply rostatic, rwstatic, or blkbase, which are used to locate static storage. | Alternative method for locating static storage and CUI implemented. | PK61525
| | | | | | | 11 | Fault Analyzer loops when reporting registers for a COBOL program with sidefile provided. | The data item pointed to by the register was not on the abending source line, and has a REDEFINES. | The source line checking for a variable is bypassed when the function is called from the register display. | PK61539 | | 12 | Message IDI0130E Response from IDIS subsystem not returned within 2 minutes, request canceled. | A loop in the IDIS subsystem caused the request to time out. | Improved loop detection has been added. | PK61549 | | 13 | The history file data set remains allocated to a CICS job. | The allocation that was made during the recording of CICSFAST duplicates was not being freed. | The allocation is now freed. | PK58894 | | 14 | Message IDI0047S abend S0C4 in LE run-time function strspn, called from PrtHostVars during formatting of DB2 VARCHAR host variable data. | An ending NULL character was not added to the end of the buffer. | The ending NULL character has been added. | PK58959 | | 15 | Table element stride is incorrect when using COBOL SYSDEBUG sidefile. | Non-OCCURS DEPENDING ON (ODO) tables are being re-calibrated when a program contains one or more ODO tables. | The re-calibration logic has been corrected. | PK59466
| | | | | | | 16 | History file specified by Analysis Control user exit in ENV.IDIHIST does not override IDIHIST DD statement specified in JCL. | The exit-specified history file name was incorrectly being overridden by the pre-allocated IDIHIST data set name. | The exit-specified history file name in ENV.IDIHIST now always overrides any other specification, including pre-allocation via JCL DD statement. | PK61568 | | 17 | IDIS subsystem continues to run with various abends after running short of storage. | If the Fault analyzer IDIS subsystem has been started without sufficient region size to support the number of history files being opened, then it might attempt to continue with many storage-related abends, rather than shutting down quickly. | The processing of IDIS storage allocation failures has been updated to cause a quick termination of the IDIS address space. | PK61585 | | 18 | XFACILIT-managed data set access is not working correctly with ACF2. | The internal settings used during the management of XFACILIT-controlled data sets were not compatible with ACF2. | Settings which are equally applicable to ACF2 and RACF are now being used. | PK59783 | | 19 | Abend S0C4 in module IDIXDCAP entry point JOBINFO offset X'444'. | During Fast Exclude processing, the attempt to determine if LE was active for the abending TCB, resulted in key 2 storage being accessed while running in problem state. | null | PK60063 | | 20 | Interactive fault entry reanalysis under CICS is failing with system abend code S23E. | After a terminal session error while performing interactive fault entry reanalysis under CICS, Fault Analyzer attempted to DETACH the subtask twice, which caused a S23E system abend. Fault Analyzer has been changed to ensure that the DETACH is issued only once. | Changed to supervisor state key 0 while determining if LE is active for the abending TCB. | PK61591
| | | | | | | 21 | Corrupted Japanese text in the formatted storage display, or failure to successfully copy the display to a data set with the COPY command. | The display contains invalid DBCS characters due to missing shift-in characters. | The missing shift-in characters have been added. | PK61592 | | 22 | Abend S0C4 in makeString() during CICS system dump analysis when processing 3-character transaction number (for example, TCP) from KE Error Table Summary. | A wrong value was passed to makeString(). | The transaction-number processing has been corrected. | PK61178 | | 23 | Missing DB2 Information section in the analysis report. | The validation of the DB2 request parameter list did not correctly determine that the parameter list was in the LE heap. | The DB2 request parameter list validation routine has been corrected. | PK60814 | | 24 | Abend S0C4 in IDICBIMS offset X'336'. | An invalid offset into an IMS control block was being used during NoDup(ImageFast(...)) processing. | The IMS offset has been corrected. | PK61593 |
APAR PK53632 Fixes and Enhancements | | Problem | Description | Fix | Complete APAR information | | 1 | Unable to create a fault entry upon exit from interactive reanalysis of an MVS dump data set (for example, a CICS system dump). | The checking for security server UPDATE access authority to the defaulted or specified history file name was not using the correct data set name. | The checking is now performed aginst the correct history file name. | PK55099 | | 2 | Side file for abending COBOL event is not being used, resulting in missing analysis report source line information. | Previous event's R15 is not pointing at the following COBOL event's entry point. | Alternative method for determining COBOL entry point address implemented. | PK55040 | | 3 | Message IEC036I 002-18 followed by message IDI0124E might be issued from the IDIS subsystem. | In situations where a high number of duplicate abends occur for the same fault entry, a record length error can result in message IEC036I 002-18 being issued in the IDIS subsystem. | The record length problem on writing to the history file $$INDEX member has been corrected. | PK55108 | | 4 | Last executed DB2 SQL statement not shown in report. | Validation of a COBOL program's DB2 SQL parameter list in WORKING-STORAGE failed as it was attempted to relate this to an entry point instead of the CSECT. | The COBOL WORKING-STORAGE DB2 SQL parameter list is now validated against the CSECT instead of an entry point. | PK55144 | | | | | | | 5 | An S0C4 abend occurs in function pp_ueh_main due to an invalid reference to an array of global user exit names. | New exits in CICS TS 3.1 and TS 3.2 are not defined in the array of user exit names. | The names of global user exits which are new in CICS TS 3.1 and TS 3.2 are now defined to Fault Analyzer. | PK55163 | | 6 | Not all of a CICS task's allocated storage is included in the minidump. | Only the first and last 4K of each storage area was being included in the minidump to allow for storage overlay checking. | The complete storage area is now included in the minidump. | PK55179 | | 7 | PIC declared structure members are not assigned an address when using an Enterprise PL/I SYSDEBUG side file. | Descriptor processing is incorrect for PIC declared character strings when they are structure members. | Descriptor processing has been corrected. | PK55120 | | 8 | Abend S0C4 in IDIDA DFHTT640 when formatting a socket domain CICS trace entry. | An abend S0C4 might occur on a MVCL instruction in DFHTT640 when formatting a CICS socket domain trace entry. | Code in the the call interface to DFHTT64 has been changed to circumvent the wrong length move problem. | PK55404 | | | | | | | 9 | Fault Analyzer event list 'loaded from' might be 'n/a' if the data set has EXECUTE ONLY security access. | When the load data set security is 'EXECUTE ONLY', then the Fault Analyzer event list 'loaded from' column might show 'n/a' instead of the load data set name. | The logic path encountering the 'EXECUTE ONLY' access has been corrected to retain the load data set name. | PK55431 | | 10 | Poor analysis performance when a job causes many WTO messages that do not start with a formal message ID to be issued. | An attempt was being made to find an explanation for the presumed message ID at the start of each WTO message. | Improved verification of the presumed message ID has been implemented to avoid the overhead of searching for a message explanation when none exists. | PK55446 | | 11 | Message IDI0092S time-out after 32 minutes. | When writing a large report, the time expected for completion was being incremented repeatedly until the maximum of 32 minutes was reached. | The expected time for completion of a large report is now incremented only once. | PK55480 | | 12 | SYSUDUMP not suppressed when a Fault Analyzer warning message (W level) is issued. | The return code set when any Fault Analyzer messages, other than informational messages (I level), were issued, caused the MVS dump (SYSUDUMP, SYSMDUMP, or SYSABEND) to not be suppressed with the RetainDump(AUTO) option in effect. | A change has been made to ensure that only severe error messages (S level) will cause the MVS dump to not be suppressed. | PK55486 |
All available Version 7 Fault Analyzer PTFs and associated APARs (most recent first):
PTF | AVAILABILITY DATE | PREREQUISITE PTFs | SUPERCEDES THESE PTFs | APAR(s) THIS PTF FIXES | | | | | | English:
UK50303 | 2009/10/02 | UK48897 | | | | | | | | English:
UK48897 | 2009/08/06 | | UK47512 UK45220 UK43414 UK41089 UK40623 UK39512 UK38356 UK36765 UK35263 UK33932 UK30778 UK28921 UK27356 UK25564 UK23264 UK21777 UK19760 | | | | | | | English:
UK47512 | 2009/06/20 | UK45220 UK41089 | | | | | | | | English:
UK45220 | 2009/03/31 | UK41089 | UK43414 | | | | | | | English:
UK43414 | 2009/01/29 | UK41089 | | | | | | | | English:
UK41089 | 2008/11/01 | | UK40623 UK39512 UK38356 UK36765 UK35263 UK33932 UK30778 UK28921 UK27356 UK25564 UK23264 UK21777 UK19760 | | | | | | | English:
UK40623 | 2008/10/16 | | UK39512 UK38356 UK36765 UK35263 UK33932 UK30778 UK28921 UK27356 UK25564 UK23264 UK21777 UK19760 | | | | | | | English:
UK39512 | 2008/09/10 | UK36765 UK33932 UK30778 UK27356 UK23264 | UK38356 | | | | | | | English:
UK38356 | 2008/08/01 | UK36765 UK33932 UK30778 UK27356 UK23264 | | PK67411 PK69532 PK69534 PK69543 PK67429 PK68264 PK69588 PK65073 | Japanese:
UK38423 | UK31071 | | | | | | | English:
UK36765 | 2008/06/02 | UK35263 UK33932 UK30778 UK25564 | | PK64341 PK66719 PK64605 PK64623 PK65132 PK66720 PK65381 PK66736 PK66813 PK66741 PK66805 | | | | | | English:
UK35263 | 2008/04/10 | UK33932 UK30778 | | PK61879 PK62386
PK61337
PK62200
PK63864 PK63708
PK63362
PK62209
PK63867 | | | | | | English:
UK33932 | 2008/02/29 | UK30778
UK25564
UK23264 |
| PK56116 PK61638
PK61641
PK58322
PK56569 PK57338
PK57337
PK61642
PK61646
PK57980 PK61690
PK61691
PK58689
PK58647
PK58899 PK58960
PK59426
PK61685
PK59784
PK60297 PK61696
PK61697
PK61700
PK61284 | | | | | | Japanese:
UK31071 | 2007/11/15 | | | | | | | | | English:
UK30778 | 2007/11/09 | UK27356
UK25564
UK23264 | UK28921 | PK52716 PK52731 PK53354 PK53331 PK54751 PK55178 PK55181 PK53346 PK55307 PK55474 PK55482 PK55487 PK55432 | | | | | | English:
UK28921 | 2007/09/12 | UK27356
UK25564
UK23264 | | PK49788 PK51492 PK50166 PK50761 PK51930 PK51294 PK51292 PK52009 PK52367 | | | | | | English:
UK27356 | 2007/07/28 | UK25564
UK23264 | | PK45989 PK49397 PK46639 PK49413 PK46907 PK47038 PK47274 PK49331 PK49469 PK49472 PK49475 PK49476 PK49385 PK48372 PK48468 PK49478 PK49480 PK49388 PK49481 PK49483 | | | | | | English:
UK25564 | 2007/06/08 | UK23264 | | PK42493 PK45830 PK45835 PK42956 PK45838 PK45840 PK45845 PK45911 PK45880 PK45905 PK45907 PK45908 | | | | | | English:
UK23264 | 2007/04/03 | | UK21777
UK19760 | PK39001 PK38823 PK38986 PK39351 PK39219 PK39525 PK41102 PK41178 PK40142 PK41265 PK41279 PK41283 PK41394 | | | | | | English:
UK21777 | 2007/02/07 | UK19760 | | PK35094 PK35455 PK38241 PK38244 PK38266 PK38244 PK38337 PK38339 PK38247 PK38256 PK38341 PK38330 PK38332 PK38259 PK38260 PK38344 PK38347 PK38264 PK38349 | | | | | | English:
UK19760 | 2006/11/23 | | | PK32559 PK34452 PK34454 PK34604 PK34456 PK34603 PK34602 PK34458 PK34600 PK34599 PK34524 PK34585 PK34586 PK34587 PK34588 PK32558 PK34598 PK34589 PK34590 PK34592 PK34593 PK34597 PK34594 PK34595 PK34596 |
APAR PK92824 Fixes and Enhancements | | Problem | Description | Fix | Complete APAR information | | 1 | Job type incorrectly determined to be STC for TSO address space, resulting in incorrect Include/Exclude behaviour. | TSO was expected to run under the 3rd TCB in an address space in order for the job type to be set to TSU. | The search for TSO has been extended to all TCBs. | | | 2 | Address range invalid message appears for hex-dumped storage range in batch report, but storage is reported correctly by interactive re-analysis. | A storage range may be registered more than one and include descriptor entries that have a length of zero. When a descriptor entry is used to determine the end address of a range, the end address will be invalid (as it is one less than the start address). | Entries with a non-zero length are now used to determine the end address of a storage range. | | | 3 | Missing DB2 information in the analysis report for some CICS transactions. | DB2 information was obtained for a different transaction and therefore discarded. | DB2 information is now being obtained for the correct CICS transaction and presented in the analysis report. | | | 4 | CFA transaction IVP selection does not do anything. | The code was not allowing for a lower case S to be entered. | Both an upper and lower case S are now accepted. | | | 5 | Abend S0C4 at entry point displayFP when displaying large hex-formatted storage section from the interactive reanalysis report. | Reformatting of the display attempted to clear the in-storage buffer to blanks, but the display had become file-paged, resulting in an invalid in-storage buffer being blanked out. | The display clearing has been changed to accommodate both normal and file-paged protocols. | | | 6 | Abend S0C4 at entry point PrtLeOpt offset X'33A'. | An invalid LE CEEOCB data area was being used for display of LE options in effect. | LE options are only displayed when a valid LE CEEOCB data area has been found. | | | 7 | The same PL/I ONCODE condition is shown against multiple PL/I events. | The check for the same PL/I Library Workspace did not allow for a PL/I routine to be calling another language, such as COBOL, before abending in another PL/I subroutine. | A PL/I Library Workspace is now only reported on once, regardless of any intermediate inter-language calls. | | | 8 | Fault Analyzer with IDISPLI or IDISPLIA usermod installed is incorrectly invoked for PL/I V2R3 ONCODE 4 conditions. | No special check was made for a PL/I ONCODE 4 condition, which should be ignored. | A check has been added to prevent Fault Analyzer from being invoked for a PL/I V2R3 ONCODE 4 condition. | |
APAR PK89335 Fixes and Enhancements | | Problem | Description | Fix | Complete APAR information | | 1 | Incorrect PL/I or C/C++ source line for offset reported when multiple lines have same offset. | The first source line at the given offset was selected. | The last source line at the given offset is now selected. | | | 2 | Abend S0C4 in FmtPliData when PL/I defined variable is used in program with PUT LIST/DATA. | Symbol entries are located in the CSECT when PUT LIST/DATA is used in PL/I program (otherwise they are located in the SYSDEBUG side file). Symbol entries located in the CSECT must be explicitly located in the minidump storage. | Defined variable is now located in the minidump storage. | | | 3 | Message IDI0095W Unexpected condition found in IDIDODSN:2810: Process error, followed by message IDI0047S and possibly IDI0126I. | An error occurred during the processing of CICS transaction isolation address ranges. | An error in processing of CICS transaction isolation address ranges has been corrected. | | | 4 | Abend S0C4 in PliSepCheck when processing an Enterprise PL/I SYSDEBUG file. | A bad CUI gives invalid offset into debug tables name pool. | The name pool offset is now checked to determine if it is within the debug tables. | | | 5 | Abend S0C4 in load module IDIXDCAP at entry point DDfclose offset X'80'. | An invalid work area address was being used for data set close processing after a failure to open the CEE.SCEERUN LE run-time library. | A check has been added to not attempt closing the LE run-time library if it has not been opened successfully. | | | 6 | Abending event appears as first user event, when it should be the last. | Comparison using register 13 values gives wrong result because the hi-order bit is on. | The hi-order bit has been masked out for register comparison. | | | 7 | Wrong machine instruction is reported, even though the PSW gives correct instruction address. | Abend S0C4 program interruption codes 10 and 11 are not extracted from the SDWA, resulting in incorrect adjustment of the instruction address. | Abend S0C4 program interruption codes 10 and 11 are now extracted from the SDWA. | | | 8 | The EQAUEDAT exit is not called to obtain the name of a VS COBOL II compiler listing data set. | The EQAUEDAT exit was only called if the listing data set name was in PROGSUM (which it is not for VS COBOL II). | The EQAUEDAT exit is now called for VS COBOL II (language code 41). | | | 9 | CICS performance problem with Fault Analyzer message IDIS0126I taking IEATDUMP and then message IDI0092S time 4 minutes exceeded subtask canceling. | With large CICS systems and a problem with normal Fault Analyzer processing such as IDI0005S out of storage due to REGION size constraint, then RFR (Recover Fault Recording) TDUMP may time out with IDI0092S message. | The RFR processing has been extended to use SDUMP because of its superior performance over TDUMP. The SDUMP process is contolled by RACF XFACILIT class access. | |
APAR PK83695 Fixes and Enhancements | | Problem | Description | Fix | Complete APAR information | | 1 | Second and subsequent reanalyses of a Recovery Fault Recording (RFR) fault entry does not show the original abend TCB problem. | The Fault Analyzer TCB was being analyzed instead of the original abend TCB. | The original abend TCB is now being correctly determined. | PK83943 | | 2 | Abend in PliSibCheck35 when processing Enterprise PL/I SYSDEBUG side file. | DSA had bad SIF data. | SIB pointed to from SIF is checked, if check fails SIBs are located differently. | | | 3 | Listing prompt is issued for COBOL side file but source line is not located. | New member name is being used as program CSECT name when creating side file CSECT record. | Program CSECT name parameter corrected. | | | 4 | When an invalid member name was supplied in the DSN field on the DSECT panel, no warning message was displayed. | The invalid member was being detected but the appropriate warning message was not being copied to the DSECT panel message field. | Warning message now correctly displayed on DSECT panel. | | | 5 | Incorrect highlighting of CICS Trace entries when using default interval (0.128). | The default interval was not explicitly set. | The default interval is now explicitly set. | | | 6 | Fault Analyzer invoked when QUIT ABEND issued in Debug Tool. This does not happen under CICS where analysis is skipped. | The detection of the QUIT ABEND command was only being performed by the Fault Analyzer CICS LE exit. | Both the CICS and non-CICS LE exits now check for the QUIT ABEND command. | | | 7 | IDI0047S IBM Fault Analyzer internal abend S230 and duplicate Recovery Fault Recording fault entries created. | An invalid DEQ is issued during Recovery Fault Recording processing, causing abend S230. The S230 abend causes Fault Analyzer RFR processing to be invoked a second time, resulting in two RFR fault entries instead of one. | The cause of the invalid DEQ has been corrected. |
| | 8 | Loop in function GetEPLISnt during real-time processing with the DeferredReport option in effect, causing IDI0092S time-out. | The end of a statement number table was not recognized correctly. | The end of the statement number table is now being determined correctly to prevent the loop. | | | 9 | Message IDI0047S abend S0C4 in Fault Analyzer dxLocate64. | Possible abend S0C4 in function dxLocate64() during real-time analysis. | Code condition added to correctly manage a special storage pattern reference function and prevent the abend S0C4. | | | 10 | No minidump is written to a new fault entry and no message is issued to explain why. | The number of minidump pages about to be written exceeded the expected number due to the use of an unsigned halfword instead of an integer to hold the count. The minidump was subsequently suppressed. | The minidump page count is now held in an integer to prevent the suppression of the minidump if the number of pages exceeds 65,535. | | | 11 | Abend S0C4 in dfhs_trace when processing CICS internal trace. | Trace anchor and internal trace blocks contain invalid pointers (possibly as a result of storage violations). | Additional sanity checks performed on pointers. | | | 12 | ABEND (CODE 0C4/AKEJ) occurs in IDIXCX53 due to backlevel XPI call with CICS/TS 4.1. | Existing XPI calls in Fault Analyzer exit code not compatible with CICS/TS 4.1. | XPI calls changed to comply with CICS/TS 4.1. |
| | 13 | Source line point-and-shoot fields locate wrong source line when source file # is not zero (primary source file). | Source display does not use file # when aligning source records. | Source display now uses file # when aligning source records. | | | 14 | Abend S0C4 in BldLX when processing Enterprise PL/I SYSDEBUG file. | The address of the structure parent is taken but this changes when the symbol lookup table is reallocated to a larger area. | The offset of the structure parent is now used instead of the address to locate the symbol lookup table entry. | | | 15 | Abend S0C4 in asm_rel_stg when assembler program has no in-scope DSECTs. | The DSECT info array pointer is not checked. | The DSECT info array pointer is now checked before processing. | | | 16 | IDISF8154W issued when COBOL compiler listing has USAGE NATIONAL data items. | Nat-xxxx tokens not recognized in MAP section. | Nat-xxxx tokens now recognized in MAP section. | | | 17 | IDILANGX gets abend U4000 when pre-allocating sequential output data set. | When the output file is opened, the default record length of 1024 is used because an explicit record length is not specified. | The output file is now opened with a record length of 1562 bytes. | | | 18 | Abend S0C4 in Extract_COBOL_Map when processing COBOL compiler listing with IDILANGX. | Data items in MAP section with LineID of zero cause non-existent source record to be scanned for PIC declaration. | Data items in MAP section with LineID of zero are no longer scanned for PIC declarations. | | | 19 | No source support when using Enterprise PL/I V3R8M0 compiler listing. | Enterprise PL/I V3R8M0 compiler listing not recognized. | Enterprise PL/I V3R8M0 compiler listing now recognized. | | | 20 | SVC dump from IRAVTABD with S0C4 in Fault Analyzer routine SETFARBB. | The Fault Analyzer SETFARBB function was not clearing the high order byte of a register before inserting the 24 bit address of a CDE entry, consequently getting an intermittent 0C4 when testing the CDE name. | The high order byte has been cleared. | | | 21 | CEE3204S Code=0C4 in DSNALLOC compile unit offset +064A when using IDILANGP utility against a SYSDEBUG side file. | The IDILANGP print utility might get abend S0C4 in DSNALLOC +064A when attempting to allocate a SYSDEBUG side file because of an input parameter list mismatch. | The DSNALLOC() input parameter list has been corrected. | |
APAR PK79445 Fixes and Enhancements | | Problem | Description | Fix | Complete APAR information | | 1 | Abend S0C4 in IDIXDCAP at offset X'9E70'. Might include DB2 abend S04E. | If Fault Analyzer is called for an abending TCB which is not running key 8, and LE is not available from LKNLST, then the DDFOPENR routine will get abend S0C4. | Tests added to detect non key 8 situation, and use the appropriate key for GETMAINs. | PK83291
| | 2 | Debug Tool abend S0C4 when calling Fault Analyzer via CALL %FA when //IDIOFF DD DUMMY is set. | The IDISNAP Fault Analyzer interface is not restoring R11 when //IDIOFF DD is set. | Correct restore of registers is now done when //IDIOFF DD is set. | PK83220 | | 3 | Abend S0C4 in module IDICBIMS at offset X'122C'. | The address of an IMS control block was not valid, causing abend S0C4 when attempting to access the storage. | Checks have been added for validation of the control block storage prior to accessing it. | PK83280 | | 4 | IDI0092S time out and performance problem if Fault Analyzer run with LE HEAPCHK(ON). | If an environment is set up with HEAPCHK(ON) as the default, then there might be siginficant performance overhead with Fault Analyzer execution. | Options in Fault Analyzer have been changed to suppress HEAPCHK(ON) for its execution. | PK83288 | | 5 | IDILANGX return code 1551 for large listing. | A listing with a very large number of symbols might not be able to be processed by IDILANGX and get a return code of 1551. | The array growth algorithm has been changed. | PK82461 | | 6 | DIALOG Error Function: DISPLAY IDI@CTRF when displaying CICS trace selection panel under CICS interactive re-analysis. | A code enhancement increased the trace sequence number field to 7 digits, however the corresponding change to the appropriate CICS panel IDI@CTRF was not made. | The panel field was increased in length accordingly. | PK79860 |
APAR PK74739 Fixes and Enhancements | | Problem | Description | Fix | Complete APAR information | | 1 | Dump Storage display FIND command loop. | An error caused the search for a specified string to re-start from address zero after not finding the string before the end of available storage. | The error has been corrected to prevent the search from wrapping. | | | 2 | CICS transaction RFR fault entry reanalysis results in "No abend could be determined--possible loop or wait situation" and unable to view saved report using "V". | When performing analysis of a CICS transaction abend Recovery Fault Recording (RFR) fault entry, then the original attributes of the fault are not being obtained correctly. | The correct attributes of the original fault are now being used to resume the interrupted real-time analysis. | | | 3 | Abend S0C4 in GetEPLISnt when processing CICS transaction abend in Enterprise PL/I program, with DeferredReport option in effect. | Incorrect handling of statement number table sections (a large function might have multiple sections). | The statement number table section processing has been corrected. | | | 4 | Fault Analyzer loops in function WhatsNext() when processing COBOL program abend. | WhatsNext() continually returns the same base locator when the highest address in the dictionary is a COBOL base locator. | WhatsNext() now checks for same base locator being returned. | | | 5 | LE heap overlay when using Views with the Fault Analyzer ISPF interface. | An insufficient buffer was allocated for the list of history file names contained in the view. | The allocated buffer size has been corrected. | | | 6 | Abend S0C4 in IDILANGX function ADD_PLIST when processing Enterprise PL/I compiler listing. | The block info structure does not have a symbol ID specified, resulting in bad pointer. | The block info structure is now not processed if the symbol ID is not set. | | | 7 | Message IDI0090E IRXEXEC rc=20 when attempting to run a REXX Notification user exit for IMS ImageFast duplicates in the IDIS subsystem. | The IDIEXEC DDname was not allocated. | The IDIEXEC DDname is now correctly being allocated prior to running the REXX user exit. | | | 8 | Incorrect source line is located from stmt# point-and-shoot field when Enterprise PL/I program is compiled with STMT and NONUMBER options. | The source info point-and-shoot field specifies both line# and stmt#, but only line# is used to align source records. When STMT and NONUMBER options are in effect, there could be multiple source lines with the same line#. | When both stmt# and line# are specified, both are checked when aligning source records. | | | 9 | Enterprise PL/I BIN(63) and BIN(64) variables are reported as BIN(31). | IDILANGX does not recognize BIN(63) and BIN(64) data types. | IDILANGX now recognizes BIN(63) and BIN(64) data types. |
| | 10 | Abend S0C4 while processing VS COBOL II event. | If there is no CLLE for VS COBOL II program, essential information about the TGT (eg. length) is unavailable, causing an abend S0C4. | Processing is bypassed when a VS COBOL II TGT is not available via the CLLE. | | | 11 | Abend S0C4 when reporting Enterprise PL/I EXTERNAL variables during re-analysis of fault created with DeferredReport in effect. | EXTERNAL variable's data not in minidump. | DeferredReport processing corrected for Enterprise PL/I EXTERNAL variables. | | | 12 | Abend S0C1 or other random problems due to an overlay with data of x'40000000' after a Fault Analyzer IDIS subsystem hang. | If the IDIS Fault Analyzer subsystem is delayed or hung such that return x-memory POST processing gets abend S102 or other problems, it is possible, depending on requestor memory reuse, to get random storage overlays. CICS abend processing is susceptible to this with IDIS running. | Validation of the return x-memory POST conditions checked before return. | | | 13 | DFHSR0606 Abend (23E/AKEB) detected after IDICALOC LOCFRESL DETACHing orphan TCB terminating CICS. | CICS DUMPCODE: SR0606 and termination after Fault Analyzer task management IDICALOC LOCFRESL DETACHing orphan TCB. The TCB address being detached is invalid. | Messages corrected to display the correct TCB=address and validation improved to prevent the condition. |
| | 14 | Abend S0C4 in PliSepSym when processing Enterprise PL/I SYSDEBUG side file. | PL/I PUT STRING statement causes symbol name pool to reside in program CSECT (instead of SYSDEBUG file), some of this storage might not be available. | Entire program and static CSECT storage now located. | | | 15 | Enterprise PL/I structure member has incorrect offset when variable with same name is used as a parameter. | When multiple instances of a variable name are declared in a block, an incorrect instance might be used. | The correct instance of the variable is now used. | | | 16 | DFHAP0701 An abend (code 0C4/AKEA) has occurred in exit IDIXCX53 at exit point XPCABND. | The Fault Analyzer IDIXCX53 exit when requesting CICS GETMAIN storage did not correctly handle the not available condition and caused an 0C4 that can terminate CICS. | The GETMAIN return checking has been corrected. | |
APAR PK74117 Fixes and Enhancements | | Problem | Description | Fix | Complete APAR information | | 1 | 0C4 in SearchDS while processing Enterprise PL/I program. | SERVICE string is an odd number of characters requiring an additional byte for halfword alignment. | Halfword alignment added when processing SERVICE string and subsequent saved options string. | PK74233 | | 2 | CICS Storage Violation SM0102 with Program IDIXCX53. | A trailing SAA is overlayed by Fault Analyzer IDIXCX53 when CICS trace data gathering fills at a buffer boundary. | The boundary code has been corrected to allow for the additional halfword end of records field. | PK74236 |
APAR PK72176 Fixes and Enhancements | | Problem | Description | Fix | Complete APAR information | | 1 | Dynamic allocation for dataset with HLQ of SILLY99 when Fault Analyzer is invoked | The code which checks for a suitable operating environments was making an unnecessary dynamic allocation for data set SILLY99.DATA88.SET77.NAME66.CHECK55. | The dynamic allocation has been removed. | | | 2 | Message: Report line threshold of 50000 lines reached - doubling the interval - being incorrectly displayed. | This message was supposed to be a diagnostic message for internal use only not to displayed to the user. | This message has been correctly changed to a diagnostic message. | | | 3 | PL/I event shows empty Associated Storage Areas panel. | No variables have been declared in an internal PL/I procedure. | New hotspot added to give access to caller's storage areas. | | | 4 | Fault Analyzer loops when processing variably located data items in a COBOL program. | The variably located data (BLV) has a bad address (eg. 0xFFFFFFFC) which causes WhatsNext() to return the same IANCHOR as that passed to it. | WhatsNext() now checks that the returned IANCHOR has an address higher than the IANCHOR passed to it. | | | 5 | Message IDI0020W issued if the NoErrorHandler option is specified. | The NoErrorHandler option is not recognized as a valid option. | The NoErrorHandler option is now recognized as a valid option. | | | 6 | Fault Analyzer abends when processing PL/I external variables. | Incorrect static csect length causes dLocate failure. | dLocate issued for adjusted section length. | | | 7 | IDI0005SIDIKEY:553 Storage allocation failed. | Analyzing a SYSMDUMP of an LE abend, a bad pointer results in an incorrect storage allocation to be attempted. | The call from DSAchain() had a bad KANCHOR pointer, which is now guarded against. | | | 8 | When a structure parameter is passed to a PL/I program, which has been compiled with PL/I for MVS & VM, the structure member offsets in the called procedure are zero. | PL/I for MVS & VM does not provide mapping for structure parameters, offsets appear as "ADJ" and total lengths as "PARAM". | Basic structure mapping is now performed by IDILANGX for parameter structures. | |
APAR PK69688 Fixes and Enhancements | | Problem | Description | Fix | Complete APAR information | | 1 | 0C4 abend occurs when Fault Analyzer calls __fmwsa for DeferredReport processing. | __fmwsa callback function issues longjmp() but setjmp() has not been called. | setjmp() now called before __fnwsa. | PK70037
| | 2 | PrtSystemWideOpenFiles() abends with 0C4 when more than 20 CICS Open Files (FLABs) are encountered. | FLABs are collected into a fixed 20 element array. | Grow array implemented for FLABs. | PK71109 | | 3 | COBOL source line accessed from register display hotspot is a comment. | The first source line for a given offset is selected regardless of whether it is a comment. | When determining the COBOL source line for a register address (which translates to base locator + offset), any leading commentary source lines are ignored. | PK71131 | | 4 | High CPU task loop in IDIS Fault Analyzer subsystem after IDI0117E message. | After the cancel of a end user waiting in Fault Analyzer processing and an IDI0117S ABNED=602 the server TCB in the IDIS subsystem can loop. | The rechaining of the work element during recovery processing was corrected. | PK71122 | | 5 | ICH408I ALTER access incorrectly requested of the ICF catalog if an ALIAS name was incorrectly used as a history file name. | In the Fault Analyzer interactive display panel, if the name of a history file to view is incorrectly entered as simply the high level ALIAS qualifier, the logic then incorrectly requests ALTER access to the Catalog containing the ALIAS. | The code is corrected to properly determine the invalid nature of the ALIAS name and give an appropriate message. | PK71522 |
APAR PK67411 Fixes and Enhancements | | Problem | Description | Fix | Complete APAR information | | 1 | IDI0047S internal abend S0C4. | Fault Analyzer report processing PrtAssociatedMessages() function can get S0C4 under conditions where message records have not been created. | Code changed to correctly check if message information is available. | PK69532
| | 2 | Fault Analyzer abends with 0C7 after selecting terminal IDs for CICS Trace. | Fault Analyzer is expecting the TCTTE transaction number to be a valid packed decimal value when, if fact, it may not be (eg. it could be 0x00000000). | Fault Analyzer now handles the TCTTE transaction number as byte data. | PK69534 | | 3 | Incorrect values in the ENV structure when a Notification user exit is invoked for CICS fast duplicates. | If the original fault entry, to which the fast duplicates refer, no longer existed, then the ENV structure was being populated from another cached fault entry, instead of being cleared. | If the original fault no longer exists, then the ENV structure is appropriately cleared. | PK69543 | | 4 | Abend S0C4 at entry point DSAchainTCB offset X'5592'. | An assumed register save area which was being processed, was spanning two 4K pages with different storage protection keys. | A check has been added to ensure that the entire register save area is accessible. | PK67429 | | 5 | Message IDI0101I, dump and analysis suppressed, even though running with NoCICSDumpTableExclude. | Exit program IDIXCCEE is losing addressability to a storage area which holds an indication of whether the CICSDumpTableExclude option is in effect. | Addressability to the storage area containing the CICSDumpTableExclude option is now maintained | PK68264 | | 6 | CICS message DFHSR0606 showing abend S878 during CICS operation. | The S878 abend occurred in the IDIS subsystem due to insufficient storage. | The IDIS GETMAIN has been made conditional to prevent the S878 abend. | PK69588 | | 7 | Unable to scroll horizontally to see a message explanation which exceeds 80 columns.
| The keylist used for the IDIPLOOK panel did not include settings of PF10 and PF11 to the LEFT and RIGHT commands respectively. | The LEFT and RIGHT commands have been added to the IDIPIKY8 keylist. | PK65073 |
APAR PK64341 Fixes and Enhancements | | Problem | Description | Fix | Complete APAR information | | 1 | Abend S0C4 in module IDIXCX53 at offset X'192F6'. | An incorrect return code check was being made and hence code was being executed which should not have been. | Problem Conclusion: 01. The return code check has been corrected. | PK66719
| | 2 | CICS Trace selection not working correctly with a large trace table when identifying all tasks for a specific terminal ID. | Incorrect processing of CICS trace sequence numbers and only the active task for a specific terminal was identified. | The sequence numbers are now processed correctly, and all tasks in the CICS trace table that have been started for a specific terminal are now being displayed. | PK64605 | | 3 | Abend S0C7 when an abending COBOL program has COMP-3 OCCURS DEPENDING ON variable of less than 3 bytes which contains invalid packed decimal data. | C built-in function decchk() returns DEC_VALUE_OK for 1 and 2-byte packed fields which contain bad data. | Packed decimal data of less that 3 bytes is promoted to 3 bytes before calling decchk(). | PK64623 | | 4 | Associated Storage Areas missing with Enterprise COBOL 4.1 events. | Enterprise COBOL 4.1 product number (5655-S71) not recognized by Fault Analyzer. | Product number 5655-S71 has been added. | PK65132 | | | | | | | 5 | Abend S0C4 in PrtOptions at offset X'3F5C'. | Unallocated storage beyond the end of a character string was being referenced. | A check has been added to ensure that the storage past the character string is only referenced when it is known to have been allocated. | PK66720 | | 6 | Abend S0C4 in generateDBRMKeyData offset X'257E'. | An SQL statement was obtained in ASCII from the SYSIBM.SYSDBRM DB2 table, when EBCDIC format was expected. This caused a search for host variable name colons to fail. | ASCII SQL statements are now converted to EBCDIC prior to processing the host variable names. | PK65381 | | 7 | IDIXDCAP abend S0C4 at offset X'1AE4'. | An abend occurred in the MVS subsystem interface, causing the IDIXDCAP ESTAE exit to unexpectedly receive a SDWA in a storage key other than 8. | The code has been changed to handle a SDWA in any storage key. | PK66736 | | 8 | Abend S0C4 in WriteMiniDump. | When Fault Analyzer is saving analysis of a system dump, it might get abend S0C4 in WriteMiniDump +7B6. | Code added to allow only 2K to be moved when low core is addressed. | PK66813 | | 9 | Loop in Fault Analyzer when analyzing CICS Temporary Storage queue control blocks. | One or more digital tree nodes have been overwritten. Fault Analyzer needs to reference these nodes to identify temporary storage queues. | All 'down pointers' in the nodes are now checked for double word alignment. If this check fails, then processing of the nodes and queues is abandoned, and a new severity 2 message is displayed. | PK66741 | | 10 | Fault Analyzer S0C4 in GetStgMem() when re-analyzing PL/I abend with a side file. | If no side file is available at the time of the abend, then storage for based variables is not included in the minidump, and subsequent re-analysis using a side file might attempt to access this storage, possibly causing abend S0C4 in GetStgMem(). | Bad basing pointers (i.e., pointers to storage not in the minidump) are identified and reported in the Associated Storage Areas section. | PK66805 |
APAR PK61879 Fixes and Enhancements | | Problem | Description | Fix | Complete APAR information | | 1 | IDILANGX issues messages IDISF8132S and IDISF8136S when processing Enterprise COBOL V4.1 compiler listing. | The Enterprise COBOL V4.1 compiler is not recognized by IDILANGX. | IDILANGX now recognizes the Enterprise COBOL V4.1 compiler. | PK62386
| | 2 | Task is missing on the CICS system dump analysis Task Summary display. | Summary lines are built for each task which has a Task Control Area (TCA), but the missing task is terminating and no longer has a TCA. | The CICS Kernel and transaction manager control blocks are now used to build and display summary lines for tasks without a TCA. | PK61337 | | 3 | COBOL SIGN IS LEADING/TRAILING SEPARATE CHARACTER clause causes incorrect reporting of data field values. | The instruction operands, when processing these data fields, do not necessarily point to the start of the data (for example, the PACK instruction operand for LEADING points passed the SIGN byte). | The data field addresses have been corrected. | PK62200 | | 4 | Copy to data set from the ISPF interface Services pull-down menu copies the visible display content only. | Implicit 'max down' missing to obtain lines beyond the visible screen depth. | Implicit 'max down' added. | PK63864 | | | | | | | 5 | Information about CICS-managed files not provided in 'Open Files' section of the analysis report. | CICS file control data areas are not referenced during the creation of the 'Open Files' report. | For CICS transaction abend analysis, CICS file control data areas are now referenced. | PK63708 | | 6 | Unable to specify compiler listing or side file data set name on prompt during interactive reanalysis if no TSO prefix set. | When using TSO PROFILE NOPREFIX, the data set name specified on the prompt during interactive reanalysis was being processed incorrectly, causing the prompt to reject the specified data set name. | The specified compiler listing or side file data set name is now processed correctly, even when TSO PROFILE NOPREFIX is used. | PK63362 | | 7 | Options on initial interactive reanalysis menu disappear after formatting event details. | A flag was being incorrectly set as part of the event formatting process, which caused the initial menu to be incorrectly re-displayed. | The flag is now correctly set and restored. | PK62209 | | 8 | Enterprise PL/I compiler listing created with RENT option in effect results in blank CSECT names in the IDILANGX X'0E' record. | The EXTERNAL SYMBOL DICTIONARY section of the compiler listing uses a single column, but the code expects two columns. | Code added to support 1 or 2 columns. | PK63867 |
APAR PK56116 Fixes and Enhancements | | Problem | Description | Fix | Complete APAR information | | 1 | Message IDI0032W I/O error writing report: EDC5003I truncation of a record occurred during an I/O operation. | Invalid DB2 GRAPHIC type host variable data was not being adequately validated before attempted written to the report. | Improved validation has been added. | PK61638
| | 2 | Abend S0C4 in mapCsectEntryPoint() when analyzing a CICS system dump. | Invalid key data was being added. | The invalid key data has been corrected. | PK61641 | | 3 | IDI0095W Unexpected condition found in IDIDODSN:287 when creating a CICS system dump fault entry. | After analyzing a CICS system dump with Fault Analyzer, the fault entry save process can get an IDI0095W error from IDIDODSN:287. | The logic has been changed to correctly accommodate the failing page boundary condition. | PK58322 | | 4 | Message IDI0047S abend S0C4. | An invalid argument was passed to the sprintf C run-time function from formatSummary + X'E7E'. | The sprintf argument has been corrected. | PK56569 | | 5 | When formatting COBOL data division, a 'Storage range xxxxxxxx-xxxxxxx not accessible' message is issued. | The base locator dictionary item length is 'trimmed' by an assembler DSECT, which redefines COBOL storage. | DSECTs have been excluded from dictionary items that can 'trim' COBOL base locator storage lengths. | PK57338
| | | | | | | 6 | When formatting COBOL data division, a 'Storage range xxxxxxxx-xxxxxxx not accessible' message is issued. | The base locator dictionary item length is 'trimmed' by an assembler DSECT, which redefines COBOL storage. | DSECTs have been excluded from dictionary items that can 'trim' COBOL base locator storage lengths. | PK57337 | | 7 | Message IDI0006E issued without a data set name. | The data set was eliminated from the associated DDname due to READ access checking wrongly assuming lack of access authorization, when in fact the data set did not exist. | If a data set does not exist, then it is left in the list of data sets for a DDname so that it is available if open error messages are issued. | PK61642 | | 8 | Incorrect length presented for second operand of an MVCL (Move Characters Long) instruction. | Bits 0-7 of the MVCL source length register represent a padding character. This was not being taken into account when presenting the length. | The length is now derived from bits 8-31 of the source length register. | PK61646 | | 9 | Fault Analyzer abends or produces incorrect results when CMPAT(V1) is used with Enterprise PL/I SYSDEBUG files. | Fault Analyzer does not support CMPAT(V1) descriptors. | Support for CMPAT(V1) descriptors has been added. | PK57980 | | 10 | Enterprise PL/I SYSDEBUG sidefile is rejected when OPTIMIZE is in effect. | Truncated PPA4 does not supply rostatic, rwstatic, or blkbase, which are used to locate static storage. | Alternative method for locating static storage and CUI implemented. | PK61690
| | | | | | | 11 | Fault Analyzer loops when reporting registers for a COBOL program with sidefile provided. | The data item pointed to by the register was not on the abending source line, and has a REDEFINES. | The source line checking for a variable is bypassed when the function is called from the register display. | PK61691 | | 12 | Panel IDIPABOT corruption when selecting "About Fault Analyzer" from the ISPF interface Help pull-down menu with Language(JPN) in effect. | The second byte of a two-byte DBCS character was missing from the ISPF dynamic area that was generated for the "About Fault Analyzer" display. | The invalid DBCS character has been corrected. | PK58689 | | 13 | Message IDI0130E Response from IDIS subsystem not returned within 2 minutes, request canceled. | A loop in the IDIS subsystem caused the request to time out. | Improved loop detection has been added. | PK58647 | | 14 | The history file data set remains allocated to a CICS job. | The allocation that was made during the recording of CICSFAST duplicates was not being freed. | The allocation is now freed. | PK58899 | | 15 | Message IDI0047S abend S0C4 in LE run-time function strspn, called from PrtHostVars during formatting of DB2 VARCHAR host variable data. | An ending NULL character was not added to the end of the buffer. | The ending NULL character has been added. | PK58960 | | 16 | Table element stride is incorrect when using COBOL SYSDEBUG sidefile. | Non-OCCURS DEPENDING ON (ODO) tables are being re-calibrated when a program contains one or more ODO tables. | The re-calibration logic has been corrected. | PK61685 | | | | | | | 17 | History file specified by Analysis Control user exit in ENV.IDIHIST does not override IDIHIST DD statement specified in JCL. | The exit-specified history file name was incorrectly being overridden by the pre-allocated IDIHIST data set name. | The exit-specified history file name in ENV.IDIHIST now always overrides any other specification, including pre-allocation via JCL DD statement. | PK59426 | | 18 | XFACILIT-managed data set access is not working correctly with ACF2. | The internal settings used during the management of XFACILIT-controlled data sets were not compatible with ACF2. | Settings which are equally applicable to ACF2 and RACF are now being used. | PK59784 | | 19 | Interactive fault entry reanalysis under CICS is failing with system abend code S23E. | After a terminal session error while performing interactive fault entry reanalysis under CICS, Fault Analyzer attempted to DETACH the subtask twice, which caused a S23E system abend. Fault Analyzer has been changed to ensure that the DETACH is issued only once. | Changed to supervisor state key 0 while determining if LE is active for the abending TCB. | PK60297
| | | | | | | 20 | Corrupted Japanese text in the formatted storage display, or failure to successfully copy the display to a data set with the COPY command. | The display contains invalid DBCS characters due to missing shift-in characters. | The missing shift-in characters have been added. | PK61696 | | 21 | Abend S0C4 in makeString() during CICS system dump analysis when processing 3-character transaction number (for example, TCP) from KE Error Table Summary. | A wrong value was passed to makeString(). | The transaction-number processing has been corrected. | PK61697 | | 22 | Missing DB2 Information section in the analysis report. | The validation of the DB2 request parameter list did not correctly determine that the parameter list was in the LE heap. | The DB2 request parameter list validation routine has been corrected. | PK61700 | | 23 | Abend S0C4 in IDICBIMS offset X'336'. | An invalid offset into an IMS control block was being used during NoDup(ImageFast(...)) processing. | The IMS offset has been corrected. | PK61284 |
APAR PK50466 Fixes and Enhancements | | Problem | Description | Fix | Complete APAR information | | 1 | Initial paragraph on panel IDIPILPT is truncated. | An inappropriate DTL tag, which does not allow formatting of more than one line, was being used. | A different tag has been used to permit text which exceeds one line to be formatted correctly. | PK50725 | | 2 | Updated string translations causing formatting errors. | Updated translations of some character strings are no longer displayed correctly due to incompatibility with the base function code. | The character string updates have been removed. | PK56302 |
| Problem | Description | Fix | Complete APAR information | | 1 | The RetainCICSDump(ALL) option is not working correctly, resulting in CICS transactions dumps being suppressed. | The setting of RetainCICSDump(ALL) option is not being correctly validated. | The RetainCICSDump(ALL) option is now being correctly validated. | PK52731
| | 2 | Side file for abending COBOL event is not being used, resulting in missing analysis report source line information. | Previous event's R15 is not pointing at the following COBOL event's entry point. | Alternative method for determining COBOL entry point address implemented. | PK53354 | | 3 | Last executed DB2 SQL statement not shown in report. | Validation of a COBOL program's DB2 SQL parameter list in WORKING-STORAGE failed as it was attempted to relate this to an entry point instead of the CSECT. | The COBOL WORKING-STORAGE DB2 SQL parameter list is now validated against the CSECT instead of an entry point. | PK53331 | | 4 | An S0C4 abend occurs in function pp_ueh_main due to an invalid reference to an array of global user exit names. | New exits in CICS TS 3.1 and TS 3.2 are not defined in the array of user exit names. | The names of global user exits which are new in CICS TS 3.1 and TS 3.2 are now defined to Fault Analyzer. | PK54751 | | | | | | | 5 | Not all of a CICS task's allocated storage is included in the minidump. | Only the first and last 4K of each storage area was being included in the minidump to allow for storage overlay checking. | The complete storage area is now included in the minidump. | PK55178 | | 6 | PIC declared structure members are not assigned an address when using an Enterprise PL/I SYSDEBUG side file. | Descriptor processing is incorrect for PIC declared character strings when they are structure members. | Descriptor processing has been corrected. | PK55181 | | 7 | Message IEC036I 002-18 followed by message IDI0124E might be issued from the IDIS subsystem. | In situations where a high number of duplicate abends occur for the same fault entry, a record length error can result in message IEC036I 002-18 being issued in the IDIS subsystem. | The record length problem on writing to the history file $$INDEX member has been corrected. | PK53346 | | 8 | Abend S0C4 in IDIDA DFHTT640 when formatting a socket domain CICS trace entry. | An abend S0C4 might occur on a MVCL instruction in DFHTT640 when formatting a CICS socket domain trace entry. | Code in the the call interface to DFHTT64 has been changed to circumvent the wrong length move problem. | PK55307 | | | | | | | 9 | Poor analysis performance when a job causes many WTO messages that do not start with a formal message ID to be issued. | An attempt was being made to find an explanation for the presumed message ID at the start of each WTO message. | Improved verification of the presumed message ID has been implemented to avoid the overhead of searching for a message explanation when none exists. | PK55474 | | 10 | Message IDI0092S time-out after 32 minutes. | When writing a large report, the time expected for completion was being incremented repeatedly until the maximum of 32 minutes was reached. | The expected time for completion of a large report is now incremented only once. | PK55482 | | 11 | SYSUDUMP not suppressed when a Fault Analyzer warning message (W level) is issued. | The return code set when any Fault Analyzer messages, other than informational messages (I level), were issued, caused the MVS dump (SYSUDUMP, SYSMDUMP, or SYSABEND) to not be suppressed with the RetainDump(AUTO) option in effect. | A change has been made to ensure that only severe error messages (S level) will cause the MVS dump to not be suppressed. | PK55487 | | 12 | Fault Analyzer event list 'loaded from' might be 'n/a' if the data set has EXECUTE ONLY security access. | When the load data set security is 'EXECUTE ONLY', then the Fault Analyzer event list 'loaded from' column might show 'n/a' instead of the load data set name. | The logic path encountering the 'EXECUTE ONLY' access has been corrected to retain the load data set name. | PK55432 |
APAR PK49788 Fixes and Enhancements |
APAR PK45989 Fixes and Enhancements | | Problem | Description | Fix | Complete APAR information | | 1 | When a COBOL SYSDEBUG file is entered via the 'Compiler Listing Not Found' prompt, and a mismatch is detected, then the mismatch is not accepted when Enter is pressed. | A logic error in re-processing of the SYSDEBUG file prevented its final acceptance. | The re-processing logic has been corrected. | PK49397
| | 2 | Message IDI0092S time-out. | An unintended loop occurred at entry point LastRDW. | The condition that caused the loop has been accounted for to prevent the loop from happening. | PK46639 | | 3 | IDI0047S IBM Fault Analyzer internal abend S0C4. | Fault Analyzer is attempting to reference fetch protected storage. | An additional check has been added for fetch protected storage in Fault Analyzer's storage access fast path function. | PK49413 | | 4 | Abend S0C4 at entry point IDICTDB2 offset X'A4'. | An invalid TCB address was passed to the routine. | A check has been added to prevent the invalid TCB address from being used. | PK46907 | | | | | | | 5 | Never ending loop processing a damaged Language Environment stack segment chain. | Control blocks have been damaged in such a way that a next segment pointer points to itself. | The next segment pointer is now compared with the address of the segment just processed. If equal, then a message is issued and processing of the segment chain is abandoned. | PK47038 | | 6 | Message IDI0095W IDIRFRDS ASASYMBM(data-set-name-pattern) substitution rc=8. | The output buffer size used for the ASASYMBM MVS symbol substitution service was insufficient. | The ASASYMBM MVS symbol substitution service output buffer size has been incremented, and the resulting data set name truncated if exceeding 44 characters (or 43 characters, if the 44th character is a period). | PK47274 | | 7 | Message IDI0105S due to Fault Analyzer internal abend. | Damage to LE control blocks, the CIB and MCH, resulted in Fault Analyzer attempting to allocate a zero amount of storage. | Unless at least one CIB and its associated MCH can be located, further CIB processing is abandoned, and this avoids a zero storage allocation attempt. | PK49331 | | 8 | Abend SE37-04 in IDILANGX when a very large compiler listing is processed. | When Fault Analyzer calls the IDILANGX program to process a very large (around 500,000 lines) compiler listing, the temporary data set might get abend SE37-04. | A larger temporary data set is now being allocated. | PK49469 | | | | | | | 9 | Abend S0C4 in Language Environment initialization of the IDICCFND program. | IDIPLT or IDIPLTD issue an MVS ATTACH for the IDICCFND program with a parameter list assembled into the calling program. In a busy system, the calling program might be deleted before LE initialization for IDICCFND has been started or completed, resulting in GPR1 becoming invalid. | A parameter list is no longer passed. Instead, register 1 is set to zero before the ATTACH is issued. | PK49472 | | 10 | Message IEW4000I and CSV031I for load failure of CEEEV003 after an application abend causes Fault Analyzer to be invoked. | The load check of CEEEV003 had not detected the module was in STEPLIB and had assumed load space would not be required because a copy was available in LPA. | The logic is changed to include the load space requirement in the case of modules also in STEPLIB and currently available in LPA. | PK49475 | | 11 | IDI0047S IBM Fault Analyzer internal abend S0C4. | LE heap storage was overlaid due to insufficient buffer size. | The size of the allocated buffer has been corrected to prevent the problem. | PK49476 | | 12 | Fault Analyzer abends in FmtCobData, or base locator offsets in the Associated Storage Areas are incorrect. | Wrong base locator numbering system used with COBOL for OS/390 & VM 2.1 (Note that COBOL for OS/390 and VM 2.1 is unaffected--that is, with 'and' not '&'). | Hexadecimal base locator numbering implemented with COBOL for OS/390 & VM 2.1. | PK49385 | | | | | | | 13 | Enterprise PL/I SYSDEBUG file is not located unless an IDISYSDB DD is used. | The SOS (saved options string) was incorrectly assumed fixed length, resulting in the SYSDEBUG file name that follows this string to not be located. | The varying length saved options string is now being processed correctly. | PK48372 | | 14 | Abend S0C4 in GetPLIStmt when analyzing OS PL/I 2.3 event. | The Statement Number Table header contains an invalid pointer. | All pointers in the Statement Number Table are checked for addresses within the static CSECT. | PK48468 | | 15 | Abend ASRA in IDIXCX53 + x'2F9E'. When analysis is skipped due to MaxWaitSeconds exceeded and the invocation was for an EXEC CICS DUMP. | Certain control blocks were not being restored to their correct initial state, which lead to subsequent abends. | All control blocks are now correctly restored. | PK49478 | | 16 | IDIPLT and IDIPLTD are RMODE 24. | Code structure was causing RMODE 24. | Code has been restructured to allow RMODE ANY. | PK49480 | | | | | | | 17 | Incorrect storage values shown for PL/I when storage class changes within AUTO/STATIC section (eg. STATIC->BASED->STATIC). | The storage pointer is not set correctly. | The storage pointer has been corrected. | PK49388 | | 18 | Message IDI0120S IBM Fault Analyzer internal abend S002 U0000 following message IEC036I 002-18 for the history file data set. | The CICS trace entries gathered for the abending task were too long for an internal segment. This caused the write error when the segment was written to the history file data set. | The code was altered to stop the segment length from being exceeded. | PK49481 | | 19 | Side file not used when COBOL program terminated via VAGEN CICS abend handler (ELAESABD). | Incorrect entry point address used. | Entry point address corrected. | PK49483 |
APAR PK42493 Fixes and Enhancements | | Problem | Description | Fix | Complete APAR information | | 1 | When specifying a large value (eg. 32000) with the LC compiler option, Enterprise PL/I compiler listing causes IDILANGX to fail with rc=1551. | Storage allocation based on LC value fails. | Storage allocation removed. This was only relevant to non-Enterprise PL/I listings. | PK45830 | | 2 | Parameters passed from COBOL to PL/I are not shown when data are aggregates (structures, arrays, strings). | Parameters were not recognized as having been passed from COBOL. | Implemented support for parameters passed from COBOL. | PK45835 | | 3 | Abend S0C4 in entry point splitString or loop involving entry points splitString and PrtRecord. | With Language(JPN) in effect, a situation where a 'shift in' character (X'0F') was inserted at the rightmost character position in the report, due to a long sentence being wrapped over multiple lines, was not handled correctly. | The wrapping of long DBCS strings is now handled correctly. | PK42956 | | 4 | SMP/E apply of IDIWTSEL usermod causes message GIM50301E. | The maximum length for the usermod name is 7 characters, not 8 as specified in the sample. | The sample job has been modified to use a 7-character usermod name. | PK45838 | | | | | | | 5 | PL/I compiler option LC (LineCount) causes IDILANGX to fail with RC=1551 when large values (eg. 32000) are used. | Memory allocation failure due to insufficient storage. | IDILANGX now uses a logical page not exceeding 100 lines. | PK45840 | | 6 | Intermittent abend S0C4 in IDIDA at offset X'12EE4' when invoked via IDIXDCAP. | In the process of issuing an IDI0005S message, an invalid pointer was being used for a FREEMAIN. | The invalid pointer reference has been corrected. | PK45845 | | 7 | CFA transaction incorrectly reporting exit status as uninstalled. | A NOTAUTH condition from the INQUIRE EXITPROGRAM command was not being correctly reported to the user. | The NOTAUTH is now reported to the user. | PK45911 | | 8 | Abend S0C4 at entry point ReadAtts. | A 32-character symbol name exceeded the size of a program variable. | The size of the variable has been increased to 256 characters. | PK45880 | | | | | | | 9 | Abend S0C4 in GetPLIStmt() occurs when NOGOSTMT compiler option and Fault Analyzer DeferredReport option is in effect. | Statement Number Table 'stub' not recognized, causing an invalid address to be used. | GetPLIStmt() quits when 'stub' statement number table is recognized to prevent the use of an invalid address. | PK45905 | | 10 | Abend S0C4 in IDILANGX when processing a C/C++ compiler listing. | An incorrect reference to an array that is not initialized for C/C++ was being made. | Code corrected to not refer to an array that is not initialized for C/C++. | PK45907 | | 11 | An event is not created for the user's abend. | The DSA belonging to CEEHDSP chains back to the Dummy DSA and causes Fault Analyzer to miss the DSAs belonging to the application. Several events are 'missed', including the CIB. | When Fault Analyzer processes the Dummy DSA, and there is still a CIB to be processed, an event is created for the CIB and register 13 in the CIB is used to backchain through the application's DSAs. | PK45908 |
APAR PK39001 Fixes and Enhancements |
APAR PK35094 Fixes and Enhancements | | Problem | Description | Fix | Complete APAR information | | 1 | IDI0005S IDIDODSN:2211 Storage allocation for 32768 (X'8000') bytes failed - processing terminated | Storage allocations accumulated when processing large working-storage sections, base locator by base locator, cause excessive storage to be used. | Working and local storage sections now use a single large allocation. | | | 2 | PL/I source file 0 appears as n/a when viewing a compiler listing interactively. | The Enterprise PL/I source file 0 support was incomplete. | Source file 0 is now supported for Enterprise PL/I. | | | 3 | COBOL function pointers are not presented as hexadecimal data. 6. | IDILANGX did not recognize the COBOL Function-Ptr data type in the map section of the compiler listing. | COBOL Function-Ptr data types are now recognized and presented as hexadecimal data. | | | 4 | Loop during CICS system dump analysis at entry point dfhs_appopl. | Pointers to user TCAs are corrupted in XM (Transaction Manager) task control blocks. Neither the user, nor the system TCA, can be located. The loop occurs in a routine which is attempting to follow the TACB chain. | The pointer in the user TCA to the system TCA is checked. If invalid, no attempt is made to analyze the system TCA or the TACB chain. A new severity 2 notice is added to the report in this situation. | | | | | | | | 5 | Failure to locate compiler listing results in missing source information for Enterprise PL/I | The side file member name is derived from the first procedure found in the CSECT (assumed to be the primary entry point, whose label is the program name). EPLI 3.6 reverses the sequence of procedures in the object code so the first procedure's code is at the end of the CSECT. | New function added to locate the entry point based on the CSECT name (which is derived from the entry point name). | | | 6 | IDITRACE ON/OFF not working in CFA transaction. | The introduction of a statistics flushing TCB had the potential of stopping the PF11 IDITRACE ON/OFF function from working in the CFA transaction. | The code has been corrected to allow for the additional TCB. | | | 7 | Incorrect load library shown in Event Summary section of report for module loaded from CICS DFHRPL concatenation. | Due to READ access checking of all data sets, including the CICS DFHRPL concatenation, data sets to which the user does not have access are removed from the concatenation. This resulted in a mismatch between the expected relative concatenation number and the truncated list of data sets. | The up-front READ access checking of DFHRPL data sets has been removed. The READ access checking will still be performed later if calling the Binder, but this will not affect the reporting of the correct data set name. | | | 8 | Hung abending task in CICS or batch if IDIS subsystem is not responding. | If the IDIS subsystem is not responding because of lockout on a history file, then the recovery fault recording process could hang until cancelled. | A STIMERM process has been added around recovery fault recording access to the IDIS subsystem to automatically terminate in the case of a hang condition. | | | | | | | | 9 | Loop in CICS kernel stack entries processing. | Fault Analyzer is attempting to place stack entries in their correct chronological order, but control block damage in CICS is causing a never-ending loop. | Code has been added to Fault Analyzer to abandon stack entry processing after a certain number of attempts. | | | 10 | Abend S0C4 in Fault Analyzer when COBOL/2 abends during start-up processing. | A bad parameter reference was passed. | The parameter reference has been corrected. | | | 11 | Abend S0B0-X'3C' in IEFQB551, abend S05C-X'214' in IEFW21SD, or abend S0C4-X'4' in IDIXDCAP entry point DCAPSUB offset X'139C'. | Analysis is attempted for an abend in a non full-function allocation address space, or an address space started with SUB=MSTR. Under these conditions, dynamic allocation is either not supported, or is likely to fail. | Checks have been added to ensure that analysis is not attempted if an address space is started with SUB=MSTR, or is not in full-function allocation mode. | | | 12 | When invoking Fault Analyzer using IDISNAP under CICS, the user exit ENV.INVOCATION_EXIT variable is set to 'C' instead of 'S'. | When initializing the ENV.INVOCATION_EXIT field, no checking for IDISNAP was done when called under CICS. | The ENV.INVOCATION_EXIT field is now correctly set to 'S' when Fault Analyzer is invoked by IDISNAP, regardless of the execution environment. | | | | | | | | 13 | Loop and IDI0092S message when CEEWUCHA exit is active and EXEC CICS HANDLE ABEND is used. | Special processing of an incomplete CIBH is not checking if the pointer to the CIB is zero. | Special processing of the CIBH now checks for a zero CIB pointer, and when zero, exits CIBH processing. | | | 14 | Fault entry CPU time reported from IDIUTIL ENV.CPU_HSECONDS is zero. | The CPU_HSECONDS value, that can be accessed from IDIUTIL, was not being correctly recorded. | The code has been corrected to record the CPU time used. | | | 15 | Possible abend S23E/AKEB in IDIXCX53 when Fault Analyzer is attached during CICS shutdown. | An attempt to DETACH a statistics recording TCB during CICS shutdown was being made. | A check is now made prior to the attempted DETACH to see if CICS is shutting down. | | | 16 | Message IDI0092S time-out might occur during Fault Analyzer processing. | The IDI0092 time-out process attempts to terminate Fault Analyzer execution to prevent loops and wait conditions. At times, the determination of a loop or wait is not correct. | This change adds an additional mechanism to try and ensure that the time-out processing does not trigger prematurely. | | | | | | | | 17 | Abend S0C4 program check in IDIXDCAP when invoked for a storage shortage type abend, for example S878. | IDIXDCAP is calling the Recovery Fault Recording process, passing the address of an uninitialized buffer containing addresses, which is subsequently causing a store to location zero. | IDIXDCAP is now passing a zero buffer address, which is recognized as there being no buffer passed. | | | 18 | IDIWRITE: Buffer space exhausted - record not written message when using REXX variable in IDIWRITE call. | The potential existed for a buffer length to be incorrectly determined and hence lead to the buffer space exhausted message. | The length check is now correctly determined. | |
APAR PK32559 Fixes and Enhancements | | Problem | Description | Fix | Complete APAR information | | 1 | Failure to locate COBOL TEST(,,SEPARATE) SYSDEBUG side file. | The attempt to locate the side file occurred prior to having determined the necessary details about the program being analyzed. | The order of processing has been corrected so that the side file is not attempted to be located prematurely. | PK34452 | | 2 | COBOL data items declared on base locator boundary result in offsets shifted by 1 byte. | Offset fix-up for IDILANGX symbol records incorrect. | Offset fix-up for IDILANGX symbol records now occurs for all data items, other than items at base locator zero, offset zero. | PK34454 | | 3 | Abend S0C7 followed by abend S0C4 during analysis of CICS system dump. | An attempt was made to unpack an invalid packed decimal number. | The code now validates the packed number before using it. | PK34604 | | | | | | | 4 | Abend S0C4 during findstack processing. | An uninitialised pointer was leading to an abend S0C4. | The pointer is now being correctly initialized. | PK34456 | | 5 | Abend S0C4 in entry point DoSubVals when PL/I abending statement contains both an array and non-array variable with the same name. | When the PL/I abending statement contains two variables of the same name, one being an array and the other not, the wrong symbol is accessed as the array. This symbol contains a zero pointer, which eventually causes an abend S0C4. | The code now correctly identifies the array symbol when parsing the application source line. | PK34603 | | 6 | IDILANGX loop near label FIND_ID when processing PL/I compiler listing. | When multiple instances of a variable name are assigned to structure members, and one of these is used in a BASED(ADDR) expression, checking of ancestors causes a loop if an ancestor does not have an owner. | Ensured that ancestors without an owner will break the loop. | PK34602 | | | | | | | 7 | COBOL Level 88 point-and-shoot fields do not appear in formatted storage when using a SYSDEBUG sidefile. | Support for COBOL Level 88 items via SYSDEBUG file not implemented. | COBOL SYSDEBUG file now includes support for Level 88 items. | PK34458 | | 8 | PL/I external variables are not reported, or reported at incorrect addresses. | Duplicate variable names cause wrong symbol to be updated. | Symbols not updated unless scope is known. | PK34600 | | 9 | Return code 3128 from IDILANGX when used under SCLM. | An additional open of the listing data set, used for DCB information extraction, was causing subsequent errors under SCLM. | The information extacted by the additional data set open is now determined via DYNALLOC, which stops the rc=3128 under SCLM. | PK34599
| | 10 | Abend S0C4 in IRXINIT offset X'A36' during REXX initialization. | It is a REXX restriction that the job step TCB (TCBPKF) must be key 8. A check was made for a non-zero key, other than 8, when it should have included key 0 also. | The check for an environment in which REXX is supported has been changed to include key 0 as an unsupported environment. | PK34524
| | | | | | | 11 | IDIXDCAP entry point DCAPSUB offset X'4D6' abend S0C4. | The current method of changing the PSW key to 8 did not work correctly when the abending TCB was not key 8. | Changed the method used for setting the PSW key to one that is not affected by the abending TCB key. | PK34585
| | 12 | An S0C4 program check is occurring in entry point findStack. | A PPA1 block is being incorrectly analyzed in a JVM function which leads to incorrect entry name length being determined and an attempt to write to protected storage. | The PPA1 is now correctly analyzed. | PK34586
| | 13 | Missing event in analysis of S0C1 program check. | Fault Analyzer failed to determine the entry point of the abending program, and thus did not create an associated event. | Code has been added to identify the entry point and create an event for the abending program. | PK34587
| | | | | | | 14 | ImageFast(IMS) does not select INCLUDE(IMSTYPE(IFP)) for Fast Path regions. | The RCTYPE flag checking for Fast Path regions did not include RCBMP. | The RCTYPE flag checking has been corrected. | PK34588
| | 15 | Incorrect properties display for empty history files. | Unitialized storage being used when displaying information for an empty history file. | Code changed to correctly handle empty history files. | PK32558
| | 16 | BMC MV S0C4 due to TCBCAUF invalid | Field TCBCAUF was not being cleared if abend analysis was being skipped due to EXCLUDE option processing. | TCBCAUF is now correctly cleared. | PK34598
| | | | | | | 17 | Abend S378-X'14' or S0C1 abends during or following calls to a Compiler Listing Read user exit. | A work area pointer used by an earlier Message and Abend Code Explanation user exit call had not been cleared. | The work area pointer has been cleared. | PK34589
| | 18 | Abend S0C4 in IDnotify + X'33C'. | The abend is caused by a storage overlay, resulting from the use of an entry point name that is longer than 198 characters. | The code has been amended to handle entry point names of any length. | PK34590
| | 19 | Hang ENQ lockout on IDIDA SYSOUT after load failure on IDIDA. | Load failure S106 abend during ATTACH of IDIDA causes ENQ lockout on major IDIDA minor SYSOUT. In this case it was a DB2 stored procedure region running out of storage that caused the load failure. | The code that detects recursion was enhanced to also recognize an ATTACH load failure of IDIDA. | PK34592
| | 20 | Message IDI0070E incorrectly displayed using CFA transaction in a CICS 4.1 region. | The CFA transaction is trying to determine the CICS release using a table and lookup mechanism, which is failing to find a table entry for CICS 4.1. | The table and lookup mechanism has been corrected. | PK34593
| | | | | | | 21 | IDILANGX rejects PL/I compiler listing when both LIST and OFFSET options are specified. | Options checking is incorrect. | Options checking corrected, either LIST or OFFSET + STORAGE are required. | PK34597
| | 22 | Incorrect events created. | An invalid DSA bcakchain pointer is not being detected. | Additional DSA checks are now performed, which prevent the incorrect events from being created. Also, a note about this is now displayed in the event details section of the report. | PK34594
| | 23 | COBOL source code is not presented if compiler listing contains FIPS messages. | FIPS messages are not recognized by IDILANGX, resulting in further (and incorrect) processing of INITD, giving a bad CSECT length. If this is less than the abend offset into CSECT, then no source code is presented. | FIPS messages are now recognized by IDILANGX. | PK34595
| | 24 | Abend S0C4 or LE abend U4094 during analysis of DB2 fault. | An LE heap storage overlay was caused by invalid offsets used to insert DB2 host variable names into the DBRM SQL statement. | The host variable name offsets are validated before being used. | PK34596 |
All available Version 6 Fault Analyzer PTFs and associated APARs (most recent first):
APAR PK95573 Fixes and Enhancements | | Problem | Description | Fix | Complete APAR information | | 1 | 01. The same PL/I ONCODE condition is shown against multiple PL/I events. | The check for the same PL/I Library Workspace did not allow a PL/I routine to be calling another language, such as COBOL, before abending in another PL/I subroutine. | A PL/I Library Workspace is now only reported on once, regardless of any intermediate inter-language calls. | PK95569 | | 2 | Fault Analyzer with IDISPLI or IDISPLIA usermod installed is incorrectly invoked for PL/I V2R3 ONCODE 4 conditions. | No special check was made for a PL/I ONCODE 4 condition, which should be ignored. | A check has been added to prevent Fault Analyzer from being invoked for a PL/I V2R3 ONCODE 4 condition. | PK96432 |
APAR PK89336 Fixes and Enhancements | | Problem | Description | Fix | Complete APAR information | | 1 | Abend S0C4 following BALR with bad R15 from function searchAbendTreeRec(). | An uninitialized function address was being used. | The function address has been correctly initialized. | PK89462 | | 2 | Incorrect PL/I or C/C++ source line for offset reported when multiple lines have same offset. | The first source line at the given offset was selected. | The last source line at the given offset is now selected. | PK92448 | | 3 | Abend S0C4 in load module IDIXDCAP at entry point DDfclose offset X'80'. | An invalid work area address was being used for data set close processing after a failure to open the CEE.SCEERUN LE run-time library. | A check has been added to not attempt closing the LE run-time library if it has not been opened successfully. | PK89919 | | 4 | Abending event appears as first user event, when it should be the last. | Comparison using register 13 values gives wrong result because the hi-order bit is on. | The hi-order bit has been masked out for register comparison. | PK92465 |
APAR PK83696 Fixes and Enhancements | | Problem | Description | Fix | Complete APAR information | | 1 | Incorrect highlighting of CICS Trace entries when using default interval (0.128). | The default interval was not explicitly set. | The default interval is now explicitly set. | PK88718 | | 2 | Fault Analyzer invoked when QUIT ABEND issued in Debug Tool. This does not happen under CICS where analysis is skipped. | The detection of the QUIT ABEND command was only being performed by the Fault Analyzer CICS LE exit. | Both the CICS and non-CICS LE exits now check for the QUIT ABEND command. | PK88678 | | 3 | No minidump is written to a new fault entry and no message is issued to explain why. | The number of minidump pages about to be written exceeded the expected number due to the use of an unsigned halfword instead of an integer to hold the count. The minidump was subsequently suppressed. | The minidump page count is now held in an integer to prevent the suppression of the minidump if the number of pages exceeds 65,535. | PK88691 | | 4 | Abend S0C4 in dfhs_trace when processing CICS internal trace. | Trace anchor and internal trace blocks contain invalid pointers (possibly as a result of storage violations). | Additional sanity checks performed on pointers. | PK88697 | | 5 | ABEND (CODE 0C4/AKEJ) occurs in IDIXCX53 due to backlevel XPI call with CICS/TS 4.1. | Existing XPI calls in Fault Analyzer exit code not compatible with CICS/TS 4.1. | XPI calls changed to comply with CICS/TS 4.1. | PK88701 | | 6 | Abend S0C4 in asm_rel_stg when assembler program has no in-scope DSECTs. | The DSECT info array pointer is not checked. | The DSECT info array pointer is now checked before processing. | PK88726 | | 7 | IDISF8154W issued when COBOL compiler listing has USAGE NATIONAL data items. | Nat-xxxx tokens not recognized in MAP section. | Nat-xxxx tokens now recognized in MAP section. | PK88714 | | 8 | IDILANGX gets abend U4000 when pre-allocating sequential output data set. | When the output file is opened, the default record length of 1024 is used because an explicit record length is not specified. | The output file is now opened with a record length of 1562 bytes. | PK88694 | | 9 | Abend S0C4 in Extract_COBOL_Map when processing COBOL compiler listing with IDILANGX. | Data items in MAP section with LineID of zero cause non-existent source record to be scanned for PIC declaration. | Data items in MAP section with LineID of zero are no longer scanned for PIC declarations. | PK88729 | | 10 | No source support when using Enterprise PL/I V3R8M0 compiler listing. | Enterprise PL/I V3R8M0 compiler listing not recognized. | Enterprise PL/I V3R8M0 compiler listing now recognized. | PK88704 | | 11 | CEE3204S Code=0C4 in DSNALLOC compile unit offset +064A when using IDILANGP utility against a SYSDEBUG side file. | The IDILANGP print utility might get abend S0C4 in DSNALLOC +064A when attempting to allocate a SYSDEBUG side file because of an input parameter list mismatch. | The DSNALLOC() input parameter list has been corrected. | PK88838 |
APAR PK79462 Fixes and Enhancements | | Problem | Description | Fix | Complete APAR information | | 1 | Debug Tool abend S0C4 when calling Fault Analyzer via CALL %FA when //IDIOFF DD DUMMY is set. | The IDISNAP Fault Analyzer interface is not restoring R11 when //IDIOFF DD is set. | Correct restore of registers is now done when //IDIOFF DD is set. | PK83226 | | 2 | Abend S0C4 in module IDICBIMS at offset X'122C'. | The address of an IMS control block was not valid, causing abend S0C4 when attempting to access the storage. Checks have been added for validation of the control block storage prior to accessing it. | 02. Checks have been added for validation of the control block storage prior to accessing it. | PK83281 | | 3 | IDI0092S time out and performance problem if Fault Analyzer run with LE HEAPCHK(ON). | If an environment is set up with HEAPCHK(ON) as the default, then there might be siginficant performance overhead with Fault Analyzer execution. Options in Fault Analyzer have been changed to suppress HEAPCHK(ON) for its execution. | Options in Fault Analyzer have been changed to suppress HEAPCHK(ON) for its execution. | PK83290 | | 4 | IDILANGX return code 1551 for large listing. | A listing with a very large number of symbols might not be able to be processed by IDILANGX and get a return code of The array growth algorithm has been changed. | The array growth algorithm has been changed. | PK83284 |
APAR PK74736 Fixes and Enhancements | | Problem | Description | Fix | Complete APAR information | | 1 | CICS Storage Violation SM0102 with Program IDIXCX53. | A trailing SAA is overlayed by Fault Analyzer IDIXCX53 when CICS trace data gathering fills at a buffer boundary. | The boundary code has been corrected to allow for the additional halfword end of records field. | PK74237 | | 2 | Fault Analyzer loops in function WhatsNext() when processing COBOL program abend. | WhatsNext() continually returns the same base locator when the highest address in the dictionary is a COBOL base locator. | WhatsNext() now checks for same base locator being returned. | PK79425 | | 3 | LE heap overlay when using Views with the Fault Analyzer ISPF interface. | An insufficient buffer was allocated for the list of history file names contained in the view. | The allocated buffer size has been corrected. | PK77342 | | 4 | Abend S0C4 in IDILANGX function ADD_PLIST when processing Enterprise PL/I compiler listing. | The block info structure does not have a symbol ID specified, resulting in bad pointer. | The block info structure is now not processed if the symbol ID is not set. | PK79426 | | 5 | Message IDI0090E IRXEXEC rc=20 when attempting to run a REXX Notification user exit for IMS ImageFast duplicates in the IDIS subsystem. | The IDIEXEC DDname was not allocated. | The IDIEXEC DDname is now correctly being allocated prior to running the REXX user exit. | PK79428 | | 6 | Incorrect source line is located from stmt# point-and-shoot field when Enterprise PL/I program is compiled with STMT and NONUMBER options. | The source info point-and-shoot field specifies both line# and stmt#, but only line# is used to align source records. When STMT and NONUMBER options are in effect, there could be multiple source lines with the same line#. | When both stmt# and line# are specified, both are checked when aligning source records. | PK79430 | | 7 | Abend S0C4 while processing VS COBOL II event. | If there is no CLLE for VS COBOL II program, essential information about the TGT (eg. length) is unavailable, causing an abend S0C4. | Processing is bypassed when a VS COBOL II TGT is not available via the CLLE. | PK79431 | | 8 | Abend S0C4 when reporting Enterprise PL/I EXTERNAL variables during re-analysis of fault created with DeferredReport in effect. | EXTERNAL variable's data not in minidump. | DeferredReport processing corrected for Enterprise PL/I EXTERNAL variables. | PK79432 | | 9 | Abend S0C1 or other random problems due to an overlay with data of x'40000000' after a Fault Analyzer IDIS subsystem hang. | If the IDIS Fault Analyzer subsystem is delayed or hung such that return x-memory POST processing gets abend S102 or other problems, it is possible, depending on requestor memory reuse, to get random storage overlays. CICS abend processing is susceptible to this with IDIS running. | Validation of the return x-memory POST conditions checked before return. | PK78769 | | 10 | DFHSR0606 Abend (23E/AKEB) detected after IDICALOC LOCFRESL DETACHing orphan TCB terminating CICS. | CICS DUMPCODE: SR0606 and termination after Fault Analyzer task management IDICALOC LOCFRESL DETACHing orphan TCB. The TCB address being detached is invalid. | Messages corrected to display the correct TCB=address and validation improved to prevent the condition | PK78987
| | 11 | Abend S0C4 in PliSepSym when processing Enterprise PL/I SYSDEBUG side file. | PL/I PUT STRING statement causes symbol name pool to reside in program CSECT (instead of SYSDEBUG file), some of this storage might not be available. | Entire program and static CSECT storage now located. | PK79424 | | 12 | Enterprise PL/I structure member has incorrect offset when variable with same name is used as a parameter. | When multiple instances of a variable name are declared in a block, an incorrect instance might be used. | The correct instance of the variable is now used. | PK79433 | | 13 | DFHAP0701 An abend (code 0C4/AKEA) has occurred in exit IDIXCX53 at exit point XPCABND. | The Fault Analyzer IDIXCX53 exit, when requesting CICS GETMAIN storage, did not correctly handle the not available condition and caused an abend S0C4 which can terminate CICS. | The GETMAIN return checking has been corrected. | PK79434 |
APAR PK72178 Fixes and Enhancements | | Problem | Description | Fix | Complete APAR information | | 1 | Message: Report line threshold of 50000 lines reached - doubling the interval - being incorrectly displayed. | This message was supposed to be a diagnostic message for internal use onlt not to displayed to the user. | This message has been correctly changed to a diagnostic message. | PK72178 | | 2 | Fault Analyzer loops when processing variably located data items in a COBOL program. | The variably located data (BLV) has a bad address (eg. 0xFFFFFFFC) which causes WhatsNext() to return the same name IANCHOR as that passed to it. | WhatsNext() now checks that the returned IANCHOR has any address higher than the IANCHOR passed to it. | PK73291 | | 3 | Message IDI0020W issued if the NoErrorHandler option is specified. | The NoErrorHandler option is not recognized as a valid option. | The NoErrorHandler option is now recognized as a valid option. | PK73061 | | 4 | Fault Analyzer abends when processing PL/I external variables. | Incorrect static csect length causes dLocate failure. | dLocate issued for adjusted section length. | PK73359 |
APAR PK69694 Fixes and Enhancements | | Problem | Description | Fix | Complete APAR information | | 1 | PrtSystemWideOpenFiles() abends with 0C4 when more than 20 CICS Open Files (FLABs) are encountered. | FLABs are collected into a fixed 20 element array. | Grow array implemented for FLABs. | PK71110
| | 2 | COBOL source line accessed from register display hotspot is a comment. | The first source line for a given offset is selected regardless of whether it is a comment. | When determining the COBOL source line for a register address (which translates to base locator + offset), any leading commentary source lines are ignored. | PK71136 | | 3 | ICH408I ALTER access incorrectly requested of the ICF catalog if an ALIAS name was incorrectly used as a history file name. | In the Fault Analyzer interactive display panel, if the name of a history file to view is incorrectly entered as simply the high level ALIAS qualifier, the logic then incorrectly requests ALTER access to the catalog containing the ALIAS. | The code is corrected to properly determine the invalid nature of the ALIAS name and give an appropriate message. | PK71521 |
APAR PK67045 Fixes and Enhancements | | Problem | Description | Fix | Complete APAR information | | 1 | Fault Analyzer abends with 0C7 after selecting terminal IDs for CICS Trace. | Fault Analyzer is expecting the TCTTE transaction number to be a valid packed decimal value when, if fact, it may not be (e.g. it could be 0x00000000). | Fault Analyzer now handles the TCTTE transaction number as byte data. | PK69536
| | 2 | Incorrect values in the ENV structure when a Notification user exit is invoked for CICS fast duplicates. | If the original fault entry, to which the fast duplicates refer, no longer existed, then the ENV structure was being populated from another cached fault entry, instead of being cleared. | If the original fault no longer exists, then the ENV structure is appropriately cleared. | PK69545 | | 3 | Abend S0C4 at entry point DSAchainTCB offset X'5592'. | An assumed register save area which was being processed, was spanning two 4K pages with different storage protection keys. | A check has been added to ensure that the entire register save area is accessible. | PK69558 | | 4 | Message IDI0101I, dump and analysis suppressed, even though running with NoCICSDumpTableExclude. | Exit program IDIXCCEE is losing addressability to a storage area which holds an indication of whether the CICSDumpTableExclude option is in effect. | Addressability to the storage area containing the CICSDumpTableExclude option is now maintained. | PK69587 | | 5 | Unable to scroll horizontally to see a message explanation which exceeds 80 columns.
| The keylist used for the IDIPLOOK panel did not include settings of PF10 and PF11 to the LEFT and RIGHT commands respectively. | The LEFT and RIGHT commands have been added to the IDIPIKY8 keylist. | PK65074
PK65078 |
APAR PK64345 Fixes and Enhancements |
APAR PK61883 Fixes and Enhancements | | Problem | Description | Fix | Complete APAR information | | 1 | IDILANGX issues messages IDISF8132S and IDISF8136S when processing Enterprise COBOL V4.1 compiler listing. | The Enterprise COBOL V4.1 compiler is not recognized by IDILANGX. | IDILANGX now recognizes the Enterprise COBOL V4.1 compiler. | PK63859
| | 2 | Task is missing on the CICS system dump analysis Task Summary display. | Summary lines are built for each task which has a Task Control Area (TCA), but the missing task is terminating and no longer has a TCA. | The CICS Kernel and transaction manager control blocks are now used to build and display summary lines for tasks without a TCA. | PK63793 | | 3 | COBOL SIGN IS LEADING/TRAILING SEPARATE CHARACTER clause causes incorrect reporting of data field values. | The instruction operands, when processing these data fields, do not necessarily point to the start of the data (for example, the PACK instruction operand for LEADING points passed the SIGN byte). | The data field addresses have been corrected. | PK63807 | | 4 | Copy to data set from the ISPF interface Services pull-down menu copies the visible display content only. | Implicit 'max down' missing to obtain lines beyond the visible screen depth. | Implicit 'max down' added. | PK62040 | | | | | | | 5 | Information about CICS-managed files not provided in 'Open Files' section of the analysis report. | CICS file control data areas are not referenced during the creation of the 'Open Files' report. | For CICS transaction abend analysis, CICS file control data areas are now referenced. | PK63871 | | 6 | Unable to specify compiler listing or side file data set name on prompt during interactive reanalysis if no TSO prefix set. | When using TSO PROFILE NOPREFIX, the data set name specified on the prompt during interactive reanalysis was being processed incorrectly, causing the prompt to reject the specified data set name. | The specified compiler listing or side file data set name is now processed correctly, even when TSO PROFILE NOPREFIX is used. | PK63370 | | 7 | Options on initial interactive reanalysis menu disappear after formatting event details. | A flag was being incorrectly set as part of the event formatting process, which caused the initial menu to be incorrectly re-displayed. | The flag is now correctly set and restored. | PK63787 | | 8 | Enterprise PL/I compiler listing created with RENT option in effect results in blank CSECT names in the IDILANGX X'0E' record. | The EXTERNAL SYMBOL DICTIONARY section of the compiler listing uses a single column, but the code expects two columns. | Code added to support 1 or 2 columns. | PK63868 |
APAR PK56117 Fixes and Enhancements | | Problem | Description | Fix | Complete APAR information | | 1 | Message IDI0032W I/O error writing report: EDC5003I truncation of a record occurred during an I/O operation. | Invalid DB2 GRAPHIC type host variable data was not being adequately validated before attempted written to the report. | Improved validation has been added. | PK56212
| | 2 | Abend S0C4 in mapCsectEntryPoint() when analyzing a CICS system dump. | Invalid key data was being added. | The invalid key data has been corrected. | PK61707 | | 3 | When formatting COBOL data division, a 'Storage range xxxxxxxx-xxxxxxx not accessible' message is issued. | The base locator dictionary item length is 'trimmed' by an assembler DSECT, which redefines COBOL storage. | DSECTs have been excluded from dictionary items that can 'trim' COBOL base locator storage lengths. | PK61709 | | 4 | Out-of-scope assembler DSECT storage is formatted. | The DSECT scoping is incorrect when a base register is reused. | The code has been changed to use the statement number from the respecify record, rather than a register symbol. | PK61710 | | | | | | | 5 | Message IDI0006E issued without a data set name. | The data set was eliminated from the associated DDname due to READ access checking wrongly assuming lack of access authorization, when in fact the data set did not exist. | If a data set does not exist, then it is left in the list of data sets for a DDname so that it is available if open error messages are issued. | PK61711 | | 6 | Incorrect length presented for second operand of an MVCL (Move Characters Long) instruction. | Bits 0-7 of the MVCL source length register represent a padding character. This was not being taken into account when presenting the length. | The length is now derived from bits 8-31 of the source length register. | PK61712 | | 7 | Fault Analyzer loops when reporting registers for a COBOL program with sidefile provided. | The data item pointed to by the register was not on the abending source line, and has a REDEFINES. | The source line checking for a variable is bypassed when the function is called from the register display. | PK58464 | | 8 | Message IDI0130E Response from IDIS subsystem not returned within 2 minutes, request canceled. | A loop in the IDIS subsystem caused the request to time out. | Improved loop detection has been added. | PK61719 | | 9 | Message IDI0047S abend S0C4 in LE run-time function strspn, called from PrtHostVars during formatting of DB2 VARCHAR host variable data. | An ending NULL character was not added to the end of the buffer. | The ending NULL character has been added. | PK58961 | | | | | | | 10 | History file specified by Analysis Control user exit in ENV.IDIHIST does not override IDIHIST DD statement specified in JCL. | The exit-specified history file name was incorrectly being overridden by the pre-allocated IDIHIST data set name. | The exit-specified history file name in ENV.IDIHIST now always overrides any other specification, including pre-allocation via JCL DD statement. | PK61725 | | 11 | Table element stride is incorrect when using COBOL SYSDEBUG sidefile. | Non-OCCURS DEPENDING ON (ODO) tables are being re-calibrated when a program contains one or more ODO tables. | The re-calibration logic has been corrected. | PK59466 | | 12 | Interactive fault entry reanalysis under CICS is failing with system abend code S23E. | After a terminal session error while performing interactive fault entry reanalysis under CICS, Fault Analyzer attempted to DETACH the subtask twice, which caused a S23E system abend. | Fault Analyzer has been changed to ensure that the DETACH is issued only once. | PK61730 | | 13 | Corrupted Japanese text in the formatted storage display, or failure to successfully copy the display to a data set with the COPY command. | The display contains invalid DBCS characters due to missing shift-in characters. | The missing shift-in characters have been added. | PK60650 | | 14 | Abend S0C4 in makeString() during CICS system dump analysis when processing 3-character transaction number (for example, TCP) from KE Error Table Summary. | A wrong value was passed to makeString(). | The transaction-number processing has been corrected. | PK61698 | | 15 | Abend S0C4 in IDICBIMS offset X'336'. | An invalid offset into an IMS control block was being used during NoDup(ImageFast(...)) processing. | The IMS offset has been corrected. | PK61731 |
APAR PK50513 Fixes and Enhancements | | Problem | Description | Fix | Complete APAR information | | 1 | Initial paragraph on panel IDIPILPT is truncated. | An inappropriate DTL tag, which does not allow formatting of more than one line, was being used. | A different tag has been used to permit text which exceeds one line to be formatted correctly. | PK50673 |
APAR PK52717 Fixes and Enhancements | | Problem | Description | Fix | Complete APAR information | | 1 | Side file for abending COBOL event is not being used, resulting in missing analysis report source line information. | Previous event's R15 is not pointing at the following COBOL event's entry point. | Alternative method for determining COBOL entry point address implemented. | PK55041 | | 2 | An S0C4 abend occurs in function pp_ueh_main due to an invalid reference to an array of global user exit names. | New exits in CICS TS 3.1 and TS 3.2 are not defined in the array of user exit names. | The names of global user exits which are new in CICS TS 3.1 and TS 3.2 are now defined to Fault Analyzer. | PK55176 | | 3 | Message IEC036I 002-18 followed by message IDI0124E might be issued from the IDIS subsystem. | In situations where a high number of duplicate abends occur for the same fault entry, a record length error can result in message IEC036I 002-18 being issued in the IDIS subsystem. | The record length problem on writing to the history file $$INDEX member has been corrected. | PK55109 | | 4 | Abend S0C4 in IDIDA DFHTT640 when formatting a socket domain CICS trace entry. | An abend S0C4 might occur on a MVCL instruction in DFHTT640 when formatting a CICS socket domain trace entry. | Code in the the call interface to DFHTT64 has been changed to circumvent the wrong length move problem. | PK55415 | | | | | | | 5 | Poor analysis performance when a job causes many WTO messages that do not start with a formal message ID to be issued. | An attempt was being made to find an explanation for the presumed message ID at the start of each WTO message. | Improved verification of the presumed message ID has been implemented to avoid the overhead of searching for a message explanation when none exists. | PK55309 | | 6 | Message IDI0092S time-out after 32 minutes. | When writing a large report, the time expected for completion was being incremented repeatedly until the maximum of 32 minutes was reached. | The expected time for completion of a large report is now incremented only once. | PK55310 | | 7 | SYSUDUMP not suppressed when a Fault Analyzer warning message (W level) is issued. | The return code set when any Fault Analyzer messages, other than informational messages (I level), were issued, caused the MVS dump (SYSUDUMP, SYSMDUMP, or SYSABEND) to not be suppressed with the RetainDump(AUTO) option in effect. | A change has been made to ensure that only severe error messages (S level) will cause the MVS dump to not be suppressed. | PK55312 | | 8 | Fault Analyzer event list 'loaded from' might be 'n/a' if the data set has EXECUTE ONLY security access. | When the load data set security is 'EXECUTE ONLY', then the Fault Analyzer event list 'loaded from' column might show 'n/a' instead of the load data set name. | The logic path encountering the 'EXECUTE ONLY' access has been corrected to retain the load data set name. | PK55308 | | 9 | Fault Analyzer ISPF display might not show all fault entries recently created. | If Fault Analyzer is running without the IDIS subsystem and PARM='UPDINDEX', then fault entries recently created might not be displayed in the ISPF view until another action, such as deletion of a fault entry, occurs. | The timing condition with parallel creation of multiple fault entries, and the history display without UPDINDEX, has been corrected. | PK56351 | | 10 | If a Fault Analyzer V8.1 AUTO-managed history file is shared with Fault Analyzer V6.1, and a fault is written to this history file using V6.1, then all fault entries that are not locked will be deleted. | The new Fault Analyzer V8.1 SetMaxFaultEntries(AUTO) history file setting is incompatible with Fault Analyzer V6.1. | Fault Analyzer V6.1 has been made compatible with the new Fault Analyzer V8.1 SetMaxFaultEntries(AUTO) history file setting. | PK55993 |
APAR PK49796 Fixes and Enhancements |
APAR PK46021 Fixes and Enhancements | | Problem | Description | Fix | Complete APAR information | | 1 | Message IDI0092S time-out. | An unintended loop occurred at entry point LastRDW. | The condition that caused the loop has been accounted for to prevent the loop from happening. | PK46636
| | 2 | IDI0047S IBM Fault Analyzer internal abend S0C4. | Fault Analyzer is attempting to reference fetch protected storage. | An additional check has been added for fetch protected storage in Fault Analyzer's storage access fast path function. | PK46380 | | 3 | Abend S0C4 at entry point IDICTDB2 offset X'A4'. | An invalid TCB address was passed to the routine. | A check has been added to prevent the invalid TCB address from being used. | PK46909 | | 4 | Never ending loop processing a damaged Language Environment stack segment chain. | Control blocks have been damaged in such a way that a next segment pointer points to itself. | The next segment pointer is now compared with the address of the segment just processed. If equal, then a message is issued and processing of the segment chain is abandoned. | PK49466 | | | | | | | 5 | Message IDI0105S due to Fault Analyzer internal abend. | Damage to LE control blocks, the CIB and MCH, resulted in Fault Analyzer attempting to allocate a zero amount of storage. | Unless at least one CIB and its associated MCH can be located, further CIB processing is abandoned, and this avoids a zero storage allocation attempt. | PK47388 | | 6 | Abend SE37-04 in IDILANGX when a very large compiler listing is processed. | When Fault Analyzer calls the IDILANGX program to process a very large (around 500,000 lines) compiler listing, the temporary data set might get abend SE37-04. | A larger temporary data set is now being allocated. | PK49470 | | 7 | Abend S0C4 in Language Environment initialization of the IDICCFND program. | IDIPLT or IDIPLTD issue an MVS ATTACH for the IDICCFND program with a parameter list assembled into the calling program. In a busy system, the calling program might be deleted before LE initialization for IDICCFND has been started or completed, resulting in GPR1 becoming invalid. | A parameter list is no longer passed. Instead, register 1 is set to zero before the ATTACH is issued. | PK49471 | | 8 | IDI0047S IBM Fault Analyzer internal abend S0C4. | LE heap storage was overlaid due to insufficient buffer size. | The size of the allocated buffer has been corrected to prevent the problem. | PK49477 | | 9 | Message IEW4000I and CSV031I for load failure of CEEEV003 after an application abend causes Fault Analyzer to be invoked. | The load check of CEEEV003 had not detected the module was in STEPLIB and had assumed load space would not be required because a copy was available in LPA. | The logic is changed to include the load space requirement in the case of modules also in STEPLIB and currently available in LPA. | PK49474 | | | | | | | 10 | Fault Analyzer abends in FmtCobData, or base locator offsets in the Associated Storage Areas are incorrect. | Wrong base locator numbering system used with COBOL for OS/390 & VM 2.1 (Note that COBOL for OS/390 and VM 2.1 is unaffected--that is, with 'and' not '&'). | Hexadecimal base locator numbering implemented with COBOL for OS/390 & VM 2.1. | PK48358 | | 11 | Abend S0C4 in GetPLIStmt when analyzing OS PL/I 2.3 event. | The Statement Number Table header contains an invalid pointer. | All pointers in the Statement Number Table are checked for addresses within the static CSECT. | PK49396 | | 12 | Incorrect storage values shown for PL/I when storage class changes within AUTO/STATIC section (eg. STATIC->BASED->STATIC). | The storage pointer is not set correctly. | The storage pointer has been corrected. | PK49391 | | 13 | IDIPLT and IDIPLTD are RMODE 24. | Code structure was causing RMODE 24. | Code has been restructured to allow RMODE ANY. | PK49479 | | 14 | Message IDI0120S IBM Fault Analyzer internal abend S002 U0000 following message IEC036I 002-18 for the history file data set. | The CICS trace entries gathered for the abending task were too long for an internal segment. This caused the write error when the segment was written to the history file data set. | The code was altered to stop the segment length from being exceeded. | PK49482 | | 15 | Side file not used when COBOL program terminated via VAGEN CICS abend handler (ELAESABD). | Incorrect entry point address used. | Entry point address corrected. | PK49484 |
APAR PK42494 Fixes and Enhancements | | Problem | Description | Fix | Complete APAR information | | 1 | When specifying a large value (eg. 32000) with the LC compiler option, Enterprise PL/I compiler listing causes IDILANGX to fail with rc=1551. | Storage allocation based on LC value fails. | Storage allocation removed. This was only relevant to non-Enterprise PL/I listings. | PK45823 | | 2 | Parameters passed from COBOL to PL/I are not shown when data are aggregates (structures, arrays, strings). | Parameters were not recognized as having been passed from COBOL. | Implemented support for parameters passed from COBOL. | PK45834 | | 3 | Abend S0C4 in entry point splitString or loop involving entry points splitString and PrtRecord. | With Language(JPN) in effect, a situation where a 'shift in' character (X'0F') was inserted at the rightmost character position in the report, due to a long sentence being wrapped over multiple lines, was not handled correctly. | The wrapping of long DBCS strings is now handled correctly. | PK41616 | | 4 | PL/I compiler option LC (LineCount) causes IDILANGX to fail with RC=1551 when large values (eg. 32000) are used. | Memory allocation failure due to insufficient storage. | IDILANGX now uses a logical page not exceeding 100 lines. | PK43646 | | | | | | | 5 | Abend S0C4 at entry point ReadAtts. | A 32-character symbol name exceeded the size of a program variable. | The size of the variable has been increased to 256 characters. | PK45855 | | 6 | An event is not created for the user's abend. | The DSA belonging to CEEHDSP chains back to the Dummy DSA and causes Fault Analyzer to miss the DSAs belonging to the application. Several events are 'missed', including the CIB. | When Fault Analyzer processes the Dummy DSA, and there is still a CIB to be processed, an event is created for the CIB and register 13 in the CIB is used to backchain through the application's DSAs. | PK44519 | | 7 | CICS Trace options are not available when re-analysis is performed with DEFERREDREPORT option in effect. | DEFERREDREPORT conditioning is only relevant to real time. | Check Fault Analyzer is running real time when determining whether DEFERREDREPORT option is applicable. | PK44039 | | 8 | CFA transaction incorrectly reporting exit status as uninstalled. | A NOTAUTH condition from the INQUIRE EXITPROGRAM command was not being correctly reported to the user. | The NOTAUTH is now reported to the user. | PK45912 | | | | | | | 9 | Abend S0C4 in GetPLIStmt() occurs when NOGOSTMT compiler option and Fault Analyzer DeferredReport option is in effect. | Statement Number Table 'stub' not recognized, causing an invalid address to be used. | GetPLIStmt() quits when 'stub' statement number table is recognized to prevent the use of an invalid address. | PK43839 | | 10 | Abend S0C4 in IDILANGX when processing a C/C++ compiler listing. | An incorrect reference to an array that is not initialized for C/C++ was being made. | Code corrected to not refer to an array that is not initialized for C/C++. | PK44221 |
| Problem | Description | Fix | Complete APAR information | | 1 | RACF message ICH409I 282-020 when editing or deleting user notes during MVS dump analysis. | Since a history file name is not applicable until a fault entry has been created, the access authority checking was using a null data set name resource. | The access authority checking will not be performed on user note changes or deletions during MVS dump analysis. This is the same principle as is already used for creation of user notes in this mode of execution. | PK41266 | | 2 | IDI0047S abend S0C4 at entry point generateDBRMKeyData + X'21A0'. | Unexpected data obtained from the DB2 catalog resulted in an attempt to access storage outside the current buffer. | Further validation of the DB2 data has been added to ensure that data is not accessed outside the current buffer. | PK39356 | | 3 | Abend S0C4 following an unsuccessful attempt to open a data set for read. | An OPEN failure is not being detected and Fault Analyzer proceeds to issue a BLDL macro, which leads to a program check. | Several routines have been changed to correctly detect a bad return code from OPEN processing. | PK41081 | | | | | | | 4 | DFHDPTA eyecatcher is being reported as invalid for certain CICS system dump analyses. | The eyecatcher is altered by CICS in certain circumstances, hence the eyecatcher validation can potentially fail. | The code has been changed to handle this by ignoring the first character of the DFHDPTA eyecatcher. | PK41269 | | 5 | Never-ending loop during CICS system dump analysis. | A TCB contained an invalid PRDTCB field. | The TCB eyecatcher is now checked before attempting to follow the RB chain off the TCB. | PK39820 | | 6 | IDI0124E IDIS subsystem subtask IDISREG IDISREG has terminated with abend code FC6. Also messages IDI0078E, IDI0095W (no member set), and IDI0047S. | The DataSets option specification of IDIHIST was not being picked up, resulting in no history file available for the dump registration fault entry to be recorded into. | The DataSets option specification of IDIHIST is now being processed correctly. | PK39786 | | 7 | Duplicate CICS trace lines written in display COPY operation. | The function which produces the CICS trace display was also used for the COPY operation. | A new routine has been added for the COPY command, which executes independently of the trace display function. | PK41179 | | 8 | Application abend event missing. | Language Environment has caused a program check during processing of an abend. Its stack is damaged, and Fault Analzyer is unable to bakcchain the application's DSA. | An event is now created from the CIB, if one exists. Backchaining will then be performed using the register found via the CIB. | PK41181 | | | | | | | 9 | Fault Analyzer IDI messages written to SYSPRINT and QUIET option specification ignored. | A diagnostic flag was misinterpreted as being on, when in fact it was off. | The problem that caused the misinterpretation of the diagnostic flag has been corrected. | PK40558 | | 10 | CICS system analysis appears to be looping. | A coded loop contained an unnecessarily repeated call to a CPU intensive subroutine. | The subroutine call has been moved out of the loop and is now only executed once. | PK41207 | | 11 | IDILANGX abend S0C4 when using a PL/I compiler listing containing multiple compile units. | Options processing was not being reprocessed for each compile unit. | Code changed to ensure that options processing is reprocessed if more than one compile unit is contained in a listing. | PK41278 | | 12 | Batch reanalysis JCL error. | An invalid single quote was inserted after the //IDIOPTS data set name, and before the open parenthesis for the member name, when both a data set name and a member name was specified as options file for batch reanalysis. | The incorrect quote has been removed. | PK41282 | | 13 | Message IDI0058W issued when providing Enterprise PL/I compiler listing through a compiler Listing Read user exit. | The primary entry point is not located following timestamp and options string. | The entry point recognition code has been extended to handle the situation where the entry point is located further into the CSECT. | PK41393 |
APAR PK35096 Fixes and Enhancements | | Problem | Description | Fix | Complete APAR information | | 1 | IDITRACE ON/OFF not working in CFA transaction. | The introduction of a statistics flushing TCB had the potential of stopping the PF11 IDITRACE ON/OFF function from working in the CFA transaction. | The code has been corrected to allow for the additional TCB. | PK38336
| | 2 | Loop during CICS system dump analysis at entry point dfhs_appopl. | Pointers to user TCAs are corrupted in XM (Transaction Manager) task control blocks. Neither the user, nor the system TCA, can be located. The loop occurs in a routine which is attempting to follow the TACB chain. | The pointer in the user TCA to the system TCA is checked. If invalid, no attempt is made to analyze the system TCA or the TACB chain. A new severity 2 notice is added to the report in this situation. | PK34427 | | 3 | Incorrect load library shown in Event Summary section of report for module loaded from CICS DFHRPL concatenation. 6. | Due to READ access checking of all data sets, including the CICS DFHRPL concatenation, data sets to which the user does not have access are removed from the concatenation. This resulted in a mismatch between the expected relative concatenation number and the truncated list of data sets. | The up-front READ access checking of DFHRPL data sets has been removed. The READ access checking will still be performed later if calling the Binder, but this will not affect the reporting of the correct data set name. | PK38338 | | | | | | | 4 | Failure to locate compiler listing results in missing source information for Enterprise PL/I | The side file member name is derived from the first procedure found in the CSECT (assumed to be the primary entry point, whose label is the program name). EPLI 3.6 reverses the sequence of procedures in the object code so the first procedure's code is at the end of the CSECT. | New function added to locate the entry point based on the CSECT name (which is derived from the entry point name). | PK38348 | | 5 | PL/I source file 0 appears as n/a when viewing a compiler listing interactively. | The Enterprise PL/I source file 0 support was incomplete. | Source file 0 is now supported for Enterprise PL/I. | PK38355 | | 6 | IDI0005S IDIDODSN:2211 Storage allocation for 32768 (X'8000') bytes failed - processing terminated | Storage allocations accumulated when processing large working-storage sections, base locator by base locator, cause excessive storage to be used. | Working and local storage sections now use a single large allocation. | PK35294 | | 7 | COBOL function pointers are not presented as hexadecimal data. | IDILANGX did not recognize the COBOL Function-Ptr data type in the map section of the compiler listing. | COBOL Function-Ptr data types are now recognized and presented as hexadecimal data. | PK38335
| | | | | | | 8 | Loop in CICS kernel stack entries processing. | Fault Analyzer is attempting to place stack entries in their correct chronological order, but control block damage in CICS is causing a never-ending loop. | Code has been added to Fault Analyzer to abandon stack entry processing after a certain number of attempts. | PK38356 | | 9 | Abend S0C4 in Fault Analyzer when COBOL/2 abends during start-up processing. | A bad parameter reference was passed. | The parameter reference has been corrected. | PK38342 | | 10 | Abend S0B0-X'3C' in IEFQB551, abend S05C-X'214' in IEFW21SD, or abend S0C4-X'4' in IDIXDCAP entry point DCAPSUB offset X'139C'. | Analysis is attempted for an abend in a non full-function allocation address space, or an address space started with SUB=MSTR. Under these conditions, dynamic allocation is either not supported, or is likely to fail. | Checks have been added to ensure that analysis is not attempted if an address space is started with SUB=MSTR, or is not in full-function allocation mode. | PK36494 | | 11 | When invoking Fault Analyzer using IDISNAP under CICS, the user exit ENV.INVOCATION_EXIT variable is set to 'C' instead of 'S'. | When initializing the ENV.INVOCATION_EXIT field, no checking for IDISNAP was done when called under CICS. | The ENV.INVOCATION_EXIT field is now correctly set to 'S' when Fault Analyzer is invoked by IDISNAP, regardless of the execution environment. | PK36563 | | | | | | | 12 | Loop and IDI0092S message when CEEWUCHA exit is active and EXEC CICS HANDLE ABEND is used. | Special processing of an incomplete CIBH is not checking if the pointer to the CIB is zero. | Special processing of the CIBH now checks for a zero CIB pointer, and when zero, exits CIBH processing. | PK38358
| | 13 | Fault entry CPU time reported from IDIUTIL ENV.CPU_HSECONDS is zero. | The CPU_HSECONDS value, that can be accessed from IDIUTIL, was not being correctly recorded. | The code has been corrected to record the CPU time used. | PK38370 | | 14 | Possible abend S23E/AKEB in IDIXCX53 when Fault Analyzer is attached during CICS shutdown. | An attempt to DETACH a statistics recording TCB during CICS shutdown was being made. | A check is now made prior to the attempted DETACH to see if CICS is shutting down. | PK38343 | | 15 | Message IDI0092S time-out might occur during Fault Analyzer processing. | The IDI0092 time-out process attempts to terminate Fault Analyzer execution to prevent loops and wait conditions. At times, the determination of a loop or wait is not correct. | This change adds an additional mechanism to try and ensure that the time-out processing does not trigger prematurely. | PK38345 | | | | | | | 16 | IDIWRITE: Buffer space exhausted - record not written message when using REXX variable in IDIWRITE call. | The potential existed for a buffer length to be incorrectly determined and hence lead to the buffer space exhausted message. | The length check is now correctly determined. | PK38661 |
APAR PK29971 Fixes and Enhancements | | Problem | Description | Fix | Complete APAR information | | 1 | Failure to locate COBOL TEST(,,SEPARATE) SYSDEBUG side file. | The attempt to locate the side file occurred prior to having determined the necessary details about the program being analyzed. | The order of processing has been corrected so that the side file is not attempted to be located prematurely. | PK29616 | | 2 | Abend S0C4 in WriteMinidump if the history file gets abend SE37. | Variables were reset on detection of a write error, but later used to reference data that did not exist. | The variables are no longer reset. | PK30120 | | 3 | COBOL data items declared on base locator boundary result in offsets shifted by 1 byte. | Offset fix-up for IDILANGX symbol records incorrect. | Offset fix-up for IDILANGX symbol records now occurs for all data items, other than items at base locator zero, offset zero. | PK30286 | | 4 | Abend S0C7 followed by abend S0C4 during analysis of CICS system dump. | An attempt was made to unpack an invalid packed decimal number. | The code now validates the packed number before using it. | PK31283 | | | | | | | 5 | QUIET option with no sub-options is not suppressing IDI0066I messages. | The check for suppression of IDI0066I messages was not considering the QUIET option having been specified without any suboptions. | The QUIET option without suboptions is now interpreted correctly, and will cause suppression of the IDI0066I message. | PK30262 | | 6 | Abend S0C4 during findstack processing. | An uninitialized pointer was leading to an abend S0C4. | The pointer is now being correctly initialized. | PK31210 | | 7 | IDILANGX loop near label FIND_ID when processing PL/I compiler listing. | When multiple instances of a variable name are assigned to structure members, and one of these is used in a BASED(ADDR) expression, checking of ancestors causes a loop if an ancestor does not have an owner. | Ensured that ancestors without an owner will break the loop. | PK34846 | | 8 | Abend S0C4 in Fault Analyzer leading to message IDI0047S. | Low fetch-protected storage accessed while traversing the application DSA chain. | The storage access is now not attempted unless the address is higher than 4095 (X'FFF'). | PK31272 | | | | | | | 9 | IDI0036E abend S0C4 during processing of Message and Abend Code Explanation user exit. The abend is in entry point duxprintf. | The problem only occurs when the user exit used is a load module, not when it is REXX. The reason for the abend is a call to a routine that is only available in the REXX user exit environment. | The call to the invalid routine has been replaced by one that is supported in the load module user exit environment. | PK30931 | | 10 | Abend S806-04 module CEEBINSS not found when using LE RTLS. | With the CEE.SCEERTLS LE library in LPA or LNKLST for LE RTLS support, module CEEBINIT was found here instead of in CEE.SCEERUN. This caused an incorrect assumption to be made about the presence of the LE runtime. | A change was made to check for module CEEBINSS instead of CEEBINIT. | PK30645 | | 11 | COBOL Level 88 point-and-shoot fields do not appear in formatted storage when using a SYSDEBUG sidefile. | Support for COBOL Level 88 items via SYSDEBUG file not implemented. | COBOL SYSDEBUG file now includes support for Level 88 items. | PK31214 | | 12 | Some KE_NUM values are not selectable as point-and-shoot fields from the CICS Kernel Task Summary display. | The KE_NUM field was not provided as a point-and-shoot field for system tasks running without a TCA. | The KE_NUM values for all active tasks is now provided as point-and-shoot fields. | PK31213 | | | | | | | 13 | PL/I external variables are not reported, or reported at incorrect addresses. | Duplicate variable names cause wrong symbol to be updated. | Symbols not updated unless scope is known. | PK34848 | | 14 | Abend S0C4 in IRXINIT offset X'A36' during REXX initialization. | It is a REXX restriction that the job step TCB (TCBPKF) must be key 8. A check was made for a non-zero key, other than 8, when it should have included key 0 also. | The check for an environment in which REXX is supported has been changed to include key 0 as an unsupported environment. | PK33446 | | 15 | An S0C4 program check is occurring in entry point findStack. | A PPA1 block is being incorrectly analyzed in a JVM function which leads to incorrect entry name length being determined and an attempt to write to protected storage. | The PPA1 is now correctly analyzed. | PK31959 | | 16 | Return code 3128 from IDILANGX when used under SCLM. | An additional open of the listing data set, used for DCB information extraction, was causing subsequent errors under SCLM. | The information extracted by the additional data set open is now determined via DYNALLOC, which stops the rc=3128 under SCLM. | PK31918 | | | | | | | 17 | IDIXDCAP entry point DCAPSUB offset X'4D6' abend S0C4. | The current method of changing the PSW key to 8 did not work correctly when the abending TCB was not key 8. | Changed the method used for setting the PSW key to one that is not affected by the abending TCB key. | PK31563 | | 18 | Missing event in analysis of S0C1 program check. | Fault Analyzer failed to determine the entry point of the abending program, and thus did not create an associated event. | Code has been added to identify the entry point and create an event for the abending program. | PK32476 | | 19 | ImageFast(IMS) does not select INCLUDE(IMSTYPE(IFP)) for Fast Path regions. | The RCTYPE flag checking for Fast Path regions did not include RCBMP. | The RCTYPE flag checking has been corrected. | PK34404 | | 20 | Incorrect properties display for empty history files. | Uninitialized storage being used when displaying information for an empty history file. | Code changed to correctly handle empty history files. | PK32474 | | | | | | | 21 | BMC MV S0C4 due to TCBCAUF invalid. | Field TCBCAUF was not being cleared if abend analysis was being skipped due to EXCLUDE option processing. | TCBCAUF is now correctly cleared. | PK34849 | | 22 | Abend S378-X'14' or S0C1 abends during or following calls to a Compiler Listing Read user exit. | A work area pointer used by an earlier Message and Abend Code Explanation user exit call had not been cleared. | The work area pointer has been cleared. | PK32982 | | 23 | Abend S0C4 in IDnotify + X'33C'. | The abend is caused by a storage overlay, resulting from the use of an entry point name that is longer than 198 characters. | The code has been amended to handle entry point names of any length. | PK33211 | | 24 | Hang ENQ lockout on IDIDA SYSOUT after load failure on IDIDA. | Load failure S106 abend during ATTACH of IDIDA causes ENQ lockout on major IDIDA minor SYSOUT. In this case it was a DB2 stored procedure region running out of storage that caused the load failure. | The code that detects recursion was enhanced to also recognize an ATTACH load failure of IDIDA. | PK34446 | | | | | | | 25 | Incorrect events created. | An invalid DSA backchain pointer is not being detected. | Additional DSA checks are now performed, which prevent the incorrect events from being created. Also, a note about this is now displayed in the event details section of the report. | PK33148 | | 26 | Message IDI0070E incorrectly displayed using CFA transaction in a CICS 4.1 region. | The CFA transaction is trying to determine the CICS release using a table and lookup mechanism, which is failing to find a table entry for CICS 4.1. | The table and lookup mechanism has been corrected. | PK33535 | | 27 | Abend S0C4 or LE abend U4094 during analysis of DB2 fault. | An LE heap storage overlay was caused by invalid offsets used to insert DB2 host variable names into the DBRM SQL statement. | The host variable name offsets are validated before being used. | PK34449 |
APAR PK27344 Fixes and Enhancements | | Problem | Description | Fix | Complete APAR information | | 1 | If a View containing a -Match criteria is selected using the VIEWS command or the File->List Views pull-down, then the -Match criteria might not be actioned. | The problem can occur if a view is already displayed and another view is selected by other means than overtyping the current view name in the Fault Entry List display. A flag that controls the actioning of a -Match criteria had not been reset. | The flag that controls the -Match actioning is now being reset correctly, regardless of the method used to select a view. | PK27571 | | 2 | Incorrect event summary and point of failure for CICS/VAGen program. | The DSA chaining function for CICS transactions has no awareness of VAGen runtime modules and the way that they interact with the application. | Additional support added to the CICS DSA chaining function to recognize CICS/VAgen runtime modules and take appropriate action. | PK27872 | | 3 | CICS trace may appear to loop during find previous command. | The existing code was unable to handle the special requirements for the CICS trace table display. | Function call and condition variables corrected. | PK27847 | | 4 | CICS system dump analysis terminated with message IDI0105S IDIECAP:146 Storage allocation for 0 (X'0') bytes failed - processing terminated. | A dump has been taken during CICS initialization before the Transaction Manager has created any tasks. Fault Analyzer was assuming that at least one task exists. | A check is now made for zero tasks, and the storage allocation is not attempted. | PK27834 | | | | | | | 5 | COBOL elementary item names missing when formatting a GROUP OCCURS that is unnamed. | Positioning elementary table item names for each occurrence is based on having located the GROUP OCCURS name. | Elementary table items are positioned after the group level number (where the name would normally appear). | PK27915 | | 6 | S0C4 abend in function FATABOKS. | Failure to LOAD the SVC back-end program IDISVC01 is not handled correctly, which leads to the program check. | The parameter list passed to the SVC routine is now checked for an indication of an unsuccessful load. If this occurs, then a message is issued and the program check is avoided. | PK28035 | | 7 | Message IDI0005S. | An incorrect length obtained from storage with invalid content was used on a request for storage. | A check has been added to validate the storage area being used. | PK28105 | | 8 | Loop in CICS SDUMP processing. | The reference to a CICS control block was not being checked correctly, and due to an invalid address, was being referenced continually. | The reference to the control block is now correctly checked. | PK28085 | | | | | | | 9 | SA03 abends during CICS shutdown. | Under certain circumstances a FA TCB was not being detached correctly, which led to a SA03 abend during CICS shutdown. | The FA TCB is now detached correctly. | PK29098 | | 10 | CICS is issuing an AEXZ abend when Fault Analyzer is processing an AD2R abend. | The CICS/DB2 TRUE issues abend AD2R and then marks the L8 TCB unclean. IDIXCX53 subsequently receives control and issues an EXEC CICS request. DFHEIP issues a change mode request, which fails and leads to abend AEXZ. | IDIXCX53 checks whether the task is associated with an open TCB. When it is, then the mode is changed to 'float' around the execution of the EXEC CICS request. This persuades CICS not to attempt a TCB mode change. | PK28405 | | 11 | Enterprise PL/I 3.5 shows Source File # 0 as "n/a". | Enterprise PL/I 3.5 assigns 0 to the main source file (this was 1 in previous releases). Fault Analyzer will show "n/a" if source file # is 0. | Fault Analyzer now shows 0 for source file # 0. | PK29173
| | 12 | Fault entry indicates minidump available when no minidump was ever written. | If a fault is determined to be a duplicate of another fault, but an End Processing user exit overrides the default fault entry suppression, then a fault might be written with indication of a minidump being available, when in fact the minidump was suppressed. | The suppressed minidump is now reflected correctly in the fault entry written. | PK28705 | | | | | | | 13 | Duplicate IDI0101I message for an analysis being excluded due to the DumpTableExclude option. | The analysis was being excluded from both the LE and XPCABND exits. | A flag is now correctly set to prevent the duplicate message. | PK28670 | | 14 | When using the Fault Analyzer LIST command in a Formatting user exit during real-time analysis, all storage referenced might not be included in the minidump. | An incorrect check was being made to determine if the storage was valid. | If the storage listed is valid, then it is now being made available to the Formatting user exit, and also included in the minidump for the fault entry. | PK29177 | | 15 | S0C4 in IDILANGX when Enterprise COBOL is using DB2 co-processor. | Unexpected level 2 item (possibly SQL---VERS-DATA) appears as first item in map section of compiler listing. | Support has been added for a level 2 item as the first item in the map section. | PK29059 | | | | | | | 16 | Heap storage overlay when large number of user exits are specified via the Exits option from more than one options source. | If the total number of user exit names for a given exit type (for example, CONTROL) is specified in the Exits option from more than one source (for example, in the IDICNF00 parmlib member and the IDIOPTS user options file), then a storage overlay can occur due to an incorrectly calculated length. | The length causing the overlay has been corrected. | PK29178 | | 17 | AE PK27344 FIX COMPLETION | | | PK29668 |
APAR PK21990 Fixes and Enhancements | | Problem | Description | Fix | Complete APAR information | | 1 | ENQ lockout on Fault Analyzer history file if IDI0106E timeout. | IDI0106E timeout messages in the IDIS subsystem may be accompanied by ENQ lockout between multiple MVS images sharing a common history file. | Recovery processing improved to ensure error processes terminate correctly. | PK26577
| | 2 | Abend S0C4 when analyzing DB2 PL/I abend. | Incorrect source line offset causes buffer overlay when collecting EXEC SQL source. | Source line offset corrected. | PK22656 | | | | | | | 3 | COBOL SYSDEBUG file is rejected when program is re-compiled without change. | Compile date/time is checked with load module and a mismatch results in an unusable SYSDEBUG file. | Compile date/time check now replaced with signature check. Re-compiling without change will not affect this check. If signature check does fail, user can continue to use the SYSDEBUG file via the listing/mismatch pop-up. | PK26579 | | 4 | INCLUDE/EXCLUDE processing not working correctly for dump/abend codes which contain unprintable characters. | Unprintable characters, specifically a leading null was effectively causing the CICSABEND include/exclude option to be skipped. | All unprintable characters are now converted to periods. | PK22866 | | 5 | Abend S0C4 when processing PL/I sidefile | Token length char(12) is not enough to handle variables with names exceeding 12 characters. | Tokenizer token length increased to char(32) -- 31 being the maximum length for a PL/I variable name. | PK26602
| | | | | | | 6 | Language environment option values are not correctly given for options defined in PARMLIB member CEEPRMxx. | Fault Analyzer had not been enhanced to support new function in z/OS 1.7. | The Fault Analyzer LE run-time options report now displays run-time options values set in CEEPRMxx. | PK22772 | | 7 | IDI0038W I/O error writing to softcopy book cache: EDC5065I A write system error was detected. __armc Data = rc fdbk lastop | An overlay of the IDICACHE KSDS key data occurred after checking for the existence of a cache record, but prior to writing a new record. On the next attempt to check and write to the cache for the same record, a duplicate overlaid record already exists. | A variable of insufficient length was used to hold the IDIBOOKS data set name. The length has been adjusted to prevent the overlay. | PK23642 | | 8 | Poor performance, loops, abends, or incorrect/incomplete report when data sets containing records with lengths greater than 256 bytes are provided via a user exit. | Erroneous record truncation to 256 bytes occurred when a Compiler Listing user exit was used to provide the name of a compiler listing or side file data set to be used for source level reporting. | The problem causing truncation has been fixed. | PK26496 | | 9 | PL/I compile time missing from the Fault Analyzer report. | PL/I installation option TSTAMP=NO is in effect. | PL/I TSTAMP (compile date and time) is now retrieved from the end of the static CSECT provided TSTAMP=YES is in effect (if not, only the bind date is shown). | PK24794
| | | | | | | 10 | Missing events and wrong point of failure determined in EXEC CICS DUMP analysis. | Following EXEC CICS HANDLE ABEND with the label option, the TACB is incorrectly considered to be representing a historical event which is no longer active. | The TACB is considered to be still active at the time when EXEC CICS DUMP is issued if the application has issued EXEC CICS HANDLE ABEND with the LABEL option. | PK26564 | | 11 | IDI0106E message or hung Fault Analyzer processes. | Intermittent hung Fault Analyzer jobs or message IDI0106E when the IDIS subsystem has a $$INDEX update task fail. | Code has been added to prevent the hang from happening. | PK26624 | | 12 | Some line command error messages from the Fault Entry List display are lost when View matching is in effect. | Messages, such as "Reanalysis not possible", can be lost if the MATCH command has been used to display only a subset of faults, as the message showing the MATCH columns used is issued instead. | Made the MATCH columns used message conditional on there not being another more important message waiting to be issued. | PK26603 | | 13 | IDI0092S message issued when analyzing inactive COBOL programs. | Locating CSECT IANCHOR using WhereAmI() iteration and unnecessary script re-dispatches causes 2min time limit to be exceeded. | Problem areas re-coded. | PK26501 | | | | | | | 14 | EIBRESP and EIBRESP2 fields not being displayed in formatted EIB report. | EIBRESP and EIBRESP2 are not being shown if EIBRCODE is also shown. | EIBRESP and EIBRESP2 are now always formatted and presented in the report. | PK26561 | | 15 | System dump analysis for CICS 6.2 and later releases, storage manager exception with code X'0F0C' is not correctly analyzed. | The parameter list for exception trace with code X'0F0C' has changed in CICS 6.2 and later releases. | The changed parameter list is now being handled correctly, additional data is displayed, and an attempt is made to identify the task which caused the storage check. | PK26615 | | 16 | IDILANGX issues messages IDISF8131S and IDISF8132S and no side file is created. | Print Control Character encountered in Enterprise PL/I compiler listing were not being allowed for. | Print Control Characters are now being allowed for. | PK25785 | | 17 | Fault Analyzer CICS system dump analysis does not recognize new TCB modes and domains in CICS TS 2.3 and CICS TS 3.1. | Not all new TCB modes were being recognized. | Panels which analyze the CICS DS (dispatcher) domain now recognize and display new TCB modes and domains. | PK26619
| | | | | | | 18 | The program causing an abend does not appear in the event summary. | The CICS LIWA (Language Interface Work Area) appears to be overwritten. Because the saved register 13 is zero, no DSA back chaining was possible. | If the LIWA appears to be overwritten and a CIB exists, register 13 in the CIB is used for DSA back-chaining. | PK25238 | | 19 | IDI0013S abend S0C4 in STIMERE routine of IDIDA invocation exit. | If a hang occurs in LE termination processing when IDIDA completes its analysis of a prior abend, an S0C4 abend can result from attempting to address storage now freed by the LE termination. | Further protection added for timeout processing in a hung termination condition. | PK26620 | | 20 | Abend S0C4 in IDILANGX processing Assembler SYSADATA. | Some SYSADATA files can cause an S0C4 abend in IDILANGX processing. | Corrected uninitialized variable. | PK26621 | | 21 | Loop or abend S0C4 during CICS system dump analysis in function PP_RM_LNKS. | Control blocks are corrupted in the CICS Recovery Manager domain. Fault Analyzer was not anticipating bad data. | Fault Analyzer processing of data in both the Recovery Manager and Directory domains has been enhanced to allow for corrupted control blocks. | PK26622 | | | | | | | 22 | Loop and IDI0092S message if an overlay produces a DSA loop. | If an application overlay in CICS produces a DSA chain that loops back on itself, Fault Analyzer may loop. | Additional loop detection added. | PK26623 |
APAR PK17305 Fixes and Enhancements | | Problem | Description | Fix | Complete APAR information | | 1 | Only the first variable declared as BASED(ADDR(xxx appears correctly in the Fault Analyzer report. | Only the first entry of the BASED(ADDR table is being used, as the basing expression is using the initial pointer. 2 and above produced listings not recognized by IDILANGX. There were also problems with support for the VB rather than VBA listing data sets. | The basing expression is now using the current pointer, allowing the full table to be used. | PK17305
| | 2 | Message IDI0002I is sometimes corrupted when LANGUAGE(JPN) is in effect. | The message corruption is due to incorrect behavior of an external run-time function used to format the message text. If no inserts are to be included in the message text at the time of writing the message to the console, the formatting routine is not called. The inserts are generally handled prior to this. | The call to the formatting routine, prior to writing the message to the console, has been removed in those cases where there are no message inserts. | PK17305 | | 3 | No warning issued when incorrect compiler listing/sidefile specified during interactive re-analysis. | Interactive re-analysis allows the specified compiler listing/sidefile to be used as realtime/re-analysis will reject the file when a signature check failed. | A popup now appears during re-analysis when a compiler listing/sidefile mismatch is detected. The popup allows the user to continue with the mismatched listing/sidefile or to specify a new compiler listing/sidefile. | PK17615 | | 4 | S0C4 in EQALANGX | An uninitialised pointer caused an S0C4 for a very small Assembler module. | Initialised the pointer to zero. | PK17616 | | | | | | | 5 | Variables missing for Enterprise PL/I 3.4 programs. | File/Line numbers not scanned from listing correctly. | Variable File/Line number position catered for as number of digits in SEQNBR determines location of File/Line number. | PK17855 | | 6 | IDI0089I Subsystem IDISDB2S RC=4 SQLCODE -104ILLEGAL SYMBOL ",9". | In DB2 systems that interpret the comma as the decimal point indicator (those with DSNHDECP DECIMAL=COMMA) the SUBSTR commas must be followed by a space. | SQL select call's using SUBSTR changed to add a space after the comma. | PK18862 | | 7 | CICS transaction dumps not being suppressed for Normal duplicates. | The Normal duplicate detection mechanism was not correctly informing the CICS invocation exits that there was a Normal duplicate and hence the CICS transaction dump was not being suppressed. | The CICS invocation exits are now correctly notified of a no rmal duplicate and hence the cics transaction dump is suppressed. | PK18681
| | 8 | Wrong point of failure given in CICS transaction dump analysis with abend code 'n/a'. | CICS TACBs may contain a zero abend code which is presented as 'n/a'. | TACBs with a zero abend code are now not used to determine the point of failure and will not be conisdered to be an event. | PK18682 | | | | | | | 9 | Possible 0C4 in IDILANGX depending on coding style of PL/I declarations. | Overlay of variable length data. | Overlay fixed. | PK18865 | | 10 | IDILANGP gives incorrect offsets for COBOL Procedure Division statements. | PROCTAB data is provided in offset sequence rather than stmt# sequence as for source lines. | A PROCTAB lookup table in stmt# sequence is now used to supply offset. | PK21359 | | 11 | Wrong parameter reported when it is part of a COBOL redefines. | Redefines logic incomplete for low level group items. | Redefines logic corrected. | PK18859 | | 12 | An attempt to issue a long message might cause storage overlays and subsequent abends. | An insufficient buffer size was used to hold the message with all of its inserts resolved. | The buffer size has been increased. | PK18730 | | | | | | | 13 | IDILANGX of C++ getting message IDISF8100S C++ contains recognized IDISF8132S Input file format invalid | Compiling using the C++ CBCC procedure front end on z/OS. | Code added for the later C++ compiler listings and VB, VBA, FB, FBA support. | PK15158 | | 14 | PDS history file full condition causing SVC dumps and IDI0011,12,13 messages. | When a PDS history file gets a D37 abend the recovery did not suppress the IDI0011,12,13 message sequence. | Code added to suppress the IDIXDCAP messages around a history file abend condition. | PK21552 | | 15 | IDI0082E DB2 Call Level Interface error: ODBC DLL function DSNAOCLI not found. | The method used to determine if the DSNAOCLI load module is available is not always providing the correct result, causing message IDI0082E to be sometimes issued incorrectly. | A different method for determining the availability of load module DSNAOCLI has been implemented. | PK21363 | | 16 | ABEND 0C4 in CICS BMC Mainview when Fault Analyzer TCB is terminating. | Under CICS Fault Analyzer real time analysis when the process is complete and the Fault Analyzer TCB is terminating, there is a timing window where the storage address placed into TCBCAUF is freed by MVS but the TCB still exists. This can cause a Mainview 0C4. | TCBCAUF will be cleared prior to LE termination and TCB DETACH. | PK21388 | | | | | | | 17 | IDILANGX loops when processing BASED(ADDR variables. | Incomplete (incompatible) symbol information caused loop in Find_Element(). | BASED(ADDR variables resolved by post processor when all symbol information is complete. | PK21425 | | 18 | Enterprise PL/I structure components declared using PICTURE specification are not formatted or appear with wrong declaration. | Length not set from Aggregate Length Table. | Length set from Aggregate Length Table. | PK20089 | | 19 | IDI0092S timeout in Fault Analyzer if the $$INDEX processing was interrupted. | An error condition in the History File $$INDEX member can cause a loop. | Code added to correctly process duplicate fault entries in the $$INDEX. | PK20280 | | 20 | Wrong source code shown for COBOL translator generated variables. | There is no source code declaration for these variables. | These variables no longer appear in the synopsis or abending event detail but are formatted in the Associated Storage Areas substituting the symbol name for the source declaration. | PK20421 | | | | | | | 21 | The IDIXCX53 exit program is causing an ATNI abend to occur. | The exit program is attempting to read the terminal buffer when processing an abend on the TCP (Terminal Control) task. | The exit program now suppresses the terminal buffer read when the abending task is TCP. | PK21426 | | 22 | Fault Analyzer abends with 0C7 when attempting to evaluate a PL/I packed decimal array subscript. | The sprintf() library function abends when invalid packed decimal data is passed to it. | PL/I packed decimal array subscripts are checked for valid data before being evaluated. | PK21560 | | 23 | Incorrect output for Enterprise PL/I 3.5 compile listing support in Fault Analyzer. | Support for IDILANGX side files was not complete for Enterprise PL/I version 3 release 5. | Enterprise PL/I 3.6 IDILANGX support has been added. | PK21232 | | 24 | Abend 0C4 in IDISUPDI IDIS Fault Analyzer sybsystem after an IDIS0044I duplicate entry is processed. | An abend 0C4 can occur in the IDIS subsystem when a duplicate fault IDI0044I is being processed. | Variable initialization corrected. | PK21345 | | | | | | | 25 | 0C4 abends with CICS/TS 3.1 when Fault Analyzer processing ATND aben d. | Incorrect offset values being used for TCT fields for CICS/T S 3.1 | The code has been altered to ensure correct offset value is used. | PK21357 | | 26 | Possible IDI0106E ENQ time out when running IDIS subsystem with PARM='UPDINDEX' | High activity on a history file $$INDEX member being managed by the IDIS subsystem with PARM='UPDINDEX' set may cause the subsystem to the data set ENQ and cause IDI0106E messages. | The test for ENQ waiting has been enhanced to alleviate issues resulting in IDI0106E messages. | PK17305 |
APAR PK18784 Fixes and Enhancements | | Problem | Description | Fix | Complete APAR information | | 1 | MESSAGE IDIM001 CONTAINS INCORRECT CHARACTERS | Missing a character in IDIM00 | IDIM00 corrected accordingly. | PK18784 |
APAR PK16200 Fixes and Enhancements | | Problem | Description | Fix | Complete APAR information | | 1 | USER'S GUIDE AND REFERENCE IS IN ENGLISH. | THE JAPANESE TRANSLATION OF THE USER'S GUIDE AND REFERENCE WAS NOT AVAILABLE AT GA DATE. | THE JAPANESE TRANSLATION OF THE USER'S GUIDE AND REFERENCE IS NOW AVAILABLE. | PK16200 |
APAR PK14702 Fixes and Enhancements | | Problem | Description | Fix | Complete APAR information | | 1 | Start address for contiguous COBOL base locators is incorrect when no sidefile is found. | Address of last contiguous base locator is used. | Address of first contiguous base locator now used. | | | 2 | Abend 102 from the IDIS Fault Analyzer subsystem may be followed by a 12 byte overlay and various MVS system problems. | In the IDIS subsystem when a requesting address space is forced or canceled, an abend S102 will occur. Under some conditions the processing of the S102 abend can cause a 12 byte overlay of system storage followed by various system problems or failures. | The x-memory POST routine ERRET routine process has been corrected. | | | 3 | Data Fields might not appear for optimized Enterprise COBOL events. | Optimization can result in code movement. This may cause statements that do not generate code to occur at the same offset as the abending statement. These 'inert' statments cause cross-referencing to fail. | Moved code is now detected and ignored when located at the same offset as the abending statement. | | | 4 | The second execution of a SetFaultPrefix against an empty history file incorrectly gets an 'invalid history file' condition. | The $$BACKUP member in the history file created by the first command is incorrectly detected as an invalid fault entry. | The logic is corrected to bypass the $$BACKUP member. | | | | | | | | 5 | Duplicate faults being written to a history file when these should instead have updated the duplicate counter of the first instance of the fault. | When multiple identical faults occur within a very short period of time, the fault entry member of the first fault might not have been completely written by the time a check for duplicates is made for the second fault. | The check for the existence of a fault entry member has been made conditional, based on the time between the two faults, to ensure that recent faults are not discarded if their fault entry members have not yet been written. | | | 6 | Fault Analyzer shows wrong parameter for IDISNAP. | Parameter was part of a redefinition and the object of the redefinition was being shown instead. | Corrected offset into redefinitions logic. | | | 7 | Abend S213-30 on IDILANGX output data set if DISP=SHR coded. | The IDILANGX output data set could get ABEND213 rc=30 open for concurrent output if the JCL has DISP=SHR rather than DISP=OLD. DISP=OLD can be difficult to schedule. | Added SPFEDIT ENQ around the IDILANGX output data set open. | | | 8 | IDILANGX source records do not point to the correct code CSECT. | The CSECT record has CEESTART as the first entry and all source records point to it. However, source records should point to the code CSECT. | CEESTART is now ignored when External Symbol Dictionary is processed, allowing the correct code CSECT to be placed in the first entry of the CSECT record. | | | | | | | | 9 | Symbols defined to MVS are not substituted in options read from the IDIOPTS DDname. | Only options read from the default IDICNF00 parmlib member are considered for MVS symbol substitution. If the same parmlib member is pointed to by an IDIOPTS DDname, then no MVS symbol substitution occurs. | The MVS symbol substitution service, ASASYMBM, is now called for all options processed, regardless of their source or the method by which they are obtained. | | | 10 | Intermittent ABEND U4039 S32E in Fault Analyzer IDIS subsystem. | CEEDUMP output shows ABEND 32E in IDISUPDI routine RSTSSTMS. | The timing exposure between the STIMERM exit and the STIMERM CANCEL routine has been corrected. | | | 11 | RC=1551 from IDILANGX. | A storage allocation problem has occurred when attempting to store a large structure. | The storing of structures has been made more efficient and, in the case when suppressed copybooks are not present, is not carried out at all. | | | 12 | No batch reanalysis report written if the DeferredReport option is in effect. | The DeferredReport option was incorrectly suppressing the batch reanalysis report. | The batch reanalysis report is now written, regardless of the use of the DeferredReport option. | | | | | | | | 13 | Abend 0C4 using Fault Analyzer DSECT command on z/OS 1.5 and above | The Assembler ADATA mapping changes in 1.5 and above not correctly accomodated. | Additions made to the logic for HLASM 1.5 ADATA. | | | 14 | Message IDI0012S abend U4087 (and possibly other abends) when the primary subsystem (JES) is not available. | Required system resources are unavailable when the primary subsystem (JES) is not active. | A check has been added to determine if the primary subsystem (JES) is available. If it is not, then Fault Analyzer will not perform analysis. | | | 15 | Abend 0C4 in IDIDA after IDI0092S in LE termination. | An ENQ hang in LE termination caused the IDI0092S timer in Fault analyzer to expire but then an 0C4 occured due to the unusual circumstances of the Language Environment termination. | Code has been added to eliminate the 0C4 if IDI0092S is driven after LE termination. | | | 16 | Enterprise COBOL 3.4 is not fully supported. | The MAP section of the Enterprise COBOL 3.4 listing has a slight difference in the right most columns compared to earlier releases. | A code change was made to cater for both variations in the MAP section of the listings. | | | | | | | | 17 | PL/I data field values do not always show arrays. | Cross-referencing did not support arrays as data fields. | PL/I array support added to cross-referencing to report on subscript and element values. | | | 18 | Abend 0C1 trying to use IDILANGP. | Getting ABEND0C1 calling IDILANGP to print a pseudo listing from a side file. | Corrected return register. Corrected return register. | | | 19 | All data, except for the fault ID, missing from the Confirm Fault Entry Deletion display. | The associated ISPF variables were not defined. | All ISPF variables for data fields on the Confirm Fault Entry Deletion display have been defined. | | | 20 | In PL/I when a variable is based on the address of another variable, addressing of field contents is incorrect. | The xref listing does not link up the two symbols so IDILANGX does not complete the formation of the symbol that is based. | Code has been added to link up the two symbols and complete the formation of the based symbol. | | | | | | | | 21 | Fault Analyzer exits without message if insufficient storage is available. | An early check in the IDIXDCAP pre-dump exit for expected necessary storage required for issuing of a WTO message might cause Fault Analyzer to abort processing without providing any reason for this. | The storage check has been removed. As a result, a message will be issued if there is sufficient storage for MVS to do this, or an abend will occur. In either case, there should be some indication that Fault Analyzer was invoked and attempted analysis. | | | 22 | Loop and OC4 program check in CICS system dump analysis. | Incorrect processing of lock waiters in routine which looks for deadlocks between CICS tasks. | The number of lock waiters is used as the maximum iteration count in the loop. | | APAR PK16879 Fixes and Enhancements | | Problem | Description | Fix | Complete APAR information | | 1 | Abend S0C4 in DoSubVals at x'128A'.
| Unexpected array coding style in abending PL/I statement causing a logic problem resulting in an 0C4. | Variation in coding style has now been accomodated. | |
All available Version 5 Fault Analyzer PTFs and associated APARs (most recent first):
APAR PK65075 Fixes and Enhancements | | Problem | Description | Fix | Complete APAR information | | 1 | Unable to scroll horizontally to see a message explanation which exceeds 80 columns. | The keylist used for the IDIPLOOK panel did not include settings of PF10 and PF11 to the LEFT and RIGHT commands respectively. | The LEFT and RIGHT commands have been added to the IDIPIKY8 keylist. | PK65081 |
APAR PK64346 Fixes and Enhancements | | Problem | Description | Fix | Complete APAR information | | 1 | Abend S0C4 in module IDIXCX53 at offset X'192F6'. | An incorrect return code check was being made and hence code was being executed which should not have been. | The return code check has been corrected. | PK66816 | | 2 | Abend S0C7 when an abending COBOL program has COMP-3 OCCURS DEPENDING ON variable of less than 3 bytes which contains invalid packed decimal data. | C built-in function decchk() returns DEC_VALUE_OK for 1 and 2-byte packed fields which contain bad data. | Packed decimal data of less that 3 bytes is promoted to 3 bytes before calling decchk(). | PK66812 | | 3 | Associated Storage Areas missing with Enterprise COBOL 4.1 events. | Enterprise COBOL 4.1 product number (5655-S71) not recognized by Fault Analyzer. | Product number 5655-S71 has been added. | PK66811 | | 4 | IDIXDCAP abend S0C4 at offset X'1AE4'. | An abend occurred in the MVS subsystem interface, causing the IDIXDCAP ESTAE exit to unexpectedly receive a SDWA in a storage key other than 8. | The code has been changed to handle a SDWA in any storage key. | PK66739 | | 5 | Abend S0C4 in WriteMiniDump. | When Fault Analyzer is saving analysis of a system dump, it might get abend S0C4 in WriteMiniDump +7B6. | Code added to allow only 2K to be moved when low core is addressed. | PK66818 | | 6 | Loop in Fault Analyzer when analyzing CICS Temporary Storage queue control blocks. | One or more digital tree nodes have been overwritten. Fault Analyzer needs to reference these nodes to identify temporary storage queues. | All 'down pointers' in the nodes are now checked for double word alignment. If this check fails, then processing of the nodes and queues is abandoned, and a new severity 2 message is displayed. | PK66751 | | 7 | Fault Analyzer S0C4 in GetStgMem() when re-analyzing PL/I abend with a side file. | If no side file is available at the time of the abend, then storage for based variables is not included in the minidump, and subsequent re-analysis using a side file might attempt to access this storage, possibly causing abend S0C4 in GetStgMem(). | Bad basing pointers (i.e., pointers to storage not in the minidump) are identified and reported in the Associated Storage Areas section. | PK66807 |
| Problem | Description | Fix | Complete APAR information | | 1 | IDILANGX issues messages IDISF8132S and IDISF8136S when processing Enterprise COBOL V4.1 compiler listing. | The Enterprise COBOL V4.1 compiler is not recognized by IDILANGX. | IDILANGX now recognizes the Enterprise COBOL V4.1 compiler. | PK63860
| | 2 | Task is missing on the CICS system dump analysis Task Summary display. | Summary lines are built for each task which has a Task Control Area (TCA), but the missing task is terminating and no longer has a TCA. | The CICS Kernel and transaction manager control blocks are now used to build and display summary lines for tasks without a TCA. | PK63795 | | 3 | COBOL SIGN IS LEADING/TRAILING SEPARATE CHARACTER clause causes incorrect reporting of data field values. | The instruction operands, when processing these data fields, do not necessarily point to the start of the data (for example, the PACK instruction operand for LEADING points passed the SIGN byte). | The data field addresses have been corrected. | PK63814 | | 4 | Copy to data set from the ISPF interface Services pull-down menu copies the visible display content only. | Implicit 'max down' missing to obtain lines beyond the visible screen depth. | Implicit 'max down' added. | PK63865 | | 5 | Information about CICS-managed files not provided in 'Open Files' section of the analysis report. | CICS file control data areas are not referenced during the creation of the 'Open Files' report. | For CICS transaction abend analysis, CICS file control data areas are now referenced. | PK63872 | | 6 | Unable to specify compiler listing or side file data set name on prompt during interactive reanalysis if no TSO prefix set. | When using TSO PROFILE NOPREFIX, the data set name specified on the prompt during interactive reanalysis was being processed incorrectly, causing the prompt to reject the specified data set name. | The specified compiler listing or side file data set name is now processed correctly, even when TSO PROFILE NOPREFIX is used. | PK63371 | | 7 | Options on initial interactive reanalysis menu disappear after formatting event details. | A flag was being incorrectly set as part of the event formatting process, which caused the initial menu to be incorrectly re-displayed. | The flag is now correctly set and restored. | PK63788 | | 8 | Enterprise PL/I compiler listing created with RENT option in effect results in blank CSECT names in the IDILANGX X'0E' record. | The EXTERNAL SYMBOL DICTIONARY section of the compiler listing uses a single column, but the code expects two columns. | Code added to support 1 or 2 columns. | PK63869 |
APAR PK56124 Fixes and Enhancements | | Problem | Description | Fix | Complete APAR information | | 1 | Message IDI0032W I/O error writing report: EDC5003I truncation of a record occurred during an I/O operation. | Invalid DB2 GRAPHIC type host variable data was not being adequately validated before attempted written to the report. | Improved validation has been added. | PK61769 | | 2 | Abend S0C4 in mapCsectEntryPoint() when analyzing a CICS system dump. | Invalid key data was being added. | The invalid key data has been corrected. | PK61708 | | 3 | Incorrect length presented for second operand of an MVCL (Move Characters Long) instruction. | Bits 0-7 of the MVCL source length register represent a padding character. This was not being taken into account when presenting the length. | The length is now derived from bits 8-31 of the source length register. | PK61770 | | 4 | Fault Analyzer loops when reporting registers for a COBOL program with sidefile provided. | The data item pointed to by the register was not on the abending source line, and has a REDEFINES. | The source line checking for a variable is bypassed when the function is called from the register display. | PK61772 | | 5 | Message IDI0047S abend S0C4 in LE run-time function strspn, called from PrtHostVars during formatting of DB2 VARCHAR host variable data. | An ending NULL character was not added to the end of the buffer. | The ending NULL character has been added. | PK58966 | | 6 | IDI0032W I/O error writing report: EDC5009I An I/O operation was attempted using an invalid FILE pointer. | An attempt was made to write the analysis report to IDIREPRT, which had not been allocated due to the DeferredReport option being in effect. | A check has been added for the DeferredReport option being in effect before attempting to write to IDIREPRT. | PK59288 | | 7 | Table element stride is incorrect when using COBOL SYSDEBUG sidefile. | Non-OCCURS DEPENDING ON (ODO) tables are being re-calibrated when a program contains one or more ODO tables. | The re-calibration logic has been corrected. | PK61687 | | 8 | Corrupted Japanese text in the formatted storage display, or failure to successfully copy the display to a data set with the COPY command. | The display contains invalid DBCS characters due to missing shift-in characters. | The missing shift-in characters have been added. | PK61774 | | 9 | Abend S0C4 in makeString() during CICS system dump analysis when processing 3-character transaction number (for example, TCP) from KE Error Table Summary. | A wrong value was passed to makeString(). | The transaction-number processing has been corrected. | PK61699 |
APAR PK50514 Fixes and Enhancements | | Problem | Description | Fix | Complete APAR information | | 1 | Initial paragraph on panel IDIPILPT is truncated. | An inappropriate DTL tag, which does not allow formatting of more than one line, was being used. | A different tag has been used to permit text which exceeds one line to be formatted correctly. | PK50727 |
APAR PK52718 Fixes and Enhancements | | Problem | Description | Fix | Complete APAR information | | 1 | Side file for abending COBOL event is not being used, resulting in missing analysis report source line information. | Previous event's R15 is not pointing at the following COBOL event's entry point. | Alternative method for determining COBOL entry point address implemented. | PK55093 | | 2 | An S0C4 abend occurs in function pp_ueh_main due to an invalid reference to an array of global user exit names. | New exits in CICS TS 3.1 and TS 3.2 are not defined in the array of user exit names. | The names of global user exits which are new in CICS TS 3.1 and TS 3.2 are now defined to Fault Analyzer. | PK55177 | | 3 | Message IEC036I 002-18 followed by message IDI0124E might be issued from the IDIS subsystem. | In situations where a high number of duplicate abends occur for the same fault entry, a record length error can result in message IEC036I 002-18 being issued in the IDIS subsystem. | The record length problem on writing to the history file $$INDEX member has been corrected. | PK55114 | | 4 | Abend S0C4 in IDIDA DFHTT640 when formatting a socket domain CICS trace entry. | An abend S0C4 might occur on a MVCL instruction in DFHTT640 when formatting a CICS socket domain trace entry. | Code in the the call interface to DFHTT64 has been changed to circumvent the wrong length move problem. | PK55430 | | 5 | Poor analysis performance when a job causes many WTO messages that do not start with a formal message ID to be issued. | An attempt was being made to find an explanation for the presumed message ID at the start of each WTO message. | Improved verification of the presumed message ID has been implemented to avoid the overhead of searching for a message explanation when none exists. | PK55478 | | 6 | Message IDI0092S time-out after 32 minutes. | When writing a large report, the time expected for completion was being incremented repeatedly until the maximum of 32 minutes was reached. | The expected time for completion of a large report is now incremented only once. | PK55485 | | 7 | SYSUDUMP not suppressed when a Fault Analyzer warning message (W level) is issued. | The return code set when any Fault Analyzer messages, other than informational messages (I level), were issued, caused the MVS dump (SYSUDUMP, SYSMDUMP, or SYSABEND) to not be suppressed with the RetainDump(AUTO) option in effect. | A change has been made to ensure that only severe error messages (S level) will cause the MVS dump to not be suppressed. | PK55488 | | 8 | Fault Analyzer event list 'loaded from' might be 'n/a' if the data set has EXECUTE ONLY security access. | When the load data set security is 'EXECUTE ONLY', then the Fault Analyzer event list 'loaded from' column might show 'n/a' instead of the load data set name. | The logic path encountering the 'EXECUTE ONLY' access has been corrected to retain the load data set name. | PK55433 | | 9 | Fault Analyzer ISPF display might not show all fault entries recently created. | If Fault Analyzer is running without the IDIS subsystem and PARM='UPDINDEX', then fault entries recently created might not be displayed in the ISPF view until another action, such as deletion of a fault entry, occurs. | The timing condition with parallel creation of multiple fault entries, and the history display without UPDINDEX, has been corrected. | PK56354 |
APAR PK49805 Fixes and Enhancements | | Problem | Description | Fix | Complete APAR information | | 1 | IMS BMP region hung, waiting for ENQ on major name SYSIDIDA minor name SYSOUT. | An ENQ issued earlier during analysis of an abend in the IEFIIC initiator TCB was still active. | Fault Analyzer has been excluded from performing analysis of abends in the IEFIIC initiator TCB. | PK51950 | | 2 | No Formatting user exit output available in the interactive reanalysis report when the DeferredReport option is in effect. | A check for the DeferredReport option being in effect was incorrectly being made without consideration of real-time or interactive reanalysis execution mode. | The DeferredReport option is now ignored for the display of Formatting user exit output in the interactive reanalysis report. | PK51968 | | 3 | Excessive minidumps are being generated. | While validating a data area, an incorrect length was being used. | The incorrect length has been corrected. | PK52177 | | 4 | IDI0092S time-out from Fault Analyzer with a very large COBOL listing. | Fault Analyzer processing of a very large COBOL listing for IDILANGX processing from a real time abend can get message IDI0092S because of the extended time required. | The call to IDILANGX to process listings for source code analysis, has extended time allowed before loop protection time-out will occur. | PK52464 |
APAR PK46022 Fixes and Enhancements |
APAR PK42495 Fixes and Enhancements |
APAR PK39012 Fixes and Enhancements |
APAR PK35278 Fixes and Enhancements |
APAR PK30902 Fixes and Enhancements | | Problem | Description | Fix | Complete APAR information | | 1 | Abend S0C4 in WriteMinidump if the history file gets abend SE37. | Variables were reset on detection of a write error, but later used to reference data that did not exist. | The variables are no longer reset. | PK31284 | | 2 | COBOL data items declared on base locator boundary result in offsets shifted by 1 byte. | Offset fix-up for IDILANGX symbol records incorrect. | Offset fix-up for IDILANGX symbol records now occurs for all data items, other than items at base locator zero, offset zero. | PK34962 | | 3 | Abend S0C7 followed by abend S0C4 during analysis of CICS system dump. | An attempt was made to unpack an invalid packed decimal number. | The code now validates the packed number before using it. | PK30443 | | 4 | QUIET option with no sub-options is not suppressing IDI0066I messages. | The check for suppression of IDI0066I messages was not considering the QUIET option having been specified without any suboptions. | QUIET is now supported and will cause suppression of the IDI 0066I message. | PK30263 | | | | | | | 5 | Abend S0C4 in entry point DoSubVals when PL/I abending statement contains both an array and non-array variable with the same name. | When the PL/I abending statement contains two variables of the same name, one being an array and the other not, the wrong symbol is accessed as the array. This symbol contains a zero pointer, which eventually causes an abend S0C4. | The code now correctly identifies the array symbol when parsing the application source line. | PK30418 | | 6 | Abend S0C4 in Fault Analyzer leading to message IDI0047S. | Low fetch-protected storage accessed while traversing the application DSA chain. | The storage access is now not attempted unless the address is higher than 4095 (X'FFF'). | PK30689 | | 7 | IDILANGX loop near label FIND_ID when processing PL/I compiler listing. | When multiple instances of a variable name are assigned to structure members, and one of these is used in a BASED(ADDR) expression, checking of ancestors causes a loop if an ancestor does not have an owner. | Ensured that ancestors without an owner will break the loop. | PK30632 | | 8 | COBOL Level 88 point-and-shoot fields do not appear in formatted storage when using a SYSDEBUG sidefile. | Support for COBOL Level 88 items via SYSDEBUG file not implemented. | COBOL SYSDEBUG file now includes support for Level 88 items. | PK31217 | | | | | | | 9 | PL/I external variables are not reported, or reported at incorrect addresses. | Duplicate variable names cause wrong symbol to be updated. | Symbols not updated unless scope is known. | PK31137 | | 10 | Abend S0C4 in IRXINIT offset X'A36' during REXX initialization. | It is a REXX restriction that the job step TCB (TCBPKF) must be key 8. A check was made for a non-zero key, other than 8, when it should have included key 0 also. | The check for an environment in which REXX is supported has been changed to include key 0 as an unsupported environment. | PK34990 | | 11 | Return code 3128 from IDILANGX when used under SCLM. | An additional open of the listing data set, used for DCB information extraction, was causing subsequent errors under SCLM. | The information extracted by the additional data set open is now determined via DYNALLOC, which stops the rc=3128 under SCLM. | PK31925 | | 12 | Missing event in analysis of S0C1 program check. | Fault Analyzer failed to determine the entry point of the abending program, and thus did not create an associated event. | Code has been added to identify the entry point and create an event for the abending program. | PK35009 | | | | | | | 13 | Incorrect properties display for empty history files. | Uninitialized storage being used when displaying information for an empty history file. | Code changed to correctly handle empty history files. | PK32475 | | 14 | BMC MV S0C4 due to TCBCAUF invalid. | Field TCBCAUF was not being cleared if abend analysis was being skipped due to EXCLUDE option processing. | TCBCAUF is now correctly cleared. | PK34450 | | 15 | Abend S378-X'14' or S0C1 abends during or following calls to a Compiler Listing Read user exit. | A work area pointer used by an earlier Message and Abend Code Explanation user exit call had not been cleared. | The work area pointer has been cleared. | PK35010 | | 16 | Abend S0C4 in IDnotify + X'33C'. | The abend is caused by a storage overlay, resulting from the use of an entry point name that is longer than 198 characters. | The code has been amended to handle entry point names of any length. | PK35011 | | | | | | | 17 | Hang ENQ lockout on IDIDA SYSOUT after load failure on IDIDA. | Load failure S106 abend during ATTACH of IDIDA causes ENQ lockout on major IDIDA minor SYSOUT. In this case it was a DB2 stored procedure region running out of storage that caused the load failure. | The code that detects recursion was enhanced to also recognize an ATTACH load failure of IDIDA. | PK35013 | | 18 | Incorrect events created. | An invalid DSA backchain pointer is not being detected. | Additional DSA checks are now performed, which prevent the incorrect events from being created. Also, a note about this is now displayed in the event details section of the report. | PK35014 | | 19 | Message IDI0070E incorrectly displayed using CFA transaction in a CICS 4.1 region. | The CFA transaction is trying to determine the CICS release using a table and lookup mechanism, which is failing to find a table entry for CICS 4.1. | The table and lookup mechanism has been corrected. | PK35017 | | 20 | Abend S0C4 or LE abend U4094 during analysis of DB2 fault. | An LE heap storage overlay was caused by invalid offsets used to insert DB2 host variable names into the DBRM SQL statement. | The host variable name offsets are validated before being used. | PK35021 |
APAR PK28146 Fixes and Enhancements | | Problem | Description | Fix | Complete APAR information | | 1 | Incorrect event summary and point of failure for CICS/VAGen program. | The DSA chaining function for CICS transactions has no awareness of VAGen runtime modules and the way that they interact with the application. | Additional support added to the CICS DSA chaining function to recognize CICS/VAgen runtime modules and take appropriate action. | PK26639 | | 2 | If a View containing a -Match criteria is selected using the VIEWS command or the File->List Views pull-down, then the -Match criteria might not be actioned. | The problem can occur if a view is already displayed and another view is selected by other means than overtyping the current view name in the Fault Entry List display. A flag that controls the actioning of a -Match criteria had not been reset. | The flag that controls the -Match actioning is now being reset correctly, regardless of the method used to select a view. | PK27879 | | | | | | | 3 | CICS system dump analysis terminated with message IDI0105S IDIECAP:146 Storage allocation for 0 (X'0') bytes failed - processing terminated. | A dump has been taken during CICS initialization before the Transaction Manager has created any tasks. Fault Analyzer was assuming that at least one task exists. | A check is now made for zero tasks, and the storage allocation is not attempted. | PK27850 | | 4 | CICS Trace may appear to loop during find previous command. | The existing code was unable to handle the special requirements for the CICS trace table display. | Function call and condition variables corrected. | PK27849 | | 5 | COBOL elementary item names missing when formatting a GROUP OCCURS that is unnamed. | Positioning elementary table item names for each occurrence is based on having located the GROUP OCCURS name. | Elementary table items are positioned after the group level number (where the name would normally appear). | PK27915 | | 6 | S0C4 abend in function FATABOKS. | Failure to LOAD the SVC back-end program IDISVC01 is not handled correctly, which leads to the program check. | The parameter list passed to the SVC routine is now checked for an indication of an unsuccessful load. If this occurs, then a message is issued and the program check is avoided. | PK29202 | | | | | | | 7 | Loop in CICS SDUMP processing. | The reference to a CICS control block was not being checked correctly, and due to an invalid address, was being referenced continually. | The reference to the control block is now correctly checked. | PK28145 | | 8 | CICS is issuing an AEXZ abend when Fault Analyzer is processing an AD2R abend. | The CICS/DB2 TRUE issues abend AD2R and then marks the L8 TCB unclean. IDIXCX53 subsequently receives control and issues an EXEC CICS request. DFHEIP issues a change mode request, which fails and leads to abend AEXZ. | IDIXCX53 checks whether the task is associated with an open TCB. When it is, then the mode is changed to 'float' around the execution of the EXEC CICS request. This persuades CICS not to attempt a TCB mode change. | PK29170 | | 9 | Fault entry indicates minidump available when no minidump was ever written. | If a fault is determined to be a duplicate of another fault, but an End Processing user exit overrides the default fault entry suppression, then a fault might be written with indication of a minidump being available, when in fact the minidump was suppressed. | The suppressed minidump is now reflected correctly in the fault entry written. | PK29255 | | 10 | Duplicate IDI0101I message for an analysis being excluded due to the DumpTableExclude option. | The analysis was being excluded from both the LE and XPCABND exits. | A flag is now correctly set to prevent the duplicate message. | PK28671 | | | | | | | 11 | S0C4 in IDILANGX when Enterprise COBOL is using DB2 co-processor. | Unexpected level 2 item (possibly SQL---VERS-DATA) appears as first item in map section of compiler listing. | Support has been added for a level 2 item as the first item in the map section. | PK29059 | | 12 | Heap storage overlay when large number of user exits are specified via the Exits option from more than one options source. | If the total number of user exit names for a given exit type (for example, CONTROL) is specified in the Exits option from more than one source (for example, in the IDICNF00 parmlib member and the IDIOPTS user options file), then a storage overlay can occur due to an incorrectly calculated length. | The length causing the overlay has been corrected. | PK29196 |
APAR PK22512 Fixes and Enhancements | | Problem | Description | Fix | Complete APAR information | | 1 | Abend S0C4 when analyzing DB2 PL/I abend. | Incorrect source line offset causes buffer overlay when collecting EXEC SQL source. | Source line offset corrected. | PK22069 | | 2 | COBOL SYSDEBUG file is rejected when program is re-compiled without change. | Compile date/time is checked with load module and a mismatch results in an unusable SYSDEBUG file. | Compile date/time check now replaced with signature check. Re-compiling without change will not affect this check. If signature check does fail, user can continue to use the SYSDEBUG file via the listing/mismatch pop-up. | PK26762 | | | | | | | 3 | INCLUDE/EXCLUDE processing not working correctly for dump/abend codes which contain unprintable characters. | Unprintable characters, specifically a leading null was effectively causing the CICSABEND include/exclude option to be skipped. | All unprintable characters are now converted to periods. | PK22836 | | 4 | ENQ lockout on Fault Analyzer history file if IDI0106E timeout. | IDI0106E timeout messages in the IDIS subsystem may be accompanied by ENQ lockout between multiple MVS images sharing a common history file. | Recovery processing improved to ensure error processes terminate correctly. | PK26767 | | 5 | Language environment option values are not correctly given for options defined in PARMLIB member CEEPRMxx. | Fault Analyzer had not been enhanced to support new function in z/OS 1.7. | The Fault Analyzer LE run-time options report now displays run-time options values set in CEEPRMxx. | PK26711 | | 6 | IDI0038W I/O error writing to softcopy book cache: EDC5065I A write system error was detected. __armc Data = rc fdbk lastop | An overlay of the IDICACHE KSDS key data occurred after checking for the existence of a cache record, but prior to writing a new record. On the next attempt to check and write to the cache for the same record, a duplicate overlaid record already exists. | A variable of insufficient length was used to hold the IDIBOOKS data set name. The length has been adjusted to prevent the overlay. | PK26706 | | | | | | | 7 | Poor performance, loops, abends, or incorrect/incomplete report when data sets containing records with lengths greater than 256 bytes are provided via a user exit. | Erroneous record truncation to 256 bytes occurred when a Compiler Listing user exit was used to provide the name of a compiler listing or side file data set to be used for source level reporting. | The problem causing truncation has been fixed. | PK23669
| | 8 | PL/I compile time missing from the Fault Analyzer report. | PL/I installation option TSTAMP=NO is in effect. | PL/I TSTAMP (compile date and time) is now retrieved from the end of the static CSECT provided TSTAMP=YES is in effect (if not, only the bind date is shown). | PK24744 | | 9 | Missing events and wrong point of failure determined in EXEC CICS DUMP analysis. | Following EXEC CICS HANDLE ABEND with the label option, the TACB is incorrectly considered to be representing a historical event which is no longer active. | The TACB is considered to be still active at the time when EXEC CICS DUMP is issued if the application has issued EXEC CICS HANDLE ABEND with the LABEL option. | PK25422 | | 10 | IDI0106E message or hung Fault Analyzer processes. | Intermittent hung Fault Analyzer jobs or message IDI0106E when the IDIS subsystem has a $$INDEX update task fail. | Code has been added to prevent the hang from happening. | PK26768
| | | | | | | 11 | Some line command error messages from the Fault Entry List display are lost when View matching is in effect. | Messages, such as "Reanalysis not possible", can be lost if the MATCH command has been used to display only a subset of faults, as the message showing the MATCH columns used is issued instead. | Made the MATCH columns used message conditional on there not being another more important message waiting to be issued. | PK26734 | | 12 | IDI0092S message issued when analyzing inactive COBOL programs. | Locating CSECT IANCHOR using WhereAmI() iteration and unnecessary script re-dispatches causes 2min time limit to be exceeded. | Problem areas re-coded. | PK25342 | | 13 | EIBRESP and EIBRESP2 fields not being displayed in formatted EIB report. | EIBRESP and EIBRESP2 are not being shown if EIBRCODE is also shown. | EIBRESP and EIBRESP2 are now always formatted and presented in the report. | PK25102 | | 14 | Fault Analyzer CICS system dump analysis does not recognize new TCB modes and domains in CICS TS 2.3 and CICS TS 3.1. | Not all new TCB modes were being recognized. | Panels which analyze the CICS DS (dispatcher) domain now recognize and display new TCB modes and domains. | PK26769
| | | | | | | 15 | IDI0013S abend S0C4 in STIMERE routine of IDIDA invocation exit or abend S0C4 in IDIXCX53 CICS exit. | If a hang occurs in LE termination processing when IDIDA completes its analysis of a prior abend, an S0C4 abend can result from attempting to address storage now freed by the LE termination. | Further protection added for timeout processing in a hung termination condition. | PK26770 | | 16 | Loop or abend S0C4 during CICS system dump analysis in function PP_RM_LNKS. | Control blocks are corrupted in the CICS Recovery Manager domain. Fault Analyzer was not anticipating bad data. | Fault Analyzer processing of data in both the Recovery Manager and Directory domains has been enhanced to allow for corrupted control blocks. | PK26761 | | 17 | Loop and IDI0092S message if an overlay produces a DSA loop. | If an application overlay in CICS produces a DSA chain that loops back on itself, Fault Analyzer may loop. | Additional loop detection added. | PK26771 |
APAR PK17315 Fixes and Enhancements | | Problem | Description | Fix | Complete APAR information | | 1 | Only the first variable declared as BASED(ADDR(xxx appears correctly in the Fault Analyzer report. | Only the first entry of the BASED(ADDR table is being used, as the basing expression is using the initial pointer. 2 and above produced listings not recognized by IDILANGX. There were also problems with support for the VB rather than VBA listing data sets. | The basing expression is now using the current pointer, allowing the full table to be used. | | | 2 | Incorrect offsets to data fields in IDISXPLA sample member. | A 4-byte reserved field is missing between ENV_LOOPPROTECTION_OPT and ENV_WRITE_ROUTINE_EP. | The reserved field has been added. | | | 3 | Message IDI0002I is sometimes corrupted when LANGUAGE(JPN) is in effect. | The message corruption is due to incorrect behavior of an external run-time function used to format the message text. | The call to the formatting routine, prior to writing the message to the console, has been removed in those cases where there are no message inserts. | | | 4 | No warning issued when incorrect compiler listing/sidefile specified during interactive re-analysis. | Interactive re-analysis allows the specified compiler listing/sidefile to be used as realtime/re-analysis will reject the file when a signature check failed. | A popup now appears during re-analysis when a compiler listing/sidefile mismatch is detected. The popup allows the user to continue with the mismatched listing/sidefile or to specify a new compiler listing/sidefile. | | | | | | | | 5 | S0C4 in EQALANGX | An uninitialised pointer caused an S0C4 for a very small Assembler module. | Initialised the pointer to zero. | | | 6 | Variables missing for Enterprise PL/I 3.4 programs. | File/Line numbers not scanned from listing correctly. | Variable File/Line number position catered for as number of digits in SEQNBR determines location of File/Line number. | | | 7 | IDI0089I Subsystem IDISDB2S RC=4 SQLCODE -104ILLEGAL SYMBOL ",9". | In DB2 systems that interpret the comma as the decimal point indicator (those with DSNHDECP DECIMAL=COMMA) the SUBSTR comma's must be followed by a space. | SQL select call's using SUBSTR changed to add a space after the comma. | | | 8 | CICS transaction dumps not being suppressed for Normal duplicates. | The Normal duplicate detection mechanism was not correctly informing the CICS invocation exits that there was a Normal duplicate and hence the CICS transaction dump was not being suppressed. | The CICS invocation exits are now correctly notified of a no rmal duplicate and hence the cics transaction dump is suppressed. | | | | | | | | 9 | Wrong point of failure given in CICS transaction dump analysis with abend code 'n/a'. | CICS TACBs may contain a zero abend code which is presented as 'n/a'. | TACBs with a zero abend code are now not used to determine the point of failure and will not be conisdered to be an event. | | | 10 | Possible 0C4 in IDILANGX depending on coding style of PL/I declarations. | Overlay of variable length data. | Overlay fixed. | | | 11 | Wrong parameter reported when it is part of a COBOL redefines. | Redefines logic incomplete for low level group items. | Redefines logic corrected. | | | 12 | An attempt to issue a long message might cause storage overlays and subsequent abends. | An insufficient buffer size was used to hold the message with all of its inserts resolved. | The buffer size has been increased. | | | | | | | | 13 | IDILANGP gives incorrect offsets for COBOL Procedure Division statements. | PROCTAB data is provided in offset sequence rather than stmt# seguence as for source lines. | A PROCTAB lookup table in stmt# sequence now used to supply offset. | | | 14 | IDILANGX of C++ getting message IDISF8100S C++ contains recognized IDISF8132S Input file format invalid | Compiling using the C++ CBCC procedure front end on z/OS. | Code added for the later C++ compiler listings and VB, VBA, FB, FBA support. | | | 15 | PDS history file full condition causing SVC dumps and IDI0011,12,13 messages. | When a PDS history file gets a D37 abend the recovery did not suppress the IDI0011,12,13 message sequence. | Code added to suppress the IDIXDCAP messages around a history file abend condition. | | | 16 | IDI0082E DB2 Call Level Interface error: ODBC DLL function DSNAOCLI not found. | The method used to determine if the DSNAOCLI load module is available is not always providing the correct result, causing message IDI0082E to be sometimes issued incorrectly. | A different method for determining the availability of load module DSNAOCLI has been implemented. | | | | | | | | 17 | ABEND 0C4 in CICS BMC Mainview when Fault Analyzer TCB is terminating. | Under CICS Fault Analyzer real time analysis when the process is complete and the Fault Analyzer TCB is terminating, there is a timing window where the storage address placed into TCBCAUF is freed by MVS but the TCB still exists. This can cause a Mainview 0C4. | TCBCAUF will be cleared prior to LE termination and TCB DETACH. | | | 18 | IDILANGX loops when processing BASED(ADDR variables. | Incomplete (incompatible) symbol information caused loop in Find_Element(). | BASED(ADDR variables resolved by post processor when all symbol information is complete. | | | 19 | Enterprise PL/I structure components declared using PICTURE specification are not formatted or appear with wrong declaration. | Length not set from Aggregate Length Table. | Length set from Aggregate Length Table. | | | 20 | The IDIXCX53 exit program is causing an ATNI abend to occur. | The exit program is attempting to read the terminal buffer when processing an abend on the TCP (Terminal Control) task. | The exit program now suppresses the terminal buffer read when the abending task is TCP. | | | | | | | | 21 | IDI0092S timeout in Fault Analyzer if the $$INDEX processing was interrupted. | An error condition in the History File $$INDEX member can cause a loop. | Code added to correctly process duplicate fault entries in the $$INDEX. | | | 22 | Wrong source code shown for COBOL translator generated variables. | There is no source code declaration for these variables. | These variables no longer appear in the synopsis or abending event detail but are formatted in the Associated Storage Areas substituting the symbol name for the source declaration. | | | 23 | Fault Analyzer abends with 0C7 when attempting to evaluate a PL/I packed decimal array subscript. | The sprintf() library function abends when invalid packed decimal data is passed to it. | PL/I packed decimal array subscripts are check for valid data before being evaluated. | | | 24 | Abend 0C4 in IDISUPDI IDIS Fault Analyzer subsystem after an IDIS0044I duplicate entry is processed. | Variable initialization incorrect. | Variable initialization corrected. | | | | | | | | 25 | 0C4 abends with CICS/TS 3.1 when Fault Analyzer processing ATND aben d. | Incorrect offset values being used for TCT fields for CICS/T S 3.1. | The code has been altered to ensure correct offset value used. | | | 26 | Possible IDI0106E ENQ time out when running IDIS subsystem with PARM='UPDINDEX' | High activity on a history file $$INDEX member being managed by the IDIS subsystem with PARM='UPDINDEX' set may cause the subsystem to the data set ENQ and cause IDI0106E messages. | The test for ENQ waiting has been enhanced to alleviate issues resulting in IDI0106E messages. | |
APAR PK18872 Fixes and Enhancements | | Problem | Description | Fix | Complete APAR information | | 1 | MESSAGE IDIM001 CONTAINS INCORRECT CHARACTERS | Missing a character in IDIM00 | IDIM00 corrected accordingly. | |
APAR PK13569 Fixes and Enhancements | | Problem | Description | Fix | Complete APAR information | | 1 | 0C1 in IDIDA in iconv() function. | Insufficient checks were being made on the validity of DBRM data which subsequently lead to a storage overlay and hence an 0C1 in iconv. | Additional validity checks have been added. | | | 2 | Start address for contiguous COBOL base locators is incorrect when no sidefile is found. | Address of last contiguous base locator is used. | Address of first contiguous base locator now used. | | | 3 | Abend 102 from the IDIS Fault Analyzer subsystem may be followed by a 12 byte overlay and various MVS system problems. | In the IDIS subsystem when a requesting address space is forced or canceled, an abend S102 will occur. Under some conditions the processing of the S102 abend can cause a 12 byte overlay of system storage followed by various system problems or failures. | The x-memory POST routine ERRET routine process has been corrected. | | | 4 | Data Fields might not appear for optimized Enterprise COBOL events. | Optimization can result in code movement. This may cause statements that do not generate code to occur at the same offset as the abending statement. These 'inert' statments cause cross-referencing to fail. | Moved code is now detected and ignored when located at the same offset as the abending statement. | | | | | | | | 5 | The second execution of a SetFaultPrefix against an empty history file incorrectly gets an 'invalid history file' condition. | The $$BACKUP member in the history file created by the first command is incorrectly detected as an invalid fault entry. | The logic is corrected to bypass the $$BACKUP member. | | | 6 | Duplicate faults being written to a history file when these should instead have updated the duplicate counter of the first instance of the fault. | When multiple identical faults occur within a very short period of time, the fault entry member of the first fault might not have been completely written by the time a check for duplicates is made for the second fault. | The check for the existence of a fault entry member has been made conditional, based on the time between the two faults, to ensure that recent faults are not discarded if their fault entry members have not yet been written. | | | 7 | Fault Analyzer shows wrong parameter for IDISNAP. | Parameter was part of a redefinition and the object of the redefinition was being shown instead. | Corrected offset into redefinitions logic. | | | 8 | IDILANGX source records do not point to the correct code CSECT. | The CSECT record has CEESTART as the first entry and all source records point to it. However, source records should point to the code CSECT. | CEESTART is now ignored when External Symbol Dictionary is processed, allowing the correct code CSECT to be placed in the first entry of the CSECT record. | | | | | | | | 9 | Symbols defined to MVS are not substituted in options read from the IDIOPTS DDname. | Only options read from the default IDICNF00 parmlib member are considered for MVS symbol substitution. If the same parmlib member is pointed to by an IDIOPTS DDname, then no MVS symbol substitution occurs. | The MVS symbol substitution service, ASASYMBM, is now called for all options processed, regardless of their source or the method by which they are obtained. | | | 10 | Intermittent ABEND U4039 S32E in Fault Analyzer IDIS subsystem. | CEEDUMP output shows ABEND 32E in IDISUPDI routine RSTSSTMS. | The timing exposure between the STIMERM exit and the STIMERM CANCLE routine has been corrected. | | | 11 | RC=1551 from IDILANGX. | A storage allocation problem has occurred when attempting to store a large structure. | The storing of structures has been made more efficient and, in the case when suppressed copybooks are not present, is not carried out at all. | | | 12 | No batch reanalysis report written if the DeferredReport option is in effect. | The DeferredReport option was incorrectly suppressing the batch reanalysis report. | The batch reanalysis report is now written, regardless of the use of the DeferredReport option. | | | | | | | | 13 | Abend 0C4 using Fault Analyzer DSECT command on z/OS 1.5 and above | The Assembler ADATA mapping changes in 1.5 and above not correctly accomodated. | Additions made to the logic for HLASM 1.5 ADATA. | | | 14 | Message IDI0012S abend U4087 (and possibly other abends) when the primary subsystem (JES) is not available. | Required system resources are unavailable when the primary subsystem (JES) is not active. | A check has been added to determine if the primary subsystem (JES) is available. If it is not, then Fault Analyzer will not perform analysis. | | | 15 | Enterprise COBOL 3.4 is not fully supported. | The MAP section of the Enterprise COBOL 3.4 listing has a slight difference in the right most columns compared to earlier releases. | A code change was made to cater for both variations in the MAP section of the listings. | | | 16 | PL/I data field values do not always show arrays. | Cross-referencing did not support arrays as data fields. | PL/I array support added to cross-referencing to report on subscript and element values. | | | | | | | | 17 | Abend 0C4 in IDIDA after IDI0092S in LE termination. | An ENQ hang in LE termination caused the IDI0092S timer in Fault analyzer to expire but then an 0C4 occured due to the unusual circumstances of the Language Environment termination. | Code has been added to eliminate the 0C4 if IDI0092S is driven after LE termination. | | | 18 | All data, except for the fault ID, missing from the Confirm Fault Entry Deletion display. | The associated ISPF variables were not defined. | All ISPF variables for data fields on the Confirm Fault Entry Deletion display have been defined. | | | 19 | In PL/I when a variable is based on the address of another variable, addressing of field contents is incorrect. | The xref listing does not link up the two symbols so IDILANGX does not complete the formation of the symbol that is based. | Code has been added to link up the two symbols and complete the formation of the based symbol. | | | 20 | Fault Analyzer exits without message if insufficient storage is available. | An early check in the IDIXDCAP pre-dump exit for expected necessary storage required for issuing of a WTO message might cause Fault Analyzer to abort processing without providing any reason for this. | The storage check has been removed. As a result, a message will be issued if there is sufficient storage for MVS to do this, or an abend will occur. In either case, there should be some indication that Fault Analyzer was invoked and attempted analysis. | | | | | | | | 21 | Loop and OC4 program check in CICS system dump analysis. | Incorrect processing of lock waiters in routine which looks for deadlocks between CICS tasks. | The number of lock waiters is used as the maximum iteration count in the loop. | | | 22 | IDIREPRT output for an IMS MPP abend is not shown until next abend if message IDI0005S occurs during the initial analysis. | When an out-of-storage condition occurs (message IDI0005S), no CLOSE of the IDIREPRT DDname is performed. Thus, given the special task management of an IMS MPP, the output written to IDIREPRT is not shown on the JES spool until the next abend occurs in the same IMS region. | The IDIREPRT file is being closed prior to returning control from Fault Analyzer in the case of message IDI0005S. | | | 23 | Message IDI0105S Storage allocation for 0 bytes failed in IDICCDB2 C A1 line 614. | A check for a valid length of data returned from queries against the DB2 system catalog was missing. | A check for a valid length has been added. | |
APAR PK12700 Fixes and Enhancements | | Problem | Description | Fix | Complete APAR information | | 1 | OC4 program check in CICS system dump analysis during build of file owners and waiters panel. | When a file owning task has no ENQ string, an attempt is made to free storage which has not been obtained. | A free will not now be attempted unless storage has been obtained to build the ENQ string. | | | 2 | Abend S0C4 in cOptions_main offset X'9348' when Fault Analyzer ISPF interface is started and DeferredReport option is in effect | The ISPF interface start-up was attempting to perform an update which is only applicable to real-time processing. | A test for the execution mode has been added. | | | 3 | Fault Analyzer ISPF display shows corrupted duplicate counter and CICS applid, termid and netname fields. | A partial HD segment overlay can occur with CICS transaction abends and a load module user exit. The problem does not occur with exits written in REXX. | The code has been corrected to avoid the overlay. | | | 4 | Need to disable the IDI0092S timer. | The LoopProtection process can result in message IDI0092S and the canceling of Fault Analyzer execution resulting in no analysis report. There needs to be an override of this
process to allow a report to be created. | The user is now able to set NoLoopProtection to allow a report to be created. | | APAR PK12788 Fixes and Enhancements | | Problem | Description | Fix | Complete APAR information | | 1 | Diaganostic message incorrectly displayed from file option 5 pull-down.
| Using the FA ISPF display file optoin 5 pull-down for system dump analysis generated a diagnostic message that should have been hidden. | Diagnostic line corrected. | | APAR PK12964 Fixes and Enhancements | | Problem | Description | Fix | Complete APAR information | | 1 | Abend S0C4 in PrtListingName when selecting source line number point-and-shoot field from the interactive reanalysis report. | Incorrect array of strings used for explanation of where the source information was derived. | The array has been corrected. | |
APAR PK11789 Fixes and Enhancements | | Problem | Description | Fix | Complete APAR information | | 1 | TRANSLATIONS FOR APAR PK11239 | TRANSLATIONS FOR APAR PK11239 | Translations complete. | |
APAR PK11239 Fixes and Enhancements |
APAR PK12031 Fixes and Enhancements | | Problem | Description | Fix | Complete APAR information | | 1 | SMPE Install problem for PTF UK07349 | Some parts changed from pre-linked to linked causing a problem when installing the PTF. | Changed the parts back to pre-linked. | |
APAR PK04460 Fixes and Enhancements | | Problem | Description | Fix | Complete APAR information | | 1 | Excessive storage is required to process COBOL loaded but not active programs. | COBOL programs loaded but not active with very large linkage sections require memory to store BLL information. | BLLs are not relevant to COBOL programs loaded but not active as the caller's storage may have been freed. Only BLW, BLV, BLX and IDX locators are recorded for COBOL programs loaded but not active. |
| | 2 | SVC dumps are taken for abends in the Fault Analyzer SVC. | It is possible that abends occur in the Fault Analyzer SVC while copying data from other address spaces since no locks are held. | Unneccesary dumps have been prevented. | | | 3 | Message CEE5101C rc=156 reason=0D07 0201 and LE abend U4093 rc=90 when running in POSIX(ON) environment. | If an abend occurs in a POSIX(ON) application, and the installation default is POSIX(ON), then Fault Analyzer will attempt to create another LE environment with POSIX(ON), which is not allowed. | Added POSIX(OFF) to Fault Analyzer LE options. | | | 4 | CICS terminates because of a Logger Problem and Fault Analyzer abends due to a storage exception - 0C4. | A message exceeded the maximum of 255 characters expected by Fault Analyzer. This caused a storage overwrite and possibly a protection exception. | Fault Analyzer has been changed to allow for dump messages of up to 511 characters. | | | 5 | IDI0066I message does not include which faultid the current fault is a duplicate of. | This information was not included in the message. | The faultid is now included in the IDI0066I message. | | | | | | | | 6 | Incorrect error messages in LE heap analysis, and then a loop occurs in the report stage. | Incorrect analysis of severely fragmented heaps. | Additional checks placed in heap analysis code to detect 'gaps' between storage elements which can occur in severely fragmented heaps. | | | 7 | IDISF8114S message for AGGREGATE, ATTRIBUTES,NEST, and OPTIONS. | These messages appear for Enterprise PL/1 3.4 which is not supported. | Support for Enterprise PL/1 3.4 added. | | | 8 | Data Field Values may be incorrect. | When the same program name occurs more than once in the event list, Data Field Values from one of the other programs may be reported. This is because the parent CSECT is not being checked. | Multiple instances of the same program are uniquely identified by checking that the base locators belong to the current CSECT. | | | | | | | | 9 | Incorrect DB2 host variable name. | The SQL statement parser did not recognize the SET keyword. | The SQL statement parser has been updated to recognize the SET keyword. | | | 10 | No information given in event summary for failing application running AMODE 24. | Fault Analyzer is treating an AMODE 24 instruction address as an AMODE 31 address. | The first byte of the instruction address is now set to binary zeros for AMODE 24. An event is now created for the failing application. | | | 11 | SYSLOG messages garbled when using LANGUAGE(JPN) option. | When issuing long SYSLOG messages that use the multiline WTO format, the splitting of the message across multiple line segments fails to properly consider the character state (DBCS or SBCS) or the message text, causing missing control characters for Japanese text. | The message writing routine has been made DBCS-aware. | | | 12 | System Abend0C4 reason code X'4' occurred in module IDILANGX csect IDIWUL2s at offset X'23C'. | Program was compiled with incorrect compiler options for successful IDILANGX execution. | Code change to help recognize missing sections of the listing so that an abend does not happen. | | | | | | | | 13 | Interactive reanalysis display garbled with LANGUAGE(JPN). | A 'shift in' character (X'0F') was missing in the right-most character position of a display line. | The missing 'shift in' character has been added. | | | 14 | Message IDI0092S time-out. | The time-out occurred when writing a large report (150,000+ lines). | An adjustment of the timer has been made to allow large reports to be written without causing the IDI0092S time-out. | | | 15 | Abends in application code due to field TCBUSER being modified by Fault Analyzer. | Fault Analyzer updates field TCBUSER to hold the address of an internal control block. This field can also be used by customer applications/exits and hence the modifying of this field can have knock on effects. | Fault Analyzer has been modified to use the TCB extension field TCBCAUF rather than TCBUSER. | | | 16 | When the Locale option is used, braces surrounding help text in the ISPF interface might not be shown correctly. | The variant characters of the current codeset are not being considered. | The codeset for the current locale is determined and the appropriate characters displayed. | | | | | | | | 17 | Source line and formatted storage areas do not appear for abending COBOL program even though correct sidefile is provided. | The COBOL program's TGT has been corrupted. | The compile time TGT in the COBOL program's CSECT is used when the run time TGT is damaged. This may provide a source line but not formatted storage areas (as the TGT locator cells may be damaged). Damaged TGTs are noted in the synopsis. | | | 18 | DB2 stored procedures getting MSGIDG306I,RC=08, RSN=528. | DB2 stored procedures that abend, may get a secondary problem from Fault analyzer with &TEMP data set not being unique.MSGIDG306I, RC=08, RSN=528. | The code was changed to not use fopen of &TEMP. | | | 19 | SetWrapFaultNumber resets to 0. | The SetWrapFaultNumber is getting reset to zero if the $$INDEX history file member is lost or deleted. | Backup of some of the main history file settings now kept in member $$BACKUP for automatic use by Fault Analyzer if the $$INDEX member has to be rebuilt. | | | 20 | IDI0103S IEWBIND error rc=3000514 module not found. | Modules in a VLF controlled library may not be found when Fault Analyzer calls the Binder for CSECT mapping. | Code has been changed to not use the CSVQUERY token for LLA/VLF loaded modules. | | | | | | | | 21 | Abend S0C4 in IDICBIMS + X'2E6'. | The IMS control region was terminating while the FA SVC was running against it. | Excluded FA IMS SVC processing for IMS U0402 abends. | | | 22 | Migrated langx dataset can cause IDI0092 message and hence analysis termination | The time allowed for Fault Analyzer analysis did not allow for the time taken to recall a migrated dataset | A check has now been added to see if a referenced langx/listing dataset is migrated and if so the analysis time is increased. | |
APAR PK01622 Fixes and Enhancements |
APAR PK00496 Fixes and Enhancements | | | | | |
