Job Management Partner 1/Software Distribution Description and Planning Guide

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

Appendix A.2 Processes of JP1/Software Distribution Client

The tables below list the processes that are made resident when JP1/Software Distribution Client is used.

Organization of this subsection
(1) Relay system processes
(2) Client processes

(1) Relay system processes

The table below lists the processes that are made resident when JP1/Software Distribution Client (relay system) is used. The parentheses following a process name enclose the number of instances of the process that can be executed concurrently.

Table A-2 Processes of JP1/Software Distribution Client (relay system)

Process name Function Supported OS Conditions for making the process resident
schserv(1) Process for monitoring scheduled jobs All OSs supported by the product Always resident
srvmain(1) Process for managing all jobs and inventories All OSs supported by the product Always resident
dmpsite(1) Process for the relay system facility All OSs supported by the product Always resident
dmpwtcp(1) Process for receiving startup requests All OSs supported by the product Always resident
dmpicron(1) Process for scheduling All OSs supported by the product Always resident
dmpserv(1) Main process started automatically from a service All OSs supported by the product Always resident
dmpsetup(1) Process for GUI installation All OSs supported by the product The user who installed JP1/Software Distribution Client (relay system) has logged on.
dmpusers(1) Process for extending the functions that are available when Package Setup Manager is used with non-Administrator user permissions All OSs supported by the product Run the client with non-Administrator user permissions was selected during setup.
alertsrv(1) Process for starting system monitoring automatically All OSs supported by the product Monitor the system was selected during setup.

(2) Client processes

The table below lists the processes that are made resident when JP1/Software Distribution Client (client) is used. The parentheses following a process name enclose the number of instances of the process that can be executed concurrently.

Table A-3 Processes of JP1/Software Distribution Client JP1/Software Distribution Client (client)

Process name Function Supported OS Conditions for making the process resident
dmpwtcp(1) Process for receiving start requests All OSs supported by the product Client starts automatically at system boot is selected during setup.
dmpicron(1) Process for scheduling All OSs supported by the product Client starts automatically at system boot is selected during setup.
dmpserv(1) Main process started automatically from a service
  • Windows 8
  • Windows Server 2012
  • Windows 7
  • Windows Server 2008
  • Windows Vista
  • Windows Server 2003
  • Windows XP
  • Windows 2000
  • Windows NT 4.0
Client starts automatically at system boot is selected during setup.
dmpstrup(1) Main process started automatically
  • Windows Me
  • Windows 98
Client starts automatically at system boot is selected during setup.
dmpsetup(1) Process for GUI installation
  • Windows Server 2003
  • Windows XP
  • Windows 2000
  • Windows NT 4.0
Either of the following condition combinations are met:
Condition combination 1 (all conditions are met):
  • Client starts automatically at system boot is selected during setup.
  • Run the client with non-Administrator user permissions is not selected during setup.
  • The user who installed JP1/Software Distribution Client has logged on.

Condition combination 2 (all conditions are met):
  • Client starts automatically at system boot is selected during setup.
  • Run the client with non-Administrator user permissions is selected during setup.
  • A user with Administrator permissions has logged on.
dmpusers(1) Process for extending the facilities available to non-Administrator user permissions when using Package Setup Manager or the Execute Job Backlog icon
  • Windows 8
  • Windows Server 2012
  • Windows 7
  • Windows Server 2008
  • Windows Vista
  • Windows Server 2003
  • Windows XP
  • Windows 2000
  • Windows NT 4.0
The process is made resident if either of the following condition combinations are met:
Condition combination 1 (all conditions are met):
  • Client starts automatically at system boot is selected during setup.
  • Run the client with non-Administrator user permissions is selected during setup.

Condition combination 2 (all conditions are met):
  • Client starts automatically at system boot is not selected during setup.
  • Run the client with non-Administrator user permissions is selected during setup.
  • Use the Package Setup Manager or Execute Job Backlog command when a client is not resident is selected during setup.
alertsrv(1) Process for starting system monitoring automatically
  • Windows 8
  • Windows Server 2012
  • Windows 7
  • Windows Server 2008
  • Windows Vista
  • Windows Server 2003
  • Windows XP
  • Windows 2000
  • Windows NT 4.0
Both of the following conditions are met:
  • Client starts automatically at system boot is selected during setup.
  • Monitor the system is selected during setup.
artsrv9x(1) Process for starting system monitoring automatically
  • Windows Me
  • Windows 98
Both of the following conditions are met:
  • Client starts automatically at system boot is selected during setup.
  • Monitor the system is selected during setup.