[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

2057.0. "R/W document in R/O drawer" by EWBV51::NAGURA (Buon Capo d'Anno!) Mon Jan 11 1993 07:54

	I have a question about an Advanced Shared Drawer.

	When you have a READ access on someone else's Shared Drawer and
      WRITE access on a document in that drawer, you can edit it but after
      hitting GOLD/F you'll get the error message indicating replacement
      error because of insufficient priviledges.

	I think the reason is the protection code of the Drawer directory,
      then I don't know how I should setup a single editable document in
      a Read-Only drawer. Do I have to ask the customer to change the access
      level of drawer for only one single document ?

						Yukiji
T.RTitleUserPersonal
Name
DateLines
2057.1IOSG::CARLINDick Carlin IOSG, Reading, EnglandMon Jan 11 1993 12:0019
    Can you give some more details, please? You should be able to do what
    you want (edit a document to which you have EDIT access in a drawer to
    which you have READ access only).
    
    I assume this is V3.0 :-)
    WPS-PLUS?
    
    Do an ID (index drawers) and R(ead) the drawer in question.
    Does it warn you that you do not have R or E access to some high level
    directory in the drawer path.
    
    If possible could you do a dir/sec right down the directory chain to
    the document in question?
    
    The answer to the last question is No, you shouldn't have to modify the
    drawer access to do what you want on this one document.
    
    Dick
    
2057.2some more detailsEWBV51::NAGURAYukiji Nagura /ALL-IN-1 CSC/Tokyo/JapanTue Jan 12 1993 00:4946
	Dick, thank you for your response.

>    I assume this is V3.0 :-)
>    WPS-PLUS?
    
	Yes, this is V3.0/Japanese and the editor is EVEJ(Japanese Version
      of EVE).

>    Do an ID (index drawers) and R(ead) the drawer in question.
>    Does it warn you that you do not have R or E access to some high level
>    directory in the drawer path.
    
	No, it functioned properly, I mean no warning messages. The output 
      is in Japanese, so I don't put it here.

>    If possible could you do a dir/sec right down the directory chain to
>    the document in question?
    
	$ dir/sec disk$a1liaison:[nagura.allin1]z*

	Directory DISK$A1LIAISON:[NAGURA.ALLIN1]
    
        ZUMJMSH21.DIR;1      [LIAISON,NAGURA]      (RWED,RWED,,E)
                  (DEFAULT_PROTECTION,SYSTEM:RWED,OWNER:RWED,GROUP:,WORLD:E)

	$ dir/sec disk$a1liaison:[nagura.allin1.zumjmsh21]doc1.dir

	Directory DISK$A1LIAISON:[NAGURA.ALLIN1.ZUMJMSH21]
    
        DOC1.DIR;1           [LIAISON,NAGURA]      (RWED,RWED,,E)
                  (IDENTIFIER=[LIAISON,NAGURA],OPTIONS=DEFAULT,ACCESS=READ+
                  WRITE+DELETE+CONTROL)
                  (IDENTIFIER=[LIAISON,NAGURA],ACCESS=READ+WRITE+DELETE+CONTROL)
                  (IDENTIFIER=[LIAISON,OTSUKA],ACCESS=READ)

	$ dir/sec disk$a1liaison:[nagura.allin1.zumjmsh21.doc1]

	Directory DISK$A1LIAISON:[NAGURA.ALLIN1.ZUMJMSH21.DOC1]
    
        ZUMJMV1NE.TXT;1      [LIAISON,NAGURA]      (RWED,RWED,RE,)
                  (IDENTIFIER=[LIAISON,NAGURA],ACCESS=READ+WRITE+DELETE+CONTROL)
                  (IDENTIFIER=[LIAISON,OTSUKA],ACCESS=READ)


	Regards, Yukiji
2057.3Check WPEDIT.SCPIOSG::CARLINDick Carlin IOSG, Reading, EnglandTue Jan 12 1993 14:4619
    Yukiji
    
    Assuming that it is Otsuka who is having the problem then the document
    cannot be edited by them because it only allows read. The default ACL
    on doc1 shows that this is a result of the default setting for new
    documents in that drawer. If you want Otsuka to be able to edit just
    this document then you should use FC MDO to modify its access.
    Alternatively you can use DRM ASO SDA to modify it for all new
    documents (and, optionally, existing documents) in the drawer.
    
    However I'm still puzzled. The edit should never have got that far. If
    Otsuka is local they should have got "You are not allowed to edit ..."
    or, if remote, "Document could not be reserved / Insufficient
    priviledge ..." and the edit should never have started. I can only
    assume that the EVEJ environment is not conforming to the reservation
    conventions (WP_SYS_EDIT.SCP/WP_SYS_CLOSE.SCP). Can you confirm this
    either way?
    
    Regards,  Dick
2057.4Oops !EWBV51::NAGURAYukiji Nagura /ALL-IN-1 CSC/Tokyo/JapanWed Jan 13 1993 00:1026
    
>    Assuming that it is Otsuka who is having the problem then the document
>    cannot be edited by them because it only allows read. The default ACL
>    on doc1 shows that this is a result of the default setting for new
>    documents in that drawer. If you want Otsuka to be able to edit just
>    this document then you should use FC MDO to modify its access.

	Oooooooops !!!

	Sorry for puzzling you, Dick. Obviously I had a typo. When I read 
     your reply first, I can't follow you, but after checking my .2, Gee !

>	$ dir/sec disk$a1liaison:[nagura.allin1.zumjmsh21.doc1]

>	Directory DISK$A1LIAISON:[NAGURA.ALLIN1.ZUMJMSH21.DOC1]
    
>        ZUMJMV1NE.TXT;1      [LIAISON,NAGURA]      (RWED,RWED,RE,)
>                  (IDENTIFIER=[LIAISON,NAGURA],ACCESS=READ+WRITE+DELETE+CONTROL)
>                  (IDENTIFIER=[LIAISON,OTSUKA],ACCESS=READ)
                                                       READ+WRITE
						       ^^^^^^^^^^
        Of cource, it has a write access. I'm not using DECwindows environment,
      I made this output by cut and paste, and also made a blunder.

	Regards, Yukiji

2057.5Patience rewardedIOSG::CARLINDick Carlin IOSG, Reading, EnglandFri Jan 15 1993 18:1822
>  <<< Note 2057.4 by EWBV51::NAGURA
>                                  -< Oops ! >-
    
    Don't worry, I've been guilty of asking irrelevant questions.
    
    Sorry about the delay, but here is the answer:
    
    I assume you are running V3.0 and not V3.0-1. If not then I'm puzzled
    again.
    
    V3.0 unfortunately required that users have CREATE access to the drawer
    to allow them to edit using "new-version" editors (eg EVE, EDT).
    
    So your alternatives are
    
    1. Upgrade to V3.0-1 (which cures the bug) or
    
    2. Give OTSUKA CREATE access to the drawer.
    
    So you were right all along.
    
    Regards, Dick