Friday, 25 July 2014

OS utilities - SAPPFPAR



OK, this one is really short (mainly I forgot to publish it 3 weeks back :-/ )

"The program sappfpar lets you check the minimum and maximum (worst case) swap space requirements for an SAP application server. It also checks the shared memory requirements and whether or not the parameters em/initial_size_MB and abap/heap_area_total are set correctly." (cite from SAP pages itself)
You will find it in this path:
/usr/sap/<SID>/SYS/exe/run

and those are some simple usage you could use these commands:
sappfpar check pf=<path_to_instance_profile> - to check given profile for errors and evaluate it
sappfpar check pf=<path_to_instance_profile> <parameter_name> - to show parameter value

I don't know what more to write. I nearly did not used it, but yes, it can be handy if you need to check, why is your SAP crashing or during some installations or upgrades.

If you want, you can read this and something little more on original page:
http://help.sap.com/saphelp_nw70/helpdata/en/66/380fb7d43d11d188bd0000e83539c3/content.htm

Friday, 18 July 2014

OS utilities - SAPOSCOL / SAPHOSTEXEC / SAPHOSTAGENT

So today just quick look on two not so needed utilities (I'm party joking now).
SAPOSCOL and SAPHOSTEXEC are utilities for collecting of OS information and relaying that info to SAP application (in case of SAPHOSTEXEC not only this). 


Lets start with SAPOSCOL at it's older. You can find this application in path:
/usr/sap/hostctrl/exe/saposcol

As it was told, app is used to relay information about OS to SAP and there is always one running SAPOSCOL per SAP instance and SAPOSCOL is independent on SAP program (and vice versa)´. All colected data are sent to SAP through share memory, where on SAP is running job SAP_COLLECTOR_FOR_PERFORMANCE (every 24 hours) which writes this data to MONI DB. SAPOSCOL program have several parameters (like -o for showing collected data), witch u can use for his administration.


From SAP NetWeaver components as of release 7.0 EhP2 there should be program SAPHOSTEXEC. It's used for control of SAPHOSTAGENT and also for control of SAPOSCOL program. You can found his executables in:
/usr/sap/hostcontrol/exe/saphostexec

What SAPOSCOL is doing we already know, so what is this SAPHOSTAGENT good for? From SAP kernel 7.20 is this application installed on system to discover and monitor SAP instance, monitor OS through SAPOSCOL and to monitor and manage database on host. There are several other function like instance provisioning.
SAPHOSTAGENT is controled through SAPHOSTEXEC program/commands.


you can found full info on addresses:
SAPOSCOL:
https://help.sap.com/saphelp_nw04/helpdata/en/c4/3a6bff505211d189550000e829fbbd/content.htm
SAPHOSTEXEC:
https://help.sap.com/saphelp_nw73ehp1/helpdata/en/f5/6737c5de81497590d2fbb4fa055dd6/content.htm
SAPHOSTAGENT:
http://help.sap.com/saphelp_nw73ehp1/helpdata/en/48/c6f9627a004da5e10000000a421937/frameset.htm

Sunday, 13 July 2014

OS utilities - DPMON / JSMON / JCMON

So for today, we will encounter a few similar tools for OS checking and administration of ABAP and Java part of SAP. Lets start with DPMON.
DPMON is "Dispatcher monitor" This tool is similar to transactions DSM50 or SM66 and it is used for monitoring and some basic task on your ABAP work processess. It is not much, but can be handy in case you are not able to access system via SAPGUI, but you do not want to shut it down (or you have closed ports or whatever).

DPMON is using menu structure with text screens, where you have to go through choices to get to desired function. You can see load statistic, queues or even kill WP.

This tool can be usually found in path:
usr\sap\<SID>\SYS\exe\run

and is used by command:
dpmon pf=<path_to_instance_profile>


When you need to check your Java stack, you have 2 tools now - JCMON and newer JSMON. Both tools are quite similar to DPMON. If you have AS Java older than 7.1 you will have only JCMON on your system.
Both can be found in path:
/usr/sap/<SID>/DVEBMGS<#no>/exe

and are ussualy started by commands:
jcmon pf=<path_to_instance_profile>
jsmon pf=<path_to_instance_profile>
(where <path_to_instance_profile> is path to your DVEBMGS<#no> profile)

Like DPMON, JCMON is using text screens and list for choice of next step / menu. But these menus are numbered with unique numbers, so if you know proper number, you can switch between menus, even if you cannot see number in list. (so you can type any time 20 to see process list)

JSMON is simmilar to JCMON, but it is using color version of "text screens" and instead of numbers, it is using internal commands (like process, display port or help command)