- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- Re: Mixed architecture cluster sharing QMAN$MASTER...
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-14-2009 05:37 PM
тАО02-14-2009 05:37 PM
All systems are running decnet phase V however we haven't resolved the name resolution issue yet, so init/batch/start/on=
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.
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-14-2009 08:16 PM
тАО02-14-2009 08:16 PM
Re: Mixed architecture cluster sharing QMAN$MASTER DB
I thought that it was required. I do it.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-15-2009 12:30 AM
тАО02-15-2009 12:30 AM
Re: Mixed architecture cluster sharing QMAN$MASTER DB
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=
This would have nothing to do with DECnet whatsoever. Please explain...
Volker.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-15-2009 01:49 AM
тАО02-15-2009 01:49 AM
Re: Mixed architecture cluster sharing QMAN$MASTER DB
In a word, YES.
That is how rolling upgrades work with mixed versions as well.
- Bob Gezelter, http://www.rlgsc.com
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-15-2009 05:48 AM
тАО02-15-2009 05:48 AM
Re: Mixed architecture cluster sharing QMAN$MASTER DB
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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-15-2009 05:48 AM
тАО02-15-2009 05:48 AM
Re: Mixed architecture cluster sharing QMAN$MASTER DB
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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-15-2009 06:03 AM
тАО02-15-2009 06:03 AM
Re: Mixed architecture cluster sharing QMAN$MASTER DB
Dave
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-15-2009 06:23 AM
тАО02-15-2009 06:23 AM
Re: Mixed architecture cluster sharing QMAN$MASTER DB
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.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-15-2009 06:30 AM
тАО02-15-2009 06:30 AM
Re: Mixed architecture cluster sharing QMAN$MASTER DB
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.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-15-2009 08:31 AM
тАО02-15-2009 08:31 AM
Re: Mixed architecture cluster sharing QMAN$MASTER DB
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.