Viking Software Solutions

LifeWorks: Added Features

The release level is changed whenever a customer is sent a new version with a bug fix, and is frequently for only the platform used by the customer. Many fix level releases will not include any new features. Also, we are continually adding diagnostic aids to enable us to more rapidly pinpoint the cause of problems that may be encountered by customers. More detail is found in the on-line directory $W/docs/ in the files README.NEW and README.DIF, and also in $W/text/lwoptions.doc.

LWK01.24 (including interim releases LWK01.23.1 through LWK01.23.5)

Options were added to LWdb to set, clear, or test for the database lock. This is used internally, but might be used within customer developed scripts or by administrators during maintenance operations.

Tape Handling

Several options (see $W/text/lwoptions.doc) to deal with characteristics of some 9 track tape drives have been added.

New Problem Determination Aid

A new program, LWtraceon, has been added. It is intended only to be used under the direction of a LifeWorks technical support person.

DUP Key in Key Verify

An optional ability, via an lwoption keyword, to change the behavior of the DUP key in Key Verify mode has been added.

In the situation where an operator is in Key Verify and uses the Field Forward key to open the field for correction, normal operation for the DUP key is to copy characters (from the present cursor position through the end of the current field) from the previous record in the batch that contained those record positions. In the first record of a batch, use of the DUP key will cause a VERIFY ERROR message to be displayed. If no previous record in the batch contained those record positions, unpredictable results can occur.

If NODUPPREV is added to $W/text/lwoptions, use of the DUP key will be inhibited in the situation where a field is opened for correction in Key Verify.

LWK01.23

Including interim releases LWK01.22.1 through LWK01.22.4)

Supervisory Command Logging

Logging of supervisory command execution has been implemented. It is now possible to turn on logging of Supervisory commands by adding LOGSUP to $W/text/lwoptions. Commands are logged to the UNIX file $W/text/log.sup.

Broadcast Message Logging

It is now possible to implement the logging of broadcast messages by adding MODEBLOGSUP to $W/text/lwoptions. The messages are also logged to the UNIX file $W/text/log.sup.

Security Changes

In addition to certain fixes (see Recent Fixes) addressing LifeWorks Data Entry security, there have been some product changes:

  • The default system behavior controlling the execution of Supervisor Functions has been changed, loosening control for Supervisors (as defined in the OPERATORS,USERID file, and tightening it for Non-Supervisors. Adding NOSUPERVISOR to $W/text/lwoptions will revert to the previous behavior. See the newsletter and technical note on security for details.
  • Modes M and I will now follow the rules for Supervisor Functions. Adding EDANYONE to $W/text/lwoptions will allow any user to use these modes as was done in prior versions.
  • $EDIT will now require the operator to provide the password for a job when OPEN or CREATE statements involve batches of a password-protected job. As it may be possible for this change to cause a problem with an existing customer procedure, adding NOEDITPASS to $W/text/lwoptions causes $EDIT to operate as it did prior to this release.

Changes Regarding “lwoptions”

A change has been made to 1) prevent an update from overwriting a customer’s $W/text/lwoptions file, and 2) to speed up processing. The LifeWorks Data Entry distribution will now contain $W/text/lwoptions.doc which documents all the available options. The installation/update process will now check for an existing $W/text/lwoptions file. If none exists, then an empty file is created. If one exists and is from a release prior to this one, comment and blank lines are removed. If one exists and is from this release or later, it is not changed.

Using the Sort Program of the Operating System instead of LifeWorks Data Entry

By adding USEOSSORT to $W/text/lwoptions, /usr/bin/sort will be used when $SORT is run rather than $W/bin/LWsort. The OS sort program may be more flexible in its use of temporary space than LWsort which only uses space in /var/tmp and will fail if there is not enough temporary space available.

New E Show Mode

A new Show Mode, E, has been added to LifeWorks Data Entry. It allows viewing of the last 200 records of the LifeWorks Data Entry log file.

LOCATE.FMT

File $W/formats/LOCATE.FMT, a new utility routine, has been added to the product. It is a $EDIT routine that can be used to search for various commands associated with format language element definitions in order to make it easier to migrate to a new LifeWorks Data Entry system, or to just find “misplaced” format code, etc.

