AS/400 Terminal Sleep mode
Brian
individual terminals and sleep mode (paging?).
I have been told that the AS/400 will put a terminal into sleep mode
after so many minutes if it has been idle. Now what I'm wondering is if
there is anyway to modify individual terminals/connections to not go
into sleep mode.
any ideas?
Brian
pil...@erie.net
Dennis Pearson
user profile signoff options.
QINACTITV Inactive job time-out
QDSCJOBITV Time Interval before disconnected job ends
QINACTMSGQ Inactive Job Message queue
The first command determines when the job will disconnect from the
terminal and the user will then see a sign on screen. The second
command determines when the job should end after it has been
disconnected from the terminal. The third command is tied into the
first. It determines if the job should end or be put on hold until the
user signs back on to the system.
My system is set at (in order) 75 min, 180 min, disconnect (hold).
You may be able to control a select user profile to not sign off the
system based a (user created) CL program as their exit program
in their profile. Hence the system signs them off and their
exit program returns them to their original state. Though there
is a possibility one may create a constant loop (user can not sign off).
I hope this helps.
Dennis Pearson
Coral Chemical Company
Brian wrote in message <36B8B88B...@erie.net>...
Jeff Schmehl
Setup key on terminal). Set to Disabled or 0 in some cases.
Brian
told me this was wrong.
Say your on a terminal session let's call it Session1 and walk away for 10
minutes and come back. The screen may be dim or blank but all you do is hit
a key to get it back. But when you goto run a command or anything the
terminal seems sluggish and takes longer than it usually does. It's like the
as/400 puts the resources to sleep for that terminal after so long a time and
when you go back it takes awhile to get up to full speed. I believe it's
called PAGING MODE. I would like to setup this up so a single workstation
isn't affected by it (also an ODBC connection).
-Brian
Dennis Pearson wrote:
> There are three commands within the AS/400 that handle the
> user profile signoff options.
>
> QINACTITV Inactive job time-out
> QDSCJOBITV Time Interval before disconnected job ends
> QINACTMSGQ Inactive Job Message queue
>
> The first command determines when the job will disconnect from the
> terminal and the user will then see a sign on screen. The second
> command determines when the job should end after it has been
> disconnected from the terminal. The third command is tied into the
> first. It determines if the job should end or be put on hold until the
> user signs back on to the system.
>
> My system is set at (in order) 75 min, 180 min, disconnect (hold).
>
> You may be able to control a select user profile to not sign off the
> system based a (user created) CL program as their exit program
> in their profile. Hence the system signs them off and their
> exit program returns them to their original state. Though there
> is a possibility one may create a constant loop (user can not sign off).
>
> I hope this helps.
>
> Dennis Pearson
> Coral Chemical Company
>
Dennis Pearson
As I read through your discussion it sounds just like a monitor
issue, and not an AS/400 issue. Your reference to PAGING MODE
does not ring any bells with me. Sorry!
Just curious! What type of Monitors are you using?
Every Monitor that we have goes to sleep after about 10 minutes.
In our case this has nothing to do with the AS/400. When we place
the same Monitor on a PC (not connected to the AS/400) it does
the same thing (in sleep mode in 10 minutes). We have several of
the old IBM 5291's and 5251's connected to the AS/400. These are
what our ancestors called the dumb terminals or green screen terminals.
These dumb terminals never go to sleep! If you leave them on overnight,
you can still see that green image shining through the office window
in the morning.
All of our new Monitors are energy compliant and they will reduce
to low wattage (sleep mode) after 10 minutes or so. I think Congress
pass a law requiring these Monitors to be energy compliant.
Dennis Pearson
The contents of this message express only the sender's
opinion. This message does not necessarily reflect the
policy or views of my employer, Coral Chemical Co..
All responsibility for the statements made in this
Usenet posting resides solely and completely with the
sender.
Brian wrote in message <36C03A5B...@erie.net>...
Kevin Wright
I believe that the delay to which Brian is referring is a result of all
memory associated with the job having been paged out during the long wait.
Likely portions of both the executable and PAG will have to be paged back
in in response to your initial enter or command key.
One way that I can think of for this not to occur at all is if the job is
the only one in a memory pool.
Apart from this, setting the value of the PURGE attribute of the job to
*NO, which is set up from the class via the routing entry and is changed
via CHGJOB, may have some effect on this delay depending on the demands on
the particular memory pool.
Be warned that there may also be an effect on the overall performance of
the subsystem or machine, depending on how close to the knee of the curve
performance already is. You may end up either living with the delay or
being chained to your terminal.
Hth
--
Kevin Wright
Usual disclaimer about the opinions expressed being my own
"Keep the Aspidistra flying"
Dennis Pearson <dennis_...@compuserve.comnojunk> wrote in article
<79q49a$7bf$1...@news.iconnect.net>...
> Brian
>
> As I read through your discussion it sounds just like a monitor
> issue, and not an AS/400 issue. Your reference to PAGING MODE
> does not ring any bells with me. Sorry!
>
> Just curious! What type of Monitors are you using?
>
> Every Monitor that we have goes to sleep after about 10 minutes.
... snip ...
>
> All of our new Monitors are energy compliant and they will reduce
> to low wattage (sleep mode) after 10 minutes or so. I think Congress
> pass a law requiring these Monitors to be energy compliant.
>
> Dennis Pearson
>
... snip ...
Pepe
instantaneously available for it after being a while not used. I would like
to know if that is possible, anyway. However you could give more authority
to the terminal than the rest but this could slow down everybody else.
Regards.