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



This may not be correct for your situation, but isn’t there a value of *CALC for the 'To' CCSID? I have relied on this for CPYTOSTMF operations and it has worked for me in the past.

Paul
-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Joep Beckeringh
Sent: Tuesday, May 10, 2016 6:00 AM
To: midrange-l@xxxxxxxxxxxx
Subject: Re: CCSID problem?

Rob,

If you are planning to use stream files anyway, I wouldn't worry about the idiosyncrasies of CPYTOSTMF. Just open a stream file with CCSID 1208 and conversion will be handled automatically.

Joep Beckeringh
Pantheon Automatisering B.V.


Op 10-5-2016 om 10:55 schreef Rob Dixon:
My product ERROS produces quite sophisticated typeset printed output,
but I decided that I needed to be able to use a publishing package for
more refined printed results, so added a facility to ERROS to generate
XML (after reading Scott Klement's excellent "XML from RPG .." page on
his website). This has been fairly simple to implement (so far), and
if, in Client Access, I use wrklnk and open an XML file created by
ERROS, I get

Browse : /tmp/indexa.xml
Record : 1 of 77 by 18 Column : 1
Control :

....+....1....+....2....+....3....+....4....+....5....+....6....+....7....
************Beginning of data************** <?xml version="1.0"
encoding="utf-8" standalone="yes"?> <STIPPLE> <items_in_catalogue>
<B><I>Adm.l Rodney</I></B> #39414,</items_in_catalogue>
<method_of_engraving> stipple,</method_of_engraving> <engraver> Peltro
William Tomkins,</engraver> <Chapter_in_which_contained>
Heroes,</Chapter_in_which_contained>
<impression_details> RSD P # 1205</impression_details>
<items_in_catalogue> <B><I>The Age of Innocence</I></B>
#38064,</items_in_catalogue> <method_of_engraving>
stipple,</method_of_engraving> <engraver> Joseph Grozer,</engraver>
<Chapter_in_which_contained> Subject
Prints,</Chapter_in_which_contained>
<impression_details> RSD P # 1180</impression_details>
<items_in_catalogue> etc...

but if I map a network file (using the same Windows PC), and open
exactly the same file, using wordpad, I get rubbish -

Lo @ ~ K @ ~ ` @ ~
on%L n%L m m
n%L nL n K @ٖ La nLa n@{ kLa m m
n%L m m

Although I will change over to using the IFS directly, at this stage I
am using a physical file to store the XML and the command CPYTOSTMF to
put it in the IFS. Scott's website page suggests using the value
STMFCODPAG(1208) with this command. However, if I do this, I get

CPDA097 CCSID conversion not supported.
Cause . . . . . : The coded character set identifier (CCSID)
conversion
between codepage 1208 specified by the STMFCODPAG parameter and the
CCSID
285 specified by the DBFCCSID parameter is not supported to do all
necessary

conversions.

Recovery . . . : Set a different codepage or CCSID value and submit
the
command
again.

The value for the DBFCCISD parameter was *FILE The code page of my
program described PF is 65535 which was created using CRTPF. 285 (UK
English) is the code page for my job. The help text for DBFCCSID says

The database file CCSID is used, unless it is 65535.
If the database file CCSID is 65535, and the file is not a
program-described file, an error condition is created. If the
database file CCSID is 65535, and the file is a program-described
file, the default job CCSID is used.

I imagine that my problem is simply that I did not use code page 1208
and the stream file therefore has the coded character set ID 285.

I am using V5R1.

Can someone please suggest a solution? I am really stuck!

Many thanks

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

Please contact support@xxxxxxxxxxxx for any subscription related questions.


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.