Editing Scanco Administration (section)

==Saveset and Zip files==

===Installation===

The standard <code>ZIP</code> and <code>UNZIP</code> tools on the VMS system cannot manage large file sizes. Therefore it is required to install a version that Mark Blanchard (February 2024) has compiled that specifically manages these large sizes.

Extract from <code>ZIP30L.ZIP</code> and <code>UNZIP60L.ZIP</code> the EXE files <code>ZIP.EXE</code> and <code>UNZIP.EXE</code>. Then as user "system" copy these into <code>DISK0:[SYS0.SYSCOMMON.SYSEXE]</code>. You need to ensure the permissions are set properly too:

 $ set def disk0:[sys0.syscommon.sysexe]
 $ set prot=(s:rwed,o:rwed,g:re,w:re) telnet_client.exe

Previous versions of <code>ZIP.EXE</code> and <code>UNZIP.EXE</code> are stored in the same directory in case it is necessary to revert to an older version.

===Saveset===

====Saveset Naming Convention====
The Scanco backup program stores raw (RAW) and image (IMA) data as save sets (SAV).  
*RAW save sets contain RSQ files and IMA savesets contain all other file types.  
*The saveset filename is composed of the 8-digit measurement number plus "_RAW.SAV" for raw data and "_IMA.SAV" for image data.  
*For example, the data for a scan with measurement number 1234 would be stored as:
<pre>
00001234_RAW.SAV  ?  RSQ
00001234_IMA.SAV  ?  all other files, ISQ, AIM, GOBJ, TXT, SCV, etc.
</pre>


