Note that 'SET RUN ON' won't prevent the automatic logoff if the id is
forced into a disconnected state. Only the system config statement
'Features Disconnect_Timeout Off' does that. If SET RUN was
sufficient, then that feature setting wouldn't have been added. The
purpose of SET RUN, according
Installing a new Linux VM and got this over the weekend (or actually
this morning):
DISCONNECT AT 00:00:00 CST MONDAY 12/21/09 BY SYSTEM
CONNECT= 88:51:11 VIRTCPU= 039:55.68 TOTCPU= 040:58.47
LOGOFF AT 00:15:00 CST MONDAY 12/21/09 BY SYSTEM
What can I do to prevent VM for
Frank,
When you had the Linux VM 3270 console up, how did you get out of the
console session?
Did you #cp disc?
Did you just close the emulator?
Ron
Frank M. Ramaekers wrote:
Installing a new Linux VM and got this over the weekend (or actually
this morning):
DISCONNECT AT 00:00:00 CST MONDAY
-390@VM.MARIST.EDU
Subject: Re: LOGOFF FORCED BY SYSTEM
Frank,
When you had the Linux VM 3270 console up, how did you get out of the
console session?
Did you #cp disc?
Did you just close the emulator?
Ron
Frank M. Ramaekers wrote:
Installing a new Linux VM and got this over the weekend
Sounds like you left the virtual machine up with an outstanding VM read on
the console.
Is SET RUN ON enabled? Reaching back awhile but I think that prevents this
issue?
On Mon, Dec 21, 2009 at 12:17 PM, Ron Foster at Baldor-IS
rfos...@baldor.com wrote:
Frank,
When you had the Linux VM
Subject: LOGOFF FORCED BY SYSTEM
Installing a new Linux VM and got this over the weekend (or actually
this morning):
DISCONNECT AT 00:00:00 CST MONDAY 12/21/09 BY SYSTEM
CONNECT= 88:51:11 VIRTCPU= 039:55.68 TOTCPU= 040:58.47
LOGOFF AT 00:15:00 CST MONDAY 12/21/09 BY SYSTEM
What can I do
Acres Dr.Fax: (254)741-5777
Waco, Texas 76710
-Original Message-
From: Linux on 390 Port [mailto:linux-...@vm.marist.edu] On Behalf Of Ed
Gilroy
Sent: Monday, December 21, 2009 12:25 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: LOGOFF FORCED BY SYSTEM
Sounds
.
-Original Message-
From: Linux on 390 Port [mailto:linux-...@vm.marist.edu] On Behalf Of
Frank M. Ramaekers
Sent: Monday, December 21, 2009 1:36 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: LOGOFF FORCED BY SYSTEM
Okay, I'll give that a shot
I think I'll add a #CP DISC after the IPL
Have the linux guest as secondary userid to OPERATOR
set secuser linux01 operator
From: Frank M. Ramaekers framaek...@ailife.com
To: LINUX-390@VM.MARIST.EDU
Date: 12/21/2009 10:59 AM
Subject:LOGOFF FORCED BY SYSTEM
Sent by:Linux on 390 Port
12:25 PM
Subject:Re: LOGOFF FORCED BY SYSTEM
Sent by:Linux on 390 Port LINUX-390@VM.MARIST.EDU
I usually issue a '#CP DISC', but I may have had it up (over the
weekend). It appears that we had some network issues over the weekend
because all of my other 3270 sessions were
on 390 Port [mailto:linux-...@vm.marist.edu] On Behalf Of
Eddie Chen
Sent: Monday, December 21, 2009 12:07 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: LOGOFF FORCED BY SYSTEM
Frank,
Have all your linux guests as secondary userid to operator
cp set secuser linux01 operator
you can also
11 matches
Mail list logo
