Eloquence A.05.01 Release Notes

Unsupported features implemented with A.05.01

The following enhancements are available with Eloquence A.05.01, but are not (yet) supported.

PRINTER IS Statement
EDITOR Statement
RCS integration
RCS integration scripts
ctd260 utility

PRINTER IS Statement

The PRINTER IS statement has been enhanced to allow usage of HP-UX pipes. If you specify a pipe char in the first character of a PRINTER IS filename, the remaining line is executed as a pipe. This makes it possible to dynamically use HP-UX capabilities.

The following example will create a pipe to the lp program:

   PRINTER IS "|lp -dlj -o2"

Please note:

This does NOT affect printers assigned by eloq.config etc.
This may cause a compatibility problem, if you used spool file names starting with a pipe character.

EDITOR Statement

EDITOR [First_line_no [,Inc]]

The EDITOR statement saves the actual program in a temporary file without line numbers and calls a HP-UX editor program. After the editor program finished, the actual program is re-read from the temporary file.

The HP-UX editor called is defined by either the EQ_EDITOR or the EDITOR environment variable. /usr/bin/vi is used as a last resort.

If First_line_no argument is present, a $LINE directive is included at the top of the editor file. If file is re-read from temporary file, the directive is used to determine how the program should be renumbered.

First_line_no specifies the first line number to use, Inc the line number increment. See notes about store utility for details.

Please Note:

The EDITOR statement is "execute-only". So you can`t include it in a program.
Line numbers are simply cut. There is no consistency checking, if they are referenced line numbers (it's common programming practice to avoid using line numbers).
The EDITOR statement is only available in DVP product.

This statement is not yet supported, because we have to proove, if it's sufficient to just cut the line numbers instead of checking for used ones. Because this statement is particular useful, it's been included in Eloquence A.05.01. A supported EDITOR statement is scheduled with the next Eloquence release.

RCS integration

Support of Revision Control Systems is an emerging need in software development. While it's possible to interface Eloquence to an RCS system by using script files, there is no integration into the interactive development environment.

The following statements provide a temporary integration of a RCS into the Eloquence devlopment environment:

RCS GET "file" [,"opt"] [;First_line_no [,Inc]]

Executes /usr/eloquence/rcs_get.
Retrieve a program from RCS system. If the opt argument is present, it is passed to the RCS script.
First_line_no specifies the first line number to use, Inc the line number increment.

RCS SAVE "file" [,"opt"] [;First_line_no [,Inc]]

Executes /usr/eloquence/rcs_save.
Saves the actual program in memory in the RCS system. If the file is checked out again by the RCS system, it is re-read by Eloquence. If the opt argument is present, it is passed to the RCS script.
If a program is read, First_line_no specifies the first line number to use, Inc the line number increment.

RCS MERGE "file" [,"opt"] [;First_line_no [,Inc]]

Executes /usr/eloquence/rcs_merge.
Merges the changes between former program revisions with the actual program in memory. First_line_no specifies the first line number to use, Inc the line number increment.

Example RCS session

Prerequisites:

Install the rcs interface scripts in /usr/eloquence and make them executable.
Create a directory named RCS in a directory where your programs reside.

Enter a sample program and store is as "SAMPLE,VOL"

   10 ! SAMPLE PROGRAM
   20 ! @(#)$Header$
   30 DISP "This is $Revision$"
   40 END

Execute the following steps:

Create an initial revision:
```
   LOAD "SAMPLE,VOL"
   RCS SAVE "SAMPLE,VOL","-l";1000,10   
```
Enter initial program description
Due to the -l argument, the program is checked out again (locked) and re-read by Eloquence. This will create a revision 1.1 of the test program.
Create another program revision. Change a program line in the sample program and check it into the RCS system again.
```
   10 ! SAMPLE PROGRAM - 2ND RELEASE
   RCS SAVE "SAMPLE,VOL"
```
Enter description of changes
This will create a revision 1.2 of the test program.
Load first revision again.
```
   RCS GET "SAMPLE,VOL","-r1.1";1000,10   
```
This will retrieve revision 1.1 of the test program.

Please Note:

All RCS statements are "execute-only". So you can`t include them in a program.
Line numbers are simply cut. There is no consistency checking, if they are referenced line numbers (it's common programming practice to avoid using line numbers).
The RCS statements are only available in DVP product.
Please refer to rcs(5) for an introduction to the RCS system.

These statements are considered temporary (experimental, not yet supported). We decided to include them with Eloquence A.05.01, because they are are a first approach to get familiar with RCS and we would like to have some feedback to implement your real needs. A supported RCS statement is scheduled with the next Eloquence release.

Example RCS integration scripts

The RCS integration scripts must be installed in the /usr/eloquence directory. Examples are provided below.

Example rcs_get script file

#!/bin/ksh
#
# usage: rcs_get file args
# The script should extract the requested file from the RCS system.

if [ $# -lt 1 ]
then
   exit 2
fi

file=$1; shift

co $* $file
rc=$?
#if [ $rc != true ]
#then
   echo "Please press return to continue \c"
   read
#fi
exit $rc

Example rcs_save script file

#!/bin/ksh
#
# usage: rcs_save file args
# The script should update the given target file in the RCS system.

if [ $# -lt 1 ]
then
   exit 2
fi

file=$1; shift

ci $* $file
rc=$?
#if [ $rc != true ]
#then
   echo "Please press return to continue"
   read
#fi
exit $rc

Example rcs_merge script file

#!/bin/ksh
#
# usage: rcs_merge file args
# The script should merge the given target file with the RCS system.

if [ $# -lt 1 ]
then
   exit 2
fi

file=$1; shift

rcsmerge $* $file
rc=$?
#if [ $rc != true ]
#then
   echo "Please press return to continue"
   read
#fi
exit $rc

ctd260 utility

The ctd260 utility is used to read HP260 media.
The undocumented -f commandline flag enables you to unpack HP260 FVBACK files.

FVBACK is a HP260 utility program to backup a whole disc into a set of backup files. The FVBACK file format is closely related to the HP260 media format.

To unpack an FVBACK archive, you have to execute the following steps:

Transfer all FVBACK files from HP260 media onto local disc
FVBACK files are of type BKUP, which are normally ignored by ctd260. In order to extract them, you have to specify the -t BKUP argument to ctd260.
Unpack the FVBACK files
To unpack the FVBACK files, specify the -f commandline flag to ctd260 and the file name of the first FVBACK file. The file name of subsequent backup files are derived from the initial backup file name.
For example:
```
      You have 3 FVBACK files:
         FVBFL.BKUP, FVBFL2.BKUP, FVBFL3.BKUP

      ctd260 -f -x FVBACK.BKUP
```
This will unpack all files, contained in the three backup files.

This feature is considered unsupported because older revisions of FVBACK may have created bad FVBACK files, so ctd260 may not be able to unpack them.

Please contact webmaster@marxmeier.com if you have any questions or suggestions regarding this service.
(c) Copyright 1995 Marxmeier Softwareentwicklung
Last update: 95/08/22