Installing Oracle (BEA) (DMQ) MessageQ (32bit) V5.0 on Integrity (64bit) running OpenVMS V8.3-1H1

[Neal Kirby]

Has anyone any experience of installing Oracle (BEA) (DMQ) MessageQ (32bit) V5.0 on Integrity (64bit) running OpenVMS V8.3-1H1. I have a licensed version of Oracle MessageQ for Itanium (Oracle Download). The official Oracle Docs are 10 years old - (Shows how install of MessageQ V5 to Alpha from CD).

When I attempt the install I see:
=================================

$ @SYS$UPDATE:VMSINSTAL MQI64V1050 DISK$USER:[MESSAGEQ_UNPACK]


OpenVMS Software Product Installation Procedure V8.3-1H1


It is 22-OCT-2010 at 11:39.

Enter a question mark (?) at any time for help.

* Are you satisfied with the backup of your system disk [YES]?


The following products will be processed:

MQI64V1 V5.0


Beginning installation of MQI64V1 V5.0 at 11:40

%VMSINSTAL-I-RESTORE, Restoring product save set A ...
%BACKUP-W-NOFILES, no files selected from DISK$USER:[MESSAGEQ_UNPACK]MQI64V1050.
A;
%VMSINSTAL-E-NOPROC, The kit's installation procedure is missing.


Has anyone any experience? Is it OK to install the 32bit version on 64bit architecture in the first place? Is there any more up-to-date installation doc available?

Thanks for your support.

Neal Kirby

[labadie_1]

Hi

Can you list all your savesets ?
And if you list your savesets, do you find a kitinstal.com ?

[Neal Kirby]

When I unzip the download B48370-01.Zip this is what I see:

Directory DISK$USER:[MESSAGEQ_UNPACK]

MQI64V1050.A;1
MQI64V1050.B;1

Total of 2 files.

[Neal Kirby]

I tried this again. I FTP'd the Zip file to VMS & unziped it using TCPWARE:UnZip. This made a difference as I am getting a different error:

$ @sys$update:vmsinstal


OpenVMS Software Product Installation Procedure V8.3-1H1


It is 27-OCT-2010 at 14:31.

Enter a question mark (?) at any time for help.

* Are you satisfied with the backup of your system disk [YES]?
* Where will the distribution volumes be mounted: DISK$USER:[MESSAGEQ_UNPACK.ZIP
PED]

Enter the products to be processed from the first distribution volume set.
* Products: *
* Enter installation options you wish to use (none):

The following products will be processed:

MQI64V1 V5.0


Beginning installation of MQI64V1 V5.0 at 14:32

%VMSINSTAL-I-RESTORE, Restoring product save set A ...
%BACKUP-F-NOTSAVESET, DISK$USER:[MESSAGEQ_UNPACK.ZIPPED]MQI64V1050.A;1 is not a
BACKUP save set
%VMSINSTAL-E-NOSAVESET, Save set A cannot be restored.


Perhaps we have been sold a pony. I'm thinking from labadie entry - that perhaps this is not the full package? Can someone confirm what the contents on the download should include?

[Robert Gezelter]

Neal,

