[Search for users]
[Overall Top Noters]
[List of all Conferences]
[Download this site]
| 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 |
2206.0. "STORAGE LOAD on TL810 fails to load volume automatically" by KERNEL::TITCOMBER () Mon Mar 03 1997 10:42
Hi,
Can anybody help or shed light on the following behaviour?
OpenVMS Alpha V6.2 (on 2100), MDMS V2.8-E02, MRU V1.1
TL810 (SCSI connection)
The problem was initially seen when trying to use ABS (PAB), but we
have since narrowed it down to interaction between MDMS and the TL810
robot.
The TL810 fails to automatically load volumes into drives as requested
via STORAGE LOAD commands. AN OPCOM request to load the appropriate
volume is issued, and separate ROBOT commands are required to load the
drive with the volume.
The ROBOT commands all work OK, which implies no problem with the robot
configuration or MRU. STORAGE IMPORT and EXPORT commands work fine,
which suggests that MDMS is talking to the robot. However, the STORAGE
LOAD commands fail.
The robot and MDMS volume database have been synchronised with a
STORAGE INVENTORY command, and below is a logfile of an interactive
session with relevant comments which exhibits the incorrect behaviour.
Am I missing something obvious? Or perhaps somebody has come across
the same scenario themselves and can put me straight?
Rich
See the following extract from an interactive session displaying the
behaviour:
--------------------------------------------------------------------------------
$ robot show robot
Robot Name: GKC0: Type: SCSI
Media Robot Identifier: DEC TL810 (C) DEC1.24
Slots: 48
Drives: 4
Inports: 4
Outports: 4
Transports: 1
$ robot show drive 0-3
DRIVE: 0 Empty
DRIVE: 1 Empty
DRIVE: 2 Empty
DRIVE: 3 Empty
$ robot show slot 0-47
SLOT: 0 AFY900
SLOT: 1 AFY909
SLOT: 2 AFY894
SLOT: 3 AFY897
SLOT: 4 AFY903
SLOT: 5 AFY906
SLOT: 6 AFY891
SLOT: 7 AFY912
SLOT: 8 AFY915
SLOT: 9 AFY918
SLOT: 10 AFY921
SLOT: 11 AFY924
SLOT: 12 AFY927
SLOT: 13 AFY930
SLOT: 14 AFY933
SLOT: 15 AFY936
SLOT: 16 AFY892
SLOT: 17 AFY895
SLOT: 18 AFY898
SLOT: 19 AFY901
SLOT: 20 AFY904
SLOT: 21 AFY907
SLOT: 22 AFY910
SLOT: 23 AFY913
SLOT: 24 AFY916
SLOT: 25 AFY919
SLOT: 26 AFY922
SLOT: 27 AFY925
SLOT: 28 AFY928
SLOT: 29 AFY931
SLOT: 30 AFY934
SLOT: 31 AFY937
SLOT: 32 AFY893
SLOT: 33 AFY896
SLOT: 34 AFY899
SLOT: 35 AFY902
SLOT: 36 AFY905
SLOT: 37 AFY908
SLOT: 38 AFY911
SLOT: 39 AFY914
SLOT: 40 AFY917
SLOT: 41 AFY920
SLOT: 42 AFY923
SLOT: 43 AFY926
SLOT: 44 AFY929
SLOT: 45 AFY932
SLOT: 46 AFY935
SLOT: 47 AFY938
$ stor show vol afy938
Volume: AFY938 Owner: AWV002::SYSTEM
Format: BACKUP Brand:
Allocated: 24-FEB-1997 13:21 Scratch: 31-DEC-9999 23:59
Purchased: 24-FEB-1997 10:33 Cleaned: 24-FEB-1997 10:33
Media type: TK87K Length: 0
Mounts: 0 UIC: [SYSTEM]
Location: AWC Protection: S:RW,O:RW,G:R,W:
Notes:
Offsite: Onsite:
IO Errors: 0 Flag: FREE
Next volume: *none* Previous: *none*
Pool: Rec len: 0 Block factor: 0
Initialized: 24-FEB-1997 10:33 Density:
Slot number:
Side: Other side:
Jukebox / slot: TL810 / 47
Drive:
Volume is in a jukebox slot.
Volume is not in a magazine.
$ storage load awv002$mkc200: afy938
%%%%%%%%%%% OPCOM 28-FEB-1997 11:56:14.19 %%%%%%%%%%%
Request 86, from user SLS on AWV002
Load "AFY938" on _AWV002$MKC200:
Requested by: SYSTEM on RTA1:
Owned by: SYSTEM
Location: AWC
%SLS-I-OPRNOTIF, operator notified (28-FEB-1997 11:56:14)
%%%%%%%%%%% OPCOM 28-FEB-1997 11:56:14.19 %%%%%%%%%%%
Request 86, from user SLS on AWV002
Load "AFY938" on _AWV002$MKC200:
Requested by: SYSTEM on RTA1:
Owned by: SYSTEM
Location: AWC
%%%%%%%%%%% OPCOM 28-FEB-1997 11:56:14.19 %%%%%%%%%%%
Request 86, from user SLS on AWV002
Load "AFY938" on _AWV002$MKC200:
Requested by: SYSTEM on RTA1:
Owned by: SYSTEM
Location: AWC
-------------------------------------------------------------------------------
At this point, from another session, user issues REPLY/TO=86
-------------------------------------------------------------------------------
12:05:42.26, request 86 was completed by operator _AWV002$RTA2:
%%%%%%%%%%% OPCOM 28-FEB-1997 12:05:42.27 %%%%%%%%%%%
Request 87, from user SLS on AWV002
Assistance required for drive _AWV002$MKC200:
- %SYSTEM-MEDOFL, medium is offline
-------------------------------------------------------------------------------
The reason for this is that the tape volume is not physically in the drive, so
user issues ROBOT commands to move the appropriate volume into the drive
-------------------------------------------------------------------------------
%%%%%%%%%%% OPCOM 28-FEB-1997 12:06:47.33 %%%%%%%%%%%
Request 87 was canceled
-------------------------------------------------------------------------------
The tape volume is now in the drive, and all is OK, until the user tries to use
STORGAE UNLOAD DRIVE to get the volume from the drive back into its original
jukebox slot
-------------------------------------------------------------------------------
$ storage unload drive awv002$mkc200:
%%%%%%%%%%% OPCOM 28-FEB-1997 12:07:56.03 %%%%%%%%%%%
Message from user SLS on AWV002
Please unload drive _AWV002$MKC200:
$ stor show vol afy938
Volume: AFY938 Owner: AWV002::SYSTEM
Format: BACKUP Brand:
Allocated: 24-FEB-1997 13:21 Scratch: 31-DEC-9999 23:59
Purchased: 24-FEB-1997 10:33 Cleaned: 24-FEB-1997 10:33
Media type: TK87K Length: 0
Mounts: 1 UIC: [SYSTEM]
Location: AWC Protection: S:RW,O:RW,G:R,W:
Notes:
Offsite: Onsite:
IO Errors: 0 Flag: FREE
Next volume: *none* Previous: *none*
Pool: Rec len: 0 Block factor: 0
Initialized: 24-FEB-1997 10:33 Density:
Slot number:
Side: Other side:
Jukebox / slot: TL810 / 47
Drive: *AWV002::AWV002$MKC200
Volume is in a jukebox slot.
Volume is not in a magazine.
-------------------------------------------------------------------------------
Take a look at TAPESTART.COM to ensure everything looks as it should
-------------------------------------------------------------------------------
$ PRI := AWV002 ! Server node or cluster alias
$ DB_NODES := AWV002 ! Nodes to start database server on
$!
$!* COPYRIGHT (c) 1995 BY DIGITAL EQUIPMENT CORPORATION, MAYNARD, MASSACHUSETTS.
$!
$! MDMS_TAPESTART.COM SLS V2.8
$!
$! This file contains the symbols you define to characterize your
$! SLS configuration.
$!
$! Do NOT start SLS by executing this file.
$!
$! You MUST use the following command to start SLS:
$!
$! $ @ SYS$STARTUP:SLS$STARTUP
$!
$! -----------------------------------------------------------------------------
$!
$! SLS Base Configuration Symbols
$!
$! -----------------------------------------------------------------------------
$! Device and directory for SLS databases
$!
$ PRIMAST := SLS$ROOT:[PRIMAST]
$!
$! --------------------------
$! Timeout interval (in seconds) for client-server connection response
$!
$ NET_REQUEST_TIMEOUT = 120
$!
$! --------------------------
$! Node Name
$!
$ NODE := 'F$TRNLNM ("SYS$NODE")'
$ NODE = NODE - "::" - "_"
$!
$! --------------------------
$! Batch queue for SLS processing
$!
$ IF NODE .NES. "" .AND. F$GETSYI("CLUSTER_MEMBER","''NODE'") .EQ. "TRUE"
$ THEN BATN := SLS$'NODE' -
/ON='NODE':: -
/JOB_LIM=1 -
/BASE=4 -
/PROT=(S:RWED,O:RWED,G,W)
$ ELSE BATN := SLS$ -
/JOB_LIM=1 -
/BASE=4 -
/PROT=(S:RWED,O:RWED,G,W)
$ ENDIF
$!
$! --------------------------
$! Drive media types and densities
$!
$! During the SLS installation, a file called
$! SLS$DATAC:SLS$AUTOCONFIGURE_MEDIA_TRIPLETS.TXT was created and can be
$! included here. This file contains media triplets for the known tape
$! devices on the system from which the installation was performed. These
$! triplets can be modified as needed to fit your needs and are provided as a
$! customized template. A new template file can be generated any time after
$! the installation by executing
$! SLS$SYSTEM:SLS$AUTOCONFIGURE_MEDIA_TRIPLETS.EXE. Note that SLS$DATAC must
$! be defined for this program to complete successfully. SLS$DATAC is always
$! defined while SLS is running.
$!
$! Please see the SLS Administrator's Guide for more information on setting up
$! media triplets if you are new to SLS.
$!
$ MTYPE_1 := TK87K
$ DENS_1 := COMP
$ DRIVES_1 := AWV002$MKC200:,AWV002$MKC300:,AWV002$MKB400:,AWV002$MKB500:
$!
$ MTYPE_2 := TK87K
$ DENS_2 := NOCOMP
$ DRIVES_2 := AWV002$MKC200:,AWV002$MKC300:,AWV002$MKB400:,AWV002$MKB500:
$!
$ MTYPE_3 := TK87K
$ DENS_3 :=
$ DRIVES_3 := AWV002$MKC200:,AWV002$MKC300:,AWV002$MKB400:,AWV002$MKB500:
$!
$!
$!
$! --------------------------
$! Tape jukebox definitions - See the V2.5 documentation for full explanation
$! and proper use. These should not be confused with
$! the RV64 items below.
$!
$ TAPE_JUKEBOXES := "TL810"
$!
$ TL810:="AWV002::GKC0:,AWV002::MKC200:,AWV002::MKC300:,AWV002::MKB400:,AWV002::MKB500:"
$!
$!
$! USER_DEFINED_NAME_2 := "node::robot_name:,node::drive_1:,..."
$! ...
$! TAPE_JUKEBOXES := "user_defined_name_1,user_defined_name_2,..."
$!
$! USER_DEFINED_NAME_1 := "node::robot_name:,node::drive_1:,..."
$! USER_DEFINED_NAME_2 := "node::robot_name:,node::drive_1:,..."
$! ...
$!
$! --------------------------
$! Execution priority for SLS server and client processes
$!
$ MGRPRI := 8
$!
$! --------------------------
$! Enable or Disable broadcast of network state changes to operators
$!
$ VERBOSE = 0
$!
$! --------------------------
$! SLS software execution privileges
$!
$ PRIV_SEEANY := OPER
$ PRIV_MODANY := OPER
$ PRIV_MAXSCR := OPER
$ PRIV_LABEL := OPER
$ PRIV_CLEAN := OPER
$ PRIV_MODOWN := TMPMBX
$!
$! -----------------------------------------------------------------------------
$!
$! Operator Terminal Control
$!
$! -----------------------------------------------------------------------------
$! Basic control assignments
$!
$ CRLF[0,8] = 13
$ CRLF[8,8] = 10
$ ESC[0,8] = 27
$!
$! --------------------------
$! Load requests
$!
$ ESC_LOAD_BOLD = ESC + "[1m" + ESC + "[7w"
$ ESC_LOAD_BLNK = ESC + "[5m" + ESC + "[7w"
$ ESC_LOAD_NORM = ESC + "[m" + ESC + "[w"
$!
$! --------------------------
$! Drive allocation
$!
$ ESC_ALLOC_BOLD = ESC + "[1m"
$ ESC_ALLOC_NORM = ESC + "[m"
$!
$! --------------------------
$! Volume mount label and ring verification
$!
$ ESC_MOUNT_OPER = CRLF + ESC + "[1m" + ESC + "#6 OPERATOR:"
$ ESC_MOUNT_BOLD = ESC + "[1m"
$ ESC_MOUNT_NORM = ESC + "[m"
$!
$! -----------------------------------------------------------------------------
$!
$! SLS Volume Control Symbols
$!
$! -----------------------------------------------------------------------------
$! Name of media library location
$!
$ LOC := AWC
$!
$! --------------------------
$! Default protection of volumes
$!
$ PROTECTION = %X0133
$!
$! --------------------------
$! Default reel size for STORAGE ALLOCATE command
$!
$ ALLOCSIZE = 2400
$!
$! --------------------------
$! Name of file or device to which volume labels are written
$!
$ LBL := _NL:
$!
$! --------------------------
$! State to put deallocated volumes into
$!
$ FRESTA := TRAN
$!
$! --------------------------
$! Time that a volume stays in transition state
$!
$ TRANS_AGE := 14 0:0:0
$!
$! --------------------------
$! Default time that the scratch date is set with a STORAGE ALLOCATE
$!
$ ALLOCSCRATCH := 365 0:0:0
$!
$! --------------------------
$! Default time that the scratch date is set with a STORAGE SAVE
$!
$ BACKUPSCRATCH := 365 0:0:0
$!
$! --------------------------
$! Maximum scratch time (for a non-OPER privileged user)
$!
$ MAXSCRATCH :=
$!
$! --------------------------
$! Notify by mail when volumes have reached the scratch date
$!
$ TAPEPURGE_WORK := MAIL
$!
$! --------------------------
$! If notifying by mail, assign additional recipients of message
$!
$ TAPEPURGE_MAIL := SYSTEM
$!
$! --------------------------
$! Default name for the offsite vault
$!
$ VLT := FIRESAFE
$!
$! --------------------------
$! Drives to be controlled by SLS
$!
$ ALLDEV := AWV002$MKC200:,AWV002$MKC300:,AWV002$MKB400:,AWV002$MKB500:
$ SELDEV := AWV002$MKC200:,AWV002$MKC300:,AWV002$MKB400:,AWV002$MKB500:
$!
$! --------------------------
$! Time interval to check for freed drives
$!
$ ALLTIM := 0 0:0:30
$!
$! --------------------------
$! Operator(s) to receive volume load requests.
$!
$ TOPERS := TAPES
$!
$! --------------------------
$! STORAGE LOAD automatic load flag
$!
$ QUICKLOAD = 1
$!
$! Number of times to retry an automount (approximately 20 seconds each)
$!
$ QUICKLOAD_RETRIES = 80
$!
$! --------------------------
$! UNATTENDED BACKUPS flag
$!
$ UNATTENDED_BACKUPS = 1
$!
$! --------------------------
$! Cleanup queue and run time
$!
$ CLEANUP_Q := 'F$EXTRACT(0,F$LOCATE("/",BATN),BATN)'/AFTER=03:00
$!
$!---------------------------------------------------------------------
$!
$! The following Jukebox definitions are for RV64's only. These should
$! not be confused with the TAPE JUKEBOX items above.
$!
$!---------------------------------------------------------------------
$!
$! Default RV64 jukebox name for STORAGE IMPORT on an RV64
$!
$! JUKEBOX := JCS$DEFAULT_JUKEBOX
$!
$! --------------------------
$! Names, and lowest and highest numbered slots for each RV64 jukebox
$!
$! JUKEBOX_1_LOWER := 1
$! JUKEBOX_1_UPPER := 64
$!
$!---------------------------------------------------------------------
$!
$! Controlling Standby archiving
$!
$!---------------------------------------------------------------------
$! Log file for standby archiving
$!
$ SBARLOG := SLS$DATA:STANDBY_ARCHIVE.LOG;
$!
$! --------------------------
$! Request scan interval time
$!
$ SBARINT := 00:00:30
$!
$! --------------------------
$! Default archive class for backup screen
$!
$ SBACLAS = "FOREVER <- insert archive class here"
$!
$!---------------------------------------------------------------------
$!
$! Continue SLS boot.
$!
$ IF F$SEARCH("SLS$ROOT:[CUSTOM]LOADER.COM") .NES. ""
$ THEN
$ @SLS$ROOT:[CUSTOM]LOADER
$ ELSE
$ @SLS$ROOT:[SYSTEM]LOADER
$ ENDIF
Help!!!!!
| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 2206.1 | Is the requestor a remote process? | KIDVAX::DESOURDIS | | Mon Mar 03 1997 14:50 | 10 |
| The behavior described seems consistent with a client which does not
know it is using a jukebox allocating a tapedrive on a server which
does. STORAGE LOAD/UNLOAD works locally, but does not work for the
remote backup (or restore).
Is that something like the scenario here, or are the (failed) MDMS load
attempts and the (successful) operator tape loads/unloads all happening
on the local node?
Ron DeSourdis/CCS Storage Mgmt./297-3457
|
| 2206.2 | All on local node... | COMICS::TITCOMBER | | Tue Mar 04 1997 10:04 | 9 |
|
Everything is being done on the local node, unfortunately!
Any more ideas?
Rich
|
| 2206.3 | Change TAPE_JUEBOXES TL810 assigment to include node name prefix in MK device names | CX3PST::WSC217::SWANK | David | Tue Mar 04 1997 15:08 | 8 |
| >$ DRIVES_{1-3}:=AWV002$MKC200:,AWV002$MKC300:,AWV002$MKB400:,AWV002$MKB500:
>$ TL810:="AWV002::GKC0:,AWV002::MKC200:,AWV002::MKC300:,AWV002::MKB400:,
>AWV002::MKB500:"
Modify TL810 assigment as follows;
$ TL810:="AWV002::GKC0:,AWV002::AWV002$MKC200:,AWV002::AWV002$MKC300:,
AWV002::AWV002$MKB400:,AWV002::AWV002$MKB500:"
|