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

(a) When executing more concurrent jobs than usual or when you want to avoid desktop heap shortages

JP1/AJS3 uses Windows desktop heap (system resource) space secured separately for each job that is executed. For this reason, if you execute many jobs simultaneously, the desktop heap available to the OS runs low, potentially causing jobs to enter the Ended abnormally status. Note that the size of the desktop heap used by each JP1/AJS3 service or job depends on the environment.

You can use the following procedure to decrease the frequency of OS desktop heap shortages. However, note that no procedure can completely prevent desktop heap shortages. In Windows Server 2012 or Windows Server 2008, the size of the desktop heap available to the OS expands so that desktop heap shortages are rare. Therefore, the following procedure is not necessary. For details, check the information posted on the Microsoft website.

1. Change the account for JP1/AJS3 services from the system account to a user account.

   When you execute a job, if you use a user account that is not the same as the JP1/AJS3 services account, each job uses a different space in the desktop heap. This space is space that is not space in the desktop heap used by the JP1/AJS3 services. Accordingly, if you use a user account that is different from the JP1/AJS3 services account to execute many jobs simultaneously, desktop heap shortages might occur.

   If the JP1/AJS3 services account and the user account for executing jobs match, you can share the space in the desktop heap secured for JP1/AJS3 services when they started, reducing the frequency of OS desktop heap shortages.

   If you use a domain user, specify domain-name\user-name for both the user account for executing jobs and the JP1/AJS3 services account. Do not specify .local after domain-name.

   Although you can specify .\user-name as the JP1/AJS3 services account on a host in the domain environment, the service control manager might start the JP1/AJS3 processes for the domain user.

2. Enable the setting for reusing an access token when a job is executed.

   When Standard is selected in the Exec. Service box in a job definition, you can enable the setting for reusing access tokens to turn off the acquisition of desktop heap space for each job execution. By doing so, you can reduce the frequency of OS desktop heap shortages when many jobs are executed simultaneously. For details about this setting, see 6.2.17 Reusing access tokens for job execution in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1.

3. Change the desktop heap size.

   You can change the desktop heap size by editing the Windows registry information. For details about how to edit the registry, go to Microsoft Support on the web for technical information about the desktop heap.

   Usage of the desktop heap by JP1/AJS3 services and active jobs depends on your system environment. Note that changing the heap size without proper forethought could affect the entire system. Keep this in mind before you decide to change the desktop heap size.

(b) 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

(c) 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.

(d) 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 Console Manager service

• JP1/AJS3 Console Agent service

• JP1/AJS3 Check Manager service

• JP1/AJS3 Check Agent service

• JP1/AJS3 Queueless Agent service

• JP1/AJS3 Queueless File Transfer 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 Job Management Partner 1/Base User's Guide about how to grant user rights to an OS user in an Active Directory environment.