In The Spotlight
While IBM i modernizations promise that decades-old business logic can easily communicate with new Java-based microservices, implementing this can pose several challenges. The challenges mainly lie in the interface layer, where data must be converted from one type to another.
By Joydip Kanjilal
This isn't just about simple syntax errors; it also involves complex, subtle type-system problems that arise from fundamental differences in how RPG represents data versus how Java and other modern standards, such as JSON, represent it.
Business users want new applications now. Market and regulatory pressures require faster application updates and delivery into production. Your IBM i developers may be approaching retirement, and you see no sure way to fill their positions with experienced developers. In addition, you may be caught between maintaining your existing applications and the uncertainty of moving to something new.
IT managers hoping to find new IBM i talent are discovering that the pool of experienced RPG programmers and operators or administrators with intimate knowledge of the operating system and the applications that run on it is small. This begs the question: How will you manage the platform that supports such a big part of your business? This guide offers strategies and software suggestions to help you plan IT staffing and resources and smooth the transition after your AS/400 talent retires. Read on to learn:
LATEST COMMENTS
MC Press Online