PK19084: FPB DEDB PC DOES NOT REPORT THE DIFFERENCE BETWEEN DATA BLOCK IDIN IOVF SPACE MAP AND THE ONE IN IOVF DATA CI.

APAR status

• Closed as program error.

Error description

• FPB DEDB PC does not report the difference between DATA BLOCK ID
  in IOVF SPACE MAP and the one in IOVF DATA CI.
  This is a forward fit of FPB V12 APAR PK11467.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: All DEDB Pointer Checker user of High        *
  *                 Performance Fast Path Utilities FP Basic     *
  *                 Tools Version 2 Release 1 (FMID: H31A210).   *
  ****************************************************************
  * PROBLEM DESCRIPTION: Forward Fit APAR of FPB V1R2 PK11467.   *
  *                      FPB DEDBPC does not report the          *
  *                      difference between data block ID in     *
  *                      IOVF space map and the one in IOVF DATA *
  *                      CI.                                     *
  ****************************************************************
  * RECOMMENDATION: Apply the maintenance for this APAR.         *
  ****************************************************************
  Forward Fit APAR of FPB V1R2 PK11467.
  This APAR solves the following 2 problems.
  
  1. FPB DEDBPC does not report the difference
     between data block ID in IOVF space map and the one
     in IOVF DATA CI.
  
  2. FPB DEDBPC does not report the incorrect value of
     each data block ID in IOVF space map CI.
  

Problem conclusion

• 1. When Pointer Checker FABADA1 detects the difference
     between data block ID in IOVF space map and the one
     in IOVF DATA CI, a new "FABA0147I" message is issued.
  
     Prior to APAR PQ38142, when Pointer Checker FABADA1 detected
     the difference between data block ID in IOVF space map and
     the one in IOVF DATA CI, an "FABA0147W" message was issued.
     This warning message reported the difference between
     data block ID in IOVF space map and the one in IOVF DATA CI.
     But the difference may be valid in case that the control
     word of data ci has x'00' and the space-map has x'80'
     by IMS/ESA V3 FP REORG UTILITY.
     Then, Pointer Checker FABADA1 was modified not to report
     the difference, and this old "FABA0147W" message was deleted
     with APAR PQ38142.
  
     Pointer Checker FABADA1 is modified to report the difference
     by a new "FABA0147I" message.
     The difference may occurs not only in the case brought about
     by IMS/ESA V3 FP REORG UTILITY, but also in other cases.
     So Pointer Checker FABADA1 reports the difference not as
     warnings but as information.
  
  2. When the first byte of data block ID in IOVF space map CI
     is neither X'80' nor X'40', a new "FABA0167E" message is
     issued. The first byte of data block ID in IOVF space map CI
     must be X'80' or X'40'. The other values are not correct.
  
  ----------------------------------------------------------------
  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 added as follows:
  
  Appendix N. FPB - Messages and Codes
  
   FABA Messages
    -------------------------------------------------------------
     FABA0147I IOVF CONTROL WORD DISCREPANCY FOUND
     - SPACE MAP CI RBA: aaaaaaaa CONTROL WORD: bbbbbbbb
     OFFSET: cccc
     - IOVF DATA CI RBA: dddddddd CONTROL WORD: eeeeeeee
  
     Explanation: the first byte of a control word value bbbbbbbb
     in the space map CI at RBA aaaaaaaa OFFSET cccc is different
     from that of the one eeeeeeee in IOVF DATA CI at RBA:
     dddddddd.
  
     System Action: Program FABADA1 continues processing.
  
     Programmer Response: Confirm the status of the first byte
     of control word value (DBLKBTUI).
  
     - DBLKBTUI in the space map CI at RBA aaaaaaaa OFFSET cccc
     is X'80', and DBLKBTUI in the IOVF DATA CI at RBA ddddddd
     is X'00', then no problem exists.
     - DBLKBTUI in the space map CI at RBA aaaaaaaa OFFSET cccc
     is X'80', and DBLKBTUI in the IOVF DATA CI at RBA ddddddd
     is not X'40', then IMS can insert segments into the IOVF
     DATA CI. Please check them for data integrity.
     - It is recommended to check them for data integrity.
  
    -------------------------------------------------------------
     FABA0167E SPACE MAP AT RBA: xxxxxxxx OFFSET: yyyy HAS
     INCORRECT CONTROL WORD VALUE: zzzzzzzz
  
     Explanation: the first byte of a control word value zzzzzzzz
     in the CI at RBA xxxxxxxx OFFSET yyyy is incorrect.
     Expected data value is X'40' which means 'Allocated',
     or X'80' which means 'Free'.
  
     System Action: FABADA1 sets an end-of-job return code of 99,
     and continues processing.
  
     Programmer Response: Correct the errors, and rerun the job.
  
    -------------------------------------------------------------
  
  210Y
  FABABMAP
  FABADBCI
  

Temporary fix

Comments

APAR Information

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

  PK11467

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

  UK11644

Modules/Macros

•    FABABMAP FABADBCI
  

Fix information

• Fixed component name

  IMS HP FP UTILI

• Fixed component ID

  5655K9400

Applicable component levels

• R210 PSY UK11644

     UP06/02/11 P F602