Re: [U2] Autologout

2013-07-24 Thread Holt, Jake
Ah, I misunderstood the command.  I thought it set the autologout time
for all users.   Thanks, it should not pose a problem for me knowing
this.

-Original Message-
From: u2-users-boun...@listserver.u2ug.org
[mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Phil Walker
Sent: Wednesday, July 24, 2013 3:03 PM
To: U2 Users List
Subject: Re: [U2] Autologout

Sort of, you would have to conditionally use the command in a Paragraph
or like to do this I believe.

LOGIN
PA
IF [skipautologout = true] GO SKIPAUTOLOGOUT AUTOLOGOUT
SKIPAUTOLOGOUT:
NEXTCOMMAND

Would be nice if UV could interrogate the ENV in one line e.g.

IF ENV.AUTOLOGOUT = 1 THEN GO SKIPAUTOLOGOUT AUTOLOGOUT

Alas but it can't at least in the manner like above.

Cheers

Phil

-Original Message-
From: u2-users-boun...@listserver.u2ug.org
[mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Holt, Jake
Sent: Thursday, 25 July 2013 7:56 a.m.
To: u2-users@listserver.u2ug.org
Subject: [U2] Autologout

This is probably a simple question but I can't seem to figure it out, is
there a way to exempt users from autologout?

 

Jake Holt l samsill l Information Technology Director

(817) 759-8038 l jh...@samsill.com <mailto:jh...@samsill.com> 

www.samsill.com <http://www.samsill.com/> 

 

___
U2-Users mailing list
U2-Users@listserver.u2ug.org
http://listserver.u2ug.org/mailman/listinfo/u2-users
___
U2-Users mailing list
U2-Users@listserver.u2ug.org
http://listserver.u2ug.org/mailman/listinfo/u2-users


___
U2-Users mailing list
U2-Users@listserver.u2ug.org
http://listserver.u2ug.org/mailman/listinfo/u2-users


Re: [U2] Autologout

2013-07-24 Thread Phil Walker
Sort of, you would have to conditionally use the command in a Paragraph or like 
to do this I believe.

LOGIN
PA
IF [skipautologout = true] GO SKIPAUTOLOGOUT
AUTOLOGOUT
SKIPAUTOLOGOUT:
NEXTCOMMAND

Would be nice if UV could interrogate the ENV in one line e.g.

IF ENV.AUTOLOGOUT = 1 THEN GO SKIPAUTOLOGOUT
AUTOLOGOUT

Alas but it can't at least in the manner like above.

Cheers

Phil

-Original Message-
From: u2-users-boun...@listserver.u2ug.org 
[mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Holt, Jake
Sent: Thursday, 25 July 2013 7:56 a.m.
To: u2-users@listserver.u2ug.org
Subject: [U2] Autologout

This is probably a simple question but I can't seem to figure it out, is there 
a way to exempt users from autologout?

 

Jake Holt l samsill l Information Technology Director

(817) 759-8038 l jh...@samsill.com <mailto:jh...@samsill.com> 

www.samsill.com <http://www.samsill.com/> 

 

___
U2-Users mailing list
U2-Users@listserver.u2ug.org
http://listserver.u2ug.org/mailman/listinfo/u2-users
___
U2-Users mailing list
U2-Users@listserver.u2ug.org
http://listserver.u2ug.org/mailman/listinfo/u2-users


[U2] Autologout

2013-07-24 Thread Holt, Jake
This is probably a simple question but I can't seem to figure it out, is
there a way to exempt users from autologout?

 

Jake Holt l samsill l Information Technology Director

(817) 759-8038 l jh...@samsill.com  

www.samsill.com  

 

___
U2-Users mailing list
U2-Users@listserver.u2ug.org
http://listserver.u2ug.org/mailman/listinfo/u2-users


Re: [U2] AUTOLOGOUT [AD]

2010-03-06 Thread Randy Styka
[AD]

Hi!

Because of the discussion of Autologout, I thought it would be a good
time to remind people of our product, LOGMON.  This software runs on
any Unix/Linux based system (we don't do Windows).  It gives you a
great deal of control over idle time logoffs.

Unlike the AUTOLOGOUT setting, or various other options, we look at
the actual CPU time used by each user, and their child proceses.  We
can then determine if a user truly is idle, instead of just looking at
keyboard activity.  You can then configure LOGMON to log off the idle
sessions.

You can vary this inactivity time by user, group, time of day,
application in use, etc.  So you can easily exempt users from logout,
if desired.  LOGMON can be set up to send a warning message before
logout.  It can also log its actions, such as who was logged off and
when.  And it can run scripts to control how specific users are logged
off.  Finally, a menu based system shows your users and how long they
have been idle, with cpu usage, etc.  We have many customers that are
Unidata or Universe based, as well as other applications on Unix/Linux.

Just wanted to mention this.  More details are at http://www.logmon.com
[/AD]
Thanks!  Randy

++
| Computronics   Randy Styka, ra...@computronics.com |
| 4N165 Wood Dale Road   Phone: 630/941-7767 |
| Addison, Illinois  60101 USA   Fax:   630/941-7714 |
++

___
U2-Users mailing list
U2-Users@listserver.u2ug.org
http://listserver.u2ug.org/mailman/listinfo/u2-users


Re: [U2] AUTOLOGOUT

2010-03-03 Thread Leroy Dreyfuss
Hi Marc,

AUTOLOGOUT is session based. Onceit is executed it remains in effect
regardless of where the user navigates.

Also, the session must be waiting for input from the user for the
logout counter to begin. Once the user enters someting as input, the
counter stops and starts over only at the next input.

Cheers,

LeRoy

Sent from my iPhone 3Gs

On 03 Mar 2010, at 8:03 PM, "Caminiti, Marc"  wrote:

> Have a quick couple of questions on the AUTOLOGOUT function.   This is
> on Red Hat Enterprise Server 5.3, Universe 10.2.7.  Is the AUTOLOGOUT
> function a global setting, or can we use this in just 1 account?  For
> example, we have 2 accounts, PROD and DEV.  If we put AUTOLOGOUT 15 in
> the DEV account, will those people that go to the DEV account be the
> only ones affected by it?  Also, if we have a select or program that
> is
> running that takes greater than the "15" minutes in the AUTOLOGOUT,
> will
> it kill the process, or wait until it is finished, then start the 15
> minutes idle time?
>
>
>
> Thanks in advance
>
> marc
>
>
>
> Marc Caminiti
>
> IS Manager
>
> Nashbar Direct, Inc
>
> 6103 State Route 446
>
> Canfield, OH 44406
>
> 330.533.1989, ext 336
>
> 330.702.9733, fax
>
>
>
> All generalisations are dangerous, even this one.
>
>
>
>
>
> CONFIDENTIALITY NOTICE: This e-mail and any attachments may contain
> confidential information that is legally privileged. The information
> is solely for the use of the intended recipient(s). Any disclosure,
> copying, distribution, or other use of this information is strictly
> prohibited. If you have received this e-mail in error, please notify
> the sender by return e-mail and delete this message.
>
> ___
> U2-Users mailing list
> U2-Users@listserver.u2ug.org
> http://listserver.u2ug.org/mailman/listinfo/u2-users

To read FRSTIA's disclaimer for the e-mail go to http://www.frstia.co.za/
___
U2-Users mailing list
U2-Users@listserver.u2ug.org
http://listserver.u2ug.org/mailman/listinfo/u2-users


[U2] AUTOLOGOUT

2010-03-03 Thread Caminiti, Marc
Have a quick couple of questions on the AUTOLOGOUT function.   This is
on Red Hat Enterprise Server 5.3, Universe 10.2.7.  Is the AUTOLOGOUT
function a global setting, or can we use this in just 1 account?  For
example, we have 2 accounts, PROD and DEV.  If we put AUTOLOGOUT 15 in
the DEV account, will those people that go to the DEV account be the
only ones affected by it?  Also, if we have a select or program that is
running that takes greater than the "15" minutes in the AUTOLOGOUT, will
it kill the process, or wait until it is finished, then start the 15
minutes idle time?

 

Thanks in advance

marc

 

Marc Caminiti

IS Manager

Nashbar Direct, Inc

6103 State Route 446

Canfield, OH 44406

330.533.1989, ext 336

330.702.9733, fax

 

All generalisations are dangerous, even this one.

 



CONFIDENTIALITY NOTICE: This e-mail and any attachments may contain 
confidential information that is legally privileged. The information is solely 
for the use of the intended recipient(s). Any disclosure, copying, 
distribution, or other use of this information is strictly prohibited. If you 
have received this e-mail in error, please notify the sender by return e-mail 
and delete this message.

___
U2-Users mailing list
U2-Users@listserver.u2ug.org
http://listserver.u2ug.org/mailman/listinfo/u2-users


Re: [U2] AUTOLOGOUT and ON.ABORT

2009-03-02 Thread Jacques G.
You should read your uvconfig file (and Manual) to see if you have a flag for 
it in the Windows version of Universe.  On the Unix version, the only thing I 
need to do in order to turn on the loggin is to create the errlog file.

Your admin menu may have an option for it somewhere.



- Original Message 
From: Mike Roosa 
To: u2-users@listserver.u2ug.org
Sent: Monday, March 2, 2009 9:35:11 AM
Subject: Re: [U2] AUTOLOGOUT and ON.ABORT

I created the errlog file and it does appear to be logging some messages.
Do I have to do anything in uniadmin as I see a couple of error messages
when universe first starts up.
Sun Mar 01 01:00:11  -4701 NT AUTHORITY\system uniVerse Log Daemon started
Sun Mar 01 01:00:11  -4701 NT AUTHORITY\system Unable to read LOGS.DIR entry
from D_UV_LOGS.
Sun Mar 01 01:00:11  -4701 NT AUTHORITY\system Can't start logging, logging
inactivated in uvconfig


On Fri, Feb 27, 2009 at 5:21 PM, Jacques G.  wrote:

> On unix it's an empty file (size zero) we create:
> EI:
>
> touch errlog
>
> On a windows the equivalent would probably be (from dos prompt when in the
> uv account):
> copy con errlog
> ^Z
>
>  1 file(s) copied.
>
> (After typing CTRL-Z you press[RETURN])  I haven't used the errlog in
> Universe for Windows though.
>
>
>
> - Original Message 
> From: Mike Roosa 
> To: u2-users@listserver.u2ug.org
> Sent: Friday, February 27, 2009 3:55:22 PM
> Subject: Re: [U2] AUTOLOGOUT and ON.ABORT
>
> Ok, so I just create a type 18 file called ERRLOG in the UV account and
> restart universe?
>
> On Fri, Feb 27, 2009 at 11:59 AM, Martin Phillips <
> martinphill...@ladybridge.com> wrote:
>
> > Hi Mike,
> >
> >  I was under the impression that the errlog only existed on
> >> unix systems. Maybe I'm wrong on this but I can't find it
> >> anywhere on our system.
> >>
> >
> > The errlog file is on Windows too but, just as on Unix, you need to
> create
> > an empty errlog file in the UV account directory to enable the system. UV
> > looks for this on entry and enables logging.
> >
> >
> > Martin Phillips
> > Ladybridge Systems Ltd
> > 17b Coldstream Lane, Hardingstone, Northampton, NN4 6DB
> > +44-(0)1604-709200 ---
> >
> > u2-users mailing list
> > u2-users@listserver.u2ug.org
> > To unsubscribe please visit http://listserver.u2ug.org/
> ---
> u2-users mailing list
> u2-users@listserver.u2ug.org
> To unsubscribe please visit http://listserver.u2ug.org/
> ---
> u2-users mailing list
> u2-users@listserver.u2ug.org
> To unsubscribe please visit http://listserver.u2ug.org/
---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/
---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/


RE: [U2] AUTOLOGOUT and ON.ABORT

2009-03-02 Thread Eric Armstrong
We use Windows and its kept at \\Mars\UVDB\TOOLS\ERRLOG.BACKUP

Eric Armstrong
Lobel Financial
IT Dept


-Original Message-
From: Mike Roosa [mailto:mike.ro...@gmail.com]
Sent: Friday, February 27, 2009 7:32 AM
To: u2-users@listserver.u2ug.org
Subject: Re: [U2] AUTOLOGOUT and ON.ABORT


I was under the impression that the errlog only existed on unix systems.
 Maybe I'm wrong on this but I can't find it anywhere on our system.

On Fri, Feb 27, 2009 at 1:17 AM, Jacques G.  wrote:

> If you turn on the errlog file in /u1/uv you may get a message in there
for
> an AUTOLOGOUT.  I'm pretty sure I've seen such messages in the past.  You
> will have the user name, the PID and some text describing the error.
>
> The errlog file only keeps the last 1001 error messages so you might want
> to have a cron job back them up with a date time stamp periodically during
> the day.
>
>
>
> - Original Message 
> > Our users have their AUTOLOGOUT set to 30 minutes and it looks like the
> > AUTOLOGOUT process causes the ON.ABORT clause to execute.  Is there an
> > easy  way using a SYSTEM() or @variable to determine that this ON.ABORT
> is the
> > result of an AUTOLOGOUT?
> ---
> u2-users mailing list
> u2-users@listserver.u2ug.org
> To unsubscribe please visit http://listserver.u2ug.org/
---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/

LOBEL FINANCIAL PRIVACY NOTICE: 
This communication may contain confidential company information that is 
protected by federal law. Federal regulations prohibit the disclosure (or 
re-disclosure) of confidential information without the written consent of the 
person(s) to whom it pertains. Additionally, the views or opinions presented in 
this email are solely those of the author and do not necessarily represent 
those of the company.
---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/


Re: [U2] AUTOLOGOUT and ON.ABORT

2009-03-02 Thread Mike Roosa
I created the errlog file and it does appear to be logging some messages.
 Do I have to do anything in uniadmin as I see a couple of error messages
when universe first starts up.
Sun Mar 01 01:00:11  -4701 NT AUTHORITY\system uniVerse Log Daemon started
Sun Mar 01 01:00:11  -4701 NT AUTHORITY\system Unable to read LOGS.DIR entry
from D_UV_LOGS.
Sun Mar 01 01:00:11  -4701 NT AUTHORITY\system Can't start logging, logging
inactivated in uvconfig


On Fri, Feb 27, 2009 at 5:21 PM, Jacques G.  wrote:

> On unix it's an empty file (size zero) we create:
> EI:
>
> touch errlog
>
> On a windows the equivalent would probably be (from dos prompt when in the
> uv account):
> copy con errlog
> ^Z
>
>  1 file(s) copied.
>
> (After typing CTRL-Z you press[RETURN])  I haven't used the errlog in
> Universe for Windows though.
>
>
>
> - Original Message 
> From: Mike Roosa 
> To: u2-users@listserver.u2ug.org
> Sent: Friday, February 27, 2009 3:55:22 PM
> Subject: Re: [U2] AUTOLOGOUT and ON.ABORT
>
> Ok, so I just create a type 18 file called ERRLOG in the UV account and
> restart universe?
>
> On Fri, Feb 27, 2009 at 11:59 AM, Martin Phillips <
> martinphill...@ladybridge.com> wrote:
>
> > Hi Mike,
> >
> >  I was under the impression that the errlog only existed on
> >> unix systems. Maybe I'm wrong on this but I can't find it
> >> anywhere on our system.
> >>
> >
> > The errlog file is on Windows too but, just as on Unix, you need to
> create
> > an empty errlog file in the UV account directory to enable the system. UV
> > looks for this on entry and enables logging.
> >
> >
> > Martin Phillips
> > Ladybridge Systems Ltd
> > 17b Coldstream Lane, Hardingstone, Northampton, NN4 6DB
> > +44-(0)1604-709200 ---
> >
> > u2-users mailing list
> > u2-users@listserver.u2ug.org
> > To unsubscribe please visit http://listserver.u2ug.org/
> ---
> u2-users mailing list
> u2-users@listserver.u2ug.org
> To unsubscribe please visit http://listserver.u2ug.org/
> ---
> u2-users mailing list
> u2-users@listserver.u2ug.org
> To unsubscribe please visit http://listserver.u2ug.org/
---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/


Re: [U2] AUTOLOGOUT and ON.ABORT

2009-02-27 Thread Jacques G.
On unix it's an empty file (size zero) we create:
EI:

touch errlog

On a windows the equivalent would probably be (from dos prompt when in the uv 
account):
copy con errlog
^Z

  1 file(s) copied.

(After typing CTRL-Z you press[RETURN])  I haven't used the errlog in Universe 
for Windows though.



- Original Message 
From: Mike Roosa 
To: u2-users@listserver.u2ug.org
Sent: Friday, February 27, 2009 3:55:22 PM
Subject: Re: [U2] AUTOLOGOUT and ON.ABORT

Ok, so I just create a type 18 file called ERRLOG in the UV account and
restart universe?

On Fri, Feb 27, 2009 at 11:59 AM, Martin Phillips <
martinphill...@ladybridge.com> wrote:

> Hi Mike,
>
>  I was under the impression that the errlog only existed on
>> unix systems. Maybe I'm wrong on this but I can't find it
>> anywhere on our system.
>>
>
> The errlog file is on Windows too but, just as on Unix, you need to create
> an empty errlog file in the UV account directory to enable the system. UV
> looks for this on entry and enables logging.
>
>
> Martin Phillips
> Ladybridge Systems Ltd
> 17b Coldstream Lane, Hardingstone, Northampton, NN4 6DB
> +44-(0)1604-709200 ---
>
> u2-users mailing list
> u2-users@listserver.u2ug.org
> To unsubscribe please visit http://listserver.u2ug.org/
---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/
---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/


Re: [U2] AUTOLOGOUT and ON.ABORT

2009-02-27 Thread Perry Taylor
#touch $(cat /.uvhome)/errlog


- Original Message -
From: owner-u2-us...@listserver.u2ug.org 
To: u2-users@listserver.u2ug.org 
Sent: Fri Feb 27 15:55:22 2009
Subject: Re: [U2] AUTOLOGOUT and ON.ABORT

Ok, so I just create a type 18 file called ERRLOG in the UV account and
restart universe?

On Fri, Feb 27, 2009 at 11:59 AM, Martin Phillips <
martinphill...@ladybridge.com> wrote:

> Hi Mike,
>
>  I was under the impression that the errlog only existed on
>> unix systems. Maybe I'm wrong on this but I can't find it
>> anywhere on our system.
>>
>
> The errlog file is on Windows too but, just as on Unix, you need to create
> an empty errlog file in the UV account directory to enable the system. UV
> looks for this on entry and enables logging.
>
>
> Martin Phillips
> Ladybridge Systems Ltd
> 17b Coldstream Lane, Hardingstone, Northampton, NN4 6DB
> +44-(0)1604-709200 ---
>
> u2-users mailing list
> u2-users@listserver.u2ug.org
> To unsubscribe please visit http://listserver.u2ug.org/
---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/

CONFIDENTIALITY NOTICE: This e-mail message, including any attachments, is for
the sole use of the intended recipient(s) and may contain confidential and
privileged information.  Any unauthorized review, use, disclosure or
distribution is prohibited. ZirMed, Inc. has strict policies regarding the
content of e-mail communications, specifically Protected Health Information,
any communications containing such material will be returned to the
originating party with such advisement noted. If you are not the intended
recipient, please contact the sender by reply e-mail and destroy all copies of
the original message.
---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/


Re: [U2] AUTOLOGOUT and ON.ABORT

2009-02-27 Thread Mike Roosa
Ok, so I just create a type 18 file called ERRLOG in the UV account and
restart universe?

On Fri, Feb 27, 2009 at 11:59 AM, Martin Phillips <
martinphill...@ladybridge.com> wrote:

> Hi Mike,
>
>  I was under the impression that the errlog only existed on
>> unix systems. Maybe I'm wrong on this but I can't find it
>> anywhere on our system.
>>
>
> The errlog file is on Windows too but, just as on Unix, you need to create
> an empty errlog file in the UV account directory to enable the system. UV
> looks for this on entry and enables logging.
>
>
> Martin Phillips
> Ladybridge Systems Ltd
> 17b Coldstream Lane, Hardingstone, Northampton, NN4 6DB
> +44-(0)1604-709200 ---
>
> u2-users mailing list
> u2-users@listserver.u2ug.org
> To unsubscribe please visit http://listserver.u2ug.org/
---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/


Re: [U2] AUTOLOGOUT and ON.ABORT

2009-02-27 Thread Martin Phillips

Hi Mike,


I was under the impression that the errlog only existed on
unix systems. Maybe I'm wrong on this but I can't find it
anywhere on our system.


The errlog file is on Windows too but, just as on Unix, you need to create 
an empty errlog file in the UV account directory to enable the system. UV 
looks for this on entry and enables logging.



Martin Phillips
Ladybridge Systems Ltd
17b Coldstream Lane, Hardingstone, Northampton, NN4 6DB
+44-(0)1604-709200 
---

u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/


Re: [U2] AUTOLOGOUT and ON.ABORT

2009-02-27 Thread Mike Roosa
I was under the impression that the errlog only existed on unix systems.
 Maybe I'm wrong on this but I can't find it anywhere on our system.

On Fri, Feb 27, 2009 at 1:17 AM, Jacques G.  wrote:

> If you turn on the errlog file in /u1/uv you may get a message in there for
> an AUTOLOGOUT.  I'm pretty sure I've seen such messages in the past.  You
> will have the user name, the PID and some text describing the error.
>
> The errlog file only keeps the last 1001 error messages so you might want
> to have a cron job back them up with a date time stamp periodically during
> the day.
>
>
>
> - Original Message 
> > Our users have their AUTOLOGOUT set to 30 minutes and it looks like the
> > AUTOLOGOUT process causes the ON.ABORT clause to execute.  Is there an
> > easy  way using a SYSTEM() or @variable to determine that this ON.ABORT
> is the
> > result of an AUTOLOGOUT?
> ---
> u2-users mailing list
> u2-users@listserver.u2ug.org
> To unsubscribe please visit http://listserver.u2ug.org/
---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/


RE: [U2] AUTOLOGOUT and ON.ABORT

2009-02-27 Thread Perry Taylor
Just a side note on the errlog file... You can increase the number of
messages by increasing the MAXERRLOGENT parameter in uvconfig.

Perry 

-Original Message-
From: owner-u2-us...@listserver.u2ug.org
[mailto:owner-u2-us...@listserver.u2ug.org] On Behalf Of Jacques G.
Sent: Thursday, February 26, 2009 11:17 PM
To: u2-users@listserver.u2ug.org
Subject: Re: [U2] AUTOLOGOUT and ON.ABORT

If you turn on the errlog file in /u1/uv you may get a message in there
for an AUTOLOGOUT.  I'm pretty sure I've seen such messages in the past.
You will have the user name, the PID and some text describing the error.

The errlog file only keeps the last 1001 error messages so you might
want to have a cron job back them up with a date time stamp periodically
during the day.



- Original Message 
> Our users have their AUTOLOGOUT set to 30 minutes and it looks like
the
> AUTOLOGOUT process causes the ON.ABORT clause to execute.  Is there an
> easy  way using a SYSTEM() or @variable to determine that this
ON.ABORT is the
> result of an AUTOLOGOUT?
---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/

CONFIDENTIALITY NOTICE: This e-mail message, including any attachments, is for 
the sole use of the intended recipient(s) and may contain confidential and 
privileged information.  Any unauthorized review, use, disclosure or 
distribution is prohibited. ZirMed, Inc. has strict policies regarding the 
content of e-mail communications, specifically Protected Health Information, 
any communications containing such material will be returned to the originating 
party with such advisement noted. If you are not the intended recipient, please 
contact the sender by reply e-mail and destroy all copies of the original 
message.
---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/


Re: [U2] AUTOLOGOUT and ON.ABORT

2009-02-26 Thread Jacques G.
If you turn on the errlog file in /u1/uv you may get a message in there for an 
AUTOLOGOUT.  I'm pretty sure I've seen such messages in the past.  You will 
have the user name, the PID and some text describing the error.

The errlog file only keeps the last 1001 error messages so you might want to 
have a cron job back them up with a date time stamp periodically during the day.



- Original Message 
> Our users have their AUTOLOGOUT set to 30 minutes and it looks like the
> AUTOLOGOUT process causes the ON.ABORT clause to execute.  Is there an
> easy  way using a SYSTEM() or @variable to determine that this ON.ABORT is the
> result of an AUTOLOGOUT?
---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/


RE: [U2] AUTOLOGOUT and ON.ABORT

2009-02-26 Thread Hona, David
I would've thought you would have the BREAK-key disabled for your users.
Do you have Break, Interrupt & Suspend keys disabled? [See BREAK
statement in the UV BASIC manual]...not that'll make a difference...just
curious why you let them 'break' out.


-Original Message-
From: owner-u2-us...@listserver.u2ug.org
[mailto:owner-u2-us...@listserver.u2ug.org] On Behalf Of Mike Roosa
Sent: Friday, 27 February 2009 1:59 PM
To: u2-users@listserver.u2ug.org
Subject: Re: [U2] AUTOLOGOUT and ON.ABORT

Unfortunately the @ABORT.CODE is 3 which is the same for AUTOLOGOUT as a
user breaking out of a program.

On Thu, Feb 26, 2009 at 7:02 PM, Hona, David 
wrote:

> In UniVerse, @ABORT.CODE is set to signify the reason code. I can't
> recall value set for AUTOLOGOUT though and I can't check right now.
>
> Regards
> David
>
>
> -Original Message-
> From: owner-u2-us...@listserver.u2ug.org
> [mailto:owner-u2-us...@listserver.u2ug.org] On Behalf Of Mike Roosa
> Sent: Friday, 27 February 2009 1:38 AM
> To: u2-users@listserver.u2ug.org
> Subject: [U2] AUTOLOGOUT and ON.ABORT
>
> We are running Universe on a Windows 2003 server and trying to set up
> some
> code to run when the user hits a runtime error.  I wrote a small
program
> to
> be called from ON.ABORT that logs the user id, date, time, and
presents
> the
> user with a message telling them to contact support so that we can
look
> at
> their problem.
> Our users have their AUTOLOGOUT set to 30 minutes and it looks like
the
> AUTOLOGOUT process causes the ON.ABORT clause to execute.  Is there an
> easy
> way using a SYSTEM() or @variable to determine that this ON.ABORT is
the
> result of an AUTOLOGOUT?
>
> Also, is there any way to find the program / line # / error message
that
> cause the abort when they encounter a runtime error.  I know Unix has
> the
> errlog in the uv directory but I'm not seeing any of that on our
Windows
> system.
>
> Thanks,
> Mike Roosa

** IMPORTANT MESSAGE *   
This e-mail message is intended only for the addressee(s) and contains 
information which may be
confidential. 
If you are not the intended recipient please advise the sender by return email, 
do not use or
disclose the contents, and delete the message and any attachments from your 
system. Unless
specifically indicated, this email does not constitute formal advice or 
commitment by the sender
or the Commonwealth Bank of Australia (ABN 48 123 123 124) or its subsidiaries. 
We can be contacted through our web site: commbank.com.au. 
If you no longer wish to receive commercial electronic messages from us, please 
reply to this
e-mail by typing Unsubscribe in the subject line. 
**
---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/


Re: [U2] AUTOLOGOUT and ON.ABORT

2009-02-26 Thread Mike Roosa
Unfortunately the @ABORT.CODE is 3 which is the same for AUTOLOGOUT as a
user breaking out of a program.

On Thu, Feb 26, 2009 at 7:02 PM, Hona, David  wrote:

> In UniVerse, @ABORT.CODE is set to signify the reason code. I can't
> recall value set for AUTOLOGOUT though and I can't check right now.
>
> Regards
> David
>
>
> -Original Message-
> From: owner-u2-us...@listserver.u2ug.org
> [mailto:owner-u2-us...@listserver.u2ug.org] On Behalf Of Mike Roosa
> Sent: Friday, 27 February 2009 1:38 AM
> To: u2-users@listserver.u2ug.org
> Subject: [U2] AUTOLOGOUT and ON.ABORT
>
> We are running Universe on a Windows 2003 server and trying to set up
> some
> code to run when the user hits a runtime error.  I wrote a small program
> to
> be called from ON.ABORT that logs the user id, date, time, and presents
> the
> user with a message telling them to contact support so that we can look
> at
> their problem.
> Our users have their AUTOLOGOUT set to 30 minutes and it looks like the
> AUTOLOGOUT process causes the ON.ABORT clause to execute.  Is there an
> easy
> way using a SYSTEM() or @variable to determine that this ON.ABORT is the
> result of an AUTOLOGOUT?
>
> Also, is there any way to find the program / line # / error message that
> cause the abort when they encounter a runtime error.  I know Unix has
> the
> errlog in the uv directory but I'm not seeing any of that on our Windows
> system.
>
> Thanks,
> Mike Roosa
>
> ** IMPORTANT MESSAGE *
> This e-mail message is intended only for the addressee(s) and contains
> information which may be
> confidential.
> If you are not the intended recipient please advise the sender by return
> email, do not use or
> disclose the contents, and delete the message and any attachments from your
> system. Unless
> specifically indicated, this email does not constitute formal advice or
> commitment by the sender
> or the Commonwealth Bank of Australia (ABN 48 123 123 124) or its
> subsidiaries.
> We can be contacted through our web site: commbank.com.au.
> If you no longer wish to receive commercial electronic messages from us,
> please reply to this
> e-mail by typing Unsubscribe in the subject line.
> **
> ---
> u2-users mailing list
> u2-users@listserver.u2ug.org
> To unsubscribe please visit http://listserver.u2ug.org/
---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/


RE: [U2] AUTOLOGOUT and ON.ABORT

2009-02-26 Thread Hona, David
In UniVerse, @ABORT.CODE is set to signify the reason code. I can't
recall value set for AUTOLOGOUT though and I can't check right now.

Regards
David


-Original Message-
From: owner-u2-us...@listserver.u2ug.org
[mailto:owner-u2-us...@listserver.u2ug.org] On Behalf Of Mike Roosa
Sent: Friday, 27 February 2009 1:38 AM
To: u2-users@listserver.u2ug.org
Subject: [U2] AUTOLOGOUT and ON.ABORT

We are running Universe on a Windows 2003 server and trying to set up
some
code to run when the user hits a runtime error.  I wrote a small program
to
be called from ON.ABORT that logs the user id, date, time, and presents
the
user with a message telling them to contact support so that we can look
at
their problem.
Our users have their AUTOLOGOUT set to 30 minutes and it looks like the
AUTOLOGOUT process causes the ON.ABORT clause to execute.  Is there an
easy
way using a SYSTEM() or @variable to determine that this ON.ABORT is the
result of an AUTOLOGOUT?

Also, is there any way to find the program / line # / error message that
cause the abort when they encounter a runtime error.  I know Unix has
the
errlog in the uv directory but I'm not seeing any of that on our Windows
system.

Thanks,
Mike Roosa

** IMPORTANT MESSAGE *   
This e-mail message is intended only for the addressee(s) and contains 
information which may be
confidential. 
If you are not the intended recipient please advise the sender by return email, 
do not use or
disclose the contents, and delete the message and any attachments from your 
system. Unless
specifically indicated, this email does not constitute formal advice or 
commitment by the sender
or the Commonwealth Bank of Australia (ABN 48 123 123 124) or its subsidiaries. 
We can be contacted through our web site: commbank.com.au. 
If you no longer wish to receive commercial electronic messages from us, please 
reply to this
e-mail by typing Unsubscribe in the subject line. 
**
---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/


RE: [U2] AUTOLOGOUT and ON.ABORT

2009-02-26 Thread John Hester
> -Original Message-
> From: owner-u2-us...@listserver.u2ug.org 
> [mailto:owner-u2-us...@listserver.u2ug.org] On Behalf Of Mike Roosa
> Sent: Thursday, February 26, 2009 6:38 AM
> To: u2-users@listserver.u2ug.org
> Subject: [U2] AUTOLOGOUT and ON.ABORT

[snip]

> AUTOLOGOUT process causes the ON.ABORT clause to execute.  Is 
> there an easy
> way using a SYSTEM() or @variable to determine that this 
> ON.ABORT is the
> result of an AUTOLOGOUT?
> 
> Also, is there any way to find the program / line # / error 
> message that
> cause the abort when they encounter a runtime error.  I know 
> Unix has the
> errlog in the uv directory but I'm not seeing any of that on 
> our Windows
> system.

I'll answer your second question first, because it pertains to the first
question in our case.  We use COMO to capture the error messages from
aborts.  All of our programs are executed by PROCs that turn COMO on
prior to executing the program.  ON.ABORT saves the user's current COMO
to a new, unique ID and emails the ID to a list of admins.

To answer your first question, we use the following test to determine if
the abort was due to AUTOLOGOUT:

IF NOT(INDEX(ITEM.COMO,'Automatic Logout',1)) THEN

We skip sending the email for autologouts.  I don't know if there's an
easier way to do it.

-John
---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/


Re: [U2] AUTOLOGOUT and ON.ABORT

2009-02-26 Thread Mike Roosa
Unfortunately this is all I have in SYSTEM(9001).
1}BP.O/ON.ABORT}0x5e~


On Thu, Feb 26, 2009 at 11:04 AM, Kevin King  wrote:

> Can you glean anything from SYSTEM(9001)?
> ---
> u2-users mailing list
> u2-users@listserver.u2ug.org
> To unsubscribe please visit http://listserver.u2ug.org/
---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/


Re: [U2] AUTOLOGOUT and ON.ABORT

2009-02-26 Thread Kevin King
Can you glean anything from SYSTEM(9001)?
---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/


[U2] AUTOLOGOUT and ON.ABORT

2009-02-26 Thread Mike Roosa
We are running Universe on a Windows 2003 server and trying to set up some
code to run when the user hits a runtime error.  I wrote a small program to
be called from ON.ABORT that logs the user id, date, time, and presents the
user with a message telling them to contact support so that we can look at
their problem.
Our users have their AUTOLOGOUT set to 30 minutes and it looks like the
AUTOLOGOUT process causes the ON.ABORT clause to execute.  Is there an easy
way using a SYSTEM() or @variable to determine that this ON.ABORT is the
result of an AUTOLOGOUT?

Also, is there any way to find the program / line # / error message that
cause the abort when they encounter a runtime error.  I know Unix has the
errlog in the uv directory but I'm not seeing any of that on our Windows
system.

Thanks,
Mike Roosa
---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/


Re: [U2] AUTOLOGOUT

2005-07-14 Thread Dean Fox
This is what I wrote for a client. Maybe it will help. It uses a
couple local UV files built from a UNIX command query(s) and if I
recall user profiles using a "charge to".  I'd have to pull it apart
to remember the details but maybe there's something in here that might
help.

There was a UV file with user timeout parameters that was checked when
the system load exceeded a specified amount.  The logout/logoff from
both UV and UNIX functioned completely when all parameters were met.

-[d]-

001   PROGRAM AUTO.LOGOFF
002 **  This program is designed to automatically logoff users that
003 **  have been inactive for a specified lenght of time.  It takes
004 **  into consideration keyboard inactivity as well as CPU usage so as not
005 **  to logoff a user who is currently processing data.
006 **
007 **  A priority user file is examined. Consideration is made for users
008 **  that are not to be logged off at all or for users who have longer
009 **  inactivity allowances. Unless an emergency limit has been reached.
010 **  In that case priority users are allowed to be logged off with
011 **  a regular timeout default.
012 **
013 **  Currently there are 90 UDT licenses. This program is set to activate
014 **  when 80+ licenses are being used.  It's felt there's no reason to
015 **  logoff a user to conserve licenses if < the max are in use, etc.
016 **
017 **
018 **  USE.REC<1> = Last two charactors of tty identifier
019 ** <2> = User login id
020 ** <3> = PID
021 ** <4> = CPU usage
022 ** <5> = Keyboard inactivity
023 ** <6> = Delete flag
024 **
025 **TUSER<1> = Last two charactors of tty identifier
026 ** <2> = User login id
027 ** <3> = PID
028 ** <4> = CPU usage
029 ** <5> = Keyboard inactivity
030 ** <6> = Delete flag
031 ** <7> = User Priority
032 **
033 **PUSER<1> = Priority Level
034 ** <2> = Max Inactivity Allowed
035 **
036 ** HIST.REC<1>   = Current Number of udt Sessions
037 ** <2.M> = Last two charactors of tty identifier
038 ** <3.M> = User login id
039 ** <4.M> = PID
040 ** <5.M> = CPU usage
041 ** <6.M> = Keyboard inactivity
042 ** <7.M> = Delete Flag
043 ** <8.M> = User Priority
044 ** <9.M> = Run Date (Internal)
045 *
046 *  MODIFICATION HISTORY
047 *
048 *  No  Date  SCRno   Who  Description
049 *  00  29-04-02  0   def  Orginal Code...
050 *
051
052   CRT ">>> AUTO.LOGOFF <<<"
053
054   CALL MP.OPEN("PRIORITY.USER" , PRIORITY.USER , OPENSTAT) ; IF OPENSTAT
055   OPEN "DICT","PRIORITY.USER" TO DICT.PRIORITY.USER ELSE STOP 201,"DICT,
056   CALL MP.OPEN("TRACK.USER" , TRACK.USER , OPENSTAT) ; IF OPENSTAT THEN
057   CALL MP.OPEN("LOGOFF.HIST" , LOGOFF.HIST , OPENSTAT) ; IF OPENSTAT THE
058
059   DONE= 0
060   KILL.ALL= 0
061   SESSION.LIMIT   = 80
062   EMERGENCY.LIMIT = 88
063   DEFAULT.TIMEOUT = 20
064
065   LOOP UNTIL DONE DO
066  SLEEP 300;* Run every 5 minutes
067
068  IF TIME() > 85500 THEN KILL.ALL = 1
069  RUN.DATE = DATE()
070
071  GOSUB 1000 ; * Build Usage Variable
072
073  USER.CNT = DCOUNT(USE.REC<1>,@VM)
074  FOR NXT.USER = 1 TO USER.CNT
075 GOSUB 2000;* Check Usage
076  NEXT NXT.USER
077
078  GOSUB 3000;* Logoff Qualified Users
079
080 * Check for program abort flag / sleep the night
081  IF KILL.ALL THEN
082 KILL.ALL = 0
083 CLEARFILE TRACK.USER;* Clear accumulated users
084 * Clear Out History Past 7 Days
085 DEL.DATE = OCONV(RUN.DATE - 7,'D')
086 STMT = 'SELECT LOGOFF.HIST WITH DATE < "' :DEL.DATE: '"'
087 EXECUTE STMT CAPTURING RESULT RETURNING ERROR
088 LOOP WHILE READNEXT ID DO
089DELETE LOGOFF.HIST,ID
090 REPEAT
091 SLEEP 21600;* Sleep six hours
092  END
093  READV DONE FROM DICT.PRIORITY.USER,"TERMINATE",1 ELSE DONE = 0
094
095   REPEAT
096
097 * Program Termination
098   RETURN
099
100 1000 ;* Build Usage Variable
101
102   USE.REC = ""
103
104 * Get udt Sessions
105   STMT = "ps -ef | grep udt | grep -v root | grep -v grep | grep -v PHAN
106   PCPERFORM STMT CAPTURING RESULT
107   ATTR.CNT = DCOUNT(RESULT,@AM)
108   UDT.SESSIONS = ATTR.CNT
109
110 * Write History Record / End Processing if Not Exceeding udt Session Limit
111   LOGOFF.HIST.ID = OCONV(RUN.DATE,"D4-"):"_":OCONV(TIME(),"MTS")
112   HIST.REC= UDT.SESSIONS
113   HIST.REC<9> = RUN.DATE
114   WRITE HIST.REC ON LOGOFF.HIST,LOGOFF.HIST.ID
115
116 * Set Session Usage for Each User
117   FOR NXT.ATTR = 1 TO ATTR.CNT
118  IF RESULT[1,1] = " " THEN RESULT = RESULT = TRIM(RESULT)
120  RESULT = CONVERT(" " , @VM , RESULT)
121  TTY = RESULT,@VM)-2> [LEN(RESULT
123  

RE: [U2] AUTOLOGOUT

2005-07-14 Thread Dana Baron
>remember that you need to 'exec' uv to overlay the current process or it
>will create a subprocess to run UniVerse. In which case, the autologout
will
>simply be returning them to their calling shell.

We take a shortcut on using startup files like .profile. Instead, we put an
entry into /etc/passwd for users that we want going directly to Unidata. In
the field used to designate the user's shell, we put a reference to a login
file that starts up Unidata. Since this then becomes the user's shell, once
the shell ends, the process goes away. For example:

juser:*:238:15:Joe User,Reservations
Dept,1131,:/usr/users/juser:/unidata/local/bin/udtlogin

The last entry points to a udtlogin which sets all the necessary environment
variable, changes directory to the top of our Unidata application menu, then
starts udt:

# Define environment variables and set PATH, then start udt
#
PRINTER=system; export PRINTER
UDTHOME=/unidata/ud5211; export UDTHOME
UDTBIN=/unidata/ud5211/bin; export UDTBIN
UDTLOCBIN=/unidata/local/bin; export UDTLOCBIN
UDT_EDIT=emacs; export UDT_EDIT
INTERFACE=/unidata/interface; export INTERFACE
#
LD_LIBRARY_PATH=/var/opt/DAU200/connect/lib; export LD_LIBRARY_PATH
PATH=$PATH:$UDTBIN:$UDTLOCBIN:LD_LIBRARY_PATH:/opt/odbc/odbc.ini; export
PATH
ODBCINI=/opt/odbc/odbc.ini; export ODBCINI
ODBCHOME=/var/opt/DAU200/connect; export ODBCHOME
EDITOR=/usr/bin/emacs; export EDITOR
#
alias ED="emacs"
alias PRINT="lp"
alias print="lp"
alias edit="emacs"
alias EDIT="emacs"
#
umask 000
#
cd /unidata/SMUGGLER/AHS
udt


Dana Baron
System Manager
Smugglers' Notch Resort
---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/


Re: [U2] AUTOLOGOUT

2005-07-14 Thread Dianne Ackerman
I think it has do to with the way they get to Universe in the first 
place.  We have it setup so the unix users automatically go to a certain 
place where there is a .profile which does 'exec uv' within it.  Then 
the AUTOLOGOUT works just as you want it to, it logs them off 
completely.  Other users we have which go into unix but stay there until 
they execute a command to go into uv work the other way, the AUTOLOGOUT 
brings them back to unix.

-Dianne

Andy Moore wrote:


DISCLAIMER:
This email and any files transmitted with it are confidential and intended
solely for the use of the individual or entity to whom they are addressed.
If you have received this email in error, please delete it and notify
the sender immediately.  Please note that there is no guarantee that
this email or any attachment is virus free or has not been intercepted
or amended.

Hello,

Anyone got any ideas on the autologout command on a Unix environment?

We have it working happily on some Windows servers, set to log people
off if they are inactive for 60 minutes, but when used on a Unix server
it drops the user to the Unix prompt when logging them off from
Universe.

I am looking for a way to completely log the user off the server.

Thanks


Andy Moore
Selima Software Ltd
Tel: 0114 2815000
Fax: 0114 281
email: [EMAIL PROTECTED]
Support: http://tracker.selima.co.uk 
Forum: http://forum.selima.co.uk 
---

---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/


RE: [U2] AUTOLOGOUT

2005-07-14 Thread Brian Leach
Andy,

How do you start their uv processes? 
If you are starting the uv process from e.g. a .profile or .login script,
remember that you need to 'exec' uv to overlay the current process or it
will create a subprocess to run UniVerse. In which case, the autologout will
simply be returning them to their calling shell.


Brian 

Hello,
> 
> Anyone got any ideas on the autologout command on a Unix environment?
> 
> We have it working happily on some Windows servers, set to 
> log people off if they are inactive for 60 minutes, but when 
> used on a Unix server it drops the user to the Unix prompt 
> when logging them off from Universe.
> 
> I am looking for a way to completely log the user off the server.
> 
> Thanks
> 
> 
> Andy Moore
> Selima Software Ltd
> Tel: 0114 2815000
> Fax: 0114 281
> email: [EMAIL PROTECTED]
> Support: http://tracker.selima.co.uk 
> Forum: http://forum.selima.co.uk 
> ---
> u2-users mailing list
> u2-users@listserver.u2ug.org
> To unsubscribe please visit http://listserver.u2ug.org/
---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/


Re: [U2] AUTOLOGOUT

2005-07-14 Thread u2
[EMAIL PROTECTED] wrote:
> 
> Hello,
> 
> Anyone got any ideas on the autologout command on a Unix environment?

How are your users logging in to Unix?
> 
> We have it working happily on some Windows servers, set to log people
> off if they are inactive for 60 minutes, but when used on a Unix server
> it drops the user to the Unix prompt when logging them off from
> Universe.

It's actually probably working the same on both. It kicks them out of the UV/UD 
environment.

With Windows, that IS their login environment so they get kicked off the server.

With Unix, chances are it's not their login environment, so they get dropped 
back to their login. Is U2 started up from their .profile? Or do they log into 
Unix and then start U2? If it's the latter, you're stuck.

If it's the former, look at the .profile. I think it's the 'exec' command - if 
you 'exec' U2 it then replaces the .profile environment - exit U2 and you get 
kicked off the system - that's the best approach. The other option is to finish 
.profile with "exit" - that terminates the login session and will kick them 
off, but it's vulnerable (a) to deliberate tampering, and (b) a crash *could* 
leave them in Unix.
> 
> Andy Moore
> Selima Software Ltd

Cheers,
Wol
---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/


[U2] AUTOLOGOUT

2005-07-14 Thread Andy Moore
DISCLAIMER:
This email and any files transmitted with it are confidential and intended
solely for the use of the individual or entity to whom they are addressed.
If you have received this email in error, please delete it and notify
the sender immediately.  Please note that there is no guarantee that
this email or any attachment is virus free or has not been intercepted
or amended.

Hello,

Anyone got any ideas on the autologout command on a Unix environment?

We have it working happily on some Windows servers, set to log people
off if they are inactive for 60 minutes, but when used on a Unix server
it drops the user to the Unix prompt when logging them off from
Universe.

I am looking for a way to completely log the user off the server.

Thanks


Andy Moore
Selima Software Ltd
Tel: 0114 2815000
Fax: 0114 281
email: [EMAIL PROTECTED]
Support: http://tracker.selima.co.uk 
Forum: http://forum.selima.co.uk 
---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/