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: November 21, 2003 05:04 AM Friday; Rod Welch

Action item system improves Context Management for getting things done.

1...Summary/Objective
2...Action Items Faster and Easier for Getting Things Done
3...Design Change Improves Speed and Capacity Managing Action Items
4...Action Item Construct SDS Record to Review
5...Counterintuitive Code Runs Fast Difficult to Understand and Maintain
6...070301 Change Design Action Item Record Use Windows Start Command
....Current Date Action Items Compare Dates to Process
....Compare Dates to Process Current Date Action Items
....File Spec Transferred to Stufqt.bat to Launch Windows Start
....NB Deletes AI Report Content Until All Records Processed
....Set Command Impacts Environment Space
....Windows Start Command Batch Process Each Record in Separate Memory
....References Update Links in Action Items
....Complete Report Format
....Format Report with Final Organization
7...070302 Format Original SDS Record for Action Item Review Record
....User ID Posted End of User's Name on Record ID
....References Deleted to Reduce Burden on Memory and Speed Processing
....Summary Objective Removed for Uniform Processing
....Citations and Links Flag for Removal in Action Item Meeting Record
....J.Headlines Converted for Action Items
....Line Number Flags Removed Action Items Converted to Headlines
....Report Type Determines Action Item Selections
....Branch Code Separately for Specified Subjects and All Subjects
....Subjects General All Process Control Fields 3 Description Lines
....Subjects Select Record Segments for Action Items
....Primary Loop Find Action Items Across Record Segments
....Subsidiary Loop Find Action Items within Record Segment
....Link to Original Source Find Appropriate Anchor for Context
....Shift Action Item Description to Common Left Margin for Report
....Citations Removed from Action Item Narrative
....Justify Action Item Description within Standard Margins
....Subroutine Select Record Segments for Specified Subjects
....Control Field Lines Contains Only Specified Subjects
....Control Field Delete Lines that Do Not Meet Report Specification
......Subject Descriptions Conform to Subject Index - 04405 Failed
......04405 - Subject Descriptions Conform to Subject Index Failed
........3.Subject Description Lines Retained All Reports
....Format Completion of SDS Record for Record to Review Action Items
8...04405 Modified to Conform Subjects in Action Item Reports
9...Subjects Descriptions Conformed to Subject Index for AI Reports
....Subjects Conformed in Chained SI Segments Change Design
....Search Fails in Subject Index Chained Segment Report Error


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

CONTACTS 

SUBJECTS
Planning Action Item Review Meeting in Schedule 070301
Action Item Review Meeting in Schedule Process Each SDS Record S
Background Action Item Review SDS Record for Meetings, 070301, 970505
Action Item Review Meeting in Schedule 070301
070302 Action Item Review Meeting in Schedule Process Each SDS Record

