|
DataMuseum.dkPresents historical artifacts from the history of: RC4000/8000/9000 |
This is an automatic "excavation" of a thematic subset of
See our Wiki for more about RC4000/8000/9000 Excavated with: AutoArchaeologist - Free & Open Source Software. |
top - metrics - download
Length: 4608 (0x1200) Types: TextFile Names: »changemanu «
└─⟦01e83a425⟧ Bits:30008166 Bånd med SW8010 og SW8500 source code └─⟦75ff9bef3⟧ └─⟦this⟧ »changemanu «
C H A N G E D I S C =================== Changedisc is a program for moving files and file descriptors from one disc to another. Example ======= The call changedisc file1.disc3 file2.disc2 will move the files or file descriptors file1 and file2 from the places where they are located to disc3 and disc2 respectively. The files will keep their scope. The call may of course be senseless, and thus it may give error messages, if the process e.g. has not got recources to write and rename files on the disks in question. Call ==== changedisc ( <source file>.<destination disk> ) 0/1 <source file> ::= <name> <destination disk> ::= <name> Function ======== The algorithm of the program is as follows: - The program will interpret its parameter list, and for each parameter pair it checks the syntax. - Then a lookup of the source file will be performed. - On the destination disk a new work entry will be created. If the size of the entry is >=0, the document name will be changed, otherwise the tail of the work entry will be identical to the tail of the source file entry. - The work file will receive the same scope (i.e. bases and permanent key) as the source file. - If the size of the entry >0, data will be moved from the source file to the work file on the destination disk. - The source file will be removed. - The work file will be renamed to the name of the source file. The algorithm, as it is implemented, will uncritically move, for instance an area entry from one end to the other of the same disk. This may be used to collect an area made up of many scattered slices into one contigous area, if the necessary adjecent slices are available. The moving of data is performed in a buffer which adapts itself to the process size. Thus the user may expect the program to move areas faster in a large process than in a small one. For each source file moved succesfully, a message: <source file> moved to <destination disk> is issued on current out. When the program terminates, it will give a terminating message stating how many files were moved succesfully, and possibly how many errors it encountered. If at least one file was moved, OK is set to YES. If at least one error was encountered, WARNING is set to YES. Error messages ============== Four types of error messages may be issued by the program: 1) <source file> cannot be moved to <destination disk>, <explanation> where explanation may be: a) cannot be found b) no temporary claims c) no permanent claims d) bases improper e) input trouble f) output trouble g) rename trouble 2) rename trouble!!! new name: <wrk name> in stead of <source file>!!! 3) <source file> not followed by a proper diskname 4) parameter pair <int> not proper, moving stopped! In case of an error of type 1, the work file on the destination disk is removed, and the source file is left unchanged. The actual reason for a given explanation (a thru g) may not always be obvious. - Explanation a may e.g. mean that an entry does not exist, but it may also mean that the bases of the process are unfit to move the entry. - Explanation b could mean that the destination disk is unknown. - Explanation d might mean that the source file is a system file. - Explanation d might mean that the source file is a system file. - To get a full explanation of e and f, it may be necessary to ask the system staff to fetch disc statistics of either the disk of the source file or the destination disk. - Explanation g may mean that somebody is using the source file. In case of an error of type 2 the user must try to find the obstacle, remove it, and perform the renaming "by hand", i.e. use the rename command. The moving of data was performed without trouble! In case of an error message of type 3, the program will try to make sense out of the following parameters. The reason may be a forgotten destination disk, in which case a type 4 error message may follow. In case of an error message of type 4, the program has given up interpretation of its parameters, because it cannot make sense out of them. ▶EOF◀