RE: CPYFRMIMPF V5R3 error?

["Goodbar, Loyd (ETS - Water Valley)" <LGoodbar@xxxxxxxxxxxxxx>]

Is the *FLDDFT value still valid for RPLNULLVAL? I hope this doesn't go away
in V5R3, and *NULLVAL should be an additional value.

Thanks,
Loyd

Loyd Goodbar
Senior programmer/analyst
BorgWarner
E/TS Water Valley
662-473-5713
-----Original Message-----
From: ron_adams@xxxxxxxxxxxxxx [mailto:ron_adams@xxxxxxxxxxxxxx] 
Sent: Tuesday, September 14, 2004 11:40
To: Midrange Systems Technical Discussion
Subject: RE: CPYFRMIMPF V5R3 error?

The parm is RPLNULLVAL the options are *NO or *NULLVAL, default is *NO.

I messed around with this, but still the same results.

What's strange is the error message is not telling me which field (*N) is 
in error, and it is telling me this on every record. I have looked at the 
input file and don't see any records with blank/null values.

Ron Adams
Information Technology Group
Crane Valves
9200 New Trails Dr. Suite 200
The Woodlands, TX 77385






"DeLong, Eric" <EDeLong@xxxxxxxxxxxxxxx>
Sent by: midrange-l-bounces@xxxxxxxxxxxx
09/14/2004 10:48 AM
Please respond to Midrange Systems Technical Discussion

 
        To:     "'Midrange Systems Technical Discussion'"
<midrange-l@xxxxxxxxxxxx>
        cc: 
        Fax to: 
        Subject:        RE: CPYFRMIMPF V5R3 error?


Ron, I believe there's a new parm (in V5R1 I think) for how to handle null
values.  CSV files with null values need to map to a database file that
supports nulls, or you must tell it to initialize the field to a default
value. 

Eric DeLong
Sally Beauty Company
MIS-Project Manager (BSG)
940-898-7863 or ext. 1863



-----Original Message-----
From: ron_adams@xxxxxxxxxxxxxx [mailto:ron_adams@xxxxxxxxxxxxxx]
Sent: Tuesday, September 14, 2004 8:04 AM
To: 'Midrange Systems Technical Discussion'
Subject: CPYFRMIMPF V5R3 error?


We just upgraded to a new 520 running V5R3 (from V4R5) and are 
experiencing trouble with CPYFRMIMPF in a process that worked flawlessly 
prior to the conversion.

Nothing has changed (that I know of), it still works on the old machine/OS 

version. The From and To files and the FDF are all the same.

I'm getting error CPF2845 - The copy did not complete for reason code 7.
   7 - The FROMFILE numeric field *N contain blank characters, or other 
 characters that are not valid for a numeric field. 

This is my Command,

CPYFRMIMPF FROMFILE(SVFDTA/CPOFILE) 
           TOFILE(SVFDTA/MAN010P) 
           MBROPT(*ADD) 
           DTAFMT(*FIXED) 
           RMVBLANK(*NONE) 
           FLDDFNFILE(SVFSRC/QDDSSRC MAN010PFDP)
           FROMRCD(1 5) 

So, what changed from V4R5 to V5R3 to muck this up? I read some stuff in 
the KB about CCSID differences, do I need to take that into heavy 
consideration? The CCSID on the Fromfile is 500, the CCSID of the Tofile 
is 37.

Ron Adams
Information Technology Group
Crane Valves
9200 New Trails Dr. Suite 200
The Woodlands, TX 77385
--
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.




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



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