CONTACTS 

SUBJECTS
Maintenance, 901016
Schedule Mainenance Not Saving Correctly to Restore the Record
0702051 Macro F2 Save Sort References, Action Items, 0702051
Contacts Out of Sync Gary's List is Different from Records on C13

0706 -
0706 -    ..
0707 - Summary/Objective
0708 -
070801 - Follow up ref SDS 2 0000.
070802 -
070803 - Gary mentioned today that the Maintenance operation in SDS found some
070804 - files that need to be restored as tasks in the Schedule and some that
070805 - should be saved as diary records.  However, the F2 save function would
070806 - not support these tasks.  This evening new code was developed to make
070807 - recoving files fast and easy. ref SDS 0 WU5L
070809 -  ..
070810 - Sent a letter to Gary with a link to this record to explain progress.
070811 - Submitted updated SDS code, per below. ref SDS 0 NE6M
070812 -
070813 -
070814 -
070816 -  ..
0709 -
0710 -
0711 - Evaluation
0712 -
071201 - Save Op F2 to Recover Disconnected Files in Schedule 00 Directory
071202 -
071203 - The new process to recover SDS task files in the 00 Schedule directory
071204 - is fast and easy with a small exception....
071205 -
071206 -    1.  The code in macro 142 for saving a record executed with F2 gets
071207 -        the flags in memory that identify a record as either a Schedule
071208 -        task or a Diary record. ref SDS 0 156J  The code in 0502 opens
071209 -        a file from the maintenance list for the 00 directory so the
071210 -        user can make an examination and decide whether to restore it
071211 -        or abandon it.  This code in 0502 reads the record type on line
071212 -        1 column 36 and sets the flags used by macro 142. ref SDS 0
071213 -        LC6J
071215 -         ..
071216 -        This procedure recognizes that if a task was converted to a
071217 -        Diary then it should be an archived diary, and if it was not
071218 -        then it will say "Schedule" and so should be restored to the
071219 -        current Schedule as a pending task.
071221 -         ..
071222 -    2.  As a result, if the file in the 00 directory says "Diary," then
071223 -        when F2 is pressed the file is converted to an archived diary
071224 -        for the date and time shown in the record, ref SDS 0 GX7I, and
071225 -        the file in the 00 directory is removed from the inventory in
071226 -        the 00 Schedule directory.
071228 -         ..
071229 -        If the file in the 00 directory says "Schedule" then the
071230 -        description is entered in the Schedule ready for performance.
071232 -         ..
071233 -    3.  An exception occurs when the file in the 00 directory says
071234 -        "Schedule," but the user wants to save it as an archived Diary
071235 -        record on the date and time shown in the file.  In other words,
071236 -        for some reason even the record type is out of sync.
071238 -         ..
071239 -        This objective can be accomplished with the following steps to
071240 -        change Schedule to Diary as follows....
071241 -
071242 -        a.  Use F10 to scroll the file down so the top line in the
071243 -            file is at the top of the screen.
071244 -
071245 -        b.  Press Home to put the cursor on the command line and and
071246 -            enter tl 0 then press Enter; or, open the Diary menu and
071247 -            select "Titles Off" which also executes the tl 0 command.
071249 -             ..
071250 -        c.  After turning the titles off, move the cursor to line 1
071251 -            column 36; put caps lock on, and type DIARY to replace
071252 -            SCHEDULE
071254 -             ..
071255 -        d.  Press F2 as in step 1 above. ref SDS 0 PJ83
071257 -  ..
071258 - After pressing F2 to restore a task by saving it to the disk as
071259 - described above, ref SDS 0 PJ6M, run maintenance again to process
071260 - other files with the same procedure, and/or use F1 to delete the files
071261 - that are not needed either becaus they already exist, or because they
071262 - have been abandoned.
071264 -  ..
071265 - Alternatively, if F2 is not pressed to recover a file, then ESC is the
071266 - only other choice, and this brings the user back to the list of
071267 - maintenance files where F1 procedures can be used to delete extra
071268 - files, which brings the files in the 00 directory into alignment with
071269 - entries in the Schedule.
071270 -
071271 -
071272 -
071274 -  ..
0713 -
0714 -
0715 - Problem
0716 -
071601 - Maintenance Needs Code Correction to Recover Lost Files
071602 -
071603 - Gary reported today that he did a Schedule Maintenance op and found a
071604 - task in the list that he wants to keep, but it is not already a diary
071605 - record.
071607 -  ..
071608 - Transferring records between home and office routinely results in
071609 - tasks being on a computer that have been converted diary records by
071610 - the other computer.  It is very rare for something to be in the
071611 - Schedule 00 directory that has not been converted to a Diary and also
071612 - is not still listed in the Schedule, because once a task is created in
071613 - the Schedule the only way for the task be removed from the Schedule is
071614 - either delete it, i.e., change your mind and decide not to do the
071615 - task, in which case Alt F8 deletes the task from the Schedule and
071616 - removes the record file in the 00 directory.  The other way is to
071617 - convert the thing to a diary record, and that removes the task from
071618 - the 00 directory.
071620 -  ..
071621 - Gary has a record today that discusses procedure issues that be
071622 - causing a buble of problems getting started.  Still, this is an issue
071623 - of concern.
071625 -  ..
071626 - Today, during a call we tried to restore a file and this failed.
071628 -  ..
071629 - The procedure should be to simply press F2 and this should write the
071630 - file and the pointers to the disk, which is the objective.  Since that
071631 - failed, we have a problem.
071632 -
071633 -     [...below, fixed the problem. ref SDS 0 WU5L
071635 -  ..
071636 - I think the problem is that this code was created in 1990, as shown in
071637 - the record on 901127, ref SDS 1 0001, and work on this system was last
071638 - performed on 941221. ref SDS 2 0001
071640 -  ..
071641 - Since that time, the procedure for saving a record has been changed.
071642 - In particular 0702051 was made a dose op on 010510 in order to
071643 - improve memory management.
071644 -
071645 -
071646 -
071647 -
071649 -  ..
0717 -
0718 -
0719 - Progress
0720 -
072001 - 000008  Macro 142, Save Function Failed Requires SDS Code Revisions
072002 -
072003 - Follow up ref SDS 3 TS7L.
072004 -
072005 - Generally, the save op distinguishes between Schedule tasks and
072006 - archived diary records.
072008 -  ..
072009 - Line 2350, ref OF 3 PR6M, -entry 142 in 000008
072010 -
072011 -    -if @273 = 5913 @c:\sd\03\05021
072012 -
072013 -        Added this new code to call a new macro file that will restore
072014 -        a file in the 00 directory to either a task in the Schedule or
072015 -        an archived diary record, per below, ref SDS 0 WU5L, if a flag
072016 -        has been set by macro 0502 that opens a file listed in the
072017 -        maintenance listing, per below. ref SDS 0 NV8J
072018 -
072020 -  ..
072021 - Line 2410, ref OF 3 FT5K, -entry 142 in 000008 about 70 lines below
072022 -
072023 -    loc_cur 3 35
072024 -    -if @272 = 1001 ic 49
072025 -    -if @272 = 1002 ic 50
072026 -    -if @271 = 2000 ic 51
072027 -
072028 -        Code puts the cursor on the column in front of Diary and
072029 -        enters 1 for Scheduled task, 2 for current diary record and 3
072030 -        for archived diary.
072032 -         ..
072033 -        Right now the condition for counters 271 and 272 are both 0.
072035 -         ..
072036 -        Enter can restore these.
072037 -
072039 -  ..
072040 - Line 2420, ref OF 3 0803, -entry 142 in 000008 about 80 lines below
072041 -
072042 -    loc_cur 3 44
072043 -    macro 841
072044 -
072045 -        User ID is stored based on counters 285 - 289, however, for a
072046 -        file being restored from maintenance these values are 0, so
072047 -        they will have to be restored.
072048 -
072049 -
072050 -
072052 -  ..
072053 - 0502  Maintenance Update to Support DOSE Op in 0702051
072054 -
072055 - Line 200, ref OF 1 GB5G, -label end in 0502 about 20 lines below.
072056 -
072057 -    pfent @c:\sd\03\0502 -gg opn_it
072058 -
072059 -        This opens the file and passes control to...
072060 -
072062 -  ..
072063 - Line 220, ref OF 1 LD3H, -label opn_it in 0502
072064 -
072065 -    top
072066 -    loc_cur 3 36
072067 -    chrcnt 1 0
072068 -
072069 -        Make Enter that opens the record, read the record type to
072070 -        determine if it shows Scheduel which means this was never
072071 -        converted to a diary.  In that case, the save function will
072072 -        create a Schedule task.
072074 -     ..
072075 -    -if @1 = 32 setcnt 271 2000
072076 -    -if @1 = 68 setcnt 271 2000
072077 -    -if @1 = 83 setcnt 272 1001
072078 -
072079 -        If the field is blank, make this a diary by default to tell
072080 -        macro 142 that is called by F2 to save the thing that that this
072081 -        is either a Schedule task or an archived diary.
072082 -
072084 -     ..
072085 -    setcnt 273 5913
072086 -
072087 -        Create flag to show we need to add a description to the
072088 -        Schedule if the thing is saved by the User, and we need to save
072089 -        the file to the directory structure and swap it out, for an
072090 -        archived diary record, which is evaluated based on this flag by
072091 -        macro 142 to save, per above. ref SDS 0 NP5J
072093 -     ..
072094 -    macro 856
072095 -
072096 -        Move global user ID to locals in counters 285 - 289, so the
072097 -        code in macro 142 will have something to process.
072098 -
072099 -
072101 -  ..
072102 - 05021  Restore File in 00 Schedule Directory to Schedule or Diary
072103 -
072104 - This is a new tool to facilitate restoring a record that gets out of
072105 - sync with the Schedule.  Even though this has never been needed, per
072106 - background above, ref SDS 0 UO5I, recent experience indicates
072107 - something can happen with new users, so if we want more new users,
072108 - then we need to be prepared to recover from unusual situations.
072110 -  ..
072111 - This op is called by macro 142 when F2 is pressed, per above,
072112 - ref SDS 0 015G, and will handle Schedule files that need to be
072113 - restored to the Schedule, and it will convert Schedule task files
072114 - marked as "DIARY" into archived diary records, and remove the file in
072115 - the 00 directory.
072116 -
072118 -  ..
072119 - Line 60, ref OF 2 4A7G in 05021
072120 -
072121 -    purge 0W6J
072122 -    purge c:\sd\03\0502
072123 -
072124 -       Since we are doing an operation that will change the content of
072125 -       the maintenance op, purge the list files generated by the
072126 -       maintenance op, and, also, purge, the processor 0502.  This
072127 -       provides a clean break so that users can run the maintenance op
072128 -       again after the restore op executes.
072129 -
072130 -
072132 -     ..
072133 -    setcnt 273 0
072134 -
072135 -        Reset the flag for the save command in macro 142, so this
072136 -        won't run again.
072138 -     ..
072139 -    markcur 4
072140 -
072141 -        Identify the file so we can switch back and forth to do stuff.
072143 -     ..
072144 -    macro 22
072145 -
072146 -        Save User's original position to restore for orientation after
072147 -        save.
072149 -     ..
072150 -    setgbl 65 @65
072151 -
072152 -        Since for archived diary records we are changing the file,
072153 -        need to capture global line number at current screen position
072154 -        to restore.
072156 -     ..
072157 -    setcura 66 0
072158 -    setgbl 66 @66
072159 -    setgbl 67 @67
072160 -
072161 -        Capture cursor location and save in globals for restoring
072162 -        archived diary records.
072163 -
072164 -
072166 -  ..
072167 - Line 90, ref OF 2 JE9L, in 05021
072168 -
072169 -    top
072170 -    gfname
072171 -    setgbl 91 @19
072172 -    setgbl 92 @20
072173 -    setgbl 93 @21
072174 -    setgbl 94 @22
072175 -
072176 -        Put cursor at the top of the file and get the filename, put it
072177 -        in globals.
072178 -
072180 -  ..
072181 - Line 90, ref OF 2 9E4J, in 05021
072182 -
072183 -    -if @271 = 2000 -goto diarY
072184 -
072185 -        If 271 = 2000 this is a Diary and should processed as an
072186 -        archived diry record, and the task file in the 00 directory is
072187 -        removed.  If not, the a new entry is created in the Schedule at
072188 -        the cursor location and the task file in the 00 directory is
072189 -        retained. ref SDS 0 J95Y
072190 -
072191 -
072193 -  ..
072194 - Schedule Task Processing Ends in Schedule Screen
072195 -
072196 - Line 110, ref OF 2 4G6F,
072197 -
072198 -    -gosub prgST
072199 -
072200 -        This is a Schedult task, so the drill is to purge it from
072201 -        memory and post the description in the Schedule.
072203 -         ..
072204 -        This subroutine opens the processor and posts the purge
072205 -        command.
072207 -     ..
072208 -    ecur 4
072209 -    loc_cur 5 6
072210 -    macro 1188
072211 -
072212 -        Return to the Schedule task and read the record description on
072213 -        line 01.
072214 -
072215 -    -gosub prgtsk
072216 -
072217 -        Go open the Schedule and purge the Schedule task, since it is
072218 -        no longer needed.  This enables the user to open the thing
072219 -        from the Schedule to update the date and time.
072221 -  ..
072222 - Line 130, ref OF 2 NC3I,
072223 -
072224 -    immed a
072225 -    loc_cur 0 9
072226 -    rel_cur 1 0
072227 -    macro 1189
072228 -
072229 -        Add a line at the cursor location, and move the cursor to the
072230 -        beginning of the task description field.  Move the cursor down
072231 -        a line to the new line just created, and enter the description
072232 -        of the task shown in the file, per above. ref SDS 0 4B4G
072233 -
072235 -  ..
072236 - Line 140, ref OF 2 YE5G,
072237 -
072238 -    of 0
072239 -    loc_cur 0 1
072240 -    getgbl 1 91
072241 -    getgbl 2 92
072242 -    getgbl 3 93
072243 -    getgbl 4 94
072244 -    ic @1
072245 -    ic @2
072246 -    ic @3
072247 -    ic @4
072248 -
072249 -        Off set the screen, put the cursor on column 1 and enter the
072250 -        file name ID
072251 -
072253 -  ..
072254 - Line 160, ref OF 2 577H,
072255 -
072256 -    of 7
072257 -    loc_cur 0 9
072258 -    errormsg  New task added
072259 -    -goto over
072260 -
072261 -        Restore standard Schedule screen offset, put the cursor at the
072262 -        beginning of the new descriptoin.  Tell User what happened and
072263 -        go end it.
072264 -
072265 -
072267 -  ..
072268 - Diary Processing Ends in SDS Record
072269 -
072270 - Line 180, ref OF 2 O99J, -label diarY in 05021
072271 -
072272 -    setgbl 65 @65
072273 -    setcura 66 0
072274 -    setgbl 66 @66
072275 -    setgbl 67 @67
072276 -
072277 -        This is a diary record and so will come back to the user for
072278 -        further editing.  The first step is to save the relative
072279 -        position of the cursor so it can be restored in an archived
072280 -        diary record, after closing and deleting the Schedule task.
072281 -        Global 65 saves the current line captured with macro 22 at the
072282 -        beginning of the process, per above. ref SDS 0 2G5P  Setcura
072283 -        saves the y and x values in globals.
072284 -
072285 -
072286 -
072287 -
072288 -
072289 -
072290 -
072291 -
072292 -
072294 -  ..
072295 - Line 200, ref OF 2 VF4L, -label diarY in 05021 about 20 lines below
072296 -
072297 -    macro 85
072298 -
072299 -        The cursor is at the top of the file so read the record ID,
072300 -        since this is a diary record.  Macro 85 converts stuff to
072301 -        globals, so we are all set.
072303 -     ..
072304 -    e c:\sd\03\05021
072305 -    line
072306 -
072307 -        Open the processor and move to the line that will create a
072308 -        comand to save the file to an SDS archived diary directory and
072309 -        filename.
072311 -     ..
072312 -    loc_cur 4 15
072313 -    macro 91
072314 -    macro 88
072315 -
072316 -        Move the cursor the column that begins the User ID.  Get
072317 -        globals and enter the SDS record filename structure.
072318 -
072320 -  ..
072321 - Line 210, ref OF 2 KC6J, -label diarY in 05021 about 30 lines below
072322 -
072323 -    line
072324 -    loc_cur 4 12
072325 -    macro 88
072326 -
072327 -        Move to the line in the processor 05021 that has the command
072328 -        for opening the SDS archived record.  Put the cursor on the
072329 -        column that begins the User ID, and call the code that enters
072330 -        the standard string for an SDS record directory and filename.
072332 -     ..
072333 -    ecur 4
072334 -    *%01
072335 -    savx d:\sd\08\
072336 -
072337 -        Return to the SDS record and execute the savx command to
072338 -        create the archived SDS record for this particular Schedule
072339 -        task.
072341 -     ..
072342 -    -gosub prgST
072343 -
072344 -        Now that the record has been saved to the disk, call a
072345 -        subroutine that switches control to processor 05021 and
072346 -        configure a command to purge from memory the Schedule task,
072347 -        since it is no longer needed.
072348 -
072350 -  ..
072351 - Line 240, ref OF 2 KK4L, -label diarY in 05021 about 40 lines below
072352 -
072353 -    line
072354 -    loc_cur 4 22
072355 -    macro 841
072356 -    loc_cur 0 31
072357 -    ic @1
072358 -    ic @2
072359 -    ic @3
072360 -    ic @4
072361 -
072362 -        In the processor 05021 move to the line that has the dose
072363 -        command to delete the Schedule task from the 00 directory,
072364 -        since we are converting to an archived dirary that uses a
072365 -        different directory and filename system.  Move the cursor to
072366 -        the column for entering the User ID and call the code that
072367 -        enters the user ID; then move to the column that has the
072368 -        filename and enter it, so the command can be executive.
072369 -
072370 -    -gosub prgtsk
072371 -
072372 -        Call subroutine that switches from the processor 05021 to the
072373 -        Schedule screen and execute the purge command.
072375 -     ..
072376 -    *%04
072377 -    dose /c del d:\sd\08\uuuuu\00\
072378 -
072379 -        Call dose command to delete the file from the disk
072380 -
072381 -
072383 -  ..
072384 - Line 260, ref OF 2 LW7L, -label diarY in 05021 about 60 lines below
072385 -
072386 -    *%03
072387 -    e d:\sd\08\uuuuu\02\yy\mm\dd\hhmmss
072388 -    setcnt 47 2
072389 -    setcnt 271 2000
072390 -    macro 856
072391 -    macro 150
072392 -
072393 -        Open the new SDS record just saved per above, ref SDS 0 HJ4G,
072394 -        and set up archived diary environment with counter 472 and 271
072395 -        2000.  Obtain user ID from globals.  Call profile.
072397 -  ..
072398 - Line 280, ref OF 2 PY9H, -label diarY in 05021 about 70 lines below
072399 -
072400 -    getgbl 65 65
072401 -    getgbl 96 96
072402 -    getgbl 97 97
072403 -    addcnt 96 1
072404 -    addcnt 97 1
072405 -
072406 -        Get counter values to restore the original position of the file
072407 -        to maintain user's orientation.
072409 -     ..
072410 -    line @65
072411 -    loc_cur @97 @96
072412 -
072413 -        Make line that was current in the Schedule task current in the
072414 -        diary record file, and move the cursor to the same relative
072415 -        location on the screen.
072416 -
072417 -    -goto over
072418 -
072419 -        Ends op, so go purge the processor.
072420 -
072421 -
072422 -
072423 -
072424 -
0725 -

SUBJECTS
Zip Update SDS Program and My SDS Records for Training Purposes on Ga
Maintenance F2 Save Not Working

090401 -  ..
090402 - SDS Program Code and Work Records Updated
090403 -
090404 - Follow up ref SDS 6 NE6M, ref SDS 5 0245.
090405 -
090406 - Submitted email notifying Gary SDS update is on the web covering the
090407 - period from last transfer on 030408. ref SDS 6 NE6M
090409 -  ..
090410 - Used procedures reported on 021201. ref SDS 4 CL9N
090411 -
090412 -     Working with Gary today showed that his contact records are out of
090413 -     sync, so will replace all of his contact records.
090414 -
090415 -     Additionally, did the update from 030301 rather than from 030408
090416 -     the last update, to ensure Gary's records align with mine.
090418 -  ..
090419 - This update includes new feature for restoring files from the Schedule
090420 - 00 directory, per above. ref SDS 0 PJ6M
090422 -  ..
090423 - Updated files can be downloaded at....
090424 -
090425 -
090426 -        http://www.welchco.com/09/
090427 -
090428 -
090429 -
090430 -
090431 -
090432 -
090433 -
090434 -
090435 -
090436 -
0905 -

SUBJECTS
Setup  combat Aerospace company Major Project Subject Accounts Transfer  nitial Lear
Gary Frustrated SDS Record on 030413 Recognizes More to Subject Index
Frustrating Gary's SDS Record on 030413 Recognizes More to Subject In

190501 -  ..
190502 - Subject Index Transform from Learning General Account to  combat Project
190503 -
190504 - Follow up ref SDS 6 WE7N.
190505 -
190506 - Email to Gary this morning says in part....
190507 -
190508 -        Also, put another SDS program and record update on the
190509 -        Internet, because after looking at your SDS records yesterday
190510 -        (boy you were busy), and then reviewing the issue on CMM KPAs
190511 -        and Activities template for adding HTML, noticed that more
190512 -        detail was needed in the SI.  This was added.  I explained the
190513 -        process in a letter to you, but if you tried to look it up, the
190514 -        stuff was not in the last update I sent, so this corrects that
190515 -        problem.  The upshot is that if you open my SDS record on
190516 -        030408 at you can look at how multiple views were developed to
190517 -        create a variety of trails back to this subject, ref SDS 6
190518 -        F34H, and perhaps get a better sense of how subjects get
190519 -        created and then applied. Notice I am tracking two major
190520 -        levels...
190521 -
190522 -            1.  03 00050, which is an SDS development view
190524 -                 ..
190525 -            2.  04 00074, which is a Gary using SDS view
190527 -         ..
190528 -        Other possible views are...
190529 -
190530 -            1.  02 06 01 05 02K, which is Knowledge Management
190531 -
190532 -            2.  07 DG, which is management science Management
190534 -         ..
190535 -        In this case, these latter areas, off hand, don't apply, but
190536 -        experience shows that with focused attention and, as further
190537 -        context unfolds over time, they might.
190539 -         ..
190540 -        I mention this because your record yesterday on 030413 says
190541 -        that there is more to using the SI than is currently being done
190542 -        in your records. ref SDS 7 0084
190544 -         ..
190545 -        So, review of your SI indicates that the only account with any
190546 -        detail is....04 00001, which I created to correct the initial
190547 -        approach that was going in the wrong direction.  To maintain
190548 -        what you had done, the initial accounts were all accumulated in
190549 -        a sort of "general" or "miscellaneous" account.  Typically,
190550 -        each of the sub accounts in 00001 should go elsewhere, as
190551 -        explained in the record on 030408. ref SDS 6 OH8I
190553 -         ..
190554 -        I am concerned that if we get a lot of stuff in miscellaneous,
190555 -        we lose the benefit of stepping through the structure in a way
190556 -        that leverages remembering the gist of information with
190557 -        multiple views.
190559 -         ..
190560 -        Incidentally, your record yesterday has excellent explanation
190561 -        of how SDS leverages human cognition to "augment intelligence."
190562 -        ref SDS 8 0001
190564 -         ..
190565 -        It is very gratifying to see that experience using SDS has led
190566 -        to such insights.  As noted in your other record, however, now
190567 -        that you have a firmer grasp on the goals, objectives and
190568 -        theory of SDS, we need to align practice with theory so that
190569 -        each supports the other.  The record on the CMM KPAs and
190570 -        Activities may help with this, as reported on 030408.
190571 -        ref SDS 6 F34H
190573 -         ..
190574 -        The main accounts for your Aerospace company assignment should be an 03
190575 -        xxxxx account with sub accounts generated using the
190576 -        "organization" template, and below that many will be dates, or in
190577 -        some cases organic structure.  Let's talk about this some more
190578 -        when you have time.
190579 -
190580 -             [On 030420 Gary schedules work on this task. ref SDS 9
190581 -             KS9H
190583 -         ..
190584 -        Possibly in the next few days, we can work on shaping up the SI,
190585 -        and on getting a format for meeting notes to support taking notes
190586 -        at tech meetings on SoS Sim Dev, shown in your Schedule to start
190587 -        tomorrow.  The letter yesterday discussed this in some detail,
190588 -        but verbal discussion often helps flesh out details and nuance
190589 -        needed for implementation.
190590 -
190591 -
190592 -
190593 -
190594 -
190595 -
190596 -
190597 -
190598 -
1906 -