ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.
Unable to run Job with CheckLogon=1 and ANONYMOUS_JOB=Y
Article ID: 84437
Updated On:
Products
CA Automic Workload Automation - Automation Engine
Issue/Introduction
Error Message :
U02001007 Uer "Username" is unknown or invalid password has been provide
It is not possible to run a job with CheckLogon=1 and ANONYMOUS_JOB=Y.
If the Job should be run as the User specified in the Login object, CheckLogon=1 should not be used.
If the requirement is not to supply passwords for the Login as well, ANONYMOUS_JOB=Y must be set.
However, when both CheckLogin=1 and ANONYMOUS_JOB=Y are set the Job will not run and the above error is displayed.
U02001007 Uer "Username" is unknown or invalid password has been provide
It is not possible to run a job with CheckLogon=1 and ANONYMOUS_JOB=Y.
If the Job should be run as the User specified in the Login object, CheckLogon=1 should not be used.
If the requirement is not to supply passwords for the Login as well, ANONYMOUS_JOB=Y must be set.
However, when both CheckLogin=1 and ANONYMOUS_JOB=Y are set the Job will not run and the above error is displayed.
Cause
Cause type:
By design
Root Cause: If either ANONYMOUS_JOB or CheckLogon=0 is set the Job will be started as the user provided in the Login Object and the password will not be verified.
By design
Root Cause: If either ANONYMOUS_JOB or CheckLogon=0 is set the Job will be started as the user provided in the Login Object and the password will not be verified.
Environment
OS: IBM AS/400
OS Version: N/A
OS Version: N/A
Resolution
If the variable ANONYMOUS_JOB is set or if CheckLogon=0 is set a job will be started as the user provided in Login Object but the password is not verified.
Therefore, you need to set ANONYMOUS_JOB=Y and CheckLogon=0.
Fix Status: No Fix
Fix Version(s):
N/A
Therefore, you need to set ANONYMOUS_JOB=Y and CheckLogon=0.
Fix Status: No Fix
Fix Version(s):
N/A
Additional Information
Workaround :
N/A
N/A
Feedback
Yes
No
Powered by
