{"id":52550,"date":"2021-10-01T16:05:28","date_gmt":"2021-10-01T14:05:28","guid":{"rendered":"https:\/\/www.arcadsoftware.com\/?p=52550"},"modified":"2022-12-09T11:49:43","modified_gmt":"2022-12-09T09:49:43","slug":"expanding-a-field-on-ibm-i-complete-the-job-in-a-quarter-of-time","status":"publish","type":"post","link":"https:\/\/www.arcadsoftware.com\/arcad\/news-events\/on-demand-webinars\/expanding-a-field-on-ibm-i-complete-the-job-in-a-quarter-of-time\/","title":{"rendered":"Expanding a field on IBM i? Complete the job in a quarter the time!"},"content":{"rendered":"

[Webinar] Expanding a field on IBM i?<\/span> Complete the job in a quarter of time!<\/span><\/strong><\/h1><\/div>

Ever tried expanding the size of a field or entity in your IBM i application? The impact across database and source code can be massive.\u00a0 Done manually, a field expansion project is expensive and high-risk \u2013 a waste of development talent and adding no functional value.<\/p>\n

Yet with the right tools, automation reduces IBM i field expansion projects<\/strong> by over 75% on average<\/strong>.<\/p>\n

There are many reasons why a field can become too small.\u00a0 For example, the bank identification (BIN) code recently expanded from 6 to 8 digits, requiring changes to banking software worldwide.\u00a0 Currency devaluations are another common cause. And given the longevity of IBM i applications, even a simple growth in business can leave a \u2018count\u2019 field too small!<\/p>\n

In our Webinar, we will demonstrate how to automate the entire process of field expansion<\/strong> in RPG and DB2 for i, including:<\/p>\n

    \n
  • Transformation of source code, propagation of changes from field to field<\/li>\n
  • Generation of data retrieval programs<\/li>\n
  • Regression testing of changes<\/li>\n<\/ul>\n

    Secure your \u2018field expansion\u2019 project and Watch Now!<\/p>\n<\/div><\/div><\/div>

    Missed our last webinar? Watch it on replay!<\/h2><\/h2><\/div>