| T.R | Title | User | Personal Name
 | Date | Lines | 
|---|
| 2211.1 | Sounds like a broken WPSDEF.WPL in Manager's acct | IOSG::SHOVE | Dave Shove -- REO2-G/M6 | Thu Feb 04 1993 09:22 | 13 | 
|  |     This sounds like a problem with WPS-PLUS in the Manager's account.
    
    Can the manager read his/her own WPS-PLUS documents?
    
    If you set the Manager's default editor to WPS-PLUS (using US SWC), can
    he/she create documents?
    
    If the answer to either or both of these is no, give the Manager a new
    WPSDEF.WPL file - copy it from sub-directory [.USER] under OA$LIB: to
    sub-directory [.MGR] under the Manager's VMS login directory
    ([ALLIN1.MGR] in a default system).
    
    Dave.
 | 
| 2211.2 | Not the manager account problem | CROCKE::YUEN | Banquo Yuen, Darwin Australia | Wed Feb 10 1993 07:34 | 5 | 
|  |     I is not likely to be the problem of the manager account because
    I call <NEWDIR to other user and read other user's document
    without problem
    
    Banquo
 | 
| 2211.3 | A protection problem? | IOSG::PYE | Graham - ALL-IN-1 Sorcerer's Apprentice | Thu Feb 11 1993 08:52 | 11 | 
|  |     Well if the manager can read and create *WPS-PLUS* documents in their
    own account, and if <NEWDIR'd to another user *AND* that user can
    create and read *WPS-PLUS* documents in their own account:
    
    THEN there must be something in that user's account that the manager
    can't access, presumably because the protections are wrong. Try
    comparing the protections of the files in the user that works with the
    one that doesn't. Check all the .DATs, .WPL and .DIRs first, then look
    in the lower directories.
    
    Graham
 | 
| 2211.4 | More on .-1 | IOSG::SHOVE | Dave Shove -- REO2-G/M6 | Thu Feb 11 1993 11:27 | 11 | 
|  |     The Manager will presumably have been using SYSPRV, and therefore
    System protections, to look at the other users' files (note that NEWDIR
    does _not_ raise the image's privs: the user must have them already.)
    
    So, check for any files on which the user has changed the S: protection
    (tell your users that this is not usually a good idea, 'cos BACKUP
    typically runs with SYSPRV and so such files won't get backed up!)
    Removing the (default) S:D protection will also stop the Janitor
    working.
    
    D.
 |