RE: CPYFRMIMPF reason code 9

I am using the ERRRCDFILE option in the command, but it's not very helpful as you can imagine. All the rows from my inbound file are listed in the member SPSPOERR.

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

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.



-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of rob@xxxxxxxxx
Sent: Wednesday, January 14, 2015 10:19 AM
To: Midrange Systems Technical Discussion
Subject: Re: CPYFRMIMPF reason code 9

CPYFRMIMPF is awfully tough to handle when you need to deal with exceptions. Which is why I roll my own using the techniques I've learned following the Scott Klement tutorial on IFS.

I've never tried this, but if you want to try battling with CPYFRMIMPF for just a wee bit longer you may want to look at these parameters of CPYFRMIMPF Errors allowed . .
Error record file:
File . . . . . .
Library . . .
Member . . . . .

Perhaps the row you 'think' is the error isn't quite it.

When I rolled my own it:
- ran faster than CPYFRMIMPF
- gave me more granularity over exception reporting.
- didn't need modification with every release upgrade like CPYFRMIMPF will.


Rob Berendt