What is abend code 4038?
In this particular case, the abend 4038 is due to the COBOL application dynamically calling a module that is not available; this could be due to specifying an incorrect module name on the CALL or the module might not exist.
How do you resolve u4038 Abend in mainframe?
PROCEDURE DIVISION. DISPLAY “STARTING PROGRAM..” PERFORM INITIALIZATION PERFORM TERMINATION GOBACK. INITIALIZATION. DISPLAY “OPENING FILE..” OPEN INPUT INFILE IF WS-FILE-STATUS IS NOT EQUAL TO ’00’ THEN GO TO ERROR-EXIT END-IF.
What is Region parameter in JCL?
JCL REGION parameter is an optional keyword Parameter and you can define REGION parameter at either JOB Level or STEP Level or at both the places. If you define JCL REGION parameter at the job level, then it is the amount of virtual storage a job requires for execution.
How are Addrspc and region parameters used?
The system uses an EXEC statement ADDRSPC parameter only when no ADDRSPC parameter is on the JOB statement and only during the job step. Code a REGION parameter to specify how much central storage the job needs. If you omit the REGION parameter, the system uses the default.
What is Addrspc in JCL?
ADDRSPC parameter is used to indicate storage required by the system. The storage can be virtual (not real pagable) or central (real storage and nonpageable). ADDRSPC parameter is an optional parameter.
How to find the cause of a 4038 Abend?
There is a place to find exactly what caused a 4038 abend. Just look at where ever you have the CESE transient data queue pointing (a lot of shops have it pointing to SYSOUT, so you may have to browse CICS output in SDSF or similar product).
What does cee3191e mean in CICS Transaction Server for z/OS?
You receive an abend 4038 and message CEE3191E when running a program below the line in CICS Transaction Server for z/OS (CICS TS). A COBOL application running above the line is dynamically calling an assembler program that is running below the line. Whenever the call is made, the abend U4038 occurs.
What is error 4038 in COBOL?
In this particular case, the abend 4038 is due to the COBOL application dynamically calling a module that is not available; this could be due to specifying an incorrect module name on the CALL or the module might not exist. Language Environment (LE) is handling this error differently than COBOL handled it in the past.
What is Abend u4038 in COBOL?
A COBOL application running above the line is dynamically calling an assembler program that is running below the line. Whenever the call is made, the abend U4038 occurs. There is a mismatch in the Language Environment (LE) runtime options. ALL31 is OFF and STACK is set to ANYWHERE. U4038 is a generic abend code issued when no dump is requested.