[[Image:Redirect.jpg|15px]] [[#top|''Return to Contents'']] or [[Main_Page|''Return to Main Page'']]

====Create and Unpack Saveset====
Savesets are OpenVMS backup files, similar to a zip.  Use the backup command.
<pre>
$ BACKUP/LOG disk3:[microct.projects.buie...] disk3:[microct.projects]buie2012.sav/sav	
                !Creates a saveset file of disk3:[microct.projects.buie].  
                !The ... after the folder indicates to include all subfolders and files.
$ BACKUP/LOG mysaveset.sav/sav disk3:[microct.projects.buie]
                !Unpacks the whole saveset to disk3:[microct.projects.buie]
$ BACKUP/LOG mysaveset.sav/sav disk3:[microct.projects.buie...]	
                !The ... at the end of the output location indicates to unpack the saveset and maintain the original directory structure.
$ BACKUP/LOG mysaveset.sav/sav/select=*.aim disk3:[microct.projects.buie]	
                !The select flag is used to indicate extraction of only aim file types.
$ BACKUP/LOG mysaveset.sav/sav/select=[microct.data...] disk3:[microct.projects.buie]	
                !The select flag is used to indicate extraction of the folder data and all subfolders and files.
$ HELP BACKUP   !More information on the backup command.
</pre>

You may want to exclude some files:
<pre>
$ set default DK0:[MICROCT.DATA]
$ BACK/LOG [.00000031.00000600]/EXCL=(*_TRNSFR.COM,*.SAV,*.ZIP,ZI*,*.RSQ) DK0:[MICROCT.DATA.00000031.00000600]3418_00000031_00000600_IMA.SAV/SAV
</pre>

[[Image:Redirect.jpg|15px]] [[#top|''Return to Contents'']] or [[Main_Page|''Return to Main Page'']]

====View Saveset Contents====
To view contents of a saveset (SAV) on disk:
<pre>
$ backup/list upat_print_list_nomatch.sav/sav
</pre>

To view the savesets (SAV) on a tape:
<pre>
$ mount/ov=id tp0:
$ dir/date tp0:*.*
$ dismount tp0:
</pre>

To view contents of a saveset (SAV) on a tape:
<pre>
$ mount/foreign tp0:
$ backup/list tp0:*.*  ! OR, backup/list tp0:*.SAV
or
$ backup/list=results.txt tp0:*.*  ! save output in results.txt
$ dismount tp0:
</pre>

An idea to get the results of the backup/list into a text file: Run the procedure in a submitted script and save the resulting log file with all the output.


[[Image:Redirect.jpg|15px]] [[#top|''Return to Contents'']] or [[Main_Page|''Return to Main Page'']]

====Extract a single file from SaveSet====

In a large SaveSet, sometimes we only want one file extracted, not the whole archive extracted. This can be done with

  $ backup /log /select=myfile.txt mysaveset.sav /sav disk1:[microct.scratch]

or []  as destination will put the file in the current directory.

This can take a while as it looks through all the saveset. Once it logs that the file has been restored, you may interrupt with F6. Else it goes on looking through the rest of the saveset.


[[Image:Redirect.jpg|15px]] [[#top|''Return to Contents'']] or [[Main_Page|''Return to Main Page'']]

====Transfer Saveset from microCT to XtremeCT====

You can create a SAV set of your project on the VivaCT and transfer it to the Xtreme system, or vice-versa.
First, create the SAV set using the command:
<pre>
For example:
$ BACKUP/LOG DISK3:[MICROCT.PROJECTS.SB.MYPROJECT...]*.*;* -
     SYS$SCRATCH:MYPROJECT.SAV/SAV
</pre>
This creates the MYPROJECT.SAV file in the scratch directory.  Now zip the file:
<pre>
$ cd sys$scratch
$ zip "-V" MYPROJECT.ZIP MYPROJECT.SAV  (NOTE: must use quotes and a capital V!!!!)
</pre>
FTP the .ZIP file to SODOR ( in binary mode!!!), and then FTP it off onto your destination system (Viva or Xtreme).  See the appropriate HowTo for FTP instructions.  Once you've FTP'd it, unzip the file:
<pre>
$ unzip MYPROJECT.ZIP
</pre>
Finally, unpack the contents of the .SAV file:
<pre>
$ BACKUP/LOG MYPROJECT.SAV/SAV DISK3:[MICROCT.PROJECTS.MYPROJECT] <--- or whatever destination directory
</pre>
NOTE:  transferring a .SAV directly from VMS to VMS should work, but not via any third operating system (like SODOR) - so zipping is always the safe way to make sure it works.


[[Image:Redirect.jpg|15px]] [[#top|''Return to Contents'']] or [[Main_Page|''Return to Main Page'']]

===Zip===

====Zip and Unzip files====
Use the zip program to add files to a zip archive. Make sure you are using version 3 if you want to Zip files greater than 2GB (contact Scanco to install v3 if necessary).
<pre>
$ ZIP myzip.zip myfile.txt;1	                !Adds myfile.txt to myzip.zip.
$ ZIP "-V" myzip.zip myfile.txt;1	        !Adds myfile.txt;1 to myzip.zip.  The "-V" maintains the OpenVMS version number.
$ ZIP "-V" myzip.zip [.subdir...]*.*;*	        !Adds all files within subdir to myzip.zip, maintaining their version number.
$ ZIP	                                        !Displays the help for the zip command.
</pre>

Use the unzip program to unzip an archive.
<pre>
$ UNZIP "-V" myzip.zip		                !Extracts myzip.zip, maintaining the OpenVMS structure.
$ UNZIP		                                !Displays the help for the unzip command.
</pre>


[[Image:Redirect.jpg|15px]] [[#top|''Return to Contents'']] or [[Main_Page|''Return to Main Page'']]

====Transfer Zip between Scanco systems====

Files must be zipped before transfer by e-mail or ftp because important attributes will be lost in the transfer otherwise.

To transfer files from system A to B, do the following.

On system A:
<pre>
$ zip "-V" for_calgary.zip uctd:UCT_SAMPLES_TORONTOXT.DAT  ! for each filename
$ zip "-V" for_calgary.zip uctd:UCT_MEASUREMENTS_TORONTOXT.DAT
</pre>
This will add both files to the same zip file.

Note: "-V" is very important, it must be capital V!

Transfer the file by e-mail, or by ftp.

On system B:
<pre>
$ unzip -j for_calgary.zip  ! to unzip on your end them (-j to 'junk' the original file path)
</pre>


[[Image:Redirect.jpg|15px]] [[#top|''Return to Contents'']] or [[Main_Page|''Return to Main Page'']]

====Unpack Zip sent by Scanco====
In the .zip file, you'll find a .sav file. Unzip the .zip just by saying

<pre>$ unzip xxxx.zip</pre>

Then:

<pre>$ backup/log xxxx.sav/sav disk3:[steve.devel.temp]</pre>

and it will unpack everything into <code>disk3:[steve.devel.temp]</code>

Or:

<pre>$ backup/list xxxx.sav/sav</pre>

and you see what's in the .sav.

Then:

<pre>$ backup/log xxx.sav/sav/sel=[andres.uct.ipl_for_cust...] disk3:[steve.devel.cipl...]</pre>

and it will create the same directory tree in <code>steve.devel.cipl</code> as it was when I 
packed it into the .sav.

[[Image:Redirect.jpg|15px]] [[#top|''Return to Contents'']] or [[Main_Page|''Return to Main Page'']]

====Tips for making and unpacking SAVSETS====
Separate all "input" files with comma, and no space in between (space separated parameters) :

<pre>
$ backup/log D0014097.RAD,D0014097.SCV myfiles.sav/sav
</pre>

You may want to consider to only take the newest/highest file version:

<pre>
$ backup/log D0014097.RAD;,D0014097.SCV; myfiles.sav/sav
</pre>

When unpacking a SAVSET, if you want the directory structure to be maintained, do something like this:
<pre>
$ BACKUP/LOG ACKNEE_HUMAN_2020-02-18.SAV/SAV/SELECT=([BONELAB.PROJECTS.ACKNEE...]*.*) DISK4:[BONELAB.PROJECTS.ACKNEE...]
</pre>

Extracting an archived SAVESET back onto the VMS system in location different from where it was originally located, for example putting it
on DISK7:[XTREMECT2.EXTERNAL] instead of DISK4:[BONELAB.PROJECTS], do the following:
<pre>
$ SET FILE/ATTR=(RFM=FIX,LRL=32256) UBC_HUMAN_2024-03-25.SAV
$ BACKUP/LOG UBC_HUMAN_2024-03-25.SAV/SAV/SELECT=([BONELAB.PROJECTS.UBC...]*.*) DISK7:[XTREMECT2.EXTERNAL.UBC...]
</pre>
[[Image:Redirect.jpg|15px]] [[#top|''Return to Contents'']] or [[Main_Page|''Return to Main Page'']]