On Tue, 18 Aug 2009 10:39:28 -0700 Edward Jaffe edja...@phoenixsoftware.com
wrote:
:R.S. wrote:
: Edward Jaffe pisze:
: Peter, this might not be in the same area of code but...
: It would be nice to be able to associate a default SAF userid with
: consoles that have not yet logged on. That
On Wed, 19 Aug 2009 00:34:28 -0500, Barbara Nitz nitz-...@gmx.net wrote:
Besides, when a sysprog monitors the IPL, it is usually because changes were
made and we need to check if there are problems, It is really hard to sit in
front of the console and wait for the messages to scrawl by. (Hence my
.
-Original Message-
From: IBM Mainframe Discussion List
[mailto:ibm-m...@bama.ua.edu] On Behalf Of Peter Fatzinger
Sent: Monday, August 17, 2009 8:34 AM
To: IBM-MAIN@bama.ua.edu
Subject: Re: Console Logon timeout?
We may have a future opportunity to make some changes
It might be nice if there was an IPL parm / option to have the NIP messages
stop and prompt you to continue when a screen fills up similar to SAD.
With emulated consoles, the messages scroll by so fast it can be nearly
impossible to look for something you want to see except after the fact
by
Edward Jaffe pisze:
Peter Fatzinger wrote:
We may have a future opportunity to make some changes in this area of
the code. While we're in there, what would you like to see changed?
- Logoff users after period of inactivity.
- Concurrent user logon to multiple consoles.
- Anything else??
Barbara Nitz wrote:
...Unfortunately, they all come up with del=rd and rtme=1, which isn't
really nice during IPL and usually leads to WTO buffer shortages. At
which point automation issues the commands.
I just ran into the same issue. Check out the INIT LOGLIM( ) statement
in CONSOLExx
HTH,
Barbara,
You can specify RTME=1/4 in CONSOL00 - that helps a lot.
Alan
-Original Message-
From: IBM Mainframe Discussion List [mailto:ibm-m...@bama.ua.edu] On
Behalf Of Barbara Nitz
What I would really like to have is the ability to issue a K E,1 command
*without* logging on. Or
Mainframe Discussion List [mailto:ibm-m...@bama.ua.edu] On
Behalf Of Peter Fatzinger
Sent: Monday, August 17, 2009 10:34 AM
To: IBM-MAIN@bama.ua.edu
Subject: Re: Console Logon timeout?
We may have a future opportunity to make some changes in this area of
the code. While we're in there, what would you like
Barbara,
We have LOGON(AUTO) set and OPERCMDS protection on the console name as
userid. We allow control (K) and display (D) commands from the
default userid. Anything else needs a LOGON. Consoles are set RD
with roll time 1/4. What I've noticed is that at IPL time any command
can be issued
Subject
Re: Console Logon timeout?
First - I would request that the period of inactivity be configurable
and that may already be planned.
Second - I have not played with the way console autologon works (so it
may already be working this way) I would like to be able to set up the
console
I think the ability to refresh console definitions without an ipl would be
useful.
Clifford McNeill
Date: Tue, 18 Aug 2009 10:02:16 -0400
From: ken.porow...@cit.com
Subject: Re: Console Logon timeout?
To: IBM-MAIN@bama.ua.edu
Barbara,
We have LOGON(AUTO) set and OPERCMDS
I'll second that!
-Original Message-
From: IBM Mainframe Discussion List [mailto:ibm-m...@bama.ua.edu] On Behalf Of
Clifford McNeill
Sent: Tuesday, August 18, 2009 11:08 AM
To: IBM-MAIN@bama.ua.edu
Subject: Re: Console Logon timeout?
I think the ability to refresh console definitions
R.S. wrote:
Edward Jaffe pisze:
Peter, this might not be in the same area of code but...
It would be nice to be able to associate a default SAF userid with
consoles that have not yet logged on. That way, OPERCMDS resources
can be used to protect commands issued from those consoles.
On Tue, 2009-08-18 at 12:07 -0400, Clifford McNeill wrote:
I think the ability to refresh console definitions without an ipl
would be useful.
Oh very yes, that's the first thing I thought of. But I'm not sure
that's in the area that Peter was talking about.
--
David Andrews
A. Duda and Sons,
Maybe not but if he wants a wish list
I appreciate that he is asking the group rather than wait for a SHARE
requirement or some such.
Of course such requests may never be implemented but at least he's
asking.
-Original Message-
David Andrews
On Tue, 2009-08-18 at 12:07 -0400,
Edward Jaffe pisze:
R.S. wrote:
Edward Jaffe pisze:
Peter, this might not be in the same area of code but...
It would be nice to be able to associate a default SAF userid with
consoles that have not yet logged on. That way, OPERCMDS resources
can be used to protect commands issued from
On Tue, 18 Aug 2009 15:20:15 -0400, Ken Porowski
ken.porow...@cit.com wrote:
Maybe not but if he wants a wish list
I appreciate that he is asking the group rather than wait for a SHARE
requirement or some such.
Of course such requests may never be implemented but at least he's
asking.
I
On Tue, 18 Aug 2009 14:49:07 -0400, David Andrews
d...@lists.duda.com wrote:
On Tue, 2009-08-18 at 12:07 -0400, Clifford McNeill wrote:
I think the ability to refresh console definitions without an ipl
would be useful.
Oh very yes, that's the first thing I thought of. But I'm not sure
that's
On Mon, 17 Aug 2009 11:54:07 -0500, Elardus Engelbrecht
elardus.engelbre...@sita.co.za wrote:
Another possibility is to reroute console messages to another alternate
console upon logoff?
Console Switch never worked well and we were very glad that we were finally
able to get rid of it as part
Hello Peter,
A Reconnect function, or a logon here, function, when you accidentally lose
the connection.
A simple remote LOGOFF function, so that any active console user can be
logged off the system, from any other console. (of course RACF protectable!)
- Logoff users after period of
Check out the INIT LOGLIM( ) statement in CONSOLExx
Set to 1. The WTO buffer shortage I am talking about is not caused by
JES2 not being up yet (and hence not taking the syslog buffer from IPL), it is
caused by consoles defined with rtme=1 and del=rd (and yes, I know I can
change those
We may have a future opportunity to make some changes in this area of the
code. While we're in there, what would you like to see changed?
- Logoff users after period of inactivity.
- Concurrent user logon to multiple consoles.
- Anything else??
Peter Fatzinger
z/OS Core Components Development
Peter Fatzinger wrote:
We may have a future opportunity to make some changes in this area of the
code. While we're in there, what would you like to see changed?
- Logoff users after period of inactivity.
- Concurrent user logon to multiple consoles.
- Anything else??
What about this: after the
Elardus Engelbrecht pisze:
Peter Fatzinger wrote:
We may have a future opportunity to make some changes in this area of the
code. While we're in there, what would you like to see changed?
- Logoff users after period of inactivity.
- Concurrent user logon to multiple consoles.
- Anything
Peter Fatzinger wrote:
We may have a future opportunity to make some changes in this area of the
code. While we're in there, what would you like to see changed?
- Logoff users after period of inactivity.
- Concurrent user logon to multiple consoles.
- Anything else??
Peter, this might
Hi Peter,
nice to see you're still working in this area! :-)
We may have a future opportunity to make some changes in this area of the
code. While we're in there, what would you like to see changed?
- Logoff users after period of inactivity.
This should be configurable. autologoff would cause
Vernooij, CP - SPLXM wrote:
We are considering moving the oposite way: eliminate console logon.
The consoles are in a highly controlled area, where only operators come.
Passwords must be carried over from shif to shift, so they are easy to
remember, shouted through the room, widely known and
Wissink, Brad [ITSYS] bjwi...@iastate.edu wrote in message
news:d827850abe9b7143b0a8d00087200b8c02d58...@exchs018.its.iastate.edu
...
We are moving our operations staff to another building from where our
processor is. Due to this change we are looking at making operations
logon to the
AFAIK there is no built in timeout function.
We put one together with our auto ops package (Control/O from BMC) that
notices a logon then issues a logoff after 30 minutes. Timer is
cancelled if the operator performs their own logoff.
We do run with LOGON=AUTO but commands are protected (Top
29 matches
Mail list logo
