MVSFORUMS.com

[stansaraczewski]

We periodically will have one programmer overlay work done by another because no CMF system (such as Panvalet) exists in the shop.

Does anyone have any suggestions on how to deal with this ?

The management is hesitant on spending the money for a commerical solution.

[semigeezer]

You already have a source code management system. SCLM comes with ISPF and it can do your builds (precompiles, compiles, links, etc) for you as well. It includes the generation of a simple set of definitions to define your setup which you can then modify. Setup isn't completely intuitive (what SCM setup is?) so you will need to read the manuals, but it is well worth the time.

SCLM (which again, you already have) can also provide versioning, auditing, the ability to make emergency fixes, exits for special needs (like tying into a change control system, notifications, approvals,etc), a programmable API and much more. It also keeps your load modules all other outputs in sync with your source and other inputs so you know the modules you run match the code you saved. You can use it as just a simple library manager (lock/unlock/promote) if you want by just defining everything (source, etc) as text, but you lose 99% of the functionality by doing that; but if lock/unlock is all you need, you can probably get set up and copy your code into it in a couple of days, and while you need to get programmers to use option 10.2 instead of option 2, for example, training is pretty trivial and the system is very easy to use for basic programmer functions. Actually, the only thing that is somewhat difficult to do (in my opinion) is set up compilers (called translators in SCLM).

Now... even if you choose not to go with an SCM like SCLM for whatever reason, make sure your programmers are intimately familiar with two ISPF editor commands: the COMPARE (or COMP) primary command (and X operand) and the Make Data (MD) line command. Those together provide a powerful, simple and visually pleasing method of comparing their changes with the version they are going to overlay. And if someone does updates in VIEW mode and just does a REPLACE (without the appropriate ENQ and compare), take 'em out behind the woodshed and give 'em what for. (the implication, if not clear, is that they should edit the TARGET data set to establish an ENQ and then manually merge their changes into that using COMPARE and MD. It is by no means fool proof but it is better than nothing, I guess).
_________________
New members are encouraged to read the How To Ask Questions The Smart Way FAQ at http://www.catb.org/~esr/faqs/smart-questions.html.

[stansaraczewski]

Thanks for that idea, semigeezer.

I need to do a bit of reading now to determine if this method allows 'voluntary participation' - if so it won't work.

It needs to be similar to Panvalet - where you don't touch the source code without 'owning' it by checking it out and no one else can touch it when you 'own' it.

I do see SCLM on my primary ISPF menu. Right under my nose.

[semigeezer]

It can be set up so that you can't edit the members fro option 2, only 10.2 (SCLM) and it does have locking. That is you check out a member, save it, build it (which can do a real build or nothing at all) and promote it (check in).

It works best, however if each user has a set of development libraries because the lock is to the library, not the user. There have been some changes to locking to add some type of user level locking in addition to library level locking, but I haven't kept up with that so I can't speak to it.
_________________
New members are encouraged to read the How To Ask Questions The Smart Way FAQ at http://www.catb.org/~esr/faqs/smart-questions.html.

[stansaraczewski]

Thanks again for your comments. I need to find out now why it hasn't been used here before.