[Search for users]
[Overall Top Noters]
[List of all Conferences]
[Download this site]
| Title: |  | 
|  | 
| Moderator: | IRNBRU::MACKENZIE | 
|  | 
| Created: | Wed Jul 10 1991 | 
| Last Modified: | Tue May 06 1997 | 
| Last Successful Update: | Fri Jun 06 1997 | 
| Number of topics: | 289 | 
| Total number of notes: | 1527 | 
288.0. "IMS-E-NOREQUEST error?" by IRNBRU::JWESTERMAN (Jeremy Westerman, MSG+ Middleware, Ayr.) Wed Apr 16 1997 10:11
Tultex came across the following.
Does this mean that the request handle being used to read from sl_get_req_elt
does not exist, ie he hasn't done a sl_read_req?
Jeremy.
From:	VBORMC::"[email protected]" "Jay Larson"  8-APR-1997 15:06:26.48
To:	Jeremy Westerman <[email protected]>
CC:	
Subj:	DMQ log message & IMS message
Jeremy,
Hope you had a good trip/flight back home. Here is the DMQ log 
message I told you about. Also, we came accross a bogus IMS 
message that needs some clarification.
DMQ Log Message:
************ dmqld (3446) 26-MAR-1997 08:43:59 ************
ipi, semaphore operation failed
************ dmqld (3446) 26-MAR-1997 08:43:59 ************
ld, initialization failure
************ dmqld (3446) 26-MAR-1997 08:43:59 ************
spi, not attached to object
************ dmqld (3446) 26-MAR-1997 08:43:59 ************
ld, caught signal 11
************ dmqld (3446) 26-MAR-1997 08:43:59 ************
ld, link receiver for group 30 from group 38 is exiting
IMS Message:
sl_get_req_elt() failure: 136020018 -
%IMS-E-NOREQUEST, the requested passed was not found
Thanks,
Jay Larson
| T.R | Title | User | Personal Name
 | Date | Lines | 
|---|
| 288.1 | is .0 One or Two problems? | BEAVER::MCKEATING |  | Wed Apr 16 1997 11:40 | 18 | 
|  | Focusing on the MSG+ part of .0 we see:-
IMS Message:
sl_get_req_elt() failure: 136020018 -
%IMS-E-NOREQUEST, the requested passed was not found
This means that the handle passed to the sl_get_req_elt call is not 
valid.
This is most likely as a result of bad program logic. Most common
causes are:-
1.not called sl_read_req yet so there is no handle in the variable.
2.sl_finish_req already called so request has been cleared.
3.handles passed to subroutines incorrectly see 287.0
hope this helps,
Bob
 |