B.3 Processes (for UNIX)
The following table lists the processes of JP1/AJS3 programs and components for UNIX.
- Organization of this subsection
-
(1) Processes of JP1/AJS3 - Manager for UNIX
There are three kinds of processes of JP1/AJS3 - Manager for UNIX:
You can use the jajs_spmd_status command to check the status of the child processes of jajs_spmd. For details, see the description of jajs_spmd_status in 2. Commands in the manual Job Management Partner 1/Automatic Job Management System 3 Command Reference 1.
To check the status of parent, child and detail processes, use the ps command.
(a) Standard configuration
Table B-13 lists the parent and child processes. Table B-14 lists the child and detail processes. The number following a parent or child process name indicates the maximum number of
processes you can activate concurrently.
Table B‒13: Parent and child processes of JP1/AJS3 - Manager for UNIX
|
Parent process
(number of processes)
|
Description
|
Child process
(number of processes)
|
Description
|
|
jajs_spmd
(1)#1
|
JP1/AJS3 service
|
jajs_dbmd_embedded-database-setup-ID(1)#2
|
Database management
This process manages embedded databases.
|
|
jajs_hstd(1)
|
Host service management
|
|
jajs_schd_scheduler-service-name(1)#3
|
Scheduler service management
|
|
jajs_agtd(1)
|
Agent service management
|
|
ajsqlagtd(1)
|
JP1/AJS3 Queueless Agent service (queueless agent process)
This process accepts queueless job execution requests from JP1/AJS3 - Manager (scheduler service).
|
ajsqlagtd (number-of-jobs-to-be-executed)
|
Queueless job management process
This process executes queueless jobs.
The same process names are generated from the JP1/AJS3 Queueless Agent service (queueless agent process) respectively for
jobs to be executed.
The process is removed on completion of queueless job execution.
The process has no detail process.
The process is necessary when the local host executes queueless jobs.
|
|
ajsqlftpd(1)
|
JP1/AJS3 Queueless File Transfer service (queueless file transfer process)
This process accepts file transfer requests from the queueless job management process.
|
ajsqlftpd (number-of-file-transfer-requests)
|
Queueless file transfer worker process
This process transfers transfer files, standard output files and standard error output files.
The same process names are generated from the JP1/AJS3 Queueless File Transfer service (queueless file transfer process) respectively
for file transfer requests.
The process is removed on completion of file transfer.
The process has no detail process.
|
|
ajschkmand(1)
|
JP1/AJS3 Check Manager service
The process controls the definition pre-check (manager process).
|
--
|
--
|
|
ajschkagtd(1)
|
JP1/AJS3 Check Agent service
|
ajschkagtd(5)
|
The process controls the definition pre-check (agent process).
|
- Legend:
-
--: Not applicable.
- #1
-
By specifying logical host names on the command line, you can differentiate between processes for physical hosts and for logical
hosts.
A process for a logical host is represented as process-name -h logical-host-name.
For example, when a logical host name is hostA, the jajs_spmd process for hostA is represented as jajs_spmd -h hostA.
- #2
-
The process name is indicated as jajs_dbmd_embedded-database-setup-ID.
For example, if the embedded database setup ID is_JF0, the process name is jajs_dbmd_JF0. If multiple embedded databases are used, the number of processes that start equals the number of embedded databases.
- #3
-
The process name is indicated as jajs_schd_scheduler-service-name.
For example, if the scheduler service name is AJSROOT1, the process name is jajs_schd_AJSROOT1. If multiple scheduler services are running, the number of processes that start equals the number of scheduler services.
Table B‒14: Child and detail processes of JP1/AJS3 - Manager for UNIX
|
Child process name
|
Detail process name
|
Description
|
|
jajs_dbmd_embedded-database-setup-identifier
|
ajsdbmgrd
|
Database operation control
This process starts, stops, and monitors embedded databases.
|
|
jajs_hstd
|
ajshlogd
|
Host-service-specific log management
|
|
ajsinetd
|
Network control process that controls access from other servers
|
|
ajsnetwd
|
Communication control and management
|
|
ajsagtmd
|
Agent management
|
|
ajsovstatd
|
This process monitors JP1/AJS3 from HP NNM when HP NNM is linked.
The process has no detail process.
|
|
ajsgwmasterd
|
This process manages the scheduler service inter-communication control process when jobnet connectors are used to control
the execution order of root jobnets between different scheduler services. The scheduler service inter-communication control
process enables communication between jobnet connectors and the jobnets to which they connect.
|
|
jpqman#1
|
Job execution control manager process.
Main process for the processing that is specific to job execution control, such as the reception of submit jobs.
|
|
jpomanager
|
Event/action control manager process.
This process manages event jobs.
|
|
jajs_schd
|
ajslogd
|
Process for recording scheduler information
|
|
jpqman#1
|
Job execution control manager process.
Main process for the processing that is specific to job execution control, such as the reception of submit jobs.
|
|
jpomanager
|
Event/action control manager process.
This process manages event jobs.
|
|
ajsmasterd
|
Scheduler.
This process monitors all the processes of the scheduler service.
|
|
jajs_agtd
|
jpqmon
|
Job execution control.
This process monitors all the processes of job execution control.
|
|
jpoagent
|
Event/action control agent process.
This process monitors and controls the monitoring processes other than jpomanager. jpoagent also controls monitoring processes
on JP1/AJS3 - Manager.
|
|
ajsinetd
|
ajsmonsvr#2
|
Process activated when JP1/AJS3 - View is connected. This process has no detail process.
|
|
ajsrcmdsvr
|
Process to be activated when a remote jobnet is executed, when a command is executed remotely, or when a JP1/AJS3 command
is executed from JP1/AJS3 - View.
|
|
ajsgwmasterd#1
|
ajsgwd#3
|
Scheduler service inter-communication control process.
This process enables communication between jobnet connectors and their connection target jobnets when jobnet connectors are
used to control the execution order of root jobnets between different scheduler services.
|
|
jpomanager#1
|
jpomgrsub#1
|
Event/action control submanager process
|
|
ajsmasterd
|
ajsschd#3
|
Schedule control process
|
|
ajsschbd#3, #4
|
Generation management subprocess
|
|
ajsflowd#3
|
Flow control process
|
|
ajssubd#3
|
Job submit process
|
|
ajssubwd#3
|
Job completion wait process
|
|
jpqnfyfd#1
|
Process for reporting the job execution control status
|
|
ajsremnetcl#3
|
Process for requesting the registration and the cancellation of registration of remote jobnets
|
|
ajsreqd#3
|
Queueless job request process.
A maximum of eight process instances start from ajsflowd.
|
|
ajsflbd#3, #5
|
Flow control subprocess
|
|
jpqmon#1
|
jpqagt#1
|
Agent process for job execution control
This process activates jobs.
|
|
jpqagtdmn#1
|
Job monitoring process activating process for job execution control
Process for activating the job monitoring process
Five processes are always activated. In a cluster system, five processes are activated for each logical host.
|
|
jpqagtchild#1
|
Job monitoring process for job execution control
Process for monitoring job process execution
Five processes are activated in the initial status. Also, one process is activated for each execution job. In a cluster system,
five processes are activated for each logical host.
|
|
jpoagent#1
|
jpoagtsub#1
|
Event/action control subagent process.
This process mainly notifies the manager of information from the monitoring process.
|
|
jpocwtflMain#1
|
File monitoring process
|
|
jpocwttmMain#1
|
Execution interval control process
|
|
jpoeventwatch#1
|
Event (such as JP1 event or log trap) monitoring process
|
|
jpoevsearch#1
|
Event search process.
This process starts to search for the specified event when a JP1 event reception monitoring job specified with a pre-execution
event search is executed.
|
|
jpocwtmlmain#1
|
Mail monitoring communication process
|
- Note
-
When you execute a command, a process with the same name as the command is activated.
- #1
-
A process name for a logical host is indicated as process-name logical-host-name. For example, when the logical host name is hostA, the ajsmasterd process for hostA is ajsmasterd hostA.
- #2
-
One process starts for the selected scheduler service when you select a scheduler service in the tree area in a JP1/AJS3 -
View window.
The maximum number of processes that can start is number-of-scheduler-services x number-of-connected-instances-of-JP1/AJS3 - View.
- #3
-
You can differentiate between a process for a physical host and a process for a logical host. A process name for a logical
host is indicated as process-name_logical-host-name.
For example, when the logical host name is hostA, the ajsschd process for hostA is indicated as ajsschd_hostA.
- #4
-
This process starts only when you specify the environment settings as described in 15.1.6 Changing the mode in which unregistration or generation management deletes the generations of a jobnet in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1.
- #5
-
This process starts only when you specify the environment settings as described in 15.1.7 Settings for using wait conditions in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1.
(b) Compatible ISAM configuration
Table B-15 lists the parent and child processes. Table B-16 lists the child and detail processes. A value in parentheses after a parent process name or a child process name in the tables
indicates the number of processes that can start simultaneously.
Table B‒15: Parent and child processes of JP1/AJS3 - Manager for UNIX
|
Parent process
(number of processes)
|
Description
|
Child process
(number of processes)
|
Description
|
|
jajs_spmd (1)#
|
JP1/AJS3 service
|
jajs_hstd (1)
|
Host service management
|
|
jajs_agtd (1)
|
Agent service management
|
|
ajsqlagtd (1)
|
JP1/AJS3 Queueless Agent service (queueless agent process)
This process accepts execution requests for queueless jobs from JP1/AJS3 - Manager (scheduler service).
|
ajsqlagtd
(number-of-jobs-to-be-executed)
|
Queueless job management process.
This process executes queueless jobs.
The process is generated by the JP1/AJS3 Queueless Agent service (queueless agent process) for each job to be executed. The
parent process and the child process have the same name.
The process disappears when execution of a queueless job ends.
This process has no detail process.
The process is required when you execute queueless jobs on a local host.
|
|
ajsqlftpd (1)
|
JP1/AJS3 Queueless File Transfer service (queueless file transfer process)
This process accepts file transfer requests from the queueless job management process.
|
ajsqlftpd
(number-of-file-transfer-requests)
|
Queueless file transfer worker process.
This process transfers data to a transfer file, the standard output file, and the standard error output file.
The process is generated by the JP1/AJS3 Queueless File Transfer service (queueless file transfer process) for each file transfer
request. The parent process and the child process have the same name.
The process disappears when file transfer ends.
This process has no detail process.
|
|
ajschkmand (1)
|
JP1/AJS3 Check Manager service
The process controls definition pre-checks (manager process).
|
--
|
--
|
|
ajschkagtd (1)
|
JP1/AJS3 Check Agent service
|
ajschkagtd (5)
|
The process controls definition pre-checks (agent process).
|
- Legend:
-
--: Not applicable.
- #
-
When you specify a logical host name on the command line, you can differentiate between a process for a physical host and
a process for a logical host.
A process name for a logical host is indicated as process-name -h logical-host-name.
For example, when the logical host name is hostA, the jajs_spmd process for hostA is jajs_spmd -h hostA.
Table B‒16: Child and detail processes of JP1/AJS3 - Manager for UNIX
|
Child process name
|
Detail process name
|
Description
|
|
jajs_hstd
|
ajshlogd
|
Host-service-specific log management
|
|
ajsinetd
|
Network control process that controls access from other servers
|
|
ajsnetwd
|
Communication control and management
|
|
ajsovstatd
|
This process monitors JP1/AJS3 from HP NNM when HP NNM is linked.
The process has no detail process.
|
|
ajsgwmasterd
|
This process manages the scheduler service inter-communication control process when jobnet connectors are used to control
the execution order of root jobnets between different scheduler services. The scheduler service inter-communication control
process enables communication between jobnet connectors and the jobnets to which they connect.
|
|
jpqman#1
|
Job execution control manager process.
Main process for the processing that is specific to job execution control, such as the reception of submit jobs.
|
|
jpomanager
|
Event/action control manager process.
This process manages event jobs.
|
|
ajsmasterd
|
Scheduler.
This process monitors all the processes of the scheduler service.
|
|
jajs_agtd
|
jpqmon
|
Job execution control.
This process monitors all the processes of job execution control.
|
|
jpoagent
|
Event/action control agent process.
This process monitors and controls the monitoring processes other than jpomanager. jpoagent also controls monitoring processes
on JP1/AJS3 - Manager.
|
|
ajsinetd
|
ajsmonsvr#2
|
Process activated when JP1/AJS3 - View is connected.
This process has no detail process.
|
|
ajsrcmdsvr
|
Process activated when a remote jobnet is executed or a command is remotely executed
|
|
ajsgwmasterd#1
|
ajsgwd#3
|
Scheduler service inter-communication control process.
This process enables communication between jobnet connectors and the jobnet to which they connect when jobnet connectors are
used to control the execution order of root jobnets between different scheduler services.
|
|
jpomanager#1
|
jpomgrsub#1
|
Event/action control submanager process
|
|
ajsmasterd
|
ajslogd#3
|
Process for recording scheduler information
|
|
ajsschd#3
|
Schedule control process
|
|
ajsschbd#3, #4
|
Generation management subprocess
|
|
ajsflowd#3
|
Flow control process
|
|
ajssubd#3
|
Job submit process
|
|
ajssubwd#3
|
Job completion wait process
|
|
jpqnfyfd#1
|
Process for reporting the job execution control status
|
|
ajsremnetcl#3
|
Process for requesting the registration and the cancellation of registration of remote jobnets
|
|
ajsreqd#3
|
Queueless job request process.
A maximum of eight process instances start from ajsflowd.
|
|
jpqmon#1
|
jpqagt#1
|
Job execution control agent process.
This process starts a job.
|
|
jpqagtdmn#1
|
Process for starting the process that monitors the job execution control job.
This process starts a job monitoring process. Five instances of this process are always active. In a cluster system, five
processes are active on each logical host.
|
|
jpqagtchild#1
|
Process for monitoring a job execution control job.
This process monitors the execution of a job process. Initially, five instances of this process are active. In addition to
these five instances, one instance starts for each executed job. In a cluster system, five instances are active on each logical
host.
|
|
jpoagent#1
|
jpoagtsub#1
|
Event/action control subagent process.
This process mainly reports the information from monitoring processes to the manager.
|
|
jpocwtflMain#1
|
File monitoring process
|
|
jpocwttmMain#1
|
Execution interval control process
|
|
jpoeventwatch#1
|
Event (such as JP1 events and log traps) monitoring process
|
|
jpoevsearch#1
|
Event search process.
This process starts and searches for events when the event reception monitoring job specified with pre-execution event search
is executed.
|
|
jpocwtmlmain#1
|
Email monitoring communication process
|
- Note
-
When you execute a command, a process with the command name starts.
- #1
-
A process name for a logical host is indicated as process-name logical-host-name. For example, when the logical host name is hostA, the ajsmasterd process for hostA is ajsmasterd hostA.
- #2
-
One process starts for the selected scheduler service when you select a scheduler service in the tree area in a JP1/AJS3 -
View window.
The maximum number of processes that can start is number-of-scheduler-services x number-of-connected-instances-of-JP1/AJS3 - View.
- #3
-
You can differentiate between a process for a physical host and a process for a logical host. A process name for a logical
host is indicated as process-name_logical-host-name.
For example, when the logical host name is hostA, the ajsschd process for hostA is ajsschd_hostA.
- #4
-
This process starts only when you specify the environment settings as described in 15.1.6 Changing the mode in which unregistration or generation management deletes the generations of a jobnet in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1.
To Page Top
(2) Processes of JP1/AJS3 - Agent for UNIX
There are three kinds of processes of JP1/AJS3 - Agent for UNIX:
You can use the jajs_spmd_status command to check the status of the child processes of jajs_spmd. For details, see the description of jajs_spmd_status in the manual Job Management Partner 1/Automatic Job Management System 3 Command Reference 1.
To check the status of parent, child and detail processes, use the ps command.
Table B-17 lists the parent and child processes. Table B-18 lists the child and detail processes. The number following a parent or child process name indicates the maximum number of
processes you can activate concurrently.
Table B‒17: Parent and child processes of JP1/AJS3 - Agent for UNIX
|
Parent process
(number of processes)
|
Description
|
Child process
(number of processes)
|
Description
|
|
jajs_spmd (1)#
|
JP1/AJS3 service
|
jpoagent (1)
|
Event/action control agent process
|
|
jpqmon (1)
|
Job execution control
This process monitors all processes for job execution control.
|
|
ajsqlagtd (1)
|
JP1/AJS3 Queueless Agent service (queueless agent process)
JP1/AJS3 - Manager
This process accepts queueless job execution requests from JP1/AJS3 - Manager (scheduler service).
|
ajsqlagtd
(number-of-jobs-to-be-executed)
|
Queueless job management process
This process executes queueless jobs.
The same process names are generated from the JP1/AJS3 Queueless Agent service (queueless agent process) respectively for
jobs to be executed.
The process is removed on completion of queueless job execution.
The process has no detail process.
|
|
ajschkagtd (1)
|
JP1/AJS3 Check Agent service
|
ajschkagtd (5)
|
This process controls the definition pre-check (agent process).
|
- #
-
By specifying logical host names on the command line, you can differentiate between processes for physical hosts and for logical
hosts.
A process for a logical host is represented as process-name -h logical-host-name. For example, when a logical host name is hostA, the jajs_spmd process for hostA is represented as jajs_spmd -h hostA.
Table B‒18: Child and detail processes of JP1/AJS3 - Agent for UNIX
|
Child process name
|
Detail process name
|
Description
|
|
jpoagent#
|
jpoagtsub#
|
Event/action control subagent process
This process mainly notifies the manager of information from the monitoring process.
|
|
jpocwtflMain#
|
File monitoring process
|
|
jpocwttmMain#
|
Execution interval control process
|
|
jpocwtmlmain#
|
Mail monitoring communication process
|
|
jpoeventwatch#
|
Event (such as JP1 event or log trap) monitoring process
|
|
jpoevseach#
|
Event search process.
This process starts to search for the specified event when a JP1 event reception monitoring job specified with a pre-execution
event search is executed.
|
|
jpqmon#
|
jpqagt#
|
Agent process for job execution control
This process activates jobs.
|
|
jpqagtdmn#
|
Job monitoring process activating process for job execution control
Process for activating the job monitoring process
Five processes are always activated. In a cluster system, five processes are activated for each logical host.
|
|
jpqagtchild#
|
Job monitoring process for job execution control
Process for monitoring job process execution
Five processes are activated in the initial status. Also, one process is activated for each execution job. In a cluster system,
five processes are activated for each logical host.
|
- Note
-
When you execute a command, a process with the same name as the command is activated.
- #
-
You can differentiate between processes for physical hosts and for logical hosts.
A process for a logical host is represented as process-name logical-host-name.
For example, when a logical host name is hostA, the jpoagent process for hostA is represented as jpoagent hostA.
To Page Top
(3) Processes of JP1/AJS3 Console Manager for UNIX
To check the processes of JP1/AJS3 Console Manager for UNIX, use the ps command.
JP1/AJS3 Console Manager consists of the following three types of processes:
Table B-19 lists the parent and child processes of JP1/AJS3 Console Manager for UNIX. Table B-20 lists the child and detail processes. The number following a parent or child process name indicates the maximum number of
processes you can activate concurrently.
Table B‒19: Parent and child processes of JP1/AJS3 Console Manager for UNIX
|
Parent process
(number of processes)
|
Description
|
Child process
(number of processes)
|
Description
|
|
ajscminetd (1)#1
|
JP1/AJS3 Console Manager service
|
ajscmmonsvr
(Number in logged-in JP1/AJS3 Console Views)#2
|
This process communicates with JP1/AJS3 Console View.
|
- #1
-
The process starts when the JP1/AJS3 Console Manager service starts. The process ends when the JP1/AJS3 Console Manager service
stops.
- #2
-
The process starts when the user logs in to JP1/AJS3 Console View. The process ends when the user logs out from JP1/AJS3 Console
View.
Table B‒20: Child and detail processes of JP1/AJS3 Console Manager for UNIX
|
Child process
|
Detail process
|
Description
|
|
ajscmmonsvr
|
ajscmstatd#
|
This process communicates with JP1/AJS3 Console Agent.
|
- Note
-
When you execute a command, a process with the same name as the command is activated.
- #
-
The process starts when the user logs in to JP1/AJS3 Console View. The process ends when the user logs out from JP1/AJS3 Console
View.
To Page Top
(4) Processes of JP1/AJS3 Console Agent for UNIX
To check the processes of JP1/AJS3 Console Agent for UNIX, use the ps command.
JP1/AJS3 Console Agent consists of the following three types of processes:
Table B-21 lists the parent and child processes of JP1/AJS3 Console Agent for UNIX. Table B-22 lists the child and detail processes. The number following a parent or child process name indicates the maximum number of
processes you can activate concurrently.
Table B‒21: Parent and child processes of JP1/AJS3 Console Agent for UNIX
|
Parent process
(number of processes)
|
Description
|
Child process
(number of processes)
|
Description
|
|
ajscainetd (1)#1
|
JP1/AJS3 Console Agent service
|
ajscagtd
(Number of agents monitored by using JP1/AJS3 Console View)#2
|
This process communicates with JP1/AJS3 Console Manager.
|
- #1
-
The process starts when the JP1/AJS3 Console Agent service starts. The process ends when the JP1/AJS3 Console Agent service
stops.
- #2
-
The process starts when the user logs in to JP1/AJS3 Console View. The process ends when the user logs out from JP1/AJS3 Console
View.
Table B‒22: Child and detail processes of JP1/AJS3 Console Agent for UNIX
|
Child process
|
Detail process
|
Description
|
|
ajscagtd
|
ajscastatd#1
|
This process acquires the status of JP1/AJS3 work tasks.
|
|
ajscagtd
|
ajscaexecd#2
|
This process manipulates the objects of JP1/AJS3.
|
- Note
-
When you execute a command, a process with the same name as the command is activated.
- #1
-
The process starts when the specified monitoring start time is reached or a refresh is executed. The process ends when the
acquisition of information is completed.
- #2
-
The process starts when the user attempts to manipulate a JP1/AJS3 object. The process ends when the user completes the manipulation
of the JP1/AJS3 object.
To Page Top
