CAF and CICS

Randall Ibbott

CAF and CICS
Guys,

I know this has been on the list before, and I have searched the archives,
but only received limited success and am in a hurry. However, what we are
doing is not rocket science, so I thought I'd drop you a line.

It's the old interface problem again, and I was after some suggestions
while I investigate some other possibilities.

Basically, we precompile our subroutines (which are called dynamically)
with ATTACH(CAF) - which gives us the DSNHLI2 call in cobol. This doesn't
work in CICS (DSNCLI seems to have an entry point for DSNHLI, which is fine
if you want to use TSO). Without having to create two modules for our
subroutines - one for batch using CAF and another for CICS, is there
another option?

It is quite possible that I'm missing something, as this is my first
attempt in managing this area of DB2, so any help would be greatly
appreciated.

Regards,


Randall Ibbott.
Senior Database Administrator
Insure IT Services, 3 Figtree Drive, Homebush Bay, NSW, AUSTRALIA
Phone: +61 2 9701 7611
Fax: +61 2 9701 7503
Mobile: +61 0400 834 769
Email: [login to unmask email]


________________________________________________________________________
This email has been scanned for all viruses by the MessageLabs SkyScan
service. For more information on a proactive anti-virus service working
around the clock, around the globe, visit http://www.messagelabs.com
________________________________________________________________________



Peter Lehmensich

Re: CAF and CICS
(in response to Randall Ibbott)
Hi Randall.

A quick solution would be to create 2 load modules, one for CICS and one
for batch. One source module, one pre-compile, one compile but 2 link edits
to include the appropriate language interface modules .... DSNCLI for CICS
and DSNALI for call attach.

Cheers.
Peter




Randall Ibbott <[login to unmask email]>@LISTSERV.YLASSOC.COM> on 17/12/2002
11:50:39

Please respond to DB2 Data Base Discussion List
<[login to unmask email]>

Sent by: DB2 Data Base Discussion List <[login to unmask email]>


To: [login to unmask email]
cc:

Subject: CAF and CICS

Guys,

I know this has been on the list before, and I have searched the archives,
but only received limited success and am in a hurry. However, what we are
doing is not rocket science, so I thought I'd drop you a line.

It's the old interface problem again, and I was after some suggestions
while I investigate some other possibilities.

Basically, we precompile our subroutines (which are called dynamically)
with ATTACH(CAF) - which gives us the DSNHLI2 call in cobol. This doesn't
work in CICS (DSNCLI seems to have an entry point for DSNHLI, which is fine
if you want to use TSO). Without having to create two modules for our
subroutines - one for batch using CAF and another for CICS, is there
another option?

It is quite possible that I'm missing something, as this is my first
attempt in managing this area of DB2, so any help would be greatly
appreciated.

Regards,


Randall Ibbott.
Senior Database Administrator
Insure IT Services, 3 Figtree Drive, Homebush Bay, NSW, AUSTRALIA
Phone: +61 2 9701 7611
Fax: +61 2 9701 7503
Mobile: +61 0400 834 769
Email: [login to unmask email]


________________________________________________________________________
This email has been scanned for all viruses by the MessageLabs SkyScan
service. For more information on a proactive anti-virus service working
around the clock, around the globe, visit http://www.messagelabs.com
________________________________________________________________________



the DB2-L webpage at http://listserv.ylassoc.com. The owners of the list
can







****************************************************************
NOTICE - This message is intended only for the use of the
addressee named above and may contain privileged and
confidential information. If you are not the intended recipient
of this message you are hereby notified that you must not
disseminate, copy or take any action based upon it. If you
received this message in error please notify HIC immediately.
Any views expressed in this message are those of the individual
sender, except where the sender specifically states them to be
the views of HIC.
****************************************************************



Randall Ibbott

Re: CAF and CICS
(in response to Peter Lehmensich)
We are running with two modules, but dual maintenance is an issue the users
don't want..
Regards,


