Re: CPYFRMIMPF reason code 9 -- 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.

On Wed, Jan 14, 2015 at 11:24 AM, Anne Boninsegna
<a_boninsegna@xxxxxxxxxxx> wrote:

In the meantime, I've downloaded Scott Kement's tutorial as advised... 91 pages of "short reading". :(

Do you know any other programming languages? If so, and if you do
decide to roll your own, you may want to use some other language.
Personally, I use Python for almost everything. Even if you don't
know Python, if you can program in almost any other language already,
it *might* be quicker to learn just enough Python and then use its
facilities, than to roll your own in RPG.

But I definitely agree with Gary that the first and best thing to do
is to inspect the raw incoming file to try to identify the problem.
You'll want to do this anyway, whether you are fixing the data before
feeding it to CPYFRMIMPF or rolling your own replacement for
CPYFRMIMPF.

I've been using CPYTOIMPF for years without issue/modification (through release upgrades), but this is the first I've needed to toy with the inbound version.

That's not too unusual. Reading data into a database is almost always
harder and prone to snags than writing data out.

John

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.