Re: Resolved: Windows 2000 Server and CSD07 problem

2004-06-23 Thread Peter Uranyi
Roger,

This was truly a heroic effort, but why didn't you try to run the install with
the MQPINUSEOK flag, as suggested in the memo.ptf?

E.g.:  U200212A.exe -a MQPINUSEOK=1

Then you only need to reboot once and you don't have to worry about anything
else.

Manual labor aside, there is one other potential problem with renaming files.
When the CSD gets installed the old files are backed up, so that you can revert
to the previous level if you need to.  (Although in the past seven years I
never had to do that :)
The renamed files won't get backed up, so you have to manually move them into
the backup directory and change their name back to the original.

Peter


--- Roger Lacroix <[EMAIL PROTECTED]> wrote:
> All,
>
> Thanks for your comments.
>
> No matter how many things I stopped and how many times I rebooted the server,
> I
> had the problem with locked files.
>
> Besides what mentioned below, here is what I did to resolve the problem:
> - Removed the MQ Taskbar icon from the Startup folder
> - Set the "IBM MQ Series" service to 'Manual' then REBOOTED.
> - Tried the CSD07 install again and of course it failed
> - Checked the CSD install log by doing the following command:
>   notepad %TEMP%\amqicsdn.txt
> - Search for the string 'Target file is in use'
> - For each entry found (I had 5), renamed it to 'roger_amq*'
> - REBOOTED again.
> - After the the reboot, deleted the 'roger_amq*' files
> - Tried the CSD07 install again and this time it worked.
> - REBOOT again.
> - Put back the Task Bar icon in the startup folder
> - Set the "IBM MQ Series" service to 'Automatic' and started the service.
> - REBOOTED one last time to make sure everything worked and it did.
>
> Now mqver gives 530.7 CSD07.  Yeah!!!
>
>
> Regards,
> Roger Lacroix
> Capitalware Inc.
> http://www.capitalware.biz
>
>
> Quoting Roger Lacroix <[EMAIL PROTECTED]>:
>
> > Help please,
> >
> > Box:
> > Windows 2000 Server SP4 (dual CPU)
> >
> > Today I installed WMQ v5.3 with CSD01 using Terminal Services (to D: drive
> of
> > server) and the install went fine (I copied the CD to a local drive then
> did
> > the install from it).  As I said, everything went fine and I reboot the
> > server.
> >
> > After the reboot, I downloaded CSD07.  First I stopped the MQ Services and
> > clicked 'Hide the icon'.  Check Task Manager for any AMQ*** or RUNMQ***
> tasks
> > and there were none.
> >
> > Under Terminal Services launched the CSD07 (U200212A.exe) and goes fine
> until
> > it
> > gets to'Checking files; please wait' (the 2nd time). Then I get the
> following
> > error:
> > 'IBM WebSphere MQ files are in use. Stop activity and retry. (AMQ4757)'
> >
> > I have rebooted the server 2 twice now, stopped services, checked the Task
> > Manager and I don't see anything MQ related running.  I have NOT even
> defined
> > a
> > queue manager yet on this server!!
> >
> > Could it be a problem with Terminal Services??  Or is CSD07 like CSD06
> where
> > it
> > wasn't fully baked by IBM?
> >
> > Anyone have an idea or comment?
> >
> > Regards,
> > Roger lacroix
> > Capitalware Inc.

Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at http://www.lsoft.com
Archive: http://vm.akh-wien.ac.at/MQSeries.archive


Re: CSD 6

2004-05-10 Thread Peter Uranyi
Nick,

> Does this ensure that files in use get overwritten?  If not, it sounds like
> it could cause problems.

This option is documented in the memo.ptf that comes with the CSD.  Do you
think IBM would tell you to do this if it wasn't safe?

Yes, you can replace in-use files, but you have to reboot your system to do
that.  Just think what happens when you install a Windows ServicePack.
Basically you are replacing your whole OS: the system dlls, drivers, and even
the kernel itself.  And you are doing this while your system is running!

The reason the CSD install fails is because it simply wants to avoid the
reboot.

I used listdlls and process explorer in the past and they are very useful, but
if your environment can tolerate a few minutes outage while you reboot your
server then don't waste your time trying to track down locked dlls.  (Of course
you should always stop your queue manager and all amq* and runmq* processes :-)

Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at http://www.lsoft.com
Archive: http://vm.akh-wien.ac.at/MQSeries.archive


Re: CSD 6

2004-05-07 Thread Peter Uranyi
Mike,

I found that instead of playing detective, the easiest way is to force the
install and then reboot the server.  Just specify the MQPINUSEOK option on the
command-line like this:

U200202A.exe -a MQPINUSEOK=1

This way the install will run even if files are in use.

HTH,
Peter

--- "Ward, Mike S" <[EMAIL PROTECTED]> wrote:
> Hi all, I am trying to apply csd 6 to a 5.3 install on windows 2000. The
> install waits for all MQ applications and processes to complete. Then it
> says checking files please wait. Then it stalls and says Websphere MQ files
> are in use. Stop activity and retry. The message is AMQ4757. Can anyone
> help? I can't find any MQ running except the csd.
>
> Thanks.
>
> Mike S. Ward Jr.
> A.V.P. Information Technology
> Security Service Federal Credit Union
> (210)476-4600
> [EMAIL PROTECTED]
>
> Instructions for managing your mailing list subscription are provided in
> the Listserv General Users Guide available at http://www.lsoft.com
> Archive: http://vm.akh-wien.ac.at/MQSeries.archive

Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at http://www.lsoft.com
Archive: http://vm.akh-wien.ac.at/MQSeries.archive


Re: AIX DB2 Remote ODBC entry

2004-04-27 Thread Peter Uranyi
--- Robert Broderick <[EMAIL PROTECTED]> wrote:
> What is needed to set up a DB2 ODBC remote entry for DB2 on an AIX machine
> running 5.0 broker. We have an ODBC entry for a local DB2 on the same box
> but need a access to a remote DB2 DB
>
>  bobbee

Just catalog the remote node and the database on your AIX machine, then the
ODBC entry will look no different from the one you setup for local databases.

Login as the instance owner and issue the following commands:

db2 "catalog tcpip node  remote  server "

db2 "catalog db  as  at node "

Then in your .odbc.ini add a line under ODBC Data Sources, and create a new
stanza with the  name:

[ODBC Data Sources]
=LTCSHARE=IBM DB2 ODBC Driver

[]
Driver=
Description=bobbee's remote database
Database=

HTH,
Peter

Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at http://www.lsoft.com
Archive: http://vm.akh-wien.ac.at/MQSeries.archive


Re: endmqlsr after endmqm

2004-03-26 Thread Peter Uranyi
John,

Do you have a newer version of the System Admin Guide?  Mine only lists the -m
and -w flags.

Peter

