Re: Survey of RDi users related to Source Code management

Okay. Simple approach:

Create two commands, check out and check in, with parameters to pass in the project number, source file/library, and member. They can't have any interactive screens. Set them up as user actions in RSE (very similar to, but more powerful than, user options in PDM).

If you want to protect yourself from someone accidentally changing your production source, set the programmers' authority to it to read only. RDi will only allow browse mode to anyone who doesn't have change authority. If you do this, you'll have to ensure that your check in command can get authority to update the production source (program adopted authority, submitting a job under another profile, or whatever approach floats your boat). Secured production source is the norm for companies that use any form of change control, since otherwise it's much too easy to cheat.

If you want to play with plugins, you could make it a lot fancier, but this is all you really need to be compatible with what you're doing now.

Dave Shaw
Mohawk Industries

----- Original Message ----- From: "Mike Cunningham" <mike.cunningham@xxxxxxx>
To: "Websphere Development Studio Client for iSeries" <wdsci-l@xxxxxxxxxxxx>
Sent: Wednesday, May 20, 2009 10:10 PM
Subject: Re: [WDSCI-L] Survey of RDi users related to Source Code management

The details are...
We made a copy of STRPDM and changed the program the command calls and the first thing you see is a screen from our app asking if you want to check out the source or just look at it. If you want to change it you have to enter what you plan on doing (aka project number) and then our app makes a backup copy of the current source just by doing a CPYF (we keep 9 previous versions) to a different QRPGSRC file. Who has it checked out is then recorded in a database. If someone else tries to open the source they are told that the code is checked out and by whom and for what reason. When the programmer checks the source back in it is implemented.