for delete a record from input file which is causing SOC7,
Is it necessary to copy input file from production to testing environment?
OR We can do it in production environment itself.
Production Support
Moderators: dbzTHEdinosauer, Moderator Group
As i already answered in other thread.
Normally, client wont allow us to deleted any production data.
If you get client approval on that, delete it in production itself.
otherwise... copy production data to development and and delete that
record and reload production file with development file ( if client is ok with that )
Normally, client wont allow us to deleted any production data.
If you get client approval on that, delete it in production itself.
otherwise... copy production data to development and and delete that
record and reload production file with development file ( if client is ok with that )
Natarajan
Chennai
Chennai
-
- Moderator
- Posts: 1625
- Joined: Sat Aug 09, 2008 9:02 am
- Location: Mumbai, India
Actually it's more likely should be answered from Your Shop Management - what kind of policies do you have comes into picture here?
S0C7 is an error that means you had a check exception while your job was executing. Most often this error occurs because of spaces being moved into a packed decimal field. It can also occur if you move this to a numeric field. Somewhere you are mismatching data that is causing this to crash, you can also go through your job dump to find the exact line causing the crash to determine where in your code this needs to be corrected.
None of these says- delete some data.. , unless 'am I missing some more reasons..
Well, again, this error should never occur in production, as this often can occur in test while your mainframe code is being tested for the first time.
How do you conclude that deleting is the only solution?for delete a record from input file which is causing SOC7,
S0C7 is an error that means you had a check exception while your job was executing. Most often this error occurs because of spaces being moved into a packed decimal field. It can also occur if you move this to a numeric field. Somewhere you are mismatching data that is causing this to crash, you can also go through your job dump to find the exact line causing the crash to determine where in your code this needs to be corrected.
None of these says- delete some data.. , unless 'am I missing some more reasons..
Well, again, this error should never occur in production, as this often can occur in test while your mainframe code is being tested for the first time.
Regards,
Anuj
Anuj
FREE TUTORIALS
Tutorials
Free tutorials from mainframegurukul
- JCL Tutorial
Covers all important JCL concepts. - Cobol Tutorial
This tutorials covers all Cobol Topics from STRING to COMP-3. - DB2 Tutorial
DB2 Tutorial focuses on DB2 COBOL Programming. - SORT Tutorial
This Tutorial covers all important aspects of DFSORT with examples - CICS Tutorial
This CICS tutorial covers CICS concepts and CICS Basics, CICS COBOL Programming.
Interview
Mainframe Interview questions
- Cobol Interview Questions
50+ Interview Questions - JCL Interview Questions
50+ Interview Questions - DB2 Interview Questions
100+ Interview Questions - CICS Interview Questions
70+ Interview Questions - VSAM Interview Questions
27 Interview Questions
Other References
Mainframe Tools and others
- XPEDITER Reference
Explains how we can debug a program - FILEAID Reference
Explains how to browse , edit and delete datasets - Change Man Reference
Quick Start tutorial on Changeman - Abend Reference
Important Abend codes explained - FaceBook Page
MainframeGurukul FaceBook Page - LinkedIn Page
MainframeGurkul Linkedin Page