Viking Software Solutions

LifeWorks: Platform-Specific Configuration for RJE

EXPRESS, from CNT, is available at three different release levels, corresponding to each of the supported platforms for LifeWorks Data Entry. There are some differences in the way each version of EXPRESS must be configured for use with LifeWorks Data Entry. The LifeWorks Data Entry configuration instructions are not affected.The RJE Workstation Manual is being revised to cover this information.


The version of EXPRESS from CNT for AIX platforms is 3.1.

EXPRESS uses a “Job Profile” as the mechanism to send data to the mainframe. A Job Profile must be associated with a specific user. As all operators of LifeWorks Data Entry run as the user “works”, the configuration instructions are to associate user works with a specifically constructed Job Profile. See the note on Page 3-2 and the discussion of the Job Profile on Page 3-5. For version 3.1 there is an owner field in the Job Profile definition that must be set to “works”. It is no longer necessary (and may not even work) to run “express” as the user works to define the special Job Profile.


The version of EXPRESS from CNT for Solaris 2 (SPARC) platforms is 2.1.3. This version should be configured as specified in the documentation.


The version of EXPRESS from CNT for UnixWare 2.1 is 2.1.2. NOTE: EXPRESS is NOT available for UnixWare 7.

LifeWorks Data Entry executes the “exrje” command for each $HASP $DATA processed. Before executing the command, RJE formats the data and writes it to the $W/RJE/pipes directory with a specific name. The “exrje” command queues a request to send the data. A successful execution means that the job has been queued by EXPRESS, not necessarily sent yet. If a subsequent $HASP $DATA is executed and the same filename is used, the prior data could be overwritten before it is sent.

An EXPRESS feature that was introduced in version 2.1.3, and therefore not available for UnixWare, allows RJE to create a unique UNIX filename for each $HASP $DATA and to pass this unique name in the “exrje” command.

Version 2.1.2 required that all Job Profile information be defined interactively. The data to be sent can be defined (“Source Type”) as a specific File or a specific Pipe file. The RJE Workstation Manual, which is currently for version 2.1.3 or later, specifies using a File with the “Source Name” of “%1”. In an attempt to provide a satisfactory solution with the limited facilities of EXPRESS 2.1.2, we have provided alternative solutions.

  • The default for UnixWare 2.1, is to use “Source Type” of “File” with “Source Name” being the full pathname to $W/rje/pipes/jesname.RD0 (where “jesname” is the named of the Job Entry Station defined in EXPRESS). As noted above, this same filename will be written for each $HASP $DATA command, so if multiple occurrences are run in a command string, with no intermediate delay, RJE may write a new file before the previous one is sent by EXPRESS.
  • An environment variable, LWRDPIPE (see $W/docs/README.ENV), if present in the execution environment of RJE, instructs RJE to write a pipe file instead. The “Source Type” in the Job Profile must be set to “Pipe”, but the “Source Name” is exactly the same. The RJE logic will look to see if an existing pipe file with this name has a zero length before writing it again.
  • An optional delay time can be specified while RJE loops after finding an existing, non-zero length, pipe file. See $W/text/lwoptions.doc for the entry on RJEWAITPIPE. This would be used only if RJE reported errors waiting for the length to go to zero and you wanted to give EXPRESS more time to read the pipe file.