×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
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
From:
David FOXWELL <David.FOXWELL@xxxxxxxxx>
To:
RPG programming on the AS400 / iSeries <rpg400-l@xxxxxxxxxxxx>
Date:
05/23/2008 09:22 AM
Subject:
Help with my first SRVPGM
I've just created my first SRVPGM. As I had to create a new file, I wrote
a module to manage all the operations on that file and created a SRVPGM
SP1 on that module.
Like this CRTSRVPGM P1 BNDSRVPGM(SRVPGMREF) where SRVPGMREF has error
handling functions.
Now, I have another module M2 that uses this SP1.
A programe P1 has to call functions in M2.
I wanted to create SP2, a SRVPGM with M2. How should I be doing this ?
At the moment I did CRTSRVPGM P2 BNDSRVPGM(SRVPGMREF CLTFSC)
That way I add to the list of service programs each time. I don't know how
to automate this process.
As up till now we never used service programs, all the modules just got
thrown in to huge BNDDIRs and then the same compile command could be used
for all the programs :
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.