Re: MIDRANGE-L Digest, Vol 3, Issue 1098

[jlowary@xxxxxxxxxxxxx]

Did find some examples of sending messages to get who the caller is, but 
looks like on *SRVPGM's they are not included in the Call Stack cause you 
get back the following.  (Even compile the CL program to activation group 
*caller  as it was in *DFTACTGRP by default, and got same results)

Message ID . . . . . . :   CPF2479  
Date sent  . . . . . . :   07/28/04      Time sent  . . . . . . : 08:23:43 
 
  
Message . . . . :   Call stack entry not found.  
  
Cause . . . . . :   Call stack entry TOZZ001SP0, specified for the send, 
receive, move or delete message operation, could not be found in the call 
stack.  
Recovery  . . . :   Change the call stack entry name or be sure the 
specified entry is in the call stack when doing the requested operation.   



So maybe my best bet is to just pass a parm after all. Thanks for the 
help!

-- Jim 
  



midrange-l-request@xxxxxxxxxxxx 
Sent by: midrange-l-bounces@xxxxxxxxxxxx
07/27/2004 10:47 AM
Please respond to
midrange-l@xxxxxxxxxxxx


To
midrange-l@xxxxxxxxxxxx
cc

Subject
MIDRANGE-L Digest, Vol 3, Issue 1098







------------------------------

message: 5
date: Tue, 27 Jul 2004 11:08:25 -0400
from: CWilt@xxxxxxxxxxxx
subject: RE: Procedures in Service Program

You could make use of the same trick trigger programs do to see who caused
the trigger to be fired.

Send a message back up the call stack and then receive it.

Should find plenty of examples in the archive.

HTH,
Charles


> -----Original Message-----
> From: jlowary@xxxxxxxxxxxxx [mailto:jlowary@xxxxxxxxxxxxx]
> Sent: Tuesday, July 27, 2004 10:52 AM
> To: midrange-l@xxxxxxxxxxxx
> Subject: Procedures in Service Program
> 
> 
> When you call a procedure in a service program, does that 
> procedure have 
> anyway of knowing who called it?  (Other than passing it a 
> parm to tell 
> it)
> 
> Thanks,
> 
> -- Jim Lowary
> ToastMaster/Salton, Inc.
> --