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?
search cancel

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?

book

Article ID: 9007

calendar_today

Updated On:

Products

ACF2 ACF2 - DB2 Option ACF2 for zVM ACF2 - z/OS ACF2 - MISC PanApt PanAudit

Issue/Introduction

When a batch job is submitted through NJE to another node,
message ACF01004 - LOGONID XXXXXXXX NOT FOUND
is issued

where XXXXXXXX is the node name of the submitting system.

Why does this logonid need to exist?


 

Environment

ACF2 receiving node has a resource rule for FACILITY resources JES.JOBCLASS.SUBMITTER and JES.JOBCLASS.OWNER

Cause

The existence of FACILITY rules for
JES.JOBCLASS.SUBMITTER and JES.JOBCLASS.OWNER
causes a validation for CLASS=JESJOBS resources.
One for the OWNER of the job and one for the SUBMITTER of the job.

Resolution

The JESJOBS resource that will be validated is

JOBCLASS.node.class.jobname

For the owner validation of this resource, the logonid that the job will run under will be used.

For the submitter validation of the resource, a logonid for the submitter must be available
in the ACF2 database.  If there is no logonid for the submitter on this node, ACF2 will
use the nodename of the sending node as the submitter.
If this logonid does not exist the job will not be allowed to run and message ACF01004
will be issued.

The resolution is to create a logonid for either the submitter or the NODE name,
or to not cause validation of the submitter (by removing the FACILITY rule JES.JOBCLASS.SUBMITTER)