CONTACTS 

SUBJECTS
SDS, Executive Services, 910121
Data Security; LAN
Concepts & Plans, Executive Services
Diary Summary, 022F02
User ID Management

1007 -
1007 -    ..
1008 - Summary/Objective
1009 -
100901 - Follow up ref SDS 6 0000.
100902 -
100903 - Work today may have improved managing User ID's for multiple SDS
100904 - sessions.
100906 -  ..
100907 - This work places greater reliance on local current counters 285 289,
100908 - in Schedule and SDS records.  The Session globals 295 299 are only
100909 - used now for report screens, and there may be no reason to use them at
100910 - all because of the new concept on managing User ID access developed
100911 - today.
100912 -
100913 -      [On 940322 continued concept. ref SDS 7 0975]
100915 -  ..
1010 -
1011 -
1012 - Concept
1013 -
101301 - Background is cited in record yesterday. ref SDS 6 5880
101302 -
101303 - Previously we have tried to apply a procedure that includes:
101304 -
101305 -                       Original User
101306 -                       Session User
101307 -                       Current User
101308 -
101309 -    ...the objective was to allow a single User to access information
101310 -    from another User's SDS records, and to apply various SDS func-
101311 -    tions, such as access to SI, Diary, Reports, on an incremental
101312 -    basis depending upon which version of the SDS progam was started by
101313 -    the original User.  A procedure was tried using global counters in
101314 -    macro 000004 to move different global counters in the current local
101315 -    counter 295 289 for posting the User ID to an actual command.
101317 -     ..
101318 -    The rational for prior method is on 921001. ref SDS 2 7603
101320 -     ..
101321 -    Experience has shown this has not worked very well.
101322 -
101324 -  ..
101325 - Today I am trying another method of just using
101326 -
101327 -                       Original
101328 -                       Current
101329 -
101330 -    The current local counter will be maintained by moving it to
101331 -    another set of local counters before any User ID is read in a
101332 -    current SDS screen and transferred to the current global counters,
101333 -    then restoring the initial current locals.
101334 -
101336 -  ..
1014 -
1015 -
1016 - Analysis
1017 -
101701 - At this point we are only dealing with getting Diary Summaries.  We
101702 - want an Executive to be able to get a Diary for the User of the record
101703 - on the screen, or to specify something else.  Other Users may only get
101704 - full chronological diaries for their own account.  If they specify
101705 - another User ID, the code will switch back to the default User ID,
101706 - i.e. their own, when it does the extraction.
101708 -  ..
101709 - Users who do not have Executive SDS may access other Users SDS record,
101710 - through the Subject Index, for common subjects.  This means they can-
101711 - not open the SI of another User.  This forces a measure of collabora-
101712 - tion formulating Subjects, which means common thinking about "objec-
101713 - tives."
101714 -
101715 -
101716 -
101718 -  ..
1018 -
1019 -
1020 - 000005
1021 -
102101 - Line 20 - getgbl 1 257, will try moving this evaluation for Executive
102102 - SDS to the point were we post the User ID.
102103 -
102104 -     We call instead macro 854 to move the local current to global.
102106 -      ..
102107 -     Ordinarily we would only move local to current globals when a User
102108 -     ID is about to be read.  The Diary summary requires a special
102109 -     method, because it may or may not read a User ID spec.  We have to
102110 -     post the current globals before the code branches between the
102111 -     automatic and specified diary, so we will know they have been set
102112 -     one way or the other.
102113 -
102115 -  ..
102117 -  ..
102118 - Line 265 - setcnt 14 30, is set here to establish a User ID was
102119 - specified.  I thought this might be applied to improve control of the
102120 - correct User ID, but it has turned out not to be necessary for that
102121 - purpose.
102122 -
102123 -      We do at this location develop a new approach for User ID control
102124 -      of saving the local current 285 - 289 counters to counters 280 -
102125 -      284, since the latter are not used for anything at this time, see
102126 -      "Concept" above.  I have been saving them in case we need a long-
102127 -      er User ID string.  Since so far that has not been necessary, I
102128 -      can use them for temporarily saving the current locals.
102130 -       ..
102131 -      After we read the User ID spec entered by the User, and then
102132 -      transfer it to current globals, 285 - 289, we then transfer the
102133 -      actual User ID back to local current counters 285 - 289.
102134 -
102135 -
102137 -  ..
102138 - Line 390 -label dCauTo_d, changed the procedure from that discussed at
102139 - ref SDS 6 line 105.  I actually eliminated the code here that was
102140 - manipulating the User Id, because we will do it all at the point were
102141 - the User ID is posted to the selection string, in the next step.
102142 -
102143 -
102145 -  ..
102146 - Line 460 -label dC_xrwQ, 40 lines below, I am trying here to determine
102147 - the appropriate User ID based on whether this is an executive session.
102149 -  ..
102150 - Created a new macro 920 in 000004 for this purpose, to replace macro
102151 - 921 that had been applying the Session global counters 295 299 at this
102152 - location in 000005.
102154 -  ..
102155 - If it is not an executive session, then we force the Diary report to
102156 - be only for the default User.  If it is an executive session which is
102157 - set in 04702, ref OF 4 line 51, then the spec entered by the User will
102158 - work.  This means only executives can get a complete diary for another
102159 - User.
102160 -
102161 -      I think this will still enable Users to flag specific records so
102162 -      they cannot be opened by anyone except the original User.  This
102163 -      capability has to be created per ref SDS 3 line 119.
102164 -
102165 -          Initially scheduled to do this oa 940411.
102166 -
102168 -  ..
102169 - Line 1950 -entry 941, this is where I moved macro 921, and then
102170 - changed it to macro 911.  The difference is that 921 gets the globals
102171 - from 295 - 299 into local current counters, 285 - 289.
102173 -  ..
102174 - I moved this code from within the Schedule profile macro 942, because
102175 - it does not seem necessary anymore to reset the local current
102176 - counters, everytime the profile is called.  Formerly it was needed,
102177 - but since we are now protecting the local current counters whenever we
102178 - enter a specification that is read into the local counters (see
102179 - reference to line 265 within macro 000005 above), it is no longer
102180 - necessary to continue this procedure.
102181 -
102182 -
102184 -  ..
102185 - Line 2010 -entry 942, this is the profile for the Schedule.  It is
102186 - called by macro 804 which is assigned to ESC to close the menu, from
102187 - within the menu macro 80.
102188 -
102189 -     This code had been calling macro 921 to move current globals into
102190 -     current locals, and that was causing the wrong SI to open when
102191 -     called from the menu, after an Executive services call to another
102192 -     User's Schedule caused the current global to be set differently
102193 -     from the current local.
102195 -      ..
102196 -     The current concept is that the current local identification will
102197 -     be maintained during an entire session.
102199 -      ..
102200 -     Since we are protecting the local current counters, it is no
102201 -     longer necessary to reset them everytime the Schedule profile is
102202 -     called, which occurs when we close the menu. Therefore, I moved
102203 -     this macro and changed it to macro 911, to within macro 941 (see
102204 -     line 1950 above), so the local current counters are only set once
102205 -     per session.
102206 -
102208 -  ..
102209 - Line 2035 - trying to remove the code that sets local counters 295 -
102210 - 299, to the current local counters in 285 - 289.  I am unsure what
102211 - purpose this serves, and so will experiment without it.
102212 -
102214 -  ..
1023 -
1024 -
1025 - 000004
1026 -
102601 - Line 300 -entry 920 added this today to get the User ID from current
102602 - global counters into the current local counters 285 - 289.  If this is
102603 - not an Executive session, macro 856 is called to load the original
102604 - session user ID in 275 - 279 into the local current counters 285 -
102605 - 289, which is then used to load the selection command to extract
102606 - records.
102608 -  ..
102609 - This new macro 920 replaces in 000005 line 460 macro 921, and also in
102610 - 03501 and 03502 using macro 921.
102611 -
102612 -
1027 -

