Re: AW: Can I create an ALWUPD/ALWDLT *No file with embeded SQL?

[qsrvbas@xxxxxxxxxxxx]

eduard wrote:
>    2. Re: AW: Can I create an ALWUPD/ALWDLT *No file with embeded
>       SQL? (eduard)
>
> Yes, we do not trust the QSECOFR on the boxes where our application runs.
> Auditters have also the tendency to not trust QSECOFR.
> Our QSECOFR we trust. Someone elses QSECOFR we might trust but better 
> sure than sorry.

Eduard:

It seems to me that the question now becomes "Why write to a file?"

Instead of writing to a file, send a journal entry. If desired, you can 
supply a model file to describe the entry-specific data so reading can 
still be done with various existing programs -- populate a temporary 
version of the model with retrieved journal entries and read those.

Reading from and writing to a journal isn't particularly more difficult 
than file I/O once a couple procs are created. And you get the the 
coverage for ALWUPD/ALWDLT essentially automatically.

If SQL doesn't work the way you would like it to, then maybe a different 
object type should be used.

Tom Liotta