[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference iosg::all-in-1_v30

Title:*OLD* ALL-IN-1 (tm) Support Conference
Notice:Closed - See Note 4331.l to move to IOSG::ALL-IN-1
Moderator:IOSG::PYE
Created:Thu Jan 30 1992
Last Modified:Tue Jan 23 1996
Last Successful Update:Fri Jun 06 1997
Number of topics:4343
Total number of notes:18308

1458.0. "SWC fails to update Profile (V2.4)" by LARVAE::COHEN_D (A pint! That's nearly an armful) Mon Sep 21 1992 12:11

    ALL-IN-1 V2.4
    Patches K603/K604
    VMS V5.5
    
    We have modified both the SPD and SWC options to remove certain fields
    (especially on SWC).  The SPD option works OK, but the SWC option gives
    the following error when a user tries to update it.
    
    "Use the US sub-system to change your Profile - no change made"
    
    I've looked through this, the V24 and V23 conferences, but have found
    nothing.
    
    A user can update PROFILE.DAT if it has W:W on it, but I'd expect that;
    naturally I don't want to allow this.
    
    The SWC form has been modified to also remove the SWC2 .FORM_SET
    command - SWC now brings up just one form SWC.
    
    Any help appreciated,
    
    David.
    
T.RTitleUserPersonal
Name
DateLines
1458.1PROFIL access checks explainedIOSG::SHOVEDave Shove -- REO-D/3CTue Sep 22 1992 12:4726
    The way this works is:
    
    If you're privileged (which means you have SYSPRV turned on, or have
    write access to the profile file (via ACL or similar) or are the System
    Administrator), you can modify any field in any record.
    
    If you're not, the code will only let you modify your own record.
    Furthermore, it will only let you change certain fields in that record
    - it finds out which fields you're allowed to change by looking at the
    field NAMES in the PROFILE form(set). PROFILE (note the "E" on the end)
    is not used for anything else except this check.
    
    This check is done in the RMS action routine, and so applies whether
    you try to change the profile record via an entry form (PROFIL, SWC
    etc) or via functions such as WRITE CHANGE PROFIL or DATA_FILE.
    
    As PROFILE is a formset, if you change one of the forms in it (and so
    move it to SITEMEMRES) you'll need to move the others there too (unless
    the v3.0 SCM does it for you - I can't remember!)
    
    Becuase the field check relies on field NAMES, you need to be careful
    you don't change the field names on the profilE formset - for example,
    the Form Editor (FMS) has a habit of renaming fields to F$0001 etc if
    you change them!
    
    Dave.