Earlier, I was explaining how to use TURNOVER Change Management to some RPG Developers who have spent years using Turnover but who had never used the Programmer Worklist Function. I was mildly surprised at the manual technique that was being used to check out each object, adding to a form source member by source member and then asking another RPG Programmer to check the form layout for errors. Invariably the Forms would fail when promoted with a number of different reasons from library list errors to missing related objects (field references, copybooks, etc).
So, I decided to start from the very basics and once this is implemented we can expand from there – this simple overview is looking at the process from a high level (aka helicopter view). If you use Turnover Programmer worklist you will do things quicker. So it has an immediate cost saving for you and your company.
It’s probably old rope to anyone that used Turnover to any degree but here’s my helicopter guide to using this very flexible IBM i Software Change Management Tool.
Important TURNOVER commands from the iSeries command line
Let’s look at how we do a typical checkout, write-code, compile and promote using the Turnover Command Line process
Just remember that each Programmer work list should refer to a PROJECT
Thats it… if #41 works then your ready…
Another useful option is 49 (print form) this could be useful to copy/paste to emails for checking….