on 08-04-2016 7:49 PM
hello everyone,
I am describing an interesting phenomenon that i found in customer system.
in SM66 a DIA wp went into PRIV mode and has a long runtime( 24359s). and when i check SM04 the user cause the wp into PRIV is actually not logon anymore. So normally when user session is broken, the related program is ended and wp should be restart automatically. But in this case the wp seems like hanging there and doing nothing. attached the details info in below link.
https://mdocs.sap.com/mcm/public/v1/open?shr=DuSkAeniEyHUlTcpHO7w2IP-scj2W6ggzd6f0-byNPM
https://mdocs.sap.com/mcm/public/v1/open?shr=DuSkAeniEyHUlTcpHO7w2IP-scj2W6ggzd6f0-byNPM
https://mdocs.sap.com/mcm/public/v1/open?shr=DuSkAeniEyHUlTcpHO7w2IP-scj2W6ggzd6f0-byNPM
Does anyone have any idea about this?
thanks,
Minas.
Hello Minas,
SM04 is an instance specific transaction.
Thus, you need to be logged on to the same instance that the user is logged on (or switch to it using SM51).
You could also use AL08 (which is similar to a "system-wide SM04").
The "connection to terminal lost" entries highlighted at the SM21 screenshots are from a different instance, not from the instance where the work process was "stopped / PRIV".
The PDF file at the SAP Document Center link does not show enough evidence to confirm that the work process was "stopped / PRIV" while the user had already logged off.
Best regards,
Isaías
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
85 | |
10 | |
10 | |
9 | |
7 | |
6 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.