Re: Telecommunications protocol support
Many thanks! Wesley Parish On Friday 13 December 2002 02:22 am, you wrote: http://www.amazon.com/exec/obidos/tg/detail/-/0136430163/qid=1039696984/sr= 1-14/ref=sr_1_14/103-9717084-4547825?v=glances=books -- Mau e ki, He aha te mea nui? You ask, What is the most important thing? Maku e ki, He tangata, he tangata, he tangata. I reply, It is people, it is people, it is people.
You're all Commie b*st*rds!
Well, at least according to Steve Ballmer you are: http://www.theregister.co.uk/content/1/12266.html He sounds worried, poor man. -- Phil Payne http://www.isham-research.com +44 7785 302 803 +49 173 6242039
Re: You're all Commie b*st*rds!
On Fri, 2002-12-13 at 11:57, Phil Payne wrote: Well, at least according to Steve Ballmer you are: http://www.theregister.co.uk/content/1/12266.html He sounds worried, poor man. The response was even better: http://www.stud.ntnu.no/~shane/stasj/div_bilder/38.html Thats a very cool site of extremely funny images, but one or two (not the one referenced above) are not neccessarily work viewable and a couple may really offend some Americans. Alan
amanda changer
I'm working on using amanda with a 3494 ATL. I have written a socket program for linux to request a tape be mounted (either scratch or a specific VOLSER). I have a socket program listening in CMS to receive the mount requests, and then issue DFSMSRM commands to mount the correct tape. It then replies back to the linux socket program - that the tape was mounted or not. Now I am having a hard time trying to figure out how to create an amanda changer script to in use in this environment. Does anyone have an example of a changer script that requests volumes and not slots? Or anyone have any hints that may get me over the hump? Mark D Pace Senior Systems Engineer Mainline Information Systems 1700 Summit Lake Drive Tallahassee, FL. 32317 [EMAIL PROTECTED] Office: 850.219.5184 Fax: 850.219.5050 http://www.mainline.com
Re: You're all Commie b*st*rds!
The response was even better: http://www.stud.ntnu.no/~shane/stasj/div_bilder/38.html Thats a very cool site of extremely funny images, but one or two (not the one referenced above) are not neccessarily work viewable and a couple may really offend some Americans. 21 especially, in the light of events. -- Phil Payne http://www.isham-research.com +44 7785 302 803 +49 173 6242039
Linux/390 and z/VM interactions.
I know that I should use the code, Luke, but I'm not that familiar with the kernel et al. Does Linux/390 take advantage of any of the VM facilities when running under VM vs. in an LPAR? I'm thinking especially of the handshaking that is possible with paging. I.e. Linux thinks the page is in memory, but VM has it paged out. I think this is done with VSE and I remember it back in the OS/VS1 days as well. What about other VM-only facilities? More curious than anything else. -- John McKown Senior Technical Specialist UICI Insurance Center Applications Solutions Team +1.817.255.3225
Vanilla Linux !
http://news.bbc.co.uk/2/hi/uk_news/england/2572205.stm
Re: IBM JDK 1.4 on Linux/390
Mark, Thanks for the information. I followed your instructions and indeed, the executables on our 2.2 system have a390 in the header while the IBM 1.4 JDK executables have 0016. I then installed the JDK on a 2.4 system we also have running, and the executables successfully ran. I guess I'll be upgrading all of our images to 2.4. Thanks again, -Jay -Original Message- From: Mark Post [mailto:[EMAIL PROTECTED]] Sent: Thursday, December 12, 2002 8:53 PM To: 'Linux on 390 Port'; 'Paulsen, Jay' Subject: RE: IBM JDK 1.4 on Linux/390 Jay, After sending my first reply, I just happened to think... During the last year, the ELF magic was changed to a standard value, rather than the arbitrary one that was initially used. It is entirely possible (if not extremely likely) that the binaries for the JKD1.4 have x'16' in that field, which means your system won't recognize them as being for the same/correct architecture. The way to find out is pick a binary executable, say foo and do this: od -x -N 20 foo If the output ends in 0016 that is your problem. If it ends in a390 then that is not your problem. Here's two samples from one of my systems so you can see what I mean: This binary has the old ELF magic of a390. # od -x -N 20 /usr/bin/expect 000 7f45 4c46 0102 0100 020 0002 a390 024 This binary has the new ELF magic of 22/x'16' # od -x -N 20 /sbin/init 000 7f45 4c46 0102 0100 020 0002 0016 024 Mark Post -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED]]On Behalf Of Paulsen, Jay Sent: Thursday, December 12, 2002 11:00 AM To: [EMAIL PROTECTED] Subject: IBM JDK 1.4 on Linux/390 Hello, I've downloaded and installed this JDK from http://www-106.ibm.com/developerworks/java/jdk/linux140/?dwzon e=java but I get the error message cannot execute binary file when trying to run the java interpreter. I have successfully run JDK 1.3.0, and wanted to upgrade, but so far I can't figure out how to get this running. Has anyone been able to run JDK 1.4 on Linux/390? Any help is greatly appreciated. fyi - we're running SuSE 7.0 - Kernel 2.2.16 on a S/390 9672-X37 (G6) -Jay Jay Paulsen Health Care Information Systems The University of Iowa [EMAIL PROTECTED]
Product install from CD
I want to install a product on my SuSE 7.0 2.2.16 image. The product resides on CD. I am using SDI TN3270PLUS in VT100 mode on my desktop which has a CD drive. The Linux image runs under VM/ESA 2.4.0 so I don't think I can use the CD from the desktop. I was thinking about down loading the CD to a file on the PC the use FTP on Linux to load the product. I used YaST to change the CTC0 IP addresses, I use VI to edit /etc/rc.config and the change is there but when I shutdown and restart Linux I can't reach the network. The VI editor works much better when using the VT100 mode vs 3270. I can connect to the network using 'insmod -Y ctc setup=0x900' then 'ifconfig ctc0 172.xx.x.xxx pointopoint 172.xx.x.xxx netmask 255.0.0.0 mtu 1492' but I would like to get this to happen when I boot Linux.
Linux-390 as a VM guest on a FLEX-ES
I have installed DEBIAN Linux-390 as a guest on my z/VM 3.1 system. I would like to access one of the network cards from the Linux guest. I am currently accessing some of the cards form VSE guests. On VSE I use a device type of 3172. How would I configure this on my Linux guest? Stephen Frazier Information Technology Unit Oklahoma Department of Corrections 3400 Martin Luther King Oklahoma City, OK 73111-4298 Tel.: (405) 425-2549 Fax: (405) 425-2554
Re: Linux-390 as a VM guest on a FLEX-ES
Treat them as LCS devices. Attach a device triplet (xx0-2) to the Linux guest just as you do with VSE, and use the information in the installer to configure a LCS connection. -- db David Boyes Sine Nomine Associates -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED]]On Behalf Of Stephen Frazier Sent: Friday, December 13, 2002 1:05 PM To: [EMAIL PROTECTED] Subject: Linux-390 as a VM guest on a FLEX-ES I have installed DEBIAN Linux-390 as a guest on my z/VM 3.1 system. I would like to access one of the network cards from the Linux guest. I am currently accessing some of the cards form VSE guests. On VSE I use a device type of 3172. How would I configure this on my Linux guest? Stephen Frazier Information Technology Unit Oklahoma Department of Corrections 3400 Martin Luther King Oklahoma City, OK 73111-4298 Tel.: (405) 425-2549 Fax: (405) 425-2554
Re: Linux/390 and z/VM interactions.
John, Not yet, although there has been some discussion of how that might be implemented. The closest you can come right now is to define a vdisk as a paging device. If a page stays on the vdisk long enough, it will get put out to real VM paging volumes, otherwise it stays in expanded storage. A number of people (myself included) have played with this with good results. Mark Post -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED]]On Behalf Of McKown, John Sent: Friday, December 13, 2002 9:42 AM To: [EMAIL PROTECTED] Subject: Linux/390 and z/VM interactions. I know that I should use the code, Luke, but I'm not that familiar with the kernel et al. Does Linux/390 take advantage of any of the VM facilities when running under VM vs. in an LPAR? I'm thinking especially of the handshaking that is possible with paging. I.e. Linux thinks the page is in memory, but VM has it paged out. I think this is done with VSE and I remember it back in the OS/VS1 days as well. What about other VM-only facilities? More curious than anything else. -- John McKown Senior Technical Specialist UICI Insurance Center Applications Solutions Team +1.817.255.3225
Re: rh7.2 upgrading util-linux package
I was looking for something else and stumbled onto this post from the end of July which I had missed at that time. (Too much good info on this list!) To fix a collision between util-linux and s390-tools, Karsten Hopp said: The correct way would be to edit the util-linux.spec file and rebuild the package with the patched spec file. Search for /sbin/fdisk in the %files section and either comment it out or better surround with ifnarch like this: %ifnarch s390 s390x /sbin/fdisk %endif Neat trick. Good to know. But this worries me. IBM needs to figure out if they *really* need a custom 'fdisk' in the S390 Tools kit since they clearly will need normal FDISK to support SCSI. I would prefer that the FDISK included in Util-Linux be properly patched than to see two versions of it. If there must be two, then it might be wise to rename the newcomer 'fdisk390'. Thoughts? -- RMT
Re: Product install from CD
Pat, If you install the Samba client RPM, and turn on MS sharing for your CD, your Linux/390 system will be able to mount the CD directly (assuming you have the smbfs file system driver compiled into your kernel or as a module). For your network problem, check /etc/modules.conf. There should be two entries in there: alias ctc0 ctc options ctc setup='ctc=0,0x0900,0x0901,ctc0' If not, add them, and that should help some. Mark Post -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED]]On Behalf Of Abruzzese, Pat Sent: Friday, December 13, 2002 10:31 AM To: [EMAIL PROTECTED] Subject: Product install from CD I want to install a product on my SuSE 7.0 2.2.16 image. The product resides on CD. I am using SDI TN3270PLUS in VT100 mode on my desktop which has a CD drive. The Linux image runs under VM/ESA 2.4.0 so I don't think I can use the CD from the desktop. I was thinking about down loading the CD to a file on the PC the use FTP on Linux to load the product. I used YaST to change the CTC0 IP addresses, I use VI to edit /etc/rc.config and the change is there but when I shutdown and restart Linux I can't reach the network. The VI editor works much better when using the VT100 mode vs 3270. I can connect to the network using 'insmod -Y ctc setup=0x900' then 'ifconfig ctc0 172.xx.x.xxx pointopoint 172.xx.x.xxx netmask 255.0.0.0 mtu 1492' but I would like to get this to happen when I boot Linux.
Re: Linux-390 as a VM guest on a FLEX-ES
On VSE there are only 2 addresses are defined not 3. (040-041) Stephen Frazier Oklahoma Department of Corrections -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of David Boyes Sent: Friday, December 13, 2002 12:54 PM To: '[EMAIL PROTECTED]'; '[EMAIL PROTECTED]' Subject: RE: Linux-390 as a VM guest on a FLEX-ES Treat them as LCS devices. Attach a device triplet (xx0-2) to the Linux guest just as you do with VSE, and use the information in the installer to configure a LCS connection. -- db David Boyes Sine Nomine Associates -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED]]On Behalf Of Stephen Frazier Sent: Friday, December 13, 2002 1:05 PM To: [EMAIL PROTECTED] Subject: Linux-390 as a VM guest on a FLEX-ES I have installed DEBIAN Linux-390 as a guest on my z/VM 3.1 system. I would like to access one of the network cards from the Linux guest. I am currently accessing some of the cards form VSE guests. On VSE I use a device type of 3172. How would I configure this on my Linux guest? Stephen Frazier Information Technology Unit Oklahoma Department of Corrections 3400 Martin Luther King Oklahoma City, OK 73111-4298 Tel.: (405) 425-2549 Fax: (405) 425-2554
HTTPD server won't stay up
I am seeing my HTTPD server starting in the console Starting Name Service Cache Daemon ..done Starting inetd ..done Starting httpd [ LDAP PERL ] ..done Master Resource Control: runlevel 5 has been reached but when I try to connect I get connection refused as though the server is not running. If I manually start the apache web server it comes up fine. before I started httpd I did not see anything with netstat -a that showed http anything listening. After the manual start I saw http-www listening tcp0 0 *:www-http *:* LISTEN 550/httpd Any Suggestions on where I can look to help with more information. \|/ (. .) TIA, ___ooO-(_)-Ooo___, Larry Davis
Re: Linux/390 and z/VM interactions.
Great! Thanks for the information. I'll be sure to mention it to our Linux administrator who is from the distributed side and has little or no mainframe experience. -- John McKown Senior Technical Specialist UICI Insurance Center Applications Solutions Team +1.817.255.3225 -Original Message- From: Rob van der Heij [mailto:[EMAIL PROTECTED]] Sent: Friday, December 13, 2002 1:45 PM To: [EMAIL PROTECTED] Subject: Re: Linux/390 and z/VM interactions. At 15:42 13-12-02, McKown, John wrote: I know that I should use the code, Luke, but I'm not that familiar with the kernel et al. Does Linux/390 take advantage of any of the VM facilities when running under VM vs. in an LPAR? I'm thinking especially of the handshaking that is possible with paging. I.e. Linux thinks the page is in memory, but VM has it paged out. I think this is done with VSE and I remember it back in the OS/VS1 days as well. What about other VM-only facilities? Yes, pseudo page fault support is there already. When a process gets blocked because the particular page is paged out by VM, the kernel gets a chance to run another process. Recent changes to z/VM improved the PFAULT support. I have not seen numbers about how effective this is for Linux, but it is enabled by default when you run in a virtual machine. In fact, virtual memory itself as provided by z/VM is already a benefit over LPAR since it allows the Linux guests to breathe. The other thing is the shared kernel support that has been there for some time now. This allows you to put some 2MB of the kernel in shared pages and thus reduce the footprint of your penguins. And the dasd driver can use Diagnose I/O instead of SSCH and exploit MDC and other z/VM benefits. There have been some problems with that part of the driver in the past, but it looks like the current code works. Rob
Re: Linux-390 as a VM guest on a FLEX-ES
Sigh -- the last real 3172 I had the docs said three. As you say, only two are actually necessary. (My brain is full. I need a vacation.) -- db David Boyes Sine Nomine Associates -Original Message- From: Stephen Frazier [mailto:[EMAIL PROTECTED]] Sent: Friday, December 13, 2002 2:24 PM To: 'David Boyes'; [EMAIL PROTECTED] Subject: RE: Linux-390 as a VM guest on a FLEX-ES On VSE there are only 2 addresses are defined not 3. (040-041) Stephen Frazier Oklahoma Department of Corrections -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of David Boyes Sent: Friday, December 13, 2002 12:54 PM To: '[EMAIL PROTECTED]'; '[EMAIL PROTECTED]' Subject: RE: Linux-390 as a VM guest on a FLEX-ES Treat them as LCS devices. Attach a device triplet (xx0-2) to the Linux guest just as you do with VSE, and use the information in the installer to configure a LCS connection. -- db David Boyes Sine Nomine Associates -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED]]On Behalf Of Stephen Frazier Sent: Friday, December 13, 2002 1:05 PM To: [EMAIL PROTECTED] Subject: Linux-390 as a VM guest on a FLEX-ES I have installed DEBIAN Linux-390 as a guest on my z/VM 3.1 system. I would like to access one of the network cards from the Linux guest. I am currently accessing some of the cards form VSE guests. On VSE I use a device type of 3172. How would I configure this on my Linux guest? Stephen Frazier Information Technology Unit Oklahoma Department of Corrections 3400 Martin Luther King Oklahoma City, OK 73111-4298 Tel.: (405) 425-2549 Fax: (405) 425-2554
Re: Linux-390 as a VM guest on a FLEX-ES
Two should be correct. David was probably thinking of qdio/qeth cards when he said 3 addresses. Other than that, I believe his advice is correct. Mark Post -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED]]On Behalf Of Stephen Frazier Sent: Friday, December 13, 2002 2:24 PM To: [EMAIL PROTECTED] Subject: Re: Linux-390 as a VM guest on a FLEX-ES On VSE there are only 2 addresses are defined not 3. (040-041) Stephen Frazier Oklahoma Department of Corrections -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of David Boyes Sent: Friday, December 13, 2002 12:54 PM To: '[EMAIL PROTECTED]'; '[EMAIL PROTECTED]' Subject: RE: Linux-390 as a VM guest on a FLEX-ES Treat them as LCS devices. Attach a device triplet (xx0-2) to the Linux guest just as you do with VSE, and use the information in the installer to configure a LCS connection. -- db David Boyes Sine Nomine Associates -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED]]On Behalf Of Stephen Frazier Sent: Friday, December 13, 2002 1:05 PM To: [EMAIL PROTECTED] Subject: Linux-390 as a VM guest on a FLEX-ES I have installed DEBIAN Linux-390 as a guest on my z/VM 3.1 system. I would like to access one of the network cards from the Linux guest. I am currently accessing some of the cards form VSE guests. On VSE I use a device type of 3172. How would I configure this on my Linux guest? Stephen Frazier Information Technology Unit Oklahoma Department of Corrections 3400 Martin Luther King Oklahoma City, OK 73111-4298 Tel.: (405) 425-2549 Fax: (405) 425-2554
Re: rh7.2 upgrading util-linux package
Rick, More careful reading ( =:o ) of the thread reveals that s390utils provides fdasd, and a symbolic link to that named fdisk. So, the real name doesn't conflict, just the link. In the future, the link could be replaced by a real module, perhaps just the same as fdisk is now, but enhanced for Linux/390. Personally, I would have preferred that fdasd never have existed, rather that the fdisk code been upgraded to handle all disk types. I still think that is the way to go in the future. It will be one less difference between Linux in general and Linux/390 to trip up newcomers. Mark Post -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED]]On Behalf Of Rick Troth Sent: Friday, December 13, 2002 2:12 PM To: [EMAIL PROTECTED] Subject: Re: rh7.2 upgrading util-linux package I was looking for something else and stumbled onto this post from the end of July which I had missed at that time. (Too much good info on this list!) To fix a collision between util-linux and s390-tools, Karsten Hopp said: The correct way would be to edit the util-linux.spec file and rebuild the package with the patched spec file. Search for /sbin/fdisk in the %files section and either comment it out or better surround with ifnarch like this: %ifnarch s390 s390x /sbin/fdisk %endif Neat trick. Good to know. But this worries me. IBM needs to figure out if they *really* need a custom 'fdisk' in the S390 Tools kit since they clearly will need normal FDISK to support SCSI. I would prefer that the FDISK included in Util-Linux be properly patched than to see two versions of it. If there must be two, then it might be wise to rename the newcomer 'fdisk390'. Thoughts? -- RMT
Re: HTTPD server won't stay up
Larry, When I've run into problems like this in the past, I just edited the /sbin/init.d/apache script (or what ever it's called on your system) and inserted echo commands, or perhaps a set -x command near the top so that I could get a better idea of what was going on. Mark Post -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED]]On Behalf Of Davis, Lawrence Sent: Friday, December 13, 2002 2:53 PM To: [EMAIL PROTECTED] Subject: HTTPD server won't stay up I am seeing my HTTPD server starting in the console Starting Name Service Cache Daemon ..done Starting inetd ..done Starting httpd [ LDAP PERL ] ..done Master Resource Control: runlevel 5 has been reached but when I try to connect I get connection refused as though the server is not running. If I manually start the apache web server it comes up fine. before I started httpd I did not see anything with netstat -a that showed http anything listening. After the manual start I saw http-www listening tcp0 0 *:www-http *:* LISTEN 550/httpd Any Suggestions on where I can look to help with more information. \|/ (. .) TIA, ___ooO-(_)-Ooo___, Larry Davis
linux on z\vm capacity planning
Hello all, i was wondering if anyone knows what kind of machinme i need to run about 30-40 z\linux images on z\vm for sap-erp purposes, and still get good performance, or where i can get that information. thanks.
Re: rh7.2 upgrading util-linux package
Mark Post wrote: Rick Troth wrote: IBM needs to figure out if they *really* need a custom 'fdisk' in the S390 Tools kit since they clearly will need normal FDISK to support SCSI. I would prefer that the FDISK included in Util-Linux be properly patched than to see two versions of it. If there must be two, then it might be wise to rename the newcomer 'fdisk390'. [...] More careful reading ( =:o ) of the thread reveals that s390utils provides fdasd, and a symbolic link to that named fdisk. So, the real name doesn't conflict, just the link. In the future, the link could be replaced by a real module, perhaps just the same as fdisk is now, but enhanced for Linux/390. Personally, I would have preferred that fdasd never have existed, rather that the fdisk code been upgraded to handle all disk types. I still think that is the way to go in the future. Hmm, I'm not entirely sure about that. The fdisk program on Linux was originally made to be a one-on-one functional replacement for the equivalent DOS program named FDISK, dealing with the IBM PC hard disk partition table format. These days, the Linux implementation of fdisk appears to also support some other partitioning schemes, such as BSD/SUN and SGI. Other Unix systems have had tools to manipulate their own disk partition tables, going by various names, such as disklabel, mkpart, parted, etc. The PC platform has added one level of confusion to the partition table story in that several UNIX implementations took their own partitioning scheme with them and added it on top of the original IBM PC partition table, which was primarily used to segregate different operating systems. E.g. FreeBSD has both an fdisk utility to manipulate the PC partition table, which is primarily used to give FreeBSD a partition (named slice in this context) in the view of any other operating systems that might be on there, and a disklabel utility to manipulate its own partition table that is used to define the various partitions used for different filesystems such. Linux, not having a non-PC history behind it, did things a bit differently and used the PC partition table as its native partition table on PC platforms. The situation with Linux/390 DASD is obviously entirely different, with Linux partitions being defined as items in the platform's native VTOC table. There is no relation at all with the IBM PC partition table scheme. Now, since Linux/390 also supports SCSI disks these days, it could very well deal with disks with PC, Sun, BSD or SGI partition tables, and thus the solution to exclude the existing fdisk program from the S/390 platform, as suggested, is clearly wrong. The conclusion must be that the link from fdisk to fdasd was a mistake, perhaps borne out of a desire to make Linux on S/390 look just like Linux on PC. Whether one wants to add IBM DASD VTOC partitioning support to fdisk, I have to wonder. This is a fundamentally different scheme, and there is no interaction whatsoever between them. My choice would be to keep it separate, choose a fitting name from a wider Unix context, rather than the current fdasd name, which contrasts it to fdisk in a narrow PC Linux context, and make sure there is no confusion with the fdisk program. Does anyone know what these tools on UTS and/or AIX/370 were called? -- Willem Konynenberg [EMAIL PROTECTED] Konynenberg Software Engineering
