head     56.3;
access   paws bayes jws quist brad dew jwh;
symbols  ;
locks    ; strict;
comment  @# @;


56.3
date     93.01.27.13.40.05;  author jwh;  state Exp;
branches ;
next     56.2;

56.2
date     93.01.27.12.15.07;  author jwh;  state Exp;
branches ;
next     56.1;

56.1
date     91.11.05.10.02.43;  author jwh;  state Exp;
branches ;
next     55.1;

55.1
date     91.08.25.10.37.33;  author jwh;  state Exp;
branches ;
next     54.1;

54.1
date     91.03.18.15.38.03;  author jwh;  state Exp;
branches ;
next     53.1;

53.1
date     91.03.11.19.36.20;  author jwh;  state Exp;
branches ;
next     52.1;

52.1
date     91.02.19.09.22.27;  author jwh;  state Exp;
branches ;
next     51.1;

51.1
date     91.01.30.16.21.04;  author jwh;  state Exp;
branches ;
next     50.1;

50.1
date     90.10.29.16.34.55;  author jwh;  state Exp;
branches ;
next     49.1;

49.1
date     90.08.14.14.18.34;  author jwh;  state Exp;
branches ;
next     48.1;

48.1
date     90.07.26.11.25.08;  author jwh;  state Exp;
branches ;
next     47.1;

47.1
date     90.05.14.11.11.53;  author dew;  state Exp;
branches ;
next     46.1;

46.1
date     90.05.07.08.59.03;  author jwh;  state Exp;
branches ;
next     45.1;

45.1
date     90.04.19.16.06.48;  author jwh;  state Exp;
branches ;
next     44.1;

44.1
date     90.04.01.22.27.55;  author jwh;  state Exp;
branches ;
next     43.1;

43.1
date     90.03.20.14.17.29;  author jwh;  state Exp;
branches ;
next     42.1;

42.1
date     90.01.23.18.00.48;  author jwh;  state Exp;
branches ;
next     41.1;

41.1
date     89.12.22.11.42.26;  author jwh;  state Exp;
branches ;
next     40.1;

40.1
date     89.09.29.12.03.30;  author jwh;  state Exp;
branches ;
next     39.1;

39.1
date     89.09.26.16.48.31;  author dew;  state Exp;
branches ;
next     38.1;

38.1
date     89.08.29.11.39.48;  author jwh;  state Exp;
branches ;
next     37.1;

37.1
date     89.05.12.11.53.25;  author dew;  state Exp;
branches ;
next     36.1;

36.1
date     89.02.06.10.30.46;  author dew;  state Exp;
branches ;
next     35.1;

35.1
date     89.02.02.13.48.54;  author dew;  state Exp;
branches ;
next     34.1;

34.1
date     89.01.23.16.22.31;  author jwh;  state Exp;
branches ;
next     33.1;

33.1
date     89.01.16.11.53.02;  author dew;  state Exp;
branches ;
next     32.1;

32.1
date     89.01.10.12.03.33;  author bayes;  state Exp;
branches ;
next     31.1;

31.1
date     88.12.14.18.24.10;  author bayes;  state Exp;
branches ;
next     30.1;

30.1
date     88.12.09.14.01.01;  author dew;  state Exp;
branches ;
next     29.1;

29.1
date     88.10.31.15.45.29;  author bayes;  state Exp;
branches ;
next     28.1;

28.1
date     88.10.06.11.11.03;  author dew;  state Exp;
branches ;
next     27.1;

27.1
date     88.09.29.11.55.14;  author bayes;  state Exp;
branches ;
next     26.1;

26.1
date     88.09.28.14.24.01;  author bayes;  state Exp;
branches ;
next     25.1;

25.1
date     88.03.02.09.52.04;  author bayes;  state Exp;
branches ;
next     24.1;

24.1
date     87.08.31.10.27.41;  author jws;  state Exp;
branches ;
next     23.1;

23.1
date     87.08.26.11.18.26;  author bayes;  state Exp;
branches ;
next     22.1;

22.1
date     87.08.17.11.56.52;  author bayes;  state Exp;
branches ;
next     21.1;

