New feature suggestion : a designer procedure which, when included in the screen, actions whenever there is screen activity

[Joe Boyle]

How about adding the date, userid and process id to the current qktrace
output ? that would be very useful.

 

  _____  

From: powerh-l-bounces+atla38=dsl.pipex.com at lists.sowder.com
[mailto:powerh-l-bounces+atla38=dsl.pipex.com at lists.sowder.com] On Behalf Of
Deskin, Bob
Sent: 27 July 2007 14:25
To: Joe Boyle; powerh-l at lists.sowder.com
Subject: RE: New feature suggestion : a designer procedure which,when
included in the screen, actions whenever there is screen activity

 

If I think of the effort involved and the potential risk, and also consider
the number of customers to whom this would be valuable, I have to be honest
and say that this one doesn't have much chance of moving forward. I will
keep it, as I do all requests.

 

Bob

-----Original Message-----
From: Joe Boyle [mailto:atla38 at dsl.pipex.com] 
Sent: July 27, 2007 8:00 AM
To: Deskin, Bob; powerh-l at lists.sowder.com
Subject: RE: New feature suggestion : a designer procedure which,when
included in the screen, actions whenever there is screen activity

I was thinking along the lines that, when the procedure is present in a
screen, it could contain code which would write a number of quick session
attributes e.g. timestamp, pid, userid, screenname etc... to a datafile.

 

It would then be possible, e.g. at times of high license usage, to have
complete control over which quick sessions 'live or die'; either by running
reports against the datafile, or by automating logouts based on the values
in the datafile. This could be done by using a quick process in conjunction
with 'run command' syntax, where even the interval time is variable.

 

The qkgo time-out option has no flexibility. The audit trail/trace options
produce a lot of output; this option would happen only when the procedure is
compiled into the screen concerned.

 


  _____  


From: powerh-l-bounces+atla38=dsl.pipex.com at lists.sowder.com
[mailto:powerh-l-bounces+atla38=dsl.pipex.com at lists.sowder.com] On Behalf Of
Deskin, Bob
Sent: 26 July 2007 19:27
To: Joe Boyle; fernando.olmos at hpa.com.au; powerh-l at lists.sowder.com
Subject: RE: New feature suggestion : a designer procedure which,when
included in the screen, actions whenever there is screen activity

 

If you're looking for something that times out QUICK, the QKGO terminal
time-out is supposed to do that based on a prompt being made and no input
happening after a period of time.

 

As well, on UNIX and Windows, there are two types of time out for Axiant
thin-client users to check whether there is activity from the user and
whether the client session is still active.

 

Bob

-----Original Message-----
From: Joe Boyle [mailto:atla38 at dsl.pipex.com] 
Sent: July 26, 2007 1:58 PM
To: Deskin, Bob; fernando.olmos at hpa.com.au; powerh-l at lists.sowder.com
Subject: New feature suggestion : a designer procedure which, when included
in the screen, actions whenever there is screen activity

New feature suggestion : a designer procedure which, when included in the
screen, actions whenever there is screen activity.

 

A simple application of this would be to enable a current timestamp for the
pid of the quick process to be written to a file, and make it much easier to
determine which quick processes have been inactive for a certain amount of
time, and subsequently either logged out or killed etc....

 


  _____  


From: powerh-l-bounces+atla38=dsl.pipex.com at lists.sowder.com
[mailto:powerh-l-bounces+atla38=dsl.pipex.com at lists.sowder.com] On Behalf Of
Deskin, Bob
Sent: 26 July 2007 14:36
To: fernando.olmos at hpa.com.au; powerh-l at lists.sowder.com
Subject: RE: Question about auto logout in QKGO file

 

I just tested this in 8.41E (Windows). It's generic and should work the same
way on all platforms. If not, please report a bug.

 

QUICK keeps an internal count if there's a QKGO Timeout setting. I don't
know how often it's checked, but I know that it issues a warning message a
few seconds before the actual time-out. For example, I set it to 30 seconds
and got a warning 7 seconds before the time-out. At the time-out it exits
QUICK (doing the appropriate rollbacks and backouts). The basis is whether
there's any input from the user. If there's none, QUICK times out.

 

Bob

 

PS You could buy more licenses :-)

-----Original Message-----
From: powerh-l-bounces+bob.deskin=cognos.com at lists.sowder.com
[mailto:powerh-l-bounces+bob.deskin=cognos.com at lists.sowder.com] On Behalf
Of fernando.olmos at hpa.com.au
Sent: July 26, 2007 12:35 AM
To: powerh-l at lists.sowder.com
Subject: Question about auto logout in QKGO file

How does the QKGO file's timeout feature work? 
Is the QKGO file (say 20 mins) checking frequently, to kick people out if
they've left a QUICK session online for longer than 20 minutes? Does it only
kick them out AFTER they try to change screens, for example?

The issue we're having is we're running out of powerhouse licenses due to
the number of users trying to access the system from a powerhouse main menu.
However, there are people that leave their sessions on the screen in this
main menu, without logging out and so it books a license. As soon as they go
back and try and do something QKGO seems to kick in and therefore logs them
out, basically saying ".uh uh.. Sorry. you took too long to action your
screen". We want QKGO to do this anyway, and kick them out of the screen
whether they are using it or not.

Thanks 

Kind regards, 

--- 
Fernando Olmos 
Senior Analyst Programmer 
HPA 
Direct: 03 9217 5411 
Fax: 03 9217 5166 
 <http://www.hpa.com.au> www.hpa.com.au 

 

**********************************************************************
IMPORTANT
The contents of this e-mail and its attachments are confidential and
intended
solely for the use of the individual or entity to whom they are addressed.
If
you received this e-mail in error, please notify the HPA Postmaster,
postmaster at hpa.com.au,
then delete  the e-mail.
This footnote also confirms that this e-mail message has been swept for the
presence of computer viruses by Ironport. Before opening or using any
attachments, check them for viruses and defects.
Our liability is limited to resupplying any affected attachments.
HPA collects personal information to provide and market our services. For
more
information about use, disclosure and access see our Privacy Policy at
www.hpa.com.au
**********************************************************************

 

     This message may contain privileged and/or confidential information.
If you have received this e-mail in error or are not the intended recipient,
you may not use, copy, disseminate or distribute it; do not open any
attachments, delete it immediately from your system and notify the sender
promptly by e-mail that you have done so.  Thank you. 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.sowder.com/pipermail/powerh-l/attachments/20070730/10ad0246/attachment.html