Conference iosg::all-in-1_v30

    
    Hello,
    
    I had a better look at previous notes.
    
    Found Richard response to a similar question.
    
================================================================================
Note 1780.3             LIST PROCESSING UNDER ALL-IN-1 V3                 3 of 3
IOSG::NEWLAND "Richard Newland, IOSG, REO2-G/L2"     21 lines  28-JAN-1993 14:01
                              -< File ownership >-
--------------------------------------------------------------------------------
>An ALL-IN-1 shared drawer has an owner.  The contents of the documents in 
>a shared drawer and the file-cab directories are RMS files.  In order that
>document access is controlled by RMS ALL-IN-1 requires that all the files
>are owned by the drawer owner. 
>
>An application which creates a file in another user's shared drawer will 
>usually fail because the user will not have the required privileges to 
>access the directories and/or create files owned by another user.
>
>ALL-IN-1 has API functions which allow one user to create files which are 
>owned by and placed in another user's drawer.  Options such as Create, 
>Edit and Copy Document have been updated to use these functions when 
>required.  Normally a temporary file will be created in the user's 
>directory and then moved or copied to the destination drawer.
>
>Other options such as WPS-PLUS list processing and Document Transfer have
>not been updated to handle creating documents in another user's drawer.  We
>already have SPRs for these problems. 
    
    This sounds like code level chages are needed. Correct ?

    Can someone post the answer(s) to these SPR's ?
    
    Regards,
    
    Jan

Code level changes are not required.  The necessary changes to fix this
problem in a PFR have been made.  It required some moderately complex
changes to DCL command procedures and ALL-IN-1 scripts.


Richard

    Hello Richard,
    
    Thanks.
    
    Last question. Customer is only interested in the List Processing function.
    He says that in SFCP it did work and now causes them quit some trouble. 
    
    Are those fixes downward compatible ?
    
    Regards,
    
    Jan

Richard, 

- are the fixes you mention in re .2 available today? 

A Danish customer, now with ALL-IN-1 v3.0A, want their users to be able to
create documents in shared drawers which they have access to, but are not
owners of. 
    
They cannot do this with list processing output documents and with their
own applications which in a similar way call DOCCREATE.SCP with #P1=NOEDIT. 

In note 3606.1 Dick Carlin told that "the fix didn't make it into V3.0-1"
I then told the customer that I expected the fix to be in the MUPA, but it 
seems like the fix also didn't make it into V3.0A?

Elin 

I can se in MUPA release notes that DOCCREATE.SCP has been changed, but not 
how.  I'll test list processing output on my own system, as the customer
might have a customized version. 

Elin

I tested it on my own v3.0A system.

It is NOT possible to select a shared folder which you are not the owner of 
as output destination for listprocessing. 

When I pressed return after having filled in form DOCDSCNT, I got message 
OA$_WP_DRAWER_NOT_OWNED saying that I must select a drawer which I am the 
owner of.

Below are a few lines from a trace.

Elin

![SYMBOL] Symbol: OA$CURDWR_SHARED, Value: J
![SYMBOL] Symbol: OA$Y, Value: J
![SYMBOL] Symbol: OA$CURDWR_REMOTE, Value: N
![SYMBOL] Symbol: OA$Y, Value: J
![SYMBOL] Symbol: #P1, Value: NOEDIT
![SYMBOL] Symbol: "NOEDIT", Value: NOEDIT
![SCRIPT] IF Operation starting
![SCRIPT] .IF condition ((OA$CURDWR_OWNER NES PROFIL.VMSUSR[OA$USER] AND OA$CURD
!               WR_SHARED EQS OA$Y) OR OA$CURDWR_REMOTE = OA$Y) AND #P1 EQS "NOE
!               DIT"  is TRUE
![SCRIPT] THEN Operation starting
![SCRIPT] DOCCREATE Line 19: .GOTO NOT_OWNED
![SCRIPT] DOCCREATE Line 20: GET OA$DISPLAY=OA$_WP_DRAWER_NOT_OWNED

Implementing the creation of the output document in a non-owned drawer
required changes to WPS-PLUS List Processing scripts and DCL command
procedures.  These changes are in ALL-IN-1 V3.1, but have not been shipped
in either V3.0-1 or V3.0A. 


Richard