21.1
date     87.08.12.14.39.38;  author bayes;  state Exp;
branches ;
next     20.1;

20.1
date     87.07.30.11.50.41;  author bayes;  state Exp;
branches ;
next     19.1;

19.1
date     87.06.01.09.08.09;  author jws;  state Exp;
branches ;
next     18.1;

18.1
date     87.05.20.16.09.20;  author bayes;  state Exp;
branches ;
next     17.1;

17.1
date     87.04.30.11.12.06;  author jws;  state Exp;
branches ;
next     16.1;

16.1
date     87.04.26.16.21.34;  author jws;  state Exp;
branches ;
next     15.1;

15.1
date     87.04.13.10.05.10;  author jws;  state Exp;
branches ;
next     14.1;

14.1
date     87.04.01.16.17.30;  author jws;  state Exp;
branches ;
next     13.1;

13.1
date     87.02.28.19.03.50;  author jws;  state Exp;
branches ;
next     12.1;

12.1
date     87.02.02.13.59.06;  author jws;  state Exp;
branches ;
next     11.1;

11.1
date     87.01.19.10.25.04;  author jws;  state Exp;
branches ;
next     10.1;

10.1
date     86.12.24.11.41.38;  author jws;  state Exp;
branches ;
next     9.1;

9.1
date     86.12.12.15.27.44;  author bayes;  state Exp;
branches ;
next     8.1;

8.1
date     86.11.27.12.34.13;  author jws;  state Exp;
branches ;
next     7.1;

7.1
date     86.11.20.14.51.30;  author hal;  state Exp;
branches ;
next     6.1;

6.1
date     86.11.04.18.41.07;  author paws;  state Exp;
branches ;
next     5.1;

5.1
date     86.10.28.17.30.20;  author hal;  state Exp;
branches ;
next     4.1;

4.1
date     86.09.30.20.23.37;  author hal;  state Exp;
branches ;
next     3.1;

3.1
date     86.09.01.13.08.59;  author hal;  state Exp;
branches ;
next     2.1;

2.1
date     86.07.30.15.23.10;  author hal;  state Exp;
branches ;
next     1.1;

1.1
date     86.06.30.17.36.03;  author danm;  state tmp;
branches ;
next     ;


desc
@Base file for PWS 3.2 release.

@


56.3
log
@
pws2rcs automatic delta on Wed Jan 27 13:14:25 MST 1993
@
text
@

   The hardware needed to run the PASCAL
compiler test suite includes a 9835 with
datacom connected to a 9826 via RS232. The 9835
must have a 9885 disk attached to it and the
9826 must have a 7906 disk attached to it as
well as any kind of printer.

   The software required to run the 9835 can be
found on a 9885 floppy disk. For the 9826 what
is required is an RS232 boot disk (described
elsewhere) and the compiler, filer, editor,
and library that go with it. Also the 7906
platter with all the test programs on it is
needed. One of the volumes on the 7906 platter
is named SYS:. This volume is the one where the
PASCAL system files should reside. Hence before
the system can be run it will be necessary
to make certain first of all that the files
have been transferred and secondly that the new
system volume is set to 17 (or that
SYSTEM.TABLE has been updated).

   In order to run the PASCAL test suite you
should make sure the PASCAL workstation is at
the outer command level; LOAD file PASC1 into
the 9835 and run it.

   The system consists of two BASIC language
programs which run on a 9835. This is to make
it easy to run one without the other. They are
connected via a LOAD statement. The first
program can be found under the file name
PASC1 and the second under the file name
PASC2. PASC1 is the program which will run
the compiler semantics test. This test compiles
and executes a series of PASCAL programs on a
9826 which can be found on four volumes on a
7906 disk platter. These programs are intended
to verify that statements in PASCAL will work
the way that they are intended. PASC2 will
compile a series of PASCAL programs which can
be found on three volumes on the same platter.
These programs will contain examples of correct
and incorrect syntaxes and the programs will
pass if only the proper errors are reported.

   File PASC1 will work with the PASCAL