0907 -
0907 -    ..
0908 - Summary/Objective
0909 -
090901 - Follow up ref SDS 11 0000. ref SDS 10 0000.
090902 -
090903 - Changed the design of the process to automatically generate an SDS
090904 - record for reviewing action items. ref SDS 0 JW4J  The new system runs
090905 - faster and has greater capacity, i.e., can process more tasks over a
090906 - longer period of time. ref SDS 0 QG5G  All relevant subjects are now
090907 - retained in Control Fields to improve context management for timely
090908 - situational awareness. ref SDS 0 LO8K  Better situational awareness
090909 - from expanding span of attention augments intelligence.  Working
090910 - "intelligently" strengthens the partnership between technology and
090911 - leadership that empowers people to get things done on time and within
090912 - budget for those who care about making good management faster and
090913 - easier to save lives and improve productivity and earnings. ref SDS 0
090914 - K34Y
090915 -
090916 -
090917 -
090918 -
090919 -
090921 -  ..
0910 -
0911 -
0912 - Evaluation
0913 -
091301 - Action Items Faster and Easier for Getting Things Done
091302 -
091303 - Evaluation criteria are reported on 031114....
091304 -
091305 -    1.  Fast and easy to use, hard to cause a failure, with significant
091306 -        increase in performance.
091308 -         ..
091309 -    2.  Existing procedures either remain the same or are improved, so
091310 -        there is minimal learning curve -- things work better with
091311 -        existing skills, including adding control fields previously
091312 -        excluded. ref SDS 0 QN4O
091314 -         ..
091315 -    3.  Memory management improved, shown by fewer crashes and
091316 -        enabling bigger reports.
091318 -  ..
091319 - The new system is about 10 times faster and increases capacity about 3
091320 - fold.  Previously, converting an Action Item report into an SDS record
091321 - to review progress with the team might take 30 seconds to a minute or
091322 - so.  While the prior system was 10 times faster than using other
091323 - methods, experience shows delay of any magnitude discourages many
091324 - people from discovering actions in time to make action effective,
091325 - under the Boy Sout "napsack" analogy, developed on 990816. ref SDS 6
091326 - 2880  The new process solves the problem by reducing the time for good
091327 - management to under 5 seconds.  For example, creating an action item
091328 - report for Gary's work at Aerospace company covering the past 90 days takes 4
091329 - seconds to find and list 123 action items.  This is unchanged, because
091330 - that part of the process was not changed today.  Converting the report
091331 - into an SDS record for a review meeting on the 123 pending issues,
091332 - however, now takes only 3 seconds rather than 30 to 60 seconds.
091334 -  ..
091335 - Context management is improved with the new design by including all
091336 - relevant subjects in Control Fields, rather than limit record segments
091337 - to only one subject, which was a convention under the prior scheme in
091338 - order to meet memory limitations. ref SDS 0 JX5H  Expanding span of
091339 - attention on organic structure of subjects improves understanding and
091340 - follow up on situations that require action.
091342 -  ..
091343 - The new design uses several steps to increase capacity. ref SDS 0 JX6H
091344 - More capacity increases context management, per above, and supports
091345 - more action items over a longer period.  Previously, a report with
091346 - more than 100 pending action items was problematical.  Testing shows
091347 - the new system supports over 200 action items.  The total number of
091348 - action items supported varies.  For example, an action item report on
091349 - "SDS" under account 03 00050, and covering 18 months finds about 170
091350 - action items.  The same report for 24 months fails.  A report for 12
091351 - months on Gary's records at Aerospace company shows about 231 action items.
091352 -
091353 -    Why the disparity between 231 action items on one project, while
091354 -    going over 170 action items failed on the SDS project?
091356 -     ..
091357 -    Records on the project have fewer control fields, and there is
091358 -    generally less context for action items; as a result, more action
091359 -    items consume fewer lines, which increases stability.  For example,
091360 -    tests showing 170 action items on SDS has 3800 lines, and the file
091361 -    is about 210K.  231 action items on the project require only 2700
091362 -    lines and the file is about 96K.  This suggests that for the
091363 -    practice at Aerospace company, there may be enough capacity in the new action
091364 -    item system to support another 230 action items, starting from the
091365 -    beginning of the project, and assuming there is continued inaction
091366 -    on pending tasks.
091368 -  ..
091369 - There is always potential that action item review over a long enough
091370 - period, say 2 years or 10 years, can accumulate enough pending tasks
091371 - to overwhelm any fixed memory capacity due to failed leadership.
091373 -  ..
091374 - SDS technology overcomes the darkness of ignorance by lighting the
091375 - path so that people have accurate, timely and full situational
091376 - awareness, along with instant access to context on who, what, when,
091377 - where, why and how to get things done correctly.  Support for working
091378 - intelligently strengthens the partnership between technology and
091379 - leadership.  Better intelligence and communication makes technology an
091380 - ally of leadership, as set out on 960307, ref SDS 4 4492, rather than
091381 - an enemy, as explained in the record on 950426, ref SDS 2 3921, and
091382 - more recently on 010908. ref SDS 8 YF5O  However, better visibility
091383 - aids only the willing.  Only leadership can aid the willfully blind.
091384 - When leadership fails to provide guidance and support for people to
091385 - get things done, then expanding the period for reporting pending tasks
091386 - will be of no help, as set out in NWO. ref OF 28 Q74L  Of course
091387 - leadership must be educated to overcome ignorance, fear and denial
091388 - that good management is unnecessary overkill, discussed on 890324.
091389 - ref SDS 1 2940
091390 -
091391 -
091392 -
091393 -
091395 -  ..
0914 -
0915 -
0916 - Planning and Background
0917 -
091701 - Design Change Improves Speed and Capacity Managing Action Items
091702 -
091703 - Yesterday Gary reported a problem converting an action item report
091704 - into an SDS record for a review meeting at Aerospace company. ref SDS 14 0001  The
091705 - record yesterday on 031120 has more background on work with the Action
091706 - Item system. ref SDS 14 GS6L
091708 -  ..
091709 - Was able to fix the code so that the Action Item report would run for
091710 - Gary.  A minor problem surfaced on formatting related to citations
091711 - that are inactive in descriptions of action items in the SDS record
091712 - for an action item review meeting.  The problem could be ignored
091713 - because it only affects appearance, and did not prevent the report
091714 - from running.  After working on the problem for a few hours, finally
091715 - abandoned the effort to remove citations, explained on 031002,
091716 - ref SDS 11 GJ9I, and instead decided to simply comment them out, since
091717 - they are not actionable in the Action Item review record.  However,
091718 - this creates a dual system, where content occurs that appears to be
091719 - actionable, but people find the appearance is misleading.  While this
091720 - is not a preferred nor elegant solution, the substance of providing a
091721 - timely and comprehensive action item report outweighs the need for
091722 - good appearances.
091724 -  ..
091725 - Testing to investigate a solution to the citation appearance problem,
091726 - showed that expanding the report beyond 90 days used by the action
091727 - item system when called in the Schedule menu for "Management," causes
091728 - the report to fail due to memory limitations.  In this case, action
091729 - items are accumulating because work is not reported on the project
091730 - showing action items are performed, so the list to gets bigger
091731 - everyday.  The problem can be redressed in part by reporting for a
091732 - shorter period. Separate SDS records could be created covering
091733 - succeeding periods.
091735 -  ..
091736 - This is not a strong solution, particularly on the project where
091737 - action items are increasing.
091739 -  ..
091740 - Researching the problem resulted in a decision today on changing the
091741 - design of the process for opening the original SDS record to extract
091742 - relevant information for constructing an SDS record on a meeting to
091743 - review action items.  The current system, developed initially on
091744 - 970505, ref SDS 5 0001, improved on 000915, ref SDS 7 0001, and again
091745 - recently on 031002, ref SDS 11 0001, does the following....
091746 -
091747 -    1.  Builds and expands the Subject Report in 06112 to list action
091748 -        items for online review and action (see process explained on
091749 -        970505. ref SDS 5 QQ7G)
091751 -         ..
091752 -    2.  Entry is read in the Action Item list and this creates an entry
091753 -        in the Schedule for a new SDS record.
091755 -         ..
091756 -    3.  New SDS record is opened.
091758 -         ..
091759 -    4.  Original SDS record for the action item is opened at the
091760 -        location for the action item in the Action Item list created by
091761 -        06112, and data is extracted for transfer to the new SDS record
091762 -        for the action item review meeting in point 3. ref SDS 0 JW66
091763 -        After the action item is extracted for transfer and formatting
091764 -        in the new SDS record for an action item review meeting, a link
091765 -        is created to the original source to support requirements for
091766 -        good management shown on 950721. ref SDS 3 1740
091768 -  ..
091769 - There are a minimum of 4 files in memory during this process.  These
091770 - files are on a collision course, because the new SDS record for a
091771 - meeting to review action items, step 3, ref SDS 0 QG4P, gets bigger
091772 - through the process of constructing the record.  Eventually, the
091773 - chances of opening an original SDS record, under step 4 that exceeds
091774 - Medit memory limits reaches 100%.  Generally, memory fragmentation
091775 - causes Medit to fail before absolute memory limits are reached under
091776 - the original scheme.
091778 -  ..
091779 - Since only a small part of an original SDS record is needed to
091780 - construct a new record for an action item review meeting, this can be
091781 - performed in a separate memory session using the Windows Start command
091782 - to reduce the problem of Medit memory limitations.  Last month on
091783 - 031002 the Windows Start command was applied for constructing an
091784 - Action Item report from the Subject Index, ref SDS 11 0001, which was
091785 - ported to a Start op earlier on 030902. ref SDS 9 0001  However, the
091786 - design of the process for constructing the SDS record for meeting to
091787 - review action items was not changed on 031002.
091789 -  ..
091790 - A new design using the Windows Start command expands the window of
091791 - opportunity for leadership to act in time.  More memory enables a new
091792 - process to post the actual control fields to the new record, rather
091793 - than construct place holders, which was adopted on 000915 in the
091794 - original design in order to reduce the size of the file and reduce
091795 - processing speed. ref SDS 7 EM93
091797 -  ..
091798 - The new process developed today opens original SDS records in a
091799 - separate memory session. ref SDS 0 XA6O  This eliminates the problem
091800 - of multiple files in memory, ref SDS 0 JX51, and particularly of a
091801 - single large SDS record causing a memory failure.  Since memory is
091802 - refreshed each pass, the problem of memory fragmentation is reduced.
091804 -  ..
091805 - A new macro, 070302, created today deletes everything in the original
091806 - record except what is needed for the action item review SDS record,
091807 - and then formats and saves the remaining content into a temporary
091808 - file.  The session is closed which returns control to the primary
091809 - memory session, where the content of the temporary file is read into
091810 - the new SDS record.  This is repeated for all of the tasks listed in
091811 - the action item review report, which are deleted sequentially.
091812 - ref SDS 0 QC5O  So, as the new SDS record grows, the action item
091813 - report list gets smaller.  This helps memory a little, but
091814 - fragmentation likely remains an issue.
091816 -  ..
091817 - Another idea would be to use the new get command to read lines from
091818 - the original record that are needed for the new task in the action
091819 - item review record and then do the editing there.  I think, but am not
091820 - sure, that there is less demand on memory by deleting lines from a
091821 - file than by opening another separate file.
091823 -  ..
091824 - Formatting action items in the original SDS records using a separate
091825 - Windows Start memory session reduces the size of the code code in the
091826 - primary session that processes the SDS action item review record.  All
091827 - of the action items in an SDS record can be processed at once to
091828 - increase the speed of the process.  The problem of formatting the
091829 - content, which initially required a compromise method, per above,
091830 - ref SDS 0 JW5G, is eliminated by doing the work in the original
091831 - record.
091832 -
091833 -
091834 -
091835 -
091836 -
0919 -

