How to archive Turnover objects – Change Management for IBM i Series


Apr 11

Steps to remove code from scheduled Releases

Simple steps to archive Turnover objects using Turnover Change Management for IBM i ( and the older iSeries / AS400 machines)


TO – Turnover Menu

archive Turnover objectsOption 9 – Work with Projects and Tasks

Create a Worklist and then Checkout program at top level (presumably your production level)

Option 46 – Add to form (on object library you want to remove objects)

This will create a new form and make sure you add recompiles

Resequence the form . . . . . . . . . . . . . . . . . N 
Check for logical files and add them to the form . . . Y 
Check cross-reference file for related objects . . . . Y 
Check for objects changed by other programmers . . . . N 

F21 – Select all Recompiles

Note – Always select application you are using on – Cross Reference application Selection screen

Now we have a form created and ready to do something to all those checked out objects. We can just go and update the form to DELETE

Option 42 – Edit form

Change each object on form to mark it as a DELETE request (dont worry because Turnover will archive the object to its archive library before it *deletes* the real one)

F7 – Update Top

Change Code to ‘D=Delete’

Repeat for each object on form

Update form and return to work list:

47 – Run Form
Verify the program source/object have been removed from targeted library and objects are checked in from your worklist.

About the Author

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.

%d bloggers like this: