4.2.3 Changing the JP1/AJS3 service settings (Windows only)

(a) When using network resources

If you use network resources (that is, shared jobs), change the account for the JP1/AJS3 services to a user account.

When a job batch file requires a connection to a network drive, making the account for the JP1/AJS3 services the same as the account for the user who starts the job will allow other jobs started from that user account to disconnect the network drive.

As the file name specified in the detailed definition of the job, instead of a path beginning with the network drive name, specify a path beginning with the computer name, as follows: \\computer-name\shared-folder\file-name

(b) When multiple scheduler services are activated and you want to avoid desktop heap shortages

Depending on the system environment, an error might occur when more than a certain number of scheduler services are activated concurrently. In this case, an error message (event ID 26) is output to the Windows event log, reporting that the application was not initialized correctly. This occurs when there are insufficient system resources (desktop heap shortage).

In JP1/AJS3, many control processes are activated by each scheduler service. When multiple scheduler services are activated concurrently, usage of the desktop heap increases proportionately and shortages might occur. In such cases, change the account used by the JP1/AJS3 services from the system account to a user account. This will prevent use of the same desktop heap area by both JP1/AJS3 services and other service programs.

(c) Privileges for running JP1/AJS3 services under a user account

The following describes the privileges you need to set when running the following services under a user account:

• JP1/AJS3 service

• JP1/AJS3 Database service

• JP1/AJS3 Check Manager service

• JP1/AJS3 Check Agent service

• JP1/AJS3 Queueless Agent service

• JP1/AJS3 Queueless File Transfer service

• JP1/AJS3 Autonomous Agent service

• JP1/AJS3 Autonomous Agent Messenger service

• JP1/AJS3 Web Application Server service

• JP1/AJS3 HTTP Server service

• JP1/AJS3 System Control Manager service

• JP1/AJS3 System Control Agent service

When the type of the embedded database is one used for JP1/AJS3 - Manager before version 10-00, privileges also need to be set for the JP1/AJS3 Database ClusterService service.

To run the above services under a user account, grant the following privileges to the user:

• Administrators privilege

• Allow log on locally

• Log on as a service

• Replace process level token

• Increase process memory quota

Operation is not guaranteed if the set user account does not have these privileges.

Set these privileges in the Local Security Policy.

When the account under which JP1/AJS3 services are activated is changed from the system account to a user account, the size of the available desktop heap also changes. This might affect the number of jobs (batch files and script files) that can be executed concurrently.

Cautionary notes

1. Set the same user account for the JP1/AJS3 services on all logical hosts and physical hosts.

2. After setting the required privileges for the account used to activate JP1/AJS3 services, you must restart the services for the privileges to take effect.

3. In a domain environment that uses Active Directory, the setup procedure differs for the host that is the domain controller and for the hosts in the domain. For details, see the explanation in the JP1/Base User's Guide about how to grant user rights to an OS user in an Active Directory environment.

(d) Procedure for changing the JP1/AJS3 service startup account to a user account

The default of the JP1/AJS3 service startup account is the system account. Use the following procedure for changing the JP1/AJS3 service startup account to a user account.

1. Stop the JP1/AJS3 service.

2. Change the account used by the JP1/AJS3 services from the system account to a user account.

3. Grant the following privileges to OS user accounts:

   • Administrators privilege

   • Allow log on locally

   • Log on as a service

   • Replace a process level token

   • Increase process memory quota

4. Restart the JP1/AJS3 service.