Randall Ibbott.
Senior Database Administrator
Insure IT Services, 3 Figtree Drive, Homebush Bay, NSW, AUSTRALIA
Phone: +61 2 9701 7611
Fax: +61 2 9701 7503
Mobile: +61 0400 834 769
Email: [login to unmask email]



Peter Lehmensich
<peter.lehmensich@H To: [login to unmask email]
IC.GOV.AU> cc: (bcc: Randall Ibbott/NSW/IITS/Insurance)
Subject: Re: CAF and CICS
17/12/2002 13:52
Please respond to
DB2 Data Base
Discussion List







Hi Randall.

A quick solution would be to create 2 load modules, one for CICS and one
for batch. One source module, one pre-compile, one compile but 2 link edits
to include the appropriate language interface modules .... DSNCLI for CICS
and DSNALI for call attach.

Cheers.
Peter




Randall Ibbott <[login to unmask email]>@LISTSERV.YLASSOC.COM> on 17/12/2002
11:50:39

Please respond to DB2 Data Base Discussion List
<[login to unmask email]>

Sent by: DB2 Data Base Discussion List <[login to unmask email]>


To: [login to unmask email]
cc:

Subject: CAF and CICS

Guys,

I know this has been on the list before, and I have searched the archives,
but only received limited success and am in a hurry. However, what we are
doing is not rocket science, so I thought I'd drop you a line.

It's the old interface problem again, and I was after some suggestions
while I investigate some other possibilities.

Basically, we precompile our subroutines (which are called dynamically)
with ATTACH(CAF) - which gives us the DSNHLI2 call in cobol. This doesn't
work in CICS (DSNCLI seems to have an entry point for DSNHLI, which is fine
if you want to use TSO). Without having to create two modules for our
subroutines - one for batch using CAF and another for CICS, is there
another option?

It is quite possible that I'm missing something, as this is my first
attempt in managing this area of DB2, so any help would be greatly
appreciated.

Regards,


Randall Ibbott.
Senior Database Administrator
Insure IT Services, 3 Figtree Drive, Homebush Bay, NSW, AUSTRALIA
Phone: +61 2 9701 7611
Fax: +61 2 9701 7503
Mobile: +61 0400 834 769
Email: [login to unmask email]


________________________________________________________________________
This email has been scanned for all viruses by the MessageLabs SkyScan
service. For more information on a proactive anti-virus service working
around the clock, around the globe, visit http://www.messagelabs.com
________________________________________________________________________



the DB2-L webpage at http://listserv.ylassoc.com. The owners of the list
can







****************************************************************
NOTICE - This message is intended only for the use of the
addressee named above and may contain privileged and
confidential information. If you are not the intended recipient
of this message you are hereby notified that you must not
disseminate, copy or take any action based upon it. If you
received this message in error please notify HIC immediately.
Any views expressed in this message are those of the individual
sender, except where the sender specifically states them to be
the views of HIC.
****************************************************************



the DB2-L webpage at http://listserv.ylassoc.com. The owners of the list
can

________________________________________________________________________
This email has been scanned for all viruses by the MessageLabs SkyScan
service. For more information on a proactive anti-virus service working
around the clock, around the globe, visit http://www.messagelabs.com
________________________________________________________________________




________________________________________________________________________
This email has been scanned for all viruses by the MessageLabs SkyScan
service. For more information on a proactive anti-virus service working
around the clock, around the globe, visit http://www.messagelabs.com
________________________________________________________________________



Marcel Harleman

Re: CAF and CICS
(in response to Randall Ibbott)
Hi Randall,