SUBJECTS
SDS, Executive Services, 910121
Data Security; LAN
Open SDS records

1305 -
1306 -   ..
130601 - Change the routine to apply the new method of saving and
130602 - restoring the local current User ID in 285 289 counters.
130604 -  ..
130605 - Created new error flag if there are no counters in a User ID field.
130607 -  ..
1307 -
1308 -
1309 - 000006
1310 -
131001 - Line 915 -entry 98, this opens SDS records listed within other SDS
131002 - records.
131004 -  ..
131005 - Line 985 -label othr, about 50 lines below, added the code to save
131006 - the local current User ID, then retore it after reading whatever is
131007 - entered in the record string, using the procedure developed today for
131008 - macro 000005 line 265, explained above.
131010 -  ..
131011 - It sets error flag if User ID field is blank.
131013 -  ..
131014 - Line 1085 -label er888, added error message if the User ID field is
131015 - blank.
131016 -
131017 -
131018 -
1311 -

SUBJECTS
SDS, Executive Services, 910121
Data Security; LAN
Control Field Code "look-up," - 03502
Subject Index Access, 911118

1706 -
1707 -   ..
170701 - Follow up ref SDS 5 0000.
170702 -
170703 - Change the routine to apply the new method of saving and restoring
170704 - the local current User ID in 285 289 counters.
170706 -  ..
1708 -
1709 -
1710 - 03502
1711 -
171101 - Last major work on this was on 931105. ref SDS 4 1179
171102 -
171103 - Line 15 - initially we move the local current to global session, for
171104 - the reasoning at ref SDS 3 line 256.  It seems to me today that this
171105 - is unnecessary for the reasoning at the work on macro file 000005 line
171106 - 265, set out above.  Therefore, I deleted that code.
171107 -
171109 -  ..
171110 - Line 335 -label MI_lk, changed this code to apply the procedure used
171111 - for macro file 000005 line 460, explained above, which is macro 920
171112 - in place of macro 921.
171113 -
171115 -  ..
1712 -
1713 -
1714 - 03501
1715 -
171501 - Line 155 -label bHstarT, about 55 lines below, removed code that
171502 - evaluated Executive SDS flag, for same reason 03502 line 15, above,
171503 - was changed, to apply new macro 920
171504 -
171505 -     We do call macro 854 to move the local current to global.
171506 -
171507 -
171509 -  ..
171510 - Line 240 -label bH_3502x, made same change as for 03502 line 335,
171511 - explained above, applying new macro 920.
171512 -
171513 -
171514 -
171515 -
1716 -