× 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 Joel,

What do you mean by "fails"?

Do you mean that the command runs, but the data is in the wrong character set? Or do you mean that you get an error? If so, what does the 2nd-level text of the error say?

Also, is this happening on CPYFRMIMPF (as you put in the subject) or CPYTOIMPF (as you put in the body of the message)???


Harvell, Joel wrote:
I was bit on the butt a couple of weeks ago by a program I tested in our
Develop environment that worked great, but when the program ran for the
first time in production it failed. Here is the skinny.

The program does a CPYTOIMPF command with *STDASCII in the STMFCODPAG
field. In develop this works, on production it fails. If I change the
STMFCODPAG field to *PCASCII it works, but it fails if I make the same
change on develop. What do I need to look at to determine why *PCASCII
fails in develop but works in production, & *STDASCII works in develop
but fails in production??

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.