JBREDESE%carleton.edu@RELAY.CS.NET (John Bredesen x4627) (11/13/86)
Greetings! Back in May, Kenneth Adelman from Caltech reported that he was having a problem defining a cluster alias for DECnet. The NCP commands DEFINE EXEC ALIAS NODE FOO and DEFINE EXEC ALIAS INCOMING ENABLED apparently caused his machine to bugcheck. We would like to do that (use the alias, not bugcheck) at our site and I was wondering if anyone has used this with/without any problems? Is your problem fixed Kenneth? Thanks for any info or 'gotchas'. John Bredesen Carleton College Northfield, MN jbredese@carleton.edu
ken@HAMLET.CALTECH.EDU (Kenneth Adelman) (11/16/86)
> Back in May, Kenneth Adelman from Caltech reported that he was having a problem > defining a cluster alias for DECnet. The NCP commands DEFINE EXEC ALIAS NODE > FOO and DEFINE EXEC ALIAS INCOMING ENABLED apparently caused his machine to > bugcheck. We would like to do that (use the alias, not bugcheck) at our site > and I was wondering if anyone has used this with/without any problems? Is your > problem fixed Kenneth? My dictionary defines "default" as "failure to meet an obligation". Because defaults are a bad thing we don't use them. Evidentally there is a bug in the VMS V4.4 NETACP which requires that EXECUTOR MAXIMUM LINKS be set to 32 or more when using the alias node feature. We had it set to about 10 or 15. I seem to recall the default is 32. Ken