Re: MQ/CICS and LU6.2
I understand what you typed and I couldn't find any reference (in the MQ doc)
to LU6.2 communication between MQ Address spaces using LU6.2 without CICS. I
have my MQs using TCP/IP, but that's off-topic. The ACCESSMETHOD(XM)is
specified in the connection resource definition in the CICS region. If CICS
regions are not going to connect, that specification is useless.
Ernest Roberts
IT - Sr Sys Prog
MBUSA, LLC
- Forwarded by Ernest Roberts/171/DCAG/DCX on 06/13/2003 12:44 PM -
Bruce Giordano <[EMAIL PROTECTED]>
Sent by: MQSeries List <[EMAIL PROTECTED]>
06/13/2003 12:03 PM
Please respond to MQSeries List
To: [EMAIL PROTECTED]
cc:
Subject: Re: MQ/CICS and LU6.2
I guess you're misunderstanding what I'm saying. If you use IRC, using
ACCESSMETHOD(XM) then CICS will use cross memory services for its
communication between the CICS regions. I'd also bet large amounts of
money that the CICS adapters for DB2 and MQSeries are also using cross
memory services to communicate to their address spaces. The reason you
have to Open the IRC facility before starting the MQSeries CICS adapter is
that it has a problem if a cross memory environment has already been
established. It is the MQSeries CICS adapter that would have already
established this environment for its use. I believe the same issue exists
with the CICS adapter for DB2.
- Bruce Giordano
EARmerc Roberts
<[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
cc:
Sent by: MQSeries List Subject: Re:
MQ/CICS and LU6.2
<[EMAIL PROTECTED]>
Friday June 13, 2003 11:29 AM
Please respond to MQSeries List
CICS, through DFHIRP, establishes cross-memory links to other CICS region
on
the same LPAR. In a SYSPLEX, DFHIRP can manage communication between CICS
regions via XCF(cross-system communication facility) or through VTAM. For
CICS
systems on remote LPARs, DFHIRP will use VTAM.
This has nothing to do with MQ or DB2.
DFHIRP resides in the LPA. The IRC referred to has to do with connecting
two
MQs using two CICS as the connectors, i.e., Distributed queuing using CICS
ISC(LU6.2), with the MQs connected to their respective CICS regions using
the
adaptor. IRC must be open for the CICS regions to communicate to each
other,
not for MQ-to-CICS connectivity.
>From the z/OS Setup Guide for WMQ v5.3:
" Note: You can use the CICS adapter in a CICS system that has interregion
communication (IRC) to remote CICS systems. If you are using IRC, you
should
ensure that the IRC facility is OPEN before you start the adapter. This is
essential if the IRC access method is defined as cross memory, that is,
ACCESSMETHOD(XM). " - the communication referred to is CICS-to-CICS.
IRC
for local CICS systems to communicate using cross-memory(XM) services.
Ernest Roberts
IT - Sr Sys Prog
MBUSA, LLC
- Forwarded by Ernest Roberts/171/DCAG/DCX on 06/13/2003 10:57 AM -
Bruce Giordano <[EMAIL PROTECTED]>
Sent by: MQSeries List <[EMAIL PROTECTED]>
06/13/2003 09:14 AM
Please respond to MQSeries List
To: [EMAIL PROTECTED]
cc:
Subject: Re: MQ/CICS and LU6.2
I'd be very surprised if the MQSeries and DB2 adapters didn't use cross
memory services. Note for example, that if you're using IRC in your CICS
region, you have to ensure that the IRC facility is open before you start
the MQSeries adapter. This is because the CICS IRC initialization has a
problem if a cross memory environment has already been established. If you
start the MQSeries adapter first, guess who already established the cross
memory environment.
- Bruce Giordano
EARmerc Roberts
<[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
cc:
Sent by: MQSeries List Subject: Re:
MQ/CICS and LU6.2
<[EMAIL PROTECTED]>
Thursday June 12, 2003 05:47 PM
Please respond to MQSeries List
Anyone from Hursley want to clarify? The statement about Cross-memory
services
may not be true. The external resource managers are MQ or DB2, but it gets
a
bit more complicated. The RMI is actually a Task-Related User Exit.
Information
transferred from the running CICS program to the Resource Manager is via a
call
to the RMI with the information being passed through a program stub
link-edited
with the running program. I can't
Re: MQ/CICS and LU6.2
I guess you're misunderstanding what I'm saying. If you use IRC, using
ACCESSMETHOD(XM) then CICS will use cross memory services for its
communication between the CICS regions. I'd also bet large amounts of
money that the CICS adapters for DB2 and MQSeries are also using cross
memory services to communicate to their address spaces. The reason you
have to Open the IRC facility before starting the MQSeries CICS adapter is
that it has a problem if a cross memory environment has already been
established. It is the MQSeries CICS adapter that would have already
established this environment for its use. I believe the same issue exists
with the CICS adapter for DB2.
- Bruce Giordano
EARmerc Roberts
<[EMAIL PROTECTED]> To:
[EMAIL PROTECTED]
cc:
Sent by: MQSeries List Subject: Re: MQ/CICS and
LU6.2
<[EMAIL PROTECTED]>
Friday June 13, 2003 11:29 AM
Please respond to MQSeries List
CICS, through DFHIRP, establishes cross-memory links to other CICS region
on
the same LPAR. In a SYSPLEX, DFHIRP can manage communication between CICS
regions via XCF(cross-system communication facility) or through VTAM. For
CICS
systems on remote LPARs, DFHIRP will use VTAM.
This has nothing to do with MQ or DB2.
DFHIRP resides in the LPA. The IRC referred to has to do with connecting
two
MQs using two CICS as the connectors, i.e., Distributed queuing using CICS
ISC(LU6.2), with the MQs connected to their respective CICS regions using
the
adaptor. IRC must be open for the CICS regions to communicate to each
other,
not for MQ-to-CICS connectivity.
>From the z/OS Setup Guide for WMQ v5.3:
" Note: You can use the CICS adapter in a CICS system that has interregion
communication (IRC) to remote CICS systems. If you are using IRC, you
should
ensure that the IRC facility is OPEN before you start the adapter. This is
essential if the IRC access method is defined as cross memory, that is,
ACCESSMETHOD(XM). " - the communication referred to is CICS-to-CICS.
IRC
for local CICS systems to communicate using cross-memory(XM) services.
Ernest Roberts
IT - Sr Sys Prog
MBUSA, LLC
- Forwarded by Ernest Roberts/171/DCAG/DCX on 06/13/2003 10:57 AM -
Bruce Giordano <[EMAIL PROTECTED]>
Sent by: MQSeries List <[EMAIL PROTECTED]>
06/13/2003 09:14 AM
Please respond to MQSeries List
To: [EMAIL PROTECTED]
cc:
Subject: Re: MQ/CICS and LU6.2
I'd be very surprised if the MQSeries and DB2 adapters didn't use cross
memory services. Note for example, that if you're using IRC in your CICS
region, you have to ensure that the IRC facility is open before you start
the MQSeries adapter. This is because the CICS IRC initialization has a
problem if a cross memory environment has already been established. If you
start the MQSeries adapter first, guess who already established the cross
memory environment.
- Bruce Giordano
EARmerc Roberts
<[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
cc:
Sent by: MQSeries List Subject: Re:
MQ/CICS and LU6.2
<[EMAIL PROTECTED]>
Thursday June 12, 2003 05:47 PM
Please respond to MQSeries List
Anyone from Hursley want to clarify? The statement about Cross-memory
services
may not be true. The external resource managers are MQ or DB2, but it gets
a
bit more complicated. The RMI is actually a Task-Related User Exit.
Information
transferred from the running CICS program to the Resource Manager is via a
call
to the RMI with the information being passed through a program stub
link-edited
with the running program. I can't confirm that the DB2 Attach Facility uses
Cross-memory services, but to my recollection, if it does, it is something
new.
Likewise, MQ adaptor when CICS connects to the MQ subsystem. I know that
CICS
can use cross-memory services to communicate between two regions on the
same
LPAR when the connection defintions are thus specified.The Cross-memory
services being referred to earlier might simply be the use of shared
memory,
and not actually Cross-memory services. I don't believe that MQ or DB2
uses
cross-memory services, but rather shared memory.
Ernest Roberts
IT - Sr Sys Prog
MBUSA, LLC
- Forwarded by Ernest Roberts/171/DCAG/DCX on 06/12/2003 04:30 PM -
Bruce Giordano <[EMAIL PROTECTED]>
Sent by: MQSeries List <[EMAIL PROTECTED]>
06/12/2003 02:24 P
Re: MQ/CICS and LU6.2
I believe SQA is used, but I also remember that MVS subtasks are associated
with each DB2 thread, so some of the storage also comes out of the CICS address
space. I am working to confirm the same for the MQ adaptor, but am not yet
finished with my research. Since all roads lead to Hursley, and it has been
clearly established that a lot of MQ code is re-worked from DB2, I suspect some
commonalities. I am setting up an MQ Adaptor in one of my regions and plan to
monitor and dump the region to see what I can find out.
Yeah, this one made me curious.
Ernest Roberts
IT - Sr Sys Prog
MBUSA, LLC
- Forwarded by Ernest Roberts/171/DCAG/DCX on 06/13/2003 11:29 AM -
Rick Tsujimoto <[EMAIL PROTECTED]>
Sent by: MQSeries List <[EMAIL PROTECTED]>
06/13/2003 09:21 AM
Please respond to MQSeries List
To: [EMAIL PROTECTED]
cc:
Subject: Re: MQ/CICS and LU6.2
Without seeing actual code, or having a logic manual available it's a bit
of a guessing game. Of course, you could spend time running and analyzing
a GTF trace, but that's up to you.
When you mention shared memory, I would assume that you're referring to
getmain'd storage from SQA, or PLPA, basically common storage. In order to
move data from one address space to another, you would schedule an SRB in
the consumer's address space. AFAIK, scheduling SRBs is slower than CMS,
i.e. a context switch is required to dispatch the SRB, whereas CMS does
not. Also, if you wanted to move a 4MB message, it would either have to be
sliced up and sent in chunks, or you would impact common storage. So the
trade off in this case would be storage vs. performance. On the other
hand, using CMS, you could simply do a move (long) instruction.
I suspect the SRBs are still used, but I believe that the use of CMS is
preferred. That's why CICS uses CMS for MRO. I would be surprised if DB2
didn't use it for data tables that span data spaces.
But, yeah, I could be wrong.
EARmerc Roberts
cc:
Sent by: Subject: Re: MQ/CICS and LU6.2
MQSeries List
<[EMAIL PROTECTED]
en.AC.AT>
06/12/2003 05:47
PM
Please respond
to MQSeries List
Anyone from Hursley want to clarify? The statement about Cross-memory
services
may not be true. The external resource managers are MQ or DB2, but it gets
a
bit more complicated. The RMI is actually a Task-Related User Exit.
Information
transferred from the running CICS program to the Resource Manager is via a
call
to the RMI with the information being passed through a program stub
link-edited
with the running program. I can't confirm that the DB2 Attach Facility uses
Cross-memory services, but to my recollection, if it does, it is something
new.
Likewise, MQ adaptor when CICS connects to the MQ subsystem. I know that
CICS
can use cross-memory services to communicate between two regions on the
same
LPAR when the connection defintions are thus specified.The Cross-memory
services being referred to earlier might simply be the use of shared
memory,
and not actually Cross-memory services. I don't believe that MQ or DB2
uses
cross-memory services, but rather shared memory.
Ernest Roberts
IT - Sr Sys Prog
MBUSA, LLC
- Forwarded by Ernest Roberts/171/DCAG/DCX on 06/12/2003 04:30 PM -
Bruce Giordano <[EMAIL PROTECTED]>
Sent by: MQSeries List <[EMAIL PROTECTED]>
06/12/2003 02:24 PM
Please respond to MQSeries List
To: [EMAIL PROTECTED]
cc:
Subject: Re: MQ/CICS and LU6.2
It is my understanding that MQSeries does use cross-memory services as does
DB2. How else is it going to get the data between the CICS and the
MQSeries address space? The RMI is just a CICS mechanism that provides an
interface between CICS and an external resource manager. It doesn't
provide for the actual transmission of data between CICS and this external
resource manager. This is up to the team writing the adapter and will
likely be done using cross-memory services.
- Bruce Giordano
EARmerc Roberts
<[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
cc:
Sent by: MQSeries List Subject: Re:
MQ/CICS and LU6.2
<[EMAIL PROTECTED]>
Thursday June 12, 2003 01:06 PM
Please respond to MQSeries List
To my knowledge, CICS connects to local MQ subsystems using an adaptor
which is
essent
Re: MQ/CICS and LU6.2
CICS, through DFHIRP, establishes cross-memory links to other CICS region on
the same LPAR. In a SYSPLEX, DFHIRP can manage communication between CICS
regions via XCF(cross-system communication facility) or through VTAM. For CICS
systems on remote LPARs, DFHIRP will use VTAM.
This has nothing to do with MQ or DB2.
DFHIRP resides in the LPA. The IRC referred to has to do with connecting two
MQs using two CICS as the connectors, i.e., Distributed queuing using CICS
ISC(LU6.2), with the MQs connected to their respective CICS regions using the
adaptor. IRC must be open for the CICS regions to communicate to each other,
not for MQ-to-CICS connectivity.
>From the z/OS Setup Guide for WMQ v5.3:
" Note: You can use the CICS adapter in a CICS system that has interregion
communication (IRC) to remote CICS systems. If you are using IRC, you should
ensure that the IRC facility is OPEN before you start the adapter. This is
essential if the IRC access method is defined as cross memory, that is,
ACCESSMETHOD(XM). " - the communication referred to is CICS-to-CICS. IRC
for local CICS systems to communicate using cross-memory(XM) services.
Ernest Roberts
IT - Sr Sys Prog
MBUSA, LLC
- Forwarded by Ernest Roberts/171/DCAG/DCX on 06/13/2003 10:57 AM -
Bruce Giordano <[EMAIL PROTECTED]>
Sent by: MQSeries List <[EMAIL PROTECTED]>
06/13/2003 09:14 AM
Please respond to MQSeries List
To: [EMAIL PROTECTED]
cc:
Subject: Re: MQ/CICS and LU6.2
I'd be very surprised if the MQSeries and DB2 adapters didn't use cross
memory services. Note for example, that if you're using IRC in your CICS
region, you have to ensure that the IRC facility is open before you start
the MQSeries adapter. This is because the CICS IRC initialization has a
problem if a cross memory environment has already been established. If you
start the MQSeries adapter first, guess who already established the cross
memory environment.
- Bruce Giordano
EARmerc Roberts
<[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
cc:
Sent by: MQSeries List Subject: Re:
MQ/CICS and LU6.2
<[EMAIL PROTECTED]>
Thursday June 12, 2003 05:47 PM
Please respond to MQSeries List
Anyone from Hursley want to clarify? The statement about Cross-memory
services
may not be true. The external resource managers are MQ or DB2, but it gets
a
bit more complicated. The RMI is actually a Task-Related User Exit.
Information
transferred from the running CICS program to the Resource Manager is via a
call
to the RMI with the information being passed through a program stub
link-edited
with the running program. I can't confirm that the DB2 Attach Facility uses
Cross-memory services, but to my recollection, if it does, it is something
new.
Likewise, MQ adaptor when CICS connects to the MQ subsystem. I know that
CICS
can use cross-memory services to communicate between two regions on the
same
LPAR when the connection defintions are thus specified.The Cross-memory
services being referred to earlier might simply be the use of shared
memory,
and not actually Cross-memory services. I don't believe that MQ or DB2
uses
cross-memory services, but rather shared memory.
Ernest Roberts
IT - Sr Sys Prog
MBUSA, LLC
- Forwarded by Ernest Roberts/171/DCAG/DCX on 06/12/2003 04:30 PM -
Bruce Giordano <[EMAIL PROTECTED]>
Sent by: MQSeries List <[EMAIL PROTECTED]>
06/12/2003 02:24 PM
Please respond to MQSeries List
To: [EMAIL PROTECTED]
cc:
Subject: Re: MQ/CICS and LU6.2
It is my understanding that MQSeries does use cross-memory services as does
DB2. How else is it going to get the data between the CICS and the
MQSeries address space? The RMI is just a CICS mechanism that provides an
interface between CICS and an external resource manager. It doesn't
provide for the actual transmission of data between CICS and this external
resource manager. This is up to the team writing the adapter and will
likely be done using cross-memory services.
- Bruce Giordano
EARmerc Roberts
<[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
cc:
Sent by: MQSeries List Subject: Re:
MQ/CICS and LU6.2
<[EMAIL PROTECTED]>
Thursday June 12, 2003 01:06 PM
Please respond to MQSeries List
To my knowledge, C
Re: MQ/CICS and LU6.2
Without seeing actual code, or having a logic manual available it's a bit
of a guessing game. Of course, you could spend time running and analyzing
a GTF trace, but that's up to you.
When you mention shared memory, I would assume that you're referring to
getmain'd storage from SQA, or PLPA, basically common storage. In order to
move data from one address space to another, you would schedule an SRB in
the consumer's address space. AFAIK, scheduling SRBs is slower than CMS,
i.e. a context switch is required to dispatch the SRB, whereas CMS does
not. Also, if you wanted to move a 4MB message, it would either have to be
sliced up and sent in chunks, or you would impact common storage. So the
trade off in this case would be storage vs. performance. On the other
hand, using CMS, you could simply do a move (long) instruction.
I suspect the SRBs are still used, but I believe that the use of CMS is
preferred. That's why CICS uses CMS for MRO. I would be surprised if DB2
didn't use it for data tables that span data spaces.
But, yeah, I could be wrong.
EARmerc Roberts
cc:
Sent by: Subject: Re: MQ/CICS and LU6.2
MQSeries List
<[EMAIL PROTECTED]
en.AC.AT>
06/12/2003 05:47
PM
Please respond
to MQSeries List
Anyone from Hursley want to clarify? The statement about Cross-memory
services
may not be true. The external resource managers are MQ or DB2, but it gets
a
bit more complicated. The RMI is actually a Task-Related User Exit.
Information
transferred from the running CICS program to the Resource Manager is via a
call
to the RMI with the information being passed through a program stub
link-edited
with the running program. I can't confirm that the DB2 Attach Facility uses
Cross-memory services, but to my recollection, if it does, it is something
new.
Likewise, MQ adaptor when CICS connects to the MQ subsystem. I know that
CICS
can use cross-memory services to communicate between two regions on the
same
LPAR when the connection defintions are thus specified.The Cross-memory
services being referred to earlier might simply be the use of shared
memory,
and not actually Cross-memory services. I don't believe that MQ or DB2
uses
cross-memory services, but rather shared memory.
Ernest Roberts
IT - Sr Sys Prog
MBUSA, LLC
- Forwarded by Ernest Roberts/171/DCAG/DCX on 06/12/2003 04:30 PM -
Bruce Giordano <[EMAIL PROTECTED]>
Sent by: MQSeries List <[EMAIL PROTECTED]>
06/12/2003 02:24 PM
Please respond to MQSeries List
To: [EMAIL PROTECTED]
cc:
Subject: Re: MQ/CICS and LU6.2
It is my understanding that MQSeries does use cross-memory services as does
DB2. How else is it going to get the data between the CICS and the
MQSeries address space? The RMI is just a CICS mechanism that provides an
interface between CICS and an external resource manager. It doesn't
provide for the actual transmission of data between CICS and this external
resource manager. This is up to the team writing the adapter and will
likely be done using cross-memory services.
- Bruce Giordano
EARmerc Roberts
<[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
cc:
Sent by: MQSeries List Subject: Re:
MQ/CICS and LU6.2
<[EMAIL PROTECTED]>
Thursday June 12, 2003 01:06 PM
Please respond to MQSeries List
To my knowledge, CICS connects to local MQ subsystems using an adaptor
which is
essentially a program running in CICS to handle direct MQ calls from
programs
in several languages. The MQ API for CICS is the same as it is for batch.
Before the implementation of TCP/IP support within MQ, the method was to go
from MQ through the CICS adaptor to CICS, then from CICS on SYSTEM-A to
CICS on
SYSTEMB, then from CICS to MQ. No cross-memory services are used. AFAIK,
the
methodology is very similar to the DB2 API implementation for CICS. Each
CICS
region only connects to one MQ subsystem through a Resource Manager
Interface,
so logistics might get more complicated with multiple CICS and MQs on the
same
system.
Ernest Roberts
IT - Sr Sys Prog
MBUSA, LLC
Three Mercedes Drive
Montvale, NJ 07345
201-573-2619
201-573-4383 fax
866-308-3782 pager
- Forwarded by Ernest Roberts/171/DCAG/DCX on 06/11/2003 08:58 PM -
Rick Tsujimoto <[EMAIL PROTECTED]>
Sent by: MQSeries List <[EMAIL PROTECTED]>
06/11/2003 02:52 PM
Please respond to MQSeries Li
Re: MQ/CICS and LU6.2
I'd be very surprised if the MQSeries and DB2 adapters didn't use cross
memory services. Note for example, that if you're using IRC in your CICS
region, you have to ensure that the IRC facility is open before you start
the MQSeries adapter. This is because the CICS IRC initialization has a
problem if a cross memory environment has already been established. If you
start the MQSeries adapter first, guess who already established the cross
memory environment.
- Bruce Giordano
EARmerc Roberts
<[EMAIL PROTECTED]> To:
[EMAIL PROTECTED]
cc:
Sent by: MQSeries List Subject: Re: MQ/CICS and
LU6.2
<[EMAIL PROTECTED]>
Thursday June 12, 2003 05:47 PM
Please respond to MQSeries List
Anyone from Hursley want to clarify? The statement about Cross-memory
services
may not be true. The external resource managers are MQ or DB2, but it gets
a
bit more complicated. The RMI is actually a Task-Related User Exit.
Information
transferred from the running CICS program to the Resource Manager is via a
call
to the RMI with the information being passed through a program stub
link-edited
with the running program. I can't confirm that the DB2 Attach Facility uses
Cross-memory services, but to my recollection, if it does, it is something
new.
Likewise, MQ adaptor when CICS connects to the MQ subsystem. I know that
CICS
can use cross-memory services to communicate between two regions on the
same
LPAR when the connection defintions are thus specified.The Cross-memory
services being referred to earlier might simply be the use of shared
memory,
and not actually Cross-memory services. I don't believe that MQ or DB2
uses
cross-memory services, but rather shared memory.
Ernest Roberts
IT - Sr Sys Prog
MBUSA, LLC
- Forwarded by Ernest Roberts/171/DCAG/DCX on 06/12/2003 04:30 PM -
Bruce Giordano <[EMAIL PROTECTED]>
Sent by: MQSeries List <[EMAIL PROTECTED]>
06/12/2003 02:24 PM
Please respond to MQSeries List
To: [EMAIL PROTECTED]
cc:
Subject: Re: MQ/CICS and LU6.2
It is my understanding that MQSeries does use cross-memory services as does
DB2. How else is it going to get the data between the CICS and the
MQSeries address space? The RMI is just a CICS mechanism that provides an
interface between CICS and an external resource manager. It doesn't
provide for the actual transmission of data between CICS and this external
resource manager. This is up to the team writing the adapter and will
likely be done using cross-memory services.
- Bruce Giordano
EARmerc Roberts
<[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
cc:
Sent by: MQSeries List Subject: Re:
MQ/CICS and LU6.2
<[EMAIL PROTECTED]>
Thursday June 12, 2003 01:06 PM
Please respond to MQSeries List
To my knowledge, CICS connects to local MQ subsystems using an adaptor
which is
essentially a program running in CICS to handle direct MQ calls from
programs
in several languages. The MQ API for CICS is the same as it is for batch.
Before the implementation of TCP/IP support within MQ, the method was to go
from MQ through the CICS adaptor to CICS, then from CICS on SYSTEM-A to
CICS on
SYSTEMB, then from CICS to MQ. No cross-memory services are used. AFAIK,
the
methodology is very similar to the DB2 API implementation for CICS. Each
CICS
region only connects to one MQ subsystem through a Resource Manager
Interface,
so logistics might get more complicated with multiple CICS and MQs on the
same
system.
Ernest Roberts
IT - Sr Sys Prog
MBUSA, LLC
Three Mercedes Drive
Montvale, NJ 07345
201-573-2619
201-573-4383 fax
866-308-3782 pager
- Forwarded by Ernest Roberts/171/DCAG/DCX on 06/11/2003 08:58 PM -
Rick Tsujimoto <[EMAIL PROTECTED]>
Sent by: MQSeries List <[EMAIL PROTECTED]>
06/11/2003 02:52 PM
Please respond to MQSeries List
To: [EMAIL PROTECTED]
cc:
Subject: Re: MQ/CICS and LU6.2
June,
CICS accesses MQ messages using cross-memory services. It doesn't use
LU6.2. The decision to use LU6.2 (or TCP/IP) affects how remote queue
managers and/or clients talk to each other.
The SIP override specifies the queue manager name the region connects to,
plus the initq used by CKTI on CICS.
June Lawton
<[EMAIL PROTECTED] To:
Re: MQ/CICS and LU6.2
Shared Memory is a very efficient and common mode of data transfer.
Ernest Roberts
IT - Sr Sys Prog
MBUSA, LLC
- Forwarded by Ernest Roberts/171/DCAG/DCX on 06/12/2003 06:18 PM -
Rick Tsujimoto <[EMAIL PROTECTED]>
Sent by: MQSeries List <[EMAIL PROTECTED]>
06/12/2003 03:43 PM
Please respond to MQSeries List
To: [EMAIL PROTECTED]
cc:
Subject: Re: MQ/CICS and LU6.2
Ernest,
How would data be transferred to/from the MQ address space to the user's
address space, e.g. CICS, batch, TSO, etc.? Perhaps Hursley could provide
some insight. Morag, are you there?
EARmerc Roberts
cc:
Sent by: Subject: Re: MQ/CICS and LU6.2
MQSeries List
<[EMAIL PROTECTED]
en.AC.AT>
06/12/2003 01:06
PM
Please respond
to MQSeries List
To my knowledge, CICS connects to local MQ subsystems using an adaptor
which is
essentially a program running in CICS to handle direct MQ calls from
programs
in several languages. The MQ API for CICS is the same as it is for batch.
Before the implementation of TCP/IP support within MQ, the method was to go
from MQ through the CICS adaptor to CICS, then from CICS on SYSTEM-A to
CICS on
SYSTEMB, then from CICS to MQ. No cross-memory services are used. AFAIK,
the
methodology is very similar to the DB2 API implementation for CICS. Each
CICS
region only connects to one MQ subsystem through a Resource Manager
Interface,
so logistics might get more complicated with multiple CICS and MQs on the
same
system.
Ernest Roberts
IT - Sr Sys Prog
MBUSA, LLC
Three Mercedes Drive
Montvale, NJ 07345
201-573-2619
201-573-4383 fax
866-308-3782 pager
- Forwarded by Ernest Roberts/171/DCAG/DCX on 06/11/2003 08:58 PM -
Rick Tsujimoto <[EMAIL PROTECTED]>
Sent by: MQSeries List <[EMAIL PROTECTED]>
06/11/2003 02:52 PM
Please respond to MQSeries List
To: [EMAIL PROTECTED]
cc:
Subject: Re: MQ/CICS and LU6.2
June,
CICS accesses MQ messages using cross-memory services. It doesn't use
LU6.2. The decision to use LU6.2 (or TCP/IP) affects how remote queue
managers and/or clients talk to each other.
The SIP override specifies the queue manager name the region connects to,
plus the initq used by CKTI on CICS.
June Lawton
<[EMAIL PROTECTED] To:
[EMAIL PROTECTED]
GROUP.COM> cc:
Sent by: Subject: MQ/CICS and LU6.2
MQSeries List
<[EMAIL PROTECTED]
en.AC.AT>
06/11/2003 01:41
PM
Please respond
to MQSeries List
Can someone give me the steps for the following?
On the OS/390 I want to set up an LU6.2 connection between the queue
manager and one of our CICS regions. I am reading the Intercomminication
and
System Setup Guide, but I am getting a little confused.
I am assuming that I have to define an applid for the channel initiator in
SYS1.VTAMLST in addition to a conn/sess in CICS. Is this correct?
June Lawton
Information Systems
The PMA Insurance Group
[EMAIL PROTECTED]
(T) 610.397.5058
(F) 610.397.5311
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
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: MQ/CICS and LU6.2
Anyone from Hursley want to clarify? The statement about Cross-memory services
may not be true. The external resource managers are MQ or DB2, but it gets a
bit more complicated. The RMI is actually a Task-Related User Exit. Information
transferred from the running CICS program to the Resource Manager is via a call
to the RMI with the information being passed through a program stub link-edited
with the running program. I can't confirm that the DB2 Attach Facility uses
Cross-memory services, but to my recollection, if it does, it is something new.
Likewise, MQ adaptor when CICS connects to the MQ subsystem. I know that CICS
can use cross-memory services to communicate between two regions on the same
LPAR when the connection defintions are thus specified.The Cross-memory
services being referred to earlier might simply be the use of shared memory,
and not actually Cross-memory services. I don't believe that MQ or DB2 uses
cross-memory services, but rather shared memory.
Ernest Roberts
IT - Sr Sys Prog
MBUSA, LLC
- Forwarded by Ernest Roberts/171/DCAG/DCX on 06/12/2003 04:30 PM -
Bruce Giordano <[EMAIL PROTECTED]>
Sent by: MQSeries List <[EMAIL PROTECTED]>
06/12/2003 02:24 PM
Please respond to MQSeries List
To: [EMAIL PROTECTED]
cc:
Subject: Re: MQ/CICS and LU6.2
It is my understanding that MQSeries does use cross-memory services as does
DB2. How else is it going to get the data between the CICS and the
MQSeries address space? The RMI is just a CICS mechanism that provides an
interface between CICS and an external resource manager. It doesn't
provide for the actual transmission of data between CICS and this external
resource manager. This is up to the team writing the adapter and will
likely be done using cross-memory services.
- Bruce Giordano
EARmerc Roberts
<[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
cc:
Sent by: MQSeries List Subject: Re:
MQ/CICS and LU6.2
<[EMAIL PROTECTED]>
Thursday June 12, 2003 01:06 PM
Please respond to MQSeries List
To my knowledge, CICS connects to local MQ subsystems using an adaptor
which is
essentially a program running in CICS to handle direct MQ calls from
programs
in several languages. The MQ API for CICS is the same as it is for batch.
Before the implementation of TCP/IP support within MQ, the method was to go
from MQ through the CICS adaptor to CICS, then from CICS on SYSTEM-A to
CICS on
SYSTEMB, then from CICS to MQ. No cross-memory services are used. AFAIK,
the
methodology is very similar to the DB2 API implementation for CICS. Each
CICS
region only connects to one MQ subsystem through a Resource Manager
Interface,
so logistics might get more complicated with multiple CICS and MQs on the
same
system.
Ernest Roberts
IT - Sr Sys Prog
MBUSA, LLC
Three Mercedes Drive
Montvale, NJ 07345
201-573-2619
201-573-4383 fax
866-308-3782 pager
- Forwarded by Ernest Roberts/171/DCAG/DCX on 06/11/2003 08:58 PM -
Rick Tsujimoto <[EMAIL PROTECTED]>
Sent by: MQSeries List <[EMAIL PROTECTED]>
06/11/2003 02:52 PM
Please respond to MQSeries List
To: [EMAIL PROTECTED]
cc:
Subject: Re: MQ/CICS and LU6.2
June,
CICS accesses MQ messages using cross-memory services. It doesn't use
LU6.2. The decision to use LU6.2 (or TCP/IP) affects how remote queue
managers and/or clients talk to each other.
The SIP override specifies the queue manager name the region connects to,
plus the initq used by CKTI on CICS.
June Lawton
<[EMAIL PROTECTED] To:
[EMAIL PROTECTED]
GROUP.COM> cc:
Sent by: Subject: MQ/CICS and LU6.2
MQSeries List
<[EMAIL PROTECTED]
en.AC.AT>
06/11/2003 01:41
PM
Please respond
to MQSeries List
Can someone give me the steps for the following?
On the OS/390 I want to set up an LU6.2 connection between the queue
manager and one of our CICS regions. I am reading the Intercomminication
and
System Setup Guide, but I am getting a little confused.
I am assuming that I have to define an applid for the channel initiator in
SYS1.VTAMLST in addition to a conn/sess in CICS. Is this correct?
June Lawton
Information Systems
The PMA Insurance Group
[EMAIL PROTECTED]
(T) 610.397.5058
(F) 610.397.5311
Instruct
Re: MQ/CICS and LU6.2
Ernest,
How would data be transferred to/from the MQ address space to the user's
address space, e.g. CICS, batch, TSO, etc.? Perhaps Hursley could provide
some insight. Morag, are you there?
EARmerc Roberts
cc:
Sent by: Subject: Re: MQ/CICS and LU6.2
MQSeries List
<[EMAIL PROTECTED]
en.AC.AT>
06/12/2003 01:06
PM
Please respond
to MQSeries List
To my knowledge, CICS connects to local MQ subsystems using an adaptor
which is
essentially a program running in CICS to handle direct MQ calls from
programs
in several languages. The MQ API for CICS is the same as it is for batch.
Before the implementation of TCP/IP support within MQ, the method was to go
from MQ through the CICS adaptor to CICS, then from CICS on SYSTEM-A to
CICS on
SYSTEMB, then from CICS to MQ. No cross-memory services are used. AFAIK,
the
methodology is very similar to the DB2 API implementation for CICS. Each
CICS
region only connects to one MQ subsystem through a Resource Manager
Interface,
so logistics might get more complicated with multiple CICS and MQs on the
same
system.
Ernest Roberts
IT - Sr Sys Prog
MBUSA, LLC
Three Mercedes Drive
Montvale, NJ 07345
201-573-2619
201-573-4383 fax
866-308-3782 pager
- Forwarded by Ernest Roberts/171/DCAG/DCX on 06/11/2003 08:58 PM -
Rick Tsujimoto <[EMAIL PROTECTED]>
Sent by: MQSeries List <[EMAIL PROTECTED]>
06/11/2003 02:52 PM
Please respond to MQSeries List
To: [EMAIL PROTECTED]
cc:
Subject: Re: MQ/CICS and LU6.2
June,
CICS accesses MQ messages using cross-memory services. It doesn't use
LU6.2. The decision to use LU6.2 (or TCP/IP) affects how remote queue
managers and/or clients talk to each other.
The SIP override specifies the queue manager name the region connects to,
plus the initq used by CKTI on CICS.
June Lawton
<[EMAIL PROTECTED] To:
[EMAIL PROTECTED]
GROUP.COM> cc:
Sent by: Subject: MQ/CICS and LU6.2
MQSeries List
<[EMAIL PROTECTED]
en.AC.AT>
06/11/2003 01:41
PM
Please respond
to MQSeries List
Can someone give me the steps for the following?
On the OS/390 I want to set up an LU6.2 connection between the queue
manager and one of our CICS regions. I am reading the Intercomminication
and
System Setup Guide, but I am getting a little confused.
I am assuming that I have to define an applid for the channel initiator in
SYS1.VTAMLST in addition to a conn/sess in CICS. Is this correct?
June Lawton
Information Systems
The PMA Insurance Group
[EMAIL PROTECTED]
(T) 610.397.5058
(F) 610.397.5311
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
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: MQ/CICS and LU6.2
It is my understanding that MQSeries does use cross-memory services as does
DB2. How else is it going to get the data between the CICS and the
MQSeries address space? The RMI is just a CICS mechanism that provides an
interface between CICS and an external resource manager. It doesn't
provide for the actual transmission of data between CICS and this external
resource manager. This is up to the team writing the adapter and will
likely be done using cross-memory services.
- Bruce Giordano
EARmerc Roberts
<[EMAIL PROTECTED]> To:
[EMAIL PROTECTED]
cc:
Sent by: MQSeries List Subject: Re: MQ/CICS and
LU6.2
<[EMAIL PROTECTED]>
Thursday June 12, 2003 01:06 PM
Please respond to MQSeries List
To my knowledge, CICS connects to local MQ subsystems using an adaptor
which is
essentially a program running in CICS to handle direct MQ calls from
programs
in several languages. The MQ API for CICS is the same as it is for batch.
Before the implementation of TCP/IP support within MQ, the method was to go
from MQ through the CICS adaptor to CICS, then from CICS on SYSTEM-A to
CICS on
SYSTEMB, then from CICS to MQ. No cross-memory services are used. AFAIK,
the
methodology is very similar to the DB2 API implementation for CICS. Each
CICS
region only connects to one MQ subsystem through a Resource Manager
Interface,
so logistics might get more complicated with multiple CICS and MQs on the
same
system.
Ernest Roberts
IT - Sr Sys Prog
MBUSA, LLC
Three Mercedes Drive
Montvale, NJ 07345
201-573-2619
201-573-4383 fax
866-308-3782 pager
- Forwarded by Ernest Roberts/171/DCAG/DCX on 06/11/2003 08:58 PM -
Rick Tsujimoto <[EMAIL PROTECTED]>
Sent by: MQSeries List <[EMAIL PROTECTED]>
06/11/2003 02:52 PM
Please respond to MQSeries List
To: [EMAIL PROTECTED]
cc:
Subject: Re: MQ/CICS and LU6.2
June,
CICS accesses MQ messages using cross-memory services. It doesn't use
LU6.2. The decision to use LU6.2 (or TCP/IP) affects how remote queue
managers and/or clients talk to each other.
The SIP override specifies the queue manager name the region connects to,
plus the initq used by CKTI on CICS.
June Lawton
<[EMAIL PROTECTED] To:
[EMAIL PROTECTED]
GROUP.COM> cc:
Sent by: Subject: MQ/CICS and LU6.2
MQSeries List
<[EMAIL PROTECTED]
en.AC.AT>
06/11/2003 01:41
PM
Please respond
to MQSeries List
Can someone give me the steps for the following?
On the OS/390 I want to set up an LU6.2 connection between the queue
manager and one of our CICS regions. I am reading the Intercomminication
and
System Setup Guide, but I am getting a little confused.
I am assuming that I have to define an applid for the channel initiator in
SYS1.VTAMLST in addition to a conn/sess in CICS. Is this correct?
June Lawton
Information Systems
The PMA Insurance Group
[EMAIL PROTECTED]
(T) 610.397.5058
(F) 610.397.5311
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
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: MQ/CICS and LU6.2
To my knowledge, CICS connects to local MQ subsystems using an adaptor which is essentially a program running in CICS to handle direct MQ calls from programs in several languages. The MQ API for CICS is the same as it is for batch. Before the implementation of TCP/IP support within MQ, the method was to go from MQ through the CICS adaptor to CICS, then from CICS on SYSTEM-A to CICS on SYSTEMB, then from CICS to MQ. No cross-memory services are used. AFAIK, the methodology is very similar to the DB2 API implementation for CICS. Each CICS region only connects to one MQ subsystem through a Resource Manager Interface, so logistics might get more complicated with multiple CICS and MQs on the same system. Ernest Roberts IT - Sr Sys Prog MBUSA, LLC Three Mercedes Drive Montvale, NJ 07345 201-573-2619 201-573-4383 fax 866-308-3782 pager - Forwarded by Ernest Roberts/171/DCAG/DCX on 06/11/2003 08:58 PM - Rick Tsujimoto <[EMAIL PROTECTED]> Sent by: MQSeries List <[EMAIL PROTECTED]> 06/11/2003 02:52 PM Please respond to MQSeries List To: [EMAIL PROTECTED] cc: Subject: Re: MQ/CICS and LU6.2 June, CICS accesses MQ messages using cross-memory services. It doesn't use LU6.2. The decision to use LU6.2 (or TCP/IP) affects how remote queue managers and/or clients talk to each other. The SIP override specifies the queue manager name the region connects to, plus the initq used by CKTI on CICS. June Lawton <[EMAIL PROTECTED] To: [EMAIL PROTECTED] GROUP.COM> cc: Sent by: Subject: MQ/CICS and LU6.2 MQSeries List <[EMAIL PROTECTED] en.AC.AT> 06/11/2003 01:41 PM Please respond to MQSeries List Can someone give me the steps for the following? On the OS/390 I want to set up an LU6.2 connection between the queue manager and one of our CICS regions. I am reading the Intercomminication and System Setup Guide, but I am getting a little confused. I am assuming that I have to define an applid for the channel initiator in SYS1.VTAMLST in addition to a conn/sess in CICS. Is this correct? June Lawton Information Systems The PMA Insurance Group [EMAIL PROTECTED] (T) 610.397.5058 (F) 610.397.5311 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: MQ/CICS and LU6.2
June, CICS accesses MQ messages using cross-memory services. It doesn't use LU6.2. The decision to use LU6.2 (or TCP/IP) affects how remote queue managers and/or clients talk to each other. The SIP override specifies the queue manager name the region connects to, plus the initq used by CKTI on CICS. June Lawton <[EMAIL PROTECTED] To: [EMAIL PROTECTED] GROUP.COM> cc: Sent by: Subject: MQ/CICS and LU6.2 MQSeries List <[EMAIL PROTECTED] en.AC.AT> 06/11/2003 01:41 PM Please respond to MQSeries List Can someone give me the steps for the following? On the OS/390 I want to set up an LU6.2 connection between the queue manager and one of our CICS regions. I am reading the Intercomminication and System Setup Guide, but I am getting a little confused. I am assuming that I have to define an applid for the channel initiator in SYS1.VTAMLST in addition to a conn/sess in CICS. Is this correct? June Lawton Information Systems The PMA Insurance Group [EMAIL PROTECTED] (T) 610.397.5058 (F) 610.397.5311 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
MQ/CICS and LU6.2
Can someone give me the steps for the following? On the OS/390 I want to set up an LU6.2 connection between the queue manager and one of our CICS regions. I am reading the Intercomminication and System Setup Guide, but I am getting a little confused. I am assuming that I have to define an applid for the channel initiator in SYS1.VTAMLST in addition to a conn/sess in CICS. Is this correct? June Lawton Information Systems The PMA Insurance Group [EMAIL PROTECTED] (T) 610.397.5058 (F) 610.397.5311 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
