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

Update: Wrong ACP

The Question is: 

I have been trying to upgrade an antiquated VMS 5.2
machine (a Vaxstation 3500) to run VMS 5.5.  As we have a
site license for VMS I tried what I thought was a simple solution
and copied the system from a machine already running VMS 5.5.

Things seem to be OK after I fixed up the node specific
stuff but I now get the queue manager hanging when it is started
or when a job is submitted to it.

The operator log messages are as follows:

%QMAN-E-COMMERROR, unexpected error #5 in communicating with node CSID 00000000
-SYSTEN-F-WRONGACP, wrong ACP for device

The first message is not listed in my system messages
document and I haven't got the faintest where the CSID 00000000
comes from.  DECNET starts fine so the networking host info
is mostly correct.

What is QMAN trying to do?

Thanks,

The Answer is: 


   Assuming you do not want to (or need to) preserve the existing
   queue definitions -- that the startup files are set up to create
   the queue definitions if necessary, simply reinitialize the queue
   manager database and recreate the necessary batch, print and server
   queues.  See START/QUEU/MAN/NEW.

   The queue manager uses SCS information to keep track of queues
   across a VMScluster, and it would appear the queue database here
   contains "stale" SCS information, information associated with the
   old environment.

   My tendency here is to use the /ON qualifier on the INIT/QUEUE/START
   commands, and always passing in the current SCS nodename value -- the
   value retrieved via a f$getsyi("SCSNODE") specification.  This ensures
   that the correct (current) node information is always specified.  Each
   node -- standalone or present in a VMScluster -- issues the queue
   commands associated with queues local to itself, using this syntax.