Please check the file that you downloaded (UNZIP -t). After unZIPing (using the OpenVMS UNZIP, possibly with the "-V" (preserve OpenVMS file attributes) option, please do a DIRECTORY/FULL on the file to list its attributes.

- Bob Gezelter, http://www.rlgsc.com

[Steven Schweda · Accepted solution]

> Has anyone any experience?

Not I, but ...

> [...] TCPWARE:UnZip.

Not a useful description. "unzip -v" should
say useful things.

> %BACKUP-F-NOTSAVESET, [...]

Yow. I wouldn't have expected that.

> Please check the file that you downloaded
> (UNZIP -t).

If you didn't get any complaints when
unpacking the thing, then "-t" is unlikely to
reveal anything new.

> After unZIPing (using the OpenVMS UNZIP,
> possibly with the "-V" (preserve OpenVMS
> file attributes) option, [...]

"zip -V" _preserves_ VMS attributes. If that
was done, then no special options are needed
for UnZip. ("unzip -V" is not the droid
you're looking for. "unzip -h", for
details.)

> %VMSINSTAL-I-RESTORE, Restoring product save set A ...
> %BACKUP-W-NOFILES, no files selected from DISK$USER:[MESSAGEQ_UNPACK]MQI64V1050.A;

backup /list DISK$USER:[MESSAGEQ_UNPACK]MQI64V1050.A /save

Just in case:

show proc /case /pars

If you intend to use Zip+UnZip, get the
current released versions, Zip 3.0 and UnZip
6.0. (At least.) http://www.info-zip.org/

[Neal Kirby]

OK - With reference to Steven - I can see the following:

$ backup /list DISK$USER:[MESSAGEQ_UNPACK.zipped]MQI64V1050.A /save
Listing of save set(s)

Save set: MQI64V1050.A
Written by: BMQTEST
UIC: [000001,000220]
Date: 21-MAY-2008 22:52:32.07
Command: BACKUP [.FOO...] MQI64V1050.A/SAVE
Operating system: hp OpenVMS I64 version V8.2
BACKUP version: V8.2
CPU ID register: 80000000
Node name: _IAVMS1::
Written on: _$1$DKA0:
Block size: 32256
Group size: 10
Buffer count: 1010

[BMQTEST.BMQ50RP.CRON.INSTALLER.FOO.FOO]KITINSTAL.COM;2
108 21-MAY-2008 22:51
[BMQTEST.BMQ50RP.CRON.INSTALLER.FOO.FOO]MQI64V1050.RELEASE_NOTES;1
221 30-MAR-2005 15:48

Total of 2 files, 329 blocks

With reference to labadie - Yes - A KITINSTAL.COM exists. I have to say - this looks encouraging.

I am also making progress on the install:
=========================================
$ @SYS$UPDATE:VMSINSTAL


OpenVMS Software Product Installation Procedure V8.3-1H1


It is 27-OCT-2010 at 15:43.

Enter a question mark (?) at any time for help.

* Are you satisfied with the backup of your system disk [YES]?
* Where will the distribution volumes be mounted: DSA1:[MESSAGEQ_UNPACK.ZIPPED]

Enter the products to be processed from the first distribution volume set.
* Products: *
* Enter installation options you wish to use (none):

The following products will be processed:

MQI64V1 V5.0


Beginning installation of MQI64V1 V5.0 at 15:43

%VMSINSTAL-I-RESTORE, Restoring product save set A ...
%VMSINSTAL-I-RELMOVED, Product's release notes have been moved to SYS$HELP.

MessageQ for OpenVMS I64 V5.01

Installation Procedure

Copyright BEA Systems, Inc. 2005.
All rights reserved.

You acknowledge that your use of this software is subject to
(i) the license terms that you signed when you placed your most
recent order with us; or, if you haven't signed a license agreement
with us, (ii) the shrinkwrap license terms included in your most
recent order with us for which we shipped software media to you;
or, if neither (i) or (ii) are applicable, then, (iii) if you are
downloading this software from edelivery.oracle.com, then the Oracle
Electronic Delivery Trial License Agreement (which you acknowledge
that you have read and understand) governs your use of the software.
Note: Programs downloaded for trial use or downloaded as replacement
media may not be used to update any unsupported programs.

MessageQ is a registered trademark of BEA Systems, Inc.


======================================================================
The MessageQ for OpenVMS I64 installation is divided into two parts:

Part 1: Base kit installation
Part 2: Client Library installation
======================================================================

--- Part 1: Select Base Kit Support ---

* Install the Base kit (144500 blks) [NO]: y

--- Part 2: Select Client Library Kit Support ---

%MQI64V1-I-CLSUPPORT, Client Library support is included with the Base kit

%MQI64V1-I-BLKSREQ, Blocks required for installation is 144500
%MQI64V1-I-DECTCP, UCX TCP/IP support will be built

* Device where MessageQ will reside [SYS$SYSDEVICE]:
* Do you want to purge files replaced by this installation [YES]?

=======================================================================
All questions regarding the installation of MessageQ for OpenVMS I64
have now been asked. The installation will continue for
approximately 15-90 minutes, depending on load and CPU type.
=======================================================================

%VMSINSTAL-I-RESTORE, Restoring product save set B ...
%BACKUP-E-POSERROR, error positioning DSA1:[MESSAGEQ_UNPACK.ZIPPED]MQI64V1050.B;
1
-RMS-F-IOP, operation invalid for file organization or device
%BACKUP-E-READERR, error reading DSA1:[MESSAGEQ_UNPACK.ZIPPED]MQI64V1050.B;1
-BACKUP-E-BLOCKCRC, software block CRC error
%BACKUP-E-INVBLKSIZE, invalid block size in save set
%BACKUP-E-INVRECTYP, invalid record type in save set
%BACKUP-E-INVRECSIZ, invalid record size in save set
%BACKUP-E-INVRECTYP, invalid record type in save set
%BACKUP-E-INVRECSIZ, invalid record size in save set
%BACKUP-W-INCFILATR, incomplete file attribute data for DSA0:[SYS0.SYSUPD.MQI64V
1050]CL.OLB;1
%BACKUP-E-VBNMISSING, DSA0:[SYS0.SYSUPD.MQI64V1050]CL.OLB;1 has missing blocks 1
through 389
%BACKUP-E-INVRECTYP, invalid record type in save set
%BACKUP-E-INVRECSIZ, invalid record size in save set
%BACKUP-E-INVRECTYP, invalid record type in save set
%BACKUP-E-INVRECSIZ, invalid record size in save set
%BACKUP-E-BLOCKLOST, block of DSA1:[MESSAGEQ_UNPACK.ZIPPED]MQI64V1050.B;1 lost d
ue to unrecoverable error
-BACKUP-E-HDRCRC, software header CRC error
%BACKUP-E-POSERROR, error positioning DSA1:[MESSAGEQ_UNPACK.ZIPPED]MQI64V1050.B;
1
-RMS-F-IOP, operation invalid for file organization or device
%BACKUP-E-POSERROR, error positioning DSA1:[MESSAGEQ_UNPACK.ZIPPED]MQI64V1050.B;
1
-RMS-F-IOP, operation invalid for file organization or device
%BACKUP-E-READERR, error reading DSA1:[MESSAGEQ_UNPACK.ZIPPED]MQI64V1050.B;1
-BACKUP-E-HDRCRC, software header CRC error
%BACKUP-E-INVBLKSIZE, invalid block size in save set
%BACKUP-E-FIDERROR, unexpected file change in DSA0:[SYS0.SYSUPD.MQI64V1050]CL.OL
B;1
%BACKUP-W-INCFILATR, incomplete file attribute data for DSA0:[SYS0.SYSUPD.MQI64V
1050]DMQ.TLB;1
%BACKUP-E-VBNMISSING, DSA0:[SYS0.SYSUPD.MQI64V1050]DMQ.TLB;1 has missing blocks
1 through 365
%BACKUP-E-INVRECTYP, invalid record type in save set
%BACKUP-E-INVRECTYP, invalid record type in save set
%BACKUP-E-INVRECSIZ, invalid record size in save set
%BACKUP-E-BLOCKLOST, block of DSA1:[MESSAGEQ_UNPACK.ZIPPED]MQI64V1050.B;1 lost d
ue to unrecoverable error
-BACKUP-E-HDRCRC, software header CRC error
%BACKUP-E-POSERROR, error positioning DSA1:[MESSAGEQ_UNPACK.ZIPPED]MQI64V1050.B;
1
-RMS-F-IOP, operation invalid for file organization or device
%BACKUP-E-READERRS, excessive error rate reading DSA1:[MESSAGEQ_UNPACK.ZIPPED]MQ
I64V1050.B;1
-BACKUP-E-HDRCRC, software header CRC error
%BACKUP-I-SPECIFY, specify option (QUIT or CONTINUE)
BACKUP>
%BACKUP-I-SPECIFY, specify option (QUIT or CONTINUE)
BACKUP> quit
%BACKUP-F-ABORT, operator requested abort on fatal error
%VMSINSTAL-E-NOSAVESET, Save set B cannot be restored.
%VMSINSTAL-E-INSFAIL, The installation of MQI64V1 V5.0 has failed.

so .A works / .B is failing. Thanks for the support thus far... I can almost smell success!

[Steven Schweda]

> I am also making progress on the install:

WHEN YOU CHANGED WHAT?

> Can you list all your savesets ?

Apparently, ".A" was ok.

> %BACKUP-E-POSERROR, [...]

Apparently, ".B" needs some work.

As usual, it might help if you showed what
you're doing, especially regarding the
creation/extraction/whatever of these BACKUP
save sets.

[Neal Kirby]

OK Steven - What I have learned:

1. Initially - I unzipped the file on Windows XP and FTP'd to OpenVMS. Wrong approach. Instead - download file. FTP zipped file to OpenVMS (Binary format). UnZip "-V" on OpenVMS.

2. Next - a key piece that I may not have mentioned before (Ahem)... is this command:
$ set file/attribute=(rfm:fix,rat:none,lrl:32256) .A

3. Run the install as documented.

Incidentally - I ran the set file/attribute for the .B to get the errors mentioned. Without running the command the installer does not acknowledge the existence of the .B.

[Steven Schweda]

> 1. Initially - I unzipped the file on
> Windows XP and FTP'd to OpenVMS. Wrong
> approach.

Yes, that's not the easiest way. (And yet
another demonstration of the value of an
accurate description of what you did.)

> Instead - download file. FTP zipped file
> to OpenVMS (Binary format). UnZip "-V" on
> OpenVMS.

As I said, you don't need to use "-V" with
UnZip (unless you want to restore version
numbers). "-V" does different things with
Zip and UnZip.

> $ set file/attribute [...]

If the archive had been created on VMS using
"zip -V", then this shouldn't have been
needed. Potentially more convenient
procedures for doing this exist. For
example:

http://antinode.info/dec/sw/fixrec.html

> [...] I ran the set file/attribute for the
> .B to get the errors mentioned. [...]

That would be to get _rid_ of the errors, not
to _get_ the errors?

> [...] "unzip -v" should say useful things.

Still true. Again, any UnZip program from
this century (and many from earlier) should,
with no special command-line options, on a
VMS system, extract BACKUP save sets with the
right (original) attributes, if the Zip
archive was created properly ("-V" on a VMS
system). If you paid money for this thing,
and that didn't work, then you might wish to
complain to the vendor.

[Neal Kirby]

Steven.

Thanks again. I ran CNVB.COM on the file and it discovered the original block size was 8192 and corrected this.

I ran the install & both .A & .B installation runs - (not with issue mind you)...

On install it appears to be defaulting to the TCP/IP services version of UCX (exists on SYS$SYSROOT - but not being used.

%MQI64V1-I-DECTCP, UCX TCP/IP support will be built

LNM$PROCESS_TABLE)
"DMQ_UCX$IPC_SHR_EXE" = "SYS$SYSROOT:[SYSLIB]UCX$IPC_SHR.EXE;"


Even though the logical clearly states that this should be TCPWare.

(LNM$SYSTEM_TABLE)
"UCX$IPC_SHR" = "TCPWARE:UCX$IPC_SHR.EXE"


When I work out the issue - I will add to the end of the Thread to complete the information. Thanks to all (esp. Steven) for all support to date.

[Steven Schweda]

> Even though [...]

It sounds as if you have more than one thing
about which to complain to the vendor.

> %MQI64V1-I-DECTCP, UCX TCP/IP support will be built

On a bad day, it's possible to mutilate the
KITINSTAL.COM on the fly (after figuring out
what to change, if the problem is curable).

[Neal Kirby]

Thanks Steven for your support.

To close out: Should anyone need this for future reference - Here is the best starting point (Accessing the Release Notes from within the Saveset):

@sys$update:vmsinstal MQI64V1050 File_Location OPTIONS N

This gives access the the Release Notes:
----------------------------------------
Software Version: BEA MessageQ for OpenVMS I64, Version 5.01

And in:
-------
1.2 New and Changed Features for MessageQ Version 5.01
This section describes the new and changed features for Version 5.01 release of MessageQ for OpenVMS:

Features not supported in this release
---
- MessageQ/TUXEDO Messaging Bridge for Alpha OpenVMS Version 7.1.
- LU 6.2
- Process Software Corporation's TCPWARE and Multinet TCP/IP stacks.
- PSS Scripting

So there you have it. The install is not running properly because TCPWare is not supported for MessageQ on I64.

Imagine the pain that could have been saved if the vendor said this first day - as opposed to 'there's no difference between MessageQ for Alpha & MessageQ for Itanium'.

Thanks for all the support. I learned a lot.

[Verne Britton]

Does TCPWare have a fake IPC_SHR image ... on my Multinet system:

$ pipe sh log/sys | sear sys$pipe IPC_SHR
"TCPIP$IPC_SHR" = "MULTINET:UCX$IPC_SHR.EXE"
"UCX$IPC_SHR" = "MULTINET:UCX$IPC_SHR.EXE"

so ... can you build it for UCX and it still could work as TCPWare will "fake it out" ??

Verne

[Neal Kirby]

Interesting suggestion Verne. I have to say that the thought did cross my mind - (& testing the scenario will be considered) but it would be an unsupported configuration for an Enterprise System and that would be a concern.

We are currently reviewing if HP OpenVMS TCP/IP Services can co exist with PSC TCPWare (both started on the same system).

If TCP/IP services was turned on (& could co-exist with TCPWare) - we could complete the install of MessageQ. I would then be content in testing bus communication over MessageQ/TCP-IP Services as opposed to MessageQ/TCPWare. We still need TCPWare as a number of other applications depend on it.

[Hoff]

The chances of two disparate IP stacks coexisting (and with both running) are somewhere between impossible and vanishingly small; the scope for collisions is, well, huge.

And as is typical for many enterprise sites, the requirements are intractably tangled. You need to get that sorted.

Your likely options here will include migrating to VM guests or to multiple physical boxes (clustered), or a port (of the application and the IP stacks, or a port off VMS, or off of MQ), or convincing your vendors to add support the configuration. None of which will be cheap.

[Neal Kirby]

Thanks Hoff.

We just got information from PSC that - "They can not run side by side. Once one is brought up the other can not be brought up without a reboot."

So that is off the table. Worth questioning though - even if the expectation of 2 IP stacks working side-by-side was some what implausible.

Getting feedback from the vendor that a patch may be available (Oct 15, 2010) to allow MessageQ on I64 to install with TCPWare and work as expected. I will feedback when I have more details.

[Neal Kirby]

I just want to close this thread. I want to inform you that Oracle had a patch to allow MessageQ work on Itanium with TCPWare. This patch was an initial release and did not work properly. I worked with Oracle to test this patch on a production type system and we worked through 3 patch releases together to get it to a production ready standard. We are now running on MessageQ on Itanium with TCPWare without issue since December 27th, 2010. Thanks to everyone for supporting me on this Thread.

[Neal Kirby]

Thread Closed.