programs that can be found on the four volumes:
PTX:, PX:, PRTE:, and BX:. The BASIC program
will begin by sending over the RS232 the
keystrokes necessary to create the file which
will contain the results of the test. This file
is created in the editor and the empty file is
written out to file SIREN:DSDRUNS.TEXT. The
program will use all of the volumes, one at a
time. The BASIC program will then tell the
9835 to send the keystrokes to the 9826 which
will cause it to get into the filer and list
all of the files on the first volume. This
list will be sent to the 9835 as well as to the
CRT of the 9826. The BASIC program will store
the list in the string variable B$. The file
names are pulled from B$ by searching for
'.TEXT' and then stepping backwards until a
non-digit-letter character is found. Hence all
file names should contain only digits and
letters, or else FNBadchar in the BASIC program
must be edited. As file names are pulled from
B$ they are put, in alphabetic order, into
Flst$. This is done a screenfull at a time.
After each screen is filled the blank character
is output from the 9835 to continue the
listing. When the end of the list has been
encountered the BASIC program will print a
message giving the number of files on that
volume. After this it will begin to step
through the list of file names. It will first
send the keystrokes to compile the program and
to put the compiled code out to file
SIREN:RJUNK.CODE. In the display area of the
9835 will be a message stating which file is
currently being used. This information can be
used to keep tabs on how far along the test
suite is as well as providing useful
information in case of any problems with the
test suite. The string variable Line$ in the
BASIC program is used to contain the
information for each file as it is processed.
It will contain information as to whether the
PASCAL program didn't compile, had a runtime
error, or whether it executed and what it
printed to the CRT. This information is
gathered by monitoring the 9826 and
interpreting the information picked up in B$.
After Line$ has been filled the 9835 will then
cause the 9826 to get into the editor, call up
file SIREN:DSDRUNS.TEXT, jump to the end and
get into insert mode. The 9835 will the send
down the characters in Line$ one at a time to
the 9826. The reason characters are sent one at
a time is that if they are all sent at once the
9826 loses some of the characters. The editor
file is then saved and the editor exited. Once
all the files from all four volumes have been
compiled and executed (if they will execute),
the file SIREN:XDIFF.CODE is executed. This
program will detect any difference between the
results of the latest run of the test suite,
contained in SIREN:DSDRUNS.TEXT and the results
of the final QA run of the test suite,
contained in SIREN:DSDSAV.TEXT. The file XDIFF
will cause the results of the comparison to be
printed to the PASCAL workstation printer.
These are the results that must be evaluated to
determine the success or failure of the
compiler being tested. The last action the
BASIC program, PASC1, will do is to LOAD the
BASIC file PASC2.

   The BASIC file PASC2 contains the second
half of the compiler verification suite. It is
concerned with the syntax checking that is done
by the PASCAL compiler. This program works with
these three volumes on the 7906 platter: BC:,
PC1:, PC2:. Each of these volumes will have its
own error summary file: SIREN:TBERRS.TEXT,
SIREN:TC1ERRS.TEXT, and SIREN:TC2ERRS.TEXT,
respectively. Each volume also has its own
final QA summary file: SIREN:BERRS.TEXT,
SIREN:CL1ERRS.TEXT, and SIREN:CL2ERRS.TEXT,
respectively. The BASIC program will then cycle
through the three volumes and perform the
following steps. First, it will create the
error summary file in the PASCAL editor.
Secondly it will list the files on the volume
and alphabetize them in the same way as PASC1
did. For every file on the volume it will
perform the following steps. First it will
compile the PASCAL program. The listing from
this program will go to file SIREN:CJUNK.TEXT.
The reason this will happen is that every file
on all three volumes will begin with a $list
'SIREN:CJUNK.TEXT'$ which will put the listing
out to that file. The 9835 will then cause the
9826 to execute the file SIREN:CATCH.CODE. This
program will scan the file CJUNK.TEXT and
detect every instance of the string '>>' which
begins every syntax error report. All of these
lines will then be written out to file
SIREN:CERRS.TEXT by CATCH. The 9835 will then
put the 9826 into the editor, call up the error
summary file, jump to the end, and do a copy
from file CERRS.TEXT. It will then do a Quit,
Save, Exit. After every file on the volume has
been compiled, XDIFF will be run to detect any
difference between the new compiler's syntax
checking and the final QA version.

   Both BASIC programs are structured so that
