Re: Help with my first SRVPGM

I gotta agree with Tommy's thoughts here on the binding directories.

Whenever I make a service program I have 3 source members involved.

The Procedures source member (or 'functions' source member if you like
that)
Name=SRVPGM_F

The Prototypes source member
Name=SRVPGM_P

The Exports (binder) source member.
Name=SRVPGM_X

Then I create the module against the SRVPGM_F member.
CRTRPGMOD

Then create the service program against the above module.
CRTSRVPGM

Then add an entry to the binding directory for that service program.

Voila it's available to be user by RPG XYZ program simply by
/copy(ing) the prototype source member, SRVPGM_P, in XYZ and
Indicating the binding directory in the compile whether in an H
Spec or on the command.

** We keep all the members in QSRVSRC so it is necessary to indicate
The Exports source member, SRVPGM_X, in the CRTSRVPGM command.

Hth

John B.




message: 5
date: Fri, 23 May 2008 09:28:34 -0500
from: Tommy.Holden@xxxxxxxxxxxxxxxxxxxxx
subject: Re: Help with my first SRVPGM

use binding directories for your service programs...it makes maintenance

so much easier. add the service programs to the binding directory and
in
your programs just put BNDDIR('MYBNDDIR') on your H spec then you don't
have to use BNDSRVPGM, etc on the compile..the compiler will use the
binding directory to find and resolve to the service programs and it's
procedures.

personally i discourage the use of binding directories for modules...but

then again i don't keep modules hanging around. i use them to compile
then nuke 'em.

Thanks,
Tommy Holden