Re: Calling Command with Parameters

["Peter Dow (ML)" <maillist@xxxxxxxxxxxxxxx>]

Hi Michael,

What does your command definition look like?  When you define a list, 
the 1st two bytes of the list returned to the program will be a binary 
number indicating how many elements of the list were filled in by the 
user and passed to the cpp.  You should only be processing that number 
of list elements; any storage beyond those is undefined.

*Peter Dow* /
Dow Software Services, Inc.
909 793-9050
pdow@xxxxxxxxxxxxxxx <mailto:pdow@xxxxxxxxxxxxxxx> /

Michael Ryan wrote:
> Yup...that's what I'm doing, but I'm having a problem when it's a list
> parameter. The single parameters look fine. It's like when I do this:
>
> SAVRSTOBJ OBJ(OBJ1 OBJ2)
>           LIB(SOMELIB)
>           RMTLOCNAME(SOMEREMOTE)
>
> The OBJ parameter (which can have multiple values) seems to have junk in the
> unused positions in the list. The LIB and RMTLOCNAME, being single values,
> don't seem to have the same problem.
>
>
> On 10/20/06, Richard ECUYER <recuyer@xxxxxxx> wrote:
>   
> > Not sure if this is really what you are looking for but usually, specify
> > the
> > parmnam and it's value like this  :
> > WRKOUTQ OUTQ(MYVALUE) ... OUTQ is the parm name, MYVALUE is the parm
> > value...
> >
> >
> > ----- Original Message -----
> > From: "Michael Ryan" <michaelrtr@xxxxxxxxx>
> > To: "Midrange Systems Technical Discussion" <MIDRANGE-l@xxxxxxxxxxxx>
> > Sent: Friday, October 20, 2006 5:42 PM
> > Subject: Calling Command with Parameters
> >
> >
> >     
> > > I'm constructing a command in an RPG program. I'm getting junk in the
> > > command processing program's entry paramters for multiple element
> > >       
> > command
> >     
> > > parms. It reminds me of the 32 byte CL program problem - in fact, that's
> > >       
> > why
> >     
> > > I front-ended the CPP with a command. So, my question is - if I have a
> > > command that takes a list for a parameter, how do I construct the
> > >       
> > command?
> >     
> > > Thanks...
> > > --
> > > This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
> > >       
> > list
> >     
> > > To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> > > To subscribe, unsubscribe, or change list options,
> > > visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> > > or email: MIDRANGE-L-request@xxxxxxxxxxxx
> > > Before posting, please take a moment to review the archives
> > > at http://archive.midrange.com/midrange-l.
> > >
> > >
> > >       
> > --
> > This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
> > list
> > To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> > To subscribe, unsubscribe, or change list options,
> > visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> > or email: MIDRANGE-L-request@xxxxxxxxxxxx
> > Before posting, please take a moment to review the archives
> > at http://archive.midrange.com/midrange-l.
> >
> >
> >