Viking Software Solutions

LifeWorks: Release Notes (LWK01.24)

New Installs

  • For any system, prior to a new install make sure that a user and group named “works” have been defined on the system. You must be root to perform the install and have the environment variable LANG set to either “en_US” or “C”. LifeWorks Data Entry assumes the use of /bin/sh or ksh and will modify the “.profile” files of root and all users. The directory path in which the LifeWorks Data Entry software is installed is stored in the “W” environment variable (you will see references to $W). In addition, the installation creates the directory and file “/install/works” among other things. You should also review SRG section 3.1 on Known Problems and issues, and section 3.3 on Technical Tips, and similar pages on the web site.
  • For SVR4, if you received the software on diskettes or from the Internet, use this procedure prior to installation with pkgadd (be aware that the uncompressed “lwk” file is up to 16.6MB and that pkgadd will want to use space in /var/tmp to process the install file): Note: The last letter (the “_” in the names below) of the file name represents the platform: s=Sun/SPARC, u=UnixWare, m=Motorola 88K.
    1. Create an empty directory named lwk and cd to it (e.g. /tmp/lwk). Move the lwk124_.gz and gunzip files obtained from the ftp site, or for diskettes do: cpio -ivc < /dev/rfffffff  [ where rfffffff is the “raw” diskette device name ]. This restores the files gunzip, sum1.24_ and lwk124_.gz. The “sum” document contains listings of the “ls” and “sum” commands run on the “lwk” file before and after compression with “gzip”.
    2. ./gunzip lwk124_.gz—this will result in the file lwk124_. Run the “pkgadd” utility as root and specify the full pathname to the uncompressed file (for example: pkgadd –d /tmp/lwk/lwk124_). After the successful install, you can delete the file lwk124_ and its directory, although you should save the gunzip program by moving it to a directory such as /usr/bin. Follow instructions below under “Additional Installation Steps”
  • AIX uses the standard operating system installation tools. It will install into /usr/lpp/lwk (this will be $W). Note: /usr/sbin/shutdown is modified to run the LWshut script. Removal of LifeWorks Data Entry will remove the changes. AIX is distributed on diskettes or from our ftp site. Use the following procedure to install:
    1. Create, and change to, a new directory in a file system with more than 22MB of free space (note that the software will be installed into /usr/lpp so it is advisable to use a different file system than /usr).
    2. Move the lwk124_p.gz and gunzip files obtained from the ftp site, or for diskettes do: cpio -ivc < /dev/rfd0 [ where rfd0 is the “raw” diskette device name ] This restores the files gunzip, sum1.24p and lwk124p.gz. The “sum” document contains listings of the “ls” and “sum” commands run on the “lwk” file before and after compression with “gzip”.
    3. ./gunzip lwk124p.gz—this will result in the file lwk124p.
    4. Run smit or smitty and choose the software installation menus for installing new software at the latest level (install_latest). When asked for the device or directory, specify the full path to the directory where lwk124p is located. The next dialog has an entry “SOFTWARE to install” which defaults to “all_licensed”. You must produce a list with the GUI button or the appropriate key, then select one of the two lines displaying the LifeWorks Data Entry package. Defaults for the other entries can be used, but you may wish to review them and decide for yourself.

Additional Installation Steps

After the software is initially installed, run $W/bin/LWpostinstall. The remainder of this document provides a summary description of the rest of the installation steps.

  • LWpostinstall will first ask for the license information. If you do not enter the license codes when requested, a DEMO license is established.
  • Next LWpostinstall runs another script to set up users. This can be done later by running the script LWusers.

LWpostinstall will do some other tasks automatically. There are two more steps you must do before you can run LifeWorks Data Entry.

  • You need to create the initial database by running LWconfig (NOTE: you must be using a $TERM value that it supported by LifeWorks Data Entry in order to run LWconfig - see Terminal Support below). If your environment is setup properly, it should contain “W=/usr/lpp/lwk” (for AIX, otherwise what was selected during the install script) and PATH includes $W/bin and $W/ya/bin. After you have figured out the solution to which terminal to use, run LWconfig and select the Database menu item (D then F8 key in vt220 emulation, or keypad Enter on xterm - the bottom of the display tells which keys to use to execute the selected menu item and to exit the menu). Enter the name of a file system (a directory is okay, but a status display (Show-A) that uses “df” will not be able to display file space information) where you want the LifeWorks Data Entry database to live - it will be created when you press the F8 or keypad Enter key. When back at the main menu, select the Update menu item to write out the config file.
  • Finally, you need to set proper permissions and ownership on the new database by running LWaccess. You will then be able to run “works” to start LifeWorks Data Entry going. There are a number of README files in the $W/docs directory which also contains a copy of the Software Release Guide in postscript.

Terminal Support

You might be able to plug an existing Motorola terminal (in $W/text/termcap/tic are files that can be used with the “tic” command to create the required terminfo database entry), or use vt220 via PC terminal emulation. It is also possible to use “aixterm” for a graphical AIX console, or “xterm” for a graphical Solaris or UnixWare console, but you would first need to setup keyboard mappings. We can talk you through this if that’s what you’d like to do. There is considerable information on this in the $W/text/termcap directory with README files on general termcap issues, and specifics for xterms (the UnixWare xterm will not display as well as we would like, but it can be used) and 029 support.

Upgrades >>