Route XEQ NJE job receives ACF2 $ACFJ225 error
Article ID: 259409
Updated On:
Products
Issue/Introduction
Error $ACFJ225 JOB SUBMISSION NOT AUTHORIZED is seen when submitting a Route XEQ job via NJE.
What is causing this error? Are there any definitions missing in ACF2?
Environment
Release : 16.0
Resolution
When reviewing the console log on the receiving system, the following additional error was found during the processing of the job:
ACF01004 LOGONID nodename NOT FOUND
When controlling the submission of jobs, there's the option to either control access by submitter or control access by jobname. The resource names for this are as follows:
Control access by submitter:
FACILITY class JES.JOBCLASS.SUBMITTER resource
JESJOBS class JOBCLASS.node.class.jobname resource
Control access by jobname:
JESJOBS class SUBMIT.nodename.jobname.userid resource
Regardless of the option chosen, if the JESJOBS class is active, one or both of these resources are validated for the submitter id for the job. If the submitting id does not exist as a logonid, ACF2 will try to validate access for the nodename. If that id does not exist, the job will fail with the $ACFJ225 message seen above.
If the JESJOBS class is active, at minimum JESJOBS SUBMIT access (control access by jobname) needs to be granted to the submitter or nodename which also needs to be a valid logonid in ACF2.
Activating the JESJOBS class is optional when performing an SDSF migration. It is not a requirement for SDSF migration.
Additional Information
When troubleshooting this issue, note that the ACF01004 message will not be associated with a job number when looking at the console log and at first glance may appear unrelated.
KD Article 9007: NJE jobclass validation is getting message ACF01004 for a logonid that is the node name of the submitting system. Why is a logonid needed for the submitting node? provides additional information regarding controlling access by submitter.
Feedback
