|
View previous topic :: View next topic
|
| Author |
Message |
Patrick Gantet
New User
Joined: 07 Apr 2010
Posts: 7
Location: Paris France
|
|
|
|
How can I intercept the Write order from a cobol transactional application, in order to stop the write in the file and replace it by a send msg via MQ.
Can I write a component to sustitute the vsam component and install it upper in the DFHRPL card? |
|
| Back to top |
|
 |
PeterHolland
Global Moderator
Joined: 27 Oct 2009
Posts: 2481
Location: Netherlands, Amstelveen
|
|
|
|
As far as i know the DFHRPL contains info about the relocatable program library data sets concatenated to the DFHRPL DDNAME for a CICS system.
So i guess if the vsam component is in the libary list, it can be replaced by a non vsam component. |
|
| Back to top |
|
|
dbzTHEdinosauer
Global Moderator
Joined: 20 Oct 2006
Posts: 6966
Location: porcelain throne
|
|
|
|
is this change to affect all VSAM files?
where will you obtain the necessary info to populate the MQS API CALL? |
|
| Back to top |
|
|
Patrick Gantet
New User
Joined: 07 Apr 2010
Posts: 7
Location: Paris France
|
|
|
|
| dbzTHEdinosauer wrote: |
is this change to affect all VSAM files?
where will you obtain the necessary info to populate the MQS API CALL? |
In fact I have to filter the vsam files : I know the names of the vsam to send to an unix system, and for the others I have to let vsam works normally.
I know the queue and the mecanism to send the records via MQ.
What I need is to understand how to realize and install a filter ontop of the vsam access!
thanks for your help |
|
| Back to top |
|
|
Robert Sample
Global Moderator
Joined: 06 Jun 2008
Posts: 8696
Location: Dubuque, Iowa, USA
|
|
|
|
This would be a an extremely challenging project.
First, I doubt the module is in the DFHRPL -- it is more likely in the STEPLIB (or JOBLIB or link list, depending upon how your site does things). DFHRPL is for application code, typically, not the system code running the applications.
Second, you would be far, far, far better off changing the application rather than attempting to make the kind of global change you're talking about.
Third, you're basically monkeying with some very low level code, so you'd better be writing code that is completely fault-tolerant and very fast or your transactional system may start having major problems.
Fourth, any changes you made would have to be remade (or at least verified) after every application of maintenance to your system. And there's a chance that maintenance will fail due to your added code.
Fifth, any system problems you have will probably have to be resolved on-site since there's no chance IBM is going to even look at any problems until your code has been removed from the system and the problem verified to exist WITHOUT your code. |
|
| Back to top |
|
|
CICS Guy
Senior Member
Joined: 18 Jul 2007
Posts: 2146
Location: At my coffee table
|
|
| Back to top |
|
|
Patrick Gantet
New User
Joined: 07 Apr 2010
Posts: 7
Location: Paris France
|
|
|
|
thank you very much....
Your solution is fantastic, and compliant with the future change of version of CICS....
Looking at the Guide you indicate, I've seen also the exits XFCREQ and XFCREQC that seems to allow to do what I need. Is it better than XDTAD?
My next step will be to be familiar with ASM to code it! But fot this I've some friends to help me!
best Regards |
|
| Back to top |
|
|
CICS Guy
Senior Member
Joined: 18 Jul 2007
Posts: 2146
Location: At my coffee table
|
|
|
|
| Quote: |
| I've seen also the exits XFCREQ and XFCREQC that seems to allow to do what I need. Is it better than XDTAD? |
I would tend to lean towards the use of the data table exit (if it can do all I think it can) because there will be no delay or interruption in the servicing of other file control requests, only other data table requests.
I do admit that I have not researched your needs as well as you will, and I realize that some exits do not allow some CICS functionality which you may need. The choice of which exit is yours.
BTW, I have done exits and once you get past their special requirements, they are fairly straight forward. Have fun....  |
|
| Back to top |
|
|
|
|
