PK18668: GSAM ON MULTI VOLUME DATABASE INSERTS TO THE WRONG VOLUME AFTER ABEND AND SUBSEQUENT XRST.

APAR status

• Closed as fixed if next.

Error description

• It's a GSAM file allocated with DISP=MOD in the original run
  (we want to add records to an existing file) and at start it
  was a mutivolume dataset with two DASDs (last record on 2.
  DASD).  The program logic was:
  XRST
  OPEN GSAM
  ISRT GSAM (many times)
  Abend After Abend the GSAM file is on 4 DASD volumes. The
  checkpoint data belong to data which are on the 4. volume
  Now we restarted the program from the last checkpoint using
  DISP=OLD for the GSAM file. The insert of data start at the 3.
  volume instead of 4. volume. This problem is caused by the
  volume counter in the checkpoint records from the originally
  (abended) job. If have copied the XDATA part of DSECT XLOGBKET
  information from the last two x'18'logrecords
  ........jGXXBFO01
  000000009CEECCDFF              <-- XGDSVONO=02 (must be 3)
  0C311200177726601
  ........jGXXBFO01
  000000009CEECCDFF              <-- XGDSVONO=03 (must be 4)
  00311300177726601
  IMS does not consider in this case that at starttime the dataset
  already consist of two volumes. IMS starts with 1 for XGDSVONO.
  

Local fix

• N/A
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: All IMS R810 users who use GSAM databases    *
  *                 with Multivolume datasets.                   *
  ****************************************************************
  * PROBLEM DESCRIPTION: The customer experienced the data loss  *
  *                      after an XRST on GSAM BMP using         *
  *                      multivolume datasets.                   *
  ****************************************************************
  * RECOMMENDATION: INSTALL CORRECTIVE SERVICE FOR APAR/PTF      *
  ****************************************************************
  The customer experienced data loss after an XRST on a GSAM BMP
  using multivolume datasets.  The problem happened
  before opening the output dataset in module DFSZD110 at
  label OPNOUT1.
  Before opening the output dataset the volume count for the
  current output dataset, GBDSVONO, was set to x'01' from
  GBVLSQ=x'0101' after label BL02.
  If the current output dataset is not located on the first
  volume, the volume count, GBSDSVONO, should be set correctly
  instead of being reset to x'01'.  The data loss will happen
  if there is an XRST issued later.
  

Problem conclusion

Temporary fix

Comments

• Due to the complexity of the change, the customer agreed this
  code can be delivered in a future release of IMS.  Thus this
  APAR is closed FIN and will be addressed in PTM KFN0434.
  

APAR Information

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

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

Fix information

• Fixed component name

  IMS V8

• Fixed component ID

  5655C5600

Applicable component levels

• R800 PSN

     UP