I added the system date and time to the sign-on screen using SDA. Much to my surprise, the date was not always accurate. My initial response was, "How could the system date be wrong?" But the system date was always correct. Where else could the date be coming from? Testing the screen with SDA always showed the correct date.
Finally, a call to IBM service provided the surprising answer. The date on the sign-on screen is not the system date but, instead, the date that QINTER was started. Our operators end QINTER prior to the nightly backup and then start QINTER when the backup has finished. This usually happens after midnight-but the process can end before midnight, causing the date on the sign-on screen to be one day behind.
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