Re: Binder language: RTVBNDSRC alphabetically

Yes, as long as you add it at the end, you are ok.  The actual procedure
itself can go any where in the service program, it's only the binder source
that controls the signature.  Btw, if you call RtvBndSrc to add the new
procedure, it will put the new set at the end and realphabetize it and screw
everything up.

----- Original Message -----
From: "Rob Berendt" <rob@dekko.com>
To: <RPG400-L@midrange.com>
Sent: Friday, March 31, 2000 9:31 PM
Subject: RE: Binder language: RTVBNDSRC alphabetically


> Let me rephrase this to see if I have it right.
> My RPG service program source might have the following
> procedures, grouped by function:
> AddDays
> DateEdit
> DayOfWeek
> DayNameL
> DayNameS
> DaysDiff
> CompanyName
> Center40
> ExecCmd
> StrNetSvrP
> CheckPrf
>
> My binder language has:
> STRPGMEXP PGMLVL(*CURRENT) LVLCHK(*YES) SIGNATURE(*GEN)
>   EXPORT SYMBOL("ADDDAYS")
>   EXPORT SYMBOL("CENTER40")
>   EXPORT SYMBOL("CHECKPRF")
>   EXPORT SYMBOL("COMPANYNAME")
>   EXPORT SYMBOL("DATEEDIT")
>   EXPORT SYMBOL("DAYNAMEL")
>   EXPORT SYMBOL("DAYNAMES")
>   EXPORT SYMBOL("DAYOFWEEK")
>   EXPORT SYMBOL("DAYSDIFF")
>   EXPORT SYMBOL("EXECCMD")
>   EXPORT SYMBOL("STRNETSVRP")
> ENDPGMEXP
> STRPGMEXP PGMLVL(*PRV) LVLCHK(*YES) SIGNATURE(*GEN)
>
> Now, let's say I add a procedure.  I could add it anywhere
> in my service program source, in between existing subprocedures
> or whatever.  My new binder language would look like:
> STRPGMEXP PGMLVL(*CURRENT) LVLCHK(*YES) SIGNATURE(*GEN)
>   EXPORT SYMBOL("ADDDAYS")
>   EXPORT SYMBOL("CENTER40")
>   EXPORT SYMBOL("CHECKPRF")
>   EXPORT SYMBOL("COMPANYNAME")
>   EXPORT SYMBOL("DATEEDIT")
>   EXPORT SYMBOL("DAYNAMEL")
>   EXPORT SYMBOL("DAYNAMES")
>   EXPORT SYMBOL("DAYOFWEEK")
>   EXPORT SYMBOL("DAYSDIFF")
>   EXPORT SYMBOL("EXECCMD")
>   EXPORT SYMBOL("STRNETSVRP")
>   EXPORT SYMBOL("RUNCMDAPI")
> ENDPGMEXP
> STRPGMEXP PGMLVL(*PRV) LVLCHK(*YES) SIGNATURE(*GEN)
>   EXPORT SYMBOL("ADDDAYS")
>   EXPORT SYMBOL("CENTER40")
>   EXPORT SYMBOL("CHECKPRF")
>   EXPORT SYMBOL("COMPANYNAME")
>   EXPORT SYMBOL("DATEEDIT")
>   EXPORT SYMBOL("DAYNAMEL")
>   EXPORT SYMBOL("DAYNAMES")
>   EXPORT SYMBOL("DAYOFWEEK")
>   EXPORT SYMBOL("DAYSDIFF")
>   EXPORT SYMBOL("EXECCMD")
>   EXPORT SYMBOL("STRNETSVRP")
> ENDPGMEXP
>
> Is this right?
>
>
>
>
>
>
> Smildenber@Washcorp.com on 03/31/2000 02:44:14 PM
> Please respond to RPG400-L@midrange.com@Internet
> To: RPG400-L@midrange.com@Internet
> cc:
> Fax to:
> Subject: RE: Binder language: RTVBNDSRC alphabetically
>
> Rob,
>
> The binder source does not have to be in the same order as the procedures
> appear in the service program, in fact I prefer them alphabetical.  But,
> when you add new procedures and have a *current and a *prv section do not
> change the order of the procedures as they originally appeared and always
> add the new procedures to the bottom of the list.  If you don't do this
you
> will have to either have to rebind all programs using the service program
> or, worse yet, the programs will run but strange things will occur.
>
> Scott Mildenberger
>
> > -----Original Message-----
> > From: Rob Berendt [SMTP:rob@dekko.com]
> > Sent: Friday, March 31, 2000 10:59 AM
> > To: RPG400-L@midrange.com
> > Subject: Binder language: RTVBNDSRC alphabetically
> >
> > I need to build binder language for my service program.  Reading
> > the redbook I thought I'd try RTVBNDSRC.  However when I run that
> > it retrieves them alphabetically.  I was under the impression that
> > you want these in the order they appear in the service program.
> > What gives?
> > I will be adding some new subprocedures very shortly.
> >
>
> +---
> | This is the RPG/400 Mailing List!
> | To submit a new message, send your mail to RPG400-L@midrange.com.
> | To subscribe to this list send email to RPG400-L-SUB@midrange.com.
> | To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com.
> | Questions should be directed to the list owner/operator:
david@midrange.com
> +---
>

+---
| This is the RPG/400 Mailing List!
| To submit a new message, send your mail to RPG400-L@midrange.com.
| To subscribe to this list send email to RPG400-L-SUB@midrange.com.
| To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---