Page 2 of 2

Re: Building one output file from two input files

PostPosted: Tue Aug 24, 2010 11:24 pm
by dick scherrer
Hello,

Dick, I did use the preview but I guess I misunderstood the "Code" tag thing.
If the "Preview" looks like you want, then Submit. It the preview is not exactly what you want, make changes and preview again.

If Submit is not clicked, the work will be lost when you move away from that page. . . And there is no warning - it is just "gone:" ;)

Re: Building one output file from two input files

PostPosted: Wed Aug 25, 2010 2:36 am
by Frank Yaeger
I'll have to try and find some more information about the Temp area, I thought I could use it as an area to build the records but I guess not.


I don't know what you mean by "the Temp area". DFSORT doesn't have one. A common technique with DFSORT is to add fields temporarily after the end of your records and then remove them. But we don't call that a "Temp area".

Re: Building one output file from two input files

PostPosted: Thu Aug 26, 2010 1:55 am
by IRHamilton
Frank Yaeger wrote:
I'll have to try and find some more information about the Temp area, I thought I could use it as an area to build the records but I guess not.


I don't know what you mean by "the Temp area". DFSORT doesn't have one. A common technique with DFSORT is to add fields temporarily after the end of your records and then remove them. But we don't call that a "Temp area".
My apologies, beginner messing up.

What I'm calling the temp area, which I guess is wrong, is when you copy records to temp storage . . .

COPY FROM(INFL) TO(TEMP1) USING(CTL1)

I thought I could build records, field by field, using this area but it didn't work out in this case. Lack of knowledge.

Thanks again for your help.

Re: Building one output file from two input files

PostPosted: Thu Aug 26, 2010 3:09 am
by Frank Yaeger
FYI, TEMP1 is referred to as a "temporary data set" meaning it is just needed for the step and not kept permanently. "temp area" would imply a temporary storage area.