|
>> What should be a service program vs a bound module etc etc etc. Simple rule of thumb. If the procedure has a one-to-one relationship with its caller then keep it as a module and bind by copy. If the procedure has a one-to-many relationship with its callers (as is your case) then put it in a service program and bind by reference. >> I would like to have a compile option in PDM so that programmers can automatically use these functions. First thing to do is to create a Binding Directory and record the name of your service program(s) there. Now you can either tell the programmers to always reference the binding directory or create a PDM option (mine is called MC - My Compile) that does a CRTBNDRPG which specifies DFTACTGRP(*NO) and references the binding directory and includes debug preferences etc. If you are on V4R2 or later you also have the option of embedding the DFTACTGRP and binding directory references in the H spec for the program. I suggest starting each program with a /COPY StdHSpec that spells this out. This way if the programmers take PDM option 14 it will still work OK. +--- | 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 +---
As an Amazon Associate we earn from qualifying purchases.
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.