SYSTEM ABENDS
I am sure everyone is aware of system ABENDS. I have tried to list ABENDS for all the possible reasons. Hope you all find it useful.SOC 1
This abend can be faced in following situations. Rule out following possibilities:- Any file doesn't have open statement and directly trying to read it
- The subscript it may be out of boundary for a defined COBOL table
- Review JCL for missing or misspelled DD name
- Problem in parm passed to subroutine related to addressing mode or Data mode
- Recording mode may be wrong
- Sub program called is not found problem in dynamic link or static link
- Check load module there can be a possibility if subroutine program id and program name not same. This means bad load module.
- An uncontrolled loop moved data on top of instructions.
- Problem can be same name for array and subroutine
SOC 7
This is a data exception and can only occur when decimal (packed) instructions are used.
This is a data exception and can only occur when decimal (packed) instructions are used.
- When alphanumeric data moved to packed decimal data (COMP 3).
- When Programmer use a variable, which is not defined in working storage.
- Period missing after imperative statements within AT END clause.
- Binary field in an arithmetic operation is not large enough to accept result.
- Failure to initialize a counter.
- Invalid incoming data (e.g., blanks, decimal points, or commas in a numeric field).
- Exceeding a table via a subscript (index) error, causing a reference to invalid data.
- Moving zeroes or low-values to a group field defined as numeric.
- An omitted or erroneous usage clause.
- Passing parameters between programs in the wrong order.
No comments:
Post a Comment