DFU to SQL translator

10 pts.
Tags:
DFU
SQL
SQL statement
Is there a package that will allow the user to enter DFU commands and then translate to SQL and send that to the processor? The situation is that the logging program doesn't see DFU commands but does see SQL statements.

Software/Hardware used:
iSeries
ASKED: November 29, 2012  9:21 PM
UPDATED: November 30, 2012  1:19 PM

Answer Wiki

Thanks. We'll let you know when a new response is added.

I know of no package that can do what you are requesting.

But to clarify, are you asking to get a log of the records that were added/changed/deleted in a file? If so, you can just journal the file and record the before and after images.

If that is what you want and need help with setting it up, let us know and we will be glad to assist.

 

Discuss This Question: 1  Reply

 
There was an error processing your information. Please try again later.
Thanks. We'll let you know when a new response is added.
Send me notifications when members answer or reply to this question.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy
  • TomLiotta
    DFU and SQL are not fully compatible, so conversion wouldn't be guaranteed. I can't imagine a product that could make the jump, especially since DFU is proprietary.   Regardless, the 'Answer' suggestion to use journaling (rather than either the database monitor or the DFU logging) is almost certainly best. SQL statement logging doesn't tell you what actually happened. Only journaling will tell you that. It's also more reliable, and it's actually acceptable for compliance and similar requirements where database monitor output would not be. (It's vulnerable to manipulation.)   The database monitor is really appropriate for performance optimization. It's not well structured for audit logging. It leaves out important audit items, such as which rows were affected, or in fact whether any rows were affected at all. And of course, it's not appropriate for any non-database (non-SQL) I/O at all.   Since there is no conversion between DFU and SQL, it seems reasonable that you need something different. It would be helpful if you could describe the business objective that you're trying to satisfy.   Tom
    125,585 pointsBadges:
    report

Forgot Password

No problem! Submit your e-mail address below. We'll send you an e-mail containing your password.

Your password has been sent to:

To follow this tag...

There was an error processing your information. Please try again later.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy

Thanks! We'll email you when relevant content is added and updated.

Following