[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

522.0. "Error Deleting group.lgp When Deleting User Accounnt" by OASS::ANDRES_B () Fri Apr 17 1992 22:52

    Customer upgraded the ALL-IN-1 V2.4 to have the WPS-PLUS V4.0 Option.
    One of the features of the WPS-PLUS V4.0 is the group and corporate
    dictionaries.  Pointers to the files oa$system_dictionaries:group.lgp
    and oa$system_dictionaries:corporate.lgp are created in the folder
    SYSTEM WIDE DICTIONARIES when users use spell checker for the first
    time.  This all works fine.  However, when the system manager goes
    to delete one of the users he is getting an error that he can't delete
    the corporate or group dictionary.  I checked on two different systems
    and on one system the corporate.lgp and group.lgp files were deleteable
    and on another system they were not.
    
    He is working around this at the present time by using the docdb form
    to change the file to deleteable before deleting the user account.
    Does anyone know of another way around this so it would not have to
    be done for each user.  What is determining whether that file is being
    set as deleteable or not deleteable.
    
    
    Beth Andres
T.RTitleUserPersonal
Name
DateLines
522.1RTFSA?AIMTEC::WICKS_AMore Ship dates than actual ShipsFri Apr 17 1992 23:0928
    Beth,
    
    This has already been reported to Engineering as a QAR (ALF467)
    against ALL-IN-1 DIAMOND in that any and all upgrades from the option
    kit will display the error:
    
    %PURGE-W-FILNOTPUR, error deleting
    A1$DISK:[ALLIN1.SYSTEM_DICTIONARIES]GROUP.LGP
    -RMS-E-PRV, insufficient privilege or file protection violation               
    %PURGE-W-FILNOTPUR, error deleting
    A1$DISK:[ALLIN1.SYSTEM_DICTIONARIES]CORPORATE.LGP
    -RMS-E-PRV, insufficient privilege or file protection violation               
    
    immediately after the "moving files to target directories" message
    
    proof if it were needed that the files put there by the option kit
    have the wrong protection. The ones in DIAMOND are correct
    
    Now if you'd read my STARS article (:==:)
    
    The workaround (it's not pretty) is either to set the protection correctly
    by hand! or do one of those CAB CHANGE_ATTRIBUTE thingies on the DOCDB
    field DELETEABLE or delete the files by hand or ...
    
    Regards,
    
    Andrew.D.Wicks                                                 
    
522.2Wrong Problem Andy!IOSG::PYEGraham - ALL-IN-1 Sorcerer's ApprenticeTue Apr 21 1992 18:5611
    Although the problem that Andy describes in .1 is a problem, it isn't
    the one that was asked about in .0!
    
    I don't know if delete user does something special to avoid deleting
    the system wide dictionaries, but they seem to be created with DELETE=Y
    in V3.0 too...
    
    Perhaps a more knowledgeable Delete user or WPS-PLUS expert will
    comment tomorrow?
    
    Graham
522.3But the right STARS articleAIMTEC::WICKS_AMore Ship dates than actual ShipsTue Apr 21 1992 19:3631
    GAP,
    
    Actually the documents pointing to the group and corporate lgp files are 
    created in v3.0 with DELETABLE set to N not Y as you say. Obviously the N 
    key on your keyboard types the letter Y the same as when you type the 
    letters 'rew' the letter 'y' appears - must be those long easter holidays 
    getting to you?
    
    The STARS article I have refers to both the upgrading to DIAMOND problem
    (the protection on the VMS files) and the Delete User problem so
    whilst there were be two 'opportunities' stored in the vaults of TIME
    there is but one STARS article so I did know a little bit about what
    I was talking about.
    
    If you take a look at LNGSPLINI.SCP in OA$DO: you'll see it's well
    commented and uses the CABINET RESET_DELETE function to mark the
    documents as non-deletable and it is quite a deliberate change made
    and commented as 10-Jun-1991 - you'll see I do do some research despite
    not being knowledgable (:==:)
    
    I'm sure I could bore you with what Delete User does with documents that are
    marked deletable and what it does with files in a user or system
    directory but I know you can read DCL. 
    
    Since Beth sits a few yards away from me and even though she uses the wrong 
    CSC ALL-IN-1 Production node to note from we'll let her work it out.
    
    Regards,
    
    Andrew.D.Wicks
    
522.4Doesn't work for me....IOSG::PYEGraham - ALL-IN-1 Sorcerer's ApprenticeWed Apr 22 1992 11:1228
    Well I must have had mine created on an older base level, since mine
    are definitely set to "Y"
    
------------------------------------- TOP --------------------------------------
                           Showing ALL-IN-1 message

Subject:
Title:               CORPORATE/EXCEPTION WORD DICTI
Sender:
Senders Full Name:
Senders Tel No:

Current Drawer:      MAIL
Drawer Owner:        PYE
Current Folder:      SYSTEM WIDE DICTIONARIES     Status:
Type of Document:                                 Document Number:   047900
Date Created:        14-May-1991 09:13am          Modifiable:        Y
Last Modified:       19-Nov-1991 01:48pm          Deletable:         Y
Date Sent:                                        Forwardable:
Date Posted:                                      Read Receipt:
Deferred Date:                                    Delivery Receipt:
Priority:                                         No of Attachments:  0
Handling:            DICTIONARY                   Data Type:        
DICTIONARY
MR id:
VMS Filename:        OA$SYSTEM_DICTIONARIES:CORPORATE.LGP

Addressees:
522.5May before June I agreeAIMTEC::WICKS_AMore Ship dates than actual ShipsThu Apr 23 1992 03:0611
    GAP,
    
    Yes you do - yours were created on May 14 and the code change was made
    on Jun 10.
    
    Anyone else use use before BL70? Where are the experts when you need
    them ....
    
    regards,
    
    Andrew.D.Wicks