Two items I have thought of.
1. In addition to putting a modification tag at the top of the code with who/date/what, we also will assign a job number to the mod in addition to a No for the mod. Such as mod 01. Then throughout the code where the changes are made we put a tag such as *<<01>> start and *<<01>> end or, just a single tag at the end of the line if only one or two lines being changed. This makes the changes very easy to search for and spot should there be problems in the new code. 2. Consider when to use a paragraph and when to use a program. Paragraphs (proc) certainly has their uses, but when the paragraph gets to using IF, Case, locate, etc seems time to use a program. For two reasons. One being while paragraphs (at least in SB+) can do a lot, getting it to do everything a program can do can be difficult. If you have an involved paragraph, sooner or later you'll be adding to it and find you can't easily add what you want to add, that it needs to be a program. Second reason being some of the commands are different syntax in a paragraph vs a program, why learn/memorize or have to look up two different syntaxes? ------- u2-users mailing list [email protected] To unsubscribe please visit http://listserver.u2ug.org/
