Re: Odd problem with SU command
Marcy, We are connecting to Win2K3 (Not R2) AD using nss_ldap + pam_kerberos (not vintella). Works fine for us. ** [OUTPUT OF ID COMMAND OBFUSCATED TO PROTECT THE INNOCENT] linux249:/var/log # cat /etc/passwd | grep tstjrw linux249:/var/log # su - tstjrw -c id;echo $? uid=[MASKED](tstjrw) gid=[MASKED]([MASKED]) groups=[MASKED] 0 linux249:/var/log # cat /etc/passwd | grep tst000 tst000:x:[MASKED]:[MASKED]:[MASKED]:/home/tst000:/bin/bash linux249:/var/log # su - tst000 -c id;echo $? uid=[MASKED](tst000) gid=[MASKED]([MASKED]) groups=[MASKED] 0 Marcy Cortes <[EMAIL PROTECTED]> Sent by: Linux on 390 Port 10/10/2006 03:23 PM Please respond to Linux on 390 Port To LINUX-390@VM.MARIST.EDU cc Subject [LINUX-390] Odd problem with SU command Running Sles9x, SP3. We have sw installed that authenticates users against Active Directory using pam.d stuff (Vintela VAS). Those users don't have to be in /etc/passwd at all. In trying to install db2, we needed to create a local userid. Fine, no problem this is supported. But the su command returns rc 1 if the user is local and rc 0 if the user is VAS. This makes the db2icrt script fail. Was wondering if someone out there is also using an off server authentication method could check and see if it fails for them too? >From root: su (localuser) -c id echo $? su (non-localuser) -c id echo $? Return code 1 is supposed to mean su failed, but su doesn't fail - we do get the results of the command properly. The RH Intel Linux servers don't have this problem and removing the VAS calls from /etc/pam.d/su didn't seem to make a difference either. We're reporting it to support, but was hoping to narrow it down to whose support :) Marcy Cortes "This message may contain confidential and/or privileged information. If you are not the addressee or authorized to receive this for the addressee, you must not use, copy, disclose, or take any action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply e-mail and delete this message. Thank you for your cooperation." -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
cannot ping itself, ipl network setup stops
I am still struggling on ipling from tape. Fortunately I could show my OSA card to linux 390 today. But still I have network problems. During the network setup portion of the linux/390 ipl, linux pings its own ip address(gets unknown host), pings the gateway ip address(gets unknown host), pings the DNS server ip address and gets a reply. It says, I cannot ping all the required interfaces, correct the problem and stops. (Does it really stop? I do not know, because I could not see a complete ipl yet!!) Then, a few seconds later, I send the ping command to linux on the hmc console, it pings all the 3 addresses successfully. Did anybody have this problem? What should I do? Can I connect the system via TN3270 in this situation? Do I use port 23 for TN3270 to linux/390? Thanks. inci -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: Odd problem with SU command
Sorry, Meant to include this output too: cat /etc/SuSE-release SUSE LINUX Enterprise Server 9 (s390x) VERSION = 9 PATCHLEVEL = 3 Jeremy Warren <[EMAIL PROTECTED]> Sent by: Linux on 390 Port 10/11/2006 08:41 AM Please respond to Linux on 390 Port To LINUX-390@VM.MARIST.EDU cc Subject Re: [LINUX-390] Odd problem with SU command Marcy, We are connecting to Win2K3 (Not R2) AD using nss_ldap + pam_kerberos (not vintella). Works fine for us. ** [OUTPUT OF ID COMMAND OBFUSCATED TO PROTECT THE INNOCENT] linux249:/var/log # cat /etc/passwd | grep tstjrw linux249:/var/log # su - tstjrw -c id;echo $? uid=[MASKED](tstjrw) gid=[MASKED]([MASKED]) groups=[MASKED] 0 linux249:/var/log # cat /etc/passwd | grep tst000 tst000:x:[MASKED]:[MASKED]:[MASKED]:/home/tst000:/bin/bash linux249:/var/log # su - tst000 -c id;echo $? uid=[MASKED](tst000) gid=[MASKED]([MASKED]) groups=[MASKED] 0 Marcy Cortes <[EMAIL PROTECTED]> Sent by: Linux on 390 Port 10/10/2006 03:23 PM Please respond to Linux on 390 Port To LINUX-390@VM.MARIST.EDU cc Subject [LINUX-390] Odd problem with SU command Running Sles9x, SP3. We have sw installed that authenticates users against Active Directory using pam.d stuff (Vintela VAS). Those users don't have to be in /etc/passwd at all. In trying to install db2, we needed to create a local userid. Fine, no problem this is supported. But the su command returns rc 1 if the user is local and rc 0 if the user is VAS. This makes the db2icrt script fail. Was wondering if someone out there is also using an off server authentication method could check and see if it fails for them too? >From root: su (localuser) -c id echo $? su (non-localuser) -c id echo $? Return code 1 is supposed to mean su failed, but su doesn't fail - we do get the results of the command properly. The RH Intel Linux servers don't have this problem and removing the VAS calls from /etc/pam.d/su didn't seem to make a difference either. We're reporting it to support, but was hoping to narrow it down to whose support :) Marcy Cortes "This message may contain confidential and/or privileged information. If you are not the addressee or authorized to receive this for the addressee, you must not use, copy, disclose, or take any action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply e-mail and delete this message. Thank you for your cooperation." -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
LVM - can both CKD and FBA reside in same volume group?
"It's OK to use FBA disks in a LVM volume group that has CKD disks in it. If Make the FBA's LVM physical extent (PE) size the same as the CKD's PE size." - John Romanowski "But if one of them is faster, you will be slowed down to speed of slower one of course." - Marian Thanks to both of you for your responses! susan zimmerman -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Server Time Protocol support for zSeries
IBM announced today support for the server Time Protocol (STP) in the zSeries hardware. Availability of Server Time Protocol can: * Help improve time synchronization for z9 EC, z9 BC, z990, and z890 * Support a multisite sysplex distance up to 100 km * Synchronize servers and Coupling Facilities across three sites (data centers) * Coexist with an External Time Reference (ETR) network * Allow concurrent migration from an ETR network when properly configured Unfortunately, z/VM, and guest running under z/VM (e.g., Linux, z/OS), Linux in an LPAR and z/VSE can not take advantage of this new feature. Details here: http://www-306.ibm.com/common/ssi/fcgi-bin/ssialias?subtype=ca&infotype=an&appname=iSource&supplier=872&letternum=ENUSAG06-0715 DJ -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: Server Time Protocol support for zSeries
> -Original Message- > From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On > Behalf Of Dave Jones > Sent: Wednesday, October 11, 2006 10:01 AM > To: LINUX-390@VM.MARIST.EDU > Subject: Server Time Protocol support for zSeries > > > > Unfortunately, z/VM, and guest running under z/VM (e.g., Linux, z/OS), > Linux in an LPAR and z/VSE can not take advantage of this new feature. > DJ Why does Linux/zSeries need STP? I know that my home system can use XNTP to set its clock (which I do daily). Can't XNTP be used for Linux on zSeries just as it is for all other Linux platforms? If not, why not? -- John McKown Senior Systems Programmer HealthMarkets Keeping the Promise of Affordable Coverage Administrative Services Group Information Technology This message (including any attachments) contains confidential information intended for a specific individual and purpose, and its content is protected by law. If you are not the intended recipient, you should delete this message and are hereby notified that any disclosure, copying, or distribution of this transmission, or taking any action based on it, is strictly prohibited. -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: Server Time Protocol support for zSeries
That's a good question, John. As far as I know, Linux on zSeries (either VM guest or native) can use an external time source to set its clock. The real problem is that z/VM and it's guests can not use the same time source as z/OS to sync their clocks together. Consider the case where there are two LPARS in a z9-BC, one running z/OS and using STP to set its clock and the other LPAR running z/VM and Linux guests with its time set by the operator's Timex. :-) DJ McKown, John wrote: -Original Message- >>Unfortunately, z/VM, and guest running under z/VM (e.g., Linux, z/OS), Linux in an LPAR and z/VSE can not take advantage of this new feature. DJ Why does Linux/zSeries need STP? I know that my home system can use XNTP to set its clock (which I do daily). Can't XNTP be used for Linux on zSeries just as it is for all other Linux platforms? If not, why not? -- John McKown Senior Systems Programmer HealthMarkets Keeping the Promise of Affordable Coverage Administrative Services Group Information Technology -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: Server Time Protocol support for zSeries
> -Original Message- > From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On > Behalf Of Dave Jones > Sent: Wednesday, October 11, 2006 10:31 AM > To: LINUX-390@VM.MARIST.EDU > Subject: Re: Server Time Protocol support for zSeries > > > That's a good question, John. As far as I know, Linux on > zSeries (either > VM guest or native) can use an external time source to set its clock. > > The real problem is that z/VM and it's guests can not use the > same time > source as z/OS to sync their clocks together. Consider the case where > there are two LPARS in a z9-BC, one running z/OS and using STP to set > its clock and the other LPAR running z/VM and Linux guests > with its time > set by the operator's Timex. :-) > > DJ I'm still a bit confused. I know that z/VM cannot set its clock to the STP time source. But why couldn't the Linux systems under z/VM use XNTP to set their clock to the z/OS value? z/OS 1.7 can run an NTP daemon which the Linux instances should be able to use. I hope that would be "close enough". -- John McKown Senior Systems Programmer HealthMarkets Keeping the Promise of Affordable Coverage Administrative Services Group Information Technology This message (including any attachments) contains confidential information intended for a specific individual and purpose, and its content is protected by law. If you are not the intended recipient, you should delete this message and are hereby notified that any disclosure, copying, or distribution of this transmission, or taking any action based on it, is strictly prohibited. -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: Server Time Protocol support for zSeries
I'm confused as well. And it has been awhile since I played with this (early days of sysplex timers, ETR, et al.) Doesn't the z9 have a *hardware* clock *AND* a TOD clock? And isn't the hardware clock be set by the Sysplex timer? In addition to John's NTP daemon idea, can't z/VM get its time from the hardware clock and subsequently z/Linux underneath z/VM? Or am I wrong about the hardware clock and the rest is my personal pipe dream? :-( Bob Richards -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of McKown, John Sent: Wednesday, October 11, 2006 11:41 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: Server Time Protocol support for zSeries > -Original Message- > From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On > Behalf Of Dave Jones > Sent: Wednesday, October 11, 2006 10:31 AM > To: LINUX-390@VM.MARIST.EDU > Subject: Re: Server Time Protocol support for zSeries > > > That's a good question, John. As far as I know, Linux on > zSeries (either > VM guest or native) can use an external time source to set its clock. > > The real problem is that z/VM and it's guests can not use the > same time > source as z/OS to sync their clocks together. Consider the case where > there are two LPARS in a z9-BC, one running z/OS and using STP to set > its clock and the other LPAR running z/VM and Linux guests > with its time > set by the operator's Timex. :-) > > DJ I'm still a bit confused. I know that z/VM cannot set its clock to the STP time source. But why couldn't the Linux systems under z/VM use XNTP to set their clock to the z/OS value? z/OS 1.7 can run an NTP daemon which the Linux instances should be able to use. I hope that would be "close enough". -- John McKown Senior Systems Programmer HealthMarkets Keeping the Promise of Affordable Coverage Administrative Services Group Information Technology This message (including any attachments) contains confidential information intended for a specific individual and purpose, and its content is protected by law. If you are not the intended recipient, you should delete this message and are hereby notified that any disclosure, copying, or distribution of this transmission, or taking any action based on it, is strictly prohibited. -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 LEGAL DISCLAIMER The information transmitted is intended solely for the individual or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of or taking action in reliance upon this information by persons or entities other than the intended recipient is prohibited. If you have received this email in error please contact the sender and delete the material from any computer. Seeing Beyond Money is a service mark of SunTrust Banks, Inc. [ST:XCL] -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: Server Time Protocol support for zSeries
Hi John, it is possible to use XNTP to sync the clock of the Linux boxes, but the VM clock will not be updated, if I'm right. On 10/11/06, McKown, John <[EMAIL PROTECTED]> wrote: But why couldn't the Linux systems under z/VM use XNTP to set their clock to the z/OS value? z/OS 1.7 can run an NTP daemon which the Linux instances should be able to use. I hope that would be "close enough". -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: Server Time Protocol support for zSeries
> -Original Message- > From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On > Behalf Of Dominic Coulombe > Sent: Wednesday, October 11, 2006 10:53 AM > To: LINUX-390@VM.MARIST.EDU > Subject: Re: Server Time Protocol support for zSeries > > > Hi John, > > it is possible to use XNTP to sync the clock of the Linux > boxes, but the VM > clock will not be updated, if I'm right. Yes, I think that is right. But it appears that I might at least be able to get my z/OS and z/Linux instances to agree about what time it is. But z/VM and z/VSE are still left in the "dark ages". OK, everybody sing along: "Does anybody know what time it really is? Does anybody really care? ..." (old rock song) -- John McKown Senior Systems Programmer HealthMarkets Keeping the Promise of Affordable Coverage Administrative Services Group Information Technology This message (including any attachments) contains confidential information intended for a specific individual and purpose, and its content is protected by law. If you are not the intended recipient, you should delete this message and are hereby notified that any disclosure, copying, or distribution of this transmission, or taking any action based on it, is strictly prohibited. -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: Server Time Protocol support for zSeries
From a RedBook I just downloaded (Server Time Protocol Planning Guide sg247280.pdf). "The z/VM(r) operating system does not support STP or the Sysplex Timer. It can, however, tolerate their existence. That is, if z/VM is running on an STP-enabled server or on a server attached to the Sysplex Timer, z/VM continues to operate normally and has no awareness of STP or the Sysplex Timer. The servers TOD is synchronized to STP or the Sysplex Timer by the LPAR LIC. The logical partition has a logical TOD offset from the processor TOD, which may be set by z/VM during IPL. If a synchronization check occurs, the LPAR LIC adjusts the logical TOD offset for each logical partition. To zero out the offset, the logical partition must be deactivated and activated again." Paul Feller AIT Mainframe Technical Support [EMAIL PROTECTED] (319)-355-7824 -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Richards.Bob Sent: Wednesday, October 11, 2006 10:49 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: Server Time Protocol support for zSeries I'm confused as well. And it has been awhile since I played with this (early days of sysplex timers, ETR, et al.) Doesn't the z9 have a *hardware* clock *AND* a TOD clock? And isn't the hardware clock be set by the Sysplex timer? In addition to John's NTP daemon idea, can't z/VM get its time from the hardware clock and subsequently z/Linux underneath z/VM? Or am I wrong about the hardware clock and the rest is my personal pipe dream? :-( Bob Richards -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of McKown, John Sent: Wednesday, October 11, 2006 11:41 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: Server Time Protocol support for zSeries > -Original Message- > From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of > Dave Jones > Sent: Wednesday, October 11, 2006 10:31 AM > To: LINUX-390@VM.MARIST.EDU > Subject: Re: Server Time Protocol support for zSeries > > > That's a good question, John. As far as I know, Linux on zSeries > (either VM guest or native) can use an external time source to set its > clock. > > The real problem is that z/VM and it's guests can not use the same > time source as z/OS to sync their clocks together. Consider the case > where there are two LPARS in a z9-BC, one running z/OS and using STP > to set its clock and the other LPAR running z/VM and Linux guests with > its time set by the operator's Timex. :-) > > DJ I'm still a bit confused. I know that z/VM cannot set its clock to the STP time source. But why couldn't the Linux systems under z/VM use XNTP to set their clock to the z/OS value? z/OS 1.7 can run an NTP daemon which the Linux instances should be able to use. I hope that would be "close enough". -- John McKown Senior Systems Programmer HealthMarkets Keeping the Promise of Affordable Coverage Administrative Services Group Information Technology This message (including any attachments) contains confidential information intended for a specific individual and purpose, and its content is protected by law. If you are not the intended recipient, you should delete this message and are hereby notified that any disclosure, copying, or distribution of this transmission, or taking any action based on it, is strictly prohibited. -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 LEGAL DISCLAIMER The information transmitted is intended solely for the individual or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of or taking action in reliance upon this information by persons or entities other than the intended recipient is prohibited. If you have received this email in error please contact the sender and delete the material from any computer. Seeing Beyond Money is a service mark of SunTrust Banks, Inc. [ST:XCL] -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: Server Time Protocol support for zSeries
The only use case I'm aware of where standard NTP usage is not accurate enough, but asking for ETR or STP usage is when you want Linux to participate in an XRC asynchronous replication scheme *and* you have a requirement for building XRC time consistency groups across multiple OS images. Those might either be homogeneous Linux or heterogenous Linux and z/OS environments where the z/OS data mover replicates data based on TOD timestamps and you can't tolerate time inconsistency in case of an outage. Best regards, Ingo -- Ingo Adlung, STSM, System z Linux and Virtualization Architecture mail: [EMAIL PROTECTED] - phone: +49-7031-16-4263 Linux on 390 Port wrote on 11.10.2006 17:40:42: > > -Original Message- > > From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On > > Behalf Of Dave Jones > > Sent: Wednesday, October 11, 2006 10:31 AM > > To: LINUX-390@VM.MARIST.EDU > > Subject: Re: Server Time Protocol support for zSeries > > > > > > That's a good question, John. As far as I know, Linux on > > zSeries (either > > VM guest or native) can use an external time source to set its clock. > > > > The real problem is that z/VM and it's guests can not use the > > same time > > source as z/OS to sync their clocks together. Consider the case where > > there are two LPARS in a z9-BC, one running z/OS and using STP to set > > its clock and the other LPAR running z/VM and Linux guests > > with its time > > set by the operator's Timex. :-) > > > > DJ > > I'm still a bit confused. I know that z/VM cannot set its clock to the > STP time source. But why couldn't the Linux systems under z/VM use XNTP > to set their clock to the z/OS value? z/OS 1.7 can run an NTP daemon > which the Linux instances should be able to use. I hope that would be > "close enough". > > -- > John McKown > Senior Systems Programmer > HealthMarkets > Keeping the Promise of Affordable Coverage > Administrative Services Group > Information Technology > > This message (including any attachments) contains confidential > information intended for a specific individual and purpose, and its > content is protected by law. If you are not the intended recipient, you > should delete this message and are hereby notified that any disclosure, > copying, or distribution of this transmission, or taking any action > based on it, is strictly prohibited. > > > -- > For LINUX-390 subscribe / signoff / archive access instructions, > send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit > http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: Server Time Protocol support for zSeries
On 10/11/06, McKown, John <[EMAIL PROTECTED]> wrote: Why does Linux/zSeries need STP? I know that my home system can use XNTP to set its clock (which I do daily). Can't XNTP be used for Linux on zSeries just as it is for all other Linux platforms? If not, why not? I did some work on that in the past. The biggest concern I think is that the way this works in the kernel causes extra work that keeps the server in queue even when it does not have real work, so it affects scalability of the configuration. The quality of the solution is also not very good in a virtualized environment (the hardware TOD is more stable than XNTP can achieve with shared CPU's - and who runs dedicated CPU on zSeries). http://www.vm.ibm.com/events/nl77.pdf When the zSeries TOD is set by the Operator's $5 Mickey Mouse watch, it will be different from other systems that use NTP to keep their clock synchronized. Stable, but different. For some applications this may be a problem, for many sysadmin things it is a nuisance. Suppose your TOD (and z/VM) are 1 minute early. When you start your Linux server with XNTP, it will probably yank the clock backwards short after startup. Ask Neale what this does to the 'make' you already started... My suggestion has always been to get a 9037-2 and use that to set the hardware TOD at POR and let it steer the clock (so it will make the TOD run a weeny bit faster or slower to catch up). Even then, there was confusion in how z/VM supports that. The fact is that a z/VM system *can* enjoy the fact that the clock is kept in synch, it just did not support the protocol that makes it aware of when such corrections are made, so you may not understand why the same job took more or less time than before. For the 9037-2 the maximum steering was 10 ppm, so if your program runs for a day you may be up to 1 second short. From what I understand of the announcement, it appears to me this is sort of the built-in version and uses other references than a dial-up to Boulder. If that's correct, then z/VM and Linux would still be able to take advantage in the same way. But I might need to spend more time reading (no pun intended). Rob -- Rob van der Heij Velocity Software, Inc http://velocitysoftware.com/ -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: Server Time Protocol support for zSeries
Ingo, I am a GDPS/XRC environment and I *will* want Linux to participate there. What is the answer or issues I face? Bob Richards -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Ingo Adlung Sent: Wednesday, October 11, 2006 12:05 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: Server Time Protocol support for zSeries The only use case I'm aware of where standard NTP usage is not accurate enough, but asking for ETR or STP usage is when you want Linux to participate in an XRC asynchronous replication scheme *and* you have a requirement for building XRC time consistency groups across multiple OS images. Those might either be homogeneous Linux or heterogenous Linux and z/OS environments where the z/OS data mover replicates data based on TOD timestamps and you can't tolerate time inconsistency in case of an outage. Best regards, Ingo -- Ingo Adlung, STSM, System z Linux and Virtualization Architecture mail: [EMAIL PROTECTED] - phone: +49-7031-16-4263 Linux on 390 Port wrote on 11.10.2006 17:40:42: > > -Original Message- > > From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On > > Behalf Of Dave Jones > > Sent: Wednesday, October 11, 2006 10:31 AM > > To: LINUX-390@VM.MARIST.EDU > > Subject: Re: Server Time Protocol support for zSeries > > > > > > That's a good question, John. As far as I know, Linux on > > zSeries (either > > VM guest or native) can use an external time source to set its clock. > > > > The real problem is that z/VM and it's guests can not use the > > same time > > source as z/OS to sync their clocks together. Consider the case where > > there are two LPARS in a z9-BC, one running z/OS and using STP to set > > its clock and the other LPAR running z/VM and Linux guests > > with its time > > set by the operator's Timex. :-) > > > > DJ > > I'm still a bit confused. I know that z/VM cannot set its clock to the > STP time source. But why couldn't the Linux systems under z/VM use XNTP > to set their clock to the z/OS value? z/OS 1.7 can run an NTP daemon > which the Linux instances should be able to use. I hope that would be > "close enough". > > -- > John McKown > Senior Systems Programmer > HealthMarkets > Keeping the Promise of Affordable Coverage > Administrative Services Group > Information Technology > > This message (including any attachments) contains confidential > information intended for a specific individual and purpose, and its > content is protected by law. If you are not the intended recipient, you > should delete this message and are hereby notified that any disclosure, > copying, or distribution of this transmission, or taking any action > based on it, is strictly prohibited. > > > -- > For LINUX-390 subscribe / signoff / archive access instructions, > send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit > http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 LEGAL DISCLAIMER The information transmitted is intended solely for the individual or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of or taking action in reliance upon this information by persons or entities other than the intended recipient is prohibited. If you have received this email in error please contact the sender and delete the material from any computer. Seeing Beyond Money is a service mark of SunTrust Banks, Inc. [ST:XCL] -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: Server Time Protocol support for zSeries
Bob, including Linux in a GDPS/XRC environment is generally fine, also without ETR or STP support for time synchronization. As far as I can see you only have the need for a data consistency group throughout multiple Linux images or between Linux and z/OS if you have transactional data in your multi-tier setup that requires time consistency in case of an outage for proper rollback processing. Remember your respective logs get (implicitly) synchronized through the z/OS data mover based on the time stamps. With the logs in case of an outage getting out of sync due to time inconsistency (one side thinks the 2-phase commit completed successfully and the other side perhaps not even finding the transaction it in its logs at all) the recovery process is getting more "complicated" ... However, please be aware that this becomes an issue *only* if the LPAR hypervisor can't adjust the time transparently (which it usually does) and therefore depends on OS collaboration. You may call this paranoia, but it is real. Without OS support for respective machine checks the hypervisor is required to virtualize the TOD for the OS not participating and thus the respective OS images start working on different TOD values. Therewith what used to be a consistency group will show a time shift between images. Hence all OS images that have the requirement for a consistency group (as outlined above) better collaborate on ETR/STP time synchronization. We are working to provide ETR support asap, but currently this anticipated support is limited to LPAR only, as z/VM doesn't provide the required guest support, yet. STP will follow. Best regards, Ingo -- Ingo Adlung, STSM, System z Linux and Virtualization Architecture mail: [EMAIL PROTECTED] - phone: +49-7031-16-4263 Linux on 390 Port wrote on 11.10.2006 18:11:51: > Ingo, > > I am a GDPS/XRC environment and I *will* want Linux to participate > there. What is the answer or issues I face? > > Bob Richards > > > > -Original Message- > From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of > Ingo Adlung > Sent: Wednesday, October 11, 2006 12:05 PM > To: LINUX-390@VM.MARIST.EDU > Subject: Re: Server Time Protocol support for zSeries > > The only use case I'm aware of where standard NTP usage is not > accurate enough, but asking for ETR or STP usage is when you want > Linux to participate in an XRC asynchronous replication scheme *and* > you have a requirement for building XRC time consistency groups > across multiple OS images. Those might either be homogeneous Linux > or heterogenous Linux and z/OS environments where the z/OS data > mover replicates data based on TOD timestamps and you can't tolerate > time inconsistency in case of an outage. > > Best regards, > Ingo > > -- > Ingo Adlung, > STSM, System z Linux and Virtualization Architecture > mail: [EMAIL PROTECTED] - phone: +49-7031-16-4263 > > Linux on 390 Port wrote on 11.10.2006 > 17:40:42: > > > > -Original Message- > > > From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On > > > Behalf Of Dave Jones > > > Sent: Wednesday, October 11, 2006 10:31 AM > > > To: LINUX-390@VM.MARIST.EDU > > > Subject: Re: Server Time Protocol support for zSeries > > > > > > > > > That's a good question, John. As far as I know, Linux on > > > zSeries (either > > > VM guest or native) can use an external time source to set its > clock. > > > > > > The real problem is that z/VM and it's guests can not use the > > > same time > > > source as z/OS to sync their clocks together. Consider the case > where > > > there are two LPARS in a z9-BC, one running z/OS and using STP to > set > > > its clock and the other LPAR running z/VM and Linux guests > > > with its time > > > set by the operator's Timex. :-) > > > > > > DJ > > > > I'm still a bit confused. I know that z/VM cannot set its clock to the > > STP time source. But why couldn't the Linux systems under z/VM use > XNTP > > to set their clock to the z/OS value? z/OS 1.7 can run an NTP daemon > > which the Linux instances should be able to use. I hope that would be > > "close enough". > > > > -- > > John McKown > > Senior Systems Programmer > > HealthMarkets > > Keeping the Promise of Affordable Coverage > > Administrative Services Group > > Information Technology > > > > This message (including any attachments) contains confidential > > information intended for a specific individual and purpose, and its > > content is protected by law. If you are not the intended recipient, > you > > should delete this message and are hereby notified that any > disclosure, > > copying, or distribution of this transmission, or taking any action > > based on it, is strictly prohibited. > > > > > > -- > > For LINUX-390 subscribe / signoff / archive access instructions, > > send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 > or > visit > > http://www.marist.edu/htbin/wlvindex?LINUX-390 > > -
from a local linux discussion group: Hans Reiser arrested for murdering his wife.
wow: Oakland police today arrested the estranged husband of 31-year-old Nina "Nenasha" Reiser on charges of murder even though in the month since she vanished, investigators have found no trace of her body. Hans Reiser, a man who has recently refused to cooperate with investigators, was arrested today along with two additional unidentified people around 11 a.m. at an acquaintance's home in the 6900 block of Simson Street, according to police. The arrest comes a day after police and FBI agents searched Reiser's Exeter Drive home for a second time, and while police today did not reveal specific evidence found Monday night, they did say that they served a search warrant for documents as well as forensic and biological evidence. Cadaver dogs were also used in the search. Police expressed confidence that the district attorney's office would arraign Reiser on charges for murder even without the discovery of Nina Reiser's body. -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: Server Time Protocol support for zSeries
> My suggestion has always been to get a 9037-2 In my understand, the STP was designed to keep a pool of z9 machines syncronized without the need of a 9037, and it is fully supported by the newer zOS. One of the z9 can be syncronized with a External server (or not) and act like the 9037 for the others. When one of the machines in the pool isn't a Z9 (without the STP), the 9037 stil is necessary. Into each machine, doesn't matter for the LPARs if the clock was externally syncronized or not. _ Clóvis Pereira IBM Brasil Global Technology Services/SW Services Tel: 55-11-2132-3399 Internet: [EMAIL PROTECTED] -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: from a local linux discussion group: Hans Reiser arrested for murdering his wife.
Very sad for the children. -- No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.1.408 / Virus Database: 268.13.2/471 - Release Date: 10/10/2006 -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: Server Time Protocol support for zSeries
> -Original Message- > From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On > Behalf Of Clovis Pereira > Sent: Wednesday, October 11, 2006 12:22 PM > To: LINUX-390@VM.MARIST.EDU > Subject: Re: Server Time Protocol support for zSeries > > > > My suggestion has always been to get a 9037-2 > > In my understand, the STP was designed to keep a pool of z9 machines > syncronized without the need of a 9037, and it is fully > supported by the > newer zOS. > One of the z9 can be syncronized with a External server (or > not) and act > like the 9037 for the others. > When one of the machines in the pool isn't a Z9 (without the > STP), the 9037 > stil is necessary. > Into each machine, doesn't matter for the LPARs if the clock > was externally > syncronized or not. One nice thing in the announcement is that they are back-porting the STP hardware/microcode/whatever so that the z890 and z990 machines can also do STP as well as the z9 machines. -- John McKown Senior Systems Programmer HealthMarkets Keeping the Promise of Affordable Coverage Administrative Services Group Information Technology This message (including any attachments) contains confidential information intended for a specific individual and purpose, and its content is protected by law. If you are not the intended recipient, you should delete this message and are hereby notified that any disclosure, copying, or distribution of this transmission, or taking any action based on it, is strictly prohibited. -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: from a local linux discussion group: Hans Reiser arrested for murdering his wife.
Is this the guy that developed the Reisner file system for Linux? DJ David Kreuter wrote: wow: Oakland police today arrested the estranged husband of 31-year-old Nina "Nenasha" Reiser on charges of murder even though in the month since she vanished, investigators have found no trace of her body. Hans Reiser, a man who has recently refused to cooperate with investigators, was arrested today along with two additional unidentified people around 11 a.m. at an acquaintance's home in the 6900 block of Simson Street, according to police. The arrest comes a day after police and FBI agents searched Reiser's Exeter Drive home for a second time, and while police today did not reveal specific evidence found Monday night, they did say that they served a search warrant for documents as well as forensic and biological evidence. Cadaver dogs were also used in the search. Police expressed confidence that the district attorney's office would arraign Reiser on charges for murder even without the discovery of Nina Reiser's body. -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: Server Time Protocol support for zSeries
On Wednesday, 10/11/2006 at 06:09 ZE2, Rob van der Heij <[EMAIL PROTECTED]> wrote: > From what I understand of the announcement, it appears to me this is > sort of the built-in version and uses other references than a dial-up > to Boulder. If that's correct, then z/VM and Linux would still be able > to take advantage in the same way. Correct. Think of it as a built-in 9037, with a variety of external synchronization options, including NTP. Alan Altmark z/VM Development IBM Endicott -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: cannot ping itself, ipl network setup stops
Yes, the install process stops at that point. If you start seeing the network setup scripts run, your IPL is already complete. You can restart the installer by re-executing /linuxrc. You will want to connect to the system via SSH, not TN3270, once the network is up and running. Trying to run the setup command via TN3270 will not be very intelligible for you. Mark Post -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of inci yeker selkan Sent: Wednesday, October 11, 2006 8:22 AM To: LINUX-390@VM.MARIST.EDU Subject: cannot ping itself, ipl network setup stops I am still struggling on ipling from tape. Fortunately I could show my OSA card to linux 390 today. But still I have network problems. During the network setup portion of the linux/390 ipl, linux pings its own ip address(gets unknown host), pings the gateway ip address(gets unknown host), pings the DNS server ip address and gets a reply. It says, I cannot ping all the required interfaces, correct the problem and stops. (Does it really stop? I do not know, because I could not see a complete ipl yet!!) Then, a few seconds later, I send the ping command to linux on the hmc console, it pings all the 3 addresses successfully. Did anybody have this problem? What should I do? Can I connect the system via TN3270 in this situation? Do I use port 23 for TN3270 to linux/390? Thanks. inci -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: from a local linux discussion group: Hans Reiser arrested for murdering his wife.
Yes, it is. On 10/11/06, Dave Jones <[EMAIL PROTECTED]> wrote: Is this the guy that developed the Reisner file system for Linux? DJ -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: from a local linux discussion group: Hans Reiser arrested for murdering his wife.
> Is this the guy that developed the Reisner file system for Linux? Yes. -- No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.1.408 / Virus Database: 268.13.2/471 - Release Date: 10/10/2006 -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: from a local linux discussion group: Hans Reiser arrested for murdering his wife.
yup Dave Jones wrote: Is this the guy that developed the Reisner file system for Linux? DJ David Kreuter wrote: wow: Oakland police today arrested the estranged husband of 31-year-old Nina "Nenasha" Reiser on charges of murder even though in the month since she vanished, investigators have found no trace of her body. Hans Reiser, a man who has recently refused to cooperate with investigators, was arrested today along with two additional unidentified people around 11 a.m. at an acquaintance's home in the 6900 block of Simson Street, according to police. The arrest comes a day after police and FBI agents searched Reiser's Exeter Drive home for a second time, and while police today did not reveal specific evidence found Monday night, they did say that they served a search warrant for documents as well as forensic and biological evidence. Cadaver dogs were also used in the search. Police expressed confidence that the district attorney's office would arraign Reiser on charges for murder even without the discovery of Nina Reiser's body. -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: from a local linux discussion group: Hans Reiser arrested for murdering his wife.
One in the same... He has been separated from his wife since 04, and she was awarded custody of their kids. He was pretty upset about it. They were in the middle of divorce proceedings. Paul >>> [EMAIL PROTECTED] 10/11/06 1:53 PM >>> Is this the guy that developed the Reisner file system for Linux? DJ David Kreuter wrote: > wow: > > Oakland police today arrested the estranged husband of 31-year-old Nina > "Nenasha" Reiser on charges of murder even though in the month since she > vanished, investigators have found no trace of her body. > > > > Hans Reiser, a man who has recently refused to cooperate with > investigators, was arrested today along with two additional unidentified > people around 11 a.m. at an acquaintance's home in the 6900 block of > Simson Street, according to police. > > > > The arrest comes a day after police and FBI agents searched Reiser's > Exeter Drive home for a second time, and while police today did not > reveal specific evidence found Monday night, they did say that they > served a search warrant for documents as well as forensic and biological > evidence. Cadaver dogs were also used in the search. > > > > Police expressed confidence that the district attorney's office would > arraign Reiser on charges for murder even without the discovery of Nina > Reiser's body. -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: Server Time Protocol support for zSeries
On 10/11/06, Alan Altmark <[EMAIL PROTECTED]> wrote: > From what I understand of the announcement, it appears to me this is > sort of the built-in version and uses other references than a dial-up > to Boulder. If that's correct, then z/VM and Linux would still be able > to take advantage in the same way. Correct. Think of it as a built-in 9037, with a variety of external synchronization options, including NTP. Which means that z/VM for most practical purposes can take advantage of a TOD that runs on time, but z/VM just does not know about how good it is? If so, would it not be nice to say so in the announcement? Or is this Chuckie's evil twin who works in another department of the company and still thinks it is good to suggest z/VM development has stopped years ago and we don't bother to support new stuff ? Rob -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: Server Time Protocol support for zSeries
This agrees with what we see in our shop. CP QUERY TIME for VM systems in LPAR's on our 3 z9's is the same, at least to the nearest second. Our one 2064 in basic mode is off by 4 seconds. We're not doing XRC or anything like that, so this is fine for us. Dennis There are 10 kinds of people in the world; those that understand binary and those that don't. -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Feller, Paul Sent: Wednesday, October 11, 2006 08:58 To: LINUX-390@VM.MARIST.EDU Subject: Re: Server Time Protocol support for zSeries From a RedBook I just downloaded (Server Time Protocol Planning Guide sg247280.pdf). "The z/VM(r) operating system does not support STP or the Sysplex Timer. It can, however, tolerate their existence. That is, if z/VM is running on an STP-enabled server or on a server attached to the Sysplex Timer, z/VM continues to operate normally and has no awareness of STP or the Sysplex Timer. The servers TOD is synchronized to STP or the Sysplex Timer by the LPAR LIC. The logical partition has a logical TOD offset from the processor TOD, which may be set by z/VM during IPL. If a synchronization check occurs, the LPAR LIC adjusts the logical TOD offset for each logical partition. To zero out the offset, the logical partition must be deactivated and activated again." Paul Feller AIT Mainframe Technical Support [EMAIL PROTECTED] (319)-355-7824 -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Richards.Bob Sent: Wednesday, October 11, 2006 10:49 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: Server Time Protocol support for zSeries I'm confused as well. And it has been awhile since I played with this (early days of sysplex timers, ETR, et al.) Doesn't the z9 have a *hardware* clock *AND* a TOD clock? And isn't the hardware clock be set by the Sysplex timer? In addition to John's NTP daemon idea, can't z/VM get its time from the hardware clock and subsequently z/Linux underneath z/VM? Or am I wrong about the hardware clock and the rest is my personal pipe dream? :-( Bob Richards -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of McKown, John Sent: Wednesday, October 11, 2006 11:41 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: Server Time Protocol support for zSeries > -Original Message- > From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of > Dave Jones > Sent: Wednesday, October 11, 2006 10:31 AM > To: LINUX-390@VM.MARIST.EDU > Subject: Re: Server Time Protocol support for zSeries > > > That's a good question, John. As far as I know, Linux on zSeries > (either VM guest or native) can use an external time source to set its > clock. > > The real problem is that z/VM and it's guests can not use the same > time source as z/OS to sync their clocks together. Consider the case > where there are two LPARS in a z9-BC, one running z/OS and using STP > to set its clock and the other LPAR running z/VM and Linux guests with > its time set by the operator's Timex. :-) > > DJ I'm still a bit confused. I know that z/VM cannot set its clock to the STP time source. But why couldn't the Linux systems under z/VM use XNTP to set their clock to the z/OS value? z/OS 1.7 can run an NTP daemon which the Linux instances should be able to use. I hope that would be "close enough". -- John McKown Senior Systems Programmer HealthMarkets Keeping the Promise of Affordable Coverage Administrative Services Group Information Technology This message (including any attachments) contains confidential information intended for a specific individual and purpose, and its content is protected by law. If you are not the intended recipient, you should delete this message and are hereby notified that any disclosure, copying, or distribution of this transmission, or taking any action based on it, is strictly prohibited. -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 LEGAL DISCLAIMER The information transmitted is intended solely for the individual or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of or taking action in reliance upon this information by persons or entities other than the intended recipient is prohibited. If you have received this email in error please contact the sender and delete the material from any computer. Seeing Beyond Money is a service mark of SunTrust Banks, Inc. [ST:XCL] -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 --
Re: Server Time Protocol support for zSeries
On 10/11/06, Ingo Adlung <[EMAIL PROTECTED]> wrote: We are working to provide ETR support asap, but currently this anticipated support is limited to LPAR only, as z/VM doesn't provide the required guest support, yet. STP will follow. No doubt the lack of my imagination, but I think it would be interesting to know which applications would take advantage of such new function. I was not aware that people would make roll-back based on TOD clock. All I have seen is where units of work are separated by in-band markers and roll-back or commit being locked on those. The "consistency groups" is when two different parallel sysplex configurations would both have the need to run on slightly different time, and both need a Linux virtual machine on the same z/VM image to run in synch with them? If it were only one, you could have z/VM run along with the same clock and you would be fine. If so, that might not be the first problem many of us run into, I would think. Rob -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: LVM - can both CKD and FBA reside in same volume group?
> Once a Linux image is built, if additional space is needed we're hoping > we can simply add the larger SCSI disk to the volume group. First comment is that Mother's Rule #1 (mix not data and system code lest peril ensue) applies here. It is a much better idea IMHO to have separate LVM spaces for data and system code. > I am > having a hard time finding information on mixing disk architecture in > an LVM. Since the CKD is emulating FBA, does LVM even care that it is > CKD as opposed to FBA? If you are truly running the box as FCP SCSI, then there is no CKD at all. VM emulates 9336 FBA devices on pure SCSI setups if you use emulation at all. FCP SCSI LUNs do not necessarily have emulation enabled -- you can choose to not use mainframe device emulation entirely if you have FCP storage, but you cannot manage that space with DIRMAINT or similar tools. > Is anyone out there doing this? It's probably wiser not to mix emulated FBA and true FCP SCSI partitions in the same LVM. -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: Server Time Protocol support for zSeries
> > Why does Linux/zSeries need STP? I know that my home system can use XNTP > > to set its clock (which I do daily). Can't XNTP be used for Linux on > > zSeries just as it is for all other Linux platforms? If not, why not? NTP causes every guest to wake up periodically to process time updates, which waste resources (NTP is not a particularly lightweight protocol). Not allowing VM to participate forces Linux to handle this individually (rather than doing it in common and allowing the Linuxen to handle it from the TOD clock offsets maintained by CP). -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: Server Time Protocol support for zSeries
Sure, it wastes a little, but it doesn't look that bad here (we have to run NTP on every server to sync security tickets and stuff). Velocity reports the idle ones at 0.01% of a CPU, and that's with their agent presumbaly doing a little stuff too). Marcy Cortes "This message may contain confidential and/or privileged information. If you are not the addressee or authorized to receive this for the addressee, you must not use, copy, disclose, or take any action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply e-mail and delete this message. Thank you for your cooperation." -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of David Boyes Sent: Wednesday, October 11, 2006 12:46 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: [LINUX-390] Server Time Protocol support for zSeries > > Why does Linux/zSeries need STP? I know that my home system can use XNTP > > to set its clock (which I do daily). Can't XNTP be used for Linux on > > zSeries just as it is for all other Linux platforms? If not, why not? NTP causes every guest to wake up periodically to process time updates, which waste resources (NTP is not a particularly lightweight protocol). Not allowing VM to participate forces Linux to handle this individually (rather than doing it in common and allowing the Linuxen to handle it from the TOD clock offsets maintained by CP). -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: from a local linux discussion group: Hans Reiser arrested for murdering his wife.
On Oct 11, 2006, at 10:53 AM, Dave Jones wrote: Is this the guy that developed the Reisner file system for Linux? Yup. -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: Server Time Protocol support for zSeries
> No doubt the lack of my imagination, but I think it would be > interesting to know which applications would take advantage of such > new function. I was not aware that people would make roll-back based > on TOD clock. All I have seen is where units of work are separated by > in-band markers and roll-back or commit being locked on those. > Rob One area might be with functions that depend on Kerberos (where coordinated and accurate time is part of the anti-replay function for a transaction) David Boyes Sine Nomine Associates -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: Server Time Protocol support for zSeries
> Sure, it wastes a little, but ... When writing "The Virtualization Cookbook", http://linuxvm.org/present/misc/virt-cookbook-2.pdf, we took Rob's suggestion to save a few cycles by doing the following: 1) Have one zLinux server run the NTP server, xntpd, syncing to servers on the Internet becoming stratum n+1 2) Have all other zLinux servers sync to the first one, becoming stratum n+2, once a night with a cron script: # cat /etc/cron.daily/set-clock #!/bin/bash # Adjust the clock /usr/sbin/ntpd -q The /etc/ntp.conf file on each simply has a single "server" statement pointing to server (1). "Mike MacIsaac" <[EMAIL PROTECTED]> (845) 433-7061 -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: Server Time Protocol support for zSeries
Michael MacIsaac wrote: Sure, it wastes a little, but ... When writing "The Virtualization Cookbook", http://linuxvm.org/present/misc/virt-cookbook-2.pdf, we took Rob's suggestion to save a few cycles by doing the following: 1) Have one zLinux server run the NTP server, xntpd, syncing to servers on the Internet becoming stratum n+1 2) Have all other zLinux servers sync to the first one, becoming stratum n+2, once a night with a cron script: # cat /etc/cron.daily/set-clock #!/bin/bash # Adjust the clock /usr/sbin/ntpd -q The /etc/ntp.conf file on each simply has a single "server" statement pointing to server (1). If the underlying hardware clock keeps good time, does the Linux clock actually drift? How? Let's ignore DST as a separate issue. -- Cheers John -- spambait [EMAIL PROTECTED] [EMAIL PROTECTED] Tourist pics http://portgeographe.environmentaldisasters.cds.merseine.nu/ Please do not reply off-list -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: from a local linux discussion group: Hans Reiser arrested for murdering his wife.
Paul Dembry wrote: Very sad for the children. Whatever Hans did, I can't imagine it's happy for him either. In such a murder, I can see why The State would wish to punish the culprit, but I don't see how it actually makes anything better for anyone. Not the childred, not the deceased, certainly not the culprit, not The Taxpayer, and nor can I imagine it deterring anyone else sufficiently emotional. -- Cheers John -- spambait [EMAIL PROTECTED] [EMAIL PROTECTED] Tourist pics http://portgeographe.environmentaldisasters.cds.merseine.nu/ Please do not reply off-list -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: Server Time Protocol support for zSeries
On 10/11/06, Marcy Cortes <[EMAIL PROTECTED]> wrote: Sure, it wastes a little, but it doesn't look that bad here (we have to run NTP on every server to sync security tickets and stuff). Velocity reports the idle ones at 0.01% of a CPU, and that's with their agent presumbaly doing a little stuff too). IIRC the NTP mechanism was to review adjusting the change of the drift every 2 seconds or so. Even though this is very little work, it does make VM think the guest is busy and keeps it in queue. Asking the snmp agent every minute for some MIBs (when the guest did real work) is an order of maginute less annoying for VM. I think the Kerberos stuff requires same time within 30 seconds. That's not a very strong requirement and could allow for some drift. If your applications can afford stepping back time a little, then an ntpd -q via cron might be good enough. Having ETR steer the LPAR TOD clock is nice because it compensates the drift for you. Combining ETR and NTP is not good because the model behind ntpd does not match ETR. Rob -- Rob van der Heij Velocity Software, Inc http://velocitysoftware.com/ -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: Server Time Protocol support for zSeries
On 10/11/06, John Summerfield <[EMAIL PROTECTED]> wrote: If the underlying hardware clock keeps good time, does the Linux clock actually drift? On zSeries, the Linux system clock was supposed to be locked to the TOD (apart from the corrections by ntpd). That's because the TOD is used to measure time rather than count by interrupts (similar to the instruction counter in Intel CPUs). There have been bugs that caused Linux system clock to drop behind. I believe those were/are bugs. Let's ignore DST as a separate issue. Yes indeed. NTP is based on UTC which does not have time changes. The glibc locale define when your local clock is yanked forward or backward, and by how much. The way that works is real cute. These are files created by my test that wrote a new file every second: 30 2004-10-31 02:59:58.0 +0200 file61.tmp 30 2004-10-31 02:59:59.0 +0200 file62.tmp 29 2004-10-31 02:00:00.0 +0100 file63.tmp 29 2004-10-31 02:00:01.0 +0100 file64.tmp I'm surprised we did not bring this up before in the thread ;-) -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: Server Time Protocol support for zSeries
Rob van der Heij wrote: On 10/11/06, John Summerfield <[EMAIL PROTECTED]> wrote: If the underlying hardware clock keeps good time, does the Linux clock actually drift? On zSeries, the Linux system clock was supposed to be locked to the TOD (apart from the corrections by ntpd). That's because the TOD is used to measure time rather than count by interrupts (similar to the instruction counter in Intel CPUs). There have been bugs that caused Linux system clock to drop behind. I believe those were/are bugs. I'm feeling a little slow; is the TOD set by the operator for each VM guest? Or managed by VM? Or, (if you have one of these features) by the underlying hardware? If no VM, then what? I can fully understand why one shouldn't trust the operators' reading of the trusty Timex, but does one really need to set the hardware clock on a modern mainframe more often than I do on my PC hardware? Let's ignore DST as a separate issue. Yes indeed. NTP is based on UTC which does not have time changes. The glibc locale define when your local clock is yanked forward or backward, and by how much. The way that works is real cute. These are files created by my test that wrote a new file every second: 30 2004-10-31 02:59:58.0 +0200 file61.tmp 30 2004-10-31 02:59:59.0 +0200 file62.tmp 29 2004-10-31 02:00:00.0 +0100 file63.tmp 29 2004-10-31 02:00:01.0 +0100 file64.tmp That could bugger up* the make. * look to the British meanings. -- Cheers John -- spambait [EMAIL PROTECTED] [EMAIL PROTECTED] Tourist pics http://portgeographe.environmentaldisasters.cds.merseine.nu/ Please do not reply off-list -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: Server Time Protocol support for zSeries
On 10/12/06, John Summerfield <[EMAIL PROTECTED]> wrote: I'm feeling a little slow; is the TOD set by the operator for each VM guest? Or managed by VM? Or, (if you have one of these features) by the underlying hardware? There's a system TOD that is set at POR time (from the clock of the PS/2 or so?) Unless you have the gear that will synch that from true time, it will be off some amount. When you IPL z/VM in the LPAR, it will pick up the TOD and allow the operator to correct that. If he does, z/VM will compute the offset and set the LPAR offset to the hardware TOD. From that point on the LPAR clock runs along with the hardware, but with fixed offset. So LPAR virtualized the TOD clock by letting each LPAR have its own. When a virtual machine reads the TOD, it will get the LPAR TOD plus a per-user fixed offset. This offset can be set (when TODENABLE set for that user) by the operating system again. So z/VM virtualized the TOD clock to let each virtual machine have its own - but they all keep that fixed distance of the real TOD. Linux on zSeries does not use this ability to set the VTOD offset. An ETR would steer the real TOD and thus also adjust all the others that are with fixed offset from it. In addition to the virtual machine set its own offset, you can also define the offset to be taken from some other user when the virtual machine logs on. This is neat for simulating parallel sysplex in virtual machines, or for Y2K testing. You could imagine at IPL of z/VM have a single virtual machine play with NTP and obtain true time, and set VTOD for that. All Linux servers could then want that time. So they would all run the same time. Good, except for drift. Back then I suggested to enhance the VTOD to allow steering - when the virtual machine is not dispatched you can adjust the clock provided you don't yank it over a set timer. Never happened, maybe because we knew the new ETR/STP stuff would come. Rob -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
