ACF2 NJE routed job ownership, inherits wrong logonid
search cancel

ACF2 NJE routed job ownership, inherits wrong logonid

book

Article ID: 246336

calendar_today

Updated On:

Products

ACF2 - z/OS

Issue/Introduction

Route a job to run on a different system, but having problem with ownership(logonid inheritance). Using Control-m scheduler to submit a job and the inherited userid is a problem. 

 

Environment

Release : 16.0

Component : ACF2 for z/OS

Resolution

Here are some options:

  1. If the LPARA node the ******** node specifies INHERIT, the local LPARA node accepts network job inheritance. A job sent to this node inherits the logonid of the user who submitted the job. Details can be found in section Network Job Entry Validation Options (NJE) under the INHERIT|NOINHERIT field of the GSO NJE record, INHERIT specifies that the local node accepts network job inheritance. A job sent to this node inherits the logonid of the user who submitted the job.
  2. If the LPARA node the ******** node specifies DFTLID(defaultlid) the default logonid defaultlid to be used for jobs that come from the remote node when no logonid can be associated with the job. (IBM restricts the NJE default logonid to a maximum of seven characters.) The DFTLID value that you specify must be a valid, specific logonid (no masking characters) defined to ACF2 at the home node. Also, you must set the RESTRICT field in the logonid record to indicate that the logonid does not require a password verification.

Details on the use of the GSO NJE record to configure the above options can be found in section Network Job Entry Validation Options (NJE).

 

This was helpful.  I don't have any further questions. You can close the ticket.