ADSM-L

Re: ADSM PRE- EMPTION of processes

1999-05-03 02:37:21
Subject: Re: ADSM PRE- EMPTION of processes
From: Russell Street <russells AT AUCKLAND.AC DOT NZ>
Date: Mon, 3 May 1999 18:37:21 +1200
> No responses have come in on my previous note regarding tapes being marked
> unavailable, but as it relates to this, I will mention it again.   If a
> process is waiting for a tape when it is pre-empted, the tape it was waiting
> for will be marked as unavailable.  If the process could be placed on hold
> instead of cancelled it would also prevent the erroneous marking of the tape
> as unavailable.

I think this one is a "feature".


If ADSM is waiting for an operator to mount a tape and the mount
request is denied, then ADSM assumes the tape to be unavailable and
marks it unavailable.

Similarly for requests for a tape to be checked into an automated library.



I just tried this on my library by asking it to audit a tape that was
not in the library.  When the

  ANR8308I 038: DLT volume BQY338 is required for use in library DLTLIB; CHECKIN
    LIBVOLUME required within 60 minutes.

messages started appearing, I cancelled the audit process and got...

  ANR2017I Administrator RSTR007 issued command: CANCEL PROCESS 229
  ANR8342I Request 038 for volume BQY338 canceled by RSTR007.
  ANR8313E Volume BQY338 is not present in library DLTLIB.
  ANR1402W Mount request denied for volume BQY338 - volume unavailable.
  ANR0940I Cancel request accepted for process 229.
  ANR1410W Access mode for volume BQY338 now set to "unavailable".
  ANR2321W Audit volume process terminated for volume BQY338 - storage media
    inaccessible.
  ANR0985I Process 229 for AUDIT VOLUME (INSPECT ONLY) running in the BACKGROUND
    completed with completion state FAILURE at 06:26:26 PM.

and the volume is now unavailable.


The logic seems to be that when the process is cancelled the
request(s) tied to that process are cancelled as well.  However,
cancelling a request tells ADSM the volume is not available.  ADSM
then marks the volume as unavailable.

It seems that ADSM needs to be a more discerning.


Have you tried raising this with IBM Support?


Russell
<Prev in Thread] Current Thread [Next in Thread>