beeeeeeeeen meselaaaa uçarım meselaaaaaaa

oam had to be stopped when the system experienced a buffer
shortage that resulted from a flood of cbr6416i messages to the
syslog and oam job log. for osreq retrieves, there is no
protection against repeating msgcbr6416i messages that can
result from either bad tape media or other h/w problems. we
need a safety mechanism for oam object tape that is similar to
oam's osmc utility which marks a volume unreadable and
stops the storage group cycle after three repeating errors.
example message:
cbr6416i oam read request failed for ddname=ddname on tape
volume volser for collection collect-name and object
object-name. {oam | point | note | unknown} return
code=return-code, reason code=reason-code.
local fix
use the following command to manually mark a problem volume as
not readable:
f oam,update,vol,volser,readable,n
the application that invokes the osreq retrieve will still get
a failing return and reason code, but no cbr6416i will be
issued. if the tape volume really is bad, use oam's recovery
utility to recreate the volume.
problem summary
• **
• users affected: oam object tape customers *
• **
• problem description: problems are occurring on tape volumes *
• trying to use point or note to position *
• the tape. these problems are causing *
• oam error msg cbr6416i to be issued. *
• the end user continued to issue *
• thousands (200,000) of reads which all *
• were failing, oam issued 200,000+ *
• cbr6416i error msgs which flooded the *
• consoles and could have caused the *
• system to have to be ipl'd *
• customer had to cancel oam to stop the *
• messages. *
• **
• recommendation: *
• **
problem conclusion
oam has been modified that while a tape volume is mounted, if
it gets "3" read errors and at least "3" cbr6416i error msgs,
the tape volume will be now be marked non-readable. a new msg
cbr6428i will be issued to indicate to the customer that there
is a problem reading this tape volume and that it has been
marked non-readable. customer needs to investigate the tape
volume and possibly the tape drive to determine the severity
of the problem. if the volume is okay, customer can then use
the oam update operator command to mark the volume readable
again.
f oam,update,volume,volser,readable,y
temporary fix
• **
• hiper *
• **
comments
apar information
apar numberoa09800
reported component namedfsms/mvs oam
reported component id5695df180
reported release1g0
statusclosed per
penope
hiperyeshiper
special attentionnospecatt
submitted date2004-11-08
closed date2004-12-01
last modified date2005-01-05
apar is sysrouted from one or more of the following:
apar is sysrouted to one or more of the following: ua15551 ua15552 ua15553
modules/macros
cbrmsg6 cbrmtvcb cbrptvcb cbrrtt cbrsmes6
cbrsmgm6 cbrsmgu6 cbrtvcb
fix information
fixed component namedfsms/mvs oam
fixed component id5695df180
applicable component levels
r1g0 psy ua15551 up04/12/08 p f412
r1h0 psy ua15552 up04/12/08 p f412
r1j0 psy ua15553 up04/12/08 p f412
fix is available
select the ptf appropriate for your component level. you will be required to sign in. distribution on physical media is not available in all countries.
copyright and trademark information
ibm, the ibm logo and ibm.com are trademarks of international business machines corp., registered in many jurisdictions worldwide. other product and service names might be trademarks of ibm or other companies. a current list of ibm trademarks is available on the web at "copyright and trademark information" at http://www.ibm.com/legal/copytrade.shtml .
rate this page
please take a moment to complete this form to help us better serve you.
this material provides me with the information i need.
strongly agree
agree
neutral
disagree
strongly disagree
this material is clear and easy to understand.
strongly agree
agree
neutral
disagree
strongly disagree
did the information help you to achieve your goal?
yes no don't know
what updates, improvements, or related information would you like to see in this document?

your response will be used to improve our document content. requests for assistance, if applicable, should be submitted through your normal support channel as we cannot respond from this site.
input the verification number to submit feedback:
verification number:91755