The link to the MQ Conversion FAQ on page
http://www-3.ibm.com/software/integration/mqfamily/support/faqs/all_ver.html
#faqa7
Appears to be a broken link. Does anyone have a softcopy of this?
Could one of the IBMers inform the MQ web site owner?
Thanks,
David C. Partridge
Security and MQ
HI Vitaliy
The answer to question 2 is that you *must* use the Java/JMS stuff that
comes as part of 5.3.
MA88 isn't appropriate to 5.3.
Dave
-Original Message-
From: MQSeries List [mailto:[EMAIL PROTECTED] Behalf Of Vitaliy
Ilyin
Sent: 31 July 2003 04:20
To: [EMAIL PROTECTED]
Subject:
Emile, I'm not sure I understand the question.
If you're asking should I *not* make all my users members of group mqm,
then I'd say that you definitely should not.
Each user/group should be granted access to only the MQ objects they need
with the minimum level of capability they require.
Dave
This is standard LAC (Logical Access Control) discipline. If you allow
everyone to do everything, then anyone can perform a DoS (Denial of Service)
attack on your system (deleting messages, queues, queue managers or
whatever), or look at (or replace) those sensitive messages that they have
no
Take a look at support pack MA12: MQSeries for MVS/ESA - Batch trigger
monitor
http://www-3.ibm.com/software/integration/support/supportpacs/individual/ma1
2.html
Dave
Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at
1) You should *never* set pExitParms-ExitReason. That is an input field to
tell your exit why it was invoked. I would not be surprised if setting
this in your exit is what caused everything to pear shaped.
2) pExitParms-ExitResponse will have the value MQXCC_OK when your exit is
called. You
Put simply, for everything except CICS, you have to do it the hard way, by
providing your own versions of the API stubs.
For the CICS environment, MQ does supply an API crossing exit (search for
CSQCAPX in the MQ documentation)
-Original Message-
From: MQSeries List [mailto:[EMAIL
Can we load MQ version 5.3 on Microsoft Windows Server 2003?
Boldly to go where no man has gone before ...
Dave
Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at http://www.lsoft.com
Archive:
Title: Support for API exits?
Tony,
The following are the minimum levels of MQ at which IBM will support the
API crossing exit:
Solaris MQ 5.2 CSD03
Windows NT etc, AIX, HP_UX, Linux, OS/400 etc
WebSphere MQ 5.3
It was actually shipped (as against supported) on most (if not
all)the
GMO.MatchOptions only works with a Version 2 or greater MQGMO.
OS/390 only supports a Version 1 GMO.
So you are forced to reset the MD.MsgId to MQMI_NONE prior to MQGET on 390.
Dave
Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide
Oops - I was wrong about 390 support for Version 1 GMO.
OS/390 at 5.3 does support Version 3 GMO. I was sure that it didn't at
some stage in the past. When did that change? Was it between 2.1 and 5.2 or
between 5.2 and 5.3?
Sorry for misinformation
Dave
Instructions for managing your
I'm pretty sure that the API crossing exit *will* do it for you, as
regardless of the language the client is written in, by the time the MQ call
is issued at the server, it is all one ...
For you clients, you should be interested in MQXE_MCA_SVRCONN type
invocations.
Why not try to use the
Sounds to me like the NT guys didn't set up a listener for the new QM ...
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
Welcome the FAQNRA (Frequently Asked Questions Never Really Answered)
section of the list!
The TSH is (for some reason) a control block that IBM consider to be
confidential and something they don't want us to know about. There is
certain information about its contents (in particular byte 10) in
Blush - you did say you had configured syncpoint ...
Sorry
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
So long as this is application driven segmentation, and you restrict your
segments to the order of 28-30kB (I'd err on the low end) this should work.
Assuming TCP/IP transport the buffer used by the channel is 32kB, but you
need to add some space for the marshalled API parameters.
To avoid loss,
you need a personal certificate (MQ does not seem to use Server type
certificates at all).
Hmmm I accept that it will work with a Verisign Class 1 certificate.
The question is how much trust you are prepared to put in a certificate
where the process of identification is only does the
I'd hazard two guesses
1) On distributed, multiple message exits are allowed. So the specification
of the message exits is in an array hung off MQCD.MsgExitPtr, and the number
of message exits in in MQCD.MsgExitsDefined. If isn't in MQCD.MsgExit
2) Are you looking at these fields at MQXR_INIT
I assume that when you say document you mean something like an IDOC?
Using MQ for data this big can give you all sorts of problems, but one thing
you can do is to use multiple channels with different TQs etc, so that your
large messages don't block the small guys. I don't think you need to go
considerations are valid for Unix and (if I am not mistaken)
Windows. I am not sure about other platforms.
Hope this will help,
Pavel
David C.
PartridgeTo:
[EMAIL PROTECTED]
[EMAIL PROTECTED]cc
Paul,
No, I don't think it will. The key point here is your second paragraph
about the OAM not being called if the caller is mqm. This means that mqm
can do *anything* to those config queues and their content.
David
Instructions for managing your mailing list subscription are provided in
the
Paul,
That makes sense - I guess that access to root and Windows Admin users also
poses a similar issue - use of things like sudo and similar tools for
Windows (do they exist) could be used to limit and or log super user access.
Thanks
Dave
Instructions for managing your mailing list
And this doesn't address the /var/mqm issue - and use of the sticky bit
(restricted deletion bit).
PS I thought that MQ installed in /opt/mqm, or is that different on AIX?
Dave
Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at
Emile,
Are you prepared to share what file this might be? Is it shipped by MQ
install with a mask of 777 or has this happened since? Is this in
/var/mqm/ or /opt/mqm/
David
Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide
Any user needs to be able to create files in these directories in order for
the MQ code to work. Is the issue that you are concerned about a DOS
attack where a malicious user does an rmdir?
The permissions I see on my Linux MQ 5.3 system for (most of) these
directories are:
drwxrwsrwx
So (for
Is it possible to use setmqaut to limit the access to a queue so that
members of group mqm do *not* have update access?
e.g. setmqaut -m qmgr1 -n a.b.* -t q -p mqm -put -get
Regards,
David C. Partridge
Security and MQ Products Manager
Primeur Group
Tel: +44 (0)1926 511058
Mobile: +44 (0)7713
Emile,
I don't quite understand the question. SSL supports LDAP for retrieving
CRLs, but I don't think that's what you're getting at. Do you think you
could give us a bit more to chew on?
Thanks
Dave
Instructions for managing your mailing list subscription are provided in
the Listserv
Rick,
Hmmm... that sounds like it *is* possible, but use at your own risk - can
anyone confirm?
Thanks
David
Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at http://www.lsoft.com
Archive:
Pavel,
Yes, I just tried to remove put and get authority from a queue for mqm and
found that any user of group mqm could still put/get messages. So until
told otherwise, it looks like mqm IS GOD (as far as MQ is concerned) and
can't be restricted (same applies on windows if I try to restrict a
My copy of the iSeries APG for ILE RPG says:
BUFLEN (10-digit signed integer) - input
Length of the message in BUFFER.
Zero is valid, and indicates that the message contains no application data.
The upper limit for BUFLEN depends on various factors:
If the destination queue is a shared queue, the
If you're getting a segmentation fault running mqlicense.sh, methinks 'tis
time to open an incident with your friendly local IBM support centre.
Dave
Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at http://www.lsoft.com
FWIW it does appear to work just fine on RHL8.
HTH
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
No, I don't think you can suppress the channel creation. That has
already happened, but you could (e.g.) modify it so it won't work.
E.g. setting a security exit that always refuses connection, or modify the IP
address of the other end ... All sorts of options
here!
Dave
That sounds like a bug in the LU6.2 implementation on VMS to me. IIRC all
the fields in an FMH5 are architected to be EBCDIC (but hey it was a LONG
time ago, and I certainly don't have the manuals to confirm that now).
Dave
Instructions for managing your mailing list subscription are provided
Could any of the Hursley MVS mavens give a clue as to what we should look
for in terms of an error in our code if we get MQRC_NOT_CONVERTED on a call
to CSQAXDX? Environment is batch MQ 5.2 (with the PTF that supplies
CSQAXDX) and MQ 5.3
Regards,
David C. Partridge
Security and MQ Products
-DALL_SOURCE on the compile command line should do it.
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
Title: MQ Client Channel Security Products?
Each to their own view I guess, and I will admit to being biased
:-)
The SSL 5.3 song works well if you're all 5.3 and all TCP/IP, but what
about other transports such as SNA, or those with mixed networks or non 5.3 QMs
(lots of folks still run
Title: MQ Client Channel Security Products?
No, compression isn't being taken out of DSMQ. DCMQ is a
complementary product to DSMQ, itdoes end to end compression as messages
are put to or gotten from the queues. DSMQE2E can process (if so
configured as to allow it) messages sentby DCMQ are
The sample exit DOES dump the connect options on the CONNX.Is the
problem one of interpreting them? As far as I remember, in the case of an
MQI client the CONNX is issued by the MCA based on the MQCONN issued at the
client. You should see the CONNX call in the trace for the exit if you
I don't think that what he describes is in any way related to MQ triggering.
The Java addListener isn't concerned with MQ, but with Java events. AFAIK
you'll need to go through the regular process definition to invoke something
like a .bat file or shell script to crank up java and run the .jar
Peter,
The one thing I still do not understand is why a 75K NP message
going thru FAST channels only does not require disk. If the default buffer
is 64K, does not the 75K message being placed into the XMIT queue leaving
the HUB require disk?
I think I can answer that. If the message is being
I thought that it was done in 5.2, but as they say:
The second thing that goes as you get older is your memory. I can't
remember what the first thing was!
I guess that's one for the Hursley folks to comment on.
Dave
Instructions for managing your mailing list subscription are provided in
the
As far as I know ProtectMQ is a channel exit solution, rather than an
application to application (end to end) solution, and therefore probably not
relevant to this particular discussion. That said however, thanks for
mentioning it.
Dave
Instructions for managing your mailing list subscription
Nice summary. SSL is (probably) not appropriate here for encryption
purposes, and an application to application encryption product such as
Primeur DSMQ E2E (preferred by me anyway, but then I'm biased, as I designed
it), Candle MQSecure, or Tivoli AMBI is more appropriate.
Alternatives to SSL
A sound case here for two different channels and TQs both connecting the two
QMs. One for NP messages with NPMSPEED(FAST), and the other for persistent.
Needs a bit of management of QR definitions, and make sure that different
dest QR are use for NP versus P messages but that's an MQ
Or you can use an external vendor's product that explicitly authenticates
the users who connect to the QM in the DMZ - of course I would recommend
our's which is Primeur's DSMQ product. There are other vendors with
solutions in this space - Candle MQSecure and of course there is MQ 5.3 SSL
with
Be aware that if you do this, any client will be able to connect and run
with the authority of that account.
Dave
-Original Message-
From: MQSeries List [mailto:[EMAIL PROTECTED] Behalf Of Andrew
Miller
Sent: 03 June 2003 09:30
To: [EMAIL PROTECTED]
Subject: Re: MQClient authorization
Well almost - if there is a security exit, this can (if it so wishes)
override the MCAUSER setting.
Cheers
Dave
-Original Message-
From: MQSeries List [mailto:[EMAIL PROTECTED] Behalf Of Wyatt,
T. Rob
Sent: 29 May 2003 17:01
To: [EMAIL PROTECTED]
Subject: Re: JMS Client UserID Password
, Hconn1 ?
Will only Msg1 be committed ? Or will both Msg1 and Msg2 will be committed
together with the whole UOW ?
Regards,
David C. Partridge
Security Products Manager
Primeur Group
Tel: +44 (0)1926 511058
Mobile: +44 (0)7713 880197
Instructions for managing your mailing list subscription
I think the -f option may be new for 5.3. It's shown in a different colour
in the Information Centre which normally indicates a change.
Dave
Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at http://www.lsoft.com
Archive:
Hi Andrea,
Rather than repeat similar related postings, I'd suggest that you look back
on earlier posts I've made on this sort of subject, and also take a good
read at:
http://www-3.ibm.com/software/ts/mqseries/support/faqs/convert.html
and of course appendix H of the Application Programming
Sounds like you tried to do a get with convert and the message format was
MQFMT_NONE
David
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
they will put the
details up soon.
Regards,
David C. Partridge
Security Products Manager
Primeur Group
Tel: +44 (0)1926 511058
Mobile: +44 (0)7713 880197
Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at http://www.lsoft.com
Archive
Are you running your Windows qmgr with CP 1252? What are you using to
determine the correctness of the code points to which the conversions are
made?
I posted on this subject recently (14th Jan and 22 Jan)
Cheers
Dave
Instructions for managing your mailing list subscription are provided in
Yes, there is! But its not documented!!! It may be only marginally
supported. It was released as a PTF to MQ 5.2 for MVS, and is in base 5.3.
The function has been in the base of V5 for the distributed platforms for a
while.
Given the status of this stuff, I think its most appropriate if the
suggest that any solution you adopt be based on
cryptographic authentication of credentials. Both our channel exit based
solution and IBM's SSL solution use this approach.
Regards,
David C. Partridge
Security Products Manager
Primeur Group
Tel: +44 (0)1926 511058
Mobile: +44 (0)7713 880197
exits and Security exits were in place (with tracing active), but were
not driven.
Any of the channel mavens got any ideas or seen this before and know what
the problem might be?
Regards,
David C. Partridge
Security Products Manager
Primeur Group
Tel: +44 (0)1926 511058
Mobile: +44 (0)7713 880197
Thanks Paul, I've passed that on the customer - the strange thing is that
there were no FDCs nor any entries in the MQ error logs. This probably
just goes to further strengthen the case for some sort of environment
problem.
Dave
-Original Message-
From: MQSeries List [mailto:[EMAIL
was not the person who set that Linux QM to have a CCSID of 1208).
Don't know if this is a problem with latest MQ5.3 on OS/390.
In general probably a bad idea to set QM default codepage to any potentially
multi-byte code set.
Regards,
David C. Partridge
Security Products Manager
Primeur Group
Tel
It's now some while since 5.3 GA2 (a.k.a. 5.3.0.1) was shipped which
purportedly contains the fixes for CSD01. Are the IBM guys able to give
some guidance on when CSD01 for 5.3 will be made available for download?
Regards,
David C. Partridge
Security Products Manager
Primeur Group
Tel: +44 (0
Can't comment on SCSQANLx as 390 isn't my strongest platform. However, the
use of a multi-byte code set as the QM's default CCSID will almost certainly
cause problems as the MQ control blocks (MD etc) are fixed length and assume
one byte per character. This means that you cannot use a
Either set the MQMD.CodedCharSetId to 1252 prior to each get with convert,
or alter the qmgr to have a default ccsid of 1252 and set
MQMD.CodedCharSetId to be MQCCSI_Q_MGR prior to each get with convert.
David
Instructions for managing your mailing list subscription are provided in
the Listserv
Title: Message
What did you use to view the data that told you that the "wrong"
characters were used in the conversion at the MVS end? What
hexadecimal values did they get converted to? For CCSID 1147 (297 plus
Euro) they should be x'90' for [ and x'b5' for ]. If these are the
code points
Why are you even calling MQXCNVC when you have already invoked get with
convert which will have already done conversion. If you want to convert
directly to 819 rather than the qmgr CCSID (I assume 850) then just set
md.CodedCharSetId = 819 prior to the get. If the conversion isn't
producing the
Paul,
Does this (channel pools) also apply to the other 5.3 distributed platforms?
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
But Deborah specifically said that the message format was set to MQFMT_NONE
(well actually she said blank, but that's the same), so no conversion should
apply. I suspect some form of application error reading or writing the
file (e.g. file read as text rather than binary).
Dave
Instructions
The data at the MVS end is not necessarily in the CCSID that you think it
is. I assume that the data is being sent as CCSID 500? Is that correct?
If so make darn sure that the accented characters and braces are actually at
the code points that match CCSID 500. It may be that you are using one
Can you run as a Java application (as distinct from applet)? Java
applications can do (just about) what they want in this regard.
David
Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at http://www.lsoft.com
Archive:
IMHO it's a bad idea to use this approach. It gives you no admin
flexibility to redirect messages, and I think you need to authorise all
users doing it to be able to write directly to the XMIT queues.
Far better to ALWAYS use a QREMOTE definition.
That said however, you still get the problem
True and also SYSTEM.ADMIN.SVRCONN being open to the world for MQExplorer
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
110 is:
AMRC_TRANSPORT_NOT_AVAILABLE 110
Completion code 2 (AMRC_ERROR) together with reason code 110
(AMRC_TRANSPORT_NOT_AVAILABLE) returned by amInitialize or amSesOpen (or the
equivalent in COBOL, C++ and Java) normally indicates that the underlying
WebSphere MQ queue manager the AMI is
,
David C. Partridge
Security Products Manager
Primeur Group
Tel: +44 (0)1926 511058
Mobile: +44 (0)7713 880197
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
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
-qnamemangling=v5
Heaven help anyone who needs to build an application using libraries built
with both V5 and V6 of the compiler.
Dave
-Original Message-
From: David C. Partridge [mailto:[EMAIL PROTECTED]]
Sent: 22 November 2002 15:53
To: MQSeries List
Subject: RE: Problem building C
Kevin,
Dancing naked inside a ring of old 360 mainframes ...
You were doing it wrong, which is why you were alone! Everyone else was
dancing in a ring of 1401s and 1130s.
Dave
Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available
An 0C4 as you probably know is equivalent to a segmentation fault on Unix or
a C005 on Windows. Make sure that you check all error returns, and that
any mallocs etc return a non-zero address.
Dave
Instructions for managing your mailing list subscription are provided in
the Listserv General
Hmmm ... This one doesn't seem to be in the JMS Exception Messages section
of the Using Java manual. Over to IBM I think.
Dave
Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at http://www.lsoft.com
Archive:
Do you mean
if (0 == memcmp(pmqmd-ApplIdentityData,
71 - MQ Monitor,
sizeof(pmqmd-ApplIdentityData)
)
{
strcpy(pmqcd-MCAUserIdentifier, mqprog );
}
Dave
Instructions for managing your mailing list subscription are provided in
Of course what I really meant to say was:
Did you mean:
static const char * const Mon71 = 71 - MQ Monitor;
static const char * const mqprog = mqprog;
if (0 == memcmp(pmqmd-ApplIdentityData,
Mon71,
min (sizeof(pmqmd-ApplIdentityData), strlen(Mon71))
)
No version of MQ for OS/390 or z/OS supports segmentation, though version 5
does support conversion of the MDE, so you can do you own segment
reassembly.
Dave
Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at
The plot thickens ...
The prototype for ImqObj::setOpenOptions in imqobj.h looks like:
ImqBoolean setOpenOptions ( const MQLONG );
and that for ImqCac::read in imqcac.h looks like:
ImqBoolean read ( const size_t, char * );
and the functions exported by the library match these signatures.
Been there, tried that - largely OK so long as you don't want to use the
C++ stuff. Standard MQI calls work ok.
Dave
but event that method is not found. It seems like methods
having MQLONG parameters are not found.
Has anyone seen this?
Regards,
David C. Partridge
Security Products Manager
Primeur Group
Tel: +44 (0)1926 511058
Mobile: +44 (0)7713 880197
Instructions for managing your mailing list subscription
GAK! MQINQ against 700 queues every 15secs Even at a cost of 1mS per MQINQ,
that's 700mS every 15 secs or put another way 14 per cent. I think this
will HURT.
Cheers
Dave
Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at
I'm fairly sure that 5.3.1 is just 5.3 with some changes to support Win XP.
I think CSD01 will be available later.
Cheers
Dave
Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at http://www.lsoft.com
Archive:
Why not do what our free file transfer over MQ tool (XSP) does - which I
think is to use the correlid.
Or of course instead of writing your own, just grab the code from our web
site:
http://www.primeur.com/products/xsp/xsp.html
Dave
-Original Message-
From: MQSeries List
was:
A Channel Stop of a retrying channel using the MQMC Channel panel caused
errors.
but it is so vague that it's hard to tell if it's relevant.
Regards,
David C. Partridge
Security Products Manager
Primeur Group
Tel: +44 (0)1926 511058
Mobile: +44 (0)7713 880197
Instructions for managing your
I know that GA2 of MQ 5.3 for Windows (with XP support) was made available
electronically on 25th October.
I believe that CSD1 is due about now, but there's nothing on the MQ fixes
web pages.
Dave
Instructions for managing your mailing list subscription are provided in
the Listserv General
If this is character data, you will need to set the format to MQFMT_STRING.
Data of MQFMT_NONE (the default) will not be converted.
Dave
Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at http://www.lsoft.com
Archive:
The issue is that the COA is sent by the queue manager with the authority of
the queue manager. The COD is sent by the queue manager with the authority
of the user identity in the MD. If this is blank, typically the OAM will
not allow the COD to be sent.
Dave
Instructions for managing your
need)!
Obviously the folks in Hursley are best placed to confirm that the
behaviour is as I stated and to comment on why it works the way it does.
Regards,
David C. Partridge
Security Products Manager
Primeur Group
Tel: +44 (0)1926 511058
Mobile: +44 (0)7713 880197
Instructions for managing your
Title: Cobol Source Code Example for AMQSBCG0
COBOL! Wassat? All real programmers do it on the bare metal
:-)
Seriously though, the code for amqsbcg0 is C code, but there is a COBOL
sample on my system called amq0gbr0.cbl which looks similarish ... I will
send it to you off line.
Dave
The TSH is documented in the IBM Confidential MQ Formats and Protocols
document :-(
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
Jonas,
Are there any message exits in the picture that might cause this? Is there
any pattern in the exact size of the messages that are damaged? Is it
possible that there is a dodgy MQSI node processing the data that messes
up occasionally? Can you prove that the message the left the other
Why would you want to have a process that had 100 open connections to a
qmgr. Shouldn't you be thinking about using some sort of thread pool
approach with work parcelled out to the threads that have connections to the
qmgr?
Dave
-Original Message-
From: MQSeries List [mailto:[EMAIL
Does anyone know which MQ stub the IMS bridge code is linked with?
Regards,
David C. Partridge
Security Products Manager
Primeur Group
Tel: +44 (0)1926 511058
Mobile: +44 (0)7713 880197
Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide
be used.
Can anyone cast some light on this issue - is what they were told by their
local IBM support team correct? If so why on earth does it work that way?
Surely the bridge could be coded to request MQGMO_CONVERT and ignore
MRQRC_FORMAT_ERROR and similar.
Regards,
David C. Partridge
Security
an impact on more than just our product.
Regards,
David C. Partridge
Security Products Manager
Primeur Group
Tel: +44 (0)1926 511058
Mobile: +44 (0)7713 880197
Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at http://www.lsoft.com
I don't have access to IBMLink. Do you think you could grab the relevant
item from there and send it too me offline.
Thanks
Dave
Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at http://www.lsoft.com
Archive:
And remember that if this is OS/390, the DEFAULT is MQPMO_SYNCPOINT!
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
201 - 300 of 316 matches
Mail list logo
