I have quite a few queue managers that do this.
I'm planning a 5.3 rollout and looking at distributing a customized version
of the MC6A or MC6B Veritas or Service Guard scripts.
They are certainly an interesting starting place as they will do progressive
levels of endmqm and kill with a specified t
Michael,
One
other approach that may not be recommended, but that does seem to work is to run
a script to delete all the IPCS resources (owned by mqm) with the ipcrm
command. If you do this before MQ comes up then it will generally come up
clean.
It's
simpler than rebuilding your qmgr
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'
se 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 MurphyMQ Solutions, LLC
"KANE, TOM M (AIT)"
<[EMAIL PROTECTED]> wrote:
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
-Original Message-
From: KANE, TOM M (AIT)
Sent: Tuesday, September 03, 2002 11:11 AM
To: 'Stefan Sievert'
Subject: RE: Supported compilers for MQ
It looks like IBM's not consistent between what they're saying in the APG
and the Quick Beginnings.
QB for WMQ 5.3 on
For those of us unfortunate enough to have MS Outlook.
It would appear that you can configure Outlook to send a custom reply to
everyone, and have a rule prior to that which says only move the message
from the listserv to another folder. Then in the rule that moves, say not
to process further rul
