On 08/08/2008, at 5:45 PM, David FOXWELL wrote:
More questions concerning yesterday's posts.
We actually have one BNDDIR per PGM with the same name as that PGM.
The BNDDIR is used on the CRTPGM command. Is there a difference to
coding it in the H specs?
No, just easier and less likely to be forgotten on the H-spec.
As there are no SRVPGM yet chez nous, each BNDDIR contains modules
specific to the program and all the modules that SHOULD be in ALL
the service programs. Ugh! Sometimes I think we'd be just as well
off with one BNDDIR for ALL programs!
Given that you are binding by copy one giant *BNDDIR with all the
modules would work fine--but it won't correct the fundamental problem
of a given module being used by multiple programs.
Who thought that idea was intelligent? Find them and slap them!
The only reason I can think of for doing this would be to use *BNDDIR
as a documentation aid---a sort of poor-man's "Where Used" facility.
However that's just dumb on OS/400. Each object knows what it uses
thus DSPPGM provides a list of the modules and service programs
actually used.
Now, in putting ALL service programs in one BNDDIR, are you
suggesting ALL SRVPGMs of ALL programs, ie one BNDDIR for SRVPGMs ?
Yes. That way new service programs can be added in one place and will
be found as soon as a program references a function contained in any
service program. Much easier than having to add used service programs
to the *PGM-specific *BNDDIR.
What is a change management system exactly?
Now THAT'S a stupid question. How can a programmer/developer/IT
person NOT know about change management systems? A STFW would have
told you the answer.
A CMS (in this context) is a tool that manages the development cycle--
things like ensuring only one developer can change a given source
module at one time (check-out and check-in), ensuring objects are
built correctly (build scripts), provides "where used" information,
helps determine WHAT objects must be changed if a field or file is
altered, may even manage dev, test, and prod environments and the
code promotion associated with same, plus a bunch of other stuff.
I expect the various CMS vendors to leap in here with references to
their specific solution. ALl I'll say on the subject is that ALL
serious development should use some form of CMS (even if it's home-
grown) and even if you work in a one-man shop.
Regards,
Simon Coulter.
--------------------------------------------------------------------
FlyByNight Software OS/400, i5/OS Technical Specialists
http://www.flybynight.com.au/
Phone: +61 2 6657 8251 Mobile: +61 0411 091 400 /"\
Fax: +61 2 6657 8251 \ /
X
ASCII Ribbon campaign against HTML E-Mail / \
--------------------------------------------------------------------
midrange.com