SUBJECTS
Configure 070301 to Run in 2nd Session When Called from Subject Index U
Action Item Report Convert to Record for Review Meeting Listed in the S

1104 -
1105 - Progress
110601 -  ..
110602 - Action Item Construct SDS Record to Review
110603 - Counterintuitive Code Runs Fast Difficult to Understand and Maintain
110604 -
110605 - Follow up ref SDS 11 5A7N, ref SDS 7 EM76.
110606 -
110607 - The new code is fast by relying on vertical and horizontal positioning
110608 - to navigate through fields and delete unneeded lines using a "*" char
110609 - in the line number field.  This positioning must be maintained in
110610 - future improvements, and is difficult to understand after a period of
110611 - time passes from the original development, and may not be explained
110612 - well in this record because the process is counterintuitive.  Looking
110613 - at the code a day, week, month or years later will result in feeling
110614 - the code is wrong, and so the tendency will be to start making changes
110615 - and this will be a mistake.
110617 -  ..
110618 - Maintenance and improvements should begin with running the existing
110619 - code in debug to first observe the process to understand the vertical
110620 - spacing issue.  This analysis is based on experience modifying the
110621 - code within only a day or so, and causing disruption to the process
110622 - flow, which was then difficult to restore.
110623 -
110625 -  ..
110626 - 070301  Change Design Action Item Record Use Windows Start Command
110627 -
110628 - Line 310, ref OF 8 SE9H, -label opnn in 070301 about 70 lines below
110629 -
110630 -    line 8
110631 -    loc_cur 4 1
110632 -    immed 99d
110633 -    immed a
110634 -
110635 -        Changed this to remove all the lines from standard new task
110636 -        record format, because the new design will add all the lines
110637 -        needed. Delete at bottom of Reference field where links will be
110638 -        added for each action item in the record.  Add a line so there
110639 -        is a blank to support finding the bottom of the record when a
110640 -        SDS record formatted by new macro file 070302 is read into the
110641 -        record created for an action item review meeting.
110642 -
110643 -
110645 -     ..
110646 -    Current Date Action Items Compare Dates to Process
110647 -    Compare Dates to Process Current Date Action Items
110648 -    File Spec Transferred to Stufqt.bat to Launch Windows Start
110649 -
110650 -
110651 - Line 340, ref OF 8 QE7L, -label lpa1 in 070301
110652 -
110653 -    top
110654 -    errorcnt 0 0
110655 -    -if @0 > 0 -goto fin........................ ref SDS 0 0212
110656 -    immed dd
110657 -
110658 -        -if 0 > 0 there was an error using nb looking for the next SDS
110659 -        record to process, per below, ref SDS 0 QC5O, so the process is
110660 -        over. Otherwise, begin to delete the next SDS record segment in
110661 -        the AI report.
110663 -     ..
110664 -    macro 85
110665 -    datecnt 13 0
110666 -    -if @3 = @13 -if @4 = @14 -if @5 = @15 setcnt 13 800
110667 -    setgbl 13 @13
110668 -    of 80
110669 -    loc_cur 0 1
110670 -    macro 851
110671 -
110672 -        Change the design today.  macro 85 reads spec for the record
110673 -        where action items are reported on line 1.  datecnt 13 0 used
110674 -        to compare date of record with current date.  If the record is
110675 -        for the current date (today) then setcnt 13 800 and make it
110676 -        global to evaluate in the temporary batch file for calling the
110677 -        Windows start command op.  of 80 positions to capture the
110678 -        User's ID needed to create a spec in the start session batch
110679 -        op.
110680 -
110681 -
110683 -  ..
110684 - Line 380, ref OF 8 099G, -label lpa1 in 070301 about 60 lines below
110685 -
110686 -    -if @13 != 800 -goto ainCS..................... ref SDS 0 QC5O
110687 -    loc_cur 0 9
110688 -    setcnt 86 180
110689 -    macro 1182
110690 -
110691 -        If not a current date op, then process archived diary spec in
110692 -        batch op for Windows start session.  loc_cur 0 9 captures the 4
110693 -        place filename for current SDS diary records created by the AI
110694 -        report.  setcnt 86 180 sets up macro 1182 to put the filename
110695 -        in counters starting at 180 for transfer into the batch file
110696 -        for Windows start session.
110697 -
110698 -
110700 -     ..
110701 -    NB Deletes AI Report Content Until All Records Processed
110702 -
110703 -
110704 - Line 390, ref OF 8 TH4M, -label ainCS in 070301
110705 -
110706 -    -label ainCS
110707 -    of 0
110708 -    z 85 85
110709 -    errorcnt 0 0
110710 -    nb
110711 -    -if @0 > 0 -goto eoR............................ ref SDS 0 XA6O
110712 -    down
110713 -    immed dd
110714 -
110715 -        ID has been captured for this record. z 85 85 zones last char
110716 -        of User ID field which is beyond anything else.  nb can find
110717 -        the specification for the next SDS record, and if there is an
110718 -        error 0 > 0 then all the records have been processed and
110719 -        counter 0 > 0 will be recognized on the next pass, per above.
110720 -        ref SDS 0 QC6J  If this is not the last record, then do a down
110721 -        and immed dd deletes the current segment to bring the next one
110722 -        to the top of the file ready for the next pass.
110723 -
110724 -
110725 -
110726 -
1108 -

SUBJECTS
Set Command Repeated in Procses Using Windows Start Command Causes E
Set Commands Added to SDS.BAT to Support All Virtual Memory Operatio
Set Commands Added to DOS.BAT to Support All Virtual Memory Operatio
Set Commands Added to Medit.bat to Support All Virtual Memory Operat

