CPYTOARCF and CPYFRMARCF -- MIDRANGE-L

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

Subject: CPYTOARCF and CPYFRMARCF
From: Justin Taylor <JUSTIN@xxxxxxxxxxxxx>
Date: Wed, 5 Dec 2018 19:21:23 +0000
List-archive: <https://archive.midrange.com/midrange-l/>
List-help: <mailto:midrange-l-request@midrange.com?subject=help>
List-id: Midrange Systems Technical Discussion <midrange-l.midrange.com>
List-post: <mailto:midrange-l@midrange.com>
List-subscribe: <https://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <https://lists.midrange.com/mailman/options/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=unsubscribe>

CPYFRMARCF seems to have CCSID issues. It unzipped a text file and assigned it to CCSID 37. It appears unreadable when my app reads it. 5250 shows it OK, but gives this warning:
Cause . . . . . : The file Coded Character Set Identifier (CCSID) was 00037, but the data in the file looks like ASCII. A CCSID of 00819 is being used.

Does anyone know a way around this?

Thanks

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

Re: CPYTOARCF and CPYFRMARCF , Jack Kingsley

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.