13.1.6 Limiting JP1/AJS3 - Manager resources to those used for job operation
Even if you use JP1/AJS3 - Manager only for job execution, the functions you do not use still use system resources, increasing the load on the host. This case study describes how to reduce resources used by JP1/AJS3 by restricting the functionality of JP1/AJS3 - Manager to job execution.
- Organization of this subsection
(1) Operation
A logical host is set up on a physical host, and instances of JP1/AJS3 - Manager are installed on the physical and logical hosts. Each host is utilized as follows:
- Physical host
-
Executes jobs but does not provide the functionality of a manager host.
- Logical host
-
Serves as a manager host.
The following figure shows this type of host configuration.
|
(2) Goal
To reduce the use of resources by JP1/AJS3.
(3) Solution
Suppress startup of some JP1/AJS3 processes. For example, in Figure 13-14, you can prevent the embedded database from starting automatically on the physical host, limiting the functionality of JP1/AJS3 - Manager on the physical host to that which is essential for job execution.
This process reduces the memory used by the JP1/AJS3 system, and also cuts down the startup time.
(4) Timing
Perform the settings before starting operation.
(5) Configuration procedure
The procedures for Windows and UNIX are described below. Make sure that you back up the configuration and definition files before modifying them. To undo your changes, restore the backup file to its original location. For details, see 2.3.3 Recovering the JP1/AJS3 - Manager setup information.
(a) In Windows
-
If the embedded database uses a method from a version earlier than 10-00, change the value set in the system common definition file.
Open the following file in a text editor such as Notepad, and change the setting. Do not perform this step if the embedded database uses a method from version 10-00 or later.
embedded-database-practical-directory\conf\pdsys
- Before
-
set pd_mode_conf = AUTO
- After
-
set pd_mode_conf = MANUAL2
-
Change the entries in the JP1/AJS3 startup process definition file.
Open the startup process definition file in a text editor such as Notepad, and delete lines beginning with jajs_dbmd, jajs_hstd, and jajs_schd.
- Path of startup process definition file:
-
JP1/AJS3-installation-folder\conf\jp1ajs_spmd.conf
- Before
-
jajs_dbmd|jajs_dbmd.exe|||1800|
jajs_hstd|jajs_hstd.exe|||1800|
jajs_agtd|jajs_agtd.exe|||1800|
jajs_schd|jajs_schd.exe|||1800|
- After
-
jajs_agtd|jajs_agtd.exe|||1800|
- Remarks
-
If you use a logical host for job execution and want to prevent certain processes from starting on the logical host, edit the startup process definition file at the following location:
shared-folder-specified-by-jajs_setup_cluster-command\jp1ajs2\conf\jp1ajs_spmd.conf
-
Change the entries in the JP1/AJS3 extended startup process definition file.
Open the extended startup process definition file in a text editor such as Notepad, and delete lines beginning with jajs_dbmd, jajs_hstd, and jajs_schd. Also delete the jajs_hstd portion of the line beginning with jajs_agtd.
The following are the location of the startup process definition file and an example of the changes.
- Path of extended startup process definition file:
-
JP1/AJS3-installation-folder\conf\jp1ajs_service_0700.conf
- Before
-
jajs_dbmd|jajs_dbmd.exe||0|3|3|21600|0|2||1|||||||
jajs_hstd|jajs_hstd.exe||1|3|20|21600|0|0|jajs_dbmd|1|||||||
jajs_agtd|jajs_agtd.exe|-HA|1|3|3|21600|0|0|jajs_hstd|1|||||||
jajs_schd|jajs_schd.exe|-HA|1|3|10|21600|0|1|jajs_agtd|1|||||||
- After
-
jajs_agtd|jajs_agtd.exe|-HA|1|3|3|21600|0|0||1|||||||
- Remarks
-
If you use a logical host for job execution and want to prevent certain processes from starting on the logical host, edit the extended startup process definition file at the following location:
shared-folder-specified-by-jajs_setup_cluster-command\jp1ajs2\conf\jp1ajs_service_0700.conf
-
Restart the JP1/AJS3 service.
(b) In UNIX
-
If the embedded database uses a method from a version earlier than 10-00, change the value set in the system common definition file.
Open the following file in an editor such as vi, and change the setting. Do not perform this step if the embedded database uses a method from version 10-00 or later.
embedded-database-practical-directory/conf/pdsys
- Before
-
set pd_mode_conf = AUTO
- After
-
set pd_mode_conf = MANUAL2
-
Change the entries in the JP1/AJS3 startup process definition file.
Open the startup process definition file in a text editor such as vi, and delete lines beginning with jajs_dbmd, jajs_hstd, and jajs_schd.
The following are the location of the startup process definition file and an example of the changes.
- Path of startup process definition file:
-
/etc/opt/jp1ajs2/conf/jp1ajs_spmd.conf
- Before
-
jajs_dbmd|/opt/jp1ajs2/bin/jajs_dbmd|||1800|
jajs_hstd|/opt/jp1ajs2/bin/jajs_hstd|||1800|
jajs_agtd|/opt/jp1ajs2/bin/jajs_agtd|||1800|
jajs_schd|/opt/jp1ajs2/bin/jajs_schd|||1800|
- After
-
jajs_agtd|/opt/jp1ajs2/bin/jajs_agtd|||1800|
- Remarks
-
If you use a logical host for job execution and want to prevent certain processes from starting on the logical host, edit the startup process definition file at the following location:
shared-directory-specified-by-jajs_setup_cluster-command/jp1ajs2/conf/jp1ajs_spmd.conf
-
Change the entries in the JP1/AJS3 extended startup process definition file.
Open the extended startup process definition file in a text editor such as vi, and delete lines beginning with jajs_dbmd, jajs_hstd, and jajs_schd. Also delete the jajs_hstd portion of the line beginning with jajs_agtd.
The following are the location of the startup process definition file and an example of the changes.
- Path of extended startup process definition file:
-
/etc/opt/jp1ajs2/conf/jp1ajs_service_0700.conf
- Before
-
jajs_dbmd|/opt/jp1ajs2/bin/jajs_dbmd||0|3|3|21600|0|2||1|||||||
jajs_hstd|/opt/jp1ajs2/bin/jajs_hstd||1|3|20|21600|0|0|jajs_dbmd|1|||||||
jajs_agtd|/opt/jp1ajs2/bin/jajs_agtd|-HA|1|3|3|21600|0|0|jajs_hstd|1|||||||
jajs_schd|/opt/jp1ajs2/bin/jajs_schd|-HA|1|3|10|21600|0|1|jajs_agtd|1|||||||
- After
-
jajs_agtd|/opt/jp1ajs2/bin/jajs_agtd|-HA|1|3|3|21600|0|0||1|||||||
- Remarks
-
If you use a logical host for job execution and want to prevent certain processes from starting on the logical host, edit the extended startup process definition file at the following location:
shared-directory-specified-by-jajs_setup_cluster-command/jp1ajs2/conf/jp1ajs_service_0700.conf
-
Restart the JP1/AJS3 service.
(6) Manual references
Type |
Item |
Location |
---|---|---|
Overview |
Process list |
|
Configuration |
C.1 Preparation for using an embedded database in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1 |
(7) Cautionary notes
-
When you use the procedures described in this case study to prevent JP1/AJS3 from starting certain processes, the output of the jajs_spmd_status command changes. The following are examples of the output of the jajs_spmd_status command when some processes are prevented from starting.
In Windows
KNAD3690-I Processing to report the status of JP1/AJS3 has started. Running processes are as follows: Process name Process ID jajs_agtd xxxx queuea xxxx evactiona xxxx KNAD3691-I All the processes have started.
In UNIX
KNAD3690-I Processing to report the status of JP1/AJS3 has started. Running processes are as follows: Process name Process ID jajs_agtd xxxx jpqmon xxxx jpqagent xxxx KNAD3691-I All the processes have started.
-
If you use the procedures described in this case study to prevent JP1/AJS3 from starting certain processes, you can only use the commands provided by JP1/AJS3 - Agent from that point onward. For details about the commands provided by JP1/AJS3 - Agent, see 1.5 Commands in the manual Job Management Partner 1/Automatic Job Management System 3 Command Reference 1.
-
After you perform the procedures described in this case study, you will no longer be able to configure a logical host to attach and detach automatically in Windows when using queueless jobs.
For details about how to configure JP1/AJS3 to automatically attach and detach logical hosts, see 8.2.5 Setting up the queueless job execution environment in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1.