2306 -
230701 -     ..
230702 -    Set Command Impacts Environment Space
230703 -    Windows Start Command Batch Process Each Record in Separate Memory
230704 -
230705 -    Follow up ref SDS 13 0001.
230706 -
230707 - Line 360, ref OF 8 JD7M, -label eoR in 070301 about 50 lines below
230708 -
230709 -    -label eoR
230710 -    e tje4h
230711 -    macro 301
230712 -
230713 -        Open temporary file to construct temporary batch file.
230715 -     ..
230716 -    immed 5a
230717 -    ins_text !@echo off!
230718 -    rel_cur 1 0
230719 -    ins_text !set AIR=%systemroot%\system32\cmd.exe /C start /I /b /wait "AI"!
230720 -
230721 -        set command for Microsoft cmd and start commands created
230722 -        temporarily for entering a spec in the batch file in a way that
230723 -        does not exceed the batch command line length.
230725 -           ..
230726 -          Actually, this turned out not to work.  Think the problem is
230727 -          repeated uses of the command that occurs in the loop for
230728 -          processing a lot of records, may fill up something in Windows
230729 -          or DOS.  This came to light when the process ran on c13 using
230730 -          a P4 processor, and failed on c11 using a P3 processor.
230732 -           ..
230733 -          Had to modify original work using set command in system
230734 -          launch ops developed on 031020, ref SDS 13 OS71, by putting
230735 -          set commands needed for reports into the batch files for
230736 -          sds.bat, ref OF 12 LV4K, mj.bat ref OF 11 and dos.bat.
230737 -          ref OF 10 LV4K  This change means that when a report is
230738 -          called, it will not have to run the same set command over and
230739 -          over, because the envirnment will already be part of SDS,
230740 -          Medit and DOS.
230742 -           ..
230743 -          This might influence long reports.
230744 -
230745 -              [On 040422 ran these systems on Windows XP computer
230746 -              successfully. ref SDS 16 6I4L
230747 -
230749 -     ..
230750 -    rel_cur 1 0
230751 -    ins_text !c:!
230752 -    rel_cur 1 0
230753 -    ins_text !cd\sd\10!
230754 -    rel_cur 1 0
230755 -    ins_text !%AIR% c:\sd\01\e d:\sd\08\00101\02\yy\mm\dd\hhmmss c:\sd\03\070302!
230756 -
230757 -        Call target file read from the AI report list and open the
230758 -        record in the 2nd memory session and process with the new macro
230759 -        file 070302. ref SDS 0 RK3I
230760 -
230761 -
230763 -  ..
230764 - Line 390, ref OF 8 TP8I, -label lpa1 in 070301 about 80 lines below.
230765 -
230766 -    loc_cur 0 27
230767 -    macro 91
230768 -    macro 88
230769 -    loc_cur 0 1
230770 -    rel_cur 1 0
230771 -    ins_text !exit!
230772 -
230773 -        Enter the SDS record ID in the temp batch file, and then enter
230774 -        an "exit" command to close the batch file op after the code
230775 -        runs.
230777 -     ..
230778 -    save c:\sd\10\stufqe.bat
230779 -    ecur 45
230780 -    dose /c c:\sd\10\stufqe.bat
230781 -
230782 -        Write the commands to a temporary batch file stufqj.bat.  ecur
230783 -        45 returns to the Action Item report.  dose command executes
230784 -        stufqj.bat to process the record with new macro file 070302,
230785 -        per below. ref SDS 0 RK3I  Then control returns to 070301 to
230786 -        load the results into the AI SDS record for reviewing action
230787 -        items.
230788 -
230790 -     ..
230791 -    References Update Links in Action Items
230792 -
230793 -
230794 - Line 420, ref OF 8 ET3K, -label lpa1 in 070301 about 120 lines below
230795 -
230796 -    z 7 7
230797 -    l /j/
230798 -    loc_cur 3 10
230799 -    macro 85
230800 -    of 81
230801 -    loc_cur 0 1
230802 -    macro 851
230803 -    of 0
230804 -    up
230805 -    macro 8
230806 -    immed c
230807 -
230809 -     ..
230810 -    Complete Report Format
230811 -    Format Report with Final Organization
230812 -
230814 -  ..
230815 - Line 640, ref OF 8 4Z5M, -label fin in 070301
230816 -
230817 -
230818 -
230819 -
230820 -
230821 -
230822 -
2309 -

SUBJECTS
Action Item Review Meeting in Schedule Process Each SDS Record S

2803 -
280401 -  ..
280402 - 070302  Format Original SDS Record for Action Item Review Record
280403 -
280404 - This is a new processor called by 070301 setting up stufqj.bat that
280405 - launches a cmd start session of memory to open an SDS record and
280406 - remove everything but the action items.   The process converts the
280407 - control file, 0wz3, for opt tech sort that constructs the initial
280408 - report, into an Medit search routine to select record segments in each
280409 - SDS record where action items occur that meet the specification.  The
280410 - default action item report for an individual called from the Schedule
280411 - covering the past 3 or 4 months, gets all action items in the record,
280412 - i.e., there is no selection for subjects. An action item report for
280413 - particular subject deletes everything that does not meet the spec.
280414 - Then the remaining segments are formatted into an SDS record for an
280415 - action item review meeting with links back to the original source.
280417 -  ..
280418 - Line 40, ref OF 9 QZ5J, in 070302
280419 -
280420 -    macro 150
280421 -    setcnt 47 2
280422 -    gfname
280423 -    setgbl 285 @10
280424 -    setgbl 286 @11
280425 -    setgbl 287 @12
280426 -    setgbl 288 @13
280427 -    setgbl 289 @14
280428 -
280429 -        Start in SDS record mode so that para can be justified within
280430 -        line number scheme.  gfname and place user ID in standard
280431 -        position for macro file 04405 to conform subject descriptions,
280432 -        per below, ref SDS 0 8C5J, and to support action item review
280433 -        drawing on work from multiple SDS users, per below. ref SDS 0
280434 -        MJ4F
280435 -
280436 -
280438 -     ..
280439 -    User ID Posted End of User's Name on Record ID
280440 -
280441 -
280442 - Line 50, ref OF 9 QZ5J, in 070302
280443 -
280444 -    setcnt 15 0
280445 -    macro 1180
280446 -    of 87
280447 -    setcnt 86 10
280448 -    macro 1181
280449 -    of 0
280450 -    loc_cur 3 1
280451 -
280452 -        Put User's ID at end of name on line 1 for the record ID.  This
280453 -        is used in 070301 to format the SDS review record by
280454 -        constructing an entry in the SDS Reference field for the links.
280455 -        We need the User ID in case the record finds multiple User's
280456 -        records.
280457 -
280458 -
280460 -     ..
280461 -    References Deleted to Reduce Burden on Memory and Speed Processing
280462 -
280463 -
280464 - Line 90, ref OF 9 YI5K, in 070302
280465 -
280466 -    line 4
280467 -    immed dd
280468 -    z 1 3
280469 -    l /04 /
280470 -    loc_cur 0 1
280471 -    ic 42
280472 -    up 5
280473 -    -if @1 > 10 up 2
280474 -    z 5 5
280476 -         ..
280477 -        Start by removing references since they are not needed.
280478 -        Hopefully, this reduces the burden on memory because we are
280479 -        going to add a few lines to capture the action items, until the
280480 -        lines are deleted later.
280481 -
280482 -
280484 -     ..
280485 -    Summary Objective Removed for Uniform Processing
280486 -    Citations and Links Flag for Removal in Action Item Meeting Record
280487 -
280488 -
280489 - Line 110, ref OF 9 YJ6J, in 070302
280490 -
280491 -    nb
280492 -    down 2
280493 -    immed d
280494 -
280495 -        Summary and Objective line is deleted in all of the records at
280496 -        this level in 070302 processing.  The code in 070301 will
280497 -        restore a single summary/objective line along with an anchor
280498 -        and follow up line when the entire is formatted after
280499 -        assembling all the records.
280501 -     ..
280502 -    z 8 85
280503 -    c/ ref / œef /* 2
280504 -
280505 -        Change all citations from "ref" to "œef" to facilitate removing
280506 -        citation strings in the narrative so that the only links to
280507 -        references in the SDS record for action item review meetings
280508 -        will be the links back to the original source.
280509 -
280510 -
280512 -     ..
280513 -    J Headlines Converted for Action Items
280514 -    Line Number Flags Removed Action Items Converted to Headlines
280515 -
280516 -
280517 - Line 130, ref OF 9 G14S, in 070302.
280518 -
280519 -    z 7 7
280520 -    c/s/ /* 1
280521 -    c/S/ /* 1
280522 -    c/j/ /* 1
280523 -    c/h/ /* 1
280524 -    c/m/ /* 1
280525 -    c/k/j/* 1
280526 -    c/f/j/* 1
280527 -
280528 -       Since action items will be headlines in the SDS record for
280529 -       Action Item review, we can set this globally by changing all
280530 -       headline flags to off, except for action items, and then
280531 -       changing action items to headlines.
280532 -
280533 -
280535 -     ..
280536 -    Report Type Determines Action Item Selections
280537 -
280538 -
280539 - Line 120, ref OF 9 KT3M, 070302
280540 -
280541 -    markcur 1
280542 -    e 0wz3
280544 -       ..
280545 -      markcur 1 identifies the SDS record where processing will occur
280546 -      in order to come back. e 0wz3 opens the Opt Tech Sort selection
280547 -      spec.  Had to change the name of this file from 1yz3 to 0wz3
280548 -      because the report macro maintains 1y* each pass and so 1yz3 is
280549 -      not available for 070302.  Changed macro 120 in 000007,
280550 -      ref OF 13 629I, and macro file 061122, ref OF 5 OZ6H, which is
280551 -      called in 000007, ref OF 13 6290,
280553 -       ..
280554 -      A typical 0wz3 selection spec looks like....
280555 -
280556 -
280557 -          General case for all subjects the last 3 months...
280558 -
280559 -          outrec(1,24,crlf)
280560 -          in(1,6,c,ge,"030824",and,1,6,c,le,"031122",
280561 -       *  and,28,2,c,eq,"K1",
280562 -          and,66,6,c,eq,"010201")
280563 -          s(1,19,c,a,23,2,c,a)
280565 -           ..
280566 -          Subject specification looks like....
280568 -           ..
280569 -          outrec(1,24,crlf)
280570 -          in(1,6,c,ge,"011023",and,1,6,c,le,"031122",
280571 -       *  and,75,8,c,eq,"03 00050",
280572 -          and,15,5,c,eq,"00101",
280573 -          and,66,6,c,eq,"010201")
280574 -          s(1,19,c,a,23,2,c,a)
280576 -       ..
280577 -      In each case only line 3 is needed....
280578 -
280579 -       *  and,28,2,c,eq,"K1",
280580 -       *  and,75,8,c,eq,"03 00050",
280582 -       ..
280583 -      The 1st number 28 determines whether this is a general selection
280584 -      for all subjects, or 75 establishes this is a subject based
280585 -      selection process.  If it is a general selection, there is no
280586 -      processing to do for subjects, so the entire routine is skipped.
280587 -      If it is a subject selection, then the 2nd number is used to set
280588 -      the field length to search, and the spec string in quotes is used
280589 -      to find the lines that meet the spec.
280590 -
280591 -
280593 -  ..
280594 - Line 130, ref OF 9 NC4L, in 070302
280595 -
280596 -    top
280597 -    immed 2d
280598 -    loc_cur 3 5
280599 -    strcnt 1 2
280600 -    -if @2 = 28 -goto fal3m...................... ref SDS 0 HC5O
280601 -
280602 -        In 0wz3 delete 1st two lines and put cursor on the number to
280603 -        determine the type of action item report called.
280604 -
280605 -
280607 -     ..
280608 -    Branch Code Separately for Specified Subjects and All Subjects
280609 -
280610 -
280611 - Line 240, ref OF 9 WA5I, -label fal3m in 070302
280612 -
280613 -    -label fal3m
280614 -    setgbl 1 @1
280615 -    ecur 1
280616 -    getgbl 50 1
280617 -    -if @50 = 28 -goto aaifp....................... ref SDS 0 QM5O
280618 -
280619 -        Code completes evaluation of 0wz3 that has the control file for
280620 -        the action item report created in macro file 06112 calling
280621 -        macro 120 in 000007 per above. ref SDS 0 VM6O  setgbl 1 @1
280622 -        makes the flag for report type global to pass from 0wz3 into
280623 -        the SDS record to control processing.  ecur 1 switches from
280624 -        file 0wz3 to the SDS record being processed.  getgbl 50 1 saves
280625 -        the process type so it will not be changed by other activity.
280626 -        -if @50 = 28 this is a generic action item that did not specify
280627 -        a subject, so -goto aaifp. ref SDS 0 QM5O
280628 -
280629 -
280631 -  ..
280632 - Line 280, ref OF 9 8H8M, -label aaifp in 070302
280633 -
280634 -    -label aaifp............................ ref SDS 0 HC5O
280635 -    purge 0wz3
280636 -    top
280637 -    z 3 3
280638 -    c/*/0/* 1
280639 -
280640 -        -label aaifp branches is the branch for general AI report on
280641 -        all subjects, per above.  Remove temp * symbols developed by
280642 -        gosub ddlp so line numbers are restored to normal format to do
280643 -        the next step.
280644 -
280646 -     ..
280647 -    Subjects General All Process Control Fields 3 Description Lines
280648 -
280649 -
280650 - Line 290, ref OF 9 OG4N, -label aaifp in 070302
280651 -
280652 -    -if @50 = 28 -gosub 3sdl........................ ref SDS 0 RG5F
280653 -
280654 -        For the general subject 3 month action item report, go remove
280655 -        subject description lines and leave only 3 for all Control
280656 -        Fields to reduce burden on memory and provide uniform report.
280657 -
280659 -     ..
280660 -    Subjects Select Record Segments for Action Items
280661 -
280662 -
280663 - Line 260, ref OF 9 MJ4H, -label fal3m in 070302 about 40 lines below
280664 -
280665 -    top
280666 -    setcnt 0 0
280667 -    -gosub ddlp.............................. ref SDS 0 8B6I
280668 -
280669 -        Call subroutine ddlp that finds record segments where specified
280670 -        subject for action item report occurs, and removes all the
280671 -        other subjects lines control fields, ref SDS 0 8B6I, so that
280672 -        the next step to format action items only includes specified
280673 -        subjects.  This routine also runs macro file 04405 to conform
280674 -        descriptions to the Subject Index.
280675 -
280676 -
280677 -
280679 -     ..
280680 -    Primary Loop Find Action Items Across Record Segments
280681 -
280682 -
280683 - Line 320, ref OF 9 OR8K, -label lpf in 070302
280684 -
280685 -    -label lpf
280686 -    z 7 7
280687 -    errorcnt 0 0
280688 -    l /j/
280689 -    -if @0 > 0 -goto format
280690 -    setcnt 112 0
280691 -    setcnt 113 0
280692 -
280693 -        Only action items have a "j" in column 7; everything else has
280694 -        been removed to facilitate processing, per above.
280695 -
280696 -
280698 -     ..
280699 -    Subsidiary Loop Find Action Items within Record Segment
280700 -
280701 -
280702 - Line 340, ref OF 9 OW4K, -label dnaiJ in 070302
280703 -
280704 -    -label dnaiJ
280705 -    macro 541
280706 -    setcnt 118 @4
280707 -    linecnt 140 0
280708 -
280709 -        macro 541 moves to left margin and puts value in counter 4;
280710 -        setcnt 118 @4 saves left margin value for reuse.  linecnt 140 0
280711 -        identifies the location for top of action item found by primary
280712 -        loop, per above. ref SDS 0 YK4M
280713 -
280714 -
280715 -
280717 -     ..
280718 -    Link to Original Source Find Appropriate Anchor for Context
280719 -
280720 -
280721 - Line 380, ref OF 9 EE4G, -label lpanc in 070302
280722 -
280723 -    -label lpanc
280724 -    l-/</
280725 -    -if @0 > 0 -goto nafai
280726 -    loc_cur 3 1
280727 -    macro 541
280728 -    -if @12 > @137 -goto uaisds
280729 -    -label nafai
280730 -    line @145
280731 -    loc_cur 3 1
280732 -    down
280733 -    eol
280734 -    rel_cur 0 -4
280735 -    setcnt 86 2
280736 -    macro 1182
280737 -    -goto ail
280738 -
280739 -        Look for an anchor symbol, and if not there, or if greater than
280740 -        action item above, then use the anchor for the prior action
280741 -        item.
280742 -
280743 -
280744 -
280746 -     ..
280747 -    Shift Action Item Description to Common Left Margin for Report
280748 -
280749 -
280750 - Line 410, ref OF 9 E56G, -label shift in 070302
280751 -
280752 -    -label shift
280753 -    setcnt 89 0
280754 -    savescr 2
280755 -
280756 -        Set up to shift the lines to the left margin for the SDS record
280757 -        to conduct an action item review meeting.
280758 -
280759 -
280761 -     ..
280762 -    Citations Removed from Action Item Narrative
280763 -
280764 -
280765 - Line 420, ref OF 9 Y83K, -label lpRef in 070302
280766 -
280767 -     -label lpRef
280768 -     setcnt 0 0
280769 -     fr / ref /
280770 -     -if @0 > 0 -goto spLi
280771 -     chrcnt 88 0
280772 -     rel_cur 0 -1
280773 -     ins_text !cOFxxxxxx!
280774 -     rel_cur 0 -3
280775 -     macro 79
280776 -     chrcnt 1 0
280777 -     -if @1 = 32 macro 79
280778 -     setcur 89 0
280779 -     -if @88 = 79 -if @89 > 66 setcnt 89 999
280780 -     -if @88 != 79 -if @89 > 65 setcnt 89 999
280781 -     -goto lpRef
280782 -
280783 -        Remove citations from the text, since they are in the original
280784 -        and so can be accessed at that location to provide alignment if
280785 -        needed in the new record.
280786 -
280787 -
280789 -     ..
280790 -    Justify Action Item Description within Standard Margins
280791 -
280792 -
280793 - Line 560, ref OF 9 EQ7F,
280794 -
280795 -    line @140
280796 -    macro 49
280797 -    down
280798 -    loc_cur 0 17
280799 -
280800 -        line @140 returns to top of action item description after all
280801 -        the lines have been shifted to column 17 for a common left
280802 -        margin required by a "report," per above. ref SDS 0 8C5N
280803 -
280804 -
280805 -
280806 -
280808 -     ..
280809 -    Subroutine Select Record Segments for Specified Subjects
280810 -
280811 -
280812 - Line 710, ref OF 9 XU6J, -label ddlp in 070302
280813 -
280814 -    -label ddlp
280815 -    @0wz3
280816 -    -if @0 = 0 -goto pcfrs..................... ref SDS 0 QN4O
280817 -    immed a
280818 -    immed dd
280819 -    z 3 3
280820 -    l-/*/
280821 -    immed dd
280822 -    -return
280823 -
280824 -        Subroutine finds specified subject account in Control Field and
280825 -        transfers control to routine that removes lines above the
280826 -        specified subject, ref SDS 0 QN4O, and also below the bottom
280827 -        of the lines for the specified subject.
280828 -        This works because line in
280829 -        the Control Field are sorted, so that all of the lines in a
280830 -        Control Field for a particular subject are contiguous.
280831 -
280833 -     ..
280834 -    Control Field Lines Contains Only Specified Subjects
280835 -
280836 -
280837 - Line 770, ref OF 9 K65M, -label pcfrs in 070302
280838 -
280839 -    -label pcfrs
280840 -    down
280841 -    chrcnt 1 0
280842 -    -if @1 > 32 -goto dgd......................... ref SDS 0 QO4J
280843 -    immed d
280844 -     -goto ddlp................................... ref SDS 0 QO5H
280845 -    -goto pcfrs
280846 -
280847 -        Delete lines above the 1st line in the Control Field with the
280848 -        subject account in the report specification, found by the prior
280849 -        step. ref SDS 0 8B6I  The cursor is on col 3 so scrolling down
280850 -        when a non-blank char is encountered this the top of the
280851 -        Control Field.  Control is then transferred to an op that
280852 -        removes lines below the specified subject account. ref SDS 0
280853 -        QO4J
280854 -
280856 -     ..
280857 -    -label dgd
280858 -    down 2
280859 -    chrcnt 1 0
280860 -    -if @1 = 42 -goto 1strS...................... ref SDS 0 QO8F
280861 -
280862 -        This is the top of a Control Field, per above. ref SDS 0 QN4O
280863 -        Need at this location to save 2 lines above the Control Field
280864 -        to provide uniform formatting, and delete all lines above this
280865 -        Control Field to below the last action item.  So, scroll down 2
280866 -        lines and test for a "*" which is entered by a sub-process to
280867 -        identify the end of a record segment with the specified subject
280868 -        account lines in the Control Field.
280869 -
280871 -  ..
280872 - Line 760, ref OF 9 N67F, -label ddlp in 070302 about 40 lines below
280873 -
280874 -    immed dd
280875 -    z 3 3
280876 -    l-/*/
280877 -    immed dd
280878 -
280879 -        Begin block delete, and look for * in col 3 which is several
280880 -        lines below the bottom of the last action item placed there by
280881 -        the code that finds and formats action items.  This has the
280882 -        effect of collapsing the record, deleting all lines that are
280883 -        not relevant to the action item.  This is a significant change
280884 -        in design and philosophy from the prior scheme developed on
280885 -        970505.  Previously, the code found an action item in the
280886 -        original file and and transferred data into another file which
280887 -        increased the size of the other file constantly increasing
280888 -        demands on memory. Now, we simply delete lines constantly
280889 -        reduce the demand on memory.
280890 -
280892 -  ..
280893 - Line 820, ref OF 9 T63F, -label dgd in 070302 about 50 lines below
280894 -
280895 -    z 53 @50
280896 -    down
280897 -    -label 1strS
280898 -    up 3
280899 -    macro 6
280900 -    zonereps
280901 -    setcnt 5 0
280902 -
280903 -        After deleting lines that are not needed above the Control
280904 -        Field z 53 @50 resets the zone to process the control subjects;
280905 -        scroll back up to the first line in the Control Field and flag
280906 -        the location with macro 6 for mark 1.  down is needed to
280907 -        integrate this process with another one. This will not work
280908 -        because the lines will be stable for the rest of this process,
280909 -        until more lines are deleted during formatting of an action
280910 -        item description.
280911 -
280912 -
280914 -     ..
280915 -    Control Field Delete Lines that Do Not Meet Report Specification
280916 -
280917 -
280918 - Line 860, ref OF 9 WH6I, -label lpb1h in 070302
280919 -
280920 -
280921 -    -label lpb1h
280922 -    up
280923 -    addcnt 5 1
280924 -    repscnt 1 0
280925 -    -if @1 = 0 -goto lpb1h
280926 -    chrcnt 1 0
280927 -    -if @1 > 32 -goto bcff........................ ref SDS 0 8C8O
280928 -
280929 -        Scroll up and compare each subject account with the specified
280930 -        account string captured above with zonereps. ref SDS 0 QO8F
280931 -        When a line is encountered that is not the specified subject,
280932 -        then all of the lines that meet the specified subject account
280933 -        have been scrolled up, and all the remaining lines can be
280934 -        deleted.  chrcnt 1 0 captures the position in col 3, so when 1
280935 -        is not a space, it means the bottom of the Control Field is
280936 -        reached, so it is not necessary to delete any lines, because
280937 -        the last line in the Control Field meets the specification.
280938 -
280940 -  ..
280941 - Line 870, ref OF 9 WJ7L, -label lpb1h in 070302 about 10 lines below
280942 -
280943 -    immed 2r
280944 -    immed dd
280945 -    z 3 3
280946 -    nb
280947 -    down
280948 -    immed dd
280949 -
280950 -        This occurs when the last line in the Control Field does not
280951 -        meet the specified subject account specification, so lines have
280952 -        to be deleted.  immed 2r creates extra lines so that a block
280953 -        command can be used with nb.  immed dd starts the block
280954 -        command.  z 3 3 specifies col 3 which is blank in a Control
280955 -        Field.  nb then jumps to the bottom of the Control Field to the
280956 -        next non-blank line.  down places the last Control Field line
280957 -        on the current line, and immed dd completes the process of
280958 -        deleting all lines in the Control Field that do meet the
280959 -        subject account report specification.
280960 -
280961 -
280963 -       ..
280964 -      Subject Descriptions Conform to Subject Index - 04405 Failed
280965 -      04405 - Subject Descriptions Conform to Subject Index Failed
280966 -
280967 -
280968 - Line 740, ref OF 9 ST4M, -label bcff in 070203 about 50 lines below
280969 -
280970 -    -label bcff
280971 -    -if @5 > 0 -goto omitSD
280972 -    macro 12
280973 -    macro 7
280974 -    macro 7
280975 -    down
280976 -    setcnt 125 50
280977 -    setcnt 127 888
280978 -    @c:\sd\03\04405  ............................. ref SDS 0 8C4K
280979 -    macro 9
280980 -
280981 -        Conform descriptions to the subject index.  setcnt 125 50 is
280982 -        used by macro file 04405 to conform descriptions to subject
280983 -        accounts.  setcnt 126 888 tells 04405 this is an action item op
280984 -        and so do not report an error when an account is not found in
280985 -        the subject index for an entry in the control field, but
280986 -        instead, enter a notice of the error and complete the op, per
280987 -        below. ref SDS 0 8D3K  Run 04405 to opens SI and finds accounts
280988 -        then enter descriptions. ref SDS 0 8C4K
280990 -         ..
280991 -        This feature is problematic.  When connected, we get "Out of
280992 -        environment space" messages from Windows, and on some large
280993 -        records, Medit fails with "Out of memory" message.  Tried to
280994 -        reduce impact by calling 04405 only when there are fewer than 8
280995 -        subject lines in the Control Field.  This reflects the fact
280996 -        that when there are a lot of Control Field lines in a record
280997 -        segment, often many are cross references to the same subject in
280998 -        a different context.  Therefore, the user typically deletes
280999 -        duplicate descriptions when needed.  Thus, where there are many
281000 -        control field lines, generally there are fewer subject
281001 -        descriptions.
281003 -         ..
281004 -        In any case, wound up disconnecting 04405.  People can run it
281005 -        when needed for the action item review meeting record.
281006 -
281007 -
281009 -         ..
281010 -        3 Subject Description Lines Retained All Reports
281011 -
281012 -        Decided instead to retain only 3 description lines to save
281013 -        memory.
281015 -  ..
281016 - Line 940, ref OF 9 MN5F, -label bcff in 070302
281017 -
281018 -    -gosub 3sdl................................. ref SDS 0 RG5F
281019 -    loc_cur 3 3
281020 -
281021 -        After deciding to disconnect call to 04405, per above,
281022 -        ref SDS 0 8C8O, decided to try deleting all but 3 subject
281023 -        description lines, calling new subroutine 3sdl, per below.
281024 -
281025 -             Call subroutine for generic
281026 -             action item report over past
281027 -             three months on all subjects......... ref OF 9 OG4N
281029 -              ..
281030 -             Call subroutine for subject
281031 -             action item report................... ref OF 9 MN5F
281033 -              ..
281034 -             Subroutine remove all but 3
281035 -             subject descriptions................. ref OF 9 SF4H
281037 -         ..
281038 -        This is necessarily extremely arbitrary in keeping only the
281039 -        top three description lines.  User's can conform any
281040 -        particular control field using 04405 by clicking above the
281041 -        Control Field beyond "Subject/File"
281042 -
281043 -
281045 -  ..
281046 - Line 990, ref OF 9 NQ4K, -label 3sdl in 070302
281047 -
281048 -    -label 3sdl
281049 -    -if @50 != 28 -goto pssR....................... ref SDS 0 RG8L
281050 -
281051 -        When subjects are specified, -goto pssR
281053 -     ..
281054 -    up 5
281055 -    errorcnt 0 0
281056 -    z 3 3
281058 -         ..
281059 -        Processing general action item report for all subjects called
281060 -        from the Schedule Manage menu.  This will find all control
281061 -        fields and call a subroutine that makes the subject
281062 -        descriptions 3 lines or less.  Starting at top of file, so
281063 -        scroll up 5 lines past Contacts field, so that locating a space
281064 -        on col 3 will find the first control field line. that locate
281066 -     ..
281067 -    -label lpcfSd
281068 -    l / /
281069 -    -if @0 > 0 -goto ecfnS.......................... ref SDS 0 RG7O
281070 -    nb
281071 -    -if @0 > 0 -goto ecfnS.......................... ref SDS 0 RG7O
281072 -
281073 -        Find a blank space on col 3 and then nb.  If either fail, all
281074 -        control fields have been processed.
281076 -     ..
281077 -    down
281078 -    -gosub pssR................................... ref SDS 0 RG8L
281079 -    -goto lpcfSd.................................. ref SDS 0 RG6I
281080 -
281081 -        Control field found; down positions for standard op in next
281082 -        process -gosub pssR
281084 -     ..
281085 -    -label ecfnS
281086 -    top
281087 -    -return.................................. ref SDS 0 8H8M
281088 -
281089 -        Call control fields processed for generic action item report
281090 -        for all subjects, so return to process action items.
281091 -
281092 -
281094 -     ..
281095 -    -label pssR
281096 -    loc_cur 5 8
281097 -    setcnt 2 1
281098 -
281099 -                                 This saves memory because there can be up to 20
281100 -                                 lines of subject descriptions for a Control Field,
281101 -                                 so for a report with 100 records, that can be up
281102 -                                 to 200 lines, which be 20K.
281103 -
281104 -
281105 -    -label tmp1
281106 -    chrcnt 1 0
281108 -      ..
281109 -
281110 -    -if @1 = 205 -return
281111 -    addcnt 2 1
281112 -    -if @2 < 4 up
281113 -    -if @2 > 3 immed d
281114 -    -goto tmp1
281115 -
281116 -
281118 -     ..
281119 -    Format Completion of SDS Record for Record to Review Action Items
281120 -
281121 -
281122 - Line 800, ref OF 9 UY4N, -label format in 070302
281123 -
281124 -
281125 -
281126 -
281127 -
281128 -
281129 -
2812 -

SUBJECTS
Control Fields Subjects Conform Descriptions to Control Field Listing
070302 Modify Code in 04405 to Support Ops in 070302 that Conform Des
Chained Segmeneted Subject Index Change Code in 04405 to Not Cycle Ba

3005 -
300601 -  ..
300602 - 04405 Modified to Conform Subjects in Action Item Reports
300603 - Subjects Descriptions Conformed to Subject Index for AI Reports
300604 -
300605 - Modified the code in 04405 to support code in 070302 that produces a
300606 - record for meeting to review action items.  Ultimately had to
300607 - disconnect the call to 04405, because the design caused memory to
300608 - fail.
300609 -
300610 -        [On 040305 eliminated 04405 and put functionality in 035012
300611 -        that calls 03501 in a separate memory segment; may help solve
300612 -        this problem, but had not tried it. ref SDS 15 W54M
300614 -  ..
300615 - Line 50, ref OF 3 3P6F, in 04405
300616 -
300617 -    -if @125 > 40 -goto cdacsi...................... ref SDS 0 4X6F
300618 -
300619 -        To call 04405 for conforming the descriptions to the subject
300620 -        index, requires 125 > 40, so set set 125 50, per above.
300621 -        ref SDS 0 8C8O
300622 -
300623 -
300624 -
300625 -
300627 -  ..
300628 - Line 120, ref OF 3 9V4I, -label cdacsi in 04405
300629 -
300630 -    -label cdacsi........................... ref SDS 0 8C4K
300631 -    tl 0
300632 -    immed /
300633 -    loc_cur 3 8
300634 -    setcnt 117 0
300635 -    z 6 6
300636 -    l /-/
300638 -         ..
300639 -        Just starting to positon Control Field for processing.
300640 -
300642 -  ..
300643 - Line 210, ref OF 3 9477, -label 9y8uX in 04405 about 30 lines below
300644 -
300645 -    e c:\sd\03\04405
300646 -    line                      && *%8w
300647 -    loc_cur 4 14
300648 -    macro 92
300649 -
300650 -        macro 92 requires User ID in counters 285 - 289, which is
300651 -        developed when the file is opened, per above. ref SDS 0 YJ4I
300652 -
300653 -
300655 -     ..
300656 -    Subjects Conformed in Chained SI Segments Change Design
300657 -    Search Fails in Subject Index Chained Segment Report Error
300658 -
300659 -
300660 - Line 750, ref OF 3 EQ7H, -label gF_648 in 04405 about 50 lines below
300661 -
300662 -    rel_cur 0 2
300663 -    chrcnt 133 0
300664 -      -if @133 = 36 -goto wSTRd
300665 -    -if @133 = 36 -goto gF_Airor.................. ref SDS 0 N59J
300666 -
300667 -        Changed this code to avoid a nesting error when a search
300668 -        encounters a chained segment.  If the search fails, then the
300669 -        code should branch to error rather attempt to try a prior
300670 -        level, as occurs at the primary level, because this creates a
300671 -        loop starting over at the primary level.
300672 -
300673 -
300675 -  ..
300676 - Line 950, ref OF 3 W68M, -label gF_Airor in 04405
300677 -
300678 -    -label gF_Airor
300679 -    setgbl 1 0
300680 -    -if @133 = 36 setgbl 1 999
300681 -    ecur 45
300682 -    getgbl 1 1
300683 -    -if @1 = 999 setcnt 127 888
300684 -    purge sndx
300685 -    -goto aIr.................................. ref SDS 0 8D3K
300686 -
300687 -        Change error handling for Action Item report record by entering
300688 -        a notice in subject description, rather than stop processing.
300689 -        Called when search fails in a Subject Index chained segment,
300690 -        rather than cycle back, per above. ref SDS 0 EP7J
300691 -
300692 -
300694 -  ..
300695 - Line 980, ref OF 3 Z49J, -label fIn in 04405
300696 -
300697 -    -label aIr
300698 -    setcnt 117 1112
300699 -    -label fIn
300700 -    -if @117 != 1112 -goto cdfnd
300701 -    -if @127 = 888 -goto aien
300702 -    beep
300703 -    down 8
300704 -    loc_cur 12 53
300705 -    errormsg  Code not found
300706 -    -goto erR
300707 -
300708 -        Added -if @126 = 888 -goto aien based on flag set in 070301,
300709 -        ref SDS 0 8C8O, to identify action item report op, so this code
300710 -        will not return error message, but proceeds and enters a
300711 -        default subject description that allows report to run.
300712 -
300714 -  ..
300715 - Line 1040, ref OF 3 TN3G, -label aien in 04405
300716 -
300717 -    -label aien
300718 -    purge sndx
300719 -    macro 9
300720 -    immed r
300721 -    macro 641
300722 -    -if @117 = 1112 -if @126 = 888 ins_text "Subject Description Not Found for Account!"
300723 -    setgbl 206 0
300724 -    -if @117 != 1112 macro 1189
300725 -    setcnt 117 0
300726 -
300727 -        Added conditionals when 117 = 1112 enter default message in
300728 -        standard position in the control field description section, so
300729 -        the action item report is completed rather than stopped.
300730 -
300731 -
300732 -
300733 -
300734 -
300735 -
300736 -
3008 -