You can use media ID generation rules on your vm.conf file as follows:
The media ID generation rule has the following syntax:
MEDIA_ID_BARCODE_CHARS <robot_number> <barcode_length>
where robot_number is the robot number, barcode_length is the number of
characters in the media's barcode format,
c1 is the first character of the Media ID
c2 is the second character of the Media ID
c3 is the third character of the Media ID
c4 is the fourth character of the Media ID
c5 is the fifth character of the Media ID
c6 is the sixth character of the Media ID
c1-c6 can specify a character from the media barcode or specify a fixed
character by prefixing the character with a "#".
For example, the rule:
MEDIA_ID_BARCODE_CHARS 0 8 #N:1:3:4:5:6
generates media IDs for robot 0 using the character N and the 1st, 3rd,
4th-6th characters of the 8 character barcode, and for the barcode, 123456L1
generates media ID N13456.
MEDIA_ID_BARCODE_CHARS 0 8 1:2:3:4:5:6
generates media IDs for robot 0 using the 1st-6th characters of the 8
character barcode, and for the barcode 006498L2 generates media ID 006498.
DATASEC Software GmbH
"Bob Van Cleef" <vancleef AT garg DOT com> wrote:
> Another quick question:
> My predecessor did not use barcode labels, which is obviously ungood.
> So, I ordered a bunch: quoted as "LTO 100GB Ultrium Vert"
> They use A00002 format with a bottom square containing an L1.
> Unfortunately, when scanned by the robot (Sun StorEdge L25) they
> are read as A00002L1, which is then truncated by NetBackup as
> Is this typical behavior?
> Version 3.4GA
> Veritas-bu maillist - Veritas-bu AT mailman.eng.auburn DOT edu