From: Gregory Leister To: All
Our operators have a habit of miskeying their password at IPL time and wind up varying off the terminal. The end result is having to do an IPL again. They also do this when only the console is active in QCTL and all other subsystems are terminated. Does anyone know an easy way around this? Any suggestions will be helpful.
From: Michael Brock To: Gregory Leister
1. Hire operators that are more careful.
2. Threaten them with finger removal.
3. Follow through with the threat from #2.
4. Kill them.
5. If the console keyboard has Play/Record feature, set up a keyboard macro for
Obviously, this response is a little tongue-in-cheek. However, I would strongly recommend any of the first four options before the fifth one (unless your situation is such that a macro sign-on would not be a threat to your security), with special emphasis on Option #1. This may seem a little harsh, especially since I don't know your operators, but it seems to me that one or two miskeys is a mistake, but repetitive errors of this type indicate nothing more than sheer carelessness.
From: Greg Leister To: Michael Brock
I agree with all of the options except 5 because of the ability for anyone to get into the system. If it were up to me I would choose #1 in the case of a repeated problem, but I have no control of that situation. Anyhow, my idea was to use a CL program to change the system value for sign-on attempts to *NOMAX, then PWR-DWNSYS to bring the system down, then use their default sign-on program to change it back, but I'm looking for a better way.
From: Ernie Malaga To: Gregory Leister
Change system value QMAXSGNACN to '2'. That only disables the user profile when the password is miskeyed past the maximum number you're allowing in QMAXSIGN. The display station will remain online. At this point, someone else (someone more careful, hopefully) can sign on instead of the klutz since the console is still up and running.
You can repeat this process until you get a successful sign-on or until you run out of user profiles.
Editor's Note: QSECOFR is the only user profile that is never disabled.
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