On Mon, 28 Apr 2008 14:09:55 -0500, Mark Zelden <[EMAIL PROTECTED]>
wrote:

>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 ............
>

Well...  not only did IBM forget to roll this fix to z/OS 1.9  they also did not
roll it up to z/OS 1.10 when they opened OA24116.   So there is a new
APAR for z/OS 1.10 for this same problem - OA26791.   Geeshh! 

  APAR Identifier ...... OA26791      Last Changed ........ 08/10/14
  I/O ERROR ON READ. MM ERROR CODES=X'00140408' DB2 REASON CODE=
  X'00C200A4'. REPRO RETURNS RPLFDBWD = X'21080018'
 
  Symptom ...... MS 21080018          Status ........... OPEN
  Severity ................... 3      Date Closed .........
  Component .......... 5695DF106      Duplicate of ........
  Reported Release ......... A10      Fixed Release ............
  Component Name DFSMS VSAM MEDA      Special Notice
  Current Target Date ..09/01/27      Flags
  SCP ...................
  Platform ............
 
  Status Detail: DESIGN/CODE - APAR solution is being designed
                               and coded.
 
  PE PTF List:
 
  PTF List:
 
 
  Parent APAR:    OA24116
  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.


--
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