Mainframe Wednesday Talks# 13 MAINFRAME COBOL SOC7

Hello Everyone! here is the another video on Wednesday talks on mainframe COBOL SOC7
Why SOC7 Is Occurred ?
How to find the line of Statement
How to find the record it got abended with SOC7
What will be the Solution to fix ?
#kumaritchannel
#cobol
#cics
#mainframe

[@jharry74]

it's really the best way for a starter or an expert to understand the S0C7 mystery finding tricks ;).. Thanks again Kumar... expecting more videos .. good luck !!

[@KumarITChannel]

Glad you liked it

[@ojaswinidash]

Really you explained very well..i got clear idea after watching so many videos..now fully concept clear..Thank you so much ..want to see all new videos also.waiting ...

[@KumarITChannel]

So nice of you

[@RAVI9455237497]

Really helpful video. Keep posting that kind of contents. Cheers!

[@abilashsrinivasan7251]

Sir your videos are helpful 🙂.. Thanks much !! Easy understandable 👍

[@jharry74]

Thanks Kumar, can we use IS NUMERIC check to identify line number and data that causing S0C7 ?... Display may cause create huge logs if there are millions of input data processing or due to data sensitivity

[@ASMR-tx4bq]

It was really helpful since I'm new into mainframes .. could you also post the video regarding mainframe modernization and mainframe +devops

[@abhishekrajkumar4880]

awesome explanation..!!!

[@KumarITChannel]

Glad it was helpful!

[@Anilkumar-fl2ri]

Hi kumar If possible can you please make a video tutorial on DB2 comit and restart logic and which record got abended and how to restart with abended record ?with curoser hold option ?

[@KumarITChannel]

Sure Anil. Thanks for your inputs.. Good Day!!

[@Nothing-xd6re]

@@KumarITChannel When will i get video on it sir

[@Jashu0819]

Can you please help me on this: I have 6 files how to identify by which file the soc7 abend is occurred.

[@Raj_KrishnaOfficial]

Hi. Anyone explain How to resolve soc7 abend in production if the file is having millions of records and how to find the corrupted record with out using file-aid?

[@KumarITChannel]

Soc7 is also explained in the video that you are watching. But here is what you can do. SOC7 abend (or S0C7) in mainframes usually indicates a data exception error, often caused by a non-numeric value being found in a numeric field. Here's a simple 4-step process to find the corrupted record without using File-AID: Compile with Diagnostic Information: Recompile the COBOL program with the LIST (or MAP) option. This generates an assembly listing with offsets for each statement. Identify the Offset: When the S0C7 abend occurs, a system dump will be produced. In this dump, look for the offset where the abend occurred. This offset points to the instruction or statement in the program causing the issue. Locate the Faulty Statement: Using the offset from step 2, match it with the diagnostic information generated during the compilation (from step 1) to identify the exact statement or instruction in your COBOL program where the abend is happening. Narrow Down and Correct the Data: Now that you know where in the program the error is occurring, add diagnostic DISPLAY statements before and after the problematic code to print the data being processed. By running the program and examining the output, you can identify which record has the non-numeric data. Once identified, you can either correct the data in the input file or modify the program to handle such scenarios.

[@Raj_KrishnaOfficial]

Do you think we can do all this in Production. No right?

[@Rpachig]

Sir in real-time we can not change the code to write disply...then how will be identifing record number..pls help sir

[@Raj_KrishnaOfficial]

Hi. I am looking for this solution for a long time. Did you find the solution yet. If yes can you please help me

[@srihithakamani4641]

Hi can anyone please help me in COBOL tasks