tag:blogger.com,1999:blog-18371456.post3442314629788541500..comments2024-03-26T00:07:20.400-05:00Comments on The Db2 Portal Blog: Cost vs. Advantage of Moving From IMS DB to DB2Craig S. Mullinshttp://www.blogger.com/profile/17077237739217901780noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-18371456.post-45975549086156408772009-03-27T13:08:00.000-05:002009-03-27T13:08:00.000-05:00Thanks for that war story, Troy. It is amazing the...Thanks for that war story, Troy. It is amazing the lengths that organizations will go to in order to avoid conversion. The case you describe is, indeed, one where it is time to "bite the bullet" and convert... or maybe, instead of cobbling together a solution requiring DB2 for some "fields" they should have hired an IMS consultant to extend the segment length to include more room (for the ZIP code and a healthy amount of filler)...Craig S. Mullinshttps://www.blogger.com/profile/17077237739217901780noreply@blogger.comtag:blogger.com,1999:blog-18371456.post-33122429736637326112009-03-27T12:54:00.000-05:002009-03-27T12:54:00.000-05:00I like the way you put this. The one subject you ...I like the way you put this. The one subject you didn't touch on is on going development. I worked at a place that stopped all changes to IMS data structures and required all enhancements to the system in DB2. When they ran out of filler in the IMS segment they had to create a DB2 table to hold any new columns. I remember when they didn't have the zip code on a customer segment for some reason. They had no filler left so they had to create a DB2 table to old this information. Now this existing IMS only transaction had to call DB2 for the zip code. If you are in this situation, at some point you have to make the move and rewrite the application I think, or it will just keep costing you more and more to maintain. It's more complex and error prone and in fact over time you are updating the same data in IMS and DB2 to keep systems synchronized.troycolemanhttps://www.blogger.com/profile/10589139698593456037noreply@blogger.com