Portal | Manuals | References | Downloads | Info | Programs | JCLs | Master the Mainframes
IBM Mainframe Computers Forums Index
 
Register
 
IBM Mainframe Computers Forums Index Mainframe: Search IBM Mainframe Forum: FAQ Memberlist Usergroups Profile Log in to check your private messages Log in
 

 

Bebug Tool error:EQA2456I

 
Post new topic   Reply to topic    IBMMAINFRAMES.com Support Forums -> IBM Tools
View previous topic :: :: View next topic  
Author Message
icetree521

New User


Joined: 04 Apr 2010
Posts: 13
Location: hangzhou, china

PostPosted: Thu Nov 18, 2010 12:49 pm    Post subject: Bebug Tool error:EQA2456I
Reply with quote

Hi all,

I've got a extremly strange question. in my program( type is PLIDCOM) I use FETCH a module then CALL it in a loop, but when using DebugTool, only the first time CALL the module will return a EQA2456I error, the second and third time will be ok.

Also, i can prove when running my program without DebugTool, the module can be called successfully, including the first time.

so have anyone met the same problem before? thanks!


Here is the Error message in DebugTool when first time call the fetched module:

The operating system has generated the following message:
EQA2456I Returning from enclave where Debug Tool was initialized
Handling of non-LE events has been suspended. Debugging of non-LE
programs is suspended in this Debug Tool session.
Back to top
View user's profile Send private message

PeterHolland

Global Moderator


Joined: 27 Oct 2009
Posts: 2422
Location: Netherlands, Amstelveen

PostPosted: Thu Nov 18, 2010 12:53 pm    Post subject:
Reply with quote

EQA2456IReturning from enclave where Debug Tool was initialized. Handling of non-LE events has been suspended. Debugging of non-LE programs is suspended in this Debug Tool session.
Explanation:
The Language Environment was invoked with TEST/NOPROMPT or NOTEST causing Debug Tool to be initialized during an enclave that was not the top enclave. The enclave in which Debug Tool was initialize is now terminating. Debug Tool will no longer intercept non-Language Environment events and, therefore, you can no longer debug non-Language Environment programs.

Programmer response:
If you do not need to debug higher-level, non-Language Environment programs or to intercept non-Language Environment events, no action is required. Otherwise, re-run the job without NOPROMPT or with the CALL to CEETEST, PLITEST or ctest() in a higher-level enclave.
Back to top
View user's profile Send private message
icetree521

New User


Joined: 04 Apr 2010
Posts: 13
Location: hangzhou, china

PostPosted: Thu Nov 18, 2010 1:11 pm    Post subject:
Reply with quote

To PeterHolland,

"Otherwise, re-run the job without NOPROMPT or with the CALL to CEETEST, PLITEST or ctest() in a higher-level enclave." what does this mean? Does it mean that i should add CALL CEFTEST in my program? icon_razz.gif
Back to top
View user's profile Send private message
PeterHolland

Global Moderator


Joined: 27 Oct 2009
Posts: 2422
Location: Netherlands, Amstelveen

PostPosted: Thu Nov 18, 2010 1:16 pm    Post subject:
Reply with quote

I wouldnt know, try the Debug Tool manual(s) for more info.
Back to top
View user's profile Send private message
View previous topic :: :: View next topic  
Post new topic   Reply to topic    IBMMAINFRAMES.com Support Forums -> IBM Tools All times are GMT + 6 Hours
Page 1 of 1

 

Search our Forum:

Similar Topics
Topic Author Forum Replies Posted
No new posts OO COBOL compile error Virendra Shambharkar COBOL Programming 3 Tue Jan 10, 2017 6:05 pm
No new posts S922 Error yuvan ABENDS & Debugging 3 Fri Dec 02, 2016 6:58 pm
No new posts Invoke Webservice Fails with DFHPI100... divated CICS 2 Thu Nov 24, 2016 5:57 pm
No new posts Error during restore rename archanamuthukrishnan All Other Mainframe Topics 2 Fri Oct 14, 2016 3:30 pm
No new posts Error IEC161I 052(009,XXXRS00)-084 wh... amitc23 JCL & VSAM 10 Wed Oct 12, 2016 5:00 pm


Facebook
Back to Top
 
Mainframe Wiki | Forum Rules | Bookmarks | Subscriptions | FAQ | Tutorials | Contact Us