[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference clt::rtl

Title:OpenVMS Run-Time Libraries
Notice:Routines documented in the Run-Time Library volumes covered here
Moderator:LOWFAT::DIETER
Created:Sat Jan 25 1986
Last Modified:Wed May 28 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:966
Total number of notes:4598

963.0. "CLI$DISPATCH => %DEBUS-I-INHCHME - why?" by JURA::JURA::DUQUESNE (Daniel - Publicit� interdite...) Tue Mar 11 1997 11:54

The following message status "%DEBUG-W-INHCHME" is given back by CLI$DISPATCH.
I'd like to know how to suppress such message...and where does it come from?

The routine activated by CLI$DISPATCH has been debugged and works as expected.

Thx for the help,
Daniel.

           <<< TURRIS::DISK$NOTES_PACK:[NOTES$LIBRARY]DEBUG.NOTE;4 >>>
                                   -< DEBUG >-
================================================================================
Note 1844.0                     %DEBUG-W-INHCHME                      No replies
JURA::DUQUESNE "Daniel - Publicit� interdite..."     14 lines  11-MAR-1997 10:37
--------------------------------------------------------------------------------
Hi,

I have a program which generates the following msg only on OVMS Alpha: same 
program doesn't display the msg on VAX. I'd like to remove this msg on Alpha.  
Which system service is currently inhibited: how can I know?

%DEBUG-I-EXITSTATUS, is '%DEBUG-W-INHCHME, inhibited CHMExecutive trap, 
code=00000000, PC=00000000, PS=000F0003'

OVMS/Alpha V6.2.


Thanks for the help,
Daniel.
T.RTitleUserPersonal
Name
DateLines
963.1QUARK::LIONELFree advice is worth every centTue Mar 11 1997 12:364
This is not an "RTL" issue, since the CLI$ routines are considered OpenVMS
"utility" routines.  Ask in VAXAXP::VMSNOTES.

				Steve
963.2What did you try to return?WIBBIN::NOYCEPulling weeds, pickin&#039; stonesTue Mar 11 1997 16:123
My guess is that the routine called by CLI$DISPATCH neglects
to return any value.  When it returns, R0 happens to contain 0x204D0,
which gets symbolized as this nonsensical condition.