T24 : Locking Globus for Users

[yohan]

Hi

Is there any command to lock the globus for user and allow only one
user to login to globus (Ex : Like starting EOD in globus without
letting any to interfere)


Regards
Yohan

[uiterwyk]

If you are running on jBase 5.1 you can set up two "databases" which
are really the same one. One for all users and one for just EOD

Then when EOD starts, you can do a DB-PAUSE on the user database.
Then EOD can use its own private database to run and do a DB-RESUME
on the user database at the end.

There are some other considerations when using anything but the
"default" database, so be sure you get the assistance of your jBase
Consultant/Administrator.

HTH

Robert

[concern shoko]

Hi Yohan,

i am on Universe and i run a script that automatically creates a file
"globus.locked" in bnk.run. i then edited my users' .profile to check
for the existence of this file. if it exits then it will deny user
from proceeding. i am sure you can do almost the same on jBASE.

Regards
Concern
+263912271566

--
C. Shoko
Temenos GLOBUS Developer
|Systems Analyst|MBCA Bank |Harare |Zimbabwe |+263 912 271 566 |

[K. Ouassa]

Hi,
Can you afford stop Telnet service? or put unix in single mode?

OUASSA K.

> Date: Thu, 9 Oct 2008 14:05:04 -0700
> Subject: T24 : Locking Globus for Users
> From: kady...@gmail.com
> To: jB...@googlegroups.com

[Simon Verona]

I have noted over a period of time that on system crashes (power cuts etc) we normally have a couple of files that are corrupted.

 

I want to be able to prevent this...

 

I’m looking into ways of ensuring that the file integrity for these files is always complete so that they are not corrupted, whilst minimizing the performance hit on the system...

 

There seem to be a couple of methods that I could use (I think) :-

 

1.       Change the files in question to J3 format with the SECURE flag set to yes.

2.       Surround the updates to these files within a transaction (I’m not sure of the exact syntax but I think this forces a disk write?).

 

Are there any other methods I should be considering ? 

 

What would be the best methodology ?

 

This is on jBASE 3.4 running on Windows server 2003.

 

Regards

Simon

 

 

 

 

 

[Jim Idle]

On Fri, 2008-10-10 at 22:10 +0100, Simon Verona wrote:

I have noted over a period of time that on system crashes (power cuts etc) we normally have a couple of files that are corrupted.

 

I want to be able to prevent this...

 

I’m looking into ways of ensuring that the file integrity for these files is always complete so that they are not corrupted, whilst minimizing the performance hit on the system...

 

There seem to be a couple of methods that I could use (I think) :-

 

1.      Change the files in question to J3 format with the SECURE flag set to yes.

This works, but the most secure is quite a performance hit as it syncs to disk on each write. J3 Secure files are your only option really. You don't need the most secure level if you are only really interested in preventing corruption rather than worried about losing data.

2.      Surround the updates to these files within a transaction (I’m not sure of the exact syntax but I think this forces a disk write?).

Won't really help you - you could crash while in the process of sync writing the transaction to disk, in which case only J3 secure will help you.

 

Are there any other methods I should be considering ? 

Some day in the not too distant future, I will be releasing a new file system that does not suffer any of these problems and is a lot faster than the current file systems. I'll put you on the beta testing list.

[Simon Verona]

Jim

 

Thanks for the reply, I suspected that j3 secure was the way to go...

 

So just to confirm...   I need the runtime environment variable setting  JEDI_SECURE_LEVEL=2 and then convert the file to j3 Secure using the statements :

 

Ø  Jrf  filename –H3

Ø  Jchmod +S filename

 

Is this correct ?

 

Simon

[Thiag Jayachandran]

Hi

 

in T24 USER application there is a field called SIGN.ON.ITEM, you can attach a routine in this field to check whether EOD is running or not and throw the users out

 

This routine will be triggered when the users login

 

regards

Thiag

[Tec Murho]

Hi Jai

Can you give me the example of that routine if possible

bes t regards