|
midrange.com
The only "issue" with doing it this way is that if you type the command and
you haven't actually telnet-ed from another system the connection that it
ends is your PC5250 session and leaves you with a blank screen. If you
want to sign back in you need to reconnect. Unlike ENDPASTHR which gives
you an error message if you aren't passed thru, if the user types the
command and gets a blank screen they don't necessarily know what happened.
Then again, maybe they deserve it for not paying more attention to what
they were doing.
Dave Parnin
Nishikawa Standard Company
Topeka, IN 46571
daparnin@xxxxxxxxxxxxxxxxxx
rob@xxxxxxxxx
To: Midrange Systems
Technical Discussion
02/12/2004 02:11
<midrange-l@xxxxxxxxxxxx>@SMTP@CTB
PM cc:
Please respond to Subject: Re: Diabling Telnet
Attention key
Midrange Systems
Technical
Discussion
<midrange-l@midra
nge.com>
I try to encourage our people to use
SIGNOFF ENDCNN(*YES)
to end telnet. Don't want them to get used to that attention key. In
fact I've even did the following:
CRTDUPOBJ OBJ(SIGNOFF) FROMLIB(QSYS) OBJTYPE(*CMD) NEWOBJ(ET)
CHGCMDDFT CMD(ET) NEWDFT('ENDCNN(*YES)')
ET = EndTelnet
or
'ET go home!' :-)
The attention key does come in handy if you've done something to really
lock up the session like LODPTF and filled the disk causing the machine to
IPL. But when it gets that drastic there's always using another session
on the source machine and ENDJOB *IMMED.
Rob Berendt
--
Group Dekko Services, LLC
Dept 01.073
PO Box 2000
Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com
"James H H Lampert" <jamesl@xxxxxxxxxxx>
Sent by: midrange-l-bounces@xxxxxxxxxxxx
02/12/2004 01:11 PM
Please respond to
Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
To
<midrange-l@xxxxxxxxxxxx>
cc
Fax to
Subject
Re: Diabling Telnet Attention key
> When you telnet from one AS/400 to another, pressing the Attention Key
> brings us the "Send Telnet Control Functions" menu.
>
> Does anyone know how to disable this "feature" so that pressing the
> Attention key does nothing?
>
> Setting the User Profile to ATNPGM(*NONE) does not work to disable this
> function.
Uh, and you expect the user to shut down the Telnet session how, with Attn
disabled?
You could lock the user out of the QGTVCTLF *PNLGRP. If you do this, then
Attn simply crashes the Telnet client (but leaves an orphaned connection
until the user signs off -- messy).
--
JHHL
_______________________________________________
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.
_______________________________________________
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
