CNC, DB and Operating System - JDE1 (MOSC)

MOSC Banner

call object kernel (THDW) status

edited Aug 9, 2017 5:00AM in CNC, DB and Operating System - JDE1 (MOSC) 3 commentsAnswered

Hello,

We have enterprise server on ISERIES, usually when call object kernel ended another kernel started instead automatically. but sometimes one of the call object kernel stuck in THDW status, is it okay to stop this job or there are related jobs to this hanged call object kernel and may affect other users??? as appear in the image there is no users connected to hanged call object kernel.

last part of the kernel log appear in ISERIES:

The ILE C heap control structure has been corrupted.                    

Maximum number of records reached for file QPRINT. (C R NOMAX 1-999999) 

NOMAX                                                                   

Signal SIGABRT raised (abnormal termination).                           

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

Don't have a My Oracle Support Community account? Click here to get started.

Category Leaderboard

Top contributors this month

E1 CNC/DBOS Tags

Instructions for posting

×

1. Select a discussion category from the picklist.


2. Enter a title that clearly identifies the subject of your question.


3. In the body, insert detailed information, including Oracle product and version.


Please abide by the Oracle Community guidelines and refrain from posting any customer or personally identifiable information (PI/CI).


Cloud / Fusion customers - Our Cloud community has moved! Please go to Cloud Customer Connect .


New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center