Conference iosg::all-in-1_v30

    By any chance are the CM$FORM$LIBS records for SITEOAFORM screwed up?
    Call up the entry form and check that you have two records -- one with
    key of the actual form library name, the other prefixed with LOCK_.  CM
    attempts to lock the latter and write details about the user who is
    locking the library in the former, which should have a lock flag field
    set to 0 (if the library is available), or 1 (if it's locked by a
    user).
    
    T

    Hi Tony,
    
    Thanks for your suggestion but it's unfortunately not that simple in
    the light of further information I have obtained.  I did what you
    suggested and the lock flag bit was get to 0 and the last user access
    field was blank, it's site that has just upgraded.
    
    What we found was that for this form only we are unable to move it to
    the live area.  I asked the customer to do the following:
    
    1. write the screen definition of the form to a temp. file
    2. create a new form and copy in the screen definition and change
       the form name in the form attributes option
    3. make the element live and test
    
    when we did this we had no problem making the element live and using
    the form.  So this points to a problem with the form it's self or it's
    definition/history in CM.  We are unable to delete the form from the
    live area as we get the same error message as in the base note, the
    SITEOAFORM locked by another user (RMS error message).
    
    What we could try to do is do the deletion manually by firstly
    following the steps for the deletion procedure, than remove the form
    from the SITEOAFORM.FLB from OpenVMS by doing a $fms/library/delete
    etc.  Before I do any of this I would be grateful for your opinion and
    input.  I don't feel safe doing this because I have not found the cause
    of the problem.
    
    Thanks for your help and advise,
    
    Sunil

    Hi,
    
    The element lock status for this form is "RECOVER ERROR" and we are
    unable to do anything with this element.  We cannot delete it or move
    the form form development to live.
    
    What does "RECOVER ERROR" mean ?  Chris Coleman had told me to
    recompile the ALL-IN-1 TXL's and try again this made no difference at
    all. From what he was saying he had a similar problem to the one I
    have.
    
    The customer is not too happy about altering the script file to remove
    the element details from ALL-IN-1 and than delete the form from OpenVMS
    using fms/lib/delete.  The customer wants to know why this happened and
    I am unable to give an explaination.  Could someone help me out on this
    please.
    
    We have a workaround this problem I have asked the customer to change
    the named data/scripts that call this form to call the copied form.
    
    Regards,
    
    Sunil

    Sorry I forgot to add that we had tried changing the lock status as per
    Tony's book.  When we tried to delete it the element went into "RECOVER
    ERROR" status.
    
    I just thought that I would add this just in case someone suggests this
    as a solution.
    
    Sunil

    
    Using form CM$SITELOG, check the live location field. I seem to
    remember that if it is OA$SITE_LIB_BRITISH:SITEOAFORM (ie. without the
    .FLB) CM has problems copying the form to live.
    
    Bruce
    

    Hi Bruce,
    
    Thanks for your help this was an obsecure problem and your solution
    solved the problem.
    
    The initial error message was misleading or as the saying goes "a bad
    workman always blames his tools :-)".  I leave the choice up to you !!!
    
    %FMS-F-OPENOUT, error opening
    SYS$PROD:[ALLIN1V2.SITE.LIB_BRITISH]SITEOAFORM.FLB; as output
    -RMS-E-FLK, file currently locked by another user
    
    Regards,
    
    Sunil

    To recover from an error:
    
    -- Check to see if there are any temp. files hanging around OA$SITE_DEV
    
    -- Decide whether or not you want to use the temp files (by putting
       them back into a forms library, or moving them to the right location)
    
    -- Adjust CM$SITELOG.LOCK_FLAG by writing a value of 0 into it. 
    
    -- Restart an edit of the element.  Everything should go OK now.
    
    The obscure nature of the invalid live location problem should be SPR'd
    so that the error message becomes a little smarter...
    
    T

>    Using form CM$SITELOG, check the live location field. I seem to
>    remember that if it is OA$SITE_LIB_BRITISH:SITEOAFORM (ie. without the
>    .FLB) CM has problems copying the form to live.

One of our customers recently encountered this problem. 

My question is why/how was the form library written without the .FLB

In other words what should they do to prevent this from happening in the future
with customized elements.

Thanks,

Cb.