15.2.20 Changing the settings for retries when user information is acquired
In JP1/AJS3, when a job# starts or ends, information about the OS user who executes the job is acquired. If viewing of user information from the OS password file is temporarily disabled due to adding or deleting OS users or changing their passwords, the KAVU7533-E message (for a queueless job, the KAVS1888-E or KAVS1884-E message) is output to the integrated trace job. At the same time, the status of the job changes to Failed to start or Ended abnormally.
If viewing of the OS password file is retried at regular intervals, this prevents the status of the job from changing to Failed to start or Ended abnormally.
Normally, you do not need to change this setting.
- #
-
A Unix job, a flexible job, an HTTP connection job an action job, a custom job, a queue job to be executed on the local host, or a submit job.
The following describes how to specify the setting. Note that the setting must be specified on the host on which the job will be executed.
- Organization of this subsection
(1) Definition procedure
-
Stop the JP1/AJS3 service.
Execute the following commands to confirm that all processes have stopped:
- When Standard is specified as Exec. Service of the job
# /etc/opt/jp1ajs2/jajs_stop#1 # /opt/jp1ajs2/bin/jajs_spmd_status
- #1:
-
Confirm that automatic termination has been set.
- When Queueless Agent is specified as Exec. Service of the job (when the job is a queueless job)
# /opt/jp1ajs2/bin/ajsqlstop # /opt/jp1ajs2/bin/ajsqlftpstop#1 # /opt/jp1ajs2/bin/ajsqlstatus
- #1:
-
This command must be executed only on JP1/AJS3 - Manager.
-
Execute the following command to set the environment setting parameter described in (2) below:
jajs_config -k "definition-key" "parameter-name"=value
You can specify only one definition key. If you want to set environment setting parameters for different definition keys, you must execute the jajs_config command for each definition key.
-
Restart JP1/AJS3.
The new settings are applied.
(2) Environment setting parameter
Definition key |
Environment setting parameter |
Explanation |
---|---|---|
[{JP1_DEFAULT|logical-host}\JP1NBQAGENT\Job]# |
"GetPasswd_RetryCount"= |
This parameter applies when Standard is specified for Exec. Service of the job, and specifies the maximum number of retry attempts when an attempt to acquire user information from the OS password file has failed. |
"GetPasswd_RetryInterval"= |
This parameter applies when Standard is specified for Exec. Service of the job, and specifies the retry interval when an attempt to acquire user information from the OS password file has failed. |
|
[{JP1_DEFAULT|logical-host}\JP1QLAGENT]# |
"AJSQL_GETPASSWD_AGTRETRYCOUNT"= |
This parameter applies when Queueless Agent is specified for Exec. Service of the job, and specifies the maximum number of retry attempts when the queueless agent service is unable to acquire user information from the OS password file. |
"AJSQL_GETPASSWD_AGTRETRYINTERVAL"= |
This parameter applies when Queueless Agent is specified for Exec. Service of the job, and specifies the retry interval when the queueless agent service is unable to acquire user information from the OS password file. |
- #:
-
The specification of the {JP1_DEFAULT|logical-host} part depends on whether the host is a physical host or a logical host. For a physical host, specify JP1_DEFAULT. For a logical host, specify the logical host name.
Definition key |
Environment setting parameter |
Explanation |
---|---|---|
[JP1_DEFAULT\JP1QLAGENT] |
"AJSQL_GETPASSWD_FTPRETRYCOUNT"= |
This parameter applies when Queueless Agent is specified for Exec. Service of the job, and specifies the maximum number of retry attempts when the queueless file transfer service is unable to acquire user information from the OS password file. |
"AJSQL_GETPASSWD_FTPRETRYINTERVAL"= |
This parameter applies when Queueless Agent is specified for Exec. Service of the job, and specifies the retry interval when the queueless file transfer service is unable to acquire user information from the OS password file. |
For details about the definition of these environment setting parameters, see the following:
(3) Notes
-
Because the retries described above are also performed if the user has not been registered, it might take a long period of time until a job's status changes to Failed to start or Ended abnormally. Make sure that the OS user is registered correctly.
-
For queueless jobs, because a new queueless job cannot be started during a retry, setting a long retry period can cause the execution of jobs to be delayed. Therefore, adjust the maximum number of retries and retry interval so that operation is not affected.