Then, shortly after migrating to V5R1, we noticed some strange messages in QSYSOPR that led us to the conclusion that someone was once again using us as an email relay. A quick check revealed that QUSRSYS/QTMSADRLST no longer existed, so I recreated it. When the SMTP server was restarted, however, it deleted QUSRSYS/QTMSADRLST! I then checked the iSeries Information Center and found that it too directed me to use QUSRSYS/QTMSADRLST as the means to prevent unauthorized email relaying.
At that point, I called IBM. The IBM rep I spoke to said that the Information Center is wrong and that relaying is now controlled by the ALWRLY parameter of the CHGSMTPA command. I changed it to *NONE, and that solved our problem. So add this to your list of things to check when converting to V5R1!
Joe Wells is a Sr. Systems Analyst with University of Alabama Health Services Foundation. He can be reached by email at
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