Differences

This shows you the differences between two versions of the page.

--- checkpoint:scan_to_slot [2019/03/25 02:54] – Scott Cunliffe
+++ checkpoint:scan_to_slot [2025/01/21 22:07] (current) – external edit 127.0.0.1
@@ Line 7: / Line 7: @@
 ===== Scanning Volumes To Slots Using Zone, Slot and Volume Barcodes =====
-This method relies on both the zones and Slots being barcoded (further information on printing barcodes can be found [[checkpoint:print_barcodes|here]]).  Slotting on the [[object:repository|Repository]] also need to be disabled if you have the Slotting allocation script being run by the scheduler or volumes will be automatically allocated a Slot based on the Slotting mode of that [[object:repository|Repository]].
+This method relies on both the zones and Slots being Barcoded (further information on printing Barcodes can be found [[checkpoint:print_barcodes|here]]).  Slotting on the [[object:repository|Repository]] also need to be disabled if you have the Slotting allocation script being run by the scheduler or volumes will be automatically allocated a Slot based on the Slotting mode of that [[object:repository|Repository]].
-From the customer tree right click the required customer/s and select ''Add'' to load volumes into the **To Scan** window.
+From the customer tree right-click the required customer/s and select ''Add'' to load volumes into the **To Scan** window.
 {{:checkpoint:checkpoint_add_volumes.png}}
@@ Line 36: / Line 36: @@
 Using this method enables you to control the Slot allocation order of [[object:volume|Volumes]], based on the order you scan them in.
-This process requires the **Do not slot** option to be enabled for the Target [[object:repository|Repository]] and the executable [[cli:tmss10slotallocation|TMSS10SlotAllocation]] to be run either manually after scanning [[object:volume|Volumes]] or scheduled on a regular basis so that it runs after scanning to set Slot allocation flag and before scanning in to the Slots to confirm.
+This process requires the **Do not slot** option to be enabled for the Target [[object:repository|Repository]] and the executable [[cli:tmss10slotallocation|TMSS10SlotAllocation]] to be run either manually after scanning [[object:volume|Volumes]] or scheduled on a regular basis so that it runs after scanning to set Slot allocation [[common:volume_flags|Flag]] and before scanning in to the Slots to confirm.
-As [[object:volume|Volumes]] are placed in a move to the [[object:repository|Repository]], a **t** flag will be assigned.  This **t** flag stops the slotting.bat script automatically assigning a Slot.
+As [[object:volume|Volumes]] are placed in a move to the [[object:repository|Repository]], a **t** [[common:volume_flags|Flag]] will be assigned.  This **t** [[common:volume_flags|Flag]] stops the slotting.bat script automatically assigning a Slot.
 {{:master:tapemaster_volume_t_flag.png}}
@@ Line 44: / Line 44: @@
 When the [[object:volume|Volumes]] arrive at the [[object:repository|Repository]], after loading the required [[object:media|Media]] into the **To Scan** window, selecting ''Process''->''Special Operations''->''Scan to Set Slot Allocation Flag'' to open the **Scan** window.
-Scan the [[object:volume|Volumes]] in the order you want the Slots to be assigned and, when all [[object:volume|Volumes]] have been scanned, close the **Scan** window. Select ''Process''->''Update Server'' to update the Slot allocation flags on the scanned [[object:volume|Volumes]].
+Scan the [[object:volume|Volumes]] in the order you want the Slots to be assigned and, when all [[object:volume|Volumes]] have been scanned, close the **Scan** window. Select ''Process''->''Update Server'' to update the Slot allocation [[common:volume_flags|Flag]]s on the scanned [[object:volume|Volumes]].