On Feb 16, 2006, at 2:51 PM, Chris Mason wrote:
Ed,
When I was last on a long-term consultancy, by example, I tried to
encourage
a crude approach to documenting responsibility - and purpose - in a
common
library by creating a member $$$INDEX. Each line in this member
started with
the name of each member I added - or had been added by someone I
worked with
and I was changing - to be followed by my name and a brief
explanation of
why it was there. (The "$" signs at the beginning of the name
ensured that
the member appeared first in the member list of course.) This was a
technique I used to use simply to keep track of my own work with my
test/education systems since I was very likely to forget work done
years
before. The 8-character member name was never much help as
documentation. I
even had <higher-level-qualifier>.$$$INDEX data sets in which I
listed my
data sets with explanations.
I expect if you made this a rule and devised some code to highlight
any
undocumented member at the end of each day/week, you might have a
management
tool to help keep track of who did what and why especially when the
"who"
was unavoidably detained incommunicado for whatever reason.
Chris,
BTDT but we are talking loadlibs here not text type files. Also the
libraries where I have seen this done are common test load libraries.
I won't *EVEN* go into finding LE modules in a production loadlib.
But you are correct this does work with sysprog libraries, Granted
its hard to get others to go through this scenerio, but it is worth
it. One vendor that I used to maintain their product had literally
100's of members. For that one vendor only we maintained a separate
loadlib pds.
In a well controlled environment it is usually doable. In others
highly doubtful.
Trying to stop a smart programmer is difficult. I wish that the
linkage editor would handle thing a bit differently but (to me) it is
basic MVS flaw and will never be fixed.
Ed
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
