Operating System - OpenVMS
cancel
Showing results for 
Search instead for 
Did you mean: 

Mixed architecture cluster sharing QMAN$MASTER DB

 
SOLVED
Go to solution
The Brit
Honored Contributor

Mixed architecture cluster sharing QMAN$MASTER DB

Is it acceptable for a Queue database to be shared between Itanium and Alpha systems in the same cluster. (Itanium is 8.3-1H1, and Alpha is 8.3).

All systems are running decnet phase V however we haven't resolved the name resolution issue yet, so init/batch/start/on=:: doesn't work. At the moment the alpha has its own Queue DB on its system disk, and the itaniums have their own DB on their system disk.

The nodes share many common disks and so it would be simple to set it up so that all nodes can see a single DB, the question is whether the DB is compatible with both architectures.

Thanks for any help,

Dave.
17 REPLIES 17
Steven Schweda
Honored Contributor

Re: Mixed architecture cluster sharing QMAN$MASTER DB

> Is it acceptable [...]

I thought that it was required. I do it.
Volker Halle
Honored Contributor

Re: Mixed architecture cluster sharing QMAN$MASTER DB

Dave,

sure, sharing the queue manager database is supported and strongly suggested as well. Note that you should also share a lot of other files (SYLOGICALS.TEMPLATE has the list).

Make sure to MOUNT the common disk, containing QMAN$MASTER.DAT and all the other common files, in SYLOGICALS.COM and DEF/SYS/EXE QMAN$MASTER to point to that common QMAN$MASTER file. Make sure you named the database location of the Queue-Manager files in a cluster-wide unique way (don't use SYS$SYSTEM !). Check with SHOW QUE/MANA/FULL

What do you mean with: 'we haven't resolved the name resolution issue yet, so init/batch/start/on=:: doesn't work' ?
This would have nothing to do with DECnet whatsoever. Please explain...

Volker.
Robert Gezelter
Honored Contributor

Re: Mixed architecture cluster sharing QMAN$MASTER DB

Dave,

In a word, YES.

That is how rolling upgrades work with mixed versions as well.

- Bob Gezelter, http://www.rlgsc.com
Hakan Zanderau ( Anders
Trusted Contributor

Re: Mixed architecture cluster sharing QMAN$MASTER DB

Dave,

One thing....

When the queuemanager starts it looks for the location of QMAN$MASTER.DAT

The defaultlocation is SYS$SYSTEM, but if you move it to another location you need to define the logical QMAN$MASTER.

The QueueManager uses three files
QMAN$MASTER.DAT
SYS$QUEUE_MANAGER.QMAN$QUEUES
SYS$QUEUE_MANAGER.QMAN$JOURNAL

The logical is the pointer to the location of QMAN$MASTER.DAT.

QMAN$MASTER.DAT holds the location of the queue & journal files.

If you move QMAN$MASTER, define the logical and start the QueueManager with

$ START/QUEUE/MANAGER

The location of the queue & jounal files will still be SYS$SYSTEM.

The format for starting the queuemanager is

$ START/QUEUE/MANAGER [location of queue and jornal files ]

After you have moved all three files, start the QueueManager using

$ START/QUEUE/MANAGER QMAN$MASTER

Hakan
Don't make it worse by guessing.........
The Brit
Honored Contributor

Re: Mixed architecture cluster sharing QMAN$MASTER DB

Volker,
I assumed it was something to do with DECnet because of the error, but I see now that it is not, it is with the Job Controller.

i.e.
$ init/batch/start/on=SPEEDY:: TEST_Q
%JBC-E-NOSUCHNODE, remote node is unknown or not reachable

however SPEEDY is a cluster Node, vis.

$ show cluster

View of Cluster from system ID 1059 node: BUD 15-FEB-2009 07:39:42
â â â â â â â â â â â â â â â â â â â â â â â â â ¬â â â â â â â â â â
â SYSTEMS â MEMBERS â
â â â â â â â â â â ¬â â â â â â â â â â â â â â â ¼â â â â â â â â â â ¤
â NODE â SOFTWARE â STATUS â
â â â â â â â â â â ¼â â â â â â â â â â â â â â â ¼â â â â â â â â â â ¤
â Node1 â VMS V8.3-1H1 â MEMBER â
â SPEEDY â VMS V8.3 â MEMBER â
â Node2 â VMS V8.3-1H1 â MEMBER â
â Node3 â VMS V8.3-1H1 â MEMBER â
â â â â â â â â â â ´â â â â â â â â â â â â â â â ´â â â â â â â â â â

Dave
The Brit
Honored Contributor

Re: Mixed architecture cluster sharing QMAN$MASTER DB

Sorry about that last entry, it is a show cluster command.

Dave

Highlighted
Volker Halle
Honored Contributor

Re: Mixed architecture cluster sharing QMAN$MASTER DB

Dave,

check with SHOW QUE/MANAGER/FULL on all your cluster nodes, whether they share the SAME qman database.

Do the JOB_CONTROL and QUEUE_MANAGER processes exist on node SPEEDY ? Can you execute the command on node SPEEDY itself sucessfully ?

Also see HELP/MESS NOSUCHNODE

Volker.


Volker Halle
Honored Contributor

Re: Mixed architecture cluster sharing QMAN$MASTER DB

Dave,

your Alpha (V8.3, node SPEEDY) system does NOT share the queue manager database with your Itanium systems. You can DEFINE a batch queue on the I64 systems with /ON=SPEEDY::, but as soon as you try to START the queue, it will fail with %JBC-E-NOSUCHNODE, as there is a different QUEUE_MANAGER running on SPEEDY, which cannot communicate with the I64 systems, because it's qusing a different queue-manager database. SHO QUE/MANA/FULL will tell. Don't be mislead by the fact, that all systems may show SYS$COMMON:[SYSEXE] as the db location. This points to a DIFFERENT device on your Alpha or your Itanium systems !

If you want to share queues between the systems, you need to have a COMMON queue-manager database.

Volker.
Steven Schweda
Honored Contributor

Re: Mixed architecture cluster sharing QMAN$MASTER DB

> Make sure to MOUNT the common disk, [...]

Or else expect to (re-)do the queue start-up
command(s) sometime after that disk is
mounted. As I recall, JBC-E-JOBQUEDIS is
what you may get if the disk is unavailable.