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

Eduard

I believe you can always create a physical file using the CRTPF command - it is
not part of any compiler, it is part of the operating system, just as CRTCLPGM
is and CRTBNDCL.

You should be able to create a source PF anywhere, as well - that is part of
the operating system. And have maybe a compile time array with the DDS source -
that would not be changeable by any user other than Leif Svalgaard.

Just some thoughts
Vern

-------------- Original message --------------
From: eduard@xxxxxxxxxxxxxxxxxxxxxxx

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.

Not necessarely this file must be created with SQL.
SQL was one of the possible options to create a externally described file on
the
fly.
Doing things from a source and compiling this is not an option because:
- We do not have that environment under our control.
- Do not know what features they have installed (can we compile?).
- Source can be changed (we do not use any scripting language either) and
that
is far to risky.

So now we have decided on Copy and Check tricks.
All files that need handling have a parent file (with the right atributes
set).
When needed we Create a new file based on the Parent.
When using the file we check ObjectCreation date/time to check if we have
created the file (and not someone else).
This procedure is not fool proof but you will need the manual (what manual?)
to
fiddle with it.

Regards,
Eduard,