SYNCTOOL: No abend but data format is not correct

expat · Posted: Wed Apr 04, 2007 6:33 pm

Girija

This looks amazingly similar to the problem we solved yesterday. What are you doing that is different ?

Girija · New User Joined: 29 Jul 2005 Posts: 14 Location: Mysore

I am not denying that...

But the output should be as follows:

second file having LRECL = 31
First File having LRECL = 166

What happening in the output is as follows:

Output LRECL = 200
Second file data is displaying for the first 31 bytes - that is fine with me
First File data having 166 bytes of data. In that, first 31 bytes displaying at the end of the output file(from 167 to 197th position) but it is supposed to display from 32nd position in the output file, hence i am not getting the format I required.
Remaining data should display after this.

Only Problem I am facing first file data that to 31 bytes, it was supposed to display from 32 position , displaying from 167 position.
I know I made some mistakes in declaring OUTREC fields, but I am not getting what is the mistake i have done.

Sortparm are as follows:

TSPDS.SORTPARM(TPSORT06) -
***************************
OUTREC FIELDS=(1,31,32:166X)
**************************

TSPDS.SORTPARM(TPSORT07) - 01.

****************************
OUTREC FIELDS=(1,166,167:1,31)
****************************

TSPDS.SORTPARM(TPSORT08)
----------------------------------------
COPY FROM(IN1) TO(T1) USING(CTL1)
COPY FROM(IN2) TO(T1) USING(CTL2)
SPLICE FROM(T1) TO(OUT) ON(1,6,CH) WITH(32,166) WITHALL

Please let me know any mistakes, done while defining OUTREC fields?

expat · Posted: Wed Apr 04, 2007 7:07 pm

This is how we redefined the shorter records yesterday, and your code does not look like what is coded here.

Girija · New User Joined: 29 Jul 2005 Posts: 14 Location: Mysore

ya, this is a different case.

First File contains lesser record length compared to second file. I come to know if the second file is having shorter records.

In this scenario,
First File having LRECL-31
Second File LRECL-166

Earlier we discussed with
First File LRECL- 500
Second File LRECL-115

If second file having more LRECL, then how to defined OUTREC in TPSORT07

Currently i have defined as follows:
TSPDS.SORTPARM(TPSORT07)
****************************
OUTREC FIELDS=(1,166,167:1,31)
****************************

By giving this , data formatting not displaying properly.

expat · Posted: Thu Apr 05, 2007 12:18 pm

Take avery close look at what we did on Tuesday.

With the shorter record we added the correct number of blanks to make the record length the same as the longer record, and then what did we do with the original shorter record ?

And for the longer record what did we do, we did not take the first 31 bytes of this record and stick it on the end .................... did we ? SO what did we put on the end of this record ?

Girija · New User Joined: 29 Jul 2005 Posts: 14 Location: Mysore

IF the first file is longer than second file, then we can adjust the second file, hence data format would be fine.

But now in the second scenario, first file having lesser compared to first one. Hence not getting the format I required.

If I match second file length by comparing first file, here it won't work and even I can't give Banks here as you know second file containing full 166 bytes of data, but some how not getting the format I REquired.

Output file conatining 200 Bytes....
in the out file - getting data format as below:

1-31, 31 bytes from second file
32-166, first file data starting from 32nd byte
167-197, first file data starting from 1st byte

What I need is ...

1-31, 31 bytes from second file
32-197, first file data starting from 1st byte

Now i think My question is clear to everybody....

expat · Posted: Thu Apr 05, 2007 1:25 pm

The problem as far as I can see is exactly the same as the one that was resolved on Tuesday, just with different record lengths.

expat · Posted: Thu Apr 05, 2007 1:45 pm

FILE2 - Increase from 31 to 31 + 166 BLANKS.

FILE1 - Pos 1-6, the key, leave as is, BLANKS in pos 7 - 31, pos 32 = 166 bytes of original FILE1 record.

Not sure if the order of the records in T1 can affect the result, but I would try by swapping the order in which the records are written to T1, doing the shorter ones first. May not affect it, let me know what happens.

Girija · New User Joined: 29 Jul 2005 Posts: 14 Location: Mysore

If I specify outrec fields mentioned as above, getting data format issue,
please can you let me know what I need to specify.

Girija · New User Joined: 29 Jul 2005 Posts: 14 Location: Mysore

Hi,

I tried as per the positions mentioned below:

FILE2 - Increase from 31 to 31 + 166 BLANKS.

FILE1 - Pos 1-6, the key, leave as is, BLANKS in pos 7 - 31, pos 32 = 166 bytes of original FILE1 record.

------------------

FILE2 - Increase from 31 to 31 + 166 BLANKS. - this is fine

FILE1 - Contains all 166 bytes of original FILE1 record, hence i speicify Blanks from 7-31, then in the output it displays Blanks and loosing 25 bytes of data

expat · Posted: Thu Apr 05, 2007 4:23 pm

I was saying that you move the 166 byte record along to position 32 so that it gets spliced with the 31 bytes of the file2 record.