In the past, we have documented at the top of the program the date, ticket
# and a description of a change. Now we are being told to put the ticket
number in the first 5 positions, copy the line we are changing, commenting
out the original line and editing the new. In CLP, /* */ to enclose the
ticket number on the line being changed.
But I cannot get anyone to explain how long this remains in the code. I
don't have a problem with commenting out and entering new lines, but when I
go in to maintain the program next, I generally want to clean up (delete)
the unused lines of code to make for better readability. When making large
changes, I also make backup copies of the source member just in case I have
to go backwards.
Can anyone point me to a best practices for documenting code changes ?
This would have to cover RPG IV and Free and CL programs. We are working
towards a SOC 2 Type 1 compliance.
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
This mailing list archive is Copyright 1997-2013 by MIDRANGE dot 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 here. If you have questions about this, please contact