they will not overflow the keyboard buffer on
the 9826. This is done by outputting a series
of characters and then waiting until some known
string, such as the command line is sent back
on the RS232 to the 9835. This only exception
to this is in PASC1 which steps through Line$
one character at a time to make sure that no
characters are lost. This makes it fairly easy
to step through both BASIC programs by pausing
one machine while continuing the other and then
doing the opposite in an alternating sequence.

   At the end of the test suite the 9826
printer will have listed out any difference
between the final QA version and the current
version. Any difference between the two
versions should be accounted for since it will
be due to some change in the action of the
compiler. For the semantics tests many of the
programs are such that any difference that
might show up will indicate the name of the
file that caused the difference. And if the
file should fail to compile, this will
definitely be indicated. Should it not be
possible to identify the file by what XDIFF
indicates it will be necessary to get into the
editor and use the find command to locate the
string and from that the offending file can be
identified. It will also not be readily
apparent which volume the offending file is on.
Each iteration through the alphabet on the
results file is a separate volume. For the
syntax test both the file name and volume name
would be indicated for all possible
differences. The information printed on the CRT
is for the most part merely to track the test
suite, but in one case it will indicate an
error condition. If the compiler should abort
while trying to compile a file during the
syntax part of the test and put up the restart
message this will be indicated on the 9835 with
a message stating which file bombed the
compiler.

   It is very simple to add tests to the test
suite. For the semantics part of the test
simply make sure that the program makes some
indication of its failure, and make sure that
its output goes to the CRT. For the syntax part
of the test simply make sure that the file
begins with $list 'SIREN:CJUNK.TEXT'$. Should
you fail to do this you will notice that when
this file is compiled by the test suite the
listing will go to the printer and that the
file which was just before this one will have
its error(s) reported twice. After the test
suite has been run it will be necessary to
determine whether the results achieved were
those desired. If they were not then the
compiler will need reform and the QA person
must keep track of what changes to expect in
the future before approval is given to the
compiler. Either way the files produced by the
compiler can be changed into the files to be
compared against for future runs of the QA
system.

   One problem that may be encountered running
the test suite is buffer overflow. This is not
likely to happen on the syntax tests unless a
very large program with lots of errors is added
to the system. The solution is to make the
buffer on the 9835 (B$) larger, or else make
the program smaller (break it into two or
whatever programs). On the semantics tests
however there are some tests originally
developed for the HP1000 that will generate an
excessive amount of output if there is an
error. Should such an error occur B$ may fill
up. The 9826 would keep on running and
overwriting its own buffer in a circular
fashion, but none of the information will be
transmitted. The system will then hang because
it does not receive the string it expects to
see before it will continue. With some
knowledge of datacom it is possible to continue
the test suite, or it may be necessary to
temporarily remove the offending file and rerun
the test suite.

@


56.2
log
@
pws2rcs automatic delta on Wed Jan 27 11:57:27 MST 1993
@
text
@d1 251
@


56.1
log
@Automatic bump of revision number for PWS version 3.25
@
text
@a0 251


   The hardware needed to run the PASCAL
compiler test suite includes a 9835 with
datacom connected to a 9826 via RS232. The 9835
must have a 9885 disk attached to it and the
9826 must have a 7906 disk attached to it as
well as any kind of printer.

   The software required to run the 9835 can be
found on a 9885 floppy disk. For the 9826 what
is required is an RS232 boot disk (described
elsewhere) and the compiler, filer, editor,
and library that go with it. Also the 7906
platter with all the test programs on it is
needed. One of the volumes on the 7906 platter
is named SYS:. This volume is the one where the
PASCAL system files should reside. Hence before
the system can be run it will be necessary
to make certain first of all that the files
have been transferred and secondly that the new
system volume is set to 17 (or that
SYSTEM.TABLE has been updated).

   In order to run the PASCAL test suite you
should make sure the PASCAL workstation is at
the outer command level; LOAD file PASC1 into
the 9835 and run it.

   The system consists of two BASIC language
