PANTT changes from edit 232 thru 252




1.0  NEW FEATURES


     1.  The OUTPUT PATH-CHARACTER listing now includes  the
         completion date of each task with a path character.

     2.  A warning is generated if dates are  output  and  a
         schedule pass is required.

     3.  Write access is no longer required to read a  PANTT
         database.   If  one  attempts to access a read only
         database, a warning is typed and  the  database  is
         opened for reading.

     4.  There are two  new  commands  which  lets  one  add
         arbitrary  attributes  to a task.  The commands are
         ATTRIBUTE and LONG-ATTRIBUTE.  An attribute is just
         something  you  want  remembered about a task.  For
         example:
         TASK DATA: ATTRIBUTE (NAME IS) BUDGET (VALUE) 35K
         TASK DATA: ATTRIBUTE (NAME IS) COST-CENTER (VALUE) 34M
         TASK DATA: LONG-ATTRIBUTE (NAME IS) COMPLETION-CRITERIA
         VALUE OF ATTRIBUTE (<ESC> WHEN DONE)
                         ALL DEMO INFORMATION IS IN FILE.
         $
         TASK DATA: LIST
         % Some dates may be wrong. Use SCHEDULE command to update all dates

         1/1
                 TASK DESCRIPTION: DEMO

                 SLACK: 0
                 ACTUAL STARTING DATE: NOT SPECIFIED
                 ACTUAL COMPLETION DATE: NOT SPECIFIED
                 MINIMUM STARTING DATE: NOT SPECIFIED
                 ESTIMATED STARTING DATE: NOT SPECIFIED
                 ESTIMATED COMPLETION DATE: NOT SPECIFIED
                 ESTIMATED TASK LENGTH (IN DAYS): 0
                 TIME SPENT ON TASK: 0
                 BUDGET: 35K
                 COST-CENTER:    34M
                 COMPLETION-CRITERIA:

                         ALL DEMO INFORMATION IS IN FILE.

                 DEVELOPER          RATE      HANDICAP
                 S-FOONLY            1         1


                                                      Page 2


2.0  CHANGES TO EXISTING FEATURES


     1.  The  OUTPUT  SCHEDULE  command  now  only  includes
         incomplete tasks.

     2.  The SET SCHEDULE-DATE answer is  now  part  of  the
         database  and  remembered from one run to the next.
         There is a new command called DELETE  SCHEDULE-DATE
         to undo the effect of a SET SCHEDULE-DATE.




3.0  BUG FIXES


     1.  Critical paths are now  correct  even  if  weekends
         come between tasks.

     2.  If a project has already started (has actual  start
         date) and there is a TIME-TO-DATE and no developer,
         the end date was wrong.

     3.  PANTT died a horrible death if any string  was  too
         long.   Added  some  code to defend PANTT from long
         strings.

     4.  Plotter software has a limit of 15  bits  worth  of
         X,Y  data  (because  PDP-11  stores  X,Y  as signed
         numbers in 16 bits).  Output warning if  data  will
         overflow.   The  data  is  written  anyway (in case
         someone  fixes   the   plot   software),   however,
         attempting to plot it will produce trash.

     5.  "?" to name of database did not provide help.




4.0  INTERNAL CHANGES


     1.  Store TSKLST index in task block.  Use  the  stored
         value to speed up  LPCHK,CKAV1A,  and FNDTKI.  This
         has a dramatic effect for a large number of tasks.

     2.  Speed up scheduler by remembering that there are no
         loops.