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



I can do that, but that means I have to use a EBCDIC compatible code
editor, i.e. EDTF or something else IBM provides. Not the best idea.
So I prefer to use jedit or emacs and not being able to have the
source in all the different codepages. It is rare that my source has
to use non ASCII characters for actual data so this is why I was glad
for a brief moment when I came to think about pragma convert. But I
can't say I wasn't all that surprised when it didn't work. There
really are some situations on this OS where you're clearly not
supposed to do stuff in other CCSIDs than 37 (or one that is
compatible with it).

2011/3/4 Dennis <iseries@xxxxxxxxxxxx>:
Erik, I must admit to lack of experience with mixed CCSID, so maybe this is a dumb question.  That's never stopped me before, though, so: ... Can you store your source in the IFS, in your desired CCSID, and improve the result that way?  Or is that what you're doing and I'm totally missing it?

"Erik Olsson" <erik.eo.olsson@xxxxxxxxx> wrote:

Thanks Dennis.

Eliminating the pragma has no effect. Or rather, implementing the
pragma has no effect.

Man, I am _not_ a fan of EBCDIC. I can't have the source in my job
CCSID as the editors I'm using (jedit for instance) quite naturally
can't handle EBCDIC but this means I'm harassed by the compiler for
daring to have source in anything but CCSID 37... Yuck.



2011/3/4 Dennis Lovelady <iseries@xxxxxxxxxxxx>:
Well, unless I'm misreading, the documentation seems ambiguous since
it
doesn't indicate whether the CCSID in question is the SOURCE or
TARGET
CCSID, and doesn't indicate whether "the other side" is the Job
CCSID,
the file CCSID or something else.  You seem to think it's for
specifying
TARGET, and that SOURCE is the file's CCSID.  (You may be right; I'm
playing devil's advocate here.)

What happens when you eliminate the #pragma?
--
"We must believe in luck. For how else can we explain the success of
those we don't like?"
  -- Jean Cocteau

-----Original Message-----
From: Erik Olsson <erik.eo.olsson@xxxxxxxxx>
Reply-to: C programming iSeries / AS400 <c400-l@xxxxxxxxxxxx>
To: C programming iSeries / AS400 <c400-l@xxxxxxxxxxxx>
Subject: [C400-L] pragma convert of string literal
Date: Fri, 4 Mar 2011 15:52:27 +0100

this:

--
This is the C programming iSeries / AS400 (C400-L) mailing list
To post a message email: C400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/c400-l
or email: C400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/c400-l.


--
This is the C programming iSeries / AS400 (C400-L) mailing list
To post a message email: C400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/c400-l
or email: C400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/c400-l.

--
Sent from my Galaxy tablet phone with with K-9 Mail. Please excuse my brevity.
--
This is the C programming iSeries / AS400 (C400-L) mailing list
To post a message email: C400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/c400-l
or email: C400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/c400-l.



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
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.