programs which run on a 9835. This is to make
it easy to run one without the other. They are
connected via a LOAD statement. The first
program can be found under the file name
PASC1 and the second under the file name
PASC2. PASC1 is the program which will run
the compiler semantics test. This test compiles
and executes a series of PASCAL programs on a
9826 which can be found on four volumes on a
7906 disk platter. These programs are intended
to verify that statements in PASCAL will work
the way that they are intended. PASC2 will
compile a series of PASCAL programs which can
be found on three volumes on the same platter.
These programs will contain examples of correct
and incorrect syntaxes and the programs will
pass if only the proper errors are reported.

   File PASC1 will work with the PASCAL
programs that can be found on the four volumes:
PTX:, PX:, PRTE:, and BX:. The BASIC program
will begin by sending over the RS232 the
keystrokes necessary to create the file which
will contain the results of the test. This file
is created in the editor and the empty file is
written out to file SIREN:DSDRUNS.TEXT. The
program will use all of the volumes, one at a
time. The BASIC program will then tell the
9835 to send the keystrokes to the 9826 which
will cause it to get into the filer and list
all of the files on the first volume. This
list will be sent to the 9835 as well as to the
CRT of the 9826. The BASIC program will store
the list in the string variable B$. The file
names are pulled from B$ by searching for
'.TEXT' and then stepping backwards until a
non-digit-letter character is found. Hence all
file names should contain only digits and
letters, or else FNBadchar in the BASIC program
must be edited. As file names are pulled from
B$ they are put, in alphabetic order, into
Flst$. This is done a screenfull at a time.
After each screen is filled the blank character
is output from the 9835 to continue the
listing. When the end of the list has been
encountered the BASIC program will print a
message giving the number of files on that
volume. After this it will begin to step
through the list of file names. It will first
send the keystrokes to compile the program and
to put the compiled code out to file
SIREN:RJUNK.CODE. In the display area of the
9835 will be a message stating which file is
currently being used. This information can be
used to keep tabs on how far along the test
suite is as well as providing useful
information in case of any problems with the
test suite. The string variable Line$ in the
BASIC program is used to contain the
information for each file as it is processed.
It will contain information as to whether the
PASCAL program didn't compile, had a runtime
error, or whether it executed and what it
printed to the CRT. This information is
gathered by monitoring the 9826 and
interpreting the information picked up in B$.
After Line$ has been filled the 9835 will then
cause the 9826 to get into the editor, call up
file SIREN:DSDRUNS.TEXT, jump to the end and
get into insert mode. The 9835 will the send
down the characters in Line$ one at a time to
the 9826. The reason characters are sent one at
a time is that if they are all sent at once the
9826 loses some of the characters. The editor
file is then saved and the editor exited. Once
all the files from all four volumes have been
compiled and executed (if they will execute),
the file SIREN:XDIFF.CODE is executed. This
program will detect any difference between the
results of the latest run of the test suite,
contained in SIREN:DSDRUNS.TEXT and the results
of the final QA run of the test suite,
contained in SIREN:DSDSAV.TEXT. The file XDIFF
will cause the results of the comparison to be
printed to the PASCAL workstation printer.
These are the results that must be evaluated to
determine the success or failure of the
compiler being tested. The last action the
BASIC program, PASC1, will do is to LOAD the
BASIC file PASC2.

   The BASIC file PASC2 contains the second
half of the compiler verification suite. It is
concerned with the syntax checking that is done
by the PASCAL compiler. This program works with
these three volumes on the 7906 platter: BC:,
PC1:, PC2:. Each of these volumes will have its
own error summary file: SIREN:TBERRS.TEXT,
SIREN:TC1ERRS.TEXT, and SIREN:TC2ERRS.TEXT,
respectively. Each volume also has its own
final QA summary file: SIREN:BERRS.TEXT,
SIREN:CL1ERRS.TEXT, and SIREN:CL2ERRS.TEXT,
respectively. The BASIC program will then cycle
through the three volumes and perform the
following steps. First, it will create the
error summary file in the PASCAL editor.
Secondly it will list the files on the volume
and alphabetize them in the same way as PASC1
did. For every file on the volume it will
perform the following steps. First it will
compile the PASCAL program. The listing from
this program will go to file SIREN:CJUNK.TEXT.
The reason this will happen is that every file
on all three volumes will begin with a $list
'SIREN:CJUNK.TEXT'$ which will put the listing
out to that file. The 9835 will then cause the
9826 to execute the file SIREN:CATCH.CODE. This
program will scan the file CJUNK.TEXT and
detect every instance of the string '>>' which
begins every syntax error report. All of these
lines will then be written out to file
SIREN:CERRS.TEXT by CATCH. The 9835 will then
put the 9826 into the editor, call up the error
summary file, jump to the end, and do a copy
from file CERRS.TEXT. It will then do a Quit,
Save, Exit. After every file on the volume has
been compiled, XDIFF will be run to detect any
difference between the new compiler's syntax
checking and the final QA version.

   Both BASIC programs are structured so that
