|
On Jan 16, 2026, at 7:15 PM, Jack Woehr via MIDRANGE-L <midrange-l@xxxxxxxxxxxxxxxxxx> wrote:
Sign your report with gpg https://en.wikipedia.org/wiki/GNU_Privacy_Guard and they'd have to major league cryptographers to alter the result without detection.
$ which gpg
/QOpenSys/pkgs/bin/gpg
Jack Woehr
Independent Consulting Programmer
[icon] 303-847-8442<tel:303-847-8442>
[icon] jack.woehr@xxxxxxxxxxx<mailto:jack.woehr@xxxxxxxxxxx>
[icon] www.procern.com<https://www.procern.com>
[icon] Stay Connected!<https://www.linkedin.com/company/procern-technology-solutions/>
[photo]
Upgrade your IT state of mind!<https://procern.com/24-7-monitoring-itil-management/>
NON-DISCLOSURE NOTICE: This communication including any and all attachments is for the intended recipient(s) only and may contain confidential and privileged information. If you are not the intended recipient of this communication, any disclosure, copying further distribution or use of this communication is prohibited. If you received this communication in error, please contact the sender and delete/destroy all copies of this communication immediately.
[__tpx__]
________________________________
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> on behalf of Jim Oberholtzer <midrangel@xxxxxxxxxxxxxxxxx>
Sent: Friday, January 16, 2026 18:11
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: Copy database to CSV file permissions
We use an example that Rob showed us to copy the results of various audit extracts (IE: dspusrprf *all) etc. to CSV files so the auditors can look sort and manipulate as they desire. Works Great, but: Now the auditors are complaining that an CSV can be modified, and there is no time stamp on the creation of the file.
Is there a way to make the resulting file read only, and put a line in it that delineates when the file was created?
--
Jim Oberholtzer
Agile Technology Architects
Jack Woehr
Independent Consulting Programmer
303-847-8442
jack.woehr@xxxxxxxxxxx
www.procern.com
Stay Connected!
Upgrade your IT state of mind!
NON-DISCLOSURE NOTICE: This communication including any and all attachments is for the intended recipient(s) only and may contain confidential and privileged information. If you are not the intended recipient of this communication, any disclosure, copying further distribution or use of this communication is prohibited. If you received this communication in error, please contact the sender and delete/destroy all copies of this communication immediately.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related questions.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2026 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.