Alternative to senstive t-codes

[Former Member]

Hello everyone,

i need to pick your brains please.

I need alternative t-codes to the following:

SM50

SM51

SE37

SM12

If no alternatives, can you please explain what the risk is with them?

many thanks

[Former Member]

there is no alternative for this & following are the risk .

SM50 : WP can be cancelled/stop,

SM51 : same as SM50 but more as you can remote login to the servers, can get logged in users list

SE37: can schedule/delete/cancel the background job

SM12: user may delete SAP lock entries

Cheers,

-Sunil

[Former Member]

Thank you for your answer Sunil!

Please allow me to re--phrase my question.

What are the best t-codes to do the following things? I have put in brackets the ones that are being used currently to do these tasks)

1. Monitoring of the live system processes and system usage (SM50)

2. Connection to check access to application servers (SM51)

3. testing of IGS, IPC, etc (SE37)

4. lock maintenance (SM12)

thank you very much in advance for your help

Best

[Former Member]

for testing the IPC you can check whether IPC is connected or not using tcode SMGW you can find connected IPC process. for IGS refer link http://help.sap.com/saphelp_erp2005vp/helpdata/en/69/a6d43ac66e1f08e10000000a114084/content.htm

In sm37 you checks for bacground jobs.

other than this everything is correct.

Cheers,

-Sunil

[matthias_gemmel]

Hi,

an addition to the post of Sunil regarding the IGS monitoring: if you are not interested in a permanent but in a single monitoring of the IGS you can only use the information "call transaction se38 and execute the program graphics_igs_admin" of the provided link.

Note <a href="http://service.sap.com/sap/support/notes/995471">995471</a> gives more information about this report.

Regards

Matthias