× 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.



Problem is, you generally can't write directly to IFS files - they are not database objects. Since 7.3 there are several IFS-related SQL service, but they are for retrieving information ABOUT IFS objects.

There are ways to write to CLOB - character large objects - those are still not record-layout tables. There are ways to build XML files directly that can be based on database data.

Hope that give you a couple directions to look at. Nothing quite so simple, though, as what you'd like to do here!

Vern

On 8/26/2020 9:46 AM, Bob Schwartz wrote:
Looking for some help on the proper syntax for SQL Insert Into statement.
Trying to write a CLP to extract some audit journal entries and then copy them out to the IFS for analysis.

I have the RUNSQL statement below, the slashes "/" in the IFS file path are giving me a problem.
I'm trying to avoid creating a PF and then running CPYTOIMPF. Thanks for your help.

RUNSQL SQL('INSERT INTO /home/gcaudit/A0825ZC.csv SELECT ZCTSTP,
ZCJOB, ZCUSER, ZCNBR, ZCPGM, ZCPGMLIB, ZCUSPF, ZCSYNM,
ZCRADR, ZCONAM, ZCOLIB, ZCOTYP, ZCACTP, ZCODTA, ZCPNM
FROM GCAUDIT.A0825ZC') NAMING(*SQL)

Token / was not valid. Valid tokens: <IDENTIFIER>.
RUNSQLSTM or RUNSQL command failed.

Thank you,
Bob Schwartz
Director of Technology Services
Glynn County Schools
1313 Egmont St.
Brunswick, GA 31520



As an Amazon Associate we earn from qualifying purchases.

This thread ...

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.