[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

821.0. "ATTENDEE.DAT FILE" by SWETSC::SANDSTROM (Elisabeth Sandstr�m) Fri Jun 05 1992 16:28

THE ATTENDEE.DAT FILE

I have a customer who gets the message
%OA-E-CMATNDWRITERR, Error writing in the attendee file
when he tries to book som attendees for a meeting.

I've seen some articles about this; You can control
the ATTENDEE.DAT file so it's not sequential and you
can also control the GBLPAGEFIL. 

Does anybody has anyother explanation or solution
for this,
Many thanks
Elisabeth
 
T.RTitleUserPersonal
Name
DateLines
821.1One possible solutionAIMTEC::ZANIEWSKI_DWhy would CSC specialists need training?Fri Jun 05 1992 22:336
        Try typing the file and see if you get an error message.  If so
        then the sysgen GBLPAGFIL is too low.  You can remove the global
        buffers on the file to temporarily resolve the problem with this
        file, but the problem will just occur somewhere else.
        
        Dave Zaniewski
821.2Error with replies from remote node.SWAM2::KELLEY_SUSusan Kelley DTN:568-2672Thu Sep 24 1992 17:0816
    I'm also having problems with attendee file.  When replies are coming
    back for a meeting that I have scheduled, if the reply came from a
    remote node I get error writing to attendee file.  This was true under
    2.3 and is still true under 2.4.
    
    On 2.3 the reply causing the error would disappear from my file cabinet
    altother under 2.4, they stay in the inbox.  I have a que of unread
    messages building up now that cause the error every time I read them. 
    I also cannot delete them.  
    
    This problem is on an internal IM&T cluster.  I am just a user.  The
    DIS hotline gave me the same answer now as last year.  Basically yes it
    is a problem.  Don't know when it will be fixed.  Don't have a work
    around.
    
    Any advice?
821.3Still true in v3.0AIMTEC::ZANIEWSKI_DWhy would CSC specialists need training?Fri Sep 25 1992 14:133
        Write a memo to the product manager voicing your dis-satisfaction.
        
        Dave Zaniewski
821.4What am I missing?A1VAX::BARTHShun the frumious BandersnatchFri Sep 25 1992 16:119
    Huh?  Shouldn't this be SPR/QAR'ed?  What's the product manager going to
    do - issue a requirement on the next release that "bugs in TM be fixed"??
    
    I daresay calling it a bug and expecting it to be fixed (somehow) is
    a reasonable expectation without involving product management.
    
    Or is there more to the suggestion in .3 than meets the eye?
    
    K.
821.5Old bugs don't fade awaySAHQ::WOLFEJohn Wolfe - (404)-924-6463Fri Sep 25 1992 17:1122
	Karl

>    Huh?  Shouldn't this be SPR/QAR'ed?  What's the product manager going to
>    do - issue a requirement on the next release that "bugs in TM be fixed"??

	This is a long standing bug in attempting to schedule meetings and
using area routing in MR (Karl Barth @ZKO).  IMHO, it is the major reason
why TM is so little used internally.  I believe it has been IPR/QAR'd with
every version since at least V2.2 but somehow it never gets fixed (The fix
would involve a rewrite of parts of both TM and MAIL) 
    
>    I daresay calling it a bug and expecting it to be fixed (somehow) is
>    a reasonable expectation without involving product management.

	I would agree but it hasn't worked so far.
    
    
>    Or is there more to the suggestion in .3 than meets the eye?
    
	Desperation :-) ?

John
821.6Bulls-eye for JohnAIMTEC::ZANIEWSKI_DWhy would CSC specialists need training?Fri Sep 25 1992 23:0910
        Hi John & Karl,
        
        I've SPR's it against v2.3/2.4/3.0.  That part's been done.  It's
        in the v3.0 release notes.  It's even been reviewed in the ongoing
        v3.0 QRB process.  If it's any consolation, my system managers
        aren't real happy about having to fix my account every few days. 
        In .3, I was implying that the SPR process hasn't worked on this
        problem.
        
        Dave Zaniewski
821.7Possibly expecting too much!SWAM2::KELLEY_SUSusan Kelley DTN:568-2672Mon Sep 28 1992 06:318
    re: last few, thanks for the moral support.  I was beginning to think
    I was alone with this problem.  I have followed recommendation in .3.
    Won't hold my breath for response.  I'll see if the DIS hotline will
    create a standing log to go in and delete the meeting replies that are
    trapped in my inbox on a weekly basis.
    
    Regards,
    Sue