If you are designing the best setup for your Software Change Management system (specifically TURNOVER V100 for iSeries) these notes might help.
We have four main user groups:
We need to clean the IBM I authorities so they correctly let these group members *USE , *CHANGE or *ADMIN different parts of the machines. Remove *ALLOBJ or *SECOFR from all developers on all machines. Correctly create group profiles for these roles and have the members part of those groups.
Within Turnover we have these functional areas:
We need to correctly define the TURNOVER definitions for these groups something like this:
Change Administrator – these are the *SECOFR of the turnover world. A rare beast and something the developers should never have access to. Can create/delete everything.
Development Team – these need rights to *USE Projects, *CHANGE tasks and create/run DEV/TST/QA forms
Software Solution Analysts – *USE rights to investigate and look at everything. Possibly rights to create/assign tasks to developers? No rights to create distribution forms or change code.
QA Team – only have rights to read data files and perhaps look at object history. It’s likely that SANDS QA users will not use turnover.
The programmers that are defined to Turnover should be setup so that they can only see the applications that they are working on.
IBM i Software Developer, Digital Dad, AS400 Anarchist, RPG Modernizer, Alpha Nerd and Passionate Eater of Cheese and Biscuits. Nick Litten Dot Com is a mixture of blog posts that can be sometimes serious, frequently playful and probably down-right pointless all in the space of a day. Enjoy your stay, feel free to comment and in the words of the most interesting man in the world: Stay thirsty my friend.
Softlanding iSeries Turnover Consultant – will change-manage for food
Turnover V100 Documentation for IBM i, iSeries and older AS400 machines
Display Object Authority on IBM i , iSeries and old AS400
What is the best change management tool for IBM i?
What is IBM i Email and SPF?
Updating Numeric DTAARA in RPGLE
How to capture IBM-i job info for submitted jobs
Going the (Levenshtein) Distance in RPG Free
Don’t hardcode library names in your TURNOVER SQL source #youbigsilly