|
I'm working in an environment that does not have the DB2 Query Manager
and SQL Development Kit so we can't embed SQL into our RPG and C
applications. I have recently been working on a project where I thought
a trigger program would be very useful. After doing a bit of research I
found that SQL trigger programs are created in the background with the
CRTSQLCI command which is the C SQL pre-compiler (part of the
development kit).
I was therefore very surprised that when I went into Operations
Navigator to attempt to create a SQL trigger it worked??? I even found a
number of sources that explicitly claim that SQL Stored Procedures and
Trigger programs can not be created without the SQL Development kit so
I'm wondering if anyone has any idea why I am able to do this?
I'm
certainly not complaining because it's nice to have the extra
functionality but I would like to know why this is possible? If I try
and run CRTSQLCI from the command line it of course fails but Operations
Navigator seems to be successfully using the pre-compiler? We are
running on V5R3.
As a side note, I'm relatively new to the iSeries environment but it
seems strange that if IBM are pushing SQL as the new standard for
iSeries (to replace RPG IO and DDS) that the SQL pre-compilers are not
part of the standard iSeries package? Does anyone know if there is any
push to make them part of the standard operating system?
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.