As luck would have it, I just found out about APAR OA24116 today.   I ran
into this problem a year ago during our z/OS 1.8 roll out.  Apparently OA16372
was not sysrouted to z/OS 1.9.   I know some other folks ran into this problem
also, hence the post.  Search the archives for OA16372 if interested in more
details.  

We are just getting ready to roll out z/OS 1.9 to the same environment I ran 
into this problem on last year at this same time.  Talk about timing... 


  APAR Identifier ...... OA24116      Last Changed ........ 08/04/02
  I/O ERROR ON READ. MM ERROR CODES=X'00140408' DB2 REASON CODE=
  X'00C200A4'. REPRO RETURNS RPLFDBWD = X'21080018'
 
  Symptom ...... MS 21080018          Status ........... CLOSED  PER
  Severity ................... 3      Date Closed ......... 08/04/02
  Component .......... 5695DF106      Duplicate of ........
  Reported Release ......... 190      Fixed Release ............ 999
  Component Name DFSMS VSAM MEDA      Special Notice
  Current Target Date ..08/06/04      Flags
  SCP ...................
  Platform ............
 
  Status Detail: TESTPACKAGING - Packaged solution is being tested.
 
  PE PTF List:
 
  PTF List:
  Release 190   : PTF not available yet
 
 
  Parent APAR:    OA16372
  Child APAR list:
 
 
  ERROR DESCRIPTION:
  Volume serials out of order.  This results in I/O errors on
  read.
  MM ERROR CODES=X'00140408'
  DB2 REASON CODE=X'00C200A4'.
  REPRO returns
  IDC3351I ** VSAM I/O RETURN CODE IS 24 - RPLFDBWD = X'21080018'
 
 
  LOCAL FIX:
  DELETE NOSCRATCH and DEFINE RECATALOG with the volumes
  specified in the correct order.  The LISTCAT for the data set
  is needed before doing the DELETE so the correct order for the
  volumes can be determined.
  Please see informational APAR II14289 which documents an
  available as is tool that will help identify data sets with
  volumes out of order.  The tool scans specified catalogs.
  It will provide the correct volume sequence for data sets.
  ADDITIONAL INFORMATION:
  Out of sequence volumes could have existed prior to R1K0,
  but the code at prior levels to R1K0 did not expose this
  error.
 
 
  PROBLEM SUMMARY:
  ****************************************************************
  * USERS AFFECTED: All HDZ11K0 users and above of VSAM reading  *
  *                 or writing to a multi-volume VSAM data       *
  *                 set where the volumes have been recataloged  *
  *                 in adifferent order than originally extended *
  *                 to.                                          *
  ****************************************************************
  * PROBLEM DESCRIPTION: VSAM GET/PUT requests fail with         *
  *                      RC=8RPLFDBK X'21080018' (media manager  *
  *                      error x'00140408') when accessing a     *
  *                      VASM data set and the data set has      *
  *                      more than 3 volumes which have been     *
  *                      recataloged out of the original         *
  *                      extent order.                           *
  *                                                              *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  VSAM Open is modified to detect Volumes out of order
  condition.  IEC161I 071(SFI)-026 informational msesage will be
  issued.  User should put volumes back in the  original order
  before proceeding.
 
 
  PROBLEM CONCLUSION:
  For out of sequence volumes, the following 2 errors will no
  longer be given:
 
  Media Manager ERROR CODES=X'00140408'
  Management RPLFDBWD = X'21080018'   However,
  the user should take measures to correct the out of sequence
  volumes as indicated by message IEC161I 'action required'.
 
  DELETE NOSCRATCH and DEFINE RECATALOG with the volumes
  specified in the correct order.  The LISTCAT for the data set
  is needed before doing the DELETE so the correct order for the
  volumes can be determined.
  Please see informational APAR II14289 which documents an
  available as is tool that will help identify data sets with
  volumes out of order.  The tool scans specified catalogs.
  It will provide the correct volume sequence for data sets.
  ADDITIONAL INFORMATION:
  Out of sequence volumes could have existed prior to R1K0,
  but the code at prior levels to R1K0 did not expose this
  error.
 

Mark
--
Mark Zelden
Sr. Software and Systems Architect - z/OS Team Lead
Zurich North America / Farmers Insurance Group - ZFUS G-ITO
mailto:[EMAIL PROTECTED]
z/OS Systems Programming expert at http://expertanswercenter.techtarget.com/
Mark's MVS Utilities: http://home.flash.net/~mzelden/mvsutil.html

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

Reply via email to