| 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 |
Hi ,
I have a customer who has two copies of pending.dat ..one is in the
site OA$SITE_DATA_SHARE and is being used by the ALL-IN-1 users and the
other copy is in the OA$DATA_SHARE and is being used by the object 73
... This is causing a problem to teamlinks users .. I have to copy the
pending.dat from the site area to the oa$data_share and then delete the
site area copy .. my question is .. what exactly this object 73 does ?
I'm afraid of loosing something else than the info from the teamlink
users stored in the pending.dat of DATA_SHARE...
ALL-IN-1 V3.0A
Thks ... Marcia
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 4191.1 | Answer | AIMTEC::WICKS_A | Atlanta's Most (In)famous Welshman | Sat May 21 1994 02:28 | 7 |
marcia
object 73 is the File Cabinet Server.
Regards,
Andrew.D.wicks
| |||||
| 4191.2 | Carefully get all the mail... | IOSG::PYE | Graham - ALL-IN-1 Sorcerer's Apprentice | Sun May 22 1994 03:55 | 13 |
Probably the safest plan is to stop the sender and fetcher, stop the
file cab server (Object 73) and then shut down ALL-IN-1 (which should
do all the previous stops).
Now get all the mail out of the PENDING.DAT files by doing a loop
NEWDIRing to all the users and doing a CAB GET PENDING for them. Do
this for the file that ALL-IN-1 is using first, then delete it, leaving
just the one that the File Cab Server is using.
It's a bug (fixed in the next version) that the FCS has OA$DATA_SHARE
hardwired for the location of PENDING.DAT.
Graham
| |||||