WA Agent will continue to run the job even if the UNIX account’s login access was blocked (denied) by the PAM configuration (/etc/pam.conf).
Example pam config
myapp auth sufficient pam_allow.so.1
myapp account required pam_unix_account.so.1
myapp account required pam_list.so.1 compat
myapp session required pam_allow.so.1
Release : 11.3/11.4/11.5
Component : CA Workload Automation System Agent
Agent ignored the PAM settings for account in the pam.conf
This issue has been resolved post-R12 agent. Consult support on providing the new fix.
Users will have to first upgrade to R12 agent and then apply the special fix.