A fix is available
APAR status
Closed as program error.
Error description
Miscellaneous bug fixes
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All Fault Analyzer Version 11 users. * **************************************************************** * PROBLEM DESCRIPTION: 01. When processing CICS Trace entries * * to determine source line #, the * * mismatch pop-up is presented, even * * though the COBOL SYSDEBUG file * * matches. * * APAR PI10675 * * 02. Cursor scrolling not working * * correctly on the CICS Internal * * Trace display, Saved Report display * * and Compiler Listing display. * * APAR PI10676 * * 03. Error message "Not a history file" * * when specifying a migrated data set * * name on the Fault Entry List * * display. * * APAR PI10677 * * 04. IMS region shutdown held up by * * Fault Analyzer abend processing * * when initial abend TCB is holding * * LE MSGFILE ENQ. * * APAR PI10678 * * 05. Fault Analyzer IDIS subsystem might * * get recursive IDI0144E and IDI0124E * * messages. * * APAR PI10679 * * 06. Blank saved report displayed with * * 'V' or 'S' line command if history * * file specified using single quotes * * in a View member. * * APAR PI10680 * * 07. Fault Analyzer report for IMS Java * * might show an additional incorrect * * LE U4038 abend in the event * * summary. * * APAR PI10681 * * 08. Fault Analyzer might produce more * * than one RFR dump for one abend * * when short on storage. * * APAR PI10682 * * 09. More than one fault entry might be * * created if the IDIS subsystem is * * experiencing Cross-System Coupling * * Facility (XCF) message delays. * * APAR PI10683 * * 10. Message IDI0095 IDICABND:1415 * * CSVQUERY error. * * APAR PI10684 * * 11. Message IDI0092S Time 32 minutes * * for analysis exceeded. * * APAR PI10700 * * 12. Fast Exclude might not work for * * abends in tasks which prohibit * * queueing of asynchronous exits. * **************************************************************** * RECOMMENDATION: Apply the provided PTF. * **************************************************************** 01. DEBUGINF is not in the minidump. 02. The saved cursor position was being retrieved from an incorrect variable. 03. The check for expected history file attributes failed when the data set was migrated. 04. The IMS region would not shut down or cancel because the Fault Analyzer IDIDA analysis task was in an ENQ deadlock with the abending TCB, which had abended in LE code while holding the LE MSGFILE ENQ. 05. If the XCF message chain pointer is overlayed, the IDIS subsystem might get recursive abends with messages IDI0144E and IDI0124E. 06. The single quotes were not expected and caused fopen of the fault entry member to fail without an error message being issued. 07. IMS with Java and CEEPIPI might cause Fault Analyzer to add a historical CIB event incorrectly in the report. 08. Recursion of S878 conditions during Recovery Fault Recording (RFR) processing can cause more than one SDUMP to be taken for the one initial abend. 09. With XCF message delays in the IDIS subsystem, the recovery process might cause more than one fault entry to be created for the same abend job and timestamp. 10. Some Fault Analyzer analysis jobs might get IDI0095W unexpected condition, CSVQUERY error. 11. Loop in code at entry point cDDfCloseP. 12. This is the existing design.
Problem conclusion
01. DEBUGINF added to minidump during COBOL CLLE discovery. 02. The saved cursor position is now retrieved from the correct variable. 03. An additional check for a migrated data set has been added, prior to the attribute check. 04. Code has been added to break the deadlock. 05. The logic has been updated to resolve the chaining error. 06. An error message will be issued if failing to open the fault entry member and specification of single quotes around View member history file names has been supported. 07. The condition has been catered for in the code. 08. Code has been added to stop additional SDUMPs against one fault entry. 09. Code added to stop assignment of a new fault ID if one already exists for the same job and timestamp. 10. Code added to accommodate provider field request getting rc=4. 11. The code has been fixed to prevent the loop from occurring. 12. The design has been changed to allow Fast Exclude for abends in task which prohibit queueing of asynchronous exits.
Temporary fix
Comments
APAR Information
APAR number
PI08458
Reported component name
FAULT ANALYZER
Reported component ID
5655W4600
Reported release
B10
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2013-12-18
Closed date
2014-02-03
Last modified date
2014-10-08
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UI14783
Modules/Macros
HADQB10J IDIALLOC IDICAASM IDICABND IDICADYN IDICALE IDICALOC IDICASUB IDICBDB2 IDICCFND IDICISA IDICNF ***This field was truncated. To obtain the full apar record, please contact your local support center.***
Fix information
Fixed component name
FAULT ANALYZER
Fixed component ID
5655W4600
Applicable component levels
RB10 PSY UI14783
UP14/02/07 P F402
Fix is available
Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.
[{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M","label":"APARs - z\/OS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"B10","Edition":"","Line of Business":{"code":"","label":""}},{"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSXJAJ","label":"Fault Analyzer for z\/OS"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"B10","Edition":"","Line of Business":{"code":"LOB35","label":"Mainframe SW"}}]
Document Information
Modified date:
08 October 2014