PM96424: MISCELLANEOUS BUG FIXES

Obtain the fix for this APAR.

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. Debug Tool analysis of HLASM might  *
  *                          fail to display some field data.    *
  *                          APAR PM97969                        *
  *                      02. Fault Analyzer report has 'no data' *
  *                          in the event list.                  *
  *                          APAR PM95415                        *
  *                      03. The user is analyzing a CICS SDUMP  *
  *                          and is seeing an incorrect task     *
  *                          state in the DS Domain Task Summary *
  *                          panel. Task State is shown as "R"   *
  *                          when it should be "A".              *
  *                          APAR PM97970                        *
  *                      04. Cursor is placed on the Fault Entry *
  *                          List display command line after     *
  *                          deletion of fault entry if option   *
  *                          to confirm deletion is in effect.   *
  *                          APAR PM97971                        *
  *                      05. Fault entry duplicate count on the  *
  *                          Fault Entry List display shows a    *
  *                          negative or decreasing value.       *
  *                          APAR PM96377                        *
  *                      06. Abend S282-20 when exiting          *
  *                          interactive MVS dump analysis.      *
  *                          APAR PM97972                        *
  *                      07. IDI0047S from Fault Analyzer in     *
  *                          MAPLMOD processing.                 *
  *                          APAR PM97973                        *
  *                      08. Fault Analyzer IDIS subsystem loop  *
  *                          with IDI0131W message and high CPU. *
  *                          APAR PM97481                        *
  *                      09. Message "ERROR: IactLEabend() can't *
  *                          be invoked from IDIPDDIR!" issued   *
  *                          when looking up abend code          *
  *                          explanation from Fault Entry List   *
  *                          display.                            *
  *                          APAR PM97974                        *
  ****************************************************************
  * RECOMMENDATION: Apply the provided PTF.                      *
  ****************************************************************
  01. The use of USING (Dsect,DsectEnd),R10 form rather than
      traditional USING Dsect,R10 will cause a problem with
      EQALANGX respecify record data.
  02. If the MVS RB chain can not be traced because of a missing
      page in the minidump, the available list of events was not
      displayed.
  03. FA CICS SDUMP analysis is interpreting a CICS status byte
      incorrectly.
  04. The original cursor position is not saved prior to
      displaying the delete confirmation panel.
  05. The duplicate count is held in a signed halfword which is
      displayed as a negative value if more than 32,767 duplicates
      have occurred, or a decreasing value if more than 65,535
      duplicates have occurred.
  06. The Fault Analyzer ISPF interface was invoked with a
      history file name set to a non-existing data set.
  07. Intermittent abend S0C4 in Fault Analyzer IDIDA MAPLMOD
      causing IDI0047S and an RFR dump to be created for recovery
      processing of the fault entry.
  08. Under some XCF recovery conditions, the IDIS subsystem might
      loop causing high CPU usage.
  09. This is a diagnostic message that was incorrectly left as a
      message to the user rather than being written to a trace
      data set.
  

Problem conclusion

• 01. The code has been updated to correct the problem.
  02. Code updated to better handle the next RB not being
      available.
  03. IDIECDS has been changed to interpret the task status byte
      correctly.
  04. The cursor is now positioned correctly.
  05. The duplicate count field is treated as unsigned, which
      allows for up to 65,535 duplicates. Once this limit is
      reached, the count will remain unchanged at its maximum
      instead of wrapping.
  06. A check has been added for the existence of the target
      history file to prevent the abend S282-20 from occurring.
  07. The MAPLMOD processing updated to correctly test the return
      from GETDSVOL processing.
  08. Code changed to handle the potential XCF recovery timing
      condition.
  09. The message is no longer displayed to the user and is only
      written to the trace data set.
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

  UK98099

Modules/Macros

• HADQB10J IDIALLOC IDICAASM IDICABND IDICADYN IDICALE  IDICALOC
  IDICASUB IDICCFND IDICISA  IDICNF00 IDICNO
  
  ***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 UK98099

     UP13/10/03 P F310

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.