Conference iosg::all-in-1_v30

    1/2. Any time somebody edits the document. The document should
    automatically get unreserved when the edit session is complete.
    
    If you are finding that the system reservation remains in force, then
    it usually means that the edit session terminated abnormally (really
    abnormally, not just GOLD-K). If you go into edit again it should pick
    up where it left off (for example if it is a remote edit then it will
    go back to the local copy rather than the original).
    
    If you do a GOLD-V with the document current you should see the date
    and time of the reservation.
    
    Dick

Ok,

but when is a reservation a system reservation; i.e. what user actions result in
a system reservation ?

Thanks,

Martin

p.s. The users at the customer's site aren't aware that they did something
     that could cause such a behaviour.

    User reservation:
    
    This is what you get when you do an RSV/RSC on a document. You can then
    edit it any number of times, knowing that noone else can get in and
    edit it, until you make it available again by doing URV/RPC. If you
    just want to edit a document once then there is no need to bother since
    system reservation (see below) will take care of things for you. User
    reservation puts a "long term hold" on the document.
    
    System reservation:
    
    This is what ALL-IN-1 does on your behalf when you just edit a
    document. It reserves it for you and, at the end of the edit session,
    automatically unreserves it for you. This means that other users who
    try and edit it will get the message saying who has it reserved.
    
    
    Re your ps. Are you saying that nobody edited the document? If so then
    I agree that is strange.
    
    Dick

Hi Dick,

Thanks for your explanation !

>    Re your ps. Are you saying that nobody edited the document? If so then
>    I agree that is strange.

That's what the endusers told the system manager and the system manager told
me ..... Endusers don't always know what they did exactly.

I can't imagine that ALL-IN-1 spontaneously system reserves documents !

I'll try to get more information.

Martin

Hi Dick,

A possible cause has been detected at one customer's site.

Some users which have (write) access to shared drawers are using ALL-IN-1 via PC
and terminal emulation. Sometimes it happens that these users are locked in 
their sessions, so only STOP/ID is possible. That's what I would call an 
abnormal end of an edit session.

Still ONE customer to go !

Martin

Hello Dick,

Last reply on this issue !

ALL-IN-1 manager at customer's site told me that he or the VMS System manager
sometimes had to kill a proces via stop/id......

No more customers to go.

Thanks for your help.

Martin

    It's unfortunate that we didn't document the automatic recovery
    procedure in .3 very well.
    
    When you find the document reserved, ALL-IN-1 is trying to say "don't
    worry, I've kept it reserved for you, so your updates won't be lost and
    no other user has been allowed to touch it. Just go in and edit it
    again". But unfortunately it looks more like a bug to most people.
    
    Dick

Hello and greetings,

Customer is using ALL-IN-1 IOS 3.0A

An account with fullpriv: R W E C to an advanced shared drawer as an 
individual and also as part of a group, couldn't create or edit a doc in 
this shared drawer, error msg:
	...document not found
	...press EXIT to file document to last checkpoint...

Happening to /NOCUSTOM mode as well

Problem occurs on advanced and regular shared drawers, on both edit and 
create, for a number of different users.

On creation, despite the error messages, a file cabinet entry IS added with a 
system reserved flag - a "pointer document" is placed in the recovered 
documents folder. 
Once the system reserved flag is removed, (the 'normal' reserved flag still 
being present) the privileged user CAN edit the document. It does not appear 
to be afflicted with the system reservation again.

I had the customer check his profile entry, his dir spec is set to 
USER$DISK:[LOBBE.A1] - which does not have a search list associated with it.
Customer does not appear to have the partition seed log on any of his systems.

So I have 2 questions
1. What is likely to be causing all these system reservations?
   There have been no abnormal session terminations, violent system shutdowns 
   etc
