Re: systools.generate_spreadsheet

so I played around with this, and found the following:
1) testing from SQL scripts went fine, but when I put in a rpgle program I
had to change authority on a directory in the path from PUBLIC *EXCLUDE to
add QPGMR *USE.
2) I then had to WRKFCNUSG to allow QPGMR to use function
QIBM_XE1_DDWNLD_RTOPCB

I let the developers know about this, as we have MANY reports that go out
as .xml via XML* builder modules, and .xml files are getting harder to
map to open with excel.
but alas, we also do a ton of column formatting that would be lost. so,
this winds up being a non-starter here.


On Tue, Feb 27, 2024 at 2:08 PM Greg Wilburn <
gwilburn@xxxxxxxxxxxxxxxxxxxxxxx> wrote:

I was looking for a quick way to generate a CSV file from an SQL
statement, when I came across SYSTOOLS.GENERATE_SPREADSHEET function in the
ACS examples.
It seems pretty slick... will create CSV, ODS or XLSX.

I experimented with it in Run SQL scripts... it works well, BUT it
generates a lot of extra "garbage" in the /tmp directory:

1. A directory like: acs.jar_cache9093688686560570926.dir
2. A file like: acs.jar_cache3db3a1041bebae62

I'm wondering if those are byproducts of using it in ACS Run SQL Scripts,
OR if it would do the same when embedded in an RPG program.
Has anyone been using this function?

TIA,
Greg
[Logo]<https://www.totalbizfulfillment.com/> Greg Wilburn
Director of IT
301.895.3792 ext. 1231
301.895.3895 direct
gwilburn@xxxxxxxxxxxxxxxxxxxxxxx<mailto:gwilburn@xxxxxxxxxxxxxxxxxxxxxxx>
1 Corporate Dr
Grantsville, MD 21536
www.totalbizfulfillment.com<http://www.totalbizfulfillment.com>
--
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.