Re: SHUTTRAP
BTW, CP seems to accept any virtual system reset or disabled wait as a signal to remove a userid from the list of users in the SHUTDOWN Pending list. That is as I expected. I presume that cancellation is also accepted. :-) Regards, Richard Schuh -Original Message- From: The IBM z/VM Operating System [mailto:IBMVM@LISTSERV.UARK.EDU] On Behalf Of Alan Altmark Sent: Monday, July 04, 2011 8:18 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: SHUTTRAP On Monday, 07/04/2011 at 09:12 EDT, David Boyes dbo...@sinenomine.net wrote: SA22-7832-08, pg. 11-16, in the section on Warnings. There's about two sentences referring to power failure. The rest is in the SHUTTRAP source code. I said it was tiny. 8-). Indeed, and vague, too. :-) According to SHUTTRAP source, the LPAR deactivation event (Quiesce) is reflected via an unsolicited Service Signal external interrupt with event 0x1D, not a Warning machine check. So it's definitely in the not published camp. Alan Altmark Senior Managing z/VM and Linux Consultant IBM System Lab Services and Training ibm.com/systems/services/labservices office: 607.429.3323 mobile; 607.321.7556 alan_altm...@us.ibm.com IBM Endicott
Re: Where console message is stored using Operation Manager
Beg to differ. While all messages for all monitored userids are logged to Operations Manager's log on disk, recent (for various values of recent) console activity is kept in data spaces, the size of which is specifiable. That's why, for a particularly active (console-wise) userid, one can only page back so far. Actually, that can be several days for low-console-activity userids, but may be only an hour or a few for those which really pump out messages. -- Mike Harding z/VM System Support mhard...@us.ibm.com mike.b.hard...@kp.org mikehard...@mindless.com (925) 926-3179 (w) (925) 323-2070 (c) IM: VMBearDad (AIM), mbhcpcvt (Y!) The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU wrote on 07/04/2011 08:23:37 PM: From: Alan Altmark/Endicott/IBM@IBMUS To: IBMVM@LISTSERV.UARK.EDU Date: 07/04/2011 08:24 PM Subject: Re: Where console message is stored using Operation Manager Sent by: The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU On Monday, 07/04/2011 at 10:13 EDT, Lu GL Gao lu...@cn.ibm.com wrote: If we use Operation Manager on z/VM, we can supervise user's console by GOMCMD OPMGRM1 VIEWCON USER(). This console message includes historical loging messages for that user. What these messages were stored in? in spool or in storage? How can I check the space left to store these messages? They are stored on disk. Read the Log Management appendix of the Operations Manager Administration Guide. Alan Altmark Senior Managing z/VM and Linux Consultant IBM System Lab Services and Training ibm.com/systems/services/labservices office: 607.429.3323 mobile; 607.321.7556 alan_altm...@us.ibm.com IBM Endicott
Re: Where console message is stored using Operation Manager
On Tuesday, 07/05/2011 at 12:42 EDT, Michael Harding/Oakland/IBM@IBMUS wrote: Beg to differ. While all messages for all monitored userids are logged to Operations Manager's log on disk, recent (for various values of recent) console activity is kept in data spaces, the size of which is specifiable. That's why, for a particularly active (console-wise) userid, one can only page back so far. Actually, that can be several days for low-console-activity userids, but may be only an hour or a few for those which really pump out messages. We don't really differ on this. I read stored as permanently stored. The messages are permanently[1] stored on disk, but as you say, recent messages are also kept in a data space, one for each monitored user. The amount of data in a user's private data space is controlled by DEFDSPS (default 1M). I believe all of the VIEWxxx commands get their data only from the data spaces, not the log file(s). Alan Altmark Senior Managing z/VM and Linux Consultant IBM System Lab Services and Training ibm.com/systems/services/labservices office: 607.429.3323 mobile; 607.321.7556 alan_altm...@us.ibm.com IBM Endicott [1] Subject to your retention policy. Obviously you can't accumulate it on local disk forever!
Re: Where console message is stored using Operation Manager
Okay, I was keying off the OP's mention of VIEWCON. -- Mike Harding z/VM System Support mhard...@us.ibm.com mike.b.hard...@kp.org mikehard...@mindless.com (925) 926-3179 (w) (925) 323-2070 (c) IM: VMBearDad (AIM), mbhcpcvt (Y!) The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU wrote on 07/05/2011 10:15:29 AM: From: Alan Altmark/Endicott/IBM@IBMUS To: IBMVM@LISTSERV.UARK.EDU Date: 07/05/2011 10:17 AM Subject: Re: Where console message is stored using Operation Manager Sent by: The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU On Tuesday, 07/05/2011 at 12:42 EDT, Michael Harding/Oakland/IBM@IBMUS wrote: Beg to differ. While all messages for all monitored userids are logged to Operations Manager's log on disk, recent (for various values of recent) console activity is kept in data spaces, the size of which is specifiable. That's why, for a particularly active (console-wise) userid, one can only page back so far. Actually, that can be several days for low-console-activity userids, but may be only an hour or a few for those which really pump out messages. We don't really differ on this. I read stored as permanently stored. The messages are permanently[1] stored on disk, but as you say, recent messages are also kept in a data space, one for each monitored user. The amount of data in a user's private data space is controlled by DEFDSPS (default 1M). I believe all of the VIEWxxx commands get their data only from the data spaces, not the log file(s). Alan Altmark Senior Managing z/VM and Linux Consultant IBM System Lab Services and Training ibm.com/systems/services/labservices office: 607.429.3323 mobile; 607.321.7556 alan_altm...@us.ibm.com IBM Endicott [1] Subject to your retention policy. Obviously you can't accumulate it on local disk forever!
Re: Where console message is stored using Operation Manager
On Tue, 5 Jul 2011 13:15:29 -0400, Alan Altmark alan_altm...@us.ibm.com wrote: I believe all of the VIEWxxx commands get their data only from the data spaces, not the log file(s). Alan Altmark For the most part, the VIEWxxx commands only deal with data in the data space. (With the MODE(RDR) option you can even get a copy of what's in t he dataspace sent to your reader.) The one exception is VIEWLOG with the DATE(/mm/dd) option. In that case, it will always send you what's on disk, not in the data space. Tracy Dean, IBM
SUSE11 and VNC Viewer
We use VNC Viewer for the gui requirements for installing our zLinux systems and other related software. Everthing worked fine with SUSE10. SUSE11 installs fine with VNC Viewer. Once the SUSE11 installation is complete, VNC View no longer seems to function, when we attempt install other software that requires a gui interface for install. We get into the SUSE11 system, but get a blank screen, with no input capability. Has anyo ne run into this issue ? If so, how did you get around it ? Thank you, Bob
Re: SUSE11 and VNC Viewer
Hello, Sorry for the intrusion. I'm trying to get off this distribution list, but not quite sure how to proceed. Any assistance would be much appreciated. Regards, Tim On Jul 5, 2011, at 1:14 PM, Bob McCarthy bob.mccar...@custserv.com wrote: We use VNC Viewer for the gui requirements for installing our zLinux systems and other related software. Everthing worked fine with SUSE10. SUSE11 installs fine with VNC Viewer. Once the SUSE11 installation is complete, VNC View no longer seems to function, when we attempt install other software that requires a gui interface for install. We get into the SUSE11 system, but get a blank screen, with no input capability. Has anyone run into this issue ? If so, how did you get around it ? Thank you, Bob
Re: SUSE11 and VNC Viewer
You might have more luck on the Linux-390 list than IBMVM. Not sure how to help you. Works fine for us under SLES 11 SP1. Marcy -Original Message- From: The IBM z/VM Operating System [mailto:IBMVM@LISTSERV.UARK.EDU] On Behalf Of Bob McCarthy Sent: Tuesday, July 05, 2011 1:14 PM To: IBMVM@LISTSERV.UARK.EDU Subject: [IBMVM] SUSE11 and VNC Viewer We use VNC Viewer for the gui requirements for installing our zLinux systems and other related software. Everthing worked fine with SUSE10. = SUSE11 installs fine with VNC Viewer. Once the SUSE11 installation is complete, VNC View no longer seems to function, when we attempt install = other software that requires a gui interface for install. We get into the= SUSE11 system, but get a blank screen, with no input capability. Has anyo= ne run into this issue ? If so, how did you get around it ? Thank you, Bob
Re: SUSE11 and VNC Viewer
On 7/5/2011 at 04:14 PM, Bob McCarthybob.mccar...@custserv.com wrote: We use VNC Viewer for the gui requirements for installing our zLinux systems and other related software. Everthing worked fine with SUSE10. SUSE11 installs fine with VNC Viewer. Once the SUSE11 installation is complete, VNC View no longer seems to function, when we attempt install other software that requires a gui interface for install. We get into the SUSE11 system, but get a blank screen, with no input capability. Has anyone run into this issue ? If so, how did you get around it ? Is this SLES11, or SLES11 SP1? Did you run the update during the installation, or did you only install what was on the media? We have had problems with an update to SP1 causing symptoms like this. There are some workaounds, and a fix is going to be released for it. For customers with Standard or Priority subscriptions, a PTF is available. Mark Post
Re: Where console message is stored using Operation Manager
Thank you everybody here! You make me clear on this topic. Best Regards! Gao Lu (高路) I/T Specialist Global Technology Services IBM Global Services (China) Company Limited. Address:18/F, Pangu Plaza, No.27, Central North 4th Ring Road, Chaoyang District, Beijing, 100101 地址：北京市朝阳区北四环中路27号盘古大观写字楼18层，100101 BeiJing 100027, PRC Cell Phone: 15001327619 Internet ID: lu...@cn.ibm.com Tracy Dean t...@us.ibm.com Sent by: The IBM To z/VM OperatingIBMVM@LISTSERV.UARK.EDU System cc IBMVM@LISTSERV.U ARK.EDU Subject Re: Where console message is stored using Operation Manager 2011-07-06 01:27 Please respond to The IBM z/VM Operating System IBMVM@LISTSERV.U ARK.EDU On Tue, 5 Jul 2011 13:15:29 -0400, Alan Altmark alan_altm...@us.ibm.com wrote: I believe all of the VIEWxxx commands get their data only from the data spaces, not the log file(s). Alan Altmark For the most part, the VIEWxxx commands only deal with data in the data space. (With the MODE(RDR) option you can even get a copy of what's in t he dataspace sent to your reader.) The one exception is VIEWLOG with the DATE(/mm/dd) option. In that case, it will always send you what's on disk, not in the data space. Tracy Dean, IBM
CF1 can not linked as MR
I load 1st level z/VM system with EXTENT 1. Then log on MAINT user. Usually we can link cf1 by 'link * cf1 cf1 mr'. But our system response following message to this command: HCPLNM101E DASD 0CF1 forced R/O; R/O by SYSTEM; stable by SYSTEM Why SYSTEM catch it? Best Regards! Gao Lu (高路) I/T Specialist Global Technology Services IBM Global Services (China) Company Limited. Address:18/F, Pangu Plaza, No.27, Central North 4th Ring Road, Chaoyang District, Beijing, 100101 地址：北京市朝阳区北四环中路27号盘古大观写字楼18层，100101 BeiJing 100027, PRC Cell Phone: 15001327619 Internet ID: lu...@cn.ibm.com
Re: CF1 can not linked as MR
The system (by default) links and accesses the CF1 disk as its A-disk and the CF2 disk as its B-disk during IPL - when it loads the CPLOAD MODULE, and reads in and processes the SYSTEM CONFIG file. It also reads some other files at IPL, and some as-needed (e.g. LOGO files). See the CP Commands.manual for CPREL and CPACC commands (off the top of my head - names may be slightly different). Mike Walter Aon Corporation Sent from the wee keyboard of a Blackberry. From: Lu GL Gao [mailto:lu...@cn.ibm.com] Sent: Tuesday, July 05, 2011 10:17 PM To: IBMVM@LISTSERV.UARK.EDU IBMVM@LISTSERV.UARK.EDU Subject: CF1 can not linked as MR I load 1st level z/VM system with EXTENT 1. Then log on MAINT user. Usually we can link cf1 by 'link * cf1 cf1 mr'. But our system response following message to this command: HCPLNM101E DASD 0CF1 forced R/O; R/O by SYSTEM; stable by SYSTEM Why SYSTEM catch it? Best Regards! Gao Lu (高路) I/T Specialist Global Technology Services IBM Global Services (China) Company Limited. Address:18/F, Pangu Plaza, No.27, Central North 4th Ring Road, Chaoyang District, Beijing, 100101 地址：北京市朝阳区北四环中路27号盘古大观写字楼18层，100101 BeiJing 100027, PRC Cell Phone: 15001327619 Internet ID: lu...@cn.ibm.com
Re: CF1 can not linked as MR
Gao, Your SYSTEM CONFIG (on the MAINT 0CF1) probably contains: CP_Access MAINTCF1 A Normally you want to issue CPREL A before you update the parm disk, followed by a CPACC MAINT 0CF1 A to reaccess it again. But you can also change the SYSTEM CONFIG line into: CP_Access MAINTCF1 A RR That will make CP link its parm disk with RR instead of the default SR and will allow you to update the disk while CP still has it accessed. The normal single writer, multiple reader rules for CMS disks apply, so it is your foot and your gun. And don't forget to let CP know that you updated the disk by issueing a CPACC MAINT CF1 A RR. Ronald van der Laan
