RE: Parameters Stepping on each other

Thanks Tom,

I think we'll be OK, since the last field is a single character, and
will always have a value.  

Another thought was to skip the CL altogether and use QCMDEXC to submit
the job from the RPG service program that normally calls the CL.  I
wasn't sure if that might not have the same problem as the CL.  I'll
probably test that when I get a spare moment.  

Greg

|-----Original Message-----
|From: rpg400-l-bounces@xxxxxxxxxxxx
[mailto:rpg400-l-bounces@xxxxxxxxxxxx]
|On Behalf Of qsrvbas@xxxxxxxxxxxx
|Sent: Monday, June 26, 2006 7:13 PM
|To: rpg400-l@xxxxxxxxxxxx
|Subject: RE: Parameters Stepping on each other
|
|rpg400-l-request@xxxxxxxxxxxx wrote:
|
|>   4. RE: Parameters Stepping on each other (Fleming, Greg (ED))
|>
|>And thanks to all who responded, as well.  Since, in this case, the CL
|>program is being called from another RPG procedure, I think we'll just
|>put the parms in a datastructure and pass it through the CL to the
final
|>RPG program.  I think that should avoid the problem...
|
|Greg:
|
|Be aware that, if you continue to use the CMD() parm, this will still
|exhibit the same problem although it will be isolated to trailing
blanks
|for the structure itself rather than trailing blanks for individual
*CHAR
|parms.
|
|If the last field in the struct _never_ has trailing blanks, all will
be
|fine. But...
|
|Tom Liotta
|
|--