reports:reconciliation
This is an old revision of the document!
Table of Contents
TapeTrack Reconciliation Report
The TapeTrack Reconciliation Report is created by the Command Line Program TMSS10Reconcile.
The program runs in 4 sequential phases:
- Phase 1 Load of the TapeTrack Scan-Map from a Scan File.
- Phase 2 Reconciliation of the Scan-Map.
- Phase 3 Listing of unreferenced Scan-Map items.
- Phase 4 Report Production.
Report Input
TapeTrack Customer Status
Scan File
Report Sections
Load of Scan-Map
The purpose of this phase is load a TapeTrack Scan-File and resolved each of the a Scan-File Entries into a Fully Qualified TapeTrack Barcode.
As the Scan-File is loaded, a Scan-Map is created.
Alternatively, rather than loading the Scan-Map from a Scan-File, the TapeTrack Import Engine can be used to load the Scan-Map. This facilitates loading from Fixed Length Reports, CSV Files and ODBC Data Sources.
The Fully Qualified TapeTrack Barcode can be resolved from an Unqualified Barcode or an Extended Attribute.
System: TapeTrack
Report Description: Phase 1: Load Scan-Map from Scan-File
Production Time: Monday, March 19, 2018 - 10:09:27 (AUS Eastern Daylight Time)
Report Width: 149 bytes
Seq. Record Barcode Resolved As Status Notes
------ ------ ---------------------------------------- -------------------- ------ -------------------------
1 1 US04.LTO.000002L5 US04.LTO.000002L5 OK
2 2 US04.LTO.000003L5 US04.LTO.000003L5 OK
3 3 US04.LTO.000004L6 US04.LTO.000004L6 OK
4 4 US04.LTO.000005L6 US04.LTO.000005L6 OK
5 5 US04.LTO.000009L6 US04.LTO.000009L6 OK
6 6 US04.LTO.000010L6 US04.LTO.000010L6 OK
7 7 US04.LTO.111111L6 US04.LTO.111111L6 OK
------ ------ ---------------------------------------- -------------------- ------ --------------------------
Reconcile of TapeTrack Volumes
The purpose of this phase is to list all of the Volumes that are either in, moving to, or unexpected in the specified Repository.
The following statuses may result:
- Reconciled if the Volume is in the target repository, is in the Scan-Map and not moving.
- Reconciled (Confirmed) if the Volume is moving into the specified Repository and is in the scan map. The Volume will be Confirmed in the TapeTrack database.
- Absent from Scan-Map if the Volume is confirmed into the specified Repository and is not present in the Scan-Map. An Audit Flag will be placed on the Volume.
- Pending Confirmation if the Volume is in a Move Status out from the specified repository and is not overdue at the target repository.
- Overdue at Target if the Volume is in a Move Status to the specified Repository, is not in the Scan-Map and is now overdue at the target repository.
- Unexpected in Scan-Map Present in Scan-Map but not present at, or moving to, the target repository.
Report headings and spacing have been edited to fit information on web formatting
System: TapeTrack
Report Description: Phase 2: Reconcile TapeTrack Volumes against Scan-Map
Report Notes: Repository OFFS
Production Time: Monday, March 19, 2018 - 10:21:34 (AUS Eastern Daylight Time)
Report Width: 169 bytes
Seq Barcode Current Rep Target Rep Move Time Overdue Scanned Status Notes
--- ------------------ -------------- ----------- ----------- ------- ------- ------ ----------------------
1 US04.LTO.000002L5 Offsite Vault No Yes OK Reconciled
2 US04.LTO.000003L5 Offsite Vault Library H1:10:39 No Yes OK Pending confirmation
3 US04.LTO.000004L6 Offsite Vault Library H1:10:39 No Yes OK Pending confirmation
4 US04.LTO.000005L6 Offsite Vault Library H1:10:05 No Yes OK Pending confirmation
5 US04.LTO.000008L6 Offsite Vault No No NOT-OK Absent from Scan-Map
6 US04.LTO.000009L6 Offsite Vault No Yes OK Reconciled
7 US04.LTO.000010L6 Library No Yes NOT-OK Unexpected in Scan-Map
-- ------------------ -------------- ----------- ----------- ------- ------- ------ -----------------------
Following the example data at the top of page we have:
- Volumes 000002L5 and 000009L6 Reconciled as they are in the scan map, and confirmed in the current repository (Offsite Vault).
- Volumes 000003L5, 000004L6 and 000005L6 Pending confirmation as they are in the scan map, and in a move from the current repository but not yet confirmed at the target repository.
- Volume 000008L6 Absent from Scan-Map as it appears in TapeTrack as at the current repository but is absent from the scan map. This shows the volume is either somewhere it shouldn't be or is missing and as such is given a status of NOT-OK and is given an audit flag for further investigation.
- Volume 000010L6 Unexpected in Scan-Map as it is present in the scan map as being at the current repository but shown in TapeTrack as being confirmed at another repository. As such is given a status of NOT-OK and is given an audit flag for further investigation.
Unreferenced Scan-Map Entries
This report shows Volumes that are in the Scan-Map, but are not known to TapeTrack.
System: TapeTrack
Report Description: Phase 3: Unreferenced Scan-Map entries
Production Time: Monday, March 19, 2018 - 10:21:34 (AUS Eastern Daylight Time)
Report Width: 29 bytes
Seq. Barcode
------ --------------------
1 US04.LTO.111111L6
------ --------------------
Reasons for this error could be:
- Volume does not belong to you but has been included with your volumes by operator error.
- Manually produced scan file with a typo on a volume ID.
- Volume added to inventory but not entered into TapeTrack.
Reconciliation Statistics
This report shows the final statistics for the Reconciliation process.
System: TapeTrack
Report Description: Phase 4: Reconciliation Statistics
Production Time: Monday, March 19, 2018 - 10:21:34 (AUS Eastern Daylight Time)
Report Width: 75 bytes
Metric Count
------------------------------------------------------------ ------------
Phase 1: Read from Scan-File 7
Phase 1: Loaded successfully from Scan-File 7
Phase 1: Loaded unsuccessfully from Scan-File + 0
------------------------------------------------------------ ------------
Phase 2: Reconciled 2
Phase 2: Reconciled (Confirmed) 0
Phase 2: Confirmation Bypass 0
Phase 2: Pending confirmation 3
Phase 2: Out of scope 3
Phase 2: Absent from Scan-Map + 1
Phase 2: Unexpected in Scan-Map + 1
Phase 2: Overdue at subject repository + 0
Phase 2: Overdue at target repository + 0
------------------------------------------------------------ ------------
Phase 3: Unreferenced Scan-Map items + 1
------------------------------------------------------------ ------------
Phase 4: Total Errors 3
------------------------------------------------------------ ------------
Phase 1 Reads in volume ID's from the scan file, parses them (depending on format) into Customer ID, Media ID and volume ID. Metrics are then displayed as the number of volumes successfully and unsuccessfully loaded ready for reconciliation in phase two.
Phase 2
Movement Aging Report
This report shows statistics on Volumes that remain in a Move Status after the Reconciliation has completed.
System: TapeTrack
Report Description: Phase 4: Movement Aging Report
Production Time: Monday, March 19, 2018 - 10:21:34 (AUS Eastern Daylight Time)
Report Width: 40 bytes
Duration Incoming Outgoing
-------------------- -------- --------
less than 1 day 0 3
less than 2 days 0 0
less than 3 days 0 0
less than 4 days 0 0
less than 5 days 0 0
less than 6 days 0 0
less than 7 days 0 0
less than 8 days 0 0
less than 9 days 0 0
9 or more days 0 0
-------------------- -------- --------
reports/reconciliation.1522888807.txt.gz · Last modified: 2025/01/21 22:07 (external edit)