they will not overflow the keyboard buffer on
the 9826. This is done by outputting a series
of characters and then waiting until some known
string, such as the command line is sent back
on the RS232 to the 9835. This only exception
to this is in PASC1 which steps through Line$
one character at a time to make sure that no
characters are lost. This makes it fairly easy
to step through both BASIC programs by pausing
one machine while continuing the other and then
doing the opposite in an alternating sequence.

   At the end of the test suite the 9826
printer will have listed out any difference
between the final QA version and the current
version. Any difference between the two
versions should be accounted for since it will
be due to some change in the action of the
compiler. For the semantics tests many of the
programs are such that any difference that
might show up will indicate the name of the
file that caused the difference. And if the
file should fail to compile, this will
definitely be indicated. Should it not be
possible to identify the file by what XDIFF
indicates it will be necessary to get into the
editor and use the find command to locate the
string and from that the offending file can be
identified. It will also not be readily
apparent which volume the offending file is on.
Each iteration through the alphabet on the
results file is a separate volume. For the
syntax test both the file name and volume name
would be indicated for all possible
differences. The information printed on the CRT
is for the most part merely to track the test
suite, but in one case it will indicate an
error condition. If the compiler should abort
while trying to compile a file during the
syntax part of the test and put up the restart
message this will be indicated on the 9835 with
a message stating which file bombed the
compiler.

   It is very simple to add tests to the test
suite. For the semantics part of the test
simply make sure that the program makes some
indication of its failure, and make sure that
its output goes to the CRT. For the syntax part
of the test simply make sure that the file
begins with $list 'SIREN:CJUNK.TEXT'$. Should
you fail to do this you will notice that when
this file is compiled by the test suite the
listing will go to the printer and that the
file which was just before this one will have
its error(s) reported twice. After the test
suite has been run it will be necessary to
determine whether the results achieved were
those desired. If they were not then the
compiler will need reform and the QA person
must keep track of what changes to expect in
the future before approval is given to the
compiler. Either way the files produced by the
compiler can be changed into the files to be
compared against for future runs of the QA
system.

   One problem that may be encountered running
the test suite is buffer overflow. This is not
likely to happen on the syntax tests unless a
very large program with lots of errors is added
to the system. The solution is to make the
buffer on the 9835 (B$) larger, or else make
the program smaller (break it into two or
whatever programs). On the semantics tests
however there are some tests originally
developed for the HP1000 that will generate an
excessive amount of output if there is an
error. Should such an error occur B$ may fill
up. The 9826 would keep on running and
overwriting its own buffer in a circular
fashion, but none of the information will be
transmitted. The system will then hang because
it does not receive the string it expects to
see before it will continue. With some
knowledge of datacom it is possible to continue
the test suite, or it may be necessary to
temporarily remove the offending file and rerun
the test suite.

@


55.1
log
@Automatic bump of revision number for PWS version 3.25A
@
text
@@


54.1
log
@Automatic bump of revision number for PWS version 3.24
@
text
@@


53.1
log
@Automatic bump of revision number for PWS version 3.24B
@
text
@@


52.1
log
@Automatic bump of revision number for PWS version 3.24A
@
text
@@


51.1
log
@Automatic bump of revision number for PWS version 3.24d
@
text
@@


50.1
log
@Automatic bump of revision number for PWS version 3.23c
@
text
@@


49.1
log
@Automatic bump of revision number for PWS version 3.24b
@
text
@@


