RE: creating a new procedure that call an existing procedure withone additional parm

Thanks Matt.  
The code in SndMsg is fairly simple and straight forward, I just didn't like 
the idea of duplicate those codes and want to check with everybody in the list 
before I do that.


-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx
[mailto:rpg400-l-bounces@xxxxxxxxxxxx]On Behalf Of Tyler, Matt
Sent: Tuesday, July 26, 2005 11:50 AM
To: 'RPG programming on the AS400 / iSeries'
Subject: RE: creating a new procedure that call an existing procedure
withone additional parm


Lim,

You might use work fields in SndMsgQ to 1) make the message variable length,
based on what is passed, 2) make up defaults to pass to SndMsg, and/or 3)
check for passed parameters and have several calls to SndMsg with different
*OMITS.

I think you are going to need to perform some extra work to make a call to
SndMsg work.  What is in SndMsg that makes it difficult to duplicate the
entire functionality into SndMsgQ?  It's probably just op-desc checking and
a call to the send program message API (right)?

When there is as much work involved in calling another function as there is
in the original function (big assumption here), then it probably needs to
just be duplicated.