Wow – that’s another long url title. I really wanted to call this “How To Check Out An Object From One Library And Promote It To A Different Library but keep the program source code line change dates” but that just seemed to ridiculously long.
Why are we talking about this?
We all know there are several ways to copy a source member from one file to another but did you know that HOW you execute the copy can make a BIG difference?
The technique used to copy a source member can cause a complete reset of all the source line change dates. In theory, all source modifications are supposed to be documented in the code itself but everyone knows it doesn’t always happen. When there aren’t adequate mod markings we rely on those line dates to help decipher what changes have taken place in the source code and when. In some source members, losing those dates is disastrous. Here is an example:
The WRONG way:
UHOH – so allthough this works we lose all our line change dates. hashtag thats not good.
The RIGHT way:
Bobs yer Uncle and Fanny’s yer Aunt.
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.
Turnover Tip – Checkout to new library retaining source line changes dates
“Turnover Change Management” Graphical Editor Error Message
Copying iSeries fields from numeric to Alpha – aka using SQL to change column data type
Softlanding Turnover Scribbled Notes, User Guide and Programmer Reference
Using EXTPRC with iSeries Turnover at V5R4
How to change all lines on turnover form to add, delete or replace