Re: Dasdfmt and other potential block sizes
OS VS/1, OS VS/2 (MVS and maybe SVS) were current at the time. I've not run Hercules for a while but as I recall one can define an FBA device to and use it to read a CD. It might be that that only works for DOS: I have a couple of 3370s defined (I've just checked my archive), but the file name suggests they might not be MVS volumes. Probably not. VS1 and VS2 had to be patched for 3380 support, and I don't remember any announcements for 3370 or other FBA devices for MVS or SVS. (I *really* wish IBM would bring back the announcement and sales manual archives for the no-longer-marketed stuff in some form. It's really annoying not to be able to look this up online any more. I'd even pay for a copy of that older material -- it's not like it's competitive information any longer...sigh.) -- 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: Can't Access YAST to complete install
Hi Mark, yes, here's what I see from those commands Thanks for helping out here 01: CP Q NIC DETAILS 01: Adapter 5000 Type: QDIO Name: GUESTLANDevices: 3 01: Port 0 MAC: 02-00-00-00-00-04 LAN: SYSTEM GUESTLAN MFS: 8192 01: RX Packets: 21 Discarded: 0 Errors: 0 01: TX Packets: 20 Discarded: 0 Errors: 0 01: RX Bytes: 6574 TX Bytes: 1314 01: Connection Name: HALLOLE State: Session Established 01: Device: 5000 Unit: 000 Role: CTL-READ 01: Device: 5001 Unit: 001 Role: CTL-WRITE 01: Device: 5002 Unit: 002 Role: DATA 01: VLAN: ANY Assigned by user 01: Unicast IP Addresses: 01: 155.180.147.41 Mask: 255.255.255.0 01: FE80::200:0:100:4/64 01: Multicast IP Addresses: 01: 224.0.0.1MAC: 01-00-5E-00-00-01 01: 224.0.0.251 MAC: 01-00-5E-00-00-FB 01: 224.0.1.22 MAC: 01-00-5E-00-01-16 01: 239.255.255.253 MAC: 01-00-5E-7F-FF-FD 01: FF02::1 MAC: 33-33-00-00-00-01 01: FF02::1:FF00:4 MAC: 33-33-FF-00-00-04 01: 01: CP Q LAN DETAILS 01: LAN SYSTEM GUESTLAN Type: QDIO Active: 5 MAXCONN: INFINITE 01: PERSISTENT UNRESTRICTED MFS: 8192ACCOUNTING: OFF 01: Adapter Owner: TCPIPNIC: 5000 Name: GUESTLAN 01: Adapter Owner: ZLIN01 NIC: 5000 Name: GUESTLAN 01: Adapter Owner: ZLIN02 NIC: 5000 Name: GUESTLAN 01: Adapter Owner: ZLIN04 NIC: 5000 Name: GUESTLAN 01: Adapter Owner: ZLIN06 NIC: 5000 Name: GUESTLAN #ifconfig -a eth0 Link encap:Ethernet HWaddr 02:00:00:00:00:04 inet addr:155.180.147.41 Bcast:155.180.147.47 Mask:255.255.255.240 inet6 addr: fe80::200:0:100:4/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1482 Metric:1 RX packets:23 errors:0 dropped:0 overruns:0 frame:0 TX packets:31 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:6926 (6.7 Kb) TX bytes:3076 (3.0 Kb) loLink encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:4 errors:0 dropped:0 overruns:0 frame:0 TX packets:4 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:202 (202.0 b) TX bytes:202 (202.0 b) sit0 Link encap:IPv6-in-IPv4 NOARP MTU:1480 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) #route -n Kernel IP routing table Destination Gateway Genmask Flags Metric RefUse Iface 155.180.147.32 0.0.0.0 255.255.255.240 U 0 00 eth0 169.254.0.0 0.0.0.0 255.255.0.0 U 0 00 eth0 127.0.0.0 0.0.0.0 255.0.0.0 U 0 00 lo 0.0.0.0 155.180.147.33 0.0.0.0 UG0 00 eth0 # lsmod lsmod Module Size Used by sg 51752 0 st 53540 0 sd_mod 32004 0 sr_mod 27688 0 scsi_mod 163144 4 sg,st,sd_mod,sr_mod cdrom 48672 1 sr_mod qeth 190284 0 qdio 58672 2 qeth ipv6 332004 76 qeth ccwgroup 17408 1 qeth dm_mod 77640 0 dasd_fba_mod 19456 1 dasd_eckd_mod 69632 4 dasd_mod 79168 7 dasd_fba_mod,dasd_eckd_mod ext3 153440 1 jbd92964 1 ext3 William 'Doug' Carroll Mainframe Systems Engineer II Global Technology Infrastructure (614) 213-4954 Office (877) 899-1697 Pager (614) 244-9897 Fax http://www.bankone.com Post, Mark K [EMAIL PROTECTED]To: LINUX-390@vm.marist.edu m cc: Sent by: Linux onSubject: Re: Can't Access YAST to complete install 390 Port [EMAIL PROTECTED] ist.edu 08/15/2005 11:11 PM Please respond to Linux on 390 Port Ok, if you've figured out how to be able to issue ping commands, then the following commands will be of interest: #cp q nic details #cp q lan details ifconfig -a route -n lsmod Mark Post -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Doug Carroll Sent: Monday, August 15, 2005 5:17 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: Can't Access YAST to complete install Sorry, I'm not seeing post on my topic at all, just checked the archives and
Re: Mainframe REXX EXEC to logon to zVM Linux instance and issue commands
The exec I listed last week, didn't allow for the return of the results, at least in the form that the exec could parse thru. However, you can always (linux form) pipe the results to a file and then ftp the file back to the calling exec. Then parse the results there. I've not had the need to do this with Linux, yet, but I do have some VM/Windows applications that do the same thing. i.e. initiate some process on the pc, send the resulting data to CMS, stage the data to tape, report results back to PC, send OK to user if everything is just fine. Sure it is klunky. We need something simular to the P/390 utilities, OS2 command and OS2PIPE. That allowed CMS users to send commands to the OS2 side of the P/390 and return the results. Tom Duerbusch THD Consulting -- 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: Can't Access YAST to complete install
The setup looks good from what I can see. _Something_ is going in and out of that interface (about 20 packets worth). Is the TCPIP Service Virtual Machine the default gateway at 155.180.147.33? Can you ping that? What are the IP addresses of the other systems on the GuestLAN? Does arp -an show anything after a ping -c 3 -b 155.180.147.47 ? Mark Post -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Doug Carroll Sent: Tuesday, August 16, 2005 9:57 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: Can't Access YAST to complete install Hi Mark, yes, here's what I see from those commands Thanks for helping out here 01: CP Q NIC DETAILS 01: Adapter 5000 Type: QDIO Name: GUESTLANDevices: 3 01: Port 0 MAC: 02-00-00-00-00-04 LAN: SYSTEM GUESTLAN MFS: 8192 01: RX Packets: 21 Discarded: 0 Errors: 0 01: TX Packets: 20 Discarded: 0 Errors: 0 01: RX Bytes: 6574 TX Bytes: 1314 01: Connection Name: HALLOLE State: Session Established 01: Device: 5000 Unit: 000 Role: CTL-READ 01: Device: 5001 Unit: 001 Role: CTL-WRITE 01: Device: 5002 Unit: 002 Role: DATA 01: VLAN: ANY Assigned by user 01: Unicast IP Addresses: 01: 155.180.147.41 Mask: 255.255.255.0 01: FE80::200:0:100:4/64 01: Multicast IP Addresses: 01: 224.0.0.1MAC: 01-00-5E-00-00-01 01: 224.0.0.251 MAC: 01-00-5E-00-00-FB 01: 224.0.1.22 MAC: 01-00-5E-00-01-16 01: 239.255.255.253 MAC: 01-00-5E-7F-FF-FD 01: FF02::1 MAC: 33-33-00-00-00-01 01: FF02::1:FF00:4 MAC: 33-33-FF-00-00-04 01: 01: CP Q LAN DETAILS 01: LAN SYSTEM GUESTLAN Type: QDIO Active: 5 MAXCONN: INFINITE 01: PERSISTENT UNRESTRICTED MFS: 8192ACCOUNTING: OFF 01: Adapter Owner: TCPIPNIC: 5000 Name: GUESTLAN 01: Adapter Owner: ZLIN01 NIC: 5000 Name: GUESTLAN 01: Adapter Owner: ZLIN02 NIC: 5000 Name: GUESTLAN 01: Adapter Owner: ZLIN04 NIC: 5000 Name: GUESTLAN 01: Adapter Owner: ZLIN06 NIC: 5000 Name: GUESTLAN #ifconfig -a eth0 Link encap:Ethernet HWaddr 02:00:00:00:00:04 inet addr:155.180.147.41 Bcast:155.180.147.47 Mask:255.255.255.240 inet6 addr: fe80::200:0:100:4/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1482 Metric:1 RX packets:23 errors:0 dropped:0 overruns:0 frame:0 TX packets:31 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:6926 (6.7 Kb) TX bytes:3076 (3.0 Kb) loLink encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:4 errors:0 dropped:0 overruns:0 frame:0 TX packets:4 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:202 (202.0 b) TX bytes:202 (202.0 b) sit0 Link encap:IPv6-in-IPv4 NOARP MTU:1480 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) #route -n Kernel IP routing table Destination Gateway Genmask Flags Metric RefUse Iface 155.180.147.32 0.0.0.0 255.255.255.240 U 0 00 eth0 169.254.0.0 0.0.0.0 255.255.0.0 U 0 00 eth0 127.0.0.0 0.0.0.0 255.0.0.0 U 0 00 lo 0.0.0.0 155.180.147.33 0.0.0.0 UG0 00 eth0 # lsmod lsmod Module Size Used by sg 51752 0 st 53540 0 sd_mod 32004 0 sr_mod 27688 0 scsi_mod 163144 4 sg,st,sd_mod,sr_mod cdrom 48672 1 sr_mod qeth 190284 0 qdio 58672 2 qeth ipv6 332004 76 qeth ccwgroup 17408 1 qeth dm_mod 77640 0 dasd_fba_mod 19456 1 dasd_eckd_mod 69632 4 dasd_mod 79168 7 dasd_fba_mod,dasd_eckd_mod ext3 153440 1 jbd92964 1 ext3 William 'Doug' Carroll Mainframe Systems Engineer II Global Technology Infrastructure (614) 213-4954 Office (877) 899-1697 Pager (614) 244-9897 Fax http://www.bankone.com Post, Mark K [EMAIL PROTECTED]To: LINUX-390@vm.marist.edu m cc: Sent by: Linux onSubject: Re: Can't Access YAST to complete install 390 Port [EMAIL PROTECTED] ist.edu 08/15/2005 11:11 PM
SLES 9 in an LPAR
I'm having a performance problem. I was asked to install SLES 9 64-bit into an LPAR. To create the server I got my hands on the needed DASD and conducted the install of Linux under z/VM. The virtual hardware configuration (DASD and OSA addresses) were specified as would be used on the LPAR. As usual, the installation went well. The resulting copy of Linux can be booted under z/VM in perhaps a minute or two. However when I attempt to start this copy of Linux in an LPAR (512M and one dedicated CPU in an IFL on a 2094-313), it runs so slow you might think the software was written by folks in Redmond, Washington. It takes perhaps 15-20 minutes to boot. At times it seems to be completely unresponsive, even to the directly-connected HMC Operating System Message panel. I've encoded the so-called kernel timer patch both enabled and disabled, to no avail. And limited the DASD the kernel is to use with a DASD=- phrase in zipl.conf. But clearly I've missed something pretty obvious. Anyone have an idea? -- 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: SLES 9 in an LPAR
What weight has the LPAR been assigned as compared to the other LPARs? Is the LPAR capped or able to obtain CPU cycles dynamically when available? David Scully, William P wrote: I'm having a performance problem. I was asked to install SLES 9 64-bit into an LPAR. To create the server I got my hands on the needed DASD and conducted the install of Linux under z/VM. The virtual hardware configuration (DASD and OSA addresses) were specified as would be used on the LPAR. As usual, the installation went well. The resulting copy of Linux can be booted under z/VM in perhaps a minute or two. However when I attempt to start this copy of Linux in an LPAR (512M and one dedicated CPU in an IFL on a 2094-313), it runs so slow you might think the software was written by folks in Redmond, Washington. It takes perhaps 15-20 minutes to boot. At times it seems to be completely unresponsive, even to the directly-connected HMC Operating System Message panel. I've encoded the so-called kernel timer patch both enabled and disabled, to no avail. And limited the DASD the kernel is to use with a DASD=- phrase in zipl.conf. But clearly I've missed something pretty obvious. Anyone have an idea? -- 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: SLES 9 in an LPAR
First guess is that the LPAR has more devices defined to it than it will use, and it's running through addresses - to see what's there. Make sure that only what it's supposed to use is defined. However when I attempt to start this copy of Linux in an LPAR (512M and one dedicated CPU in an IFL on a 2094-313), it runs so slow you might think the software was written by folks in Redmond, Washington. It takes perhaps 15-20 minutes to boot. At times it seems to be completely unresponsive, even to the directly-connected HMC Operating System Message panel. -- 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: SLES 9 in an LPAR
Is the DASD shared? If so, I would think that qualifies as one of those ...results will be hard to diagnose. My thought is without z/VM your system is seeing everything available to it according to the access list and possibly the candidate list of each channel as defined in your IOCP. If you are using ESCON attached DASD could you ensure the channel(s) of your IPL device is offline to any other system identified in the IOCP (access/candidate list) for your device in question? If the DASD is shared this still won't resolve contention at the CU/device level though I can't image anything like this taking 15-20 minutes. Regards, Kevin -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Scully, William P Sent: Tuesday, August 16, 2005 9:13 AM To: LINUX-390@VM.MARIST.EDU Subject: SLES 9 in an LPAR I'm having a performance problem. I was asked to install SLES 9 64-bit into an LPAR. To create the server I got my hands on the needed DASD and conducted the install of Linux under z/VM. The virtual hardware configuration (DASD and OSA addresses) were specified as would be used on the LPAR. As usual, the installation went well. The resulting copy of Linux can be booted under z/VM in perhaps a minute or two. However when I attempt to start this copy of Linux in an LPAR (512M and one dedicated CPU in an IFL on a 2094-313), it runs so slow you might think the software was written by folks in Redmond, Washington. It takes perhaps 15-20 minutes to boot. At times it seems to be completely unresponsive, even to the directly-connected HMC Operating System Message panel. I've encoded the so-called kernel timer patch both enabled and disabled, to no avail. And limited the DASD the kernel is to use with a DASD=- phrase in zipl.conf. But clearly I've missed something pretty obvious. Anyone have an idea? -- 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: SLES 9 in an LPAR
Whether or not you limit the DASD range in zipl.conf it will still do a store subchannel and sense id for each of the devices it can find for the active IOCDS. If it's trying to do sense id (maybe even read device characteristics, I can't recall) for heavily used devices on other LPARs you could run into performance issues. Neale -Original Message- I've encoded the so-called kernel timer patch both enabled and disabled, to no avail. And limited the DASD the kernel is to use with a DASD=- phrase in zipl.conf. But clearly I've missed something pretty obvious. Anyone have an idea? -- 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: SLES 9 in an LPAR
I wondering how many devices are defined to the LPAR in the IOCDS. Any idea? Mark Post -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Scully, William P Sent: Tuesday, August 16, 2005 12:13 PM To: LINUX-390@VM.MARIST.EDU Subject: SLES 9 in an LPAR I'm having a performance problem. I was asked to install SLES 9 64-bit into an LPAR. To create the server I got my hands on the needed DASD and conducted the install of Linux under z/VM. The virtual hardware configuration (DASD and OSA addresses) were specified as would be used on the LPAR. As usual, the installation went well. The resulting copy of Linux can be booted under z/VM in perhaps a minute or two. However when I attempt to start this copy of Linux in an LPAR (512M and one dedicated CPU in an IFL on a 2094-313), it runs so slow you might think the software was written by folks in Redmond, Washington. It takes perhaps 15-20 minutes to boot. At times it seems to be completely unresponsive, even to the directly-connected HMC Operating System Message panel. I've encoded the so-called kernel timer patch both enabled and disabled, to no avail. And limited the DASD the kernel is to use with a DASD=- phrase in zipl.conf. But clearly I've missed something pretty obvious. Anyone have an idea? -- 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
Linux query command for 64-bit?
Is there a Linux command that will tell me that I am 64-bit? I guess I could issue a ?uname ?a? and look for the x in s390x but was hoping if there was a better way. Thanks. Peter This Email message and any attachment may contain information that is proprietary, legally privileged, confidential and/or subject to copyright belonging to Pepco Holdings, Inc. or its affiliates (PHI). This Email is intended solely for the use of the person(s) to which it is addressed. If you are not an intended recipient, or the employee or agent responsible for delivery of this Email to the intended recipient(s), you are hereby notified that any dissemination, distribution or copying of this Email is strictly prohibited. If you have received this message in error, please immediately notify the sender and permanently delete this Email and any copies. PHI policies expressly prohibit employees from making defamatory or offensive statements and infringing any copyright or any other legal right by Email communication. PHI will not accept any liability in respect of such communications. -- 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: SLES 9 in an LPAR
Some additional comments, to everyone who has offered advice: - We have a dedicated processor so it's not an LPAR weight issue. That was my first guess, but we've confirmed the processor is dedicated. - We have a -very- large number of devices defined to the LPAR, and since at our site we tend to keep each LPAR configured similarly, Linux is seeing them all. We are considering reworking the device configuration for -this- particular LPAR to greatly restrict the number of devices. I -do- suspect this will help. Thanks for the advice and I'll keep you all posted on any further status. -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Post, Mark K Sent: Tuesday, August 16, 2005 1:31 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: SLES 9 in an LPAR I wondering how many devices are defined to the LPAR in the IOCDS. Any idea? Mark Post -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Scully, William P Sent: Tuesday, August 16, 2005 12:13 PM To: LINUX-390@VM.MARIST.EDU Subject: SLES 9 in an LPAR I'm having a performance problem. I was asked to install SLES 9 64-bit into an LPAR. To create the server I got my hands on the needed DASD and conducted the install of Linux under z/VM. The virtual hardware configuration (DASD and OSA addresses) were specified as would be used on the LPAR. As usual, the installation went well. The resulting copy of Linux can be booted under z/VM in perhaps a minute or two. However when I attempt to start this copy of Linux in an LPAR (512M and one dedicated CPU in an IFL on a 2094-313), it runs so slow you might think the software was written by folks in Redmond, Washington. It takes perhaps 15-20 minutes to boot. At times it seems to be completely unresponsive, even to the directly-connected HMC Operating System Message panel. I've encoded the so-called kernel timer patch both enabled and disabled, to no avail. And limited the DASD the kernel is to use with a DASD=- phrase in zipl.conf. But clearly I've missed something pretty obvious. Anyone have an idea? -- 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: Linux query command for 64-bit?
You should be tell from a file /sbin/init command. This is what I get on my machine: [EMAIL PROTECTED] log]# file /sbin/init /sbin/init: ELF 64-bit MSB executable, version 1 (SYSV), for GNU/Linux 2.4.0, dynamically linked (uses shared libs), stripped You have new mail in /var/spool/mail/root [EMAIL PROTECTED] log]# snip Is there a Linux command that will tell me that I am 64-bit? I guess I could issue a ?uname ?a? and look for the x in s390x but was hoping if there was a better way. Thanks. /snip -- 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: Linux query command for 64-bit?
Is there a Linux command that will tell me that I am 64-bit? I guess I could issue a ?uname ?a? and look for the x in s390x but was hoping if there was a better way. Thanks. No ... there is no better way. On zSeries, it is up to the guest op sys (in the case of Linux, this is controlled by the kernel) whether or not to be in 64-bit mode. The kernel reports this by way of the utsname() function which is what 'uname' uses. So the x on the end is the official way to know you're in 64-bit mode. -- R; -- 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
Companies take divergent paths with mainframe
http://www.computerworld.com/hardwaretopics/hardware/story/0,10801,103916,00 .html?source=NLT_AMnid=103916 +--+ | Chris Little OKDHS Platform Services | | IS Operating Systems Specialist IV | | email [EMAIL PROTECTED] | | work (405)522-1306 cell (405)229-7822 | +--+ -- 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: Linux query command for 64-bit?
As others have indicated, uname is typically used. Why don't you like that method? Or, perhaps a better question, what would make some other method a better way for your purposes? Mark Post -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Peter E. Abresch Jr. - at Pepco Sent: Tuesday, August 16, 2005 2:34 PM To: LINUX-390@VM.MARIST.EDU Subject: Linux query command for 64-bit? Is there a Linux command that will tell me that I am 64-bit? I guess I could issue a ?uname ?a? and look for the x in s390x but was hoping if there was a better way. Thanks. Peter -- 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: Linux query command for 64-bit?
If you want, compile and run this.
Name it bill_bitness.c
gcc -obill_bitness bill_bitness.c
/
Find out the bitness and write a
Bill of Bitness
*/
#include stdio.h
int main()
{
int size;
size=sizeof(long);
if (size == 4)
printf(32 bit system. Get with the program.\n);
else if (size == 8)
printf(64 bit system. Whoa! Good for you!\n);
return 0;
}
-Original Message-
From: Post, Mark K [mailto:[EMAIL PROTECTED]
Sent: Tuesday, August 16, 2005 2:28 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: Linux query command for 64-bit?
As others have indicated, uname is typically used. Why don't
you like that method? Or, perhaps a better question, what
would make some other method a better way for your purposes?
Mark Post
-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On
Behalf Of Peter E. Abresch Jr. - at Pepco
Sent: Tuesday, August 16, 2005 2:34 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Linux query command for 64-bit?
Is there a Linux command that will tell me that I am 64-bit?
I guess I could issue a ?uname ?a? and look for the x in
s390x but was hoping if there was a better way. Thanks.
Peter
--
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: Linux query command for 64-bit?
uname -m and look for the x? -Original Message- From: Peter E. Abresch Jr. - at Pepco [mailto:[EMAIL PROTECTED] Sent: Tuesday, August 16, 2005 1:34 PM To: LINUX-390@VM.MARIST.EDU Subject: Linux query command for 64-bit? Is there a Linux command that will tell me that I am 64-bit? I guess I could issue a ?uname ?a? and look for the x in s390x but was hoping if there was a better way. Thanks. Peter This Email message and any attachment may contain information that is proprietary, legally privileged, confidential and/or subject to copyright belonging to Pepco Holdings, Inc. or its affiliates (PHI). This Email is intended solely for the use of the person(s) to which it is addressed. If you are not an intended recipient, or the employee or agent responsible for delivery of this Email to the intended recipient(s), you are hereby notified that any dissemination, distribution or copying of this Email is strictly prohibited. If you have received this message in error, please immediately notify the sender and permanently delete this Email and any copies. PHI policies expressly prohibit employees from making defamatory or offensive statements and infringing any copyright or any other legal right by Email communication. PHI will not accept any liability in respect of such communications. -- 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: Linux query command for 64-bit?
I am trying to write a generic script that runs on SLES8, SLES9, and SLES9x and was not convinced that s390x really was good enough to signify 64-bit. From everyone?s responses, it sounds like x marks the spot. I will use uname ?m. Thanks to everyone that responded. Peter Post, Mark K [EMAIL PROTECTED] Sent by: Linux on 390 Port LINUX-390@VM.MARIST.EDU 08/16/2005 03:27 PM Please respond to Linux on 390 Port LINUX-390@VM.MARIST.EDU To LINUX-390@VM.MARIST.EDU cc Subject Re: Linux query command for 64-bit? As others have indicated, uname is typically used. Why don't you like that method? Or, perhaps a better question, what would make some other method a better way for your purposes? Mark Post -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Peter E. Abresch Jr. - at Pepco Sent: Tuesday, August 16, 2005 2:34 PM To: LINUX-390@VM.MARIST.EDU Subject: Linux query command for 64-bit? Is there a Linux command that will tell me that I am 64-bit? I guess I could issue a ?uname ?a? and look for the x in s390x but was hoping if there was a better way. Thanks. Peter -- 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 This Email message and any attachment may contain information that is proprietary, legally privileged, confidential and/or subject to copyright belonging to Pepco Holdings, Inc. or its affiliates (PHI). This Email is intended solely for the use of the person(s) to which it is addressed. If you are not an intended recipient, or the employee or agent responsible for delivery of this Email to the intended recipient(s), you are hereby notified that any dissemination, distribution or copying of this Email is strictly prohibited. If you have received this message in error, please immediately notify the sender and permanently delete this Email and any copies. PHI policies expressly prohibit employees from making defamatory or offensive statements and infringing any copyright or any other legal right by Email communication. PHI will not accept any liability in respect of such communications. -- 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: Linux query command for 64-bit?
Peter E. Abresch Jr. - at Pepco wrote:
I am trying to write a generic script that runs on SLES8, SLES9, and
SLES9x and was not convinced that s390x really was good enough to signify
64-bit. From everyone?s responses, it sounds like x marks the spot. I will
use uname ?m. Thanks to everyone that responded.
Peter
Post, Mark K [EMAIL PROTECTED]
Sent by: Linux on 390 Port LINUX-390@VM.MARIST.EDU
08/16/2005 03:27 PM
Please respond to
Linux on 390 Port LINUX-390@VM.MARIST.EDU
To
LINUX-390@VM.MARIST.EDU
cc
Subject
Re: Linux query command for 64-bit?
As others have indicated, uname is typically used. Why don't you like
that method? Or, perhaps a better question, what would make some other
method a better way for your purposes?
Mark Post
-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of
Peter E. Abresch Jr. - at Pepco
Sent: Tuesday, August 16, 2005 2:34 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Linux query command for 64-bit?
Is there a Linux command that will tell me that I am 64-bit? I guess I
could issue a ?uname ?a? and look for the x in s390x but was hoping if
there was a better way. Thanks.
Of these solutions, only the C program will work on my UltraSparc. If
you want something that also works on {i,p}Series you need something a
little more elaborate than uname and test for the x
--
Cheers
John
-- spambait
[EMAIL PROTECTED] [EMAIL PROTECTED]
Tourist pics http://portgeographe.environmentaldisasters.cds.merseine.nu/
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: Mainframe REXX EXEC to logon to zVM Linux instance and issue commands
Tom Duerbusch wrote: The exec I listed last week, didn't allow for the return of the results, at least in the form that the exec could parse thru. However, you can always (linux form) pipe the results to a file and then ftp the file back to the calling exec. Then parse the results there. I've not had the need to do this with Linux, yet, but I do have some VM/Windows applications that do the same thing. i.e. initiate some process on the pc, send the resulting data to CMS, stage the data to tape, report results back to PC, send OK to user if everything is just fine. Sure it is klunky. We need something simular to the P/390 utilities, OS2 command and OS2PIPE. That allowed CMS users to send commands to the OS2 side of the P/390 and return the results. or to learn to use better tools:) One can talk to almost anything using expect (a programming language, an extention of TCL). Expect is fully interactive (but you need to know the likely paths in the conversation). One can imbed expect into Perl - see perl-expect. One can do this command-generator | ssh -t linux-box or even command-generator | ssh -t linux-box | command-checker One can write a CGI and talk to it with Any Web Browser (but watch your security). If you don't like a Patchy web server, you can write your own in half-a-dozen or so lines of Perl or Python. One _could_ put somethig to run a shell into xinet.d/shell.conf and pipe commands to it with netcat like in the ssh exmaples above: command-generator | nc linux-box Of course, this isn't very secure, even with tcpwrappers. One could also use TCP sockets (when I used REXX on OS/2 there was a sockets package) to chat up the Linux box. Again, watch your security. command-generator and command-checker can be written in REXX, or as simple as this: ssh -t command-list | mail -s Command results' [EMAIL PROTECTED] _I_ would likely be doing it from a Linux box and use shell scripts to generate commands and process the results, ssh to send the commands. Years ago, when I had some concerns about performance of Warp 4 vd Warp Connect, I used a bat file (or REXX procedure, I don't recall) to control the Machine Under Test, including running the benchmark and rebooting. I submitted commands by rsh or rexec. -- Cheers John -- spambait [EMAIL PROTECTED] [EMAIL PROTECTED] Tourist pics http://portgeographe.environmentaldisasters.cds.merseine.nu/ 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: Can't Access YAST to complete install
Still having problems seeing posts so sorry about the cut'n paste here. The setup looks good from what I can see. _Something_ is going in and out of that interface (about 20 packets worth). Is the TCPIP Service Virtual Machine the default gateway at 155.180.147.33? Can you ping that? From the linux server I'm installing I can not ping 155.180.147.33 and can ping it from other guests running sles8 currently it is defined this way DEVICE OSAVM1 OSD 0FA0 PORTNAME OSAG0C5 PRIROUTER AUTORESTART LINK ETH1 QDIOETHERNET OSAVM1 DEVICE OSAVM2 OSD 0FD0 PORTNAME OSAG0CD PRIROUTER AUTORESTART LINK ETH2 QDIOETHERNET OSAVM2 DEVICE VMGLAN OSD 5000 PORTNAME GUESTLAN AUTORESTART LINK ETH3 QDIOETHERNET VMGLAN HOME 10.238.192.110 ETH1 10.238.192.238 ETH2 155.180.147.33 ETH3 then we use OSPF so MPROUTE is configured What are the IP addresses of the other systems on the GuestLAN? At the time of these tests the following servers where up and are reachable via IP 155.180.147.36 cohzlnx01 test 1 server 155.180.147.37 cohzlnx02 test 2 server 155.180.147.39 cohzlnx04 NFS Server The server in question is reachable after IPL'ing from the RDR and entering the IP info for it, after completing the YAST setup,this is the one unreachable via IP 155.180.147.41 cohzlnx06 one being installed. Does arp -an show anything after a ping -c 3 -b 155.180.147.47 ? cohzlnx06:~ # ping -c 3 -b 155.180.147.47 ping -c 3 -b 155.180.147.47 WARNING: pinging broadcast address PING 155.180.147.47 (155.180.147.47) 56(84) bytes of data. --- 155.180.147.47 ping statistics --- 3 packets transmitted, 0 received, 100% packet loss, time 2015ms cohzlnx06:~ # arp -an arp -an cohzlnx06:~ # William 'Doug' Carroll Mainframe Systems Engineer II Global Technology Infrastructure (614) 213-4954 Office (877) 899-1697 Pager (614) 244-9897 Fax http://www.bankone.com Post, Mark K [EMAIL PROTECTED]To: LINUX-390@vm.marist.edu m cc: Sent by: Linux onSubject: Re: Can't Access YAST to complete install 390 Port [EMAIL PROTECTED] ist.edu 08/15/2005 11:11 PM Please respond to Linux on 390 Port Ok, if you've figured out how to be able to issue ping commands, then the following commands will be of interest: #cp q nic details #cp q lan details ifconfig -a route -n lsmod Mark Post -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Doug Carroll Sent: Monday, August 15, 2005 5:17 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: Can't Access YAST to complete install Sorry, I'm not seeing post on my topic at all, just checked the archives and saw some replies. for some of the questions, the SLES9 host is on the same subnet as my SLES8 hosts and I can not ping in either direction. SLES8 and SLES8 are both on the same guestlan. i.e. SLES8 can not ping SLES9 host and visa-versa I can not ping the Gateway either from the SLES9 host I can ping the SLES9s own IP from SLES9 the /28 is the correct subnet for the host i have tried re-ipling the SLES9 server and it goes through skipping the customization steps it is still unreachable William 'Doug' Carroll Mainframe Systems Engineer II Global Technology Infrastructure (614) 213-4954 Office (877) 899-1697 Pager (614) 244-9897 Fax http://www.bankone.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 -- 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: SLES 9 in an LPAR
Do you have 100% cpu usage? HMC can tell that. If it's so, than is this user or system load? Linux on 390 Port LINUX-390@VM.MARIST.EDU írta 2005.08.16 20:38:54 időpontban: Some additional comments, to everyone who has offered advice: - We have a dedicated processor so it's not an LPAR weight issue. That was my first guess, but we've confirmed the processor is dedicated. - We have a -very- large number of devices defined to the LPAR, and since at our site we tend to keep each LPAR configured similarly, Linux is seeing them all. We are considering reworking the device configuration for -this- particular LPAR to greatly restrict the number of devices. I -do- suspect this will help. Thanks for the advice and I'll keep you all posted on any further status. -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Post, Mark K Sent: Tuesday, August 16, 2005 1:31 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: SLES 9 in an LPAR I wondering how many devices are defined to the LPAR in the IOCDS. Any idea? Mark Post -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Scully, William P Sent: Tuesday, August 16, 2005 12:13 PM To: LINUX-390@VM.MARIST.EDU Subject: SLES 9 in an LPAR I'm having a performance problem. I was asked to install SLES 9 64-bit into an LPAR. To create the server I got my hands on the needed DASD and conducted the install of Linux under z/VM. The virtual hardware configuration (DASD and OSA addresses) were specified as would be used on the LPAR. As usual, the installation went well. The resulting copy of Linux can be booted under z/VM in perhaps a minute or two. However when I attempt to start this copy of Linux in an LPAR (512M and one dedicated CPU in an IFL on a 2094-313), it runs so slow you might think the software was written by folks in Redmond, Washington. It takes perhaps 15-20 minutes to boot. At times it seems to be completely unresponsive, even to the directly-connected HMC Operating System Message panel. I've encoded the so-called kernel timer patch both enabled and disabled, to no avail. And limited the DASD the kernel is to use with a DASD=- phrase in zipl.conf. But clearly I've missed something pretty obvious. Anyone have an idea? -- 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 -- 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