48.1
log
@Automatic bump of revision number for PWS version 3.24a
@
text
@@


47.1
log
@Automatic bump of revision number for PWS version 3.23
@
text
@@


46.1
log
@Automatic bump of revision number for PWS version 3.23
@
text
@@


45.1
log
@Automatic bump of revision number for PWS version 3.23C
@
text
@@


44.1
log
@Automatic bump of revision number for PWS version 3.23B
@
text
@@


43.1
log
@Automatic bump of revision number for PWS version 3.23aA
@
text
@@


42.1
log
@Automatic bump of revision number for PWS version 3.23e
@
text
@@


41.1
log
@Automatic bump of revision number for PWS version 3.23d
@
text
@@


40.1
log
@Automatic bump of revision number for PWS version 3.23c
@
text
@@


39.1
log
@Automatic bump of revision number for PWS version 3.23b
@
text
@@


38.1
log
@Automatic bump of revision number for PWS version 3.23a
@
text
@@


37.1
log
@Automatic bump of revision number for PWS version 3.3a
@
text
@@


36.1
log
@Automatic bump of revision number for PWS version 3.22
@
text
@@


35.1
log
@Automatic bump of revision number for PWS version 3.22
@
text
@@


34.1
log
@Automatic bump of revision number for PWS version 3.22
@
text
@@


33.1
log
@Automatic bump of revision number for PWS version 3.22D
@
text
@@


32.1
log
@Automatic bump of revision number for PWS version 3.22C
@
text
@@


31.1
log
@Automatic bump of revision number for PWS version 3.22B
@
text
@@


30.1
log
@Automatic bump of revision number for PWS version 3.22A
@
text
@@


29.1
log
@Automatic bump of revision number for PWS version 3.22b
@
text
@@


28.1
log
@Automatic bump of revision number for PWS version 3.3b
@
text
@@


27.1
log
@Automatic bump of revision number for PWS version 3.3a
@
text
@@


26.1
log
@Automatic bump of revision number for PWS version 3.3 Synch
@
text
@@


25.1
log
@Automatic bump of revision number for PWS version 3.2Y
@
text
@@


24.1
log
@Automatic bump of revision number for PWS version 3.2
@
text
@@


23.1
log
@Automatic bump of revision number for PWS version 3.2P
@
text
@@


22.1
log
@Automatic bump of revision number for PWS version 3.2N
@
text
@@


21.1
log
@Automatic bump of revision number for PWS version 3.2M
@
text
@@


20.1
log
@Automatic bump of revision number for PWS version 3.2L
@
text
@@


19.1
log
@Automatic bump of revision number for PWS version 3.2K
@
text
@@


18.1
log
@Automatic bump of revision number for PWS version 3.2J
@
text
@@


17.1
log
@Automatic bump of revision number for PWS version 3.2I+
@
text
@@


16.1
log
@Automatic bump of revision number for PWS version 3.2I
@
text
@@


15.1
log
@Automatic bump of revision number for PWS version 3.2H
@
text
@@


14.1
log
@Automatic bump of revision number for PWS version 3.2G
@
text
@@


13.1
log
@Automatic bump of revision number for PWS version 3.2F
@
text
@@


12.1
log
@Automatic bump of revision number for PWS version 3.2E
@
text
@@


11.1
log
@Automatic bump of revision number for PWS version 3.2D
@
text
@@


10.1
log
@Automatic bump of revision number for PWS version 3.2C
@
text
@@


9.1
log
@Automatic bump of revision number for PWS version 3.2B
@
text
@@


8.1
log
@Automatic bump of revision number for PWS version 3.2A
@
text
@@


7.1
log
@Automatic bump of revision number for PWS version 3.2l
@
text
@@


6.1
log
@Automatic bump of revision number for PWS version 3.2k
@
text
@@


5.1
log
@Automatic bump of revision number for PWS version 3.2j
@
text
@@


4.1
log
@Automatic bump of revision number for PWS version 3.2i
@
text
@@


3.1
log
@Auto bump revision for PAWS 3.2h
@
text
@@


2.1
log
@Auto bump rev number to 2.1 for sys 3.2e.
@
text
@@


1.1
log
@Initial revision
@
text
@@