maybe there's a way of running a "CICS-batch"; if I recall well that
is possible, at least I've stumbled upon a construction like that in
the past. Then everything is running with the CICS interface. One
issue you might run into is that maybe RACF (if you're using it)
restricts the use of the language interface to the userid's of CICS
itself.

Contact your CICS people to see if they have an example of how to do
it.

Marcel.

>We are running with two modules, but dual maintenance is an issue the users
>don't want..
>Regards,
>
>
>Randall Ibbott.
>Senior Database Administrator
>Insure IT Services, 3 Figtree Drive, Homebush Bay, NSW, AUSTRALIA
>Phone: +61 2 9701 7611
>Fax: +61 2 9701 7503
>Mobile: +61 0400 834 769
>Email: [login to unmask email]
>
>
>
> Peter Lehmensich
> <peter.lehmensich@H To: [login to unmask email]
> IC.GOV.AU> cc: (bcc: Randall Ibbott/NSW/IITS/Insurance)
> Subject: Re: CAF and CICS
> 17/12/2002 13:52
> Please respond to
> DB2 Data Base
> Discussion List
>
>
>
>
>
>
>
>Hi Randall.
>
>A quick solution would be to create 2 load modules, one for CICS and one
>for batch. One source module, one pre-compile, one compile but 2 link edits
>to include the appropriate language interface modules .... DSNCLI for CICS
>and DSNALI for call attach.
>
>Cheers.
>Peter
>
>
>
>
>Randall Ibbott <[login to unmask email]>@LISTSERV.YLASSOC.COM> on 17/12/2002
>11:50:39
>
>Please respond to DB2 Data Base Discussion List
> <[login to unmask email]>
>
>Sent by: DB2 Data Base Discussion List <[login to unmask email]>
>
>
>To: [login to unmask email]
>cc:
>
>Subject: CAF and CICS
>
>Guys,
>
>I know this has been on the list before, and I have searched the archives,
>but only received limited success and am in a hurry. However, what we are
>doing is not rocket science, so I thought I'd drop you a line.
>
>It's the old interface problem again, and I was after some suggestions
>while I investigate some other possibilities.
>
>Basically, we precompile our subroutines (which are called dynamically)
>with ATTACH(CAF) - which gives us the DSNHLI2 call in cobol. This doesn't
>work in CICS (DSNCLI seems to have an entry point for DSNHLI, which is fine
>if you want to use TSO). Without having to create two modules for our
>subroutines - one for batch using CAF and another for CICS, is there
>another option?
>
>It is quite possible that I'm missing something, as this is my first
>attempt in managing this area of DB2, so any help would be greatly
>appreciated.
>
>Regards,
>
>
>Randall Ibbott.
>Senior Database Administrator
>Insure IT Services, 3 Figtree Drive, Homebush Bay, NSW, AUSTRALIA
>Phone: +61 2 9701 7611
>Fax: +61 2 9701 7503
>Mobile: +61 0400 834 769
>Email: [login to unmask email]
>
>
>________________________________________________________________________
>This email has been scanned for all viruses by the MessageLabs SkyScan
>service. For more information on a proactive anti-virus service working
>around the clock, around the globe, visit http://www.messagelabs.com
>________________________________________________________________________
>
>
>
>the DB2-L webpage at http://listserv.ylassoc.com. The owners of the list
>can
>
>
>
>
>
>
>
>****************************************************************
>NOTICE - This message is intended only for the use of the
>addressee named above and may contain privileged and
>confidential information. If you are not the intended recipient
>of this message you are hereby notified that you must not
>disseminate, copy or take any action based upon it. If you
>received this message in error please notify HIC immediately.
>Any views expressed in this message are those of the individual
>sender, except where the sender specifically states them to be
>the views of HIC.
>****************************************************************
>
>
>
>the DB2-L webpage at http://listserv.ylassoc.com. The owners of the list
>can
>
>________________________________________________________________________
>This email has been scanned for all viruses by the MessageLabs SkyScan
>service. For more information on a proactive anti-virus service working
>around the clock, around the globe, visit http://www.messagelabs.com
>________________________________________________________________________
>
>
>
>
>________________________________________________________________________
>This email has been scanned for all viruses by the MessageLabs SkyScan
>service. For more information on a proactive anti-virus service working
>around the clock, around the globe, visit http://www.messagelabs.com
>________________________________________________________________________
>
>
>



James Campbell

Re: CAF and CICS
(in response to Marcel Harleman)
If you don't use ATTACH(CAF) the precompiler generates a call to the DSNHLI. Entry points of this name are in both the DSNALI and DSNCLI modules (as well as DSNELI (TSO Attach), DSNRLI (RRSAF Attach) and DFSLI000 (IMS Attach)). Linking the appropriate module into your load module allows a
single pre-compile, and single compile with two links. As there is a single precompile, there is a single bind. I think this is what Peter was referring to. It is the offical line from IBM - http://listserv.ylassoc.com/cgi/wa.exe?A2=ind0012B&L=DB2-L&P=R13214

Prior messages in that thread however indicate various techniques of
writing a common interface module which determines at run time what
attachement is in use, and either branches to the code (mimiking the
code in DSNCLI) or loads the appropriate alias entry point (DSNHLI2
in DSNALI, DSNHLI in DSNELI, or DSNHLIR in DSNRLI (you might want to
call your routines from a WLM environment SP in the future)). An
alternative to determining (based on what modules are loaded into the
address space) the attachement in use,
is to have special load libraries each with one of the interface modules and DSNHLI (and DSNWLI) exposed as an alias. The appropriate library is then put into STEPLIB and the common interface module just does a load on DSNHLI. The appropriate real LI module is then loaded.

NOT FOR THE FAINT HEARTED, NOT SUPPORTED, YOU'RE ON YOUR OWN IF THINGS GO BELLY UP. I DIDN'T WRITE IT, I NEVER SUGGESTED THAT YOU WILL HAVE SUCCESS IF YOU TRY.

(Note http://bama.ua.edu/cgi-bin/wa?A2=ind0011&L=ibm-main&P=R38980&I=1 - be warned though, this was not from IBM so is not guranteed to be valid under some/any future circumstance.)

James Campbell


On 17 Dec 2002 at 6:55, Marcel Harleman wrote:

> Hi Randall,
>
> maybe there's a way of running a "CICS-batch"; if I recall well that
> is possible, at least I've stumbled upon a construction like that in
> the past. Then everything is running with the CICS interface. One
> issue you might run into is that maybe RACF (if you're using it)
> restricts the use of the language interface to the userid's of CICS
> itself.
>
> Contact your CICS people to see if they have an example of how to do
> it.
>
> Marcel.
>
> >We are running with two modules, but dual maintenance is an issue the users
> >don't want..
> >Regards,
> >
> >
> >Randall Ibbott.
> >Senior Database Administrator
> >Insure IT Services, 3 Figtree Drive, Homebush Bay, NSW, AUSTRALIA
> >Phone: +61 2 9701 7611
> >Fax: +61 2 9701 7503
> >Mobile: +61 0400 834 769
> >Email: [login to unmask email]
> >
> >
> >
> > Peter Lehmensich
> > <peter.lehmensich@H To: [login to unmask email]
> > IC.GOV.AU> cc: (bcc: Randall Ibbott/NSW/IITS/Insurance)
> > Subject: Re: CAF and CICS
> > 17/12/2002 13:52
> > Please respond to
> > DB2 Data Base
> > Discussion List
> >
> >
> >
> >
> >
> >
> >
> >Hi Randall.
> >
> >A quick solution would be to create 2 load modules, one for CICS and one
> >for batch. One source module, one pre-compile, one compile but 2 link edits
> >to include the appropriate language interface modules .... DSNCLI for CICS
> >and DSNALI for call attach.
> >
> >Cheers.
> >Peter
> >
> >
> >
> >
> >Randall Ibbott <[login to unmask email]>@LISTSERV.YLASSOC.COM> on 17/12/2002
> >11:50:39
> >
> >Please respond to DB2 Data Base Discussion List
> > <[login to unmask email]>
> >
> >Sent by: DB2 Data Base Discussion List <[login to unmask email]>
> >
> >
> >To: [login to unmask email]
> >cc:
> >
> >Subject: CAF and CICS
> >
> >Guys,
> >
> >I know this has been on the list before, and I have searched the archives,
> >but only received limited success and am in a hurry. However, what we are
> >doing is not rocket science, so I thought I'd drop you a line.
> >
> >It's the old interface problem again, and I was after some suggestions
> >while I investigate some other possibilities.
> >
> >Basically, we precompile our subroutines (which are called dynamically)
> >with ATTACH(CAF) - which gives us the DSNHLI2 call in cobol. This doesn't
> >work in CICS (DSNCLI seems to have an entry point for DSNHLI, which is fine
> >if you want to use TSO). Without having to create two modules for our
> >subroutines - one for batch using CAF and another for CICS, is there
> >another option?
> >
> >It is quite possible that I'm missing something, as this is my first
> >attempt in managing this area of DB2, so any help would be greatly
> >appreciated.
> >
> >Regards,
> >
> >
> >Randall Ibbott.
> >Senior Database Administrator
> >Insure IT Services, 3 Figtree Drive, Homebush Bay, NSW, AUSTRALIA
> >Phone: +61 2 9701 7611
> >Fax: +61 2 9701 7503
> >Mobile: +61 0400 834 769
> >Email: [login to unmask email]
> >
> >
> >________________________________________________________________________
> >This email has been scanned for all viruses by the MessageLabs SkyScan
> >service. For more information on a proactive anti-virus service working
> >around the clock, around the globe, visit http://www.messagelabs.com
> >________________________________________________________________________
> >
> >
> >
> >the DB2-L webpage at http://listserv.ylassoc.com. The owners of the list
> >can
> >
> >
> >
> >
> >
> >
> >
> >****************************************************************
> >NOTICE - This message is intended only for the use of the
> >addressee named above and may contain privileged and
> >confidential information. If you are not the intended recipient
> >of this message you are hereby notified that you must not
> >disseminate, copy or take any action based upon it. If you
> >received this message in error please notify HIC immediately.
> >Any views expressed in this message are those of the individual
> >sender, except where the sender specifically states them to be
> >the views of HIC.
> >****************************************************************
> >
> >
> >
> >the DB2-L webpage at http://listserv.ylassoc.com. The owners of the list
> >can
> >
> >________________________________________________________________________
> >This email has been scanned for all viruses by the MessageLabs SkyScan
> >service. For more information on a proactive anti-virus service working
> >around the clock, around the globe, visit http://www.messagelabs.com
> >________________________________________________________________________
> >
> >
> >
> >
> >________________________________________________________________________
> >This email has been scanned for all viruses by the MessageLabs SkyScan
> >service. For more information on a proactive anti-virus service working
> >around the clock, around the globe, visit http://www.messagelabs.com
> >________________________________________________________________________
> >
> >
> >
>
>
>



Victor x28091 Gil

Re: CAF and CICS
(in response to James Campbell)
Randall,

Can't send you the source, but here's what I've done to address the issue:

a) Wrote a DUMMY DSNHLI program B that is called INSTEAD of the ACTUAL
DSNHLI [see CAF documentation and also (b)]. It serves as a bridge between
SQL requesters and CAF so that real DSNALI/DSNHLI/DSNHLI2 are loaded, DB2 is
CONNECTed and PLAN is open on the very first SQL call.

b) Wrote a top-level program T, that would always get control first
[explicit ENTRY T during link-editing], issue IDENTIFY to associate "DNSHLI"
with the address of B [from (a)] and statically CALL the actual DB2 module.
To accommodate *any* batch DB2 module the name to CALL is coded as @@@ but
reset during link-editing to the actual module name [CHANGE @@@(DB2MOD1)].

c) Each batch DB2 program is now "sandwiched" between T and B and although
it issues DYNAMIC calls to DSNHLI they are redirected to B due to IDENTIFY
in T. Here's a sample LINK for DB2MOD1:

* (1) USE 'T' INSTEAD OF <YOUR PROGRAM ENTRY POINT>:
*?ENTRY DB2MOD1
ENTRY T
*
* (2) TELL EDITOR TO REPLACE '@@@' WITH <YOUR PROGRAM ENTRY POINT>
CHANGE @@@(DB2MOD1)
*
* (3) INCLUDE TOP AND BOTTOM (ORDER MATTERS!):
INCLUDE SYSLIB(T) - TOP LEVEL ROUTINE
INCLUDE SYSLIB(B) - BRIDGE TO CAF IN BATCH

*
* (4) NOW INCLUDE YOUR PROGRAM(S):
INCLUDE SYSLIB(DB2MOD1) - MAIN LOGIC
MODE AMODE(31),RMODE(ANY)
NAME DB2MOD1(R)

It is completely transparent to DB2MOD1 whether it runs in batch or CICS as
all the CAF calls are handled automatically. You can even enhance T with a
DISCONNECT call [after DB2MOD1 returns back] so that OMEGAMON is not
complaining about improperly terminated connection.

Of course, you would have to make B to somehow determine proper DB2
subsystem and plan name, but hopefully you've got the idea.

Good luck,
-Victor-

Roger Miller

Re: CAF and CICS
(in response to Victor x28091 Gil)
I've looked at half a dozen examples of techniques to allow one load module.
When I look at customer examples of techniques to have one load module, I
usually see additional cpu time that would be unacceptable to many other
customers. You'll need to decide how much additional cpu time is
acceptable in your shop. To keep the cpu time down, many of the examples
use data areas that were not intended to be interfaces, so that they are
too likely to break. Other examples only work for some specific
environments and languages or depend upon a customer convention.

