THE WELCH COMPANY
440 Davis Court #1602
San Francisco, CA 94111-2496
415 781 5700
rodwelch@pacbell.net


S U M M A R Y


DIARY: March 17, 2004 07:50 PM Wednesday; Rod Welch

SDS revise method of assigning filenames to new tasks in the Schedule.

1...Summary/Objective
2...Schedule New Task Filenames Being Lost Updated Incorrectly
3...000005 F1 New Task Revise Method of Assigning Filenames
4...008501 Schedule 00 File and Directory Sort
5...008502 Merge Sort List of Files in 00 Directory with List in 00 File
6...Optech Sort Command File for 008501 to Merge and Sort Schedule Files
7...Schedule Maintain Task Filenames in Sync with Files on Disk in 00 Dir
8...Diary Summary Syncronize List with Actual Records on Disk
9...Syncronize Diary Archive Records with Summary Record Descriptions
10...Diary Archive Syncronize Records Diary Summary Record Descriptions


..............
Click here to comment!

CONTACTS 

SUBJECTS
Schedule Changed Method of Developing New Task Filenames Macro 95 in
Planning New Task Filenames Macro 95 in Schedule Based on List in 00
Planning Schedule Changed Method of Developing New Task Filenames Ma
Schedule Task Numbers being Renumbered from 0001 Causing a Big Mess

