SL8500 - Problem Reading Volser Labels due to Marginal Labels and Read Verify Flag

Asset ID:	1-72-1017376.1
Update Date:	2011-03-16
Keywords:

Solution Type Problem Resolution Sure

Solution 1017376.1 : SL8500 - Problem Reading Volser Labels due to Marginal Labels and Read Verify Flag

Applies to:

Sun StorageTek SL8500 Modular Library System - Version: Not Applicable and later [Release: N/A and later]
All Platforms
Checked for relevance on 16-Mar-2011.

Symptoms

Marginal cartridge labels can impact PTP (Point-to-Point) operations
Cartridges are abandoned in PTP
External cartridge label read errors
Read verify flag can get permanently set
Label read errors
Read verify flag is permanently set.

Changes

{CHANGE}

Cause

{CAUSE}

Solution

Resolution
Vary PTP and elevator offline and back online.

Additional Information
Marginal Labels and Read Verify Flag
Customer site reported problems reading external cartridge labels and found tapes unexpectedly abandoned in the SL8500 PTP. Investigation found two contributing factors; marginal cartridge labels and read verify flag set at the SL8500 PTP.

External marginal labels can be related to many factors, the most common:
- Use of non-supported labels for 9x40 cartridges. Oracle/STK only supports EDP/ColorFlex and American Eagle System/Wrightline. 9x40 labels have a "unique" barcode format based on the
Code 39 barcode.
- Improper placement of the label within the recessed area of the cartridge. Improper alignment between the media id and 6 character label. The scan line should be on the same plane. If the 6 character label and Media ID and are skewed in opposite directions the horizontal scan may cause intermittent read errors. This is more critical on the original thinner/short bar code labels common in older 93xx installations.

Refer to attached picture document below.

Read verify flag unexpectedly set for all moves to the PTP and elevators. The read verify flag will cause label verification on all moves to the PTP and elevator. This greatly increases the opportunity of label read errors at customer sites with marginal labels. A code problem causes this flag to never get reset as expected when an entire "library audit" selection is done via SLC. A simple vary offline and back online of the PTP and elevator will reset the flag. A door open does not generate this problem which will also trigger a full library audit.
Note: This issue will be resolved in a future release of microcode scheduled for the fall of 2007 at 3.9x.

As a temporary solution, it be necessary to run a full library audit via SLC. Follow the procedure or recommendation below:

Procedure to audit an entire library via the Min/Max Audit Command on SLC

In order to physically audit all the storage cells in a library using the SLC Audit command, it is necessary to enter 14 separate requests as follows:
- Select "Slot" for both the Start Address and the End Address.
- Leave Library at Min for Start and Max for End.
- For the Rail, Column, Side, Row values use the following fourteen settings where the shorthand symbols N means Min and X means Max.

Start Address/End Address:
1. N,N,N,N 3,N,N,13 Above Safety door on left
2. 4,N,N,6 4,N,N,13 Safety Door (SD) hole on left
3. N,N+1,N,N X,-7,N,13 Up to corner before PTP
4. N,-6,N,6 X,-6,N,13 PTP cells
5. N,-5,N,N X,-3,N,13 Up to Drives
6. N,3,N,N X,5,N,13 Right of Drives to PTP
7. N,6,N,6 X,6,N,13 PTP cells on right
8. N,7,N,N X,X-2,N,13 Corner to SD hole on right
9. N,X-1,N,N 3,X-1,N,13 3 rails on top of SD
10. 4,X-1,N,6 4,X-1,N,13 SD holes on right
11. N,X,N,N X,X,N,13 Final column on outside
12. N,N+2,X,N X,-9,X,X Inside skipping holes for SD (left)
13. N,-2,X,N X,2,X,X Across from Drives
14. N,9,X,N X,X-2,X,X Inside on right

Recommendation:
- Upgrade the SL8500 microcode to a minimum level of 3.72.
- Use the Entire Library Physical Audit in SLC and as soon as it is started in SLC, vary each elevator and PTP offline and then online to reset the permanent read verify flag.

@ SL Console, Audit, Cartridge label, SL8500, PTP, SLC
Previously Published As STKKB80309

Attachments

This solution has no attachment