| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| API Exits with SQL? |
« View previous topic :: View next topic » |
| Author |
Message
|
| jed |
 Posted: Sun Jul 11, 2004 11:42 pm Post subject: API Exits with SQL? |
 |
|
Centurion
Joined: 08 Jan 2004
Posts: 118
Location: MI, USA
|
Is it possible to do API Exits with SQL?
I'm able to make an API Exit program to write into a flat file (text file).
I'm reading/checking the MQ Systems Administration Manual and Application Programming Guide regarding this and there is no metion on it.
Anyone can shed light on this?
Many thanks!
_________________
Jed |
|
| Back to top |
|
 |
| jefflowrey |
| Posted: Mon Jul 12, 2004 4:23 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Can you be more specific about what you mean by this question?
Yes, I believe you can write a C exit that will create a database connection, and pass SQL statements to an SQL interpreter on the database management system on the other side of the database connection.
Did you mean something less normal than "Can I connect to a database within an exit"?
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| jed |
| Posted: Mon Jul 12, 2004 7:35 pm Post subject: |
|
|
Centurion
Joined: 08 Jan 2004
Posts: 118
Location: MI, USA
|
Ooops, sorry about that Jeff.
Well, you posted the right question that I wanted to ask.
Can I connect to a database within an API Exit?
I can't find any information regarding connecting to a database or performing SQL commands within an API Exit.
_________________
Jed |
|
| Back to top |
|
|
| oz1ccg |
| Posted: Mon Jul 12, 2004 10:41 pm Post subject: |
|
|
Yatiri
Joined: 10 Feb 2002
Posts: 628
Location: Denmark
|
I don't see anything that should prevent you from using database calls from an API exit. If you use C/C++ you can do what ever you like.
Yse you can write to a flat fil if you like... just make shure that you code can manage the different naming conventions on differnet platforms: win, AIX, Z/OS etc.
My personal oppinion is keep application design inside your applications and use exits for special purposes only. The main reason is the exit is hidden from the programmers, and typicly it's forgotton when the application programmers made changes..
Another reason can be performance. The API exit is invoked frequently, and might cause performace degradation if the design is bad.... Too much complex SQL... etc. 
I can see a usage for using the API exit for debuging, special transformations, encryption, thruput messaure etc.
Just my $0.02 
_________________
Regards, Jørgen
Home of BlockIP2, the last free MQ Security exit ver. 3.00
Cert. on WMQ, WBIMB, SWIFT. |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
