Operating System - OpenVMS
1752799 Members
5704 Online
108789 Solutions
New Discussion юеВ

Re: Moving the queue manager to a non-system disk

 
SOLVED
Go to solution
MarkOfAus
Valued Contributor

Re: Moving the queue manager to a non-system disk

Simon, the disk is mounted before the queue manager is started via the clu_mount_disk command provided by HP. All of this is done is sylogicals.



Incidentally,

If I move the files back to sys$system, remove the start/queu/manager from sylogicals, the system starts the queue manager correctly at startup.
Volker Halle
Honored Contributor

Re: Moving the queue manager to a non-system disk

Mark,

the DEVOFFLINE error is most likely NOT related to the access to the qman disk - as one might think - but to an non-existing mailbox used to communicate with the JOB_CONTROL process, which does not exist when SYLOGICASL.COM is being invoked !

Just leave the START/QUE/MANA command out of SYLOGICALS.COM and try again. It will work (of you have the disk mounted and the logical assigned).

Volker.
MarkOfAus
Valued Contributor

Re: Moving the queue manager to a non-system disk

Volker,

"there is no need to manually issue the START/QUEUE/MANAGER command (since approximately V5.5-2) during startup.
"

Ok. So I will remove that from the commands.
It still doesn't start up. Ack!

"All you need to do in SYLOGICALS.COM is:

- define QMAN$MASTER logical to point to the disk and directory where QMAN$MASTER.DAT resides. The location of the queue-manager database files are stored in QMAN$MASTER.DAT."

Done it!

"- MOUNT the QMAN disk"

Done it!

"The %MOUNT-I-REBUILD operation is a synchronous operation, so the MOUNT command does not return to DCL until the volume has been rebuilt."

As I thought, hence I added norebuild "just in case"...


Volker.
Volker Halle
Honored Contributor

Re: Moving the queue manager to a non-system disk

Mark,

is there an error message - please also check OPERATOR.LOG !

Did you manually do a STOP/QUE/MANA/CLUSTER before moving the data to the common disk ? Try manually starting the queue manager ONCE:

$ START/QUE/MANAGER DKC300:[COMMON.SYSTEM]

Volker.
MarkOfAus
Valued Contributor

Re: Moving the queue manager to a non-system disk

Volker,

"is there an error message - please also check OPERATOR.LOG !"

The only error message is in the startup.log. There is 1 error in the operator.log referring to decdtm. This has never been an issue though.


"Did you manually do a STOP/QUE/MANA/CLUSTER before moving the data to the common disk ? "

Yes, the order of details was:
stop the queue, wait for it to drop its process (and close the files), then copy the files from the current location to the new one. It should have been a simple thing.



"Try manually starting the queue manager ONCE:

$ START/QUE/MANAGER DKC300:[COMMON.SYSTEM]"

Ok, I have done this, but I will try it again.

I moved the files back to their original position and then rebooted. Viola, the queue manager started! No logical defined, either. Is that the problem?

Here's the sylogicals.com exerpt:
$ THIS_NODE = F$GETSYI("NODENAME")
$ if THIS_NODE .eqs. "EMU2"
$ then
$ @sys$sysdevice:[vms$common.sysmgr]clu_mount_disk dkc300 sys3
$ sho dev/mount
$ dir dkc300:[000000]
$ define/system/exec common$disk dkc300:
$ endif
$ if THIS_NODE .eqs. "EMU1"
$ then
$ @sys$sysdevice:[vms$common.sysmgr]clu_mount_disk dka300 set02
$ define/system/exec common$disk dka300:
$ endif
$
$ define/system/exec comsys common$disk:[common.system]
$ define/system/exec datsys common$disk:[common.system]
$ define/system/exec comadm common$disk:[common.admin]
$
$ DEFINE/SYSTEM/EXECUTIVE SYSUAF comsys:sysuaf.dat
$ DEFINE/SYSTEM/EXECUTIVE RIGHTSLIST comsys:rightslist.dat
$ DEFINE/SYSTEM/EXECUTIVE NETPROXY comsys:NETPROXY.DA
$ define/system/executive LMF$LICENSE comsys:LMF$LICENSE.LDB
.
.
.
$ write sys$output "SYLOGICALS> Defining Qman$Master"
$ DEFINE/SYSTEM/EXECUTIVE QMAN$MASTER common$disk:[common.system]
$ sho log qman$master
$ write sys$output "SYLOGICALS> Setting rebuild of common$disk"
$ SET VOLUME/REBUILD COMMON$DISK:


So there is nothing startling in here - except a lot of debugging info.

The startup.log:

