|
|
|
|
We may be good, but we can't do everything for you. You have to decide what is the best organization for your data given your unique requirements. Razor will handle pretty much any organization you desire. To give you a good foundation to build on, we suggest that you study the section "Containers: databases, groups, and folders" on page 183. This section discusses these three important data organization methods and provides some things to consider when layout your database.
The kid_of_xxx processes are used to assist issues, versions, threads, and the database server for low-level operations. Don't worry, some day they will grow up and leave home.
During operations for which the versions tool must check-in or introduce a file, a backup copy is made first. This file is named `...<filename>' (under UNIX) or `<filename>.RZ_BACKUP' (under Windows) and is copied simply as a safety mechanism. Users may, at their discretion, remove these files at anytime. The rz_cleanup UNIX script may be used to delete ones that have reached a certain age. Users may also prevent the creation of these files in the first place if they so desire, (See "Versions.makeBackup" on page 285.)
At various points in the flow of the programs, users may notice a small glyph appear for short periods. This was originally used purely as a debugging aid while developing the tool. It signals when asynchronous database updates are being received by the programs from the Razor server (rz_server). As time went by, it was decided to draw it as a sailor, in recognition of the fact that version 1 of the tool suite was used on a Navy project.
The glyph was un-named until the history of William of Occam was investigated. Since then, he became `Occam the icon', or `Bill' for short. We decided we'd leave him in the program until people complained. See "Occam the Icon" on page 289 for details on how to dispense with our mascot.
The odds are that pretty much every computer program on the planet will be doing backflips and spewing bits all over the carpet. Razor, however, is all set and ready for the transition. We will be as secure and safe as the underlying operating system you are running on; no more, no less.
Tower's official statement, "The software products from Tower Concepts are `Millennium Compliant', in that they provide the following functions: (a) handle date information before, during, and after January 1, 2000, including but not limited to accepting date input, providing date output, and performing calculations on dates; and (b) function accurately and without interruption before, during, and after January 1, 2000, without any change in operations associated with the advent of the new century. Tower Concepts cannot and does not guarantee the `Millennium Compliance' of any software or operating systems on which it may rely (e.g., UNIX, SCCS, RCS, Windows 95/NT, etc)."
Some editors, most notably Emacs, are often configured to insert spaces into the file you are editing each time you hit the tab key. Disable this feature and try again.
There are X resources that can be set to control where mail goes. Look at "E-mail back to Tower Concepts" on page 289.
First, the sky darkens and you'll notice a mist coming down from the mountains in the east... But seriously, you will no longer have access to Tower's fine support staff or product updates. Oh, and by the way, your Razor tools will continue to work. You will be contacted by our license department for an opportunity to renew your service contract before it expires.
According to the dictionary we have here in the office, it should rhyme with `cliff', as in the word `hieroglyphic'. It does not rhyme with `wife'.
After modifying files in the Tables directory, you must restart the database server. Did you remember to bring the database server down before making the changes? Take a look at "Customizing the Attributes file" on page 197 for details.
Check your tty setting using the command `stty' If the `tostop' flag is set, clear it using the command: stty -tostop
You came to the right place. Take a look at the examples directory in $RAZOR_HOME. This directory contains all sort of scripts and files that Tower has collected and/or developed over the years. Many of these might even be useful to you. Peruse the README file which contains a quick description of the use of each file. Take a look here when you get a new release of Razor for updates and new goodies.
Razor currently supports either SCCS or RCS. The simple answer is to pick the archive engine you have available on your system.1 If you have a choice, it becomes a matter of preference. This discussion is not intended to argue the merits of either archival system, just to present some things to consider:
When you create a database or group, you are prompted for the archival engine. The archive engine method is then stored in a file called Vcs in the Tables directory each group and used by Razor as its access method.
alias rissues issues -remote
Yes. Refer to "Changing the compression engine" on page 217.
This is fairly easy, but must be done from the command line with the database down. (Before doing this though, you should really be familiar with how a Razor database is represented on disk. This is discussed on page 253.)
In brief, you would bring the database down, then go to where the directories for the group exists, delete them, then bring the database back up. For example, if you no longer want the apple group...
# razor down # cd $RAZOR_UNIVERSE_DIR/DOMAIN_01 # rm -fr apple # rm -fr apple##Threads # cd # razor up
Good question. The ASCII database is used only as a flushing mechanism. It is loaded, (read), by our database server daemon, (rz_server), at startup and then held in memory to improve performance. As updates are made, information is written back to the database files. All client applications which are connected to the database server receive the information that the server has in memory. So the only performance hit is at startup time, and not with each operation.
When you create a new database, you can copy your master templates into the Tables directory for the issues, versions and threads groups. When the database is brought on-line it will have your characteristics already built in. Common scripts should be placed into a general area which is on each users search path. You can even setup your templates to refer to the fullpath to your scripts so that no ambiguity is possible.
The simple answer is that there is one and only one domain. It was numbered in early anticipation of product growth along these lines, but that has not yet occurred.
Each database has its own rz_prep file (and corresponding rz_prep.sh). You may set up aliases in your .cshrc file to source the appropriate rz_prep file.
The key is to make the rz_prep and rz_prep.sh files smart. Look at the files $RAZOR_HOME/examples/rz_prep.smart and $RAZOR_HOME/examples/rz_prep.sh.smart to see how they can be set up.
NOTE: You should run the script $RAZOR_HOME/scripts/rz_support_os to add the appropriate rz_db_exec script to $RAZOR_UNIVERSE_DIR/bin.
Since the Archive directory is controlled through a process called the Vcs Daemon, started by the server, it will perform all accesses to the files in this directory. Each client connects to one of these daemon processes to perform the appropriate VCS command, as will the razor command line and IssueWeaver. The Vcs Daemon (rz_vcsd) is started by the server. Thus, the Vcs Daemon process, via the server, is the only process that needs write access to the Archive directory.
The bottom line is all file accesses are handled by the Vcs Daemon, and all file permissions are honored via the Access_list file, discussed on page 199.
Most Razor-related operations can be controlled via the Access_list file. Out of the box, Razor permits anyone to bring the server up and down. There is an operation called RAZOR_DOWN that controls who can take the server down. For control of this and other Razor operations, refer to "Access controls" on page 199.
If you disconnect your remote connection, you have 10 minutes to reconnect to the same license token. As long as the database server is still running, the reconnection time will be minimal. Exiting a remote application will force you to login again when the application is restarted and will force a complete reload of information from the server.
When making changes to the Razor group's Attributes file, either editing the file or running the Razor-provided modification scripts,
YOU MUST STOP THE DATABASE SERVER!
All other Razor control files can be modified
...But you will need to re-run the appropriate Razor client application to verify your changes (also, any currently running Razor clients WILL NOT exhibit the changes made).
The Razor database server reads each Razor group's Attributes file when the server is started. Basically, the Attributes file defines a set of data that the server retains in memory. Changes to these files are only read when the server is restarted.
On the other hand, ALL other Razor control files are read when the Razor application is started. Any "attribute" information an application may need is provided to the client by the database server.
Your shell controls this. Try using the command: `nohup razor_lm &' when starting the Razor license manager.
The number of simultaneous users on a network. We do not lock usage of the tool to particular machines or users. Usage may float around your network on an as-needed basis.
Remote users are given the opportunity to disconnect from the database server without exiting the application. This is intended to help users with dial-up connections. When a user reconnects, only the objects that have changed in the currently subscribed group of the database will be reloaded. This will save in the reconnection time. As with local UNIX clients, bringing up the application will consume a license token. The action of disconnecting will NOT release the license token immediately. The license token will remain in use until the user exits the application normally (with the Exit option of the File menu or from the windows Close menu) or after one hour of being disconnected. This time limit is set to handle the situation where a client exits abnormally (such as a power outage), that does not give the server an exit notification. As with other "dead" clients, the server will eventually time them out after one hour and release their license token.
Notice the rest of the message says "You may wish to bring this to the attention of your Razor Administrator". This means that the Razor Administrator needs to create Razor remote client password accounts. Refer to "Remote client password" on page 45 for all the details.
Issue numbers are intended to represent a sequence of 1 to 999,999. In showing the numbers to the user, unused digits are replaced with dots and the comma becomes a dash.
This can be implemented in a number of ways. One popular way this is done is to define an X_OF_MANY attribute which contains either peoples names or more generically their role/title.
Change the print command via the Print Setup... option of the File pulldown menu. The defined command will receive the contents of the information to print on stdin. For example: "lpr -Peng" will send the print output to print queue "eng".
Create a file named Databases in the $RAZOR_LICENSE_DIR directory. In this file put tab separated entries of the form:
<database name label>
<path of RAZOR_UNIVERSE directory>
This will enable the Databases menu item on the main issues screen which contains the <database name label> entries contained in the file.
NOTE: It may seem obvious, but the other database must be active (as a result of a razor up command) to access it.
In this particular case, the attribute label `State' was changed in the Attributes file. This label was probably associated with the STATE attribute. To avoid this warning each time the issues tool is invoked, change references to `State' to the new label for the STATE attribute in the file:
$RAZOR_UNIVERSE_DIR/DOMAIN_01/++ISSUES++.<group name>/ Tables/Bitmaps
There are numerous types of Bitmaps warnings which are usually an indication of a change in an attribute label or value without a similar change to the Bitmaps file. Use the following scripts to rename/remove an attribute label or value, as they will update the Bitmaps file as well as the Attributes file:
$RAZOR_HOME/scripts/rz_rename_attr $RAZOR_HOME/scripts/rz_rename_attr_val $RAZOR_HOME/scripts/rz_remove_attr $RAZOR_HOME/scripts/rz_remove_attr_val
You are not required to include a STATE attribute, however, if you choose not to include this attribute, you will probably receive BITMAP warnings when the database server is started. Also, a number of the supplied scripts and reports may be affected. Hey, we warned you!
# razor down # cd $RAZOR_UNIVERSE_DIR/DOMAIN_01 # mv ++ISSUES++.<old group> ++ISSUES++.<new group> # razor up
If you have any related file activity associated with the renamed issues group, they will not be automatically renamed. The following script snippet can be used to rename the history for the issues group "first" to the issues group "second":
#!/bin/sh
cd $RAZOR_UNIVERSE_DIR/DOMAIN_01
list=\Qgrep -l `++ISSUES++.first' */History/*/*\Q
for f in $list
do
cat $f | \
sed "s/++ISSUES++.first/++ISSUES++.second/" \
> $TMPDIR/tmp
cp $TMPDIR/tmp $f
rm -f $TMPDIR/tmp
done
There is a very useful script in $RAZOR_HOME/examples called attr_to_xy. Usage: attr_to_xy [-g <issue group>] [<outfile>]. It will generate an Xdefaults file which uses X/Y positioning for attributes on an issue form. If <outfile> is specified, output will go to this file, otherwise, stdout will receive the output.
Changing the forms and attributes shouldn't be a painful process. For a detailed procedure for updating attributes see "Customizing the Attributes file" on page 197.
Just take the server down and add it to the Attributes file. Upon restarting the database, the new states will appear.
Yes & NO! You can use SCCS/RCS commands to get copies of files, but you should NOT use them to lock files for edit or check them back in. Razor needs to handle these operations.
This question often comes up with respect to using the versions program for archiving CAD drawings. Many CAD packages read/utilize/write several files in a single shot, all related to the same single drawing. What users often do is take advantage of the before and after scripts to pack and unpack the collection.
Look at $RAZOR_HOME/examples/intro.before. Be sure to modify your Actions file to refer to this file.
Make sure that the startup directory for versions properties is a valid directory. Select Edit from the versions tool menu and select Tool Properties. In the Versions Props dialog, verify the setting of Startup Directory.
You can rename file control groups using the UNIX move ("mv") command. BEFORE you rename groups, however, there are a couple of things to consider.
If the above does not apply to your situation, here are the steps you should follow:
# razor down # rm $RAZOR_UNIVERSE_DIR/Mapping # cd $RAZOR_UNIVERSE_DIR/DOMAIN_01 # mv <old group name> <new group name> # mv <old group name>##Threads <new group name>##Threads # razor up
... a new Mapping file will be generated
Typically, only the file owner can check files back in or uncheck them. BUT, Razor allows users defined in the RAZOR_ADMIN role to check files back in that they did not check out. Refer to "Checking files back in" on page 92 for the specifics.
Yes. Check out "Injecting existing SCCS/RCS investments" on page 86 for the details.
Yes, along with dozens (if not hundreds) of other things, all via X resources. We'd encourage you to check out Appendix C of this manual set, but to answer your question, just put lines similar to the following in your ~/.Xdefaults file.
Issues*title: Happy Issues*iconName: Silly
issues -no_color &
Issues*maxWidth: nnn Issues*maxHeight: nnn Versions*maxWidth: nnn Versions*maxHeight: nnn Threads*maxWidth: nnn Threads*maxHeight: nnn
Where `nnn' would be the maximum width/height in pixels that you'd want to be able to resize the window.
Emulation of Emacs behavior can be enabled via Xdefaults. Take a look at the file $RAZOR_HOME/examples/Xdefaults.sample for more details.
This means that you either have too little memory on your X workstation or you are running another program (like Netscape) that has hogged some of the colors that Razor wants. Quit the piggy program, run the Razor program, then re-run the piggy program. If you want to run in black & white, see "Not enough color" on page 48 for an explanation.
|
|
|
|
|
(Part 6 of 7 for this section) (Generated 09/13/99 at 18:25:10) |
|||
|
Copyright Tower Concepts http://www.tower.com Voice: 315-363-8000 Fax: 315-363-7488 support@tower.com sales@tower.com |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |