What causes the 'changed outside of turnover' iSeries error message
I'm currently working with IBMi (iSeries) Turnover change management system. It's the best SCM (Software Change Management) application in IBMi land and has a great balance between being easy to use and very powerful.
I know the product fairly well, but it still grins and kicks me in the shins occasionally. This week I've been seeing a lot of "this program has been changed outside of turnover" warning message when checking Turnover Forms to promote code changes. But, when I use DSPOBJD to compare object differences, the only thing different is the last used and the change date. Maybe its a system authority change on the object? Or something deeper and trickier...
The trouble is... what exactly is Turnover checking when it compares the old and new objects?
I've frequently scratched my head over this so it's time to submit the following question to SOFTLANDING SUPPORT
What exactly is the cause of "program has been changed outside of turnover" messages...
Objects (can be anything from a RPG to a *PF) are merely promoted and installed on remote machine... DSPOBJD shows details as the same. Getting this 'changed outside of turnover' error so much the developers are just ignoring it....
What is the exact list of conditions that set this message off?
Now... time to sit back and await the official reply...
Comments
Added by SoftLanding Support
TurnOver maintains internal audit files, which document the last known object and/or source change dates for the objects. At various points, such as checkout or form submission, TurnOver will check the data in these files against the actual object/source change date of the item in question. If a difference is found, we will report a Change Outside of TurnOver.
So, it is really a question of what is causing your objects/source members to show a different change date than the last known change date according to TurnOver. Any number of things can cause the actual source/object change date to change.
The Audit Report (command AUDITRPT) will run a report showing any items which have been changed outside of TurnOver. On the AUDITRPT command, you can specify *ALL applications and libraries, or, a very specific library or object to evaluate. This report will show the TurnOver value, and also the actual value of the source/object change date.Y
This will update the internal TurnOver files with the actual object/source change dates for all objects.
Regards,
Add new comment