0706 -
0706 -    ..
0707 - Summary/Objective
0708 -
070801 - Follow up ref SDS 6 0000, ref SDS 4 0000.
070802 -
070803 - Tried to develop a stronger method of creating a unique filename for a
070804 - new task in the Schedule, in order to fix severe problems in the past
070805 - few days.  The solution being tried is to abandon the method developed
070806 - in about 1989 of maintaining a filename at the top of the Schedule and
070807 - managing that number as new tasks are created and others are removed
070808 - from the Schedule, either by archiving performed tasks, or by deleting
070809 - tasks, i.e, the User decides not perform a task.  The new method
070810 - constructs a list of files on the disk and compares that list with the
070811 - list of files already in the Schedule, and then increments the highest
070812 - filename, in order to ensure the new name is always unique and does
070813 - not replicate anything already on the disk, that has somehow gotten
070814 - disconnected from system and Schedule maintenance.  Applied the new
070815 - method to schedule maintenance so there is a uniform method of
070816 - synchronizing the list of files on the disk in the current Schedule 00
070817 - directory with the list in the Schedule 00 file.
070818 -
070819 -            [On 040406 Gary had similar problem. ref SDS 8 O832
070821 -             ..
070822 -            [On 071219 removed call for Maintenance from Schedule File
070823 -            menu. ref SDS 9 U898
070824 -
070825 -
070826 -
070828 -  ..
0709 -
0710 -
0711 - Problem
0712 -
071201 - Schedule New Task Filenames Being Lost Updated Incorrectly
071202 -
071203 - Over the past few days the Schedule 00 file and the 00 directory have
071204 - experienced severe problems, which are addressed with planning to
071205 - revise and add new support, ref SDS 0 5L6I, to the solve the
071206 - following...
071208 -         ..
071209 -    1.  Pending, unperformed tasks were being deleted from the disk.
071211 -         ..
071212 -    2.  Pending, unperformed tasks were being renamed in the 00
071213 -        Schedule file beginning with 0001, so if there were 10 pending
071214 -        tasks, the names were changed to 0002 - 0010.
071215 -
071216 -            [On 040325 worked on this again. ref SDS 7 OG6J
071217 -
071218 -            [On 040406 Gary had similar problem. ref SDS 8 O832
071220 -         ..
071221 -    3.  Since files with the new names did not actually exist, and
071222 -        since the files that did exist were deleted, when a pending
071223 -        scheduled task was opened or converted to a diary to perform
071224 -        the work, the content would be blank.
071226 -  ..
071227 - In addition to these recent problems, there has been another ongoing
071228 - problem since changing the method of assigning filenames on 031125...
071230 -         ..
071231 -    4.  After transferring records and starting to work on a different
071232 -        computer, when a new task is created rather than display the
071233 -        format for a new task, content is displayed for a previous
071234 -        record that has already been archived on the other machine.  We
071235 -        need a different method to assign new task numbers that avoids
071236 -        using a filename on the disk and that is already in the 00
071237 -        Schedule file.  The old method of cycling through numbers
071238 -        worked pretty well.
071239 -
071240 -
071241 -
071243 -  ..
0713 -
0714 -
0715 - Background
0716 -
071601 - The design to use an 00 directory for pending Schedule tasks, and 00
071602 - for the Schedule filename was first reported on 901015.  At that time,
071603 - the decision was made to list tasks in the Schedule only as lines, and
071604 - not to create records on the disk, until and unless the use decided to
071605 - report activity on the task. ref SDS 1 1K57
071607 -  ..
071608 - On 040229 the Schedule Launch operation was modified, ref SDS 5 5B8N,
071609 - to solve a rare problem that showed up 2 months later, caused by prior
071610 - work on 031217 the Schedule Launch operation was modified. ref SDS 4
071611 - 0001
071613 -  ..
071614 - Review does not suggest why the work on 040229, and reported on
071615 - 031217, would cause the problems experienced today. ref SDS 0 056N
071617 -  ..
071618 - The original work on 031125 to change the method for resetting the
071619 - current new task number, ref SDS 3 AS5L, is at least suspicious.
071620 - Background at that time explains continuing problems managing the new
071621 - task number, which up until 031125 was managed only by F1 in the
071622 - Schedule.  The problems today are puzzeling because they have not
071623 - seemed to occur until the past few days.  If the system developed on
071624 - 031125 was defective, they problems would be expected to have occurred
071625 - at about that time, not 4 months later.  Actually, the sequence
071626 - strongly suggests that code changes in the past few days caused this
071627 - new problem, but there are no reports of code changes for the past 10
071628 - days, to 040307. ref SDS 6 0001  Nothing on 040702 suggests the cause
071629 - of the problem.
071631 -  ..
071632 - In particular, work to 04702 on 040307 was performed at lines less
071633 - than 1500. ref SDS 6 YW3I  The work on 031125 that added new task
071634 - filename management is in 04702 above line 2200. ref SDS 3 OL57
071635 -
071636 -
071638 -  ..
0717 -
0718 -
0719 - Analysis
0720 -
072001 - Background review makes the cause of recent problems a mystery, in
072002 - that there is no evident direct linkage in time or location to explain
072003 - causation. ref SDS 0 PP9U
072005 -  ..
072006 - Since the new method developed on 031125 has at least a persistent
072007 - weakness, ref SDS 0 054Q, another solution is needed.  Additionally,
072008 - this could, be the cause of recent more severe problems, per above.
072009 - ref SDS 0 OH8J
072010 -
072011 -
072013 -  ..
0721 -
0722 -
0723 - Planning
0724 -
072401 - Decided to...
072402 -
072403 -    1.  Create a more affirmative method of assigning filenames for new
072404 -        tasks in the Schedule when F1 is used calling macro 95 in
072405 -        macro file 000005
072407 -         ..
072408 -    2.  Apply this new method to maintain the Schedule 00 directory in
072409 -        sync with the Schedule 00 file during the SDS program launch
072410 -        operations managed by macro file 04702; revise the work on
072411 -        040307 that incorporated Schedule maintenance into SDS program
072412 -        launch ops. ref SDS 6 PPYT
072413 -
072414 -            [On 071219 removed call for Maintenance from Schedule File
072415 -            menu. ref SDS 9 U898
072417 -  ..
072418 - Hopefully, this will solve the problems reported today. ref SDS 0 056N
072419 -
072420 -
072421 -
072422 -
0725 -

SUBJECTS
95 Macro Filenames New Task in Schedule Based on List in 00 File and
Schedule Changed Method of Developing New Task Filenames Macro 95 in

0904 -
0905 - Progress
090601 -  ..
090602 - 000005  F1 New Task Revise Method of Assigning Filenames
090603 -
090605 -  ..
090606 - Line 3050, ref OF 5 FQ6L, -label 18aq in 000005
090607 -
090608 -    @c:\sd\03\008501......................... ref SDS 0 YJ7L
090609 -
090610 -        Eliminated the system that tracked filenames at the top of the
090611 -        00 Schedule file, and instead call this new macro file to
090612 -        calculate the filename based on incrementing the last filename
090613 -        in both the list in the 00 current Schedule file, and the list
090614 -        of files on the disk in the current Schedule 00 directory.
090615 -
090616 -
090617 -
090619 -  ..
090620 - 008501  Schedule 00 File and Directory Sort
090621 -
090622 - This new macro created today improves work on 040307, ref SDS 6 PPYT,
090623 - has two purposes...
090624 -
090625 -    1.  Build a composite list of files on the disk for the 00 Schedule
090626 -        directory and with the list in the 00 Schedule file and sort
090627 -        the list so there is a simple direct way to detemine the next
090628 -        filename to assign to a new task using F1 in the Schedule file,
090629 -        called by macro 95 in 000005, per above. ref SDS 0 5L6I
090631 -         ..
090632 -    2.  Identify and delete files on the disk in the 00 Schedule
090633 -        directory for which there are no files listed in the Schedule
090634 -        00 file, when the SDS program launch op managed by 04702
090635 -        maintains the system once a day.  This revises work on 040307
090636 -        that incorporated Schedule maintenance into SDS program launch
090637 -        ops. ref SDS 6 PPYT
090639 -  ..
090640 - The format needed to support the 2nd objective is not needed for the
090641 - 1st objective, but using a single format is effective by not adding to
090642 - the time nor to memory use, so a single command file for Optech Sort
090643 - is adequate for both purposes. ref SDS 0 HB3K
090645 -  ..
090646 - This is a new method of getting a list of files for the 00 Schedule
090647 - directory and merging and sorting with the list in the 00 Schedule
090648 - file to then determine the next filename to assign a new task.  The
090649 - only requirement is to create a unique filename.
090650 -
090651 -          [On 071219 removed call from Schedule File menu.
090652 -          ref SDS 9 U898
090654 -  ..
090655 - Line 60, ref OF 2 7R7J, in 008501
090656 -
090657 -    save stufq1
090658 -    e c:\sd\03\008501
090659 -    line                                                       && *%4s
090660 -    loc_cur 4 22
090661 -    macro 92
090662 -    dose /c dir d:\sd\08\uuuuu\00 > stufq2
090663 -    dose /c c:\sd\01\o stufq3 stufq4 c:\sd\03\008502
090664 -
090665 -        Write the current 00 Schedule file to the disk in stufq1; open
090666 -        the processor and move to the line for entering the User ID;
090667 -        macro 92 enters the User ID; dose dir... gets the list of
090668 -        actual files on the disk.  dose c:\sd\01\o calls Optech Sort.
090670 -         ..
090671 -        o command is Optech Sort.  Command syntax is reported on
090672 -        010301. ref SDS 2 SM6X
090674 -         ..
090675 -        This command sorts both the list in the 00 file and from the
090676 -        list of files on the disk in dir 00, and reads in the list at
090677 -        the bottom of the macro file, then reads the last filename and
090678 -        increments it by one.
090679 -
090681 -  ..
090682 - 008502  Merge Sort List of Files in 00 Directory with List in 00 File
090683 - Optech Sort Command File for 008501 to Merge and Sort Schedule Files
090684 -
090685 - There are two purposes
090686 -
090688 -  ..
090689 - Line 10, ref OF 6 0000, 008502
090690 -
090691 -    outrec(1,16,crlf)
090692 -    s(1,4,c,a,16,1,c,a)
090693 -    in(1,1,c,ge,"0")
090694 -
090695 -        Optech Sort commands are illustrated by the record on 010301.
090696 -        ref SDS 2 SM6X  Initially, tried to do this without a command
090697 -        file, which requires a separate file on the disk.  The length
090698 -        of the command may have been too long for Medit to put the
090699 -        command on the screen in DOS, so created this very small file
090700 -        to list the commands.
090701 -
090702 -
090703 -
090704 -
0908 -

SUBJECTS
Schedule Maintenance 008501 Develop List of Files on Disk in 00 Dire

1103 -
110401 -  ..
110402 - Schedule Maintain Task Filenames in Sync with Files on Disk in 00 Dir
110403 -
110404 - Follow up ref SDS 6 EH43.
110405 -
110406 - Decided to revise the work on 040307 that incorporated Schedule
110407 - maintenance into SDS program launch ops. ref SDS 6 PPYT
110409 -  ..
110410 - Line 1130, ref OF 3 TL3M, -label Exectv in 04702 about 80 lines below
110411 -
110412 -    Debug tested here because operations on 00 Schedule file begin.
110414 -  ..
110415 - Line 1250, ref OF 3 D15O, -label bRno_curr in 04702
110416 -
110417 -    Debug tested here.
110419 -  ..
110420 - Line 1260, ref OF 3 U16L, -label bRno_curr in 04702
110421 -
110423 -  ..
110424 - Line 1480, ref OF 3 PC8H, -label dneS in 04702 about 130 lines below
110425 -
110426 -    @c:\sd\03\03101
110427 -
110428 -        Unplug this temporarily for testing so that debug will not step
110429 -        through the archiving process.
110431 -  ..
110432 - Line 1490, ref OF 3 M19N, -label dneS in 04702 about 150 lines below.
110433 -
110434 -    This is where the code maintains the 00 file, using Supersort for a
110435 -    similar function created today using Optech Sort to determine the
110436 -    next filename, per above. ref SDS 0 YJ7L  We may want to change
110437 -    04702 to apply the new scheme in 008501.
110439 -  ..
110440 - Line 1530, ref OF 3 QTYT, -label dneS in 04702 about 200 lines below
110441 -
110442 -    @c:\sd\03\008501
110443 -
110444 -        Apply the new feature to construct a composite listing of
110445 -        files on the disk and the list in 00.
110447 -         ..
110448 -        Actually, this did not work, because the format for the
110449 -
110450 -
110451 -
110452 -
110453 -
1105 -

SUBJECTS
Diary Summary Record Listed in Summary But No Record Exists How to D

1403 -
140401 -  ..
140402 - Diary Summary Syncronize List with Actual Records on Disk
140403 - Syncronize Diary Archive Records with Summary Record Descriptions
140404 - Diary Archive Syncronize Records Diary Summary Record Descriptions
140405 -
140406 - There has been an ongoing problem.  When SDS is launched the first
140407 - time each day, performed tasks identified by a dot is col 15 are
140408 - removed from the schedule and from the current 00 Schedule directory,
140409 - and are saved to the disk under the required directory structure for
140410 - diary records.
140412 -  ..
140413 - Line 1900, ref OF 3 T58F, -label bRlp_1g in 04702
140414 -
140415 -    loc_cur 3 6
140416 -
140417 -        Change code today to work from of 0; loc_cur 3 6 evaluates the
140418 -        col that is maintained by 0702051 when F2 is pressed to save
140419 -        the record.  The save function in 0702051 enters a dot in col 6
140420 -        to establishes that a task has been written to disk
140421 -
140422 -
140424 -  ..
140425 - Line 1960, ref OF 3 EA7F, -label sCu0 in 04702
140426 -
140427 -    loc_cur 0 15
140428 -    ic 32
140429 -
140430 -        Added this code to perform the step described above when a
140431 -        blank is encountered in col 6 for a task in the Schedule for
140432 -        the current date then move the cursor to col 15 and enter a
140433 -        space to conform the user intent that is set with F8 to enter a
140434 -        dot in col 15 with the user action that failed to open the task
140435 -        and make it a diary record.  About 50% of the time the task
140436 -        will not have been done, and the user will have made a mistake
140437 -        by starting to think about doing the task, and then not having
140438 -        time and so it was not done, and should be rolled ahead to
140439 -        perform later.  The other 50% of the time the task will have
140440 -        been done, but the user did not have time to open the record
140441 -        and report activity.
140443 -  ..
140444 - Line 2190, ref OF 3 4327, -label lp_u7e in 04702
140445 -
140446 -    -label lp_u7e
140447 -    loc_cur 3 1
140448 -    l /./
140449 -
140450 -
140452 -  ..
140453 - Line 2500, ref OF 3 RQVS, -label lptnUm in 04702
140454 -
140455 -    -label lptnUm
140456 -
140457 -        This is a subroutine to calculate the next task number to set
140458 -        at the top of the Schedule 00 file. ref SDS 0 TJ3J
140459 -
140461 -  ..
140462 - Line 2570, ref OF 3 3C5L, -label bRDATE in 04702 about 40 lines below
140463 -
140464 -    setcnt 1 0
140465 -    line @120
140466 -    -gosub lptnUm......................... ref SDS 0 TI6K
140467 -    z 1 1
140468 -    3C5L
140469 -    errorcnt 0 0
140470 -    -label SrtS
140471 -    nb
140472 -    -if @0 > 0 -goto NtnD
140473 -    -gosub lpnST
140474 -    -goto SrtS
140475 -    -label NtnD
140476 -
140477 -        This code was added recently, but evidently not reported to
140478 -        figure out the last filename and enter it on line 1 of the
140479 -        file, which was previously used by macro 95 to determine the
140480 -        next filename when a new task is created.
140481 -
140482 -
140483 -
140484 -
140485 -
140486 -
140487 -
140488 -
140489 -
140490 -
140491 -
140492 -
140493 -
140494 -
140495 -
140496 -
140497 -
140498 -
140499 -
140500 -
140501 -
1406 -