Hi everyone:
Does any know a solution or procedure to disable the famous "output to console" option?
This is due to some users used to kill a determined session, but the problem is, they are doing this on update sesion! So this is causing a lot of problems due to unifinished transactions!

Thank you in advance!

Here's an instance where the best solution isn't programatic..

Slap the users. =)

Dave

Hi Dave,
I agree with you. The problem is that, somewhere in the time, someone teched that vicious to the users. Now, that vicious has been multiplied.

In order to slap the users, there is a way to know when a user do this?
Is there any way to recognize when a kill session was done by this way or when a session goes out due to a LAN problem?

Thank you in advance.

You know, Baan should catch that the bshell terminated and roll back the transation. You shouldn't be left with a partial transation (depending on what you're talking about)

Output to Console is actually an ok way to kill your bshell cleanly.

it's not a session though, it's part of the BW so there's no way to disable it that I know of.

Dave

Hi Dave,
The problem is that, when I talk with SSA Global, to ask why the balance is not ok, they were tell us, again and again, that is a problem with desconections or "output to console" procedure!

If output to console, is a clean way to kill a session, why they are arguing this?

In order to discard all the posibilities to solve this problem, in first term, we aspire to discard this option as a cause to not have our balances ok.

If you have any idea, I will appreciate that.
Thank you.

I don't buy that. Any disconnect will roll back the transaction - unless the session is written in a 2 commit process. (i.e., I commit to table A then table B) at which point you would have to be consistantly dropping the connection RIGHT at that moment.

Plus I can't think of any session written like that.

What do you/they do to fix your out of balance problem? is there a session? or do they use GTM?

Dave

Hi Dave,
When tha accountants detect an error in the balance, they ask us to run the session tfgld3203m00 (rebuild opening balance/history from transactions).

Thank you.

Bug in the program..

Hard part is trying to determine which program.

Dave

Yeah, I agree with you. There must be a bug in some program.
So I will keep searching a solution and when I find it I will post it in the board.

Thank you again.

Hi Dave,
I agree with you. The problem is that, somewhere in the time, someone teched that vicious to the users. Now, that vicious has been multiplied.

In order to slap the users, there is a way to know when a user do this?
Is there any way to recognize when a kill session was done by this way or when a session goes out due to a LAN problem?

Thank you in advance.


Hi

These kind of problems are not limited to LAN, these may occurs because of database error or long processing period of session. So you should tune your database along with network to sort out these problem.