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



Hi Thomas,

It is not necessarily the emulator only. I had the same problem when I transferred a member from my PC into a source file with the wrong ccsid.

'typedef struct ä' should be 'typedef struct {'. The letter 'ä' is a German Umlaut and in this case an indicator for that the source member has been unintentionally translated to a wrong ccsid.

I assume that PUB400.COM is configured with CCSID 273 or 1141 and that your job runs with that CCSID. Then CRTSRCPF creates a source file with CCSID 273 or 1141, which may cause unexpected translations.

Assuming that your "home" CCSID is 37 you should ensure that:

* your job runs with CCSID 37
* your job runs with langid EN
* your emulator uses CCSID 37

At least all these things should match. Either the German or the US properties. Otherwise unexpected translation may happen when copying code.

Thomas.


Am 15.04.2023 um 09:13 schrieb Thomas Burrows:
! typedef struct
! ä
.a...............................................................
======> a - CZM0191 The character ä is not a valid C source chara
! char name¬LEN|;
+ char name¬10;|;
....a........b...................................................
======> a - CZM0275 Unexpected text 'char' encountered.
======> b - CZM0046 Syntax error.
! char phone¬LEN|;
! ü
.a...............................................................

I am using PUB400.COM. Thinking maybe the emulator might be the issue.

Thomas


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.