Job Management Partner 1/Automatic Job Management System 3 System Design (Configuration) Guide

[Contents][Glossary][Index][Back][Next]

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

This subsection describes the types of situations where it might be advisable to change the JP1/AJS3 service settings from the defaults. The JP1/AJS3 service setting for linking to another program is also explained.

Organization of this subsection
(1) Changing the account for services provided by JP1/AJS3
(2) Account for linking to the mail service
(3) Required changes for linking to JP1/Power Monitor
(4) Required changes for using the JP1/Base startup control

(1) Changing the account for services provided by JP1/AJS3

Depending on the job execution environment, it might be better to change the account for the JP1/AJS3 services to a user account. Examine the user account settings in JP1/AJS3 services as needed.

The following describes the types of situations when you will need to change the account used by the following services:

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

In JP1/AJS3, each job that is executed uses the Windows desktop heap (a system resource). If a large number of jobs are executed concurrently, there might be insufficient space in the desktop heap, and jobs might end abnormally.

The procedure below can help to reduce desktop heap shortages, although it will not completely prevent the problem:

  1. Change the account for JP1/AJS3 services from the system account to a user account.
    By making the account used by JP1/AJS3 services the same as the user account for executing jobs, you can reduce the likelihood of desktop heap shortages.
    In JP1/AJS3, jobs can be executed under any user account. However, when jobs are executed under a user account different from the JP1/AJS3 services account, they will use a desktop heap area different from that used by the JP1/AJS3 services. As a result, if a large number of jobs are executed concurrently under an account different from the JP1/AJS3 services account, desktop heap shortages might occur.
    Changing a JP1/AJS3 service account to the user account for job execution ensures that jobs will use the same desktop heap area as used by the JP1/AJS3 service. This reduces desktop heap usage at job execution, and can help reduce desktop heap shortages when a large number of jobs are executed at the same time.
    If using domain user accounts, specify both the user account for job execution and the JP1/AJS3 service account in the format domain-user\user-name. Do not specify .local after the domain name.
  2. Enable the setting for reusing an access token when a job is executed.
    When Standard is specified in Exec. Service, by enabling the setting for reusing an access token when a job is executed, you can reduce desktop heap usage. This also reduces desktop heap shortages when a large number of jobs are executed at the same time. 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 the procedure, see the relevant information on Microsoft's Help and Support website.
    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:

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

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.

(2) Account for linking to the mail service

The mail service account does not have to be the same as the JP1/AJS3 services account.

In the JP1/AJS3 Mail service, set the account of a user for whom a mail profile has been defined. Also, set the following privileges:

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

Set these privileges in the Local Security Policy.

(3) Required changes for linking to JP1/Power Monitor

To perform power control linked with JP1/Power Monitor, you must start JP1/AJS3 using the JP1/Base startup control. In this case, set the Startup Type of the JP1/AJS3 service to Manual.

(4) Required changes for using the JP1/Base startup control

By default, the JP1/AJS3 service starts under the JP1/Base startup control.

When using the JP1/Base startup control:
Set the Startup Type of the JP1/AJS3 service to Manual.
If you have upgraded from JP1/Base version 8 to version 9 or later, comment-out the automatic startup parameter Jp1AJS2MONITOR in the JP1/Base start sequence definition file Jp1svprm.dat.

When not using the JP1/Base startup control:
The Startup Type of the JP1/AJS3 service can be set as Manual or Automatic.

[Contents][Back][Next]

[Trademarks]

Copyright (C) 2009, 2010, Hitachi, Ltd.
Copyright (C) 2009, 2010, Hitachi Solutions, Ltd.