RRS Best Practices

Sheldon Davis

RRS Best Practices
Hi



We need to use RRS in our DB2 V7 environment to manage two phase commit
with MQ Series.



My plan is to have a centralized routine (RRSMAIN) which will accept via
SYSIN the connection details and main DB2 COBOL module to be called.

RRSMAIN will perform the connection to the required DB2 subsystem and
then call the application program (APPMAIN) which will do normal
application, MQ and DB2 logic.

If APPMAIN want's to perform a commit it will perform a SRRCMIT or
SRRCBACK command.



My problem with this is that all subroutines of APPMAIN will also have
to be linked with the RRSCAF which means that I cannot use any existing
subroutines.



I am very interested in how other shops implemented RRS to obtain two
phase commit between MQ and DB2.



Best Regards

Sheldon Davis

IsraCard

tel: 972 3 6895763




The IDUG DB2-L Listserv is only part of your membership in IDUG. DB2-L list archives, the FAQ, and delivery preferences are at http://www.idug.org/lsidug under the Listserv tab. While at the site, you can also access the IDUG Online Learning Center, Tech Library and Code Place, see the latest IDUG conference information, and much more. If you have not yet signed up for Basic Membership in IDUG, available at no cost, click on Member Services at http://www.idug.org/lsms

James Campbell

Re: RRS Best Practices
(in response to Sheldon Davis)
Out of curiosity, why don't you use the DB2 MQ functions?

On the subject of the MQ functions, PK37290 (apparently) implements (some of) these
functions using MQI, instead of AMI. I've no actual experience of using this enhancement.

James Campbell

On 7 Jan 2008 at 9:53, Sheldon Davis wrote:

>
> Hi
>
> We need to use RRS in our DB2 V7 environment to manage two phase commit
> with MQ Series.
>
> My plan is to have a centralized routine (RRSMAIN) which will accept via SYSIN
> the connection details and main DB2 COBOL module to be called.
> RRSMAIN will perform the connection to the required DB2 subsystem and then
> call the application program (APPMAIN) which will do normal application, MQ
> and DB2 logic.
> If APPMAIN want´s to perform a commit it will perform a SRRCMIT or
> SRRCBACK command.
>
> My problem with this is that all subroutines of APPMAIN will also have to be
> linked with the RRSCAF which means that I cannot use any existing
> subroutines.
>
> I am very interested in how other shops implemented RRS to obtain two phase
> commit between MQ and DB2.
>
> Best Regards
> SheldonDavis
> IsraCard
> tel: 972 3 6895763

The IDUG DB2-L Listserv is only part of your membership in IDUG. DB2-L list archives, the FAQ, and delivery preferences are at http://www.idug.org/lsidug under the Listserv tab. While at the site, you can also access the IDUG Online Learning Center, Tech Library and Code Place, see the latest IDUG conference information, and much more. If you have not yet signed up for Basic Membership in IDUG, available at no cost, click on Member Services at http://www.idug.org/lsms

Victor Gil

Re: RRS Best Practices
(in response to James Campbell)
This may not answer your question, but if the callable entry points in RRSMAIN
are "exposed as external" via the IDENTIFY service [see the assembler macro]
then APPMAIN and the application subrouitnes would be able to call them
dynamically, i.e. without the need of being linked into the same load module.

HTH,
-Victor-

On Mon, 7 Jan 2008 09:53:05 +0200, Sheldon Davis
<[login to unmask email]> wrote:

>Hi
>
>
>
>We need to use RRS in our DB2 V7 environment to manage two phase commit
>with MQ Series.
>
>
>
>My plan is to have a centralized routine (RRSMAIN) which will accept via
>SYSIN the connection details and main DB2 COBOL module to be called.
>
>RRSMAIN will perform the connection to the required DB2 subsystem and
>then call the application program (APPMAIN) which will do normal
>application, MQ and DB2 logic.
>
>If APPMAIN want's to perform a commit it will perform a SRRCMIT or
>SRRCBACK command.
>
>
>
>My problem with this is that all subroutines of APPMAIN will also have
>to be linked with the RRSCAF which means that I cannot use any existing
>subroutines.
>
>
>
>I am very interested in how other shops implemented RRS to obtain two
>phase commit between MQ and DB2.

The IDUG DB2-L Listserv is only part of your membership in IDUG. DB2-L list archives, the FAQ, and delivery preferences are at http://www.idug.org/lsidug under the Listserv tab. While at the site, you can also access the IDUG Online Learning Center, Tech Library and Code Place, see the latest IDUG conference information, and much more. If you have not yet signed up for Basic Membership in IDUG, available at no cost, click on Member Services at http://www.idug.org/lsms