The content described here is for the following:
Windows versions: V11.0L10 or later
Solaris versions: 11.0 or later
Linux versions: V11.0L10 or later
Linux for Itanium versions: V12.0L10 or later
HP-UX versions: 11.0 or later
AIX versions: 11.0 or later
To check the process running status, execute the following command on the server for which you want to check the process running status:
[Windows versions]
<systemwalker install directory>\mpwalker.jm\bin\mppviewo[UNIX versions]
/opt/systemwalker/bin/mppviewo
The following type of execution result is displayed:
###################### PROCESS INFORMATION BEGIN ###################### ** <package name> ** <monitored process name> PID RUNNING-TIME ####################### PROCESS INFORMATION END #######################
The PID and RUNNING-TIME explanations are shown below.
Process ID for the process
Accumulated execution time for the process
Example of the execution in Windows versions
The example below shows the execution of the command that displays the process running status on the Operation Management Server. The following example shows that the process "mjsoba.exe" is abnormal.
###################### PROCESS INFORMATION BEIN ####################
** Service Name **
PROCESS-NAME PID
** Systemwalker ACL Manager **
f3crssvr.exe 2332
** Systemwalker MpJmCal **
f3crhcs1.exe 2456
f3crhcs2.exe 2458
** Systemwalker MpNjsosv **
CNSSVENG.EXE 2468
** Systemwalker MpAosfB **
f3crhesv.exe 2488
f3crhdsv.exe 2489
f3crhxsv.exe 2522
** Systemwalker MpAosfP **
f3crhsv2.exe 2562
** Systemwalker MpAosfX **
f3crhxsw.exe 2564
** Systemwalker MpMpMjes **
mjssvc.exe 2568
mjsoba.exe 2572
** Systemwalker MpMpMjes1 **
mjssvc.exe 2545
>>>>> ERROR:Process Not Found : mjsoba.exe
** Systemwalker MpMpMjes2 **
mjssvc.exe 2634
mjsoba.exe 2642
:
:
###################### PROCESS INFORMATION END #######################Example of the execution in Solaris versions
The example below shows the execution of the command that displays the process running status on the Operation Management Server. The following example shows that the process "mjsdaemon -sys 1" is abnormal.
####################### PROCESS INFORMATION BIGIN###################### ** Package Name ** PROCESS-NAME PID RUNNING-TIME ** FJSVfwseo ** MpFwsec 2345 0:19 ** FJSVjmcal ** f3crhcs2 2241 0:18 ** FJSVJMCMN ** jmnetsv 2245 0:15 mpjmsrv 2265 0:17 ** FJSVJOBSC ** [Subsystem0] tskmnsrv 2745 0:14 [Subsystem1] tskmnsrv 2749 0:12 [Subsystem2] tskmnsrv 2751 0:09 ** FJSVMJS ** [Subsystem0] mjsdaemon -sys 0 2821 0:21 mjsdaemon -sys 0 2822 0:20 mjsdaemon -sys 0 2823 0:19 mjsnetsv 0 2825 0:18 [Subsystem1] mjsdaemon -sys 1 2921 0:20 mjsdaemon -sys 1 2923 0:19 >>>>> ERROR:Process NOT Found : mjsdaemon -sys 1 mjsnetsv 0 2925 0:17 [Subsystem2] mjsdaemon -sys 2 3024 0:15 mjsdaemon -sys 2 3025 0:14 mjsdaemon -sys 2 3026 0:14 mjsnetsv 0 3016 0:12 : ####################### PROCESS INFORMATION END ######################
Information
Running status for process monitoring
To check the running status of the process monitoring function, use the following to check if the service or process has started. Refer to "B.2 Process Names" for information on the service or process names.
Windows: Windows Task Manager, Windows Services, or some other tool.
UNIX: The ps command, or some other command.
Additionally, if the process monitoring function coexists with Systemwalker Centric Manager, operation monitoring of the Application Monitoring function can also be used. To enable monitoring of the number of processes, it will be necessary to set a lower limit of 1, and no upper limit.