Hitachi

JP1 Version 12 JP1/Automatic Job Management System 3 Messages


KAVU7533-E

The execution user (user-name) mapped from JP1 user (host name=host-name, JP1 user name=user-name) is invalid. (reason code:reason-code)

An invalid execution user name is mapped.

(S)

Cancels the requested processing.

(O)

The reason code is given as follows:

For Windows

Value obtained by Win32 API function GetLastError

For UNIX

Value obtained by errno

The following describes probable causes for reason codes, and suggests corrective actions:

For Windows
  • If reason-code is 1326

    The access token for the OS user executing the job might not have been acquired. Note the following points:

    - If the user who executes the job is a domain user, the status of the domain controller might be the cause of the error. For a user account to be referenced, the domain user must be able to log on. However, because JP1/AJS3 does not take into account the number and status of domain controllers, use care when restarting a domain controller during the execution of a job.

    - Acquisition of the access token might not be possible due to a temporary error in a Win32 API function. For details, see 5.4.1 User account for job execution in the manual JP1/Automatic Job Management System 3 Overview.

  • If reason-code is 1330

    When the job is executed with a user account that is different from a JP1/AJS3 service account, check whether the user password has expired.

  • If reason-code is 1385

    Check whether message KAVU7201-E was ouput to the integrated trace log before or after this error message. If so, see the message explanation.

    If message KAVU7201-E was not output, set Allow Log On Locally in the security policy for the OS user and then re-execute the job.

  • If reason-code is 1792

    When the job is executed with a user account that is different from a JP1/AJS3 service account, check whether the NetLogon service is running.

  • If reason-code is 1909

    The account of the OS user executing the job might be locked out. Check whether an invalid password was set for the OS user who executed the job.

    If the account is locked out, unlock it and then re-execute the job.

    For details about how to unlock an account, see the Microsoft website.

For UNIX

Even though the OS user executing the job is currently registered, a temporary error might occur due to an OS system call when the OS user is registered or unregistered, or the OS user's password is changed. If a temporary error occurs, wait until the registration, unregistration, or password change is completed and then re-execute the job.

You can change the retry settings for acquiring user information. For details, see 15.2.20 Changing the settings for retries when user information is acquired in the JP1/Automatic Job Management System 3 Configuration Guide.

If reason-code is other than the above, inappropriate OS users might have been registered in the user mapping definition.

Check the following points, and if any applies, register an appropriate OS user.

  • Whether a non-existent OS user has been registered

  • Whether an invalid password has been registered for an OS user

  • Whether an OS user with an invalid account has been registered

  • Whether an OS user who does not have permission to log on has been registered

If the user mapping definition has no errors, memory might have become insufficient. If so, review memory estimates.

If the OS is Windows, you can reduce the frequency of this error by reusing an access token during job execution. For details on how to enable reuse of an access token during job execution, see 6.2.17 Reusing access tokens for job execution in the JP1/Automatic Job Management System 3 Configuration Guide.