Job is abending with U4095

b4uthammi · New User Joined: 21 Feb 2005 Posts: 14 Location: hyderabad

Hi,

I am calling pgm B from pgm A. At The time of execution of pgm B,my job is abending with U4095.

Below is the message i am getting.

A U4095 abend occurred during execution of program PAYDUMPX (assembler routine).

Please help me in this regard.How can i resolve this one.

Thanks
Tr.

William Thompson · Posted: Mon Nov 27, 2006 3:53 pm

Information is power.....

http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/BOOKS/CEEA106/3.8.21?SHELF=&DT=19990120151826&CASE=

U4095 (X'FFF')

Explanation: An abend was issued as a response to the fatal return code of a Language Environment-conforming language.

Reason codes:

<X'12C' (<300)
The reason code is set to the Language Environment-conforming language ID.
X'12C' (300)
The condition was provoked from a user handler attention routine.
X'12D' (301)
The condition was provoked from a user handler routine.

Programmer Response: See system programmer.

System Action: Enclave terminated.

mann_naaz · New User Joined: 13 Dec 2006 Posts: 4 Location: Pune

U KNOW WHAT IS U4094 ABEND CODE
FOR

IT COMES WHILE I M RUNNING THE JOB
WHICH TAKES 1 INPUT AND DISPLAYS IN OUTPUT
I HAVE OPENED OUTPUT IN EXTEND MODE

William Thompson · Posted: Wed Dec 20, 2006 7:16 pm

Information is power..... same fine manual, one topic earlier....

http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/BOOKS/CEEA106/3.8.20?SHELF=&DT=19990120151826

U4094 (X'FFE')
Explanation: An abend was issued during termination, when errors were detected.
Reason codes:
X'04' (4)
An invalid parameter to termination services was discovered.
X'08' (8)
A language-specific event handler returned an invalid return code.
X'0C' (12)
A language-specific event handler returned to termination with a return code, causing immediate termination.
X'10' (16)
Condition management could not properly terminate.
X'14' (20)
Program management could not properly terminate.
X'18' (24)
Storage management could not properly free stack and/or heap storage. This might be due to writing beyond storage.
X'1C' (28)
Storage management could not properly free the initial storage allocation.
X'20' (32)
The user stack was unable to be collapsed using GOTO.
X'24' (36)
The fixed-size termination stack overflowed.
X'28' (40)
An unhandled condition of severity 2 or greater occurred in a created enclave with TRAP(OFF) set in the creating enclave. Under CMS, this abend is issued when a severity 2 or greater condition is unhandled in a nested enclave, or a debugging tool has terminated the enclave at the user's request.
In addition to TRAP(OFF), this abend can also result when a parent enclave save area chain cannot be located, even though two enclaves existed, thus causing an attempt to propagate the failing condition. When the parent enclave received control, the save area chain was not intact, and the ABEND was percolated.
An example of this is a COBOL program that is invoked without a LINK SVC and with a reusable run-time environment. On return from the COBOL program, the Language Environment enclave still exists, because of the reusable environment. When a second COBOL program is invoked by a LINK SVC, any Language Environment attempt to create a second enclave does not succeed. In an attempt to propagate this error condition to the parent enclave, Language Environment issues an abend. When the first enclave is not in the current save area chain, Language Environment percolates this abend. See OS/390 Language Environment Programming Guide for information about nested enclaves.
X'2C' (44)
Termination requested during termination.
X'30' (48)
Condition management for OpenEdition MVS could not properly terminate.
X'34' (52)
The OpenEdition MVS environment could not properly terminate.
X'38' (56)
A language-specific event handler returned to thread termination with a return code, causing immediate termination.
X'3C' (60)
An internal logic error occurred during recursive termination handling.
X'40' (64)
An internal logic error occurred during forced thread termination handling.
X'44' (68)
An internal logic error occurred because termination was not expected.
X'48' (72)
During termination, library latches were being held and could not be released, causing immediate termination.
X'4C' (76)
Library latch services have received an unrecognized latch request, causing immediate termination.
X'4E' (78)
A language-specific event handler returned to thread termination with a return code, causing immediate termination.
Programmer Response: See system programmer.
System Action: Enclave terminated.