WMQIv2 shutdown problem
Hi, We have just upgraded an our MQSi system to WMQSI and have noticed a small problem which has stumped us a little. We have a broker and it just won't shut down the 1st execution Group (ie the default execution group). It will shut down all the others but never that one. All we get is an error in the syslog saying: WMQIv210[4270]: (TEST_BROKER)[772]BIP2804E: The broker has detected that Execution Group Services, process ID 41542, has not shutdown. : TEST_BROKER.agent: /build/S210_P/src/AdminAgent/ImbAdminStore.cpp: 606: ImbAdminStore::FindAndReportAllLongRunningProcesses: : " Once we issue a kill command on this process the broker shuts down not a problem and the mqsistop command returns the normal message: "BIP8061I: Successful comamnd completion." The software revisions are WMQSI 2.1 csd04 MQ 5.2 csd 05 DB2 UDB 7.2 AIX 4.3.3.0 RML 10 Hardware is IBM RS/6000 pSeries 6C1 Any help would be greatly apreciated. Regards John Abbott PS: your list was very helpful with another similar problem on MQSeries. Many thanks to all that provided solutions. ** * IMPORTANT INFORMATION* This document should be read only by those persons to whom it is addressed and its content is not intended for use by any other persons. If you have received this message in error, please notify us immediately. Please also destroy and delete the message from your computer. Any unauthorised form of reproduction of this message is strictly prohibited. St.George is not liable for the proper and complete transmission of the information contained in this communication, nor for any delay in its receipt. **
Re: Large record size
Hi Lizette, what exactly is your concern? Is it amount of data or number of messages? Or both...? Generally speaking, 1k is not really a big message. If you add the message descriptor and transmission header (roughly 450 bytes), you are talking about approc. 1500 bytes per message. If you look at the performance support pacs you will see that this is the average message size at which MQ throughput peaks, so I wouldn't worry about the size (it doesn't matter anyway, they say). ;-) Assuming you have enough disk space everywhere the messages touch a disk (XMITQ on /390, target queue on Win2K) and your log files are sufficiently defined, you should be fine. The real challenge will be to convince your programmer not to try to send all 900.000 messages in ONE unit of work, but to do frequent commits ;-) There is a queue manager parameter that limits the number of uncommited messages (I think on 390 its called MAXSMSGS), that will limit how many messages the application can put within a syncpoint. It is a good practice to design applications so that they can make use of 'reasonable' batch sizes (preferably configurable) so this limit is not reached (it causes an MQCC_FAILED with MQRC_BACKED_OUT, I think). Remember, the MCA on the mainframe will not even see the messages (and start transmitting them) until the application calls MQCMIT. I am assuming that they are put using MQPM_SYNCPOINT; first of all because they are persistent, secondly because it's the default on /390. Bottom line: I would be more concerned about a tunable design, using a configurable application batch size, than about sheer volume. Other opinions/aspects/remarks out there? Hope it helps a bit, Stefan From: "Anderson, Lizette T. (RyTull)" <[EMAIL PROTECTED]> Reply-To: MQSeries List <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] Subject: Large record size Date: Tue, 3 Dec 2002 17:22:39 -0600 I have a programmer currently designing an MQ application who would like to send 900,000 persistent messages through MQ. The bytes per record is 1012. It will run on OS/390 to a Window 2000 server both running 5.2 MQ. Are there any negative affects to sending this many records? It is by far the largest record size we have defined and I am concerned. --- Legal Disclaimer: The information contained in this communication may be confidential, is intended only for the use of the recipient named above, and may be legally privileged. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution, or copying of this communication, or any of its contents, is strictly prohibited. If you have received this communication in error, please re-send this communication to the sender and delete the original message and any copy of it from your computer system. 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 _ STOP MORE SPAM with the new MSN 8 and get 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
Re: Clustering on iSeries
Ben, Yes for both questions. MQ5.2 suppports clustering. For remote administration using MQ explore,. you can learn the details of remote admin on Chapter 3 of iSeries System Administration Guide. Cheers, Ian -Original Message-From: Pope, Ben [mailto:[EMAIL PROTECTED]]Sent: Wednesday, 4 December 2002 5:37 AMTo: [EMAIL PROTECTED]Subject: Clustering on iSeries Apologies for such a simple question but the AS/400 is as alien to me as walking on the moon. Does MQ 5.2 on the iSeries support clustering? Looking at the documentation (5th addition) it states the docs apply to 5.3 for iSeries but I haven't found anything that mentions the minimum version needed for clustering support on iSeries. Also, assuming 5.2 does support clustering can I plan on using MQExplorer to manage its cluster? Thanks, Ben
Large record size
I have a programmer currently designing an MQ application who would like to send 900,000 persistent messages through MQ. The bytes per record is 1012. It will run on OS/390 to a Window 2000 server both running 5.2 MQ. Are there any negative affects to sending this many records? It is by far the largest record size we have defined and I am concerned. --- Legal Disclaimer: The information contained in this communication may be confidential, is intended only for the use of the recipient named above, and may be legally privileged. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution, or copying of this communication, or any of its contents, is strictly prohibited. If you have received this communication in error, please re-send this communication to the sender and delete the original message and any copy of it from your computer system. 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
Re: V5.3/V5.3.1 etc
Great explanation, this helps a great deal. I am still concerned about mqver. Here is the output I get on both my Windows 2000 and Linux machines. Note that my Windows 2000 memo.ptf says it has CSD 1 but Linux says no CSD applied:
Name: WebSphere MQ Version: 530 CMVC level: p000-L021011 BuildType: IKAP - (Production)
How can I tell the CSD applied with this? To me it is gibberish.
Mike Murphy
MQ Solutions, LLC
Mark Taylor <[EMAIL PROTECTED]> wrote:
Date Recieved:
12/03/2002 08:54:42 AM
To:
[EMAIL PROTECTED]
cc:
Bcc
Subject:
V5.3/V5.3.1 etcLet me make one thing very clear: there is NO SUCH THING as V5.3.1
For a brief time, the download images were labelled that way, but it was
quickly corrected to say V5.3.0.1. That extra zero makes all the
difference.
The first tranche of V5.3 platforms were shipped mid-year, and we often
refer to those as the GA1 release.
Testing then continued on the extra platforms (Linux, OS/400) and a number
of fixes were made in cross-platform code. So, when the second set was
released ("GA2") it made sense to refresh the manufacturing images of the
original set of platforms at the same time, so they were all at exactly the
same level. New shipments of the original platforms will all, in effect,
have CSD01 pre-applied.
However you could also get the same set of code by applying CSD01 to a GA1
platform. You will see the CSD level included in inventory commands such as
lslpp on AIX, wherever that's possible.
Two minor complications: CSD01 isn't separately downloadable at the moment,
because of a hitch dealing with the fact that it contains crypto code. We
are trying to sort that out urgently. (I believe some people have been sent
it directly, but can't be sure of that.)
And if you want to install on Windows XP you must get the new level, as the
earlier install code (which of course cannot be updated by CSD) explicitly
refused to allow you to put it on XP.
But when CSD02 arrives, you will be able to install it on top of a GA1
package, a GA2 package or a GA1+CSD01 package.
Mark Taylor.
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
"{-®ç-ì~æjv x2¢êæj)b b²Û.nÇ+b¢v«zè¾'^v)í
ââ²Û ®ñêÚK ®Á®×½¨¥i¹^jØm¶ÿà %²írÈb½èm¶ÿ¾f¤§·óIêâzÆ«r¯
Re: Perl module on NT
Jesse, I can't speak either for Active State nor the current module maintainer, Hildo Biersma, so I'm not really in a position to say. My guess however would be "not any time soon". The reason is that both Perl and MQ are available on such a wide variety of platforms, and the binary module is specific to the versions of Perl, MQ and OS that it was compiled on. Any reasonably complete binary distribution would need to cover a multitude of combinations. The encouraging news is that Active State has at least taken notice of the module and now includes it in their documentation, although at a back level: http://aspn.activestate.com/ASPN/Modules/dist_html?dist_id=9178 Perhaps if there is enough interest, they will add the current version of the module to their repository. -- T.Rob -Original Message-From: jesse h. goode jr. [mailto:[EMAIL PROTECTED]]Sent: Tuesday, December 03, 2002 4:10 PMTo: [EMAIL PROTECTED]Subject: Re: Perl module on NT T. Rob any chance these modules will eventually get into an Activestate perl module package? jesse goode jrvalero energy corporation[EMAIL PROTECTED] - Original Message - From: Wyatt, T. Rob To: [EMAIL PROTECTED] Sent: Tuesday, December 03, 2002 1:41 PM Subject: Re: Perl module on NT Thanks, Ian. I've been working with the current module author and we have identified a few bugs in the code related to cluster commands. Hopefully, some of these failed tests will pass once the new version comes out. Unfortunately, once the Perl bugs are out of the way, there are still the mysteries of clusters to deal with. I've decoded the PCF commands by hand with a hex dumper and calculator and see that the formats are right and the responses back from the Command Server are good - but some of the commands appear to have no effect. Even MQ Explorer reports conflicting information about my cluster, depending on where you look. Sigh... -- T.Rob -Original Message-From: Ian Steyn [mailto:[EMAIL PROTECTED]]Sent: Tuesday, November 26, 2002 4:20 PMTo: [EMAIL PROTECTED]Subject: Re: Perl module on NTRob, I get the following. Failed Test Status Wstat Total Fail Failed List of Failed t\20convert.t 6 2 33.33% 5-6 t\30basic.t 17 3 17.65% 6-7, 15 Failed 2/7 test scripts, 71.43% okay. 5/1949 subtests failed, 99.74% okay. If "NOSERVER=1" in the CONFIG file is commented out, the results is exactly the same as yours. I don't have a PCF script to test and see if that works. Ian "Wyatt, T. Rob" <[EMAIL PROTECTED]> Sent by: MQSeries List <[EMAIL PROTECTED]> 11/26/2002 12:34 PM Please respond to MQSeries List To: [EMAIL PROTECTED] cc: Subject: Perl module on NTHas anyone out there gotten the Perl MQSeries module to compile *and* had asuccessful run of the test suite on NT? I've been using the module on NTservers for quite a while. It compiles and installs but never passes thetests. Still, it works great for most everyday functions. Recently I trieddoing some PCF cluster commands and I guess I'm exercising the parts of thecode that fail the tests. I've tried module versions 1.7 through 1.9 onActive State 5.6.1 builds 629 through 633 with the same result.I'd feel a lot better if I knew whether anyone else has done thissuccessfully.Here's the run-time error:Unable to translate Command/Parameters into MQEncodePCF inputData conversion hook (PutConvert) failed atD:/Perl/site/lib/MQSeries/Command.pm line 772The compile shows the following warnings:Please specify prototyping behavior for DeadLetter.xs (see perlxs manual)Please specify prototyping behavior for PCF.xs (see perlxs manual)Please specify prototyping behavior for RulesFormat.xs (see perlxs manual)The test run looks like this:I:\MQSeries-1.19>nmake test TEST_VERBOSE=1Microsoft (R) Program Maintenance Utility Version 6.00.8168.0Copyright (C) Microsoft Corp 1988-1998. All rights reserved. D:\Perl\bin\perl.exe -Mblib -ID:\Perl\lib -ID:\Perl\lib -e "useTest::Harness qw(&runtests $verbose); $verbose=0; runtests @ARGV;" t\10constants.tt\20convert.t t\30basic.t t\40oo-qmgr.t t\50oo-command.t t\60-logs.tt\70-config.tUsing I:/MQSeries-1.19/MQClient/../blibt\10constants...okt\20convert.FAILED tests 2-6 Failed 5/6 tests, 16.67% okayt\30basic...FAILED tests 2-17
Re: V5.3/V5.3.1 etc
Hi Mark Mark Taylor wrote: > Let me make one thing very clear: there is NO SUCH THING as V5.3.1 > For a brief time, the download images were labelled that way, > but it was quickly corrected to say V5.3.0.1. That extra zero makes > all the difference. Thanx a lot for this statement! But ... 1. developerWorks: Toolbox The Downloads at "developerWorks: Toolbox" are still wrong ... http://www6.software.ibm.com/devcon/devcon/docs/contents.html#Enterprise-mqseries-servers 2. Solaris Package Package version tells us 5.3.0. Why not 5.3.0.1? :( Best regards, Marcel Hofstetter, JomaSoft GmbH IBM Certified Specialist - MQSeries 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: Perl module on NT
T. Rob any chance these modules will eventually get into an Activestate perl module package? jesse goode jrvalero energy corporation[EMAIL PROTECTED] - Original Message - From: Wyatt, T. Rob To: [EMAIL PROTECTED] Sent: Tuesday, December 03, 2002 1:41 PM Subject: Re: Perl module on NT Thanks, Ian. I've been working with the current module author and we have identified a few bugs in the code related to cluster commands. Hopefully, some of these failed tests will pass once the new version comes out. Unfortunately, once the Perl bugs are out of the way, there are still the mysteries of clusters to deal with. I've decoded the PCF commands by hand with a hex dumper and calculator and see that the formats are right and the responses back from the Command Server are good - but some of the commands appear to have no effect. Even MQ Explorer reports conflicting information about my cluster, depending on where you look. Sigh... -- T.Rob -Original Message-From: Ian Steyn [mailto:[EMAIL PROTECTED]]Sent: Tuesday, November 26, 2002 4:20 PMTo: [EMAIL PROTECTED]Subject: Re: Perl module on NTRob, I get the following. Failed Test Status Wstat Total Fail Failed List of Failed t\20convert.t 6 2 33.33% 5-6 t\30basic.t 17 3 17.65% 6-7, 15 Failed 2/7 test scripts, 71.43% okay. 5/1949 subtests failed, 99.74% okay. If "NOSERVER=1" in the CONFIG file is commented out, the results is exactly the same as yours. I don't have a PCF script to test and see if that works. Ian "Wyatt, T. Rob" <[EMAIL PROTECTED]> Sent by: MQSeries List <[EMAIL PROTECTED]> 11/26/2002 12:34 PM Please respond to MQSeries List To: [EMAIL PROTECTED] cc: Subject: Perl module on NTHas anyone out there gotten the Perl MQSeries module to compile *and* had asuccessful run of the test suite on NT? I've been using the module on NTservers for quite a while. It compiles and installs but never passes thetests. Still, it works great for most everyday functions. Recently I trieddoing some PCF cluster commands and I guess I'm exercising the parts of thecode that fail the tests. I've tried module versions 1.7 through 1.9 onActive State 5.6.1 builds 629 through 633 with the same result.I'd feel a lot better if I knew whether anyone else has done thissuccessfully.Here's the run-time error:Unable to translate Command/Parameters into MQEncodePCF inputData conversion hook (PutConvert) failed atD:/Perl/site/lib/MQSeries/Command.pm line 772The compile shows the following warnings:Please specify prototyping behavior for DeadLetter.xs (see perlxs manual)Please specify prototyping behavior for PCF.xs (see perlxs manual)Please specify prototyping behavior for RulesFormat.xs (see perlxs manual)The test run looks like this:I:\MQSeries-1.19>nmake test TEST_VERBOSE=1Microsoft (R) Program Maintenance Utility Version 6.00.8168.0Copyright (C) Microsoft Corp 1988-1998. All rights reserved. D:\Perl\bin\perl.exe -Mblib -ID:\Perl\lib -ID:\Perl\lib -e "useTest::Harness qw(&runtests $verbose); $verbose=0; runtests @ARGV;" t\10constants.tt\20convert.t t\30basic.t t\40oo-qmgr.t t\50oo-command.t t\60-logs.tt\70-config.tUsing I:/MQSeries-1.19/MQClient/../blibt\10constants...okt\20convert.FAILED tests 2-6 Failed 5/6 tests, 16.67% okayt\30basic...FAILED tests 2-17 Failed 16/17 tests, 5.88% okayt\40oo-qmgr.ok 1/9MQCONN failed (Reason = 2058) (Queue manager namenotvalid or not known.) at t\40oo-qmgr.t line 40t\40oo-qmgr.FAILED tests 2-9 Failed 8/9 tests, 11.11% okayt\50oo-command..okt\60-logs...okt\70-config.okFailed Test Status Wstat Total Fail Failed List of Failedt\20convert.t 6 5 83.33% 2-6t\30basic.t 17 16 94.12% 2-17t\40oo-qmgr.t 9 8 88.89% 2-9Failed 3/7 test scripts, 57.14% okay. 29/1824 subtests failed, 98.41% okay.NMAKE : fatal error U1077: 'D:\Perl\bin\perl.exe' : return code '0xff'Stop.NMAKE : fatal error U1077: 'cd' : return code '0x2'Stop.I:\MQSeries-1.19>Thanks -- T.RobInstructions for managing your mailing list subscription are provided inthe Listserv General Users Guide available at http://www.lsoft.comArchive: http://vm.akh-wien.ac.at/MQSeries.
Re: Sec Channel Exit code
Chris, Can I have a copy, too.thanks. marc. Sudheer Kumar <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] Sent by: MQSeries List cc: <[EMAIL PROTECTED]> Subject: Re: Sec Channel Exit code Tuesday December 3, 2002 01:56 PM Please respond to MQSeries List Chris, I would like a copy of the article and the code. Thanks, Sudheer -Original Message- From: MQSeries List [mailto:[EMAIL PROTECTED]]On Behalf Of Howarth, Chris Sent: Thursday, November 28, 2002 12:37 AM To: [EMAIL PROTECTED] Subject: Re: Sec Channel Exit code I wrote the article mentioned below. It has an explanation of how channel security exits work and has outline template code. You still need to plug in the actual security you choose to implement, but the article explains what each step is for, how it works and different methods of security you can plug in. If anyone wants the article and code, drop me a note. I think the link below has the first part of the article. Regards, ___ Chris Howarth CommerceQuest UK Ltd -Original Message- From: Bullock, Rebecca (CSC) [mailto:[EMAIL PROTECTED]] Sent: 27 November 2002 17:34 To: [EMAIL PROTECTED] Subject: OS/390: Channel Security Exit Wasn't someone asking a question about this very topic just a week or so ago? I just thought I'd point out that the latest issue of Mainframe Week (http://www.mainframeweek.com) has the start of a series of articles on this. It may be too late for the person with the query, but perhaps someone else would be interested. Regards, Rebecca P.S. For those of you in the U.S. --Happy Thanksgiving! Rebecca Bullock Computer Sciences Corporation Educational Testing Service Account Princeton, NJ 08541 e-mail: [EMAIL PROTECTED][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 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: Sec Channel Exit code
Chris, part 1 looks pretty useful at mainframe week. If part 2 is going to be a while, I would also appreciate the full article via mail or post. Thanks Bill -Original Message- From: Yu, David [mailto:[EMAIL PROTECTED]] Sent: Tuesday, December 03, 2002 10:51 AM To: [EMAIL PROTECTED] Subject: Re: Sec Channel Exit code Chris, Could you send me the article and code. Thanks David -Original Message- From: Howarth, Chris [mailto:[EMAIL PROTECTED]] Sent: Thursday, November 28, 2002 2:37 AM To: [EMAIL PROTECTED] Subject: Re: Sec Channel Exit code I wrote the article mentioned below. It has an explanation of how channel security exits work and has outline template code. You still need to plug in the actual security you choose to implement, but the article explains what each step is for, how it works and different methods of security you can plug in. If anyone wants the article and code, drop me a note. I think the link below has the first part of the article. Regards, ___ Chris Howarth CommerceQuest UK Ltd -Original Message- From: Bullock, Rebecca (CSC) [mailto:[EMAIL PROTECTED]] Sent: 27 November 2002 17:34 To: [EMAIL PROTECTED] Subject: OS/390: Channel Security Exit Wasn't someone asking a question about this very topic just a week or so ago? I just thought I'd point out that the latest issue of Mainframe Week (http://www.mainframeweek.com) has the start of a series of articles on this. It may be too late for the person with the query, but perhaps someone else would be interested. Regards, Rebecca P.S. For those of you in the U.S. --Happy Thanksgiving! Rebecca Bullock Computer Sciences Corporation Educational Testing Service Account Princeton, NJ 08541 e-mail: [EMAIL PROTECTED][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 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
MQSI - ascii constants in eSql
Hi, Does anyone know how to create a ascii value constant in a compute node? We have a need to include the Tab (ascii 09) and NewLine (ascii 10) characters in a message. Thanks, Lynn
Re: Perl module on NT
Thanks, Ian. I've been working with the current module author and we have identified a few bugs in the code related to cluster commands. Hopefully, some of these failed tests will pass once the new version comes out. Unfortunately, once the Perl bugs are out of the way, there are still the mysteries of clusters to deal with. I've decoded the PCF commands by hand with a hex dumper and calculator and see that the formats are right and the responses back from the Command Server are good - but some of the commands appear to have no effect. Even MQ Explorer reports conflicting information about my cluster, depending on where you look. Sigh... -- T.Rob -Original Message-From: Ian Steyn [mailto:[EMAIL PROTECTED]]Sent: Tuesday, November 26, 2002 4:20 PMTo: [EMAIL PROTECTED]Subject: Re: Perl module on NTRob, I get the following. Failed Test Status Wstat Total Fail Failed List of Failed t\20convert.t 6 2 33.33% 5-6 t\30basic.t 17 3 17.65% 6-7, 15 Failed 2/7 test scripts, 71.43% okay. 5/1949 subtests failed, 99.74% okay. If "NOSERVER=1" in the CONFIG file is commented out, the results is exactly the same as yours. I don't have a PCF script to test and see if that works. Ian "Wyatt, T. Rob" <[EMAIL PROTECTED]> Sent by: MQSeries List <[EMAIL PROTECTED]> 11/26/2002 12:34 PM Please respond to MQSeries List To: [EMAIL PROTECTED] cc: Subject: Perl module on NTHas anyone out there gotten the Perl MQSeries module to compile *and* had asuccessful run of the test suite on NT? I've been using the module on NTservers for quite a while. It compiles and installs but never passes thetests. Still, it works great for most everyday functions. Recently I trieddoing some PCF cluster commands and I guess I'm exercising the parts of thecode that fail the tests. I've tried module versions 1.7 through 1.9 onActive State 5.6.1 builds 629 through 633 with the same result.I'd feel a lot better if I knew whether anyone else has done thissuccessfully.Here's the run-time error:Unable to translate Command/Parameters into MQEncodePCF inputData conversion hook (PutConvert) failed atD:/Perl/site/lib/MQSeries/Command.pm line 772The compile shows the following warnings:Please specify prototyping behavior for DeadLetter.xs (see perlxs manual)Please specify prototyping behavior for PCF.xs (see perlxs manual)Please specify prototyping behavior for RulesFormat.xs (see perlxs manual)The test run looks like this:I:\MQSeries-1.19>nmake test TEST_VERBOSE=1Microsoft (R) Program Maintenance Utility Version 6.00.8168.0Copyright (C) Microsoft Corp 1988-1998. All rights reserved. D:\Perl\bin\perl.exe -Mblib -ID:\Perl\lib -ID:\Perl\lib -e "useTest::Harness qw(&runtests $verbose); $verbose=0; runtests @ARGV;" t\10constants.tt\20convert.t t\30basic.t t\40oo-qmgr.t t\50oo-command.t t\60-logs.tt\70-config.tUsing I:/MQSeries-1.19/MQClient/../blibt\10constants...okt\20convert.FAILED tests 2-6 Failed 5/6 tests, 16.67% okayt\30basic...FAILED tests 2-17 Failed 16/17 tests, 5.88% okayt\40oo-qmgr.ok 1/9MQCONN failed (Reason = 2058) (Queue manager namenotvalid or not known.) at t\40oo-qmgr.t line 40t\40oo-qmgr.FAILED tests 2-9 Failed 8/9 tests, 11.11% okayt\50oo-command..okt\60-logs...okt\70-config.okFailed Test Status Wstat Total Fail Failed List of Failedt\20convert.t 6 5 83.33% 2-6t\30basic.t 17 16 94.12% 2-17t\40oo-qmgr.t 9 8 88.89% 2-9Failed 3/7 test scripts, 57.14% okay. 29/1824 subtests failed, 98.41% okay.NMAKE : fatal error U1077: 'D:\Perl\bin\perl.exe' : return code '0xff'Stop.NMAKE : fatal error U1077: 'cd' : return code '0x2'Stop.I:\MQSeries-1.19>Thanks -- T.RobInstructions for managing your mailing list subscription are provided inthe Listserv General Users Guide available at http://www.lsoft.comArchive: http://vm.akh-wien.ac.at/MQSeries.archive
Re: Removal of Messages
Michael, It's a long road to travel but you can do it with Perl. I say "a long road" because you would need to... a) Download and install Perl (preferably Active State) b) Download the MQSeries Perl module from CPAN c) Install Visual Studio or some other compiler d) Compile and install the MQSeries Perl module and then finally... e) run the script. Of course an NT shop might have some or all of this environment already set up. That being said, I previously posted a Perl script for a similar request at http://www.t-rob.net/Downloads/MQAge.zip The script accepts a queue name but defaults to the DeadQ. You pass in a number of days and it deletes messages older than the specified threshold. It could easily be modified to use hours instead of days. If you have Active State's Perl Dev Kit, you could even compile the script and modules into one executable. Come to think of it, I have the Perl Dev kit and would be happy to post an executable version if you want. Let me know. -- T.Rob -Original Message- From: Administrator [mailto:[EMAIL PROTECTED]] Sent: Monday, December 02, 2002 1:20 PM To: [EMAIL PROTECTED] Subject: Removal of Messages I have a message problem that I need to deal with. I have messages that can sit on my queue and get stuck there. I need to write a script that will clear messages that have been sitting on the queue over a period of time, say 100 hours. Unfortunatly my client will not set expiry on the message, so this has to be a script that I write to handle this process. I am a straight Windows NT shop. If anybody has a script that I can use to clear messages meeting this criteria I would greatly appreciate it. Thank you. Michael 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: Sec Channel Exit code
Chris, I would like a copy of the article and the code. Thanks, Sudheer -Original Message- From: MQSeries List [mailto:[EMAIL PROTECTED]]On Behalf Of Howarth, Chris Sent: Thursday, November 28, 2002 12:37 AM To: [EMAIL PROTECTED] Subject: Re: Sec Channel Exit code I wrote the article mentioned below. It has an explanation of how channel security exits work and has outline template code. You still need to plug in the actual security you choose to implement, but the article explains what each step is for, how it works and different methods of security you can plug in. If anyone wants the article and code, drop me a note. I think the link below has the first part of the article. Regards, ___ Chris Howarth CommerceQuest UK Ltd -Original Message- From: Bullock, Rebecca (CSC) [mailto:[EMAIL PROTECTED]] Sent: 27 November 2002 17:34 To: [EMAIL PROTECTED] Subject: OS/390: Channel Security Exit Wasn't someone asking a question about this very topic just a week or so ago? I just thought I'd point out that the latest issue of Mainframe Week (http://www.mainframeweek.com) has the start of a series of articles on this. It may be too late for the person with the query, but perhaps someone else would be interested. Regards, Rebecca P.S. For those of you in the U.S. --Happy Thanksgiving! Rebecca Bullock Computer Sciences Corporation Educational Testing Service Account Princeton, NJ 08541 e-mail: [EMAIL PROTECTED][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: Unsubscribe
Jon and Robert, Send unsubscription requests to [EMAIL PROTECTED] with "signoff mqseries" (no quotes, of course) in the body. No subject necessary. -Original Message-From: MQSeries List [mailto:[EMAIL PROTECTED]]On Behalf Of Jon ShearerSent: Tuesday, December 03, 2002 12.24To: [EMAIL PROTECTED]Subject: UnsubscribeUnsubscribe
Clustering on iSeries
Apologies for such a simple question but the AS/400 is as alien to me as walking on the moon. Does MQ 5.2 on the iSeries support clustering? Looking at the documentation (5th addition) it states the docs apply to 5.3 for iSeries but I haven't found anything that mentions the minimum version needed for clustering support on iSeries. Also, assuming 5.2 does support clustering can I plan on using MQExplorer to manage its cluster? Thanks, Ben
Re: Unsubscribe
Unsubscribe
Unsubscribe
Unsubscribe
Re: V5.3/V5.3.1 etc
Mark, Thanks very much for the clarification Dave 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: V5.3/V5.3.1 etc
The passport advantage software download site gave the following output when
I checked just now...
WebSphere MQ V5.3.1 Documentation, HTML eImage 2002-10-25
WebSphere MQ V5.3.1 Documentation, HTML tar eImage - Brazilian Portuguese,
2002-10-25
WebSphere MQ V5.3.1 Documentation, PDF and Info Center tar eImage - Brazili
2002-10-25
WebSphere MQ V5.3.1 Documentation, PDF and Info Center zip eImage - Brazili
2002-10-25
WebSphere MQ V5.3.1 for AIX Client eImage - Brazilian Portuguese, French, G
2002-10-25
WebSphere MQ V5.3.1 for AIX Client with SSL eImage - Brazilian Portuguese,
2002-10-25
WebSphere MQ V5.3.1 for AIX eImage - Brazilian Portuguese, French, German,
2002-10-25
WebSphere MQ V5.3.1 for HP-UX Client eImage - Brazilian Portuguese, French,
2002-10-25
WebSphere MQ V5.3.1 for HP-UX Client with SSL eImage - Brazilian Portuguese
2002-10-25
WebSphere MQ V5.3.1 for HP-UX eImage - Brazilian Portuguese, French, German
2002-10-25
WebSphere MQ V5.3.1 for iSeries Client eImage - Brazilian Portuguese, Frenc
2002-10-31
WebSphere MQ V5.3.1 for iSeries eImage - Brazilian Portuguese, French, Germ
2002-10-31
WebSphere MQ V5.3.1 for Linux for Intel eImage - Brazilian Portuguese, Fren
2002-10-25
WebSphere MQ V5.3.1 for Linux for zSeries eImage - Brazilian Portuguese, Fr
2002-10-25
WebSphere MQ V5.3.1 for Linux on Intel Client eImage - Brazilian Portuguese
2002-10-25
WebSphere MQ V5.3.1 for Linux on Intel Client with SSL eImage - Brazilian P
2002-10-25
WebSphere MQ V5.3.1 for Linux on zSeries Client eImage - Brazilian Portugue
2002-10-25
WebSphere MQ V5.3.1 for Linux on zSeries Client with SSL eImage - Brazilian
2002-10-25
WebSphere MQ V5.3.1 for Solaris Client eImage - Brazilian Portuguese, Frenc
2002-10-25
WebSphere MQ V5.3.1 for Solaris Client with SSL eImage - Brazilian Portugue
2002-10-25
WebSphere MQ V5.3.1 for Solaris eImage - Brazilian Portuguese, French, Germ
2002-10-25
WebSphere MQ V5.3.1 for Windows Client eImage - Brazilian Portuguese, Frenc
2002-10-25
WebSphere MQ V5.3.1 for Windows NT 2000 & XP eImage - Brazilian Portuguese,
2002-10-25
WebSphere MQ V5.3.1 Install Documentation, zip eImage - Brazilian Portugue
2002-10-25
WebSphere MQ V5.3.1 Install Documentation, tar eImage - Brazilian Portugues
2002-10-25
So it definitely says 5.3.1, not 5.3.0.1...
Regards
John
> -Original Message-
> From: Mark Taylor [mailto:[EMAIL PROTECTED]]
> Sent: 03 December 2002 15:55
> To: [EMAIL PROTECTED]
> Subject: V5.3/V5.3.1 etc
>
>
> Let me make one thing very clear: there is NO SUCH THING as V5.3.1
>
> For a brief time, the download images were labelled that way,
> but it was quickly corrected to say V5.3.0.1. That extra zero
> makes all the difference.
>
> The first tranche of V5.3 platforms were shipped mid-year,
> and we often refer to those as the GA1 release.
>
> Testing then continued on the extra platforms (Linux, OS/400)
> and a number of fixes were made in cross-platform code. So,
> when the second set was released ("GA2") it made sense to
> refresh the manufacturing images of the original set of
> platforms at the same time, so they were all at exactly the
> same level. New shipments of the original platforms will all,
> in effect, have CSD01 pre-applied.
>
> However you could also get the same set of code by applying
> CSD01 to a GA1 platform. You will see the CSD level included
> in inventory commands such as lslpp on AIX, wherever that's possible.
>
> Two minor complications: CSD01 isn't separately downloadable
> at the moment, because of a hitch dealing with the fact that
> it contains crypto code. We are trying to sort that out
> urgently. (I believe some people have been sent it directly,
> but can't be sure of that.) And if you want to install on
> Windows XP you must get the new level, as the earlier install
> code (which of course cannot be updated by CSD) explicitly
> refused to allow you to put it on XP.
>
> But when CSD02 arrives, you will be able to install it on top
> of a GA1 package, a GA2 package or a GA1+CSD01 package.
>
> Mark Taylor.
>
> 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
**
Click here to visit the Argos home page http://www.argos.co.uk
The information contained in this message or any of its attachments may be privileged
and confidential, and is intended exclusively for the addressee.
The views expressed may not be official policy, but the personal views of the
originator.
If you are not the intended addressee, any disclosure, reproduction, distribution,
dissemination or use of this communication is not authorised.
If you have received this message in error, please advise the sender by using your
reply facility in youe e-mail software.
All messages sent and received by Argos Ltd are monitored for virus, high risk file
extensions, and inappropriate content.
V5.3/V5.3.1 etc
Let me make one thing very clear: there is NO SUCH THING as V5.3.1
For a brief time, the download images were labelled that way, but it was
quickly corrected to say V5.3.0.1. That extra zero makes all the
difference.
The first tranche of V5.3 platforms were shipped mid-year, and we often
refer to those as the GA1 release.
Testing then continued on the extra platforms (Linux, OS/400) and a number
of fixes were made in cross-platform code. So, when the second set was
released ("GA2") it made sense to refresh the manufacturing images of the
original set of platforms at the same time, so they were all at exactly the
same level. New shipments of the original platforms will all, in effect,
have CSD01 pre-applied.
However you could also get the same set of code by applying CSD01 to a GA1
platform. You will see the CSD level included in inventory commands such as
lslpp on AIX, wherever that's possible.
Two minor complications: CSD01 isn't separately downloadable at the moment,
because of a hitch dealing with the fact that it contains crypto code. We
are trying to sort that out urgently. (I believe some people have been sent
it directly, but can't be sure of that.)
And if you want to install on Windows XP you must get the new level, as the
earlier install code (which of course cannot be updated by CSD) explicitly
refused to allow you to put it on XP.
But when CSD02 arrives, you will be able to install it on top of a GA1
package, a GA2 package or a GA1+CSD01 package.
Mark Taylor.
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: Archive log block size
> > It would have been nice if IBM (also) provided the info as a SupportPac. Well, the info is in the System Setup guide in 5.2. I checked the 5.3 manual too. It seems that the default goes from 20480 (optimal for 3380) to 28672, the maximum, optimal for logging to tape. And a disaster for logging to 3390. Except from a hardware vendors viewpoint ;-). Cheers, Jan. -/ /&Jan van Kemenade \&www.cressida.info -\ 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: Sec Channel Exit code
Chris, Could you send me the article and code. Thanks David -Original Message- From: Howarth, Chris [mailto:[EMAIL PROTECTED]] Sent: Thursday, November 28, 2002 2:37 AM To: [EMAIL PROTECTED] Subject: Re: Sec Channel Exit code I wrote the article mentioned below. It has an explanation of how channel security exits work and has outline template code. You still need to plug in the actual security you choose to implement, but the article explains what each step is for, how it works and different methods of security you can plug in. If anyone wants the article and code, drop me a note. I think the link below has the first part of the article. Regards, ___ Chris Howarth CommerceQuest UK Ltd -Original Message- From: Bullock, Rebecca (CSC) [mailto:[EMAIL PROTECTED]] Sent: 27 November 2002 17:34 To: [EMAIL PROTECTED] Subject: OS/390: Channel Security Exit Wasn't someone asking a question about this very topic just a week or so ago? I just thought I'd point out that the latest issue of Mainframe Week (http://www.mainframeweek.com) has the start of a series of articles on this. It may be too late for the person with the query, but perhaps someone else would be interested. Regards, Rebecca P.S. For those of you in the U.S. --Happy Thanksgiving! Rebecca Bullock Computer Sciences Corporation Educational Testing Service Account Princeton, NJ 08541 e-mail: [EMAIL PROTECTED][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: Archive log block size
Back around Feb, 2001, IBM issued a series of informational APARs that described a wide range of tuning recommendations. APAR PQ31226 contained the following: BLKSIZE Specifies the block size of the archive log data set. The block size you specify must be compatible with the device type you specify in the UNIT parameter. The parameter must be in the range 4 097 through 28 672. The value you specify is rounded up to a multiple of 4 096. The default is 20 480. This parameter is ignored for data sets that are managed by the storage management subsystem (SMS). If the archive log data set is written to DASD, you are recommended to choose the maximum block size that will allow 2 blocks per track. For example, for a 3390 device, you should use a block size of 24 576." It would have been nice if IBM (also) provided the info as a SupportPac. Jan van Kemenade cc: Sent by: Subject: Archive log block size MQSeries List 12/03/2002 04:43 AM Please respond to MQSeries List Hi, For those who still believe in 'tuning'... The default blocksize for Archive logs is 20480 (5*4096). No doubt chosen by IBM because this represents halftrack blocking on a 3380 disk (with lrecl=4096). But since 3390's have a larger track size, an optimum blocksize would be 24576(6*4096). Saves about 1/6 of the allocated archive log Cheers, Jan. -/ /&Jan van Kemenade \&www.cressida.info -\ 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: WMQI V2.1 vs. MQSI V2.0.2
Integrator Broker was released as a pricing marketing tool. It is the base WMQI with out, at the least, the NNSY support. bobbee From: Michael F Murphy/AZ/US/MQSolutions <[EMAIL PROTECTED]> Reply-To: MQSeries List <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] Subject: Re: WMQI V2.1 vs. MQSI V2.0.2 Date: Mon, 2 Dec 2002 13:13:34 -0700 And to add to this, what is with the new name? Now I see both WebSphere MQ Integrator and WebSphere MQ Integrator Broker. Does the term "broker" make it different? I can see versions with and without "broker" in the name, both version 2.1, but if you click on the link to either download it takes you to the same site for WebSphere MQ Integrator Broker. Are these different products? Mike Murphy Sr. Middleware Consultant MQ Solutions, LLC http://www.mqsolutions.com [EMAIL PROTECTED] wrote: Date Recieved: 12/02/2002 10:46:19 AM To: [EMAIL PROTECTED] cc: Bcc Subject: WMQI V2.1 vs. MQSI V2.0.2 I've searched the IBM website for documents comparing these two version, but have found none which directly address the differences. Have I missed something ? Does anyone know of any document which summarizes the differences ? Thanks ! Phil This communication is for informational purposes only. It is not intended as an offer or solicitation for the purchase or sale of any financial instrument or as an official confirmation of any transaction. All market prices, data and other information are not warranted as to completeness or accuracy and are subject to change without notice. Any comments or statements made herein do not necessarily reflect those of J.P. Morgan Chase & Co., its subsidiaries and affiliates. 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 _ The new MSN 8: advanced junk mail 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
Archive log block size
Hi, For those who still believe in 'tuning'... The default blocksize for Archive logs is 20480 (5*4096). No doubt chosen by IBM because this represents halftrack blocking on a 3380 disk (with lrecl=4096). But since 3390's have a larger track size, an optimum blocksize would be 24576(6*4096). Saves about 1/6 of the allocated archive log Cheers, Jan. -/ /&Jan van Kemenade \&www.cressida.info -\ 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 V2.1 vs. MQSI V2.0.2
Title: Message Hi Michael, WMQI = MQSI + NEON WMQI BROKER = MQSI - NEON Emile Kearns Office telephone no: +27(0)114586670 SOFTWARE FUTURESthe business advantageProud member of MGXwww.softwarefutures.com -Original Message-From: Michael F Murphy/AZ/US/MQSolutions [mailto:[EMAIL PROTECTED]] Sent: 02 December 2002 10:14To: [EMAIL PROTECTED]Subject: Re: WMQI V2.1 vs. MQSI V2.0.2And to add to this, what is with the new name? Now I see both WebSphere MQ Integrator and WebSphere MQ Integrator Broker. Does the term "broker" make it different? I can see versions with and without "broker" in the name, both version 2.1, but if you click on the link to either download it takes you to the same site for WebSphere MQ Integrator Broker. Are these different products? Mike MurphySr. Middleware ConsultantMQ Solutions, LLChttp://www.mqsolutions.com[EMAIL PROTECTED] wrote: Date Recieved: 12/02/2002 10:46:19 AM To: [EMAIL PROTECTED] cc: Bcc Subject: WMQI V2.1 vs. MQSI V2.0.2I've searched the IBM website for documents comparing these two version,but have found none which directly address the differences. Have I missedsomething ?Does anyone know of any document which summarizes the differences ?Thanks !PhilThis communication is for informational purposes only. It is not intended asan offer or solicitation for the purchase or sale of any financial instrumentor as an official confirmation of any transaction. All market prices, dataand other information are not warranted as to completeness or accuracy andare subject to change without notice. Any comments or statements made hereindo not necessarily reflect those of J.P. Morgan Chase & Co., itssubsidiaries and affiliates.Instructions for managing your mailing list subscription are provided inthe Listserv General Users Guide available at http://www.lsoft.comArchive: http://vm.akh-wien.ac.at/MQSeries.archive
