SOC7 abend

Mukesh Pandey · Active User Joined: 11 Nov 2008 Posts: 143 Location: India

Hi,

Please help me in resolving the error. below are the info that i have gathered.

A Data Exception is caused when a computational-3 field has
an invalid digit (not 0-9), or its last byte contains an invalid
sign (not A, B, C, D, E, or F).

1FB79DB4
Operand = 00000000
#
The above field is in error
# - Sign is invalid

expat · Posted: Tue Oct 13, 2009 3:57 pm

Is this a continuation of your previous S0C7 thread ???

Mukesh Pandey · Active User Joined: 11 Nov 2008 Posts: 143 Location: India

expat... no... i find it difficult to trace the variable which is having invalid data in the pgm through abendaid.

Please guide.

Mukesh Pandey · Active User Joined: 11 Nov 2008 Posts: 143 Location: India

i am using xls in changeman as a abendaid. if there is any other way please let me know...

Thanks in advance,

Mukesh Pandey · Active User Joined: 11 Nov 2008 Posts: 143 Location: India

A-operand (TO field)

1FC19184
Operand = 0738124C

B-operand (FROM field)

1FB79DB4
Operand = 00000000
#
The above field is in error
# - Sign is invalid

This is what i get in the abendaid.

Thanks,

Robert Sample · Posted: Tue Oct 13, 2009 4:47 pm

Your error indicates that you have LOW-VALUES in a COMP-3 field. With what you have provided, that is all we can tell you. No source, no abend messages, no diagnostics -- nothing for us to go on.

And Abend Aid is extremely good at telling you not just the variables involved but the line of source code involved as long as you have a compile in the DDIO that matches the load module.

So the first question to ask is exactly what kind of help do you need? And the second question is what are you going to provide from the abend and dump that can help us help you?

Mukesh Pandey · Active User Joined: 11 Nov 2008 Posts: 143 Location: India

Robert and EXPAT,

i am using cman... and my job ended with SOC7. from SAR i got the offset. I need to know how to check the exact line causing the error. i use listing in cman to check the error having option L . or XLS to check the dump. but i am confused with the explanation showing hex values. My motive is to please guide me how to check the exact line of error in the pgm using abendaid. just a proper document would also help.

Thanks in advance.

Robert Sample · Posted: Tue Oct 13, 2009 7:57 pm

Do you mean you are using CHANGEMAN when you say "cman"? If not, what is "cman" -- I've never heard the term (but then I've only been working on mainframes for 32.5 years)? What language are you coding in -- C? COBOL? PL/I? Assembler? There are many choices on the mainframe.

Usually the dump output will include the module (CSECT) in which the abend occurred, and the offset in that module -- and I know that Abend Aid output includes this data. Compiler output can be customized to include pseudo assembler for each line of source code; that output can be used with the offset from the dump to determine which line of source had the error. Once that is done, the variables can be reviewed to determine which one has the bad data and where it came from.

If you do not understand packed decimal, binary, and display formats for data items you need to spend serious time in the manuals before attempting to write another line of code for a mainframe. Numeric representations on mainframes differs -- often radically -- from numeric representations on other platforms and you must understand the possible formats to understand error messages that are generated.

Mukesh Pandey · Active User Joined: 11 Nov 2008 Posts: 143 Location: India

Thanks Robert for your valuable information and suggestions. by cman i mean changeman and i am coding in cobol. surely i will go through the data formats suggested by you.

Thank you.

Robert Sample · Posted: Wed Oct 14, 2009 3:07 pm

COBOL compiler options LIST,NOOFFSET will generate a pseudo assembler listing in the compile output.