No cold start is required, that affects SPOOL files (System Data Files). 
The SYSTEM CONFIG file is not saved in an SDF.
You might want to:

1) Check for any error or warning messages on the SPOOLed console log from 
the IPL. 
2) Issue a CP Q CPDISKS and see what disk is accessed as the A-disk.
    a) Check the SYSTEM CONFIG file on that disk to ensure that it has the 
change that you made.

Mike Walter
Hewitt Associates
The opinions expressed herein are mine alone, not my employer's.





"Wandschneider, Scott" <[email protected]> 

Sent by: "The IBM z/VM Operating System" <[email protected]>
08/19/2010 11:08 AM
Please respond to
"The IBM z/VM Operating System" <[email protected]>



To
[email protected]
cc

Subject
Re: FORCED BY SYSTEM






We did not do a shutdown reipl.  We did an IPL with a warm start do we
need to do a cold start?

Thank you,

Scott


-----Original Message-----
From: The IBM z/VM Operating System [mailto:[email protected]] On
Behalf Of Riedel, Alexander
Sent: Thursday, August 19, 2010 11:05 AM
To: [email protected]
Subject: Re: FORCED BY SYSTEM

Did you used the CPSYNTAX tool to check the system config for errors?

Alexander 

-----Original Message-----
From: The IBM z/VM Operating System [mailto:[email protected]] On
Behalf Of Wandschneider, Scott
Sent: Thursday, August 19, 2010 5:45 PM
To: [email protected]
Subject: Re: FORCED BY SYSTEM

That is exactly what I did.  So I re-added it yesterday and scheduled a
IPL for last night and it still is happening.

SYS CONFIG Snippet:
  Enable                    ,      /* ENABLE THE FOLLOWING FEATURES  */

    Dynamic_I/O             ,      /* ALLOW DYNAMIC I/O CHANGES      */

    Set_Devices             ,      /* ALLOW DYNAMIC SET DEVICES      */

    Set_Dynamic_I/O         ,      /* ALLOW DYNAMIC CHANGES          */

    New_Devices_Initialized_When_Added, /* CREATE RDEV BLOCKS        */

    Set_Privclass           ,      /* ALLOW SET PRIVCLASS COMMAND    */

    Validate_Shutdown       ,      /* SYSTEM systemid is required    */

  DISCONNECT_TIMEOUT OFF    ,      /* disables the automatic logoff  */

  Retrieve                  ,      /* RETRIEVE OPTIONS               */

    Default  25             ,      /* DEFAULT.... DEFAULT IS 20      */

    Maximum  50             ,      /* MAXIMUM.... DEFAULT IS 255     */

  MaxUsers noLimit          ,      /* No limit on number of users    */


Thank you,

Scott


-----Original Message-----
From: The IBM z/VM Operating System [mailto:[email protected]] On
Behalf Of Alan Altmark
Sent: Thursday, August 19, 2010 10:36 AM
To: [email protected]
Subject: Re: FORCED BY SYSTEM

On Thursday, 08/19/2010 at 11:27 EDT, "Wandschneider, Scott" 
<[email protected]> wrote:
> We just completed an upgrade from z/VM 5.3 0602 to z/VM 5.4 0902 and
now
our 
> CMS users are being forced off the system with the following:
> 
> 10:58:32 GRAF L000F DISCONNECT SBAH     USERS = 58    FORCED BY SYSTEM
> 11:05:32 GRAF L0003 DISCONNECT JOSE     USERS = 58    FORCED BY SYSTEM
> 
> Can someone enlighten me as to what I changed or missed?  Thanks in
advance!

Did you copy the FEATURES DISCONNECT_TIMEOUT from your old SYSTEM CONFIG

to the new?  Sounds like it was OFF, but now it isn't.  (Default is 15 
minutes.)

Alan Altmark
z/VM Development
IBM Endicott

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.

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.





The information contained in this e-mail and any accompanying documents may 
contain information that is confidential or otherwise protected from 
disclosure. If you are not the intended recipient of this message, or if this 
message has been addressed to you in error, please immediately alert the sender 
by reply e-mail and then delete this message, including any attachments. Any 
dissemination, distribution or other use of the contents of this message by 
anyone other than the intended recipient is strictly prohibited. All messages 
sent to and from this e-mail address may be monitored as permitted by 
applicable law and regulations to ensure compliance with our internal policies 
and to protect our business. E-mails are not secure and cannot be guaranteed to 
be error free as they can be intercepted, amended, lost or destroyed, or 
contain viruses. You are deemed to have accepted these risks if you communicate 
with us by e-mail. 


Reply via email to