| Title: | Storage Library System |
| Moderator: | COOKIE::REUTER |
| Created: | Sun Oct 13 1991 |
| Last Modified: | Fri Jun 06 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 2270 |
| Total number of notes: | 7850 |
Any ideas why the OPCOM request doesn't timeout for STORAGE LOAD of volume alrea
dy in drive. The environment is QUICKLOAD = 0, UNATTENDED_BACKUP = 0,
local TK70 drive with the allocated volume to be used already in the drive
with ready light on steady. The following shows the sequence of events;
$ REPLY/ENABLE=TAPES
%%%%%%%%%%% OPCOM 31-JAN-1997 14:48:42.81 %%%%%%%%%%%
Operator _TUBORG$VTA136: has been enabled, username SWANK
%%%%%%%%%%% OPCOM 31-JAN-1997 14:48:42.82 %%%%%%%%%%%
Operator status for operator _TUBORG$VTA136:
TAPES
$ STORAGE ALLOCATE TK70
Volume: TK70_1 Owner: TUBORG::SWANK
.
.
.
$ STORAGE SELECT TAPE TK70_1
%DCL-I-ALLOC, _$1$MUA2: allocated
$ STORAGE LOAD TAPE TK70_1
%%%%%%%%%%% OPCOM 31-JAN-1997 14:49:40.88 %%%%%%%%%%%
Request 408, from user SLS on TUBORG
Load "TK70_1" on _$1$MUA2:
Requested by: SWANK on VTA136:
Owned by: SWANK
Location: HEADQUARTERS
%SLS-I-OPRNOTIF, operator notified (31-JAN-1997 14:49:40)
(the load command waits indefinitely...)
From another operator terminal;
$ REPLY/TO=408
From the original terminal;
14:50:47.02, request 408 was completed by operator _URQUEL$FTA1629:
$
Any ideas why the OPCOM request doesn't timeout. It seems to me that the RQ
process should see the media is available, do its label processing and cancel
the load request OPCOM message.
\David
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 2190.1 | Sounds normal | COOKIE::MCCLELLAND | Marty, SLS/MDMS Engineering | Mon Feb 10 1997 09:41 | 11 |
Hi David, Unless I'm missing something, the behavior you describe is normal. With QUICKLOAD=0, the operator must reply to the opcom request before MDMS will attempt to read the tape. With QUICKLOAD=1, MDMS initiates a periodic check of the drive to see if a volume has been loaded. Marty | |||||