RE: Problem with CPYFRMIMPF

["Harvell, Joel" <jbharvell@xxxxxxxxxxxx>]

Oops sorry about that, it is the CPYTOIMPF

I get CPF2845 -- The copy did not complete for reason code 1.

The CCSID = 37 on the file, I'm copying on both systems.  The file I'm
coping from is an Externally Described file.

Be seeing you...B

Joel B. Harvell
Food Lion, LLC
(704) 633-8250 x2709
jbharvell@xxxxxxxxxxxx


-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Scott Klement
Sent: Monday, November 10, 2008 12:28 PM
To: Midrange Systems Technical Discussion
Subject: Re: Problem with CPYFRMIMPF

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??