Movement of COMP-3 fields

dilipbiradar · Posted: Thu Aug 06, 2009 11:25 am

Hi,

I have two fields A and B, both are COMP-3 S9(17)

A is being moved to B.

Some Displays of A and B after the program execution

A=0000000000020920C
B=00000000000209203

A=0000000000000187M
B=0000000000000187M

A=0000000000000900}
B=0000000000000900}

The field is being used as an input in some other program which is giving the SOC7 error.

Please advice.

dilipbiradar · Posted: Thu Aug 06, 2009 11:34 am

Beg your pardon........

The A field is PIC S9(17) only..not the COMP-3

Binop B · Posted: Thu Aug 06, 2009 1:02 pm

Hi Dilip,

As per you post, it looks like you are having a loop which is processing each record. Most probably one of these records might be having corrupt data for this field which is causing the SOC7 abend.

Bill O'Boyle · Posted: Thu Aug 06, 2009 3:30 pm

The last position is the SIGN byte.

Please review the following Sticky -

ibmmainframes.com/viewtopic.php?t=40254

Bill

dick scherrer · Posted: Thu Aug 06, 2009 8:03 pm

Hello,

In the program that does the "move", suggest you code an IF to check if the A value is numeric before doing the move. . .

A decision needs to be made on what action to take if the value is not numeric (abend the code, issue an error, etc).

Bill O'Boyle · Posted: Thu Aug 06, 2009 8:24 pm

Adding to Dick's suggestion, if the field is display-numeric signed but the data has an 'F' zone in the last-byte, instead of a 'C' or a 'D', the numeric check will fail because the translate-table being used to validate the display-numeric signed-field doesn't consider an 'F' zone as a valid sign for a display-numeric signed-field.

This is also true vice-versa, if you had a 'C' or 'D' zone in the last-byte of an unsigned display-numeric field, the numeric test will fail as well, because the translate-table is expecting an 'F' zone in the last-byte.

Just my .02 cents....

Bill