The input file has 121,530,021 records. The actual job took 4 minutes elapsed time and the impression I get is that it read the WHOLE file.
Quote:
ICE054I 0 RECORDS - IN: 121530021, OUT: 121530021
ICE227I 0 FORSTA : DELETED = 121529021, REPORT = 0, DATA = 1000
ICE228I 0 FORSTA : TOTAL IN = 121530021, TOTAL OUT = 1000
Can someone explain why it would do that when I've specified a value in ENDREC (which, logically to me, should ensure that DFSORT "knows" when it's read enough records). _________________ Michael
What I think you're asking is "why doesn't the OUTFIL I coded do that?"?
I think you'd be asking for code for a very specific case: a COPY operation, no SORTOUT and only one OUTFIL. The relationship here between SORTIN and OUTFIL is coincidental only. As soon as you actually SORT, that pseudo-relationship is broken. If you have SORTOUT, that pseudo-relationship is broken. If you have two OUTFILs.... well, you get the picture.
And where what you want to achieve can be done anyway by limiting the SORTIN with what is available to do that.
Although it may appear neat if it worked like you seem to want, you'd have more code in several places just to achieve that. Just a waste.
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum