on 08-13-2009 10:08 AM
Hi Everyone, I am going to ask BASIC thing but effective one I feel.
I felt below blog is soo useful
/people/matt.kangas/blog/2009/03/03/sap-netweaver-executables
this lists all kernal files and usage.
at the same time I am curious to know the how to use(syntax) of non-common kernel files . Specially for Java related(Except Jcmon,jcontrol,jlaunch) and few others.I know many of these kernel files were used by SAP internally to serve for diff purposes.But still we can use few for administrative reasons.My request is if any one used any non-common kernal file for troubleshooting or analyzing any scenario then I would request to reply back with usage in practical of that kernal file.
Please note - please dont reply for common executable's usage.(say dpmon,saposcol,stopsap ,startsap,jcmon,cleanipcdisp+work,sappfpar,saproot.sh,sapwebdisp,sapevt,saplicense,SAPCAR,tp,r3trans ).Already we have many threads to serve for these common executable related posts.
Thank you.
Edited by: Juan Reyes on Aug 13, 2009 10:18 AM
HI Srikanth,
First thankyou very much for giving such a wonderful knowledge resource .
Answer:
all executables have fixed to run ... lets cosider JCMON.
In standalone java system or WAS abap+JAVA we check status of java isntance using JCMON.on os level Same syntax like
JCMON pf = <istance profile of java >. same like DPMON.
try this:
<sapexe> - help
..it will give u the syntax of how to use particular exe.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Arun,
that is fine we can get standard help but I need more of in what scenarios other filess can be used.I feel like SAP kernal is a strong tool to analyze all sort of problems but we just use these kernal files in few scenarios.
Hope you got my point.
I will give you an example here :-
Scenario:-
User is complaining that his/her SAP GUI session is logging off on its own quite frequently:-
In this case first we have to check sapworkdir in his/her PC(for error log.gui file) for errors and if still we are unable to find the root cause then NIPING can be usable(Note 21559)
we can use NIPING to trouble shoot many issues. with below command
niping -c -H <hostname> -B 10 -D "<few flags****> -V 2 -T "C:\test\test2ping.trc"
above command can be clearly explained in note number - 21599
Thank you.
I need this type of scenarios.
Any ways thanks for the reply.
User | Count |
---|---|
71 | |
26 | |
10 | |
9 | |
7 | |
6 | |
4 | |
4 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.