[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

3117.0. "Problem reading msg / attendee file sus?" by GIDDAY::BURT (Chele Burt - CSC Sydney, DTN 7355693) Mon Aug 09 1993 06:45

Hello and greetings,

Customer is running ALL-IN-1 V3.0 (British)

User attempted to reply to a meeting which had already been held.
The recipient, who was using SMU, was unable to read the message, and is
experiencing problems with the attendee file. (according to the trace log)

The trace, wittily called Q72991.TRACE, can be found at
 	MSOTIS::DKA300:[BURT.PUBLIC.ALL-IN-1]

I fail to see anything amazingly amazing about the log, but would be most 
pleased if someone else would care to peruse and comment upon it.

Many thanks,

Chele
T.RTitleUserPersonal
Name		DateLines
3117.1Could be SO/SMU relatedIOSG::CHINNICKgone walkaboutMon Aug 09 1993 11:2616
    Hi Chele,
    
    Does the customer have any patches installed??
    
    Does the customer do something to purge data out of the MEETINGS and
    ATTENDEE files which could have caused the attendee record to go
    missing?
    
    This could be related to the SO/SMU problem (Note 3066) for which there
    is a patch. That problem is to do with context not being reset upon
    error and subsequent operations are affected.
    
    I'll pass the details along to our TM expert and he might be able to
    comment.
    
    Paul.
3117.2Classic TM restrictionIOSG::PARTONJLight, I know, treads the 10M stars...Mon Aug 09 1993 17:3922
    Chele,
    
    	Paul is right: there is a patch available (ICF016) which cleans up
    after the 'error occurred writing to attendee file' - prior to this
    patch any further attempts to create, edit e.t.c events would result in
    corrupt data/mail not being sent. It is impossible to deduce from your
    trace what may have lead up to the error, but the main culprit within
    Digital, for instance, is the 'area routing' scheme (e.g. JONATHAN
    PARTON @REO actually equates to PARTONJ@A1@IOSG); there is no way that
    TM can reconcile the return address from an attendee with the original
    outgoing attendee address stored in ATTENDEE.DAT in such circumstances. 
    Other causes of this problem are using SO and editing an existing 
    attendees response - when the scheduler reads this new response there is 
    no such record in ATTENDEE.DAT again, or else using AM after SO (ICF016 
    also bars the use of such 'naughty' options which lead to this situation) 
    - this could even be the source of the problem you are seeing. It's a can 
    of worms...
    
    Regards,
    
    Jonathan$TM_whipping_boy.
3117.3customer has 3.0-1GIDDAY::BURTPlot? What plot? Where?Thu Aug 12 1993 06:5313
Hello all,

Somehow I seem to have managed to have avoided anything to with ICFs thus far 
in my time at the CSC. Does one need to submit a CLD, or ask nicely of 
"someone" @ REO? I have searched this conference, and found zip other than 
suggestions to contact certain persons at REO who are no longer to be found in 
ELF (and suggestions to "see elsewhere in the conference" for how-to's)

Many thanks,

Chele
3117.5ICF AvailabilityWAYOUT::CLARKEThu Aug 12 1993 09:3323
Chele 

You do not need to log a CLD to receive an ICF. These are the instructions 
regarding ICF's that I have received.

Due to the highly limited distribution of ICFs, Engineering need to keep
track of all customers/sites that receive and install these kits. Please
help Engineering keep accurate records by providing the following information
when requesting this patch kit.

        1) Customer/site name,
        2) Digital Support Contact (name / DTN / ENET address)
        3) Reason for requesting patch
        4) List of currently installed patches at target site
        5) *** IMPORTANT *** World:Write directory where the saveset can
                             be SPOOLED to by Engineering.
 
Ours are normaly provided by Martin Cook @REO.

Regards

Aston Clarke
UK CSC