ADSM-L

ADSM I/O error recovery bug (second post)

1996-08-16 09:59:00
Subject: ADSM I/O error recovery bug (second post)
From: Eric van Loon <evanloon AT KLM DOT NL>
Date: Fri, 16 Aug 1996 14:59:00 +0100
Hi fellow ADSM-ers,

I repost my following question, I haven't had any reply yet. I would especially 
like to ask somebody of ADSM Support to answer this:

I encountered a problem with ADSM/MVS:
I got an I/O error on a volume when ADSM was writing backup data. The following
messages were displayed:

ANR1411W Access mode for volume MVSADSMT.B0000019.BFS now set to
"read-only" due to write error.
ANR5208I Dismounting volume MVSADSMT.B0000019.BFS (updated).
IGD104I MVSADSMT.B0000019.BFS RETAINED, DDNAME=SYS00016
IGD104I MVSADSMT.B0000019.BFS RETAINED, DDNAME=SYS00015
ANR1181E ASTXN270: Data storage transaction 0:21637 was aborted.
ANR0532W SMNODE802: Transaction 0:21637 was aborted for session 2 for
node XIF7F11 (OS/2) .

The ANR1181E message indicates that the transaction was aborted and it
did! It resulted in an canceled backup cycle! Why? ADSM recovers fine from the
error (it sets the volume to read-only) but why doesn't ADSM just mount another
volume to continue the backup????
Has anybody seen this before or can somebody from ADSM development shed
a light on this?
Kind regards,
Eric van Loon
<Prev in Thread] Current Thread [Next in Thread>