| T.R | Title | User | Personal Name
 | Date | Lines | 
|---|
| 473.1 |  | PHENIX::CONNELL | Down on Toidy-toid & Toid Avenue | Fri Feb 26 1988 14:56 | 9 | 
|  | >   I'm finding references
>   to notefiles right and left and these files don't appear on any
>   list that I have. 
	Could you cite some examples, please?  I find nearly five full pages
of notesfiles titles (relating to "Valuing Differences", "Employee Interests",
and "Miscellaneous") in EASYNOTES.LIS.
					Regards, 		--Mike
 | 
| 473.2 | one example... | WINERY::BOUCHARKE |  | Fri Feb 26 1988 15:32 | 1 | 
|  |     How about the conference called:firearms?
 | 
| 473.3 | confidentiality and proprietary | AUNTB::SOEHL | Keeping the lid on | Fri Feb 26 1988 15:59 | 4 | 
|  |     As the disclaimer at the beginning of EASYNOTES.LIS mentions, there
    are some conferences that are not open to the general DIGITAL public
    because they relate to unannounced products/projects.  Many of these
    are not even announced.  
 | 
| 473.4 | Please let me know where you are getting your copy of the list! | LEDER1::THOMPSON | Question reality | Fri Feb 26 1988 16:30 | 12 | 
|  |     Where are you getting your copy of EASYNOTES.LIS? The FIREARMS
    conference (ALIEN::FIREARMS) has been listed in EASYNOTES.LIS
    for some time. The latest copy of EASYNOTES.LIS is always at
    ANCHOR::NET$LIBRARY:EASYNOTES.LIS. There are other copies around
    the net but the one on ANCHOR is the master copy.
    
    You can also look in the TLE::EASYNET_CONFERENCES conference
    where conferences are announced. Hit KP7 or SELECT to add it
    to your notebook.
    
    			Alfred Thompson
    			EASYNOTES.LIS Editor
 | 
| 473.5 | ... Birth, Death, Infinity | SDSVAX::SWEENEY | Patrick Sweeney DTN 352.2157 | Fri Feb 26 1988 17:40 | 23 | 
|  |     Reasons a NOTES conference no longer exists:
    
    (a) APATHY: many subjects can't sustain enough interest to justify
    the disk space (I didn't participate in them)  (By far the biggest
    reason)
    
    (b) CONTROVERSY: many subjects attract too much interest and visibility
    beyond the participants (ie sexuality, religion)  (Is note 111 here
    the right reference?)
    
    (c) SPLIT: one conference has broken into two or more
    
    (d) COMBINED: two or more conferences have merged
    
    (e) MOOT: a conference discusses an event that's past (ex. DECWORLD_87)
    
    Certain conferences discussing new products are referenced _only_ in
    conferences discussing the current product and thereby attract the
    involved as opposed to the merely curious. 
    
    A reference that's from 1984 or thereabouts is very likely to point
    to a non-existent conference as well since there's substantial movement
    of conferences in the EASYNET.
 | 
| 473.6 | adding on to .5 | WELKIN::ADOERFER |  | Sat Feb 27 1988 10:12 | 19 | 
|  | 
    a few more reasons you may not find a conference
    
    (f) MOVED: often references to a conference from a while back will
               point to a wrong node.  Alfred said how to get the current
    	       location.  Notes conference locations are also in VTX
    	       using the keywords NOTES_INDEX and/or EASYNOTES.
    (g) ADDRESS ERROR:  You know where the current location of the conference
	        is, but the system you are on has the wrong location
    	        for that node name.  This is getting rarer, but still
    	        possible.
    (h) TEMPORARY RESOURCE PROBLEM ON THE HOST NODE.  It's possible
               the disk the conference is on didn't get mounted, or
    	       was removed while the drive was needed for something
               else.  It's possible number of people trying for the
    	       file exceeds the limits of users the system gave to 	
    	       notes usage.
    _bill
    
 | 
| 473.7 | They are not required to be accessible all the time | ALIEN::MELVIN | Ten zero, eleven zero zero by zero 2 | Sat Feb 27 1988 18:05 | 15 | 
|  | >    How about the conference called:firearms?
Something to realize at the start is that any notesfile anywhere is not
always guaranteed to be accessible 100% of the time.  Sometimes the systems
involved have to be used for real work and will occassionally be taken off
the network (depending on what has to get done).  Other times, the network
traffic puts a sufficient load on the target system that access has to be
restricted to certain hours, when normal workloads will not be impacted.
FIREARMS is on a system that has been taken standalone a number of times in
recent weeks.  It is quite possible that you could not get to it for that
reason.  As far as that one is concerned, you'll probably have to look for
the conspiracy of silence elsewhere :-).
-Joe
 |