In The Spotlight
IBM i systems used by enterprises in regulated industries face specific challenges in migrating to the cloud, but there are ways around some of the biggest problems.
By John Ghrist
IBM Power Systems and its predecessor platforms are strongly represented in regulated industries (e.g., banking, healthcare, insurance, government) that must follow national laws set up for these types of market sectors. These most notably include the Payment Card Industry Data Security Standard (PCI DSS), which requires protection of payment card account information; the Sarbanes-Oxley Act of 2002 (SOX), which mandates security controls on financial data and annual reporting/auditing of those controls; the Health Insurance Portability and Accountability Act (HIPAA), which specifies measures needed to protect the security and privacy of individual's data in the healthcare industry; and Europe's General Data Protection regulation (GDPR), which governs handling of the personal data of European Union residents.
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