HP OpenVMS Systems

Ask the Wizard
» 

HP OpenVMS Systems

OpenVMS information

» What's new on our site
» Upcoming events
» Configuration and buying assistance
» Send us your comments

HP OpenVMS systems

» OpenVMS software
» Supported Servers
» OpenVMS virtualization
» OpenVMS solutions and partners
» OpenVMS success stories
» OpenVMS service and support
» OpenVMS resources and information
» OpenVMS documentation
» Education and training

Quick Links

» Non-javascript page
» Ask the Wizard
» OpenVMS FAQ

Test Drive OpenVMS

» OpenVMS I64 test drive
» Java test drive

Other information resources available to you include:

» OpenVMS freeware
» ECO kits, software and hardware support, prior version support
» Alpha SRM, ARC, and AlphaBIOS firmware updates
» ENCOMPASS - HP user group
» OpenVMS software downloads, OpenVMS freeware CD-ROM
» OpenVMS firmware locations
» DECconnect passive adaptor charts
» Cables reference guide
» MicroVAX console commands
» OpenVMS student research

Select a topic below to see Questions Frequently Asked by partners

» Using the online documentation library(installing BNU from the asap SDK)
» Global sections(how to create and use.)
» xx$CREATE_BUFOBJ system service(usage)
» Ethernet address(methods of determination)
» Shareable images(cookbook approach to creating one)
» Sharing data/code at absolute addresses(a guide with examples)
» Determining the Alpha microprocessor
» Using GETSYI to get hardware status

Evolving business value

» Business Systems Evolution
» AlphaServer systems transition planning
» Alpha RetainTrust program

Related links

» HP Integrity servers
» HP Alpha systems
» HP storage
» HP software
» HP products and services
» HP solutions
» HP support
disaster proof
HP Integrity server animation
HP Integrity server animation
Content starts here

Ask the Wizard Questions

DNS V1.1 Problem

The Question is:

I am experiencing DECnet event 353.5 (DNS-E-NOCOMMUNICATION)
accompanied by LINKEXIT errors on DNS client systems. This
appears to occur at random on about 6-10 clients at a time
but there does not appear to be anything in common occurring
on the systems at these times. The DNS servers have more
than adequate DECnet links available and the DNS$SERVER
account has ample quotas. What other circumstances could
cause this event and associated LINKEXIT message? I would
also be interested in locating more detailed information
about the internal mechanisms of DNS, or at least a brief
description of how to use the undocmented DNS$ANALYSE.

Notes:

1. We are using DNS V1.1 in a Phase IV environment.
2. The namespace is only served within an unrouted LAN.
2. The DNS servers are a clustered pair of VAX 4105's with a
   cluster alias, although DNS is installed as though the
   systems were independent and the clients do not reference
   the alias nodename in their DNS$DEFAULT_FILES.


The Answer is:

We're afraid we don't have a lot of information for you.
DNS V1 product is now almost ten years old.

If you were running V2 servers, I could help you.  If any of the clerks
which are loosing connectivity are V2 systems, you can turn on a protocol
trace, and other tracing. But if you are still running a pure V1 environment,