Table of Contents
c.catalog
Initial Catalog Creation
The catalog itself is placed on the HOST filesystem. If it doesn't exist, it's automatically created.
We will start by cataloging the CYBIS/R1 system by issuing the following command:
cdc.io c.catalog -d demodatabase.sqlite3 -c "E:\Emulation\TH.CybisRelease1\disks" TH.CybisRelease1
where:
-d demodatabase.sqlite3 is the name of the catalog database
-c “E:\Emulation\TH.CybisRelease1\disks” is the path-type cluster of disks to be scanned/cataloged
TH.CybisRelease1 is the character string (your choice) which names this inventory/collection.
For each PLATO file that is found, an entry is created in the database.
The first time a cluster is cataloged, the procedure takes a bit of time and depends (mostly) on CPU speed because each entry is being cryptographically hashed, defining a unique signature for the file.
Get some coffee…
When the process ends - you'll see:
Now do the same thing for the CYBIS/R2 instance.
cdc.io c.catalog -d demodatabase.sqlite3 -c "E:\Emulation\CybisRelease2.Prod\disks" CybisRelease2
Get some more coffee…
Once you see:
Check Your Work
Check your work by issuing the following command
cdc.io cat.list -d demodatabase.sqlite3
The response should be:
Test Compare
Now all of your hard work pays off! If you want to compare the two instances, issue the following command:
cdc.io cat.compare -d demodatabase.sqlite3 "TH.CybisRelease1" "CybisRelease2"
The response should be:
Success!
You have now:
- cataloged two different instances (took some time)
- listed the names of the instances from the database (took no time)
- compared the FULL contents of two separate instances (in under a second)!