Interesting this.. I use MQXCC_CLOSE_CHANNEL and this just 'closes' the
channel instance involved, all other active CLNTCONNs continue to run
without any issue. I haven't used QXCC_SUPPRESS_FUNCTION.. perhaps I
should.
One other interesting/confusing aspect is that if the connection attempt is
A question re Z/OS security exits.
Does anyone know if exits are invoked as MQXR_TERM when a channel initiator
is shut-down?
The question relates to the requirement to free gotten storage that is
allocated on the first MQXR_INIT and is then used by all exit invocations
thereafter. It would be
Adding SCSQAUTH to the LINKLIST is I think overkill for just what you need
to do. If you issue a..
TSOLIB ACT DSNAME('whatever.SCSQAUTH')
Before you go into ISPF, e.g. in your profile CLIST member for example, you
will get the allocation as needed without the LINKLIST entry.
Robert Sloper
I wish IBM was that consistent... On Z/OS the shared queues require the use
of DB2.
Robert Sloper
Data Center: Middleware
Phone: (613) 837 9879
[EMAIL PROTECTED]
Paul Clarke
[EMAIL PROTECTED] To:[EMAIL PROTECTED]
There are sample programs in the install libs..
C program SCSQC37S(CSQ4BCK1)
Cobol SCSQCOBS(CSQ4BVK1)
Just Compile and use or modify to suit.
Robert Sloper
Data Center: Middleware
Phone: (613) 837 9879
[EMAIL PROTECTED]
Hill, Dave
Take a look at the message in the OS/390 DLQ, it will be written there when
you get the 294. This will show you the actual length of the message you
are writing and you can see perhaps why you have the buffer overflow.
Beinert, William
[EMAIL
We have a client who operate on VSE v2.6 that we want to connect in to our
Z/OS MQSeries systems.
This client has a CICS system that they want to be able to MQPUT
messages from. They do not have MQSeries server but do want to use the
available VSE MQSeries Client interface. We have found that we
/10/03 04:50 PM
Please respond to
MQSeries List
If you issue the command directly to the subsystem, it works when the queue
manager is down.
- Bruce Giordano
Robert X. Sloper
I tried to use the new Z/OS V5.3 command REFRESH QMGR TYPE(EARLY) and got
a
CSQ9036E MQ KEYWORD TYPE PARAMETER 'EARLY' NOT ALLOWED WHEN QUEUE
MANAGER IS ACTIVE.
And if I try it when the Qmgr is down I get an MQCONN error (not a
surprise).
I did RTFM and can't find any reference to how this
OS/390...
MQ/CICS bridge...
1.Allow applications to set expiry on the reply message
2.Have the ability to request that the CKBP transaction issue a LINK
with SYNCONRETURN
3.Break the affinity between CKBR and CKBP so that they can run in
separate CICS regions
4.Allow the queue
I have not used this trigger monitor but the nomal approach would be to get
disable the queue that the trigger monitor is polling.
Barney
Perhaps you could post the content of your MSGUSR sysout from the CICS
region around the abend. As was said before, a bad message should not
terminate the bridge monitor (CKBR) but will terminate the bridge task
(CKBP), there is a separate CKBP for each message received.
Any failure in a CKBP
He only did that when he was young, so much younger than today.
Robert Broderick
robertbroderick@HOTM To:[EMAIL PROTECTED]
AIL.COM cc:
Sent by: MQSeries Subject: Re: HELP
1.Triggering the CKBR transaction is how we start the bridge.
2.Don't understand why clustering would be an issue.
3.The bridge monitor does not fail on much, your examples are I think
for failures of bridge tasks i.e. CKBPs.
4.Scrape the console messages and page if the bridge
if there are still messages on the queue?
-Original Message-
From: Robert X. Sloper [SMTP:[EMAIL PROTECTED]]
Sent: Wednesday, January 08, 2003 9:38 AM
To: [EMAIL PROTECTED]
Subject: Re: CICS DPL Bridge Questions?
1.Triggering the CKBR transaction is how we start the bridge
You can have multiple CKBR transactions running, each against a different
queue if you wish. You don't need a different transaction name, just plain
ol' CKBR will do. The monitor will 'watch' the queue that the request
message is written to, I assume you are triggering the CKBR when a message
16 matches
Mail list logo
