× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  1.  Home
  2. RPG400-L
  3. March 2008

Re: _cipher API vs Qc3Encrypt/Qc3DecryptData vs SQL

ADDPFTRG FILE(ROB/CHUCKY)
TRGTIME(*BEFORE)
TRGEVENT(*READ)
PGM(ROB/BARNEY)

CPD730A -TRGTIME(*BEFORE) not allowed with TRGEVENT(*READ).

Two issues. One: Can we use a trigger to secure the data? According to
the above - no, we can only report on it afterwards. Two, can we change
the buffer to suit some purpose? If you can't do the above you sure as
heck can't do this.
(as I am typing this it is starting to sink in what you are saying about
the record buffer...)

Or, are you saying that I could use the read trigger with *AFTER but
before the data is actually returned to the application (to secure the
data)? Then I could fail the read (Traditional RPG or SQL) by having the
trigger fail? And then the file read status would indicate a trigger
failure?

Rob Berendt

As an Amazon Associate we earn from qualifying purchases.

This thread ...
Follow-Ups:
Replies:
Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.