Hi,

I have observed that some my Clients, if got irritated with the time taken by some session they using the "start bshell" option in the "option diaglog" and kill the session forcefully.

Can anyone explain me the impact of doing this. Secondly can I disable the feature of start bshell in the option dialog screen.

regards
Sudha

Hi Sudha,

killing a running session with the described method has roughly the same effect as closing a form by cklicking the right hand "x" of Windows. This will only stop this object, not the whole bshell.

You can stop users by calling this shell by taking the authorizations for this object away. I think it is: ottstpshell

By the way, do not confuse this with a proper Unix shell, which would be the object ottstpvtemul.

Reagrds

Markus

Hello,
When the session is forcefully terminated, there is a possibility that the session is still taking the resources at the backend!!
I think it can be disabled by ottstpshell, but I am not sure.

Time being I have removed the User authorization for the session ttstpshell.
Now its Ok, the user not able to start the shell

regards
Sudha

You might consider training them to kill there own processes as follows;

On Option dialog screen ;

start shell
enter ps (displays all users Unix processed)
enter kill "pid number" (of session, report etc).
enter exit (returns to option dialog screen)

Warning: Use for 'Intelligent' users only

What exactly happens depends on what sort of system you are running and what you are running it on, but as a rule of thumb it is not advisable to allow users to exit this way.

Don't compare it to 'x-ing' out of a windows program, compare it to 'ctrl-alt-del-ing' out of a windows program. It is messy and might leave all kinds of debris behind that potentially will affect your system performance.