%STDRV-I-STARTUP, OpenVMS startup begun at 2-AUG-2007 15:30:23.26
Searching for disk DKC300...
%MOUNT-I-MOUNTED, SHAD03B mounted on _$4$DKC300: (EMU2)
%MOUNT-I-REBLDREQD, rebuild not performed; some free space unavailable; diskquo

Device Device Error Volume Free Trans Mnt
Name Status Count Label Blocks Count Cnt
$4$DKC0: (EMU2) Mounted 0 ALPHASYS 57731334 188 1
$4$DKC300: (EMU2) Mounted 0 SYS3 66528972 1 1

Directory DKC300:[000000]

000000.DIR;1 BACKUP.DIR;1 BACKUP.SYS;1 BADBLK.SYS;1
BADLOG.SYS;1 BITMAP.SYS;1 COMMON.DIR;1 CONTIN.SYS;1
CORIMG.SYS;1 INDEXF.SYS;1 ORACLE_CONV.DIR;1 RESTORE.DIR;1
RSDBLIST.LIS;1 SECURITY.SYS;1 SMART.DIR;1 SMART_BASE.BCK;1
VOLSET.SYS;1

Total of 17 files.
SYLOGICALS> Defining Qman$Master
"QMAN$MASTER" = "COMMON$DISK:[COMMON.SYSTEM]" (LNM$SYSTEM_TABLE)
SYLOGICALS> Starting Queue Manager.
%SYSTEM-F-DEVOFFLINE, device is not in configuration or not available
SYLOGICALS> Queue Manager started.
SYLOGICALS> Setting rebuild of common$disk


MarkOfAus
Valued Contributor

Re: Moving the queue manager to a non-system disk

Apologies the startup.log is an older one, but essentially all the information is the same except the volume label of the disk.
Volker Halle
Honored Contributor

Re: Moving the queue manager to a non-system disk

Mark,

you still seem to issue the START/QUE/MANA command in SYLOGICALS.COM - remove it.
Then reboot - any error message ?

$ SHO QUE/MANA/FULL

If it's not running: $ START/QUE/MANA COMMON$DISK:[COMMON.SYSTEM]

Then reboot - any errors ? Is the queue manager running now ?

Volker.
MarkOfAus
Valued Contributor

Re: Moving the queue manager to a non-system disk

Volker,

Apologies, the log was an old one. Sorry.

"you still seem to issue the START/QUE/MANA command in SYLOGICALS.COM - remove it.
Then reboot - any error message ?"

No errors.


"$ SHO QUE/MANA/FULL"

SRS$USER:MARK> SHO QUE/MANA/FULL
Master file: DKC300:[COMMON.SYSTEM]QMAN$MASTER.DAT;

Queue manager SYS$QUEUE_MANAGER, running, on EMU2::
/ON=(EMU2)
Database location: DKC300:[COMMON.SYSTEM]

So, the queue manager is now running!!

Therefore, the sylogicals.com explanation is incorrect? You should only run the START/QUEUE/MANAGER QMAN$MASTER once after the copy?

To quote sylogicals.com:
"$! default. To place the queue manager database in another location, enter
$! the START/QUEUE/MANAGER command with a parameter. For example, to put
$! the queue database files in the same cluster common directory as the
$! queue master file, enter the command:
$!
$! $ START/QUEUE/MANAGER/ON=(NodeX,NodeY,NodeZ) QMAN$MASTER
"

Thanks,
Mark.
Volker Halle
Honored Contributor

Re: Moving the queue manager to a non-system disk

Mark,

you need to ONCE run the START/QUE/MANA disk:[dir] manually after moving the files after STOP/QUE/MANA/CLUSTER.

So the comments in SYLOGICALS.TEMPLATE are a little bit misleading...

The disk:[dev] information is stored in QMAN$MASTER.DAT, so the QUEUE_MANAGER will find this information, if you correctly define QMAN$MASTER and mount the disk.

You need to issue the START/QUE/MANA disk:[dir] command only ONCE to WRITE that info into QMAN$MASTER.DAT.

Volker.
John Gillings
Honored Contributor

Re: Moving the queue manager to a non-system disk

Mark,

Could you please show your exact and complete logical name:

$ SHOW LOG/FULL QMAN$MASTER*

Make sure it's EXEC mode.

I suspect the problem is the disk name in the definition. "dkc300" may work for most things, but the queue manager is a bit more fussy than most. The definition of QMAN$MASTER must be identical across all nodes, and must point to the same file. Some ways of referring to a device work differently across nodes. It looks like cluster wide working name should be $4$DKC300
A crucible of informative mistakes