FourJs and IDS sessions lock

Hi Is there a mechanism either via SQL scripting or anything else which can be used to identify the user who are really idle from do data manipulation or processing. For example : UserA activate a program call customer. By doing that he/she will get the program menu and the form. Then he/she leave it the screen open from the morning till the evening without doing anything. By looking in onstat -g ses, one session already being created. Since the applcation using FourJs, it already locked one session of FourJs(this effected the number of FourJs license used). One of our client writing the script by looking at OS point of view in term of idling to kill the user. By that, the FourJs and the Informix session not clearly release and it lock other user who really want to access the program. Can somebody give some clue to rectify this. Thanks

Probably when UserA activates a program, he/she enters a loop like MENU or a dialog like an INPUT (or DISPLAY ARRAY, etc) statement. If you are using FourJ's GENERO look at the [ ON IDLE n ] statement you can use inside a MENU or INPUT, for example ON IDLE 60 CALL MyExitProgramFunc() -----Original Message----- From: SYED AHMAD .... [mailto:najmi@centurysoftware.com.my] Sent: ?a?as?e??, 18 Fe????a???? 2005 3:58 pµ To: ids@iiug.org Subject: FourJs and IDS sessions lock [4294] Hi Is there a mechanism either via SQL scripting or anything else which can be used to identify the user who are really idle from do data manipulation or processing. For example : UserA activate a program call customer. By doing that he/she will get the program menu and the form. Then he/she leave it the screen open from the morning till the evening without doing anything. By looking in onstat -g ses, one session already being created. Since the applcation using FourJs, it already locked one session of FourJs(this effected the number of FourJs license used). One of our client writing the script by looking at OS point of view in term of idling to kill the user. By that, the FourJs and the Informix session not clearly release and it lock other user who really want to access the program. Can somebody give some clue to rectify this. Thanks -- No virus found in this incoming message. Checked by AVG Anti-Virus. Version: 7.0.300 / Virus Database: 265.8.8 - Release Date: 14/2/2005

Check for onstat several times to detect changes. For example onstat -u show you read and writes, that in combination to OS idle time may tell you if the user is doing something or not. This way you better decide to kill or not a session. J. -----Original Message----- From: "SYED AHMAD ...." <najmi@centurysoftware.com.my> To: ids@iiug.org Date: Thu, 17 Feb 2005 20:58:17 -0500 (EST) Subject: FourJs and IDS sessions lock [4294] Hi Is there a mechanism either via SQL scripting or anything else which can be used to identify the user who are really idle from do data manipulation or processing. For example : UserA activate a program call customer. By doing that he/she will get the program menu and the form. Then he/she leave it the screen open from the morning till the evening without doing anything. By looking in onstat -g ses, one session already being created. Since the applcation using FourJs, it already locked one session of FourJs(this effected the number of FourJs license used). One of our client writing the script by looking at OS point of view in term of idling to kill the user. By that, the FourJs and the Informix session not clearly release and it lock other user who really want to access the program. Can somebody give some clue to rectify this. Thanks Jean Sagi jeansagi@myrealbox.com jeansagi@yahoo.com

Has anyone modified the kill idle script to do this? -----Original Message----- From: Jean Sagi [mailto:jeansagi@myrealbox.com] Sent: Friday, February 18, 2005 9:03 AM To: ids@iiug.org Subject: Re: FourJs and IDS sessions lock [4298] Check for onstat several times to detect changes. For example onstat -u show you read and writes, that in combination to OS idle time may tell you if the user is doing something or not. This way you better decide to kill or not a session. J. -----Original Message----- From: "SYED AHMAD ...." <najmi@centurysoftware.com.my> To: ids@iiug.org Date: Thu, 17 Feb 2005 20:58:17 -0500 (EST) Subject: FourJs and IDS sessions lock [4294] Hi Is there a mechanism either via SQL scripting or anything else which can be used to identify the user who are really idle from do data manipulation or processing. For example : UserA activate a program call customer. By doing that he/she will get the program menu and the form. Then he/she leave it the screen open from the morning till the evening without doing anything. By looking in onstat -g ses, one session already being created. Since the applcation using FourJs, it already locked one session of FourJs(this effected the number of FourJs license used). One of our client writing the script by looking at OS point of view in term of idling to kill the user. By that, the FourJs and the Informix session not clearly release and it lock other user who really want to access the program. Can somebody give some clue to rectify this. Thanks Jean Sagi jeansagi@myrealbox.com jeansagi@yahoo.com

That's what we do here. I don't have enough skilled operators to run 24x7, so I (and the Sr. SysAdmin) wrote a script to identify and analyze things. We identify OS properties (who -u and finger info, commands being executed, and 4gl/4ge processes that may be active), and then isolate their terminal session against the onstat -g information to determine if they are running SQLs (few users allowed!) or have an active thread that is clocking time or read/writes. The information displayed is enough to tell semiskilled operators if they have to kill threads against the DB before the user, or give Sr. Analysts information on who is running critical or resource intense processes. The implementation is easy for the basics. It's the Captive User Interface to keep customers' semiskilled operators from killing things that are important that provides us the ongoing challenge. Start with the general ID of all users on the system, id'ing the PIDs (parent and child of all processes). This allows you to either ID by processes that are running, or if you know your users, ID by user (that's the way we do it, since we have the luxury of knowing our users). Then simply split it up from there... example: Follow the process thread to the terminal session and match that against the onstat -u information with a quick and dirty AWK; this, in turn, can be passed to another short snipet to get onstat -g information or any other relevant information you may need. At this point, we have guidelines for actual operator decision making on what to do and what to kill, including a few automated snippets to kill DB threads before OS threads, look for orphan processes, etc. Hope these ideas help... they are easier to talk about than to code! Rob Konikoff Sr. Logistics Analyst -----Original Message----- From: forum.subscriber@iiug.org [mailto:forum.subscriber@iiug.org] On Behalf Of Jean Sagi Sent: Friday, February 18, 2005 10:03 AM To: ids@iiug.org Subject: Re: FourJs and IDS sessions lock [4298] Check for onstat several times to detect changes. For example onstat -u show you read and writes, that in combination to OS idle time may tell you if the user is doing something or not. This way you better decide to kill or not a session. J. -----Original Message----- From: "SYED AHMAD ...." <najmi@centurysoftware.com.my> To: ids@iiug.org Date: Thu, 17 Feb 2005 20:58:17 -0500 (EST) Subject: FourJs and IDS sessions lock [4294] Hi Is there a mechanism either via SQL scripting or anything else which can be used to identify the user who are really idle from do data manipulation or processing. For example : UserA activate a program call customer. By doing that he/she will get the program menu and the form. Then he/she leave it the screen open from the morning till the evening without doing anything. By looking in onstat -g ses, one session already being created. Since the applcation using FourJs, it already locked one session of FourJs(this effected the number of FourJs license used). One of our client writing the script by looking at OS point of view in term of idling to kill the user. By that, the FourJs and the Informix session not clearly release and it lock other user who really want to access the program. Can somebody give some clue to rectify this. Thanks Jean Sagi jeansagi@myrealbox.com jeansagi@yahoo.com