CONSOLE is disconnected (it's never used, except for an emergency and to
REIPL.)
Frank M. Ramaekers Jr.
Systems Programmer MCP, MCP+I, MCSE & RHCE
American Income Life Insurance Co. Phone: (254)761-6649
1200 Wooded Acres Dr. Fax: (254)741-5777
Waco, Texas 76710
-----Original Message-----
From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On
Behalf Of fjpohlen-maill...@gmx.de
Sent: Tuesday, January 12, 2010 9:02 AM
To: IBMVM@LISTSERV.UARK.EDU
Subject: Re: FORCED BY SYSTEM
Frank,
the SET RUN ON doesn't hold the system when it enters the CP READ state.
You can set it dynamically by SEND CP vse-userid SET RUN ON. This
options cannot be queried by Q RUN. You must enter Q SET.
output of Q SET
MSG ON , WNG ON , EMSG ON , ACNT OFF, *RUN ON *
LINEDIT ON , TIMER OFF , ISAM OFF, ECMODE ON
ASSIST OFF , PAGEX OFF, AUTOPOLL OFF
IMSG ON , SMSG OFF , AFFINITY NONE , NOTRAN OFF
VMSAVE OFF, 370E OFF
STBYPASS OFF , STMULTI OFF 00/000
MIH OFF , VMCONIO OFF , CPCONIO OFF , SVCACCL OFF , CONCEAL OFF
MACHINE ESA, SVC76 CP, NOPDATA OFF, IOASSIST OFF
Do you run your VSE disconnected or logged on? I normally use dialed
devices for the vse consoles. Thus it's easy to get the console at any
vm enabled terminal, even if you are connected over a VPN.
kind regards
Franz Josef Pohlen
Frank M. Ramaekers schrieb:
>
> Exactly what are the reasons (if there is more than one) that will
> cause CP for FORCE a user off? (If more than one, it would be nice to
> have at least a reason code for the FORCE.)
>
> Will "SET RUN ON" prevent a FORCE? Why don't I see a "QUERY RUN"
> command? Is there no way to tell if "SET RUN ON" was set?
>
> Frank M. Ramaekers Jr.
>
>
>
> Systems Programmer
>
>
>
> MCP, MCP+I, MCSE & RHCE
>
> American Income Life Insurance Co.
>
>
>
> Phone: (254)761-6649
>
> 1200 Wooded Acres Dr.
>
>
>
> Fax: (254)741-5777
>
> Waco, Texas 76701
>
>
>
>
------------------------------------------------------------------------
>
> *From:* The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu]
> *On Behalf Of *Wakser, David
> *Sent:* Tuesday, January 12, 2010 8:20 AM
> *To:* IBMVM@LISTSERV.UARK.EDU
> *Subject:* Re: FORCED BY SYSTEM
>
> Frank:
>
> Probably because it was actually logged onto a terminal and had a CP
> READ (or a VM READ). Those are what the system forces off.
>
> David Wakser
>
>
------------------------------------------------------------------------
>
> *From:* The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu]
> *On Behalf Of *Frank M. Ramaekers
> *Sent:* Tuesday, January 12, 2010 9:13 AM
> *To:* IBMVM@LISTSERV.UARK.EDU
> *Subject:* FORCED BY SYSTEM
>
> I'm at a loss as to why our TEST (luckily) z/VSE system got FORCED. As
> far as I can tell it was active up until midnight:
>
> J1 0050 OC002I PARTITION NOW ACTIVE AGAIN 23:59:30 01/11/10
>
> J1 0050 OC001I PARTITION IN WAIT STATE FOR 000005 SECONDS 23:59:31
> 01/11/10
>
> J1 0050 OC002I PARTITION NOW ACTIVE AGAIN 23:59:36 01/11/10
>
> J1 0050 OC001I PARTITION IN WAIT STATE FOR 000005 SECONDS 23:59:37
> 01/11/10
>
> J1 0050 OC002I PARTITION NOW ACTIVE AGAIN 23:59:42 01/11/10
>
> J1 0050 OC001I PARTITION IN WAIT STATE FOR 000005 SECONDS 23:59:42
> 01/11/10
>
> (rest of console could have been lost because of buffering)
>
> But at midnight...
>
> 10/01/12 00:00:00 : 00:00:00 GRAF 6F07 DISCONNECT AILTEST USERS = 35
> FORCED BY SYSTEM
>
> Then 15 minutes later...
>
> 10/01/12 00:15:00 : 00:15:00 USER DSC LOGOFF AS AILTEST USERS = 34
> FORCED BY SYSTEM
>
> Was this because the virtual machine's console was (originally)
> connected to a real terminal?
>
> Frank M. Ramaekers Jr.
>
> Systems Programmer MCP, MCP+I, MCSE & RHCE
>
> American Income Life Insurance Co. Phone: (254)761-6649
>
> 1200 Wooded Acres Dr. Fax: (254)741-5777
>
> Waco, Texas 76710
>
> _____________________________________________________ This message
> contains information which is privileged and confidential and is
> solely for the use of the intended recipient. If you are not the
> intended recipient, be aware that any review, disclosure, copying,
> distribution, or use of the contents of this message is strictly
> prohibited. If you have received this in error, please destroy it
> immediately and notify us at privacy...@ailife.com.
>
> Confidentiality Note: This e-mail, including any attachment to it, may
> contain material that is confidential, proprietary, privileged and/or
> "Protected Health Information," within the meaning of the regulations
> under the Health Insurance Portability & Accountability Act as
> amended. If it is not clear that you are the intended recipient, you
> are hereby notified that you have received this transmittal in error,
> and any review, dissemination, distribution or copying of this e-mail,
> including any attachment to it, is strictly prohibited. If you have
> received this e-mail in error, please immediately return it to the
> sender and delete it from your system. Thank you.
>
> _____________________________________________________ This message
> contains information which is privileged and confidential and is
> solely for the use of the intended recipient. If you are not the
> intended recipient, be aware that any review, disclosure, copying,
> distribution, or use of the contents of this message is strictly
> prohibited. If you have received this in error, please destroy it
> immediately and notify us at privacy...@ailife.com.
_____________________________________________________
This message contains information which is privileged and confidential and is
solely for the use of the
intended recipient. If you are not the intended recipient, be aware that any
review, disclosure,
copying, distribution, or use of the contents of this message is strictly
prohibited. If you have
received this in error, please destroy it immediately and notify us at
privacy...@ailife.com.
