PK66252: FABC3798E - AREA INFORMATION RECORD FOR AREA 4 (AREANAME: PXDBF04 ) NOT FOUND RECEIVED DURING RELOAD 08/05/20 PTF PECHANGE

APAR status

• Closed as program error.

Error description

• The customer unloaded datasets with RMODTYPE=S and restructure
  mode. The segments in the old area3 were randomized to the
  new area3 and area4.
  When the USR file was reloaded, the following message was
  received and the JOB abended.
  FABC3798E - AREA INFORMATION RECORD FOR AREA 4 (AREANAME:
  PXDBF04 ) NOT FOUND
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: All DEDB Unload/Reload users of              *
  *                 High Performance Fast Path Utilities         *
  *                 FP Basic Tools Version 3 Release 1           *
  *                 (FMID: H31A310).                             *
  ****************************************************************
  * PROBLEM DESCRIPTION: Reloading the unloaded file that was    *
  *                      produced by unload with RMODTYPE=S and  *
  *                      restructure mode got U3798 abend with   *
  *                      FABC3798E message.                      *
  ****************************************************************
  * RECOMMENDATION: Apply the maintenance for this APAR.         *
  ****************************************************************
  The customer unloaded ADS with RMODTYPE=S and restructure mode.
  The records in the old area3 were randomized to the new area3
  and area4.
  The unload program FABCUR1 issued FABC0185I message indicating
  that some records in the input area3 was randomized to
  different area.
  When the unloaded file was reloaded, the following message was
  received and the JOB abended.
  FABC3798E - AREA INFORMATION RECORD FOR AREA 4 (AREANAME:
  PXDBF04 ) NOT FOUND
  This message was introduced by the APAR PK42190.
  

Problem conclusion

• Unload with RMODTYPE=S and restructure mode issued FABC0185I
  message when the randomizer randomized a root segment to
  a different    area from the original one. The message is
  as follows:
    FABC0185I RMODTYPE=S BUT RANDOMIZED TO ANOTHER AREA
  Only one FABC0185I message is issued per input area even if more
  than one root segment are randomized to different areas.
  
  After issuing this message, unload program destroyed the
  RAP RBA value of the only one databese record in the area to be
  reloaded corresponding to the following 3rd condition.
  
  The condition of RAP RBA destruction:
   1.A root segment is randomized to a different area.
     New RAP RBA is calculated and saved in the register 5.
     New area number and the RAP RBA are set to the unloaded
     segment record buffer.
   2.FABC0185I message is issued.
     This process uses register 5 as a work one.
     Thus content of the register 5 is destroyed.
   3.If the root segment randomized to an area as a first record
     of the area, then  Area information record (AIR) is
     produced and written to the output unloaded file.
     Writing the AIR uses same unloaded segment record buffer.
     Then RAP RBA field in the record buffer is rebuild for
     the unloaded root segment record from the register 5.
     Thus RAP RBA value of the unloaded segment record is
     destroyed.
  
  If all DB records are randomized to the original area, then
  above 2 and 3 step are not processed so correct RAP RBA
  is kept.
  Even if a DB record is randomized to a different area and
  FABC0185I message is issued, if some DB records are already
  written to the area, the step 3    is not performed and correct
  RAP RBA is kept.
  
  Reload with the USR including the destroyed RAP RBA processes
  as follows:
  Reload compares the destroyed RAP RBA to the CI boundary value
  of reloaded area to determine the RAP RBA of reloaded area.
  
  1. When the destroyed RAP RBA does not match CI boundary value,
     reload processing of this area finishes,
     and the root segment record that has destroyed RAP RBA and
     subsequent segment records are remained for the next area.
     Reload process expected the AIR of the next area, but cannot
     find the AIR and abends with U3789 as no AIR for reloaded
     area.
  
  2. When the destroyed RAP RBA matches CI boundary value,
     reload processing inserts the segment into incorrect
     RAP RBA CI.
     This DB record can not be accessed by the on-line application
     when it is accessed with key-specified GU call because it is
     stored in the in correct RAP CI.
  
  FABCUR1U has been modified to change the base register R5 for
  FABC0185I message area into R14.
  
  Because this problem is due to a change made by APAR PK42190,
  its PTF UK23743 has been marked PE.
  310Y
  FABCUR1U
  

Temporary fix

• *********
  * HIPER *
  *********
  

Comments

APAR Information

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

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

  UK36645

Modules/Macros

•    FABCUR1U
  

Fix information

• Fixed component name

  IMS HP FP UTILI

• Fixed component ID

  5655K9400

Applicable component levels

• R310 PSY UK36645

     UP08/05/23 P F805 «