Re: Hipersockets and z/VM access
On Thursday, 11/25/2004 at 05:21ZE10, Vic Cross <[EMAIL PROTECTED]> wrote: > The MTU size must be set appropriately with respect to the definition of the > Hipersockets CHPID in HCD. This definition in effect determines the maximum > 'block size' that can be sent on that CHPID, and there are corresponding > maximum MTU sizes that must be used. Note that the largest MTU is less than > the hardware block size! > > You'll need to check what was defined in HCD for that Hipersockets, and then > verify the largest MTU you are allowed to use -- and if it's a Hipersockets > Guest LAN on z/VM, check the DEFINE LAN as that hardware setting is mirrored > there. The value in HCD is the Maximum Frame Size (MFS). This is the OS= setting for the chpid in the IOCDS. The MTU is always MFS-8K. 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: sles9 install
You will need to insmod the DASD driver, with the appropriate device numbers for your DASD units: insmod dasd_mod dasd=num1,num2,num3-num4 I haven't looked at the SLES9 install yet, so I don't know if dasd_mod will then automatically load dasd_eckd_mod or not. If not, then just insmod dasd_eckd_mod After that, you should be able to mount your file systems. Mark Post -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Herczeg, Zoltan Sent: Friday, November 26, 2004 5:22 PM To: [EMAIL PROTECTED] Subject: sles9 install Thanks for the suggestions!., I was able to get sles9 installation done through yast. The system now reboots itself from dasd and it appears that all the networking information I entered during the install does not come up. I try to ping the ip address of the linux lpar and nothing. I cannot access this system through putty and to make matters worse any command I try to enter on the HMC console for that lpar does nothing. So I had the idea that I would boot the sles9 install, enter my network config then mount the previously created dasd /dev/dasda and see what might be wrong with the config files. So I boot the install stuff, enter the networking info and telnet into this lpar. I then try to issue commands mkdir zoltan then mount -t ext2 /dev/dasda1 /zoltan and I get the message mount: /dev/dasda1 is not a valid block device. I think the problem is that I have to associate a physical device address with /dev/dasda1 but how do I do that? I checked in all my Linux manuals and came up blank. I am thinking this is a s390 type function only. All help is appreciated! Zoltan -- 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
sles9 install
Thanks for the suggestions!., I was able to get sles9 installation done through yast. The system now reboots itself from dasd and it appears that all the networking information I entered during the install does not come up. I try to ping the ip address of the linux lpar and nothing. I cannot access this system through putty and to make matters worse any command I try to enter on the HMC console for that lpar does nothing. So I had the idea that I would boot the sles9 install, enter my network config then mount the previously created dasd /dev/dasda and see what might be wrong with the config files. So I boot the install stuff, enter the networking info and telnet into this lpar. I then try to issue commands mkdir zoltan then mount -t ext2 /dev/dasda1 /zoltan and I get the message mount: /dev/dasda1 is not a valid block device. I think the problem is that I have to associate a physical device address with /dev/dasda1 but how do I do that? I checked in all my Linux manuals and came up blank. I am thinking this is a s390 type function only. All help is appreciated! Zoltan -- 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: Clocking in z/VM
Ranga Nathan <[EMAIL PROTECTED]> wrote: >The last couple of days I am seeing VM clocking in my MAINT session when >I do something trivial like viewing the reader files. One time it even >killed the session while trying to view a file in the reader list. I had >to log in as operator and 'force' MAINT. >I am not sure how to go about tracing this kind of problems. What do you mean by "VM clocking"? X CLOCK? What emulator are you using? That sounds more like an emulator problem, if CP FORCE helped -- if you were hung in CP, that wouldn't do much. Extra is particularly bad for hangs in my experience (and the current version doesn't hang, it GPFs if I type too fast...amazing). ...phsiii -- 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: Programmable Operator - your comments?
Use the "basic mode" feature of the VM Performance Toolkit. Much more sophisticated matching capabilities than basic PROP, and makes a very acceptable scrolling console and event manager. > Just turned on the LGLOPR Programmable Operator guest. Looking at the > string matches in the routing table, it looks pretty basic to me. I would > like to see grep like regular expression matching. > I would like to know how or if others are using it or what else is being > used in its place. > -- 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: Hipersockets and z/VM access
> It would be nice to have some DWIMity built into computers. > > DWIM = Do What I Mean (geekspeak) I still have my Xerox Dandetiger. It has DWIM functions...8-) --d b -- 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: SLES9 31 bit upgrade to 64 bit
Being in the middle of developing the 64-bit version of Slack/390, I can state with great assurance that you would be _much_ better off doing a fresh install. There is just too much stuff going on that is too difficult to figure out in a reasonable period of time. What are you trying to preserve via an upgrade, versus having to redo with a new install? Mark Post -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: Friday, November 26, 2004 1:24 PM To: [EMAIL PROTECTED] Subject: SLES9 31 bit upgrade to 64 bit SLES9 for S/390 (31-bit) in an LPAR > (no VM) using a shared IFL (I have one other LPAR running SLES9 31-bit) I would like to upgrade my existing 31-bit system to 64-bit. When I tried running upgrade mode, there were hundreds of conflicts and I was not sure how to resolve them. That seemed logical to me (31-bit vs. 64-bit issues) but should I delete the dependencies, ignore them, or what? Any suggestions on an approach would be much appreciated. Doug -- 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: DASD Usage
You can do a "pvdisplay /dev/dasd?#" command for each volume that makes up the logical volume. Or, you can do "cat /proc/lvm/global" and look at all of them at once. Mark Post -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Aristarc Diez Redorta Sent: Friday, November 26, 2004 1:55 AM To: [EMAIL PROTECTED] Subject: DASD Usage Hi, We're using LVM in our SLES8 on z800. If I do 'df -h' it shows me ... /dev/grpnotes/volnotes 48G 3.2G 42G 7% /local but volnotes have 8 volumes 3390 model 9. My question: is there any way to know the real usage of each volume? Thanks in advance, Aris . ..: : : : Aristarc Diez : [EMAIL PROTECTED] : : : Programador de Sistemas : Tel.: +34.93.2536100: : : COSTAISA: Ext.: 209 : : : Barcelona : FAX : +34.93.2057917: : :...: :: -- 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
SLES9 31 bit upgrade to 64 bit
SLES9 for S/390 (31-bit) in an LPAR > (no VM) using a shared IFL (I have one other LPAR running SLES9 31-bit) I would like to upgrade my existing 31-bit system to 64-bit. When I tried running upgrade mode, there were hundreds of conflicts and I was not sure how to resolve them. That seemed logical to me (31-bit vs. 64-bit issues) but should I delete the dependencies, ignore them, or what? Any suggestions on an approach would be much appreciated. Doug -- 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: Clock setting in VM
On Fri, 26 Nov 2004 11:03:49 -0500, Peter Webb, Toronto Transit Commission <[EMAIL PROTECTED]> wrote: > What do you get back from a 'QUERY TIMEZONE' command? I believe we concluded that at IPL they adjusted local time in the wrong time zone and thus set the LPAR offset to the TOD clock... He would have to set the proper time zone, IPL and set the clock back, and then IPL again to run without time change. Rob -- Rob van der Heij rvdheij @ gmail.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: Clock setting in VM
What do you get back from a 'QUERY TIMEZONE' command? -Original Message- From: Ranga Nathan [mailto:[EMAIL PROTECTED] Sent: November 25, 2004 19:43 To: [EMAIL PROTECTED] Subject: Re: Clock setting in VM __ Ranga Nathan / CSG Systems Programmer - Specialist; Technical Services; BAX Global Inc. Irvine-California Tel: 714-442-7591 Fax: 714-442-2840 "Peter Webb, Toronto Transit Commission" <[EMAIL PROTECTED]> Sent by: Linux on 390 Port <[EMAIL PROTECTED]> 11/25/2004 06:13 AM Please respond to Linux on 390 Port To: [EMAIL PROTECTED] cc: Subject:Re: Clock setting in VM Sounds like you need to make a change to your VM SYSTEM CONFIG file (Normally on MAINT CF1 and CF2). First off you need to find a couple of statements like this: /**/ /*Timezone Definitions*/ /**/ Timezone_Definition EDT West 04.00.00 /* EDT is West 4 from UTC */ Timezone_Definition EST West 05.00.00 /* EST is West 5 from UTC */ And change them to suit your needs. Also look for these statements: TimeZone_Boundary on 2004-04-04 at 02:00:00 to EDT TimeZone_Boundary on 2004-10-31 at 02:00:00 to EST TimeZone_Boundary on 2005-04-03 at 02:00:00 to EDT TimeZone_Boundary on 2005-10-30 at 02:00:00 to EST Hmmm did these early in the installation. No joy :-(. Somehow our ops have fiddled the hardware clock. And make sure they reflect your reality. IPL VM, and you should be happy. If you need VM to handle users in multiple time zones, each seeing their own time, check the VM list archives. I think it has been discussed there. -Original Message- From: Ranga Nathan [mailto:[EMAIL PROTECTED] Sent: November 24, 2004 18:02 To: [EMAIL PROTECTED] Subject: Re: Clock setting in VM This is my problem. VM is showing mountain time. But we need PST/PDT. This is something I can do with 'ntp' on Linux. __ Ranga Nathan / CSG Systems Programmer - Specialist; Technical Services; BAX Global Inc. Irvine-California Tel: 714-442-7591 Fax: 714-442-2840 "Peter Webb, Toronto Transit Commission" <[EMAIL PROTECTED]> Sent by: Linux on 390 Port <[EMAIL PROTECTED]> 11/24/2004 10:27 AM Please respond to Linux on 390 Port To: [EMAIL PROTECTED] cc: Subject:Re: Clock setting in VM You cannot use an NTP client to sync VM's time to an external server. VM was never designed to have its time adjusted at anytime other than IPL. That said, I have tried it on a second-level test system, and VM did survive the time change, but it is doubtful whether a system with anything useful running on it would. There are NTP servers available to allow clients to sync to VM's time. -Original Message- From: Ranga Nathan [mailto:[EMAIL PROTECTED] Sent: November 24, 2004 13:05 To: [EMAIL PROTECTED] Subject: Clock setting in VM Is it possible to run 'ntpd' in z/VM to sync time? The z/VM clock setting uses the hardware clock which gave me problems with our Linux LPAR. Linux guests are running 'ntpd' to sync time and it works beautifully. All this because our hardware is in CO and we are in CA and we need the time set to PST/PDT. __ Ranga Nathan / CSG Systems Programmer - Specialist; Technical Services; BAX Global Inc. Irvine-California Tel: 714-442-7591 Fax: 714-442-2840 -- 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 __ The information transmitted is intended only for the person 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 of any action in reliance upon, this information by persons or entities other than the intended recipient or delegate is strictly prohibited. If you received this in error, please contact the sender and delete the material from any computer. The integrity and security of this message cannot be guaranteed on the Internet. The Sender accepts no liability for the content of this e-mail, or for the consequences of any actions taken on the basis of the information provided. The recipient should check this e-mail and any attachments for the presence of viruses. The sender accepts no liability for any damage caused by any virus transmitted by this e-mail. This disclaimer is the property of the TTC and must not be altered or circumvented in any manner. -- For LINUX-390 subscr
Re: RV: NFS - RPC Failure (Portmap)
On Gwe, 2004-11-26 at 10:48, Josà RaÃl BarÃn Rodriguez wrote: > > mount -t nfs 197.10.1.8:/mnt/cdrom /mnt/cdrom > > > > But it fails saying: > > > > mount: RPC: Port mapper failure - RPC: Unable to receive > > > > I just can't find which my mistake has been. Could anyone help me ? First try pinging from one box to the other, that lets you know the network layer is ok. If that seems ok then check if you have any firewalls turned on (eg the Red Hat standard firewall) -- 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: Configuration of Mainframe Machine.
But you will not be able to buy that from IBM anymore ;-) Seriously, the question was answered on the list yesterday or so. Have a look at the archives. -- Rob van der Heij rvdheij @ gmail.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
RV: NFS - RPC Failure (Portmap)
> Hi to everyone ! > > I have a SuSE Linux in a z/VM 4.4 in which I want to install a DB2 Server. > To achieve this I must NFS-access my installation CD mounted in a RedHat > PC which performs as NFS Server. > > What I have done is this: > > IN MY PC (RedHat Linux 9) > = > - I include the following line in /etc/exports > > /mnt/cdrom > *(sync,ro,no_root_squash,subtree_check,no_auth_nlm) > > - Then I restart both PORTMAP & NFS via the commands: > > /etc/init.d/portmap stop > /etc/init.d/nfs stop > /etc/init.d/portmap start > /etc/init.d/nfs start > (it executes OK, no tricks here :-) > > - And finally I execute exportfs -a so that changes in /etc/exports take > effect. > > > IN MY S/390 (SUSE Linux 8) > == > > - I try to mount the NFS system file through the command: > > mount -t nfs 197.10.1.8:/mnt/cdrom /mnt/cdrom > > But it fails saying: > > mount: RPC: Port mapper failure - RPC: Unable to receive > > I just can't find which my mistake has been. Could anyone help me ? > > > Greetings from Spain, > > > José R. Barón > -- 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
Configuration of Mainframe Machine.
Hi All, Can anyone let me know whether there is any limitation on the minimum mainframe machine configuration (cannot be installed on Generation X and below machines) required for installing LINUX. Thanks and Regards, Kirti -- 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
