PK14413: SDEP POINTER ERRORS ARE BEING DETECTED BY FABADA1, BUT NOT BY FABADA3 WITH TYPES RPT AND PTRALL

APAR status

• Closed as program error.

Error description

• SDEP pointer errors are being detected by the DEDB Pointer
  Checker FABADA1, but not by FABADA3 when TYPRUN=RPT or
  TYPRUN=PTRALL are specified.
  In this case FABADA3 reports the unexpected message of:
  FABA0302I - FABADA3 ENDED NORMALLY - NO POINTER ERRORS DETECTED
  
  This is a forward fit of FPB APAR PK09593 and PK12367.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: All DEDB Pointer Checker users of High       *
  *                 Performance Fast Path Utilities FP Basic     *
  *                 Tools Version 2 Release 1 (FMID: H31A210).   *
  ****************************************************************
  * PROBLEM DESCRIPTION: Forward Fit APAR of FPB V1R2 PK09593    *
  *                      and PK12367:                            *
  *                      SDEP pointer errors are being detected  *
  *                      by the DEDB Pointer Checker FABADA1,    *
  *                      but not by FABADA3 when TYPRUN=RPT or   *
  *                      TYPRUN=PTRALL are specified.            *
  ****************************************************************
  * RECOMMENDATION: Apply the maintenance for this APAR.         *
  ****************************************************************
  This APAR solves the following 2 problems.
  
  1. SDEP pointer errors are being detected by the DEDB Pointer
     Checker FABADA1, but not by the succeeding FABADA3 when
     TYPRUN=RPT or TYPRUN=PTRALL are specified.
     In this case FABADA3 reports the unexpected message of:
     FABA0302I - FABADA3 ENDED NORMALLY - NO POINTER ERRORS
     DETECTED
     The succeeding FABADA3 should detect SDEP pointer errors as
     well.
  
     - Pointer Checker FABADA1 generates a SDEP pointer
       record (4,P) per SDEP pointer, and a SDEP segment record
       (4,S) per SDEP segment.
       Pointer Checker FABADA3 checks consistency of these
       records and reports if errors exist or not.
       When the RBA value of SDEP pointer (SPTF/SPCF) indicates
       outside SDEP area and the pointed segment does not exist,
       the error message is detected but neither a SDEP pointer
       record or a SDEP segment record are generated by FABADA1.
       As a result, Pointer Checker FABADA3 can't report
       any errors.
  
  2. Pointer Checker FABADA1 does not check the cycle count value
     of SPTF and SPCF.
  

Problem conclusion

• 1. When Pointer Checker FABADA1 detects such invalid pointer
     value, then generates SDEP pointer record (4,P) including
     erroneous pointer value. In this case, a new "FABA0159E"
     message is issued and SDEP checksum validation is bypassed
     subsequently.
     Pointer Checker FABADA3 verifies these records including
     the erroneous 4,P records and issue "FABA0329E" message.
  
  2. When Pointer Checker FABADA1 detects incorrect cycle count
     value, then issues a new "FABA0158E" message,
     generates a CI snap and SDEP pointer record (4,P)
     including erroneous pointer value.
     In this case, "FABA0159E" message is issued and
     SDEP checksum validation is bypassed.
     Pointer Checker FABADA3 verifies these records including
     the erroneous 4,P records and issue "FABA0329E" message.
  
  ----------------------------------------------------------------
  Documentation Changes:
  The IMS High Performance Fast Path Utilities for z/OS
  User's Guide Volume 2: Fast Path Basic Tools Version 2 Release 1
  (SC18-9238-00) should be changed as follows:
  
  Appendix U. Fast Path Basic Tools - Messages and Codes
  
   FABA Messages
    -------------------------------------------------------------
     FABA0158E SEGMENT AT RBA: xxxxxxxx
     (SEGCD: yy) HAS INVALID SDEP CYCLE COUNT VALUE
  
     Explanation: The SDEP cycle count value contained
     in the segment at RBA xxxxxxxx is incorrect.
  
     System Action: Program FABADA1 sets an end-of-job return
     code of 99, and continues processing.
  
     Programmer Response: See  "Integrity Verification"
     on page 14. Correct the error and rerun the job,
     or continue with the execution of FABADA3, FABADA4,
     and FABADA5 as desired.
  
    -------------------------------------------------------------
     FABA0159E INVALID VALUE IN "SPCF"/"SPTF" - SDEP
     CHECKSUM VALIDATION PROCESSING BYPASSED FOR AREA: areaname
  
     Explanation: Program FABADA1 encountered an error
     while validating the "SPCF" and the "SPTF"
     with the specified area.
  
     System Action: Program FABADA1 stops SDEP checksum
     validation processing, sets an end-of-job return code of 99,
     and continues processing.
  
     Programmer Response: Correct the error and rerun the job,
     or continue with the execution of FABADA3, FABADA4 and
     FABADA5 as desired.
  
    -------------------------------------------------------------
  
  210Y
  DA1WRK10
  DA3SDEP0
  DA3WRK10
  FABACKCC
  FABACNVT
  FABADA1
  FABADA3
  FABADBCI
  FABADMAC
  FABAFDAR
  FABAINIT
  FABAMDAR
  FABASDEP
  FABAUMSG
  FABA1SB0
  

Temporary fix

Comments

APAR Information

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

  PK09593

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

  UK09012

Modules/Macros

•    DA1WRK10 DA3SDEP0 DA3WRK10 FABACKCC FABACNVT
  FABADA1  FABADA3  FABADBCI FABADMAC FABAFDAR FABAINIT FABAMDAR
  FABASDEP FABAUMSG FABA1SB0
  

Fix information

• Fixed component name

  IMS HP FP UTILI

• Fixed component ID

  5655K9400

Applicable component levels

• R210 PSY UK09012

     UP05/11/15 P F511