ADSM-L

Re: Had an interesting problem crop up on our 3584 last week

2006-09-25 16:10:18
Subject: Re: Had an interesting problem crop up on our 3584 last week
From: Zoltan Forray/AC/VCU <zforray AT VCU DOT EDU>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Mon, 25 Sep 2006 16:09:05 -0400
Funny you should mention this.

We have a 3494 and I always wondered why IBM changed the way the I/O
locking process works.

When we first got our 3494 in 1996, the I/O door was locked for the
duration of the checkout process.  Then, somewhere along the way, the LM
code got updated and the door constantly locks and unlocks between each
ejection and yes, our operators have grabbed and opened the door between
ejects, thinking it was finished, thus causing a failure/intervention.

I notice the 3582 libraries do the same and we have farged them up, as
well.

Anyone from IBM care to explain this logic/process ?




"Kauffman, Tom" <KauffmanT AT NIBCO DOT COM>
Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
09/25/2006 03:58 PM
Please respond to
"ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>


To
ADSM-L AT VM.MARIST DOT EDU
cc

Subject
[ADSM-L] Had an interesting problem crop up on our 3584 last week






It seems that it is possible to open the I/O port door as the library is
performing a lock function on the door. This left the door open and
unable to close because the lock pin (or tab, or whatever) was in the
way.

This was during a checkout script run, and our tape grabber seems to
have been in a bit of a hurry this time.

So there we sat, with the ANR8387I message coming up about once per
minute and all library functions at a standstill (my assumption is that
the gripper had its mouth full -- I didn't check when I came in). Once I
cleared the tab and closed the door, everything ran as it should, just
late.

I'm changing the checkout script . . .

Tom Kauffman
NIBCO, Inc
CONFIDENTIALITY NOTICE:  This email and any attachments are for the
exclusive and confidential use of the intended recipient.  If you are not
the intended recipient, please do not read, distribute or take action in
reliance upon this message. If you have received this in error, please
notify us immediately by return email and promptly delete this message
and its attachments from your computer system. We do not waive
attorney-client or work product privilege by the transmission of this
message.

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