How to sort using COMP-3 variable

vinodkumarrs · New User Joined: 31 Mar 2008 Posts: 8 Location: india

Hi,

I have a 12 byte COMP-3 field from byte 230-235 as shown below. i need to sort the records based on the 5-7 bytes of the field, ie with the value 302, in the given record. The input file is of 403 byte length.

[img]C:\Documents and Settings\169685\Desktop\record[/img]

Thanks in advance.[/img]

vinodkumarrs · New User Joined: 31 Mar 2008 Posts: 8 Location: india

Girish Firke · New User Joined: 04 Feb 2009 Posts: 5 Location: Mumbai

Hi Vinod,

Sort control card syntax for packed decimal values will be
SORT FIELDS=(Starting Position, Length, PD,A)

By looking at your question I am getting that you want to sort the 3 bytes from 5 character of a comp-3 field. If that is the case then please try below control card and let me know whether it works fine or not.

In your case

SORT FIELDS=(232,02,PD,A)

vinodkumarrs · New User Joined: 31 Mar 2008 Posts: 8 Location: india

Hi Girish,

The SORT FIELDS=(232,02,PD,A), will take 4 bytes to check. In my case it will take the value '3021' for sorting, I need only upto '302'.

Thanks,
Vinod

Girish Firke · New User Joined: 04 Feb 2009 Posts: 5 Location: Mumbai

Hi,

Your screenshot shows the hexa-decimal value of the record.

The hex-decimal value X'30' represent one ascii character and X'21' represents another ascii character.

I am not sure whether we can sort those as per your requirement.

Garry Carroll · Posted: Tue Feb 10, 2009 4:23 pm

Also, since you are not checking the entire packed field, specifying PD for the sort is invalid.

You could try INREC processing to expand the COMP-3 field into an appended work field and sort based on the expanded 3 characters in that field. Then use OUTREC processing to drop the work field.

Garry.

vinodkumarrs · New User Joined: 31 Mar 2008 Posts: 8 Location: india

I tried the above mentioned logic and it worked. thanks

Garry Carroll · Posted: Tue Feb 10, 2009 6:20 pm

Thanks for letting us know, Vinod.

Glad to have been able to help.

Garry.

Frank Yaeger · Posted: Tue Feb 10, 2009 10:09 pm

Here's a much easier way to do this using DFSORT's bit notation for the length:

vinodkumarrs · New User Joined: 31 Mar 2008 Posts: 8 Location: india

This also works fine.
Since I need 3 bytes to compare I modified as below.

Frank Yaeger · Posted: Wed Feb 11, 2009 9:47 pm

Huh? You are dealing with 2 bytes (232-233), not 3 bytes.

1.4 for the length means 1 byte and 4 bits. 1.3 for the length means 1 byte and 3 bits. 1.4 for the length would give the correct results for all cases whereas 1.3 for the length wouldn't.

As an example, if 232-233 had records with these hex values:

3010
3000
3030
3020

Using 232,1.4 you would correctly get these output records:

3000
3010
3020
3030

Using 232,1.3, you would incorrectly get these output records:

3010
3000
3030
3020

As you can see, that fourth bit does matter.

vinodkumarrs · New User Joined: 31 Mar 2008 Posts: 8 Location: india

Hi,

I got the same results when I tried with 232,1.3 as well as 232,1.4 bytes.
Anyway I got the point that Frank mentioned above. Hence I will follow with the 232,1.4 option. Thanks for the clear explanation.

Regards,
Vinod

dick scherrer · Posted: Thu Feb 12, 2009 10:10 am

Hello,