RE: CPYFRMIMPF V5R3 error? -- MIDRANGE-L

My apar must be different.

Rob Berendt
-- 
Group Dekko Services, LLC
Dept 01.073
PO Box 2000
Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com





ron_adams@xxxxxxxxxxxxxx 
Sent by: midrange-l-bounces@xxxxxxxxxxxx
09/21/2004 09:15 AM
Please respond to
Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>


To
Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
cc

Fax to

Subject
RE: CPYFRMIMPF V5R3 error?






Apparently, APAR SE17348 has been opened/closed to resolve this issue.
However, I don't see a PTF available for yet, though. I assume it will be 
in the next DB CUMe PTF group.

For the interim, IBM gave us a workaround to have the cmd use the V5R2 
version. 

Ron Adams
Information Technology Group
Crane Valves
9200 New Trails Dr. Suite 200
The Woodlands, TX 77385
Office: 281-298-5463 x104
Direct: 281-465-3054
Cell: 281-216-7721





rob@xxxxxxxxx
Sent by: midrange-l-bounces@xxxxxxxxxxxx
09/21/2004 08:02 AM
Please respond to Midrange Systems Technical Discussion

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


We have ptf SI15133 on.  However we also have an apar that just opened 
regarding CPYFRMIMPF.  Ok, our pmr opened on April 7, ptf SI15133 was put 
on 8/19, and they recently were finally able to duplicate it at their 
office to get the same condition and now finally opened the apar.

CPYFRMIMPF uses the SQLCLI api's.  And it was a contest as to whether the 
api's were in error or the way they were called (two different teams).  I 
think it has to do with just the wrong combination of CCSID's.  IBM is 
really being a stickler on CCSID's with V5R3 in a lot of areas.

Rob Berendt
-- 
Group Dekko Services, LLC
Dept 01.073
PO Box 2000
Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com





"Cox, Joe" <joecox@xxxxxxxxxxx> 
Sent by: midrange-l-bounces@xxxxxxxxxxxx
09/20/2004 01:14 PM
Please respond to
Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>


To
"Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx>
cc

Fax to

Subject
RE: CPYFRMIMPF V5R3 error?






We ran into similar problems with CPYFRMIMPF after upgrading from V5R2
to V5R3.  PTF SI15133 for 5722SS1 fixed that.  In addition Client access
data transfers treated nulls and spaces differently after the upgrade.
Prior to the upgrade '' and ' ' were treated the same in selection
criteria.  After the upgrade they were not.  The PTF did not change that
behavior.

Sorry for the time lag,  I've been out for a week.

Joe Cox
Director Information Systems
MSU Foundation Inc.
1501 S 11th Avenue
Bozeman, MT  59717
(406) 994-2416
joecox@xxxxxxxxxxx

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of
ron_adams@xxxxxxxxxxxxxx
Sent: Tuesday, September 14, 2004 7: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.



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