Author: Robert Sample
Posted: Tue Nov 15, 2016 12:50 am (GMT 5.5)
First, the region size will have absolutely NOTHING to do with your problem -- so why are you changing it? Changing random things hoping the problem will go away is NOT a valid debugging method. Increasing the data set (note that it is NOT a "file") space may resolve the file status 34, but it depends on why the file status 34 occurred.
Second, the file status 34 may be the direct cause of the S0C4 ABEND. You've posted nothing that would allow us to help you determine this, though.
Third, the file status 34 may have nothing to do with the S0C4 ABEND. Again, you've posted nothing that would allow us to help you determine this.
_________________
TANSTAAFL
The first rule of code reuse is that the code needs to be worth re-using.
"We should forget about small efficiencies, say about 97% of the time: premature optimization is the root of all evil." -- Donald Knuth
Posted: Tue Nov 15, 2016 12:50 am (GMT 5.5)
| Quote: |
| I increased space of file and also tried with max region for the job but still getting same error. |
Second, the file status 34 may be the direct cause of the S0C4 ABEND. You've posted nothing that would allow us to help you determine this, though.
Third, the file status 34 may have nothing to do with the S0C4 ABEND. Again, you've posted nothing that would allow us to help you determine this.
_________________
TANSTAAFL
The first rule of code reuse is that the code needs to be worth re-using.
"We should forget about small efficiencies, say about 97% of the time: premature optimization is the root of all evil." -- Donald Knuth