--- "Dawson, John" <[EMAIL PROTECTED]> wrote:
> Rebecca,
>
>   After reading Paul's response, I looked in the WMQ Version 5.3 System
> Administration Guide and it is documented. So at least Paul will not
> received the 'ruler on the hand' treatment.
>
>
> John
>
>
>  -Original Message-
> From:   Bullock, Rebecca (CSC) [mailto:[EMAIL PROTECTED]
> Sent:   Friday, March 26, 2004 1:12 PM
> To: [EMAIL PROTECTED]
> Subject:Re: endmqlsr after endmqm
>
> No, it's not a big deal, Pavel. And that's what I've done in the past, using
> the  ever popular kill -9. I'd hesitate to touch the setmqaut's since then
> you have to put them back. Hadn't thought of the MCAUSER -- That's a nice
> easy approach. But Paul's oh-so-secret flag is even easier.
>
> -Original Message-
> From: Pavel Tolkachev [mailto:[EMAIL PROTECTED]
> Sent: Friday, March 26, 2004 1:52 PM
> To: [EMAIL PROTECTED]
> Subject: Re: endmqlsr after endmqm
>
>
> Just gave it some thought..
>
> One way to achieve that (meaning -- the maintenance mode, without bringing
> down listener) must be to prohibit anyone to connect to QM, with setmqaut..
> Another should be to set MCAUSER in all channels to someone who cannot
> connect (like nobody). Also, is it so bad just to kill listener process?
>
> Pavel
>
>
>
>
>
>   "Bullock, Rebecca
>   (CSC)"   To:
> [EMAIL PROTECTED]
>   <[EMAIL PROTECTED]cc:
>   >Subject:  Re: endmqlsr after
> endmqm
>   Sent by: MQSeries
>   List
>   <[EMAIL PROTECTED]
>   n.AC.AT>
>
>
>   03/26/2004 12:53
>   PM
>   Please respond to
>   MQSeries List
>
>
>
>
>
>
> Hi, Ian. No, I don't have the answer, but I wanted to interject another
> reason one might want to end the listener but not the queue manager. In some
> circumstances, one might wish to perform some maintenance-type work on the
> queue manager but not have users connecting, only allowing access through
> applications/programs local to the MQ server (such as runmqsc). While you
> can ask that users not connect (ha!), the chances are that they still will.
> Being able to end the listener would preclude that. I've sometimes wondered
> about the requirement to end the qmgr, too..
>   -Original Message-
>   From: Chan, Ian M [mailto:[EMAIL PROTECTED]
>   Sent: Thursday, March 25, 2004 10:26 PM
>   To: [EMAIL PROTECTED]
>   Subject: endmqlsr after endmqm
>
>   Hi all,
>
>   This is not a problem question. However, I am really curious to know
> why.
>
>   Before MQ v5.3, I use UNIX listener rather than the MQ listener.  Now
> with the upgrade to v5.3, I started to use MQ listener.  Logically thinking,
> I start the qmgr and then the mq listener and end the listener before ending
> the qmgr.  However, the endmqlsr command cannot be issued while qmgr is
> active (you will get AMQ9596 error).  I have to endmqm first and then
> endmqlsr.
>
>   On the Windows platform, I got the same AMQ9596 error if I issue
> endmqlsr from the Command Prompt while the qmgr is active .  However I can
> end listener from the MQ services while the qmgr is active.
>
>   Anyone know why endmqlsr cannot be issued while qmgr is active ? To me
> it is logical to stop listener first and then the qmgr.  Besides, what is
> the difference between using endmqlsr from command prompt and the stop
> listener from MQ services in the Windows platform?
>
>   Regards,
>
>   Ian
>
>
>
>
>
> **
>
>
> This e-mail and any files transmitted with it may contain privileged or
>
>
> confidential information. It is solely for use by the individual for whom
>
>
> it is intended, even if addressed incorrectly. If you received this e-mail
>
>
> in error, please notify the sender; do not disclose, copy, distribute, or
>
>
> take any action in reliance on the contents of this information; and delete
>
>
> it from your system. Any other use of this e-mail is prohibited. Thank you
>
>
> for your compliance.
>
>
>
>
>
>
>
>
>
>
>
>
>
> --
>
> This e-mail may contain confidential and/or privileged information. If you
> are not the intended recipient (or have received this e-mail in error)
> please notify the sender immediately and destroy this e-mail. Any
> unauthorized copying, disclosure or distribution of the material in this
> e-mail is strictly forbidden.
>
> Instructions for managing your mailing list subscription are provided in
> the Listserv General Users Guide available at http://www.lsoft.com
> Archive: http://vm.akh-wien.ac.at/MQSeries.archive
>
>
>
> *

Re: Where do I find Default Queue Size ???

2004-02-26 Thread Peter Uranyi
Dennis,

> Where do I find what the default Queue size is for MQ V5.3  and can I still
> set the DefaultQueueSize to something bigger in the qm.ini file ?   This is
> for Solaris.

I just went through this "exercise" about a month ago.  MQ 5.3 supports queue
files greater than 2GB without any special tuning.

You just have to make sure that your filesystem can support the file size you
need and also check the file-size limit for the mqm user (ulimit -f).

Peter

Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at http://www.lsoft.com
Archive: http://vm.akh-wien.ac.at/MQSeries.archive


Re: SAVEQMGR PCF ERROR

2004-02-26 Thread Peter Uranyi
Brent,

> I was hoping someone could provide a new SAVEQMGR executable with this new
> queue attribute called NPMCLASS.
>
> Or step-by-step instructions on how to compile it myself.

I have attached the modified saveqmgr.h and queue.c files.  Make sure you have
downloaded the latest version from the SupportPac web site (a new version was
posted just a few weeks ago) and then compare the files to see what was
changed.
Compiling instructions are in the readme file for all supported platforms.

Peter
<>


Re: Running trigger monitor under non-mqm account

2004-02-26 Thread Peter Uranyi
Pavel,

I never tried to set this up but I know that the trigger monitor opens the
dead-letter queue on startup.

Hope this helps.
Peter

--- Pavel Tolkachev <[EMAIL PROTECTED]> wrote:
> Hello,
>
> Have anyone managed to run trigger monitor on behalf of non-mqm user? On AIX
> platform, we copied the binary without set-id bits and try to run it
>
> # path/to/runmqtrm -q INIT.QUEUE.NAME -m QM.NAME
> 5724-B41 (C) Copyright IBM Corp. 1994, 2002.  ALL RIGHTS RESERVED.
> WebSphere MQ trigger monitor started.
> Use of WebSphere MQ trigger monitor not authorized.
> WebSphere MQ trigger monitor ended.
>
> If what I want to do is possible, does the user have to have any other
> permissions than to the INIT queue? If not, what are our alternatives? Any
> ideas?
>
> Thank you,
> Pavel

Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at http://www.lsoft.com
Archive: http://vm.akh-wien.ac.at/MQSeries.archive


Re: SAVEQMGR PCF ERROR

2004-02-26 Thread Peter Uranyi
Michael,

> The version from 27-Jan-2004 was not an actual update,
> IBM is reorganising it's webcontent bit by bit and so
> the date changed and the url to the package, but not
> the package itself.

I don't know when the latest version came out, and what version you have, or
what IBM is doing with their web site, but I know that in the zip file I
downloaded the files had 1/27/2004 timestamps.  The contents of most files were
different from the one I previously had, (which were dated Aug 2003).
And the readme file just totally fooled me when it said:

| 05 Aug 2003|
| v5.3.1.a
...
| 27 Jan 2004|
|  v5.3.2|
|   a. Added -a and -x flags for specify parameters  |
|  to mqconnx for client connections |
|   b. shipped client and server version of windows, aix,|
|  solaris, linux executables|
|   c. cleaned up some code and makefiles to avoid   |
|  compile time warnings. Restructured makefiles.|

I thought for sure that I am looking at a new version.  And one other thing.
The zip file I downloaded on Jan 29 didn't have any windows executables, but
the one I got yesterday did.  According to the web site it was last updated on
2-2-2004.  Now I am totally confused.

Peter

Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at http://www.lsoft.com
Archive: http://vm.akh-wien.ac.at/MQSeries.archive


Re: SAVEQMGR PCF ERROR

2004-02-25 Thread Peter Uranyi
Rao,

I assume saveqmgr will be updated soon to include this new queue attribute.
Since the source code is included you can also do it yourself.

Peter


--- "Adiraju, Rao" <[EMAIL PROTECTED]> wrote:
> What does it mean - the Saveqmgr won't work with MQ V5.3 - CSD06, if so what
> are the alterantives. We are planning to upgrade to CSD06 within couple of
> weeks and we use Saveqmgr quite heavily.
>
> Cheers
>
> Rao Adiraju
> WebSphere MQ Specialist
> The National Bank of NZ Ltd.
> Wellington - New Zealand
> Tel:  +64-4-494 4299
> Fax: +64-4-802 8509
> Mbl: +64-211-216-116
>
>
>
> -Original Message-
> From: Peter Uranyi [mailto:[EMAIL PROTECTED]
> Sent: 26 February 2004 3:43 PM
> To: [EMAIL PROTECTED]
> Subject: Re: SAVEQMGR PCF ERROR
>
> Brent,
>
> A new queue attribute was introduced in CSD06, called NPMCLASS.
>
> It is documented in the readme file.
>
> Peter
>
> --- Brent Ireland <[EMAIL PROTECTED]> wrote:
> > Hi,
> >
> > I ran the saveqmgr and got about 30 "Unknown PCF Integer Parameter: 78"
> > messages.
> >
> > Does anyone why i am getting error 78? What does 78 refer to?
> >
> > I am running WebSphere MQ v5.3 on Win2K with CSD06.
> >
> > Thank you in advance.
> >
> > Brent Ireland
> > CAE Inc.
> > Global Information Technology (Dept J8) Supply Chain Programmers Group
> > Tel : (514) 341-6780 Ext. 2745 Fax  / Tilicopieur : (514) 734-5605
> > Email / Courriel : [EMAIL PROTECTED]
> >
> > Instructions for managing your mailing list subscription are provided
> > in the Listserv General Users Guide available at http://www.lsoft.com
> > Archive: http://vm.akh-wien.ac.at/MQSeries.archive
>
> Instructions for managing your mailing list subscription are provided in the
> Listserv General Users Guide available at http://www.lsoft.com
> Archive: http://vm.akh-wien.ac.at/MQSeries.archive
>
> This communication is confidential and may contain privileged material.
> If you are not the intended recipient you must not use, disclose, copy or
> retain it.
> If you have received it in error please immediately notify me by return email
> and delete the emails.
> Thank you.
>
> Instructions for managing your mailing list subscription are provided in
> the Listserv General Users Guide available at http://www.lsoft.com
> Archive: http://vm.akh-wien.ac.at/MQSeries.archive

Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at http://www.lsoft.com
Archive: http://vm.akh-wien.ac.at/MQSeries.archive


Re: SAVEQMGR PCF ERROR

2004-02-25 Thread Peter Uranyi
Brent,

A new queue attribute was introduced in CSD06, called NPMCLASS.

It is documented in the readme file.

Peter

--- Brent Ireland <[EMAIL PROTECTED]> wrote:
> Hi,
>
> I ran the saveqmgr and got about 30 "Unknown PCF Integer Parameter: 78"
> messages.
>
> Does anyone why i am getting error 78? What does 78 refer to?
>
> I am running WebSphere MQ v5.3 on Win2K with CSD06.
>
> Thank you in advance.
>
> Brent Ireland
> CAE Inc.
> Global Information Technology (Dept J8)
> Supply Chain Programmers Group
> Tel : (514) 341-6780 Ext. 2745
> Fax  / Tilicopieur : (514) 734-5605
> Email / Courriel : [EMAIL PROTECTED]
>
> Instructions for managing your mailing list subscription are provided in
> the Listserv General Users Guide available at http://www.lsoft.com
> Archive: http://vm.akh-wien.ac.at/MQSeries.archive

Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at http://www.lsoft.com
Archive: http://vm.akh-wien.ac.at/MQSeries.archive


Re: How to Specify Ethernet Adapter

2004-02-02 Thread Peter Uranyi
Arlen,

If you are always using the same IP address in the cluster then you could just
add it to the default channel definition.  This way all dynamically created
channels would automatically use the correct address/port.

Peter

--- "Williams, Arlen" <[EMAIL PROTECTED]> wrote:
> My problem is this is an MQ cluster repository and the outbound connection
> is being created dynamically. The remote queue manager is not a repository
> and it is successfully connecting to the repository, but when the repository
> tries to create the dynamic channel back to the remote queue manager, it is
> failing because it is using the wrong port. It would be nice if it was smart
> enough to use the port that the inbound connection used to come in on for
> it's connection back. I suppose I could manually define the channel, but
> wasn't sure if I should.
>
> Arlen Williams
> EDS
>
> -Original Message-
> From: Peter Uranyi [mailto:[EMAIL PROTECTED]
> Sent: Saturday, January 31, 2004 12:05 PM
> To: [EMAIL PROTECTED]
> Subject: Re: How to Specify Ethernet Adapter
>
>
> Arlen,
>
> For outbound communications you can use the LOCLADDR attribute of the sender
> channel to specify the IP address, and optionally the port(s) to use.
>
> For inbound communications start the listener with the -i switch and specify
> the IP address to listen on.
>
> Peter
>
> --- "Williams, Arlen" <[EMAIL PROTECTED]> wrote:
> > I have a 5.3 WMQ queue manager running on an AIX server that has 3
> > network adapters and so 3 different TCP/IP addresses. Because of a
> > firewall I need to force connections out of this server to go out one
> > specific adapter so the source TCP/IP address is the one the firewall
> > rules are expecting. Can I do that by configuring something in the
> > queue manager or is that something you have to do with a network
> > setting on AIX?
> >
> > Arlen Williams
> > EDS

Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at http://www.lsoft.com
Archive: http://vm.akh-wien.ac.at/MQSeries.archive


Re: How to Specify Ethernet Adapter

2004-01-31 Thread Peter Uranyi
Arlen,

For outbound communications you can use the LOCLADDR attribute of the sender
channel to specify the IP address, and optionally the port(s) to use.

For inbound communications start the listener with the -i switch and specify
the IP address to listen on.

Peter

--- "Williams, Arlen" <[EMAIL PROTECTED]> wrote:
> I have a 5.3 WMQ queue manager running on an AIX server that has 3 network
> adapters and so 3 different TCP/IP addresses. Because of a firewall I need
> to force connections out of this server to go out one specific adapter so
> the source TCP/IP address is the one the firewall rules are expecting. Can I
> do that by configuring something in the queue manager or is that something
> you have to do with a network setting on AIX?
>
> Arlen Williams
> EDS
>
> Instructions for managing your mailing list subscription are provided in
> the Listserv General Users Guide available at http://www.lsoft.com
> Archive: http://vm.akh-wien.ac.at/MQSeries.archive

Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at http://www.lsoft.com
Archive: http://vm.akh-wien.ac.at/MQSeries.archive


Re: Antwort: Enabling large queues

2004-01-28 Thread Peter Uranyi
Roland,

Thanks for your help.  This is exactly what I had to do.

Peter

--- Roland Duenki <[EMAIL PROTECTED]> wrote:
> Hi,
> I made a test with MQ 5.3 on AIX just a few days ago: 26Gigs i a queue
> mith 1MB messages.
>
> Here's the trick:
> There is a filesize-limit for every user! To check it, enter "ulimit
> -a" with your mqm user.
> There will be a line like "file(blocks) unlimited".
> If this is not "unlimited", then thats probably the reason for your
> problem.
> Im no expert how to set this. But try this:
> smit user -> show/change Charakteristics of a user -> mqm -> soft File
> Size = -1
>
> The rest you already have:
> - Large file support is enabled
> - The logfiles can hold all uncommitted messages - You commit every
> message
>
> There was no need to set any ini-file-stanzas!
>
> Roland
>
>
>
>
>   Peter Uranyi
>   <[EMAIL PROTECTED]An:
> [EMAIL PROTECTED]
>   M>   Kopie:
>   Gesendet von:Thema:Enabling large
> queues
>   MQSeries List
>   <[EMAIL PROTECTED]
>   n.AC.AT>
>
>
>   27.01.04 20:54
>   Bitte antworten
>   an MQSeries List
>
>
>
>
> According to the MQ docs "WebSphere MQ Version 5.3 supports queues
> larger than
> 2 GB."  I wanted to try this, but my queue file refuses to grow even
> past 1 GB.
>
> I am running MQ 5.3 CSD05 on AIX 5.1.  I created the queue manager and
> the
> queue on a 10 GB filesystem that even has large file support enabled.
> I am putting 100 MB messages on the queue, but I can only put 10 of
> these
> messages successfully.
> The 11th message fails with MQRC 2056 - MQRC_Q_SPACE_NOT_AVAILABLE.
>
> Obviously space is not a problem, the filesystem is only 13% full.
>
> What am I doing wrong?
> Thanks.
> Peter

Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at http://www.lsoft.com
Archive: http://vm.akh-wien.ac.at/MQSeries.archive


Enabling large queues - solved

2004-01-27 Thread Peter Uranyi
Thanks to everyone who responded.  You nice people didn't want to insult me by
asking whether I remembered Rule #1 in troubleshooting: check the error logs.
Finally I did remember to take a look at the /var/mqm/errors directory and to
my surprise I found some FDC files and their corresponding entries in the
errorlog.
The errors indicated that at the real reason for the mqrc 2056 was that MQ
received a RC=27 from the OS.  This means: "A file cannot be larger than the
value set by ulimit."
Suddenly the light came on!  The default ulimit for files is 2097151 on AIX,
which is 1GB.  After setting the ulimit to -1 (unlimited) for the mqm user (in
the /etc/security/limits file) and restarting the qmgr, everything worked.

So, the documentation was correct after all:  MQ 5.3 does support queue files
greater than 2GB.  And it does so without any special tuning.
The TuningParameters/DefaultQFileSize setting is not needed anymore.
(I also found APAR IC27246, which states that the defaultqfilesize has been
increased to 2GB back in MQ 5.1)

All one needs to do is set the ulimit properly, and if the queue has to be able
to grow beyond 2GB then the filesystem should be created with large file
support enabled.

Thanks.
Peter

> -Original Message-----
> From: Peter Uranyi [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, January 27, 2004 2:54 PM
> To: [EMAIL PROTECTED]
> Subject: Enabling large queues
>
>
> According to the MQ docs "WebSphere MQ Version 5.3 supports queues larger
> than
> 2 GB."  I wanted to try this, but my queue file refuses to grow even past 1
> GB.
>
> I am running MQ 5.3 CSD05 on AIX 5.1.  I created the queue manager and the
> queue on a 10 GB filesystem that even has large file support enabled.
> I am putting 100 MB messages on the queue, but I can only put 10 of these
> messages successfully.
> The 11th message fails with MQRC 2056 - MQRC_Q_SPACE_NOT_AVAILABLE.
>
> Obviously space is not a problem, the filesystem is only 13% full.
>
> What am I doing wrong?
>
> Thanks.
> Peter

Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at http://www.lsoft.com
Archive: http://vm.akh-wien.ac.at/MQSeries.archive


Re: Enabling large queues

2004-01-27 Thread Peter Uranyi
Rick,

Thanks, I also found this, and tried it, but it didn't work.  Also, I think the
DefaultQFileSize parameter was only invented for MQ 5.0 to allow the size of
the queuefile to be increased from 320MB to 1GB.  Later versions of MQ
shouldn't need it (if the documentation is accurate.)

Peter

--- Rick Tsujimoto <[EMAIL PROTECTED]> wrote:
> Peter,
>
> Here's an old posting.  You can change the value to 2GB:
>
> Please respond to MQSeries List <[EMAIL PROTECTED]>
>
>
> Sent by:MQSeries List <[EMAIL PROTECTED]>
> To:   [EMAIL PROTECTED]
> cc:
> Subject:Re: Queue File Size
>
>
> Jay asked >>>
> I just can't remember, but I know on Unix that there was a max file size
> for a queue under a normal installation.
>
> Does anyone know what that is.
>
> I also seem to remember that there are stanzas I can put in the queue
> manager ini file that allows for a bigger file size.  I think these are
> undocumented.
>
> Does anyone know these also.
> <<<
>
> Some old notes I have state the default limit size for a queue file is
> 320M...to
> override this limit add the following to your qm.ini
>
> DefaultQFileSize =10
>
> Remember that any queue created before adding this to your qm.ini will be
> limited to the 320M so if you need the 1G
> limit you'll need to delete and redefine the queue after changing the
> qm.ini
>
> Marc Verhiel
> Candle Corp.
>
>
>
>
>   Peter Uranyi
>   <[EMAIL PROTECTED] To:
> [EMAIL PROTECTED]
>   OM>  cc:
>   Sent by: Subject: Re: Enabling large
> queues
>   MQSeries List
>   <[EMAIL PROTECTED]
>   en.AC.AT>
>
>
>   01/27/2004 03:54
>   PM
>   Please respond
>   to MQSeries List
>
>
>
>
>
> I have increased the log files to the max (16384 pages).  I was using the
> default 3 primary 2 secondary log setup, but I also do a commit after every
> message.  Also, I created another queue and put ten 100MB messages on that
> one
> without a problem.  So, now I have two 1GB queue files on the filesystem.
> Still, the 11th message fails.  Somehow I just can't go past the 1GB limit.
>
>
> --- "Potkay, Peter M (PLC, IT)" <[EMAIL PROTECTED]> wrote:
> > How big are your logs?
> >
> >
> >
> > -Original Message-
> > From: Peter Uranyi [mailto:[EMAIL PROTECTED]
> > Sent: Tuesday, January 27, 2004 2:54 PM
> > To: [EMAIL PROTECTED]
> > Subject: Enabling large queues
> >
> >
> > According to the MQ docs "WebSphere MQ Version 5.3 supports queues larger
> > than
> > 2 GB."  I wanted to try this, but my queue file refuses to grow even past
> 1
> > GB.
> >
> > I am running MQ 5.3 CSD05 on AIX 5.1.  I created the queue manager and
> the
> > queue on a 10 GB filesystem that even has large file support enabled.
> > I am putting 100 MB messages on the queue, but I can only put 10 of these
> > messages successfully.
> > The 11th message fails with MQRC 2056 - MQRC_Q_SPACE_NOT_AVAILABLE.
> >
> > Obviously space is not a problem, the filesystem is only 13% full.
> >
> > What am I doing wrong?
> >
> > Thanks.
> > Peter
> >
> > Instructions for managing your mailing list subscription are provided in
> > the Listserv General Users Guide available at http://www.lsoft.com
> > Archive: http://vm.akh-wien.ac.at/MQSeries.archive
> >
> >
> > This communication, including attachments, is for the exclusive use of
> > addressee and may contain proprietary, confidential or privileged
> > information. If you are not the intended recipient, any use, copying,
> > disclosure, dissemination or distribution is strictly prohibited. If
> > you are not the intended recipient, please notify the sender
> > immediately by return email and delete this communication and destroy all
> > copies.
> >
> > Instructions for managing your mailing list subscription are provided in
> > the Listserv General Users Guide available at http://www.lsoft.com
> > Archive: http://vm.akh-wien.ac.at/MQSeries.archive
>
> Instructions for managing your mailing list subscription are provided in
> the Listserv General Users Guide available at http://www.lsoft.com
> Archive: http://vm.akh-wien.ac.at/MQSeries.archive
>
> Instructions for managing your mailing list subscription are provided in
> the Listserv General Users Guide available at http://www.lsoft.com
> Archive: http://vm.akh-wien.ac.at/MQSeries.archive

Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at http://www.lsoft.com
Archive: http://vm.akh-wien.ac.at/MQSeries.archive


Re: Enabling large queues

2004-01-27 Thread Peter Uranyi
Christopher,

> I believe the default limit size for a queue file is now 1GB. To override
> this limit add the following to your qm.ini TuningParameters stanza:
>
> DefaultQFileSize = 20
>
> This should increase the queue file size to around 2GB (or whatever value
> you specified).
>
> If you've already created your queue then I believe you will have to delete
> and redefine the queue after making this change, as this will not change
> the default queue file size for an existing queue.

Unfortunately I tried this too and it didn't work.  Here are the exact steps I
took:
- deleted the qmgr
- created a new qmgr
- added the following to my qm.ini (pasted here from the actual ini file):
TuningParameters:
   DefaultQFileSize=20
- started the qmgr
- altered the qmgr to allow 100MB messages
- created a queue w/ maxmsgl 100MB
- started putting 100MB messages on it
- only 10 made it, the 11th one failed

Why would the manual say that MQ now supports greater than 2GB files, if it
can't even get past 1GB?

Thanks.
Peter

Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at http://www.lsoft.com
Archive: http://vm.akh-wien.ac.at/MQSeries.archive


Re: Enabling large queues

2004-01-27 Thread Peter Uranyi
That could very well be, but why can't I reach that 2 gig on the drive?  I am
only half way there when I get stopped.

--- Robert Broderick <[EMAIL PROTECTED]> wrote:
> I thought it was 2 gig in the buffer and 2 gig on the actual drive???
> NO?????
>
>
> >From: Peter Uranyi <[EMAIL PROTECTED]>
> >Reply-To: MQSeries List <[EMAIL PROTECTED]>
> >To: [EMAIL PROTECTED]
> >Subject: Enabling large queues
> >Date: Tue, 27 Jan 2004 11:39:53 -0800
> >
> >According to the MQ docs "WebSphere MQ Version 5.3 supports queues larger
> >than
> >2 GB".  I wanted to try this, but my queue file refuse to grow beyond even
> >1
> >GB.
> >
> >I am running MQ 5.3 CSD05 on AIX 5.1.  I created a 10 GB filesystem with
> >large
> >file support enabled.  I created a queue manager and a queue on this
> >filesystem.
> >I am putting 100 MB messages on the queue, but I can only put 10 of these
> >messages successfully.
> >The 11th message fails with 2056 - MQRC_Q_SPACE_NOT_AVAILABLE.
> >
> >What am I doing wrong?
> >
> >Thanks in advance for any help.
> >Peter
> >
> >Instructions for managing your mailing list subscription are provided in
> >the Listserv General Users Guide available at http://www.lsoft.com
> >Archive: http://vm.akh-wien.ac.at/MQSeries.archive
>
> _
> Check out the coupons and bargains on MSN Offers!
> http://shopping.msn.com/softcontent/softcontent.aspx?scmId=1418
>
> Instructions for managing your mailing list subscription are provided in
> the Listserv General Users Guide available at http://www.lsoft.com
> Archive: http://vm.akh-wien.ac.at/MQSeries.archive

Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at http://www.lsoft.com
Archive: http://vm.akh-wien.ac.at/MQSeries.archive


Re: Enabling large queues

2004-01-27 Thread Peter Uranyi
I have increased the log files to the max (16384 pages).  I was using the
default 3 primary 2 secondary log setup, but I also do a commit after every
message.  Also, I created another queue and put ten 100MB messages on that one
without a problem.  So, now I have two 1GB queue files on the filesystem.
Still, the 11th message fails.  Somehow I just can't go past the 1GB limit.


--- "Potkay, Peter M (PLC, IT)" <[EMAIL PROTECTED]> wrote:
> How big are your logs?
>
>
>
> -Original Message-
> From: Peter Uranyi [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, January 27, 2004 2:54 PM
> To: [EMAIL PROTECTED]
> Subject: Enabling large queues
>
>
> According to the MQ docs "WebSphere MQ Version 5.3 supports queues larger
> than
> 2 GB."  I wanted to try this, but my queue file refuses to grow even past 1
> GB.
>
> I am running MQ 5.3 CSD05 on AIX 5.1.  I created the queue manager and the
> queue on a 10 GB filesystem that even has large file support enabled.
> I am putting 100 MB messages on the queue, but I can only put 10 of these
> messages successfully.
> The 11th message fails with MQRC 2056 - MQRC_Q_SPACE_NOT_AVAILABLE.
>
> Obviously space is not a problem, the filesystem is only 13% full.
>
> What am I doing wrong?
>
> Thanks.
> Peter
>
> Instructions for managing your mailing list subscription are provided in
> the Listserv General Users Guide available at http://www.lsoft.com
> Archive: http://vm.akh-wien.ac.at/MQSeries.archive
>
>
> This communication, including attachments, is for the exclusive use of
> addressee and may contain proprietary, confidential or privileged
> information. If you are not the intended recipient, any use, copying,
> disclosure, dissemination or distribution is strictly prohibited. If
> you are not the intended recipient, please notify the sender
> immediately by return email and delete this communication and destroy all
> copies.
>
> Instructions for managing your mailing list subscription are provided in
> the Listserv General Users Guide available at http://www.lsoft.com
> Archive: http://vm.akh-wien.ac.at/MQSeries.archive

Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at http://www.lsoft.com
Archive: http://vm.akh-wien.ac.at/MQSeries.archive


Enabling large queues

2004-01-27 Thread Peter Uranyi
According to the MQ docs "WebSphere MQ Version 5.3 supports queues larger than
2 GB."  I wanted to try this, but my queue file refuses to grow even past 1 GB.

I am running MQ 5.3 CSD05 on AIX 5.1.  I created the queue manager and the
queue on a 10 GB filesystem that even has large file support enabled.
I am putting 100 MB messages on the queue, but I can only put 10 of these
messages successfully.
The 11th message fails with MQRC 2056 - MQRC_Q_SPACE_NOT_AVAILABLE.

Obviously space is not a problem, the filesystem is only 13% full.

What am I doing wrong?

Thanks.
Peter

Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at http://www.lsoft.com
Archive: http://vm.akh-wien.ac.at/MQSeries.archive


Enabling large queues

2004-01-27 Thread Peter Uranyi
According to the MQ docs "WebSphere MQ Version 5.3 supports queues larger than
2 GB".  I wanted to try this, but my queue file refuse to grow beyond even 1
GB.

I am running MQ 5.3 CSD05 on AIX 5.1.  I created a 10 GB filesystem with large
file support enabled.  I created a queue manager and a queue on this
filesystem.
I am putting 100 MB messages on the queue, but I can only put 10 of these
messages successfully.
The 11th message fails with 2056 - MQRC_Q_SPACE_NOT_AVAILABLE.

What am I doing wrong?

Thanks in advance for any help.
Peter

Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at http://www.lsoft.com
Archive: http://vm.akh-wien.ac.at/MQSeries.archive


Re: A little Windows Scripting help in relation to MS03

2003-12-22 Thread Peter Uranyi
Peter,

Just add the following line before invoking saveqmgrc:

mkdir %BackupDir%\QM1_FOLDER >NUL 2>&1

This will create the directory if it doesn't exist.

Peter

--- "Potkay, Peter M (PLC, IT)" <[EMAIL PROTECTED]> wrote:
> This works 100%:
> SET BackupDir=.\QueueManagerBackups\
> REM
> SET MQSERVER=QM1.MS03.CHANNEL/TCP/MyServerName
> saveqmgrc -m QM1 -f %BackupDir%\QM1_BACKUP.txt -R
>
>
>
> This bombs because it can't find the folder called QM1_FOLDER (its not
> automatically created by the script)
> SET BackupDir=.\QueueManagerBackups\
> REM
> SET MQSERVER=QM1.MS03.CHANNEL/TCP/MyServerName
> saveqmgrc -m QM1 -f %BackupDir%\QM1_FOLDER\QM1_BACKUP.txt -R
>
>
> My goal is that this script will try and put the output of the command into
> a folder called ..\QueueManagerBackups\QM1_FOLDER\, and if the QM1_FOLDER
> folder does not exist, create it and then stick in there the file
> QM1_BACKUP.txt.
>
> Since this script runs everyday, the next day it should gracefully handle
> the fact that the QM1_FOLDER is there.
>
> Any tips on how to do this? What would I do to the following line to always
> create the named folder (in this case QM1_FOLDER) if it didn't exist?
> saveqmgrc -m QM1 -f %BackupDir%\QM1_FOLDER\QM1_BACKUP.txt -R
>
>
> (I have hundreds of entries, so I don't want to have to go into
> ..\QueueManagerBackups and have to manually create QM1_FOLDER . . .
> QM999_FOLDER).
>
>
>
> Peter Potkay
> MQSeries Specialist
> The Hartford Financial Services
> [EMAIL PROTECTED]
> x77906
> IBM MQSeries Certified
>
>
>
>
> This communication, including attachments, is for the exclusive use of
> addressee and may contain proprietary, confidential or privileged
> information. If you are not the intended recipient, any use, copying,
> disclosure, dissemination or distribution is strictly prohibited. If
> you are not the intended recipient, please notify the sender
> immediately by return email and delete this communication and destroy all
> copies.
>
> Instructions for managing your mailing list subscription are provided in
> the Listserv General Users Guide available at http://www.lsoft.com
> Archive: http://vm.akh-wien.ac.at/MQSeries.archive

Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at http://www.lsoft.com
Archive: http://vm.akh-wien.ac.at/MQSeries.archive


Re: Building an API exit on Solaris

2003-10-16 Thread Peter Uranyi
Tony,

If you haven't tried it yet, I would suggest to try and setup the sample API
exit.  First with the binary that IBM provided, then build your own exit from
the (unmodified) source.  This would prove that both the MQ configuration and
the compile/link process are correct.
Also, exits should be written in C, so I am not sure whether compiling it as a
C++ program does not cause any problems.
I would think that LD_LIBRARY_PATH does not have any effect here, since
/var/mqm/exits is the default directory for exits, and also you have specified
the full path.  Unfortunately I don't have access to a Solaris box, so I can't
try out what works and what doesn't.
Is the QM generating any FDC files?

Peter

--- Antony Boggis <[EMAIL PROTECTED]> wrote:
> Thank you.
>
> I tried that, and it did indeed generate a binary (smaller than my previous
> version!), but I still get the same error.
>
> Are there any issues with the value of LD_LIBRARY_PATH?
>
> tonyB.
>
> -Original Message-
> Sent: Thursday 10/16/2003 12:30:32 PM
> Subject: Re: Building an API exit on Solaris
>
> >Tony,
> >
> >Try something like this:
> >
> >CC -c -O -mt -KPIC mqAPIExit.cpp -o mqAPIExit.o
> >CC -G -mt -lmqmzf -lmqm -lmqmcs -lmqmzse mqAPIExit.o -o mqAPIExit.so
> >
> >HTH,
> >Peter
> >
> >--- Antony Boggis <[EMAIL PROTECTED]> wrote:
> >> I am trying to get MQ to run my API exit, written in C++ (it's a hacked
> >> version of the sample amqsaxe0.c). It works fine under Windows.
> >>
> >> I am using the following to build the .so file:
> >>
> >> CC -mt mqAPIExit.cpp -G -o mqAPIExit.so -lmqmzf -lmqm -lmqmcs -lmqmzse
> >>
> >> and no errors are generated, and the output is generated.
> >>
> >> I have added the following to qm.ini:
> >>
> >> ApiExitLocal:
> >>Sequence=100
> >>Function=EntryPoint
> >>Module=/var/mqm/exits/mqAPIExit.so
> >>Name=mqAPIExit
> >>Data=16
> >>
> >> But when I try to start the qmgr I get the following:
> >>
> >> [EMAIL PROTECTED]:/var/mqm/trace]$ strmqm TEST
> >> AMQ7214: The module '/var/mqm/exits/mqAPIExit.so' for Api Exit 'mqAPIExit'
> >> could not be loaded for reason xecU_S_LOAD_FAILED.
> >>
> >> I have tried running an early trace, but all the trace files give me is
> the
> >> same return code info, so I am suspecting that my build is not good.
> >>
> >> Any help/comments appreciated,
> >>
> >> Regards,
> >>
> >> tonyB.
> >>
> >> Instructions for managing your mailing list subscription are provided in
> >> the Listserv General Users Guide available at http://www.lsoft.com
> >> Archive: http://vm.akh-wien.ac.at/MQSeries.archive
> >
> >Instructions for managing your mailing list subscription are provided in
> >the Listserv General Users Guide available at http://www.lsoft.com
> >Archive: http://vm.akh-wien.ac.at/MQSeries.archive
>
> Instructions for managing your mailing list subscription are provided in
> the Listserv General Users Guide available at http://www.lsoft.com
> Archive: http://vm.akh-wien.ac.at/MQSeries.archive

Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at http://www.lsoft.com
Archive: http://vm.akh-wien.ac.at/MQSeries.archive


Re: Building an API exit on Solaris

2003-10-16 Thread Peter Uranyi
Tony,

Try something like this:

CC -c -O -mt -KPIC mqAPIExit.cpp -o mqAPIExit.o
CC -G -mt -lmqmzf -lmqm -lmqmcs -lmqmzse mqAPIExit.o -o mqAPIExit.so

HTH,
Peter

--- Antony Boggis <[EMAIL PROTECTED]> wrote:
> I am trying to get MQ to run my API exit, written in C++ (it's a hacked
> version of the sample amqsaxe0.c). It works fine under Windows.
>
> I am using the following to build the .so file:
>
> CC -mt mqAPIExit.cpp -G -o mqAPIExit.so -lmqmzf -lmqm -lmqmcs -lmqmzse
>
> and no errors are generated, and the output is generated.
>
> I have added the following to qm.ini:
>
> ApiExitLocal:
>Sequence=100
>Function=EntryPoint
>Module=/var/mqm/exits/mqAPIExit.so
>Name=mqAPIExit
>Data=16
>
> But when I try to start the qmgr I get the following:
>
> [EMAIL PROTECTED]:/var/mqm/trace]$ strmqm TEST
> AMQ7214: The module '/var/mqm/exits/mqAPIExit.so' for Api Exit 'mqAPIExit'
> could not be loaded for reason xecU_S_LOAD_FAILED.
>
> I have tried running an early trace, but all the trace files give me is the
> same return code info, so I am suspecting that my build is not good.
>
> Any help/comments appreciated,
>
> Regards,
>
> tonyB.
>
> Instructions for managing your mailing list subscription are provided in
> the Listserv General Users Guide available at http://www.lsoft.com
> Archive: http://vm.akh-wien.ac.at/MQSeries.archive

Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at http://www.lsoft.com
Archive: http://vm.akh-wien.ac.at/MQSeries.archive


Re: AW: Antwort: AMQ4128 ??

2003-10-14 Thread Peter Uranyi
Michael,

Instead of 'strmqm' and 'endmqm' you should use:
'amqmdain start QMgrName' and 'amqmdain end QMgrName'

It appears, the problem is that 'strmqm' starts a channel initiator (just like
on Unix), but this is not the one defined in MQServices.  Consequently, the
initiator defined in MQServices will fail.
On the other hand, 'amqmdain' is a command-line interface to MQServices, so it
will start the channel initiator defined there.  As an added benefit, it will
also start your command-server, listener, and any trigger monitors you have
defined in MQServices.

Peter

--- "Fleck, Michael" <[EMAIL PROTECTED]> wrote:
> Hi Roland,
>
> I have deleted the channel initiator and rebooted the server. The channel
> initiator was created and is running.
> But our problem is a different one. We want to stop the Queue Manager with
> "endmqm" from a scheduler on a regular basis to do backups of the MQ -
> directories. After this we want to start the Queue Manager again.
>
> So I stopped the Queue Manager again before doing my backups. After this the
> channel initiator doesn't start again with "strmqm". If I try to do this
> manually, the AMQ4128 appears again.
>
> Any ideas how to stop and start the queue manager on a regular basis?
>
> Best regards,
> Michael
>
> -Urspr|ngliche Nachricht-
> Von: Roland Duenki [mailto:[EMAIL PROTECTED]
> Gesendet: Freitag, 10. Oktober 2003 15:49
> An: [EMAIL PROTECTED]
> Betreff: Antwort: AMQ4128 ??
>
> Hi,
>
> Sometimes, the channel initiator is running but it is not shown in in the mq
> services tool. (It usually happens to me right after creating a new qmgr.) If
> you add a new channel initiator by using this tool under this circumstances,
> then the tool gets confused by the already existing channel initiator. by
> trying to start the same initiator again, you get rc=20.
>
> To correct the mq services entries, do this: delete the channelinitiator
> entry. reboot. check your tool again. when initiator is back again:
> everything ok. if not. add it and start it.
>
> Roland
>
>
>
>
> Hi list members,
> I stopped a queue manager from the commandline using "endmqm -i qmgr". After
> this I started it again using "strmqm qmgr". Everything seems to be fine, but
> when I looked at the Mq-Services Utility I saw that the Channel Initiator was
> still stopped. When I try to start it manually I get Error AMQ4128 with
> rc=20. Any ideas?
>
> Instructions for managing your mailing list subscription are provided in
> the Listserv General Users Guide available at http://www.lsoft.com
> Archive: http://vm.akh-wien.ac.at/MQSeries.archive

Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at http://www.lsoft.com
Archive: http://vm.akh-wien.ac.at/MQSeries.archive


Re: Max Channels

2003-10-09 Thread Peter Uranyi
Paul,

Maybe I don't need to know about the parameters, but it would be useful to know
the maximum number of threads running in each channel pool process, (and also
in the agent processes as well.)
If I remember correctly, the amqzlaa0 process used to be single-threaded in
5.2, but now in 5.3 it looks like it is multi-threaded.
What I would like to find out is that for a given number of client connections,
how many amqzlaa0 and amqrmppa processes are created. (MQ 5.3 CSD04 for AIX).

Thanks In Advance,
Peter

--- Paul Clarke <[EMAIL PROTECTED]> wrote:
> MaxChannels and MaxActiveChannels are global parameters. They specify the
> maximum values regardless of how many listeners you have running or indeed
> use inetd. There is no MQ parameter which limits the number that can
> connect to a single listener.  In 5.3 you can have a single listener to
> handle all your inbound channels regardless of how many there are. In this
> case the connection is farmed out to a pool of channel processes. There are
> parameters to control how many are farmed out to each process but we don't
> document them 'cos in general you don't need to know.
>
> Cheers,
> P.
>
> Paul G Clarke
> WebSphere MQ Development
> IBM Hursley
>
>
>
>
>
>   Ruzi R
>   <[EMAIL PROTECTED]To:
> [EMAIL PROTECTED]
>   M>   cc:
>   Sent by: MQSeriesSubject:  Re: Max Channels
>   List
>   <[EMAIL PROTECTED]
>   N.AC.AT>
>
>
>   07/10/2003 13:26
>   Please respond to
>   MQSeries List
>
>
>
>
>
> Sid,
>
> >if you run 5
> > listners and you have MaxChannels set to 1000 does
> > that mean there are 5000
> > channels available (assuming server is capable of
> > handling that many in
> > bound connections).
>
> I believe (someone will correct me if I am wrong) the
> numbers that are set for   MAxChannels and
> MAxActiveChannels are for a single port. So, in your
> example, you will have max 5000 channels.
>
> Best regards,
>
> Ruzi
>
> --- [EMAIL PROTECTED] wrote:
> > Howdy again,
> >
> > Does each listener contribute to the total
> > MaxChannels value or if you run 5
> > listners and you have MaxChannels set to 1000 does
> > that mean there are 5000
> > channels available (assuming server is capable of
> > handling that many in
> > bound connections).
> >
> > Thanks
> >
> > Sid
> >
> >
> >
> > -Original Message-
> > From: Ruzi R [mailto:[EMAIL PROTECTED]
> > Sent: Monday, 6 October 2003 8:55 PM
> > To: [EMAIL PROTECTED]
> > Subject: Re: Max Channels
> >
> >
> > MaxActiveChannel needs to be at least 2500 (assuming
> > the server can handle this many connections).
> >
> > Best regards,
> >
> > Ruzi
> > --- [EMAIL PROTECTED] wrote:
> > > G'Day all,
> > >
> > > I have about 500 clients all trying to connect at
> > > about the same time and
> > > transfer data from one of my MQ server (NT4
> > mqv5.1),
> > > each client is running
> > > 5 threads with their own connection, so my
> > question
> > > is this.
> > >
> > > Is 500 clients and 5 threads each = 2500
> > > connections?
> > > Does Max Channel need to be at least 2500 ?
> > >
> > >
> > > Sid
> > >
> > > Instructions for managing your mailing list
> > > subscription are provided in
> > > the Listserv General Users Guide available at
> > http://www.lsoft.com
> > > Archive: http://vm.akh-wien.ac.at/MQSeries.archive
> >
> > Instructions for managing your mailing list
> > subscription are provided in the
> > Listserv General Users Guide available at
> > http://www.lsoft.com
> > Archive: http://vm.akh-wien.ac.at/MQSeries.archive
> >
> > Instructions for managing your mailing list
> > subscription are provided in
> > the Listserv General Users Guide available at
> > http://www.lsoft.com
> > Archive: http://vm.akh-wien.ac.at/MQSeries.archive
>
> Instructions for managing your mailing list subscription are provided in
> the Listserv General Users Guide available at http://www.lsoft.com
> Archive: http://vm.akh-wien.ac.at/MQSeries.archive
>
> Instructions for managing your mailing list subscription are provided in
> the Listserv General Users Guide available at http://www.lsoft.com
> Archive: http://vm.akh-wien.ac.at/MQSeries.archive

Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at http://www.lsoft.com
Archive: http://vm.akh-wien.ac.at/MQSeries.archive


Re: Solaris version of SupportPac MS03

2003-09-06 Thread Peter Uranyi
T.Rob,

I would be interested in a version of saveqmgr that uses MQCONNX.  Channel
tables and/or environment variables are good for static applications that
always connect to the same queue manager.  But I think utility programs need to
be more flexible and should use MQCONNX instead.
I think the best solution would be to ask Wayne to include these changes in the
next version of saveqmgr.  This way you won't need to patch the source every
time a new version comes out.

Peter


--- "Wyatt, T. Rob" <[EMAIL PROTECTED]> wrote:
> Peter,
>
> When I first tried to get that version, IBM was still serving the old one.
> Wayne Schutz and I exchanged emails and he got them to move the new code
> into the repository a few days ago.  If anyone has what they think is the
> latest version but it does not have the Windows client executable, they
> should download it again.
>
> Wayne's version of the client program is the same saveqmgr code but linked
> with the client libraries.  If you change lmqm to lmqic in the makefile, you
> can build the client executable for any of the listed platforms.  I liked
> the MQCONNX approach better because it doesn't need environment variables or
> a channel table.  I pulled that code out of the CONNX sample program and
> patched it into the latest saveqmgr.  It takes the SVRCONN channel name and
> IP address as additional command line parameters.  I've compiled it for
> Solaris and will be happy to make it and the source code available if anyone
> wants it.
>
> -- T.Rob
>
> -Original Message-
> From: Potkay, Peter M (PLC, IT) [mailto:[EMAIL PROTECTED]
> Sent: Thursday, September 04, 2003 8:30 PM
> To: [EMAIL PROTECTED]
> Subject: Re: Solaris version of SupportPac MS03
>
>
> FYI, there was a new version of the MS03 Support Pack just put out a couple
> weeks ago.
> http://www-3.ibm.com/software/integration/support/supportpacs/individual/ms0
> 3.html
>
> Below is a cut-n-paste of what is new. Most notably, there is now a Windows
> Client executable included, which I am using succesfully.
>
> The following changes have been made in this release:
> minor 'readme' documentation fixes
> allowance for missed reply messages when pcf error messages are received and
> -i is specified
> all references updated from MQSeries to WebSphere MQ
> where possible, the name of the object associated with the PCF error is
> printed
> RetCode is set to WARNING, if a damaged object is found and -i was specified
>
> the message 'xxx definitions written' has been changed to 'writing xxx
> definitions', to illustrate exactly when the message is being produced
> version number added on command line
> a Win-Client version (saveqmgrc) has been included
> improved iSeries support - see AS400READ.ME file for details.
>
> -Original Message-
> From: Wyatt, T. Rob [mailto:[EMAIL PROTECTED]
> Sent: Thursday, September 04, 2003 7:02 PM
> To: [EMAIL PROTECTED]
> Subject: Re: Solaris version of SupportPac MS03
>
>
> I have it for 5.3 CSD04 Solaris 2.8.  Will email directly to you.
>
> -- T.Rob
>
> -Original Message-
> From: Antony Boggis [mailto:[EMAIL PROTECTED]
> Sent: Thursday, September 04, 2003 6:41 PM
> To: [EMAIL PROTECTED]
> Subject: Solaris version of SupportPac MS03
>
>
> Does anyone have available the Solaris version of the latest (or recent)
> version of SupportPac ms03?
>
> Could someone e-m me a copy. The compiler is not installed on any system I
> currently have access to, so I can't build it myself.
>
> Thanks,
>
> tonyB.
>
> Instructions for managing your mailing list subscription are provided in
> the Listserv General Users Guide available at http://www.lsoft.com
> Archive: http://vm.akh-wien.ac.at/MQSeries.archive
>
> Instructions for managing your mailing list subscription are provided in
> the Listserv General Users Guide available at http://www.lsoft.com
> Archive: http://vm.akh-wien.ac.at/MQSeries.archive
>
>
> This communication, including attachments, is for the exclusive use of
> addressee and may contain proprietary, confidential or privileged
> information. If you are not the intended recipient, any use, copying,
> disclosure, dissemination or distribution is strictly prohibited. If
> you are not the intended recipient, please notify the sender
> immediately by return email and delete this communication and destroy all
> copies.
>
> Instructions for managing your mailing list subscription are provided in
> the Listserv General Users Guide available at http://www.lsoft.com
> Archive: http://vm.akh-wien.ac.at/MQSeries.archive
>
> Instructions for managing your mailing list subscription are provided in
> the Listserv General Users Guide available at http://www.lsoft.com
> Archive: http://vm.akh-wien.ac.at/MQSeries.archive

Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at http://www.lsoft.com
Archive: http://vm.akh-wien.ac.at/MQSeries.archive


Re: make file for HP-UX?

2003-07-24 Thread Peter Uranyi
Rick,

SupportPac MS03 (saveqmgr) comes with makefiles for different platforms,
including HP-UX.  If you can build saveqmgr successfully, then you can use that
makefile as a starting point.

--- Rick Tsujimoto <[EMAIL PROTECTED]> wrote:
> I need to build a C program on HP-UX and I try to use a makefile one from
> AIX and it didn't work.  Could some kind soul out there please send me a
> makefile to build a simple C program, such as amqsget?

Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at http://www.lsoft.com
Archive: http://vm.akh-wien.ac.at/MQSeries.archive


Re: WANTED: Planning Guide

2003-07-23 Thread Peter Uranyi
Stefan,
You can find it on this page:

http://www-3.ibm.com/software/integration/mqfamily/library/manualsa/manuals/crossprev.html



--- Stefan Sievert <[EMAIL PROTECTED]> wrote:
> Hi y'all,
> does anybody know what happened to the MQSeries - ahem - WebSphere MQ
> Planning Guide?
> It had this nice table at the end which had the functional comparison
> between platforms and I don't seem to be able to find it for the latest MQ
> release.
> Ideas? Hursley?
> Stefan
>
> _
> The new MSN 8: smart spam protection and 2 months FREE*
> http://join.msn.com/?page=features/junkmail
>
> Instructions for managing your mailing list subscription are provided in
> the Listserv General Users Guide available at http://www.lsoft.com
> Archive: http://vm.akh-wien.ac.at/MQSeries.archive

Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at http://www.lsoft.com
Archive: http://vm.akh-wien.ac.at/MQSeries.archive


Re: Using MS03, how do I capture its errors to a file?

2003-07-21 Thread Peter Uranyi
It is just bad coding :-)  You can have both stdin & stderr go to the same
file on Windows too.  In general, you would type:

saveqmgr -m QueueManagerName -f MyOutputfile.txt -R  >log.log 2>&1
(to write to log.log)

saveqmgr -m QueueManagerName -f MyOutputfile.txt -R  >>log.log 2>>&1
(to append to log.log if it exists)

This works on both Unix and Windows.

But saveqmgr writes all messages to stderr, so you could just type:

saveqmgr -m QueueManagerName -f MyOutputfile.txt -R  2>log.log

That's because you can use the -c option (instead of -f) to write all MQ
definitions to stdout.  So, you would get the same results if you type:

saveqmgr -m QueueManagerName -c -R >MyOutputfile.txt 2>log.log

HTH,
Peter

--- Roger Lacroix <[EMAIL PROTECTED]> wrote:
> Hi,
>
> Of course, Windows has to add a twist on that idea (or maybe its a bug or
> just bad coding ).
>
> On Windows NT/2000, you CANNOT have both stdin & stderr go to the same
> file.  If you do the following command:
> saveqmgr -m QueueManagerName -f MyOutputfile.txt -R  >>log.log 2>>log.log
>
> or
>
> saveqmgr -m QueueManagerName -f MyOutputfile.txt -R  1>>log.log 2>>log.log
>
> The Windows command processor will open the stdout but closes the file when
> it sees that stderr goes to the same file. In other words, only the last
> redirect will be used if the same file name is used on both redirects.
>
> It is better to do (on Windows that is) the following:
> saveqmgr -m QueueManagerName -f MyOutputfile.txt -R  1>>ok.log 2>>error.log
>
>
> later
> Roger...
>
>
> At 09:47 PM 7/20/2003, you wrote:
> >Peter,
> >
> >On unix platforms, I always run it in a batch file with 'LOG=logfilename'
> >and then specify those commands with output to >>$LOG and 2>>$LOG (i.e
> >saveqmgr -m QueueManagerName -f MyOutputfile.txt -R >>$LOG 2>>$LOG).
> >Everything should be under the logfile incluing errors.
> >
> >Cheers,
> >
> >Ian
> >
> >-Original Message-
> >From: Potkay, Peter M (PLC, IT) [mailto:[EMAIL PROTECTED]
> >Sent: Saturday, 19 July 2003 6:31 AM
> >To: [EMAIL PROTECTED]
> >Subject: Using MS03, how do I capture its errors to a file?
> >
> >
> >saveqmgr -m QueueManagerName -f MyOutputfile.txt -R
> >
> >This is the command that I run from a bat file to back up my QM. If MS03
> >works, then MyOutputfile.txt has the stuff I need to use runmqsc.
> >
> >But if MS03 has a problem (maybe the QM is down, or the Command Server is
> >down, etc), it simply hangs for a few seconds, throws an error to the
> >screen, and does not produce any text file at all.
> >
> >This is a problem since I want to be able to look at a server and see after
> >the fact what the problem was.
> >
> >Is there any way to capture in a text file the data that MS03 throws out to
> >the screen?
> >
> >
> >
> >
> >
> >Peter Potkay
> >MQSeries Specialist
> >The Hartford Financial Services
> >[EMAIL PROTECTED]
> >x77906
> >IBM MQSeries Certified
> >
> >
> >
> >
> >This communication, including attachments, is for the exclusive use of
> >addressee and may contain proprietary, confidential or privileged
> >information. If you are not the intended recipient, any use, copying,
> >disclosure, dissemination or distribution is strictly prohibited. If
> >you are not the intended recipient, please notify the sender
> >immediately by return email and delete this communication and destroy all
> >copies.
> >
> >Instructions for managing your mailing list subscription are provided in
> >the Listserv General Users Guide available at http://www.lsoft.com
> >Archive: http://vm.akh-wien.ac.at/MQSeries.archive
> >
> >Instructions for managing your mailing list subscription are provided in
> >the Listserv General Users Guide available at http://www.lsoft.com
> >Archive: http://vm.akh-wien.ac.at/MQSeries.archive
>
> Instructions for managing your mailing list subscription are provided in
> the Listserv General Users Guide available at http://www.lsoft.com
> Archive: http://vm.akh-wien.ac.at/MQSeries.archive

Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at http://www.lsoft.com
Archive: http://vm.akh-wien.ac.at/MQSeries.archive


Re: Applying HIPER PTF on AIX for CSD03...

2003-07-08 Thread Peter Uranyi
Brian,

Try using the -x flag with the 'fuser' command, like this:

   fuser -fux libimqb23ia_r.a

HTH,
Peter


--- "McCarty, Brian" <[EMAIL PROTECTED]> wrote:
> I commented out listener and port entries in inetd.conf and services and
> refreshed inetd.conf.  There are no memory segments showing up with ipcs -a |
> grep mqm and I am executing slibclean.  I am still getting cannot open or
> remove a file containing a running program.
>
> I tried using fuser -fu libimqb23ia_r.a but it only returns this to the
> command line:
>
> libimqb23ia_r.a:
>
> Is there any other options or tools I can use here?  Thanks for all the help,
>
> Brian
>
>  -Original Message-
> From:   Stephan C. Moen [mailto:[EMAIL PROTECTED]
> Sent:   Tuesday, July 08, 2003 11:28 AM
> To: [EMAIL PROTECTED]
> Subject: Re: Applying HIPER PTF on AIX for CSD03...
>
> Use the 'fuser -fu ' command to display the process Ids that have
> this file open.
>
> Steve Moen
>
> -Original Message-
> From: MQSeries List [mailto:[EMAIL PROTECTED] Behalf Of McCarty,
> Brian
> Sent: Tuesday, July 08, 2003 11:00 AM
> To: [EMAIL PROTECTED]
> Subject: Applying HIPER PTF on AIX for CSD03...
>
> There is a HIPER fix out called IY43610 that I am trying to apply on AIX
> 4.3.3 running WMQ 5.3 CSD03.  I stopped the queue managers and used ipcrm
> and slibclean before trying to copy the files.  I was able to move 6 of the
> files (logged in as root), but I can't get 2 of them to copy.
>
> cp: ./libimqb23ia_r.a: Cannot open or remove a file containing a running
> program.
> cp: ./libimqs23ia_r.a: Cannot open or remove a file containing a running
> program.
>
> Does anyone have any idea why these files are still being used or if there
> is a tool or process that I can use to figure it out?
>
> Thanks for any advice in advance,
>
> Brian M. McCarty
> USAA, Senior Systems Programmer
> 210.913.1678
> MQ/WMQI Specialist/Solutions Expert
> e-business Solution Advisor/Designer/Technologist
>
> Instructions for managing your mailing list subscription are provided in
> the Listserv General Users Guide available at http://www.lsoft.com
> Archive: http://vm.akh-wien.ac.at/MQSeries.archive
> ___
> This message was content-scanned by GatewayDefender
> 7/8/2003 - 12:12:02 PM - BA045ecefc.0001.mml
>
> Instructions for managing your mailing list subscription are provided in
> the Listserv General Users Guide available at http://www.lsoft.com
> Archive: http://vm.akh-wien.ac.at/MQSeries.archive
>
> Instructions for managing your mailing list subscription are provided in
> the Listserv General Users Guide available at http://www.lsoft.com
> Archive: http://vm.akh-wien.ac.at/MQSeries.archive

Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at http://www.lsoft.com
Archive: http://vm.akh-wien.ac.at/MQSeries.archive


Re: Weird triggering problem

2003-07-05 Thread Peter Uranyi
Roger,

First to answer your question about "Why...?" see the following section from
the on-line help under "Custom Services":

"The programs started by this means run under the same user account as
the WebSphere MQ Service itself, namely MUSR_MQADMIN. This allows
them to be run when Windows is booted, without needing a user to be
logged on. Note therefore that you should not start any program that
runs a visible user interface under the account that started it, as it
will not be visible to you the currently logged on user, and
interaction with it will not be possible."

The same applies to other services like the trigger monitor as well.  This is a
Windows feature, and it has nothing to do with triggering.

But you can do the following.  (It worked on XP, but it should work on W2K
too):

- Stop all MQSeries processes
- Create a new user, for example: "mqadmin"
- Setup this ID like MUSR_MQADMIN.  The easiest way to do this is with the
following command:

   amqmsrvn -user  -password 

This will set the proper user-rights and group memberships for the id.
(I also found that it is useful to put this id in the local Administrators
group while experimenting.  This is just to avoid logging on and off.)

Instead of creating a new user, you can just change the MUSR_MQADMIN's
password, so you can login with that id.

- Reconfigure the DCOM server:
  Run dcomcnfg.exe, select "IBM MQSeries Services", "Properties".
  On the "Identity" tab select "The interactive user"

- Logoff and logon with the mqadmin id
- Start up MQSeries
- Verify in Task Manager that the mq processes are running under your login id
- Now if you trigger Notepad it will run in the foreground.

In the DCOM config step above, you could also select "The launching user" on
the "Identity" tab.  But in this case you have to make sure that you start the
Queue Manager from one of the MMC snap-ins (MQExplorer or MQServices) and NOT
from the Windows Services applet.

The only problem with these options is that if you logoff the Queue Manager
will stop :-(  But then again, if you are not logged on why would you want to
run a GUI app?

To reset everything the way it was just run: amqmjpse -r

I think that overall a much better solution would be to use The Client Trigger
Monitor Service, (SupportPac MA7K).  Just make sure that the service runs under
the Local System account, and the "Allow service to interact with desktop" box
is checked.  This way the Queue Manager runs as a service, so it won't stop
when you log off, and any user who logs on can trigger the GUI app.

HTH,
Peter


--- Roger Lacroix <[EMAIL PROTECTED]> wrote:
> All,
>
> I am having a problem with triggering from the "Trigger Monitor as a
> Service".  I need to launch a GUI Windows program on a Windows 2000 box
> using WMQ v5.3 CSD3.
>
> No matter what I do, I cannot trigger my GUI Windows application (and I am
> no novice).  So I thought I would do a basic test and launch notepad.  In
> the process definition, I set the AppID to "start C:\WinNT\notepad.exe"
>
> I created the Trigger Monitor service and used a blank as the initiation
> queue name (this defaults to SYSTEM.DEFAULT.INITIATION.QUEUE).
>
> So put a message on the triggering queue nothing happens.  I cleared the
> queue and tried it several times - nothing.
>
> So I stopped the Trigger Monitor service, open a Command Prompt and typed
> runmqtrm.exe (no parameters specified!!).  I put a message on the
> triggering queue (same queue) and viola, notepad appeared.  (I did not
> change any of the queue or process definitions).
>
> So, I stopped runmqtrm at the Command Prompt (closed notepad), started the
> Service Trigger Monitor and put a message on the triggering queue - nothing
> again
>
> After using IBM's name in vain, I checked the Windows Task Manager. Under
> the "Applications" tab, it was normal looking but under the "Processes" tab
> it showed that I had 5 notepad programs running. I also noticed several
> copies of my missing program that I did not think was started.
>
> So I looked at my Taskbar and also pressed Alt-Tab, there were no notepad
> programs (or my GUI appl.).  If I try to kill them, I get "Access denied".
> The only way to get rid of them is by rebooting.
>
> I looked in the manuals but I don't see any restrictions about launching
> GUI applications from the Service Trigger Monitor.
>
> Obviously the simple solution is to run the trigger monitor from the
> Command Prompt but WHY.  Why can't Trigger Monitor as a Service
> successfully start a Windows GUI application? (i.e. AppID set to "start
> C:\WinNT\notepad.exe")
>
> Anybody got any ideas?
>
> later
> Roger...
>

Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at http://www.lsoft.com
Archive: http://vm.akh-wien.ac.at/MQSeries.archive


Re: MQ V5.1 CSD06 for Solaris

2003-06-01 Thread Peter Uranyi
You can download it from here:

ftp://ftp.software.ibm.com/software/mqseries/fixes/solaris51/U471246/

Peter

--- listname ANONYMOUS postings DIGests <[EMAIL PROTECTED]> wrote:
> I am in desperate need for CSD06 for V5.1 running on Solaris.  Does anyone
> have a copy of this CSD that they could send to me?
>
> Thank You,
>
> John Haraburda
> TPS/ITS/Database Technologies Group
> MQSeries
> Office : 412-762-8548

Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at http://www.lsoft.com
Archive: http://vm.akh-wien.ac.at/MQSeries.archive


Re: WMQ 5.3 on Linux RedHat 7.3

2003-04-04 Thread Peter Uranyi
Andrew,
Because of the way threads are implemented in Linux, each new thread will show
up as a separate process.  So, what you see are actually just threads of the
same process.

You can find a lot of info about this on the Internet.  For example, here is an
explanation from Linus Torvalds on the advantages of this implementation:

http://www.ussg.iu.edu/hypermail/linux/kernel/9608/0191.html

Peter

--- Andrew Gardner <[EMAIL PROTECTED]> wrote:
> Hi all,
>
> I've just recently installed WMQ 5.3 on Linux for the first time:-  weusually
> run WMQ on AIX. I'm surprised the see the large number of WMQ processes under
> Linux compared to those under AIX. (The display below is from pstree(1)
> because
> it's compact):
>
> Under AIX:
>
>  |--+= 88508 mqm amqzxma0 -m MQCNDEV3
>  |  |--- 29062 mqm amqharmx MQCNDEV3 /var/mqm
>  |  |--- 42980 mqm amqzllp0 -mMQCNDEV3 ?
>  |  |--- 47814 mqm amqzlaa0 -mMQCNDEV3 -fip2
>  |  |--- 54084 mqm /usr/mqm/bin/amqzdmaa -m MQCNDEV3
>  |  |--- 68368 mqm amqzlaa0 -mMQCNDEV3 -fip1
>  |  |--- 71718 mqm amqhasmx MQCNDEV3 /var/mqm
>  |  |--- 117848 mqm /usr/mqm/bin/runmqchi -m MQCNDEV3
>  |  |--- 125586 mqm amqzlaa0 -mMQCNDEV3 -fip0
>  |  |--- 137190 mqm /usr/mqm/bin/amqzfuma -m MQCNDEV3
>  |  \--- 148198 mqm /usr/mqm/bin/amqrrmfa -t2332800 -s2592000 -p2592000
> -g5184000 -c3600 -m MQCNDEV3
>
> whereas under Linux, a similar setup yeilds:
>
> init-+-amqpcsea---amqpcsea---amqpcsea
>  |-amqzxma0-+-amqhasmx---amqhasmx---amqhasmx
>  |  |-amqrrmfa---amqrrmfa-+-amqrrmfa
>  |  | `-amqrrmfa
>  |  |-amqzdmaa---amqzdmaa-+-amqzdmaa
>  |  | `-amqzdmaa
>  |  |-amqzfuma---amqzfuma-+-amqzfuma
>  |  | `-amqzfuma
>  |  |-amqzlaa0---amqzlaa0-+-amqzlaa0
>  |  | |-amqzlaa0
>  |  | |-amqzlaa0
>  |  | |-amqzlaa0
>  |  | |-amqzlaa0
>  |  | |-amqzlaa0
>  |  | `-amqzlaa0
>  |  |-amqzllp0---amqzllp0-+-amqzllp0
>  |  | `-amqzllp0
>  |  |-amqzxma0-+-amqzxma0
>  |  |  |-amqzxma0
>  |  |  `-amqzxma0
>  |  `-runmqchi---runmqchi-+-runmqchi
>  ||-runmqchi
>  |`-runmqchi
>
>
> Is this normal ? Can some explain what's going on here ?
>
> Regards,
>
> Andrew Gardner
> E-Business Enablement Services
> IBM Global Services Australia
> +61 2 61242151 (Ph)
> +61 2 61242155 (Fx)
> +61 41 7911179 (Mb)
>
> Instructions for managing your mailing list subscription are provided in
> the Listserv General Users Guide available at http://www.lsoft.com
> Archive: http://vm.akh-wien.ac.at/MQSeries.archive

Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at http://www.lsoft.com
Archive: http://vm.akh-wien.ac.at/MQSeries.archive


Re: MC63 supportpac and WMQ 5.3

2003-03-11 Thread Peter Uranyi
Sandor,

I copied this from my previous post on this problem:

"...the IPC directory names have slightly changed from v5.2 to v5.3, so I
needed to update the halinkmqm and hadltmqm scripts accordingly.

The second problem was that the queue manager would not start up.  (It started
up, but within seconds it crashed leaving a bunch of FDC files behind.)

I found two solutions to this problem:

1. The halinkmqm script creates a link from /var/mqm/qmgrs/QMGR to the real
location of the queue manager.
...
# The link from /var/mqm/qmgrs is not necessary, but some programs
# may assume a default path to the queue manager so we'll create it anyway
ln -fs $3/qmgrs/$2 /var/mqm/qmgrs/$2
...
After removing this link the queue manager started up normally.

2. After creating the HA queue manager QM1, the QueueManager stanza in the
mqs.ini looks something like this:

QueueManager:
   Name=QM1
   Prefix=/MQHA/QM1/data
   Directory=QM1

Changing the Prefix to /var/mqm (and leaving the above mentioned symlink in
place!) did also fixed the problem."

I ended up doing the second option.  I also attached the modified halinkmqm and
hadltmqm, but please make sure you review it, understand it and test it, as I
cannot guarantee that it will work for you.

Peter

--- Sandor Zudor <[EMAIL PROTECTED]> wrote:
> Dear All,
>
> We have a MQ 5.2 and WMQI 2.1 configuration installed on AIX 4.3.3 with
> HACMP support. The MQ and WMQI was configured using MC63 and IC61
> supportpacs - this configuration works properly from few month.
> After migrating MQ 5.2 to WMQ 5.3 the configuration doesn't work, the
> queue manager can't start. After queue manager deletion and recreation
> (using the scripts from MC63 supportpac) the result are the same.
>
> Please, can You help us to solve our problem ?
>
> Best Regards,
> 
> Sandor Zudor - T-Logic KFT.
> e-mail: [EMAIL PROTECTED]
> Tel:+36-1-424.06.01
> Cell:   +36-20-956.97.70
> Fax:+36-1-227.57.16
> URL:www.t-logic.hu
>
>


mqha_aix.zip
Description: mqha_aix.zip


Re: Problems with MQSeries Explorer (MMC)

2003-03-05 Thread Peter Uranyi
> Changes had been made to the security template but the Windows
> experts are at a loss to explain.
This is a frequent problem with experts :-)

> Anyone have this happen??
Yes, I just made it happen on my machine.

> DCOM got error "Logon failure: the user has not been granted the requested
> logon type at this computer. " and was unable to logon .\MUSR_MQADMIN in
> order to run the server:
> {4576E163-FA1A-11D1-ABB8-0004ACF79B59}

MUSR_MQADMIN needs some advanced user rights that "normal" users don't have.
Your experts revoked one (or some) of these rights.

First check if MUSR_MQADMIN has "Log on as a batch job" user right.  (I revoked
this and I got the same messages as you.)

While you're at it check the other user rights too that MUSR_MQADMIN needs:

"Act as part of the operating system"
"Bypass traverse checking"
"Increase quotas"
"Log on as a batch job"
"Log on as a service"
"Replace a process level token"
"Shut down the system"

Hope this helps.

Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at http://www.lsoft.com
Archive: http://vm.akh-wien.ac.at/MQSeries.archive


Re: CLNTCONN - mqrc 2058 error

2003-03-04 Thread Peter Uranyi
If you define your client channel like this:

DEFINE CHANNEL(OH4848T1.SVRCONN) +
   CHLTYPE(CLNTCONN) +
   CONNAME('hostname(port)')
Then:
"amqsputc QL.TEST" will work, but
"amqsputc QL.TEST OH4848T1" will return 2058 (MQRC_Q_MGR_NAME_ERROR)

That's because you specified the qmgr name in your program, so mq will look for
an entry in the channel table with this name.

If you define the qmgr name when you create your client channel:

DEFINE CHANNEL(OH4848T1.SVRCONN) +
   CHLTYPE(CLNTCONN) +
   CONNAME('hostname(port)') +
   QMNAME(OH4848T1)
Then:
"amqsputc QL.TEST" will return 2059 (MQRC_Q_MGR_NOT_AVAILABLE)
"amqsputc QL.TEST OH4848T1" will work.

Now the first command will fail because you didn't specify the qmgr in the
program, so mq will look for an entry in the channel table with a blank qmgr
name.

If you want to have it to work both ways, you have to create two channels, one
with a qmgr name and one without.


--- "Yeh, Jeff" <[EMAIL PROTECTED]> wrote:
> We have Windows 2000 Advanced Servers.
> I am having a strange problem of using client connection.
> I have environmental variables properly defined for MQCHLLIB and  MQCHLTAB
> in Client machine.
> In server machine, the queue manager, I have QL.TEST (QLocal),
> OH4848T1.SVRCONN (server conn), OH4848T1.SVRCONN (Client Conn). I then
> moved the tab file from Program File\IBM\Websphere [EMAIL PROTECTED]
> to client machine.
> When I use IBM provided sample program:
>   amqsputc QL.TEST OH4848T1
>   I got a 2058 reason code, qmgr name error.
> But, if I don't supply the qmgr:
>   amqputc QL.TEST
>   It works fine.
> I rebooted the machine several times, and delete and recreate qmgr several
> times, same thing happens.
> I have other sets of machines and never have this problem.
> Don't know what is going on. Please help. Thanks.
>
> Jeff Yeh

Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at http://www.lsoft.com
Archive: http://vm.akh-wien.ac.at/MQSeries.archive


Re: wmqi - data conversion

2003-03-04 Thread Peter Uranyi
Chris,

> The broker does everything in unicode.

But at some point, WMQI will, for example, convert from Unicode to EBCDIC. What
conversion tables does it use for this? Is it possible to provide non-standard
conversion tables for WMQI to use when converting to and/or from Unicode?

Thanks.

Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at http://www.lsoft.com
Archive: http://vm.akh-wien.ac.at/MQSeries.archive


wmqi - data conversion

2003-03-04 Thread Peter Uranyi
Hello,
I want to perform a non-standard conversion in WMQI between ASCII and EBCDIC,
so I need to build and load a conversion table.
Does anyone know which conversion tables a WMQI broker uses? Does it use the
MQSeries conversion tables or does it have its own set? If the latter, where
are they situated in the WMQI directory?

I need to know for both NT and AIX platforms.

thanks.

Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at http://www.lsoft.com
Archive: http://vm.akh-wien.ac.at/MQSeries.archive


Re: AMI

2003-02-13 Thread Peter Uranyi
Yes, it is a SupportPac:

http://www-3.ibm.com/software/ts/mqseries/txppacs/ma0f.html

--- Robert Broderick <[EMAIL PROTECTED]> wrote:
> Is AMI functionality a seperate install from the base MQ set
>
>
>  bobbee
>
>
>
>
>
> _
> Add photos to your messages with MSN 8. Get 2 months FREE*.
> http://join.msn.com/?page=features/featuredemail
>
> Instructions for managing your mailing list subscription are provided in
> the Listserv General Users Guide available at http://www.lsoft.com
> Archive: http://vm.akh-wien.ac.at/MQSeries.archive

Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at http://www.lsoft.com
Archive: http://vm.akh-wien.ac.at/MQSeries.archive



Re: DR Script

2003-02-11 Thread Peter Uranyi
If you use saveqmgr to backup your queue manager, then you can specify that you
also want to include reset channel commands in the script. (-R switch)

--- Robert Broderick <[EMAIL PROTECTED]> wrote:
> Before I waste my time and write on. Does anybody have a script that will do
> a "RESET" on all the server channels on a particular box
>
> It can be .sh .ksh or .pl
>
>
>bobbee
>
>
>
>
>
> _
> Tired of spam? Get advanced junk mail protection with MSN 8.
> http://join.msn.com/?page=features/junkmail
>
> Instructions for managing your mailing list subscription are provided in
> the Listserv General Users Guide available at http://www.lsoft.com
> Archive: http://vm.akh-wien.ac.at/MQSeries.archive

Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at http://www.lsoft.com
Archive: http://vm.akh-wien.ac.at/MQSeries.archive



Re: MQSeries 5.2.1 and 2046 error between Win2000 cleint and IBM MVS server (mq 2.1)

2003-01-08 Thread Peter Uranyi
David,

You are using a get option that is not valid on MVS.
My first guess would be that in your program you have something like this:

gmo.Version = MQGMO_VERSION_2; /* Avoid need to reset Message  */
gmo.MatchOptions = MQMO_NONE;  /* ID and Correlation ID before */
   /* every MQGET  */

This does work if you connect to a queue manager on Windows or Unix but not on
MVS.

Instead of using the above options, you have to reset the Message ID and
Correlation ID before every(!) MQGET.

Like this:

memcpy(md.MsgId, MQMI_NONE, sizeof(md.MsgId));
memcpy(md.CorrelId, MQCI_NONE, sizeof(md.CorrelId));

I hope this helps.
Peter

--- COHEN David <[EMAIL PROTECTED]> wrote:
> Dear all
>
> I have a question regarding MQSeries 5.2.1 installed on an Windows 2000 as a
> client
> And MQSeries 2.1 installed on an IBM MVS as a server. When trying to do an
> MQGET on a queue I receive an error message 2, 2046.
>
> The MQGET connects fine to the Channel and to the Queue but when trying to
> retrive the message on the IBM MVS side the error 2, 2046 appears. We can see
> on the IBM MVS side the error
>
> Csqx 208E error receiving data code 461
>
> I do not know if it is related
>
> ***
> Changing current directory to c:\rightfax\production\bin Connected to
> 'RightFAX' (0,0)
> Opened Queue 'RF_Queue'  (0,0)
> Creating primary buffer of size 64 Ko Unable to retrieve message error 2,
> 2046
> ***
>
> If I install an MQSeries 5.2.1 on another Windows 2000 as a server and define
> the queues the same way as on the IBM everything works fine
>
> Any idea ?
>
> David COHEN
>
> Thank you
>
> Instructions for managing your mailing list subscription are provided in
> the Listserv General Users Guide available at http://www.lsoft.com
> Archive: http://vm.akh-wien.ac.at/MQSeries.archive

Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at http://www.lsoft.com
Archive: http://vm.akh-wien.ac.at/MQSeries.archive



Re: savqmgr and 5.3

2002-12-27 Thread Peter Uranyi
Tom,
There are two 'versions' of 5.3, GA1 and GA2.  GA2 (or 5.3.0.1) has CSD01
built-in.
On GA1 mqver displays this:
$ mqver
Name:WebSphere MQ
Version: 530
CMVC level:  p000-L020617
BuildType:   IKAP - (Production)

Looking at the output from your mqver command, you have the GA2 level
installed.
I assume this is on your AIX box, where you found the problem with the KAINT
parameter.
You should also run mqver on your HP box, where you didn't have a problem with
saveqmgr.  I think that your HP box has GA1 installed and KAINT was introduced
only in GA2.

The amqmcert command is only available on Windows (both GA1 and GA2) and it is
documented in the System Administration Guide and in the Security Guide.

--- "KANE, TOM M (AIT)" <[EMAIL PROTECTED]> wrote:
> Peter,
> I'm not sure how to check the 'edition' of 5.3.  I had assumed that there
> was one 5.3 for Unix and that CSDs were the only way to have further levels.
> I am unsure of this version however, as some of the commands in the MQ
> Command Reference are coming up not found.
> I'm looking for, but not finding: amqmcert.
> mqver does give me:
>
> $ mqver
> Name:WebSphere MQ
> Version: 530
> CMVC level:  p000-L021011
> BuildType:   IKAP - (Production)
> $
>
>
> -Original Message-
> From: Peter Uranyi [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, December 18, 2002 9:04 PM
> To: [EMAIL PROTECTED]
> Subject: Re: savqmgr and 5.3
>
>
> Can you check which edition of 5.3 are you running?  I looked at my queue
> managers on AIX and Windows (both GA1 level) and there is no KAINT
> parameter.
> But in GA2 Windows there is!
> So, maybe KAINT was only introduced in October with GA2.  This would also
> explain why saveqmgr (released in September) doesn't recognize this
> parameter.
>
>
> --- "KANE, TOM M (AIT)" <[EMAIL PROTECTED]> wrote:
> > Mike,
> > Didn't see your response.
> > I had found this problem on AIX.  I didn't see this on HP.  I just looked
> at
> > HP it's not a valid parameter on the channel definition there.  And that's
> > probably why it was missed in the SupportPac.
> > Since then I have made additions to the code.  They are pretty basic.  The
> > new attribute is an integer and if it's -1 then the KAINT should be set to
> > auto.  Probably 3 places that the code needs to change.
> >
> > Tom
> >
> > -Original Message-
> > From: Michael F Murphy/AZ/US/MQSolutions [mailto:[EMAIL PROTECTED]]
> > Sent: Friday, December 06, 2002 4:06 PM
> > To: [EMAIL PROTECTED]
> > Subject: savqmgr and 5.3
> >
> >
> >
> > I have encountered the exact same problem in my testing.  The mqsc output
> > seems fine though.  According to the manual, the KAINT parameter is for
> z\os
> > only.  Is this true?  The documentation is a bit misleading because it
> > explains keep alive for all platforms and makes this disclaimer at the
> end.
> > Is this true?  And if this is the case, the error seems harmless.
> However,
> > it should be corrected.
> >
> > Mike Murphy
> > MQ Solutions, LLC
> >
> > "KANE, TOM M (AIT)" <[EMAIL PROTECTED]> wrote:
> >
> >
> > Date Recieved:
> >  12/06/2002 10:14:23 AM
> >
> > To:
> >  [EMAIL PROTECTED]
> >
> > cc:
> >
> >
> > Bcc
> >
> >
> > Subject:
> >  savqmgr and 5.3
> >
> >
> >
> > Hi,
> >
> > I'm testing with a 5.3 qmgr and the latest saveqmgr that I downloaded from
> >
> > IBM is still failing on the KAINT parameter not being cared for by the
> >
> > program.
> >
> > Has anybody else seen this?  It manifests itself as several messages like:
> >
> > Unknown PCF Integer Parameter: 1566
> >
> >
> >
> > I looked briefly at the code in channel.c and it looks like it needs to be
> >
> > changed to support this parameter.
> >
> >
> >
> > Tom
> >
> >
> >
> > 
> >
> > Tom Kane
> >
> > MQSeries System Support

Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at http://www.lsoft.com
Archive: http://vm.akh-wien.ac.at/MQSeries.archive



Re: savqmgr and 5.3

2002-12-18 Thread Peter Uranyi
Can you check which edition of 5.3 are you running?  I looked at my queue
managers on AIX and Windows (both GA1 level) and there is no KAINT parameter.
But in GA2 Windows there is!
So, maybe KAINT was only introduced in October with GA2.  This would also
explain why saveqmgr (released in September) doesn't recognize this parameter.


--- "KANE, TOM M (AIT)" <[EMAIL PROTECTED]> wrote:
> Mike,
> Didn't see your response.
> I had found this problem on AIX.  I didn't see this on HP.  I just looked at
> HP it's not a valid parameter on the channel definition there.  And that's
> probably why it was missed in the SupportPac.
> Since then I have made additions to the code.  They are pretty basic.  The
> new attribute is an integer and if it's -1 then the KAINT should be set to
> auto.  Probably 3 places that the code needs to change.
>
> Tom
>
> -Original Message-
> From: Michael F Murphy/AZ/US/MQSolutions [mailto:[EMAIL PROTECTED]]
> Sent: Friday, December 06, 2002 4:06 PM
> To: [EMAIL PROTECTED]
> Subject: savqmgr and 5.3
>
>
>
> I have encountered the exact same problem in my testing.  The mqsc output
> seems fine though.  According to the manual, the KAINT parameter is for z\os
> only.  Is this true?  The documentation is a bit misleading because it
> explains keep alive for all platforms and makes this disclaimer at the end.
> Is this true?  And if this is the case, the error seems harmless.  However,
> it should be corrected.
>
> Mike Murphy
> MQ Solutions, LLC
>
> "KANE, TOM M (AIT)" <[EMAIL PROTECTED]> wrote:
>
>
> Date Recieved:
>  12/06/2002 10:14:23 AM
>
> To:
>  [EMAIL PROTECTED]
>
> cc:
>
>
> Bcc
>
>
> Subject:
>  savqmgr and 5.3
>
>
>
> Hi,
>
> I'm testing with a 5.3 qmgr and the latest saveqmgr that I downloaded from
>
> IBM is still failing on the KAINT parameter not being cared for by the
>
> program.
>
> Has anybody else seen this?  It manifests itself as several messages like:
>
> Unknown PCF Integer Parameter: 1566
>
>
>
> I looked briefly at the code in channel.c and it looks like it needs to be
>
> changed to support this parameter.
>
>
>
> Tom
>
>
>
> 
>
> Tom Kane
>
> MQSeries System Support
>
>
>
> Instructions for managing your mailing list subscription are provided in
>
> the Listserv General Users Guide available at  http://www.lsoft.com
> 
>
> Archive:  http://vm.akh-wien.ac.at/MQSeries.archive
> 
> "{--o
~a
jvx2 j)b b.n6+bvz'^v)M B2  Z K nW i^jma 6 %rdb`>=mo6 f  M7 ITz
> r
>
>

Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at http://www.lsoft.com
Archive: http://vm.akh-wien.ac.at/MQSeries.archive



Re: Set maxconnections for each Client channel

2002-12-17 Thread Peter Uranyi
Take a look at SupportPac ME71.


--- "Springer, Henry" <[EMAIL PROTECTED]> wrote:
> Hello all,
>
> our application programmer provide a good DOS attack against our
> QueueManager. They coded a client connection in a loop without freeing the
> current sessions. After a short period of time, all allowed connections are
> busy and the normal Server to Server channels didn't start anymore. Stopping
> and restarting the client channel took a long time.
> Are there any suggestions to avoid these problems:
> -   Maybe, there will be extra parms for client channels, a made
> application can't eat up server connections
> -   Maybe, the maxconnection parm is adjusted per client channel, now,
> I'm able to provide each channel with its own value
> -   I can think of a client channel exit, counting all session
> start/stop and reject any connection after a given maximum.
>
> Do you know a circumvention (or better: solution) of this problem ?
>
> Best regards
>
> Henry Springer
> MQSeries Familie
> K-DOI-23
>
> Volkswagen AG
> Brieffach 1891
> 38436 Wolfsburg
>
> Telefon +49-53 61-92 97 74
> Telefax +49-53 61-92 28 13
> eFax +49-5361-95 72 97 74
> http://www.volkswagen.de
>
> Instructions for managing your mailing list subscription are provided in
> the Listserv General Users Guide available at http://www.lsoft.com
> Archive: http://vm.akh-wien.ac.at/MQSeries.archive

Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at http://www.lsoft.com
Archive: http://vm.akh-wien.ac.at/MQSeries.archive



Re: Support pac MC6A and MQ 5.3

2002-12-16 Thread Peter Uranyi
I didn't, but I am using HACMP on AIX.  I also ran into problems after
upgrading to MQ5.3, so the following might help.

First of all I found that the IPC directory names have slightly changed from
v5.2 to v5.3, so I needed to update the halinkmqm and hadltmqm scripts
accordingly.

The second problem was that the queue manager would not start up.  (It started
up, but within seconds it crashed leaving a bunch of FDC files behind.)

I found two solutions to this problem:

1. The halinkmqm script creates a link from /var/mqm/qmgrs/QMGR to the real
location of the queue manager.
...
# The link from /var/mqm/qmgrs is not necessary, but some programs
# may assume a default path to the queue manager so we'll create it anyway
ln -fs $3/qmgrs/$2 /var/mqm/qmgrs/$2
...
After removing this link the queue manager started up normally.

2. After creating the HA queue manager QM1, the QueueManager stanza in the
mqs.ini looks something like this:

QueueManager:
   Name=QM1
   Prefix=/MQHA/QM1/data
   Directory=QM1

Changing the Prefix to /var/mqm (and leaving the above mentioned symlink in
place!) did also fixed the problem.

I hope this helps.
Peter


--- Greg Ross <[EMAIL PROTECTED]> wrote:
> Hi all,
>
> Is anyone using the Veritas Solaris cluster support pac MC6A with MQ 5.3?
>
> We have tried defining some Q managers and have run into problems starting
> up the new Q manager. These startup problems do not occur if the Q manager
> is defined with the normal CRTMQM command.
>
>
> Thanks.Greg
>
> __
> The information contained in this email communication may be confidential.
> You
> should only read, disclose, re-transmit, copy, distribute, act in reliance
> on or
> commercialise the information if you are authorised to do so. If you are
> not the
> intended recipient of this email communication, please notify us
> immediately by
> email to [EMAIL PROTECTED] or reply by email direct to the sender
> and then destroy any electronic or paper copy of this message.  Any views
> expressed in this email communication are those of the individual sender,
> except
> where the sender specifically states them to be the views of a member of
> the
> National Australia Bank Group of companies.  The National Australia Bank
> Group
> of companies does not represent, warrant or guarantee that the integrity of
> this
> communication has been maintained nor that the communication is free of
> errors,
> virus or interference.
>
> Instructions for managing your mailing list subscription are provided in
> the Listserv General Users Guide available at http://www.lsoft.com
> Archive: http://vm.akh-wien.ac.at/MQSeries.archive

Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at http://www.lsoft.com
Archive: http://vm.akh-wien.ac.at/MQSeries.archive



Peter Uranyi/Bsg/MetLife/US is out of the office.

2002-06-02 Thread Peter Uranyi

I will be out of the office starting  06/03/2002 and will not return until
06/10/2002.

I will be out of the office between 6/3 and 6/7, returning on 6/10.  If
this is urgent please contact Milt Weinberger (908-575-5344) or Joseph
Willis (908-575-5307), otherwise I will respond to your message when I
return.

Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at http://www.lsoft.com
Archive: http://vm.akh-wien.ac.at/MQSeries.archive