Conference iosg::all-in-1_v30

    
    re .0
    
    If they are running V3.0-1 (K701) then it is an introduced bug
    in K701 that is know about, any FCS interaction with the inbox
    will be suspect. The FCS cannot find the inbox, that is what
    the card id not found error is trying to say.
    
    --Bob
    

    Hi Bob,
    
    Thanks for the confirmation I have had to CLD this at priority 2
    because the customer insisted and wanted a quick solution.
    
    It has also been found that other functions also cause this problem and
    these are RFD and MCD, if the documents are to be filed or moved to
    another drawer.
                    
    Sorry Chaps and Chappesses :-), honest I was forced into CLDing it by
    this customer they carry alot of weight (about 500 kilos 8*) ).
    
    Regards,
    
    Sunil

    Hi All,
    
    		**** Moderators please delete if you feel this ****
    		**** reply should not be placed in this here.  ****
    
    Just to wrap up this note a solution has been proposed and a patch is
    available on an Individual Customer bases.  Please do not discuss this
    with customers, unless they have an absolute need to have the problems
    fixed.
    
    Announcing Individual Customer Fix "ICF #009" for ALL-IN-1 V3.0
    
    The problems that have been fixed are:
    
    In V3.0, if an attempt is made to refile an UNREAD mail             
    message to another drawer, the following error message is
    returned :
    
         "Cannot refile an UNREAD or NOTED document between drawers"
          However, with V3.0-1 this message is replaced by the error:
    
          "File Cabinet object does not exist"
    
    The fix for this problem also solves various other problems with accessing
    INBOX documents after installation 0f V3.0-1: e.g.
    
    a) If a document is in the INBOX you get the following message when
       Answering the message.  From the Inbox Index or Read just enter A then 
       call a script file containing the following code.
    
             get #cdwr=oa$curdwr
             get #attdoc=oa$curdoc
             filecab attach (drawer=#cdwr, document=#attdoc,
    			     to_drawer=#cdw, to_document=oa$curmes)
    
               The error message you get is:
                    %OAFC-I-CARDIDNF, File Cabinet object does not exist
    
    b) CFS.3609
    
       SOMETIMES, a received ALL-IN-1 mail doesn't create the INBOX folder when
       the INBOX folder does not exist. The unread mailcount goes up, but you 
       can only find this mail using Index with Status UNREAD.
    
    c) After selecting a Remote Drawer (DSO option) then RN will
       always indicate there are no more messages waiting to be read.
    
    2) CLD MUH2433, THR-17139, THR-17410
    
       TeamLinks does not update UNREAD count.
       If you create an ALL-IN-1 user with the form LAST.FIRST (i.e.
       containing a dot ".") or the VMS and IOS Usernames differ then
       opening/closing that user's main drawer/inbox from TeamLinks does
       not fetch new mail from pending and does not correctly update the new 
       mail count.
    
    The kit A1_FIX009030.A;3 (1242 blocks) is available on an individual
    request basis from IOSG Engineering.
    
    I'd like to thanks all concerned for their timely solution and
    commitment, just goes to prove how committed the IOSG is to quality.
    
    Regards,
    
    Sunil

    The previous note, which I've hidden, contains details of a fix for
    this problem.
    
    I don't think this notesfile should replace the official process for
    reporting problems, getting fixes done and distributing patches. If
    there are problems with any of those processes, we should get them
    looked at!
    
    Suffice to say that there is now an ICF available for this problem
    which can be obtained through the usual channels.
    
    Graham
    
    PS Sunil, thanks for the compliments about our quality commitment!

    I've taken advice from the people who produced ICF #009 and they're
    happy for this one to be widely advertised.
    
    Obtain the patch through the usual channels (Don't mail me if you don't
    know what they are!!!)
    
    Graham

    Hi All,
    
    Just to add that the customer has fully tested the ICF #009 and it has
    fixed the problem and they have not experienced any new problems.
    
    Just thought I would add this for people who may wonder did it cause a
    problem.  Anyway it's only a not so random sample of 1 :-).
    
    Regards,
    
    Sunil