2. Can user type users (non-priv'd) unreserve system reservations?

Thanks & regards,

Chele

Just on the off-chance that someone is feeling charitable...

In the customer trace the following can be found:

![SYMBOL] Symbol: PROFIL.VMSUSR[OA$USER], Value: LOBBE
![SCRIPT] .IF condition (OA$CURDWR_REMOTE EQS OA$N AND OA$CURDWR_OWNER EQS PROFI
!               L.VMSUSR[OA$USER]) is FALSE
![SCRIPT] WP_SYS_EDIT Line 51: .THEN
![SCRIPT] WP_SYS_EDIT Line 53: .ELSE
![SCRIPT] WP_SYS_EDIT Line 54: GET #EXPORT_LOCATION = FC$_LANG_RL_DOCUMENT
![FUNC]   Function: GET, Cmd line: #EXPORT_LOCATION = FC$_LANG_RL_DOCUMENT
![A1LOG]  Entry: %OA-I-LOGFUN, Function: GET             #EXPORT_LOCATION = FC$_
!               LANG_RL_DOCUMENT
![SYMBOL] Symbol: #EXPORT_LOCATION = FC$_LANG_RL_DOCUMENT, Value: Document
.
.
.
.![MESS]   Message: The document could not be replaced (Document not edited)


In the CSC trace the trace reads as follows:
![SYMBOL] Symbol: PROFIL.VMSUSR[OA$USER], Value: BURT
![SCRIPT] .IF condition (OA$CURDWR_REMOTE EQS OA$N AND OA$CURDWR_OWNER EQS PROFI
!               L.VMSUSR[OA$USER]) is TRUE
![SCRIPT] WP_SYS_EDIT Line 51: .THEN
![SCRIPT] WP_SYS_EDIT Line 52: GET #EXPORT_LOCATION = FC$_LANG_RL_NONE
![FUNC]   Function: GET, Cmd line: #EXPORT_LOCATION = FC$_LANG_RL_NONE
![A1LOG]  Entry: %OA-I-LOGFUN, Function: GET             #EXPORT_LOCATION = FC$_
!               LANG_RL_NONE
![SYMBOL] Symbol: #EXPORT_LOCATION = FC$_LANG_RL_NONE, Value: No copy

The document creation & subsequent edit continues without any problem _here_.


Not being very good at reading entrails, I would really appreciate someone 
enlightening me as to why the customer script appears to be checking if a 
condition is false, whereas our version checks if the same condition is true, 
and how/why the #EXPORT_LOCATION value for the customer is set to document, 
whereas as ours is set to no copy. This is where it starts to go awry for the 
customer.

Thanks & regards,

Chele

    Chele
    
    Sorry you didn't get a reply before now.
    
    Regarding the traces in .9, the customer was creating a document
    in someone else's drawer. The CSC creation was happening in your own
    drawer. Therefore the processing differed. What you saw (.IF ...
    is FALSE) was the RESULT of evaluating the condition - I think you
    assumed that that was the actual condition being evaluated. So, nothing
    out of the ordinary up to now.
    
    Regarding the problem in .8, I didn't follow exactly what you were
    saying. What should happen in their case is that a file cabinet entry
    is placed in the target drawer (status reserved). The document creation
    (the edit stage) actually occurs in the "RECOVERED DOCUMENTS" folder in
    their main drawer and, as a final step, the text file is copied to its
    final destination and simultaneously the target file cabinet entry is
    unreserved.
    
    The errors they were getting were WPS-PLUS errors, but I'm not sure
    what could have caused them. Were they doing extravagant things with
    GOLD-O and Delete?
    
    Also I'm not sure what you mean by 'normal' and 'system' reserved
    flags.
    
    Finally, can you point me to a complete trace for a failing case?
    
    Dick

Hello Dick,

Thankyou for checking the entrails, I find it especially difficult to read
them when they're still steaming.

I've just spoken to the customer again for the revised edition of the story.

Drawer access stuff I'll put on the next page.

Once upon a time a customer had an advanced shared drawer called PUBSMAN. The
customer had all sorts of access to this drawer, but when he attempted to
create a document in it, he received a message stating "document not found".
His current document block had, however, been changed to display this
non-found document, which had a status of "reserved".

When he looked in his MAIN drawer in the RECOVERED DOCUMENTS folder, his
non-found document title was there. There was no RESERVED status, on a READ
the document was empty (fair enough).

The customer leapt back in to his shared drawer, modified the rserved status
"Do you wish to cancel the system reservation" to which he replied "Y", and
was able to edit the document just like a bought one.

When he had a look back in his MAIN drawer again, the now-found document was
sort of there - but when he attempted to read it, he received the message "Not
a document" etc etc and a top & bottom control block were displayed.

I am not aware of the customer doing "extravagant things with GOLD-O and 
Delete" - and would they lie to me?


Thanks & regards,

Chele



Date: 30-May-1994         File Cabinet Drawer Full Report               Page: 1
                          ===============================               


Drawer              AWARDS C

System              AIRMEL::

Owner               PUBSMAN

Drawer name         AWARDS C

Description         PUBLICATIONS - C Awards

Directory           AWARDS_C:[A1]

You have CONTROL access to the drawer

Drawer is shared with other users

Drawer is located on this system

Drawer type is ADVANCED SHARED


                    List of users who may access the drawer
                    =======================================

                                 Shared
User or Group                   VMS Acct    Read     Create    Delete   Control

PUBSMAN                                      Y         Y         Y         Y
LOBBE                                        Y         Y         Y         Y
*PUBS_MANAGER                                Y         Y         Y         Y
*PROGRAMMERS                                 Y         Y         Y         Y



                    Default access for new documents
                    ================================

                                 Shared                        Delete/
User or Group                   VMS Acct    Read      Edit     Refile   Control

PUBSMAN                                      Y         Y         Y         Y
LOBBE                                        Y         Y         Y         Y
*PUBS_MANAGER                                Y         Y         Y         Y
*PROGRAMMERS                                 Y         Y         Y         Y