Re: Calling RPGLE module.

Those RNF7031's aren't the problem; those are informational messages. Check
the associated job log (not the compile listing) - you may find more
information there.

On 4/7/06, Jake M <jakeroc@xxxxxxxxx> wrote:
>
> Pro's,
> Thanks a bunch for the input. It still does not compile. I do not know
> what
> I am doing wrong here....I am using CRTBNDRPG.
>
> RNS9301 Program CALLCTST in library MYLIB not created.
> RNF7031 The name or indicator POSPLIT is not referenced.
> RNF7031 The name or indicator BWIEDIDNB is not referenced.
> RNF7031 The name or indicator CHAINSTORE is not referenced.
> RNF7031 The name or indicator CTYSTJST@ is not referenced.
> RNF7031 The name or indicator EDICUSTPO is not referenced.
>
> CALLCTST:
>
> ********************************************************************************************************
>       /COPY QPROTOSRC,EDITOOLTST
>       *
>      D  CSTZIP         S             70
>      D  CITY           S             35
>      D  STE            S              2
>      D  ZIP            S              9
>      D  ERR            S              1
>      D  pass           S              1
>      D   RESULT        S            118
>
>       *
>       *
>       *
>       /FREE
>          CSTZIP = 'SCHULENBURG, TX';
>          RESULT = CTSTJSTTST(CSTZIP:CITY:STE:ZIP:pass:err);
>        *inlr = *on;
>       /END-FREE
>
> ************************************************************************************************************
> I appreciate all the help.
>
> Jake.
>
> On 4/6/06, Scott Klement <rpg400-l@xxxxxxxxxxxxxxxx> wrote:
> >
> > > I am trying to call a module which was coded by somebody else. I think
> I
> > am
> > > calling it wrongly. Would y'all mind taking a look at this please and
> > guide
> > > me in the right direction? I am learning RPG so I am not be
> > understanding
> > > the module correctly.
> >
> > The CTSTJSTTST procedure is written incorrectly.  It doesn't matter for
> > your particular example, since you're passing a 70A field for CSTZIP,
> but
> > if you ever pass something shorter than 70 characters, you run the risk
> of
> > getting garbage in the parameter, since the programmer who wrote this
> code
> > clearly didn't understand how options(*VARSIZE) works.
> >
> > OPDESC was also supplied, but the operational descriptor doesn't appear
> to
> > be used anywhere in the code.  Seems a little odd.
> >
> > However, with the way you're using it (passing a full 70A field) it
> works
> > okay.  I tried compiling and running your example and it worked for me.
> > Can you please tell us what problem you were having?
> > --
> > This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing
> list
> > To post a message email: RPG400-L@xxxxxxxxxxxx
> > To subscribe, unsubscribe, or change list options,
> > visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
> > or email: RPG400-L-request@xxxxxxxxxxxx
> > Before posting, please take a moment to review the archives
> > at http://archive.midrange.com/rpg400-l.
> >
> >
> --
> This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing list
> To post a message email: RPG400-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
> or email: RPG400-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/rpg400-l.
>
>