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

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).

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

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

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

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

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

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

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

Unsubscribe

Unsubscribe

Re: Unsubscribe

Unsubscribe

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

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

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

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

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]

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]

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

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

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: