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

In SndMsgQ, if I turn around and do callp SndMsg(MsgInId :MsgInData :MsgInType 
:MsgFile :MsgLib :MsgInQueue), I will encounter the following 2 problems:
1) SndMsg uses CEEDOD (BTW: Reason for opdesc) to determine the actual length 
of MsgInData.  In this case, it will always get a result of 32766 because that 
is what declared in SndMsgQ.
2) If caller only passes the first two required parms, the rest of the parm 
fields may or may not be *null, which could cause problem in SndMsg.





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


Yes, just have SndMsgQ do a 
SndMsg(..... and rearrange the parameters)
Or am I overlooking something?  (I've never used opdesc.)

Rob Berendt