TIMEOUT in lwoptions

When LifeWorks Data Entry sends messages to various related background processes, it sets a clock to timeout waiting for a reply in case the other process fails. The default value for the timeout is 60 seconds. The processes this timeout applies to are LWbcman, LWixman, LWlock and LWlant. To change the timeout value, add a line to $W/text/lwoptions in the following format (replacing nnnn with the number of seconds to wait for a reply):

TIMEOUT=nnnn
A value of 0 means to use the built-in default value. Values less than the default are not recommended.

New Features for Troubleshooting

Several features have been added to aid in system troubleshooting efforts. A $DEBUG supervisor command has been added to allowed the debugging toggles to be manipulated in command strings. See $W/toolbox/READMEdebug for details. An administrative user, running as “root” may want to run tests as a normal LifeWorks Data Entry user (LifeWorks Data Entry provides some special treatment for a root user). A NOTROOT statement may be added to $W/text/lwoptions and a new toggle, “#” in Mode D has been added, to accomplish this.

LWK01.22

New Utility Program

A new utility, $W/toolbox/checklog has been added to examine the log or LWtsdump files for errors. Documentation may be found in $W/toolbox/READMEtoolbox. This can be used by administrators to get an early warning of potential problems.

New Lock File

A new lock file, “/install/LWKLOCK” was established. It will be set when doing an install or upgrade. It will prevent works, works2 or LWlant from running. It was sometimes difficult to upgrade a system with a site license if any of the other systems were running. Also, when an administrator would run LWmaint to stop works in preparation of an upgrade, a remote user could start works going again. This lock will be reported by the $W/toolbox/locks utility. It can be set and cleared manually by administrators for other purposes, such as running end of day processing.

LWK01.21

DISAM

LifeWorks Data Entry now uses a newer version of the underlying indexed file system. Previously it used version 3.25. It now uses DISAM96. The vendor indicates that there are significant performance improvements—see the comparison.

Mode D

Mode D, for debugging use only, now displays “Do you want to enter debug mode? [y/{n)]” to prevent operators from accidentally enabling the debug operation.

Upgrade and lwoptions File

During an upgrade installation, the $W/text/lwoptions file is now copied to /var/tmp/lwoptions.preupgrade, and a message is displayed at the end of LWpostinstall if there are differences between it and the newly installed file.

New Utility Programs

Three new programs have been added to $W/bin. LWtsdump is used to collect a wide variety of trouble shooting information in the event it is needed by LifeWorks Software engineering to solve a reported problem. LWmw and LWview are for use with the MultiWorks feature.  See $W/toolbox/READMEtoolbox for additional information.

LWK01.20

at386

Termcaps were added to support the UnixWare console. The environment variable TERM must be set to the value “at386”.

LWTABINLZ: Altered the Operation of the Field Forward Key

Before release LWK01.20, if the FIELD FORWARD function key (usually the TAB key on most keyboards) was pressed in a Left Zero field, the cursor went to the next field, potentially violating the Left Zero field format. This was fixed in release LWK01.20 so that the FIELD FORWARD key is inhibited in Left Zero fields unless it is in the first position of the field.

A new LifeWorks Data Entry flag has been created named LWTABINLZ. If it is enabled, it will cause the FIELD FORWARD function key to be treated as the RETURN function key in Left Zero fields.

This feature can be enabled for all users of a LifeWorks Data Entry partition by enabling the LWTABINLZ flag in the $W/text/lwoptions file for that partition. This feature can be enabled on an individual user basis by enabling the LWTABINLZ flag in individual $HOME/.lifeworks Data Entry files.

LWK01.19.1

MSFPPASS: User Control of When MSFP Commands Execute

MSFP elements in format code normally only execute in new records or in pass 2 of Key Verify. We have now added a feature to LifeWorks Data Entry to allow the customer the ability to enable the execution of MSFP format code elements at other times as well, as described below. This feature is enabled through the use of the variable named MSFPPASS in the $W/text/lwoptions file.

Setting MSFPPASS=2 will cause MSFP commands to be executed in existing records in pass 2, regardless of operating mode (Entry, Find, Verify), as well as in new records.

