4038 is a generic abend code which encompasses many 'user' abends.
I remember specifying a small region parameter resulting in ABEND U4038. The cure was to increase the region card on the job.
Here are some other cases:
1) You create JCL to test a COBOL program and you accidentally change a DDNAME that is used by the program. You submit the job and it abends with a U4038.
2) Mismatching record-length to the physical file's record length.
I will let U know if any I come across any other Reason.
Bye.
Adding to that point...U4038 occurs when memory not available for STEP to execute. Suppose for DB2 steps REGION=8M should be given to avoid this abend.
An important point is to note that when there is some other abend and the dump is being produced in spool and all the memory available for this dump gets exhausted it results in U4038. So you should go through the complete log to figure what was the original problem to be solved.
Are the two same or not? I am asking because, I am getting S4038 every day. I think its something to do with file handling. But I am struggling to get through this one.
One of the situation where you encounter the 4038 error will be out of range. If you compile with the Compiler option SSRANGE then you might not receive the out of range problem.
More in detail if you would like to know.
Sai
learnmf wrote:
Hi Friend
Quote:
I want to know about u4038 abend.
As we get it on not mentioning stop run.
What are the other things due to which it occurs.
