This could occur when entering an invalid password when using ODBC.
<i>After this is processed the id status shows as disabled. Why is this happening?</i>
If that is the precise sequence (i.e., after the message appears the user ITJOHN is disabled but was enabled before the message), then the password that was supplied for ITJOHN was incorrect.
It might be ODBC, or it might be iSeries Navigator, or it might be any iSeries Access function that uses the Signon Server. (It could even be a 3rd-party product or home-grown, as long as authentication is through the Signon Server.)
The message ID CPIAD0B is simply the Signon Server reporting that it has been contacted to “Retrieve Signon Information” for ITJOHN. Whatever process was started on (almost certainly) a client PC in the name of ITJOHN requested a logon approval and was denied. Your system audit journal should contain more detail about why.
The most common reason might be a NetServer (e.g., Windows mapped drive) that is using a wrong password, perhaps a Windows password rather than the AS/400 password. However, many other possibilities exist.