Fwd: IBM Launches the z13 Mainframe
On 1/13/2015 at 07:05 PM, Mark Regan 000d30be819f-dmarc-requ...@listserv.ua.edu wrote: http://www-03.ibm.com/press/us/en/pressrelease/45808.wss Thanks, Mark Regan, USNR-Ret, 1969-1991 What he said. Also, a link to a YouTube video (from Mark Sipples of IBM) and a couple of links to images. http://www-03.ibm.com/press/us/en/attachment/45824.wss?fileId=ATTACH_FILE2fileName=IBM%20Launches%20z13%20Mainframe%20--%20Most%20Powerful%20and%20Secure%20System%20Ever%20Built.jpg http://www-03.ibm.com/press/us/en/attachment/45825.wss?fileId=ATTACH_FILE2fileName=IBM%27s%20New%20z13%20Mainframe%20Designed%20to%20Handle%20Billions%20of%20Transactions%20for%20the%20Mobile%20Economy.jpg https://www.youtube.com/watch?v=ErZRSQoTFXw Mark Post -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/
Re: cio_ignore vs Linux in System z
Indeed, as pointed out by other folks this feature was introduced in our very early days, when clients started to install Linux into LPARs with possibly tens of thousands of devices they would need if IPLing z/OS into it. Not only did it take long to boot, but we initially only operated on the first 1024 devices found, and didn't have plugging rules yet. And other z/OS holding permanent RESERVEs on shared ECKD devices it owned didn't help much either. We'd discussed whether to introduce black lists or white lists addressing the challenges at hand and eventually implemented both. Much has changed since then and whether it should be a default or not is a valid discussion to have. You may consider it paranoia but its introduction served a purpose - and still does. If running under z/VM and/or if using Linux in LPAR with your IODF written in a way that only devices the LPAR is supposed to operate on are configured to it you can presumably safely turn it off. Best regards Ingo Ingo AdlungIBM Deutschland Research IBM Distinguished Engineer Development GmbH Chief Architect, System z Vorsitzender des Aufsichtsrats: Virtualization Linux Martina Koederitz mail: adl...@de.ibm.comGeschäftsführung: Dirk Wittkopp phone: +49-7031-16-4263Sitz der Gesellschaft: Böblingen Registergericht: Amtsgericht Stuttgart, HRB 243294 Linux on 390 Port LINUX-390@VM.MARIST.EDU wrote on 12.01.2015 20:43:00: From: Mike Walter mike.wal...@aon.com To: LINUX-390@VM.MARIST.EDU Date: 12.01.2015 20:43 Subject: Re: [LINUX-390] cio_ignore vs Linux in System z Sent by: Linux on 390 Port LINUX-390@VM.MARIST.EDU Thanks, Sam, Jay, Jim, Harley, and Mark (and anyone else who may have replied since I looked at the log), There are no LPAR-only Linux servers running here, only those running (RHEL) under z/VM. I suspected that cio_ignore was something related to security (perhaps an auditor fearing that an errant z/VM sysprog might attach a wrong device address to a guest, or poor security rules coupled with use of VMCP would let the wrong Linux user access the wrong devices), or performance. It appears that the performance issue was the culprit, but not one of concern for me with only z/VM guests. I've shared the suggestions with our zLinux admins, who will probably make dynamic updates for the few PoC guests currently running, and the next Golden Image(s). Have to love this list, thanks again! Mike Walter Aon Corporation The opinions expressed herein are mine alone, not necessarily those of my employer. -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/ -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/
Re: Where to put Z/VM tools and utilities
Thanks everyone. I will set up a user to own the tools as suggested and use VMLINK. I am the only z/VM user except for a couple of people in the company who used VM many years ago and have an id for nostalgic reasons (and who could be useful if I am not around) so I will just update the PROFILE EXECs rather than tinker with SYSPROF EXEC. SFS looks attractive but I have no knowledge of it so I will stick with minidisks for now. Ditto for nicknames. Keith On Monday, 12 January 2015, 15:58, Rick Troth ri...@velocitysoftware.com wrote: On 01/12/2015 09:20 AM, Robert J Brenneman wrote: Mother's rule of z/VM Service number 1: Never change anything IBM sends you Mother's rule of z/VM Service number 2: Never mix your stuff with IBM's stuff. Amen! But see below for an exception. In my shop we create a user in the directory named after our department and set the PW to NOLOG. We give that new user a 191 disk ... This, plus what Sam said about using VMLINK. VMLINK is your friend. And when using VMLINK, you can selectively put some things on minidisk and other things into SFS (like Alan suggested) as needed, without having to be wholly in one mode or the other. As a help when servicing, I like to have an ID for each product (or tool or package). Lock it down, but allow logon-by for maint. For minidisk, there must be an ID (see prior paragraph) to own the storage. Rather than 191, I recommend v/r/m for three or four levels. This is fun, though less flexible than SFS. For example, my copy of Arty's IUCVTRAP is at FIX19. I could have a user IUCVTRAP with disk 019 or F19. People would link that disk. (Using 'VMLINK' of course!) For each dotted level, you get 0 to 15 (last six in hex). SFS is simpler. For z/OS people on your team (or if it's just you), SFS might feel more natural, and that's a plus. Exception to Mother's rule #1: At a previous site, we had a small (read that as easy to maintain) mod to SYSPROF EXEC to conditionally drive LCLPROF EXEC. The latter then did as little as possible, but arranged for our local stuff to be quickly on-hand without keeping everyone's private PROFILE EXEC in synch. Sounds like you have a small enough team (just you? or others too?) that you might be able to get by with just doing it in PROFILE EXEC. Repeating what Sam said: more art than science. You'll get a handle on it. -- Rick Troth Senior Software Developer Velocity Software Inc. Mountain View, CA 94041 Main: (877) 964-8867 Direct: (614) 594-9768 ri...@velocitysoftware.com mailto:ri...@velocitysoftware.com -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/ -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/
Re: LINUX-390 Digest - 9 Jan 2015 to 12 Jan 2015 (#2015-5)
I now want to install some tools from the VM downloads web pages. Is there a= standard or commonly used convention for where such tools should be stored?= I found some sample instructions for installing pipeddr where the code was i= nstalled on the MAINT 191 for instance. I would not expect that to be a suit= able location. It is absolutely *not* suitable. For your own sanity, follow Mother's Third Law: Never mix your stuff with IBM stuff. If you're running a pure minidisk system, one convention that works well is to build a TOOLS id and put the code for the contributed stuff on minidisks attached to the TOOLS id, one minidisk per tool. You then modify SYSPROF EXEC to automatically access a minidisk -- say TOOLS 19F -- that has EXECs on it that VMLINKs the appropriate minidisk, runs the tool, and releases the minidisk when it's done. That way all the files for a tool stay together, they don't interfere with IBM-supplied stuff, and when you upgrade, you have only one thing to remember to carry forward. (the change to SYSPROF EXEC). In a SSI, you can put the minidisks on shared DASD, and everybody in the SSI uses the same stuff. If you're SFS-friendly, the same trick works with a SFS pool -- we create a new one called TOOLS:, and the same TOOLS userid convention. Since it's not one of the IBM 'magic' ones, it's immediately available on all nodes in a SSI world, and you can just ACCESS TOOLS:TOOLS. fm from anywhere and you're set. AVOID USING THE IBM SFS POOLS FOR THIS. You don't want to have to mess with migrating it on upgrade, and the VMSYSx: ones are not easily sharable in a SSI world. Also, does IBM provide a list of various MAINT minidisks and their functions= ? IBM doesn't (AFAIK), but Dave Jones has done all the homework and provided such an animal. Look through the archives of recent postings to this list to find it. -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/
Re: Fedora 21 for IBM System z release
That is good news Dan! Any chance to have a Fedora 21 s390x base image for docker? Thanks! Tito On Mon, Jan 5, 2015 at 1:59 PM, Dan Horák dho...@redhat.com wrote: On Mon, 5 Jan 2015 15:43:54 + Tener, Stuart (ITS) stuart.te...@its.ny.gov wrote: ALCON, With OpenCobol now becoming GnuCobol, I am curious which (if any) of the distributions it has made that package inclusive as a standard package thus far? Fedora 21 provides OpenCobol 1.1, I guess the maintainer will update it to 2.0 when it is released. Dan Until recently I had not looked at OpenCobol in several years, though it does seem to have matured quite nicely. Very Respectfully, Stuart Stuart Blake Tener, N3GWG Computer Scientist, IBM (contractor) NY State Office of Information Technology Services Enterprise UNIX Systems Support W. Averell Harriman State Office Building Campus 1220 Washington Avenue Building 8, Cube 7-114 Albany, NY 12226-1800 stuart.te...@its.ny.gov (NY State) stuart.te...@bh90210.net (personal) 3103580...@pm.sprint.com (email to text gateway for my iPhone) its.dl.dc.iats.zli...@its.ny.gov (z/Linux Team email alias) tax.dl.unix.st...@its.ny.gov (Enterprise UNIX Team email address) +(1) 518.862.6081 (desk) +(1) 215.338.6005 (Google Voice) +(1) 310.358.0202 (mobile) -Original Message- From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Dan Horák Sent: Thursday, December 18, 2014 7:33 AM To: LINUX-390@VM.MARIST.EDU Subject: Fedora 21 for IBM System z release Hello everyone, Fedora 21 GA release for the IBM System z (s390x) is here. This time only 9 days after primary release. The difference against primary Fedora is smaller than it was in Fedora 20, but we are still missing packages related to nodejs (v8 engine not publicly ported to s390x) or golang (but work is being done on gcc-go, so this should change in the future) and most of ocaml modules (native port would be required). For details see http://fedora.danny.cz/s390/rebuild/koji-compare-f21.txt The links to the actual release are here: http://mirrors.fedoraproject.org/publiclist/Fedora/21/s390x/ or directly at http://download.fedoraproject.org/pub/fedora-secondary/releases/21/Server/s390x/ http://download.fedoraproject.org/pub/fedora-secondary/releases/21/Everything/s390x/os/ Currently Fedora for s390x is available as the Server flavor (refer to http://fedoraproject.org/wiki/Fedora.next for more information). The first directory contains the installation tree as well as one DVD ISO with the complete release. There are plans on adding Cloud flavor in the future, but it depends on s390x support in several related projects. Everything as usual contains, well, everything. :) For general Fedora documentation please see http://docs.fedoraproject.org/ and Fedora 21 common bugs are documented at http://fedoraproject.org/wiki/Common_F21_bugs Additional information about known issues, the current progress and state for future release, where and how the team can be reached and just anything else Fedora on IBM System z related can be found here: http://fedoraproject.org/wiki/Architectures/s390x/21 For architecture specific release notes, please read it as there are changes in the interactive installation process. It's a wiki so don't hesitate to add your knowledge there. You can find useful information also in the previous release notes linked from the current ones. More information about Fedora on IBM System z can be found at http://fedoraproject.org/wiki/Architectures/s390x Our team got expanded during the last year so my thanks also go to the other team members and to everyone involved in making this happen! Your Fedora/s390x Maintainers -- Dan Horák Senior Software Engineer, Secondary Architectures Team Lead Red Hat Czech s.r.o., Purkyňova 99, 612 45 Brno -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/ -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/ -- Linux User #387870 . _/_õ|__| ..º[ .-.___.-._| . . . . .__( o)__( o).:___
Re: Fedora 21 for IBM System z release
On Tue, 13 Jan 2015 14:20:16 -0200 Tito Garrido titogarr...@gmail.com wrote: That is good news Dan! Any chance to have a Fedora 21 s390x base image for docker? oh, there is a demand for docker on s390 :-) There are plans for the future to provide that, but there are still obstacles on the road, like docker wants to builds itself with golang, but we will have gcc-go and few more. But the plans do exist. Dan Thanks! Tito On Mon, Jan 5, 2015 at 1:59 PM, Dan Horák dho...@redhat.com wrote: On Mon, 5 Jan 2015 15:43:54 + Tener, Stuart (ITS) stuart.te...@its.ny.gov wrote: ALCON, With OpenCobol now becoming GnuCobol, I am curious which (if any) of the distributions it has made that package inclusive as a standard package thus far? Fedora 21 provides OpenCobol 1.1, I guess the maintainer will update it to 2.0 when it is released. Dan Until recently I had not looked at OpenCobol in several years, though it does seem to have matured quite nicely. Very Respectfully, Stuart Stuart Blake Tener, N3GWG Computer Scientist, IBM (contractor) NY State Office of Information Technology Services Enterprise UNIX Systems Support W. Averell Harriman State Office Building Campus 1220 Washington Avenue Building 8, Cube 7-114 Albany, NY 12226-1800 stuart.te...@its.ny.gov (NY State) stuart.te...@bh90210.net (personal) 3103580...@pm.sprint.com (email to text gateway for my iPhone) its.dl.dc.iats.zli...@its.ny.gov (z/Linux Team email alias) tax.dl.unix.st...@its.ny.gov (Enterprise UNIX Team email address) +(1) 518.862.6081 (desk) +(1) 215.338.6005 (Google Voice) +(1) 310.358.0202 (mobile) -Original Message- From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Dan Horák Sent: Thursday, December 18, 2014 7:33 AM To: LINUX-390@VM.MARIST.EDU Subject: Fedora 21 for IBM System z release Hello everyone, Fedora 21 GA release for the IBM System z (s390x) is here. This time only 9 days after primary release. The difference against primary Fedora is smaller than it was in Fedora 20, but we are still missing packages related to nodejs (v8 engine not publicly ported to s390x) or golang (but work is being done on gcc-go, so this should change in the future) and most of ocaml modules (native port would be required). For details see http://fedora.danny.cz/s390/rebuild/koji-compare-f21.txt The links to the actual release are here: http://mirrors.fedoraproject.org/publiclist/Fedora/21/s390x/ or directly at http://download.fedoraproject.org/pub/fedora-secondary/releases/21/Server/s390x/ http://download.fedoraproject.org/pub/fedora-secondary/releases/21/Everything/s390x/os/ Currently Fedora for s390x is available as the Server flavor (refer to http://fedoraproject.org/wiki/Fedora.next for more information). The first directory contains the installation tree as well as one DVD ISO with the complete release. There are plans on adding Cloud flavor in the future, but it depends on s390x support in several related projects. Everything as usual contains, well, everything. :) For general Fedora documentation please see http://docs.fedoraproject.org/ and Fedora 21 common bugs are documented at http://fedoraproject.org/wiki/Common_F21_bugs Additional information about known issues, the current progress and state for future release, where and how the team can be reached and just anything else Fedora on IBM System z related can be found here: http://fedoraproject.org/wiki/Architectures/s390x/21 For architecture specific release notes, please read it as there are changes in the interactive installation process. It's a wiki so don't hesitate to add your knowledge there. You can find useful information also in the previous release notes linked from the current ones. More information about Fedora on IBM System z can be found at http://fedoraproject.org/wiki/Architectures/s390x Our team got expanded during the last year so my thanks also go to the other team members and to everyone involved in making this happen! Your Fedora/s390x Maintainers -- Dan Horák Senior Software Engineer, Secondary Architectures Team Lead Red Hat Czech s.r.o., Purkyňova 99, 612 45 Brno -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/ -- For
Can't get FEDORA21 installer to start IPL z/VM RDR.
This worked the last time I did it .. FEDORA18. Any ideas? [ 291.090419] dracut-initqueue[848]: Warning: Could not boot. Mounting Configuration File System... [ [32m OK [0m] Mounted Configuration File System. [ [32m OK [0m] Started Show Plymouth Boot Screen. [ [32m OK [0m] Reached target Paths. [ [32m OK [0m] Reached target Basic System. [ 291.090419] dracut-initqueue[848]: Warning: Could not boot. [ 291.092246] dracut-initqueue[848]: Warning: /dev/root does not exist Starting Dracut Emergency Shell... Warning: /dev/root does not exist Generating /run/initramfs/rdsosreport.txt Entering emergency mode. Exit the shell to continue. Type journalctl to view system logs. You might want to save /run/initramfs/rdsosreport.txt to a USB stick or /boot after mounting them and attach it to a bug report. dracut:/# MY PRM FILE ro ramdisk_size=4 cio_ignore=all,!0.0.0009 vnc rd.dasd=0.0.0250,251,252,253,254 rd.dasd=0.0.025f ip=1xx.xx.xx.126::1xx.xx.xx.1:255.255.254.0:fedora.hhh.com:eth0:none rd.znet=qeth,0.0.0340,0.0.0341,0.0.0342,layer2=0,portno=0 http_proxy=http://aaa:bb...@xx.xx.xx.xx:8080 proxy=http://aaa:bb...@xx.xx.xx.xx:8080 root=live: http://mirrors.kernel.org/fedora-econdary/releases/21/Server/s390x/os /images/install.img nameserver=1xx.xx.xx.1 -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/
Re: Fedora 21 for IBM System z release
Docker requires golang from google as it is built using the go build command. There is a project that is creating a gccgo build. Some folks in IBM Germany appear to be helping on this. I suspect in order to get docker going. I have built a gcc-5.0 with gccgo which has s390x as a target which builds the go command but it still requires work. On 1/14/15, 3:20 AM, Tito Garrido titogarr...@gmail.com wrote: That is good news Dan! Any chance to have a Fedora 21 s390x base image for docker? Thanks! Tito -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/
