×

Good News Everybody!

The new search engine is LIVE!

Please report any problems to david (at) midrange.com.




Those headers are ASCII text for me. I'd suspect the CCSID of your
source file before that; try using iconv to convert it. (PASE programs
don't care about the CCSID attribute; they just want ASCII/UTF-8 text.)
Alternatively, just save it using means you know will result in non-
EBCDIC text; EDTF is a gigantic footgun.

On Mon, 2021-08-23 at 16:25 -0400, Jay Vaughn wrote:
I'm trying to develop a small POC to call an RPG ILE pgm from PASE.

I'll use a C program to run in PASE that will invoke a native IBM RPG
ILE
pgm and return a parm value.

Has anyone done something like this before?

Where I'm getting hung up is trying to utilize the two required
header files
#Include <as400_protos.h>
#include <as400_types.h>

(these both live in /usr/include, as well as in
/qopensys/qibm/proddata/os400/pase/include)

My C pgm source is compiled from a PF source file member.
So I copied those /usr/include header files to my lib into an h
srcfile.

My C pgm manages to find the header files this way, but I'm getting
all
kinds of compile errors related to the below as it "includes" the
header
files...
"The character ^? is not a valid C source character"
and many more other invalid specified characters...

Leads me to believe i have a ccsid issue on the source file but it is
37.

Anyone been down this path?  I saw something about using Rfile to
convert
files to ascii, but thinking that only applies if I move these header
files
to AIX.... which I'm not.

tia

Jay



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