Conference turris::easynet_conferences

Any updates on this effort?

I would prefer to access notefiles directly instead of routing through a VMS system.

Or, to try to find out myself the IP addresses, is there a place to find out 
the location of a DECnet node? then I can try to turn NODE into 
NODE.location.dec.com

If you look up the DECnet node using VTX EASYNET (see 1.13), it will often
show you a corresponding TCP/IP host name.

				Steve

> Or, to try to find out myself the IP addresses, is there a place to find out 
> the location of a DECnet node? then I can try to turn NODE into 
> NODE.location.dec.com

	As Steve said, there is VTX EASYNET.  You can also check where a node
	is registered from a DECnet Phase V system (or even a Phase IV system
	with a DECdns clerk).  For example, on Digital UNIX (or ULTRIX) with
	DECnet Phase V installed (and the DECnet UTIL subset installed),
	you can use the command syntofull command, example:

vaxcpu> /usr/field/syntofull humane vaxcpu ssdevo nac
humane => DEC:.mro.humane
vaxcpu => DEC:.zko.vaxcpu
ssdevo => DEC:.CXO.SSDEVO
nac => DEC:.LKG.NAC

	which should give Internet names of (all in .dec.com) humane.mro,
	vaxcpu.zko, ssdevo.cxo, nac.lkg.  Using the [DEC]dns Control
	Program you can map synonym to fullname via:

vaxcpu> dnscp
dns> show link dec:.DNA_NodeSynonym.humane dns$linktarget
                                SHOW
                            SOFTLINK  DEC:.DNA_NodeSynonym.humane
                                  AT  05-MAR-1997:14:55:54
                      DNS$LinkTarget = DEC:.mro.humane

	(the program is probably called something like DNS$Control on
	VMS, and if under Phase IV, the command syntax is different).

Thanks for the replies.

I no longer have access to a VMS account (never had it to an ULTRIX or 
D-UNIX), I'm now all PC-based (w95/Exchange) so I'll use VTX EASYNET, 
through WIN VTX.

Well, I tried, but several of the conferences I follow either the node 
doesn't have a TCP address or access to the notesfile through TCP is denied.

So I guess I'll stick with a route node until the whole company moves out of 
DECnet.

    
    	How about WWW access?
    
    	You can use
    
    	http://www-esn.lkg.dec.com/decnotes/altavista.html
    
    	to find the conference.
    

> How about WWW access?

	Also uses a route node which the author is already using.  And
	using the WWW=>NOTES gateway you mentioned, while you can still
	emulate a notebook with bookmarks, you do lose the concept of seen
	maps .........

As discussed in DIGITAL, it seems that no other conferencing, forum or news 
product comes close to the functionality of notes.

Wonder if Digital will ever get to a totally non-VMS environment. Probably, 
but not in the near or mid-term future, unless something drastic happens.

I hope that somebody ports notes to NT before that, or we license the 3rd 
party product mentioned there.

I still want to add TCP/IP listings to EASYNOTES.LIS, but I doubt I will ever
get to it.  My group will (we think) soon be leaving the company and I'm looking
for a new maintainer for EASYNOTES.LIS and the list of conferences on the Web
page.

Paul

    re .27
    
    Paul,
    
    is this
    >>>get to it.  My group will (we think) soon be leaving the company ...
    one of these
    countless notes that we still loose competence...?
    
    Uli
    

> is this one of these countless notes that we still loose competence...?

Perhaps.  Stay tuned.

Paul

Now that it appears my group is not leaving the company, I may have time to add
TCP/IP listings to EASYNOTES.LIS.  Note that this same information is provided
to the Web Notes listing, so TCP/IP data would probably appear there also.

How should I do this?  The current eighty columns of EASYNOTES.LIS don't have
the space for more text, so should there be a second line below the conference
and DECnet information listing the TCP/IP information?  Should the format be
expanded to 132 columns?  Should there be a separate listing?

Suggestions are welcome.

Paul

	How about just providing a table mapping nodenames to hostnames
	for any node listed in the normal listing?  Such as:

DECnet	TCP/IP hostname
======	==================
HUMANE	humane.mro.dec.com
SMURF	smurf.zk3.dec.com
....

    
    	Good idea.
    
    	Anyone with any sort of data retrieval skills should be able to
    	match up a conference with a hostname if [s]he so desires.
    
    	Barring that, I'd suggest 132 columns with all details on one
    	line.