[THIN] Re: SV: Re: Maximum User logon

  • From: "BRUTON, Malcolm, FM" <Malcolm.BRUTON@xxxxxxxx>
  • To: "'thin@xxxxxxxxxxxxx'" <thin@xxxxxxxxxxxxx>
  • Date: Wed, 7 Jul 2004 10:15:51 +0100

I was thinking more of a history thing rather than immediate.  But I guess
to start now would help.  Any chance you could post your script or snippets
of it.

 

Malcolm

 

  _____  

From: thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx] On Behalf
Of Svein Arild Haugum
Sent: 07 July 2004 08:16
To: thin@xxxxxxxxxxxxx
Subject: [THIN] SV: Re: Maximum User logon

 

I have written a script wich reports the licensing information from the
"clicense connections" command.

 

This script runs every 10 minutes, and gives me the connection number to a
txt file.

 

I have written the script for filter out: Pooled Available. But you should
have no problem exporting Pooled In Use instead.

 

Eksample of the output is:

2004/05/24;14:24:16;16
2004/05/24;14:34:16;20
2004/05/24;14:44:16;23
2004/05/24;14:54:16;28
2004/05/24;15:04:17;49
2004/05/24;15:14:17;60
2004/05/24;15:24:17;62
2004/05/24;15:34:17;70
2004/05/24;15:44:18;83
2004/05/24;15:54:18;101
2004/05/24;16:04:18;147

 

 

This is easy to import in Excel, and make cool graphs....


Mvh 
Svein Arild 

-----Opprinnelig melding-----
Fra: Landin, Mark [mailto:Mark.Landin@xxxxxxxxxxxxxxxx]
Sendt: 6. juli 2004 22:21
Til: thin@xxxxxxxxxxxxx
Emne: [THIN] Re: Maximum User logon

The new licensing with MPS 3.0 will have this kind of information, or will
make it easy to extract it.

 


 

that would be nice wouldn't it

-----Original Message-----
From: BRUTON, Malcolm, FM [mailto:Malcolm.BRUTON@xxxxxxxx]
Sent: Tuesday, July 06, 2004 1:34 PM
To: 'thin@xxxxxxxxxxxxx'
Subject: [THIN] Maximum User logon

Hi All

 

Anyone know of a way to be able to tell the maximum number of users who have
logged on say over the last month.  I do have Resource Manager installed but
can't find something that looks like it would fit the bill quickly.  Cheers

 

Malcolm Bruton

Workspace Team 

The Royal Bank of Scotland - Corporate Banking and Financial Markets
t:   +44 20 7085 5768
e:  <mailto:dmalcolm.bruton@xxxxxxxx> malcolm.bruton@xxxxxxxx
w:  <http://oneteam.fm.rbsgrp.net/> http://oneteam.fm.rbsgrp.net

 



****************************************************************************
*******
The Royal Bank of Scotland plc. Registered in Scotland No 90312. Registered
Office: 36 St Andrew Square, Edinburgh EH2 2YB. 
Authorised and regulated by the Financial Services Authority 

This e-mail message is confidential and for use by the 
addressee only. If the message is received by anyone other 
than the addressee, please return the message to the sender 
by replying to it and then delete the message from your 
computer. Internet e-mails are not necessarily secure. The 
Royal Bank of Scotland plc does not accept responsibility for 
changes made to this message after it was sent. 

Whilst all reasonable care has been taken to avoid the 
transmission of viruses, it is the responsibility of the recipient to 
ensure that the onward transmission, opening or use of this 
message and any attachments will not adversely affect its 
systems or data. No responsibility is accepted by The Royal 
Bank of Scotland plc in this regard and the recipient should carry 
out such virus and other checks as it considers appropriate. 
Visit our websites at: 
http://www.rbs.co.uk/CBFM 
http://www.rbsmarkets.com 
****************************************************************************
****

CONFIDENTIAL COMMUNICATION - PLEASE READ PRIVACY NOTICE This communication
is confidential and may be read only by its intended recipient(s). It may
contain legally privileged and protected information. If you believe you
have received this communication in error, please "Reply" to the Sender and
so indicate or call (603) 663-2800. Then, please promptly "Delete" this
communication from your computer. This communication, and any information
contained herein, may only be forwarded, printed, disclosed, copied or
disseminated by those specifically authorized to do so. UNAUTHORIZED
DISCLOSURE MAY RESULT IN LEGAL LIABILITY FOR THOSE PERSONS RESPONSIBLE.

Other related posts: