Q: Is there any reason why a user with *ALLOBJ special authority is not authorized to sign on to a specific device? Shouldn't *ALLOBJ special authority override the authority for a device description (*DEVD)?
A: Your system value to limit security officer device access (QLMTSECOFR) is probably set to '1' (explicit device access required). It limits users with *ALLOBJ or *SERVICE special authority to only those devices for which they have specific authority. It's the one exception to authority checking I know of that is bypassed when a user has the *ALLOBJ special authority value.
You must either change system value QLMTSECOFR to '0' (explicit device access not needed) or grant the users in question the device authority needed. (A user needs *CHANGE authority to sign on.)
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