Editing Scanco Administration (section)

===Copy and Move===
====Copy files between accounts/users====

As user <code>system</code> you can copy files between accounts (e.g., microct and devel).  There is no need to set user/priv=bypass as this is set by default as user system.

If you want to copy between two users (i.e. normal users, not calibration or system), then you can only write on the user directories for which you are logged in. So, if you want
to copy files from account xtremect2 to microct, you need to log into microct account and copy the file from xtremect2 to microct

If you want to use the backup command for copying multiple subdirectories with 
the three dots (e.g., <code>disk2:[microct.data.00000034...]</code>) then you HAVE to put an <code>/owner=devel</code> at the end:

<pre>
$ backup/log disk2:[microct.data.00000034...] -
        disk2:[devel.data.00000034...]/own=devel
</pre>


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

====Move a directory on the same device====

You can simply use the rename command to move a directory on the same device, but you need to set DELETE protection for the file owner for this to work
 $ set prot=o:rwed <dir>.dir
 $ ren <dir>.dir new:[parent.directory]
 $ set prot=o:rwe new:[parent.directory]<dir>.dir


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

====Move a whole directory structure with BACKUP command====

Sometimes we want to move entire directories. For example, moving a measurement directory from DISK2 to DISK6, or moving a project to another disk. 

Here is how to move a project:
  $ BACKUP DISK2:[MICROCT.PROJECTS...] DISK3:[MICROCT.PROJECTS...]/VERIFY

Note the use of <code>...</code> in both places.

If you move a data measurement, you could do it as follows:
  $ BACKUP DISK2:[XTREMECT2.DATA...] DISK6:[XTREMECT2.DATA...]/LOG/VERIFY

In both cases, you can add a <code>/DELETE</code> command to so that it deletes after the move is completed and verified (files will be deleted, but not folders).
  $ BACKUP/VERIFY/DELETE DISK2:[XTREMECT2.DATA...] DISK6:[XTREMECT2.DATA...]/LOG/VERIFY

Alternatively, you can simply check that the move was successful, and then delete the original files (be <b>very</b> careful!!):
  $ delete disk2:[microctt.projects...]*.*;*
  $ dl disk2:[microctt.projects...]*.dir     ! A for all; do until sub-dirs are gone

Note that I've misspelled "microctt" on purpose as these commands are VERY dangerous. You could wipe out a lot of data by accident. Be careful!


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

====Fix corrupted VMS files when moved to or from a PC====

There seem to be two options. The most simple one is to simply run:

 $ set file/attr=(lrl:512, rfm:fix) filename.isq

Alternatively, we start by getting good file format/attributes from a good aim/isq/gobj, etc.

  $ ana/rms/fdl/out=correct.fdl good.aim

Then we edit the file <code>correct.fdl</code>, leaving only 5 lines:
  RECORD
        BLOCK_SPAN                        yes
        CARRIAGE_CONTROL                  none
        FORMAT                            fixed
        SIZE                              512
 
Now we have to set the file attributes of the affected aim (isq, gobi) file:

  $ set file/attr=lrl=514 bad.aim    ! Yes, 514
  $ set file/attr=lrl=514 *.AIM        ! do a bunch at a time

Finally we create a fixed file

  $ convert/fdl=correct.fdl/trunc bad.aim converted.aim

This process discards the superfluous 2 bytes, usually caused by transferring to/from a PC.


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