Re: How to time-out idle terminals?

["Scott Lindstrom" <SLindstrom@xxxxxxxxxx>]

If you have the ROBOT job scheduler, they throw in the command CNLIDLEJOB
for free:

                               Cancel Idle Job (CNLIDLEJOB)

      Minutes allowed idle:  . . . . .   0             0-9999
      Exempt (job) from cancel:  . . .   *NONE         Name, *NONE, *ANY
        User name: . . . . . . . . . .                 Name
                     + for more values   *NONE

      Subsystems to check: . . . . . .   *ALL          Name, *ALL
                     + for more values
      Message queue: . . . . . . . . .   QSYSOPR       Name
      Message Queue Library: . . . . .   *LIBL         Name, *LIBL


Scott Lindstrom
Pactiv Corp



                    George Kinney
                    <GKinney@nextranspo       To:     
"'midrange-l@midrange.com'" <midrange-l@midrange.com>
                    rt.com>                   cc:     (bcc: Scott 
Lindstrom/PDC/Pactiv)
                    Sent by:                  Subject:     How to time-out idle 
terminals?
                    midrange-l-admin@mi
                    drange.com


                    08/22/02 12:24 PM
                    Please respond to
                    midrange-l






This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.
--
[ Picked text/plain from multipart/alternative ]
I've been poking through the docs, but apparently missing what I need.

In a nut shell, we have a certain number of devices on our system that
provide 3270 emulation to one of our customer's mainframes. We have a
limited number of devices, and our users are too pig-headed to understand
that they must sign-off these devices when not in use. Some of the devices
are printer emulations that must remain connected at all times, the rest
are terminal emulations, and they are the problem.

Is there any way to make the terminal sessions automatically time-out
without
affecting the printer emulations?

Or is there a way to make certain user profiles time-out, without affecting
all of them?

Essentially, I have come to believe that the only way we can stop this
situation is by
booting everyone off, but I'm sick of doing it manually. (And I don't want
to kill an
active connection, just the ones that have been idle for a while.)

This will all need to happen on an old v3r7 400, if you can offer any
input,
I'd
appreciate it.

Thanks.