T10000C - 1.57.308 Code Changes (Doc ID 1550532.1)

Last updated on MARCH 17, 2025

Applies to:

Symptoms

 Various problems that are addressed in 1.57.308 code.

Changes

T10000C Drive code changes since 1.53.316 Release

Note: The FSC's listed here are associated to very specific 'foot prints' or failure scenarios related to that specific FSC. The fact that the FSC gets listed in these instructions is in no way implying that the FSC will not be seen with this version of code, as there are multiple ways (or foot prints) for a drive to present a specific FSC or FSC/s.

This release of code addresses issues identified with prior releases.

Changes in 1.57.308 Version:
Change made to use the current cartridge tape mark count/s stored in the RFID chip in response to high-speed-positioning requests whenever the MIR is marked ‘invalid’. Previously available in RB53.315 special build.
37F6
Fix for read ERP ping-pong problem seen with 37F6 error recovery.
Fix for logging all temporary errors in event logs.
SGL – LTFS MAM support. Previously available in RC53.315 special build.
SAM-QFS fix reporting remaining capacity when max-capacity is on. Previously available in RH53.315 special build.
0930
Fix 0930 SNO which occurred during an offline/VOP rebuild-MIR attempt on a partitioned tape (ALP).
SGL – LTFS remaining capacity fix. Previously available in RF53.315 special build.
3923
Fix for 3923 SNO w/ FSA on + fix for tape mark count now logged in the RFID. Previously available in RD53.315 special build.
OSB (Oracle Secure Backup) fix when BFS is issued at BOT. This problem is only seen with new (blank) tapes. Previously available in RI53.315 special build.
36BA
Improved append write error recovery procedures for majority of 36BA perm write during appends. Previously available in RA53.316, RE53.316 and RI53.316 special builds.
37F6
Improve 37F6 read ERP tables to reduce 37F6 Read PERM events. Previously available in RA53.316 special build.
Extended Rebuild-MIR time-out setting to 44 hours for ALP tapes. This change now allows sufficient time to rebuild a MIR on an ALP written tape where the majority of the partitions are blank or empty.
48F8
T10KB written tapes which have only one HLU and that HLU fits into one single matrix. Then loading such tapes into a T10K-C drive and issuing a FSF command will cause the 48F8 SNO.
Fix to allow SNMP ID table in drive configuration option to enter SNMP ID’s in any of the available table fields without restricting top-to-bottom entries.
Customers were experiencing high cleaning tape usage on some of their T10KC drives. This fix will provide a 3X reduction in occurrences of those types of early clean requests. This code has been modified by changing the boost value criteria in the cleaning algorithm along with a minimum distance since last clean threshold.
Corporate policy compliance change to remove E-Key licensing functionality from T10KC drive specific to encryption entitlement. FE’s and Customers can now skip E-Key download of key files for encryption licensing procedures and proceed directly to Enrollment procedures in OKM encryption installations. Note: This code will now display the drive as already Licensed (Un-enrolled) during VOP connection.
Fix to allow customers to position and read beyond current EOD on a tape. Note: Typically only used when customers have inadvertently over-written files or have re-labeled active data sets on a tape.
3697
Fix for 3697 SNO problem which was introduced in RA53.316 special build. Previously available in RE53.316 special build.
3493
Fix to disable sending FSC 3493 messages to the library/s. Customer was complaining about these messages wrapping library logs. This logging began in 1.53.316.
TAA feature now gets two more selectable modes when running in FC mode. These will be seen in the VOP configuration menus. Future Service documentation and the Operator’s guide will be updated to reflect the details of this change. T2 Service & Support has created and posted the details of this change into knowledge base doc # 1534143.1.
Note: FICON configuration menus under TAA will NOT reflect these two new sub-optional modes.
STA change to pass correct information pertaining to what source initiated any media verification.
This drive/code will bring new FIPS certification which has mandated the following - in three of four following modes: 1) Encryption Disabled or OFF. 2) Encryption Enabled or ON, Permanently. 3) Encryption Enabled or ON – switchable. 4) DPKM mode is no longer FIPS approved and from this release going forward requires the FE or Customer to turn off DPKM mode in the drive configuration menus (committing IPL’s the drive) then the code files can be loaded (successful transfer of the code image is
followed by another IPL) DPKM can then be re-configured as ON ( committing will IPL the drive ). Note” New FIPS 140-2 requirements mandate that code transfer be performed only in FIPS mode. T2 Service & Support has created and posted the details of this change into knowledge base doc # 1534138.1
Switching interface types (FC to 3592 FICON, 3592 FICON to VSM or any of the reverse order/s) will bring return the drive/s to all original factory default configuration menu settings. Features or options supported under the channel interface modes will potentially need to be re-set manually subsequent to the time of the interface mode change/s.
T2 Service & Support has created and posted the details of this change into knowledge base doc # 1534143.1
6205
This code bug-fix is addressing a very rare but potential problem. The scenario is 1st seen with a 6205 PERM Write error during FSA re-constitute. This change fixes a bug found in the code where a write perm can occur during the drive’s efforts to re-constitute spare data and data remaining in the buffer is falsely reported to be on the tape. With this fix, when a 6205 perm is detected any/all data in the buffer is properly reported as “not written to the tape”.
A221
Fix for seldom seen A221 SNO when the SNMP Task failed to Start. Note: only seen when T10K drives are connected to SDP.
STA Fix MDV metrics bugs. Add formatting of metrics in dumps.

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.