RE: Service Programs

The "signature" of a Service program indicates it's list of exported
modules.  That's what's so cool about BND Source... you can support multiple
signatures for the same Service Program so that if you add a new module you
only need to compile programs requiring the new module...

The USERSERV service program has the following signature... (from it's BND
source)

STRPGMEXP PGMLVL(*CURRENT)
  EXPORT SYMBOL("#CHKUSER")
  EXPORT SYMBOL("#GETUSER")
ENDPGMEXP

It is currently bound (through a binding directory) to program A, B, and C.
I need to add a new module, #DELUSER to this service program so that program
D can delete users.  I create the new Module and change the BND Source to
this...

STRPGMEXP PGMLVL(*CURRENT)
  EXPORT SYMBOL("#CHKUSER")
  EXPORT SYMBOL("#GETUSER")
  EXPORT SYMBOL("#DELUSER")
ENDPGMEXP

STRPGMEXP PGMLVL(*PRV)
  EXPORT SYMBOL("#CHKUSER")
  EXPORT SYMBOL("#GETUSER")
ENDPGMEXP


Now I UPDSRVPGM for USERSERV and add #DELUSER.  My service program now has
multiple "Signatures", one includes #DELUSER as an exported module and one
does not.  I can have *PRV signatures ad infinitum.

Best of all, I only need to compile and create program D in order to use the
new "signature": I can leave programs A, B, and C alone.


Joel R. Cochran
Director of Internet Services
VamaNet.com
(800)480-8810
mailto:webmaster@vamanet.com


> -----Original Message-----
> From: dmosley@dancik.com [mailto:dmosley@dancik.com]
> Sent: Friday, April 19, 2002 11:21 AM
> To: rpg400-l@midrange.com
> Subject: Re: Service Programs
>
>
>
> I found this defintion on the web.
> "When creating a service program, the system calculates a
> 'signature' for
> your service program. This works in a similar manner to the
> way 'record
> format level checks' work on a database file -- if something
> in the service
> program changes, they prevent you from possibly accessing it
> incorrectly."
>
> To be more specific, if something changes in any of the procedures
> parameters, this would cause a Signature Violation.
>
>
> David L. Mosley, Jr.
> Systems Analyst
> 2000 CentreGreen Way
> Suite 250
> Cary, NC 27513
>
>
>
>                     Justin Houchin
>                     <jhouchin9@charte        To:
> rpg400-l@midrange.com
>                     r.net>                   cc:
>                     Sent by:                 Subject:     Re:
> Service Programs
>                     rpg400-l-admin@mi
>                     drange.com
>
>
>                     04/19/02 11:04 AM
>                     Please respond to
>                     rpg400-l
>
>
>
>
>
>
> So let me get this straight, with a service program, I can
> change the its
> module and I do not have to recompile the program? And what
> do you mean by
> "signature"?
>
>
> Justin Houchin
> ----- Original Message -----
> From: <dmosley@dancik.com>
> To: <rpg400-l@midrange.com>
> Sent: Friday, April 19, 2002 9:59 AM
> Subject: Re: Service Programs
>
>
> >
> > For one, if the module changes, then the Program itself has to be
> > re-compiled.  If the module/service program changes, no big
> deal. (As
> long
> > as the signature doesn't change)
> >
> > David L. Mosley, Jr.
> > Systems Analyst
> > 2000 CentreGreen Way
> > Suite 250
> > Cary, NC 27513
> >
> >
> >
> >                     Justin Houchin
> >                     <jhouchin9@charte        To:     RPG Midrange
> <rpg400-l@midrange.com>
> >                     r.net>                   cc:
> >                     Sent by:                 Subject:     Service
> Programs
> >                     rpg400-l-admin@mi
> >                     drange.com
> >
> >
> >                     04/19/02 10:50 AM
> >                     Please respond to
> >                     rpg400-l
> >
> >
> >
> >
> >
> >
> > This is a multi-part message in MIME format.
> > --
> > [ Picked text/plain from multipart/alternative ]
> > Hi Everyone,
> >     What is the advantage of creating a service program out
> of a module
> > than just binding that module to create the program?
> >
> >
> > Justin Houchin
> > Programmer
> > Reliatek, Inc
> > _______________________________________________
> > This is the RPG programming on the AS400 / iSeries
> (RPG400-L) mailing
> list
> > To post a message email: RPG400-L@midrange.com
> > To subscribe, unsubscribe, or change list options,
> > visit: http://lists.midrange.com/cgi-bin/listinfo/rpg400-l
> > or email: RPG400-L-request@midrange.com
> > 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@midrange.com
> > To subscribe, unsubscribe, or change list options,
> > visit: http://lists.midrange.com/cgi-bin/listinfo/rpg400-l
> > or email: RPG400-L-request@midrange.com
> > 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@midrange.com
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/cgi-bin/listinfo/rpg400-l
> or email: RPG400-L-request@midrange.com
> 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@midrange.com
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/cgi-bin/listinfo/rpg400-l
> or email: RPG400-L-request@midrange.com
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/rpg400-l.
>