Let's be careful out there. If the code breaks something, you get to keep
the pieces, and remember Humpty Dumpty.

Roger Miller


On Tue, 17 Dec 2002 23:45:44 +1000, James Campbell
<[login to unmask email]> wrote:

>If you don't use ATTACH(CAF) the precompiler generates a call to the
DSNHLI. Entry points of this name are in both the DSNALI and DSNCLI
modules (as well as DSNELI (TSO Attach), DSNRLI (RRSAF Attach) and DFSLI000
(IMS Attach)). Linking the appropriate module into your load module allows
a
>single pre-compile, and single compile with two links. As there is a
single precompile, there is a single bind. I think this is what Peter was
referring to. It is the offical line from IBM -
http://listserv.ylassoc.com/cgi/wa.exe?A2=ind0012B&L=DB2-L&P=R13214
>
>Prior messages in that thread however indicate various techniques of
>writing a common interface module which determines at run time what
>attachement is in use, and either branches to the code (mimiking the
>code in DSNCLI) or loads the appropriate alias entry point (DSNHLI2
>in DSNALI, DSNHLI in DSNELI, or DSNHLIR in DSNRLI (you might want to
>call your routines from a WLM environment SP in the future)). An
>alternative to determining (based on what modules are loaded into the
>address space) the attachement in use,
>is to have special load libraries each with one of the interface modules
and DSNHLI (and DSNWLI) exposed as an alias. The appropriate library is
then put into STEPLIB and the common interface module just does a load on
DSNHLI. The appropriate real LI module is then loaded.
>
>NOT FOR THE FAINT HEARTED, NOT SUPPORTED, YOU'RE ON YOUR OWN IF THINGS GO
BELLY UP. I DIDN'T WRITE IT, I NEVER SUGGESTED THAT YOU WILL HAVE SUCCESS
IF YOU TRY.
>
>(Note http://bama.ua.edu/cgi-bin/wa?A2=ind0011&L=ibm-main&P=R38980&I=1 -
be warned though, this was not from IBM so is not guranteed to be valid
under some/any future circumstance.)
>
>James Campbell
>
>
>On 17 Dec 2002 at 6:55, Marcel Harleman wrote:
>
>> Hi Randall,
>>
>> maybe there's a way of running a "CICS-batch"; if I recall well that
>> is possible, at least I've stumbled upon a construction like that in
>> the past. Then everything is running with the CICS interface. One
>> issue you might run into is that maybe RACF (if you're using it)
>> restricts the use of the language interface to the userid's of CICS
>> itself.
>>
>> Contact your CICS people to see if they have an example of how to do
>> it.
>>
>> Marcel.
>>
>> >We are running with two modules, but dual maintenance is an issue the
users
>> >don't want..
>> >Regards,
>> >
>> >
>> >Randall Ibbott.
>> >Senior Database Administrator
>> >Insure IT Services, 3 Figtree Drive, Homebush Bay, NSW, AUSTRALIA
>> >Phone: +61 2 9701 7611
>> >Fax: +61 2 9701 7503
>> >Mobile: +61 0400 834 769
>> >Email: [login to unmask email]
>> >
>> >
>> >
>> > Peter Lehmensich
>> > <peter.lehmensich@H To: DB2-
[login to unmask email]
>> > IC.GOV.AU> cc: (bcc: Randall
Ibbott/NSW/IITS/Insurance)
>> > Subject: Re: CAF and
CICS
>> > 17/12/2002 13:52
>> > Please respond to
>> > DB2 Data Base
>> > Discussion List
>> >
>> >
>> >
>> >
>> >
>> >
>> >
>> >Hi Randall.
>> >
>> >A quick solution would be to create 2 load modules, one for CICS and one
>> >for batch. One source module, one pre-compile, one compile but 2 link
edits
>> >to include the appropriate language interface modules .... DSNCLI for
CICS
>> >and DSNALI for call attach.
>> >
>> >Cheers.
>> >Peter
>> >
>> >
>> >
>> >
>> >Randall Ibbott <[login to unmask email]>@LISTSERV.YLASSOC.COM> on
17/12/2002
>> >11:50:39
>> >
>> >Please respond to DB2 Data Base Discussion List
>> > <[login to unmask email]>
>> >
>> >Sent by: DB2 Data Base Discussion List <[login to unmask email]>
>> >
>> >
>> >To: [login to unmask email]
>> >cc:
>> >
>> >Subject: CAF and CICS
>> >
>> >Guys,
>> >
>> >I know this has been on the list before, and I have searched the
archives,
>> >but only received limited success and am in a hurry. However, what we
are
>> >doing is not rocket science, so I thought I'd drop you a line.
>> >
>> >It's the old interface problem again, and I was after some suggestions
>> >while I investigate some other possibilities.
>> >
>> >Basically, we precompile our subroutines (which are called dynamically)
>> >with ATTACH(CAF) - which gives us the DSNHLI2 call in cobol. This
doesn't
>> >work in CICS (DSNCLI seems to have an entry point for DSNHLI, which is
fine
>> >if you want to use TSO). Without having to create two modules for our
>> >subroutines - one for batch using CAF and another for CICS, is there
>> >another option?
>> >
>> >It is quite possible that I'm missing something, as this is my first
>> >attempt in managing this area of DB2, so any help would be greatly
>> >appreciated.
>> >
>> >Regards,
>> >
>> >
>> >Randall Ibbott.
>> >Senior Database Administrator
>> >Insure IT Services, 3 Figtree Drive, Homebush Bay, NSW, AUSTRALIA
>> >Phone: +61 2 9701 7611
>> >Fax: +61 2 9701 7503
>> >Mobile: +61 0400 834 769
>> >Email: [login to unmask email]
>> >
>> >****************************************************************
>> >NOTICE - This message is intended only for the use of the
>> >addressee named above and may contain privileged and
>> >confidential information. If you are not the intended recipient
>> >of this message you are hereby notified that you must not
>> >disseminate, copy or take any action based upon it. If you
>> >received this message in error please notify HIC immediately.
>> >Any views expressed in this message are those of the individual
>> >sender, except where the sender specifically states them to be
>> >the views of HIC.
>> >****************************************************************