Setting MSFPPASS=1 will cause MSFP commands to be executed in existing records in both pass 1 and 2, regardless of operating mode (Entry, Find, Verify), as well as in new records.

Setting MSFPPASS equal to something other than 1 or 2 will cause an error to be logged and the feature to be ignored. Behavior will revert to the normal default.

EXITB, a New Format Command

A new Format Code command element has been created: EXITB. This command allows the format programmer to force a batch to be exited.

EXITB will cause the format code to behave as if the operator had pressed the EXIT (Mode) key. It will also cause the accompanying message in quotes to be displayed on the message line and the operator must press the RESET key to acknowledge the message. After pressing the RESET key the operator must select a new operating mode.

The syntax for the EXITB command is: EXITB “message”.

Usage Notes:

  • The message in quotes can be a maximum of 80 characters.
  • Either single or double quotes can be used, but the opening and closing quotes must be of the same type.
  • EXITB will override the MODE# command if it is in effect.
  • EXITB is effective regardless of the operating mode (Entry, Find, or Verify) in effect.
  • EXITB is effective regardless of the pass (1, 2) in effect.
  • No space is allowed between EXITB and the opening quote of the message to be displayed.
  • EXITB normally would be in a conditional statement, otherwise the format could never complete.
  • The current record, if any, is not (re)written to disc. The format is aborted, and pass 3 does not occur.

Enhanced Mode P

There has been a change in the implementation of Mode P,D (for Displaying and Changing Print Definitions). Formerly, Mode P,D would only Display information. Any changes had to be made via the Menu System or $SETPRINT commands. Now Mode P,D will allow changes to be made. If OPERATORS,USERID is in effect, then the user must be defined as a Supervisor to make changes.

LWK01.19

Maximum number of LifeWorks Data Entry users allowed per system (node) is raised to 255 from 199.

LWK018.4

tm.029: Termcaps Added for “029” Emulation for the “tm220” Terminal

The environment variable TERM must be set to the value “tm.029” and an entry in the “terminfo” database must be created.

LWK01.17.2

Upgrade installation process added. No longer need to first remove the product in order to upgrade to a new version.

LWK01.17.1

Pseudo Nodes

In conjunction with MultiWorks, allows communication between partitions just like between systems. See separate documentation.

wy.029

Termcaps were added to provide “029” emulation for Wyse 60 terminals with enhanced PC keyboards. The environment variable TERM must be set to the value “wy.029” and an entry in the “terminfo” database must be created.

On-Line “Keys” Tool

The “keys” tool, to assist in termcap modification, found in $W/toolbox is now available via the “debug” mode (Mode D—see $W/toolbox/READMEdebug) as Mode DK.

LWK01.17

Ft45 Support

Added download program compiled for all platforms. See the $W/text/termcap/tic/term/READMEterm file.

Generalized Tape Support

Tape support has been generalized. In previous releases, all tape support, except LWbackup and LWrestore, was only available for 9-track devices, and would only function on Motorola 88K platforms. Now $TAPE and MSFP operations may be applied to SCSI tape devices, 9-track and other types supported by the OS. Bear in mind that device characteristics may restrict certain operations. For example, QIC streamer tapes cannot be used with variable length blocks. See the $W/docs/README and README.DIF files.

The media size of the tape (backup) device is no longer used.

Standard Install for AIX

This release now uses the operating system standard installation tools.

LWK01.16a

Limited National Character Support

Limited support for national characters has been added. It assumes that the keyboard and display use octal values greater 0200, and that the data to be stored on disk is a different value. The changes made allow sections 2 and 4 of the $W/text/termcap files to be modified as in this example:

For the character Æ, the keyboard and display value is 0344 and it is to be stored as the data character 0173—change section 4 at value 0344 to [0344 0173]—change section 2 at value 0173 to [0173 0344]. This feature is enabled by uncommenting the line containing the word SPECIALCHARS in the file $W/text/lwoptions. See $W/docs/README and README.DIF files for more information.

LWK01.15

Network Licensing

This release introduces network (site) licensing. A separate document is included if a network license was ordered.