Re: CMS Pipelines for Windows
Pipelines was never intended to represent a port of CMS Pipelines - nor w as it originally intended for anything other than a useful tool for those ti mes when you might need to modify/translate some data. My background was as a VM/TPF systems programmer and one day I realised t hat I could really use a tool 'like' CMS Pipelines - but there wasn't one on my Windows platform. So I wrote Pipelines. James.
Re: CMS Pipelines for Windows
I have had a chance to look through a bunch of interesting stuff on this forum/discussion platform, which up until the last day or so .. I didn't even know existed. As I said in my previous post; Pipelines was written as a useful (hopeful ly) tool - but if anyone has any suggestions on how to take the project forwa rd in terms of 'what would make it more useful' then please let me know. I am currently looking into how to bind variables in OOREXX, so that I ca n write VAR and STEM stages.
Re: CMS Pipelines for Windows
This is awesome work you've done. There are two or three strong implementations of Pipelines for non-CMS/TSO environments. I don't mean to dis any of them. I'm looking for something written in C for maximum efficiency and portability. Having a core that is pure C does not prohibit some of the STAGES being written in C++ or anything else. Some months back, I began to assemble the following into runnable code. It is not complete, but the idea is ... two Unix pipe() pairs for each effective Pipelines connection wrapper functions output(), peekto(), and readto() are illustrated below The two Unix pipes go opposite directions. One goes forward and carries data (duh!) and also any meta data (such as length of the record available, if any) from producer to consumer. The other goes backward and carries requests and feedback from consumer to producer. So a record flows something like ... producer calls output() consumer calls peekto() under the covers, peekto() sends STAT backward output() sends metadata forward (most interesting being size of the record) assuming the buffer can hold the record, peekto() sends PEEK backward output() then sends the data A readto() does all of the above plus sends NEXT at the end and output() can return. When output() returns, the producer is unblocked and we get proper record flow. (You can dealy the record ... or not!) The design starts with two Unix pipes but can use shared mem if the platform supports that. The code is accomodating. (A NULL pointer to a shared mem struct means don't use shared mem.) -- R; On Tue, Aug 31, 2010 at 04:17, James Laing james_la...@hotmail.co.uk wrote: Pipelines was never intended to represent a port of CMS Pipelines - nor was it originally intended for anything other than a useful tool for those times when you might need to modify/translate some data. My background was as a VM/TPF systems programmer and one day I realised that I could really use a tool 'like' CMS Pipelines - but there wasn't one on my Windows platform. So I wrote Pipelines. James.
Re: Running back level VSE on a z/10 with VM6.1
This is from the VSE support page: These releases will not run on z990, z890, z9 or z10 servers. However, for transition purposes, a temporary patch may be available. Be aware, these releases are unsupported and the temporary patch does not in any way imply supported status. Use of unsupported releases is always at the user's risk. If you are interested in running one of these releases on any of the servers indicated, please contact the Z/VSE Team. Billy On 30 Aug 2010 at 13:04, Tony Thigpen wrote: VSE 2.2 is not even Y2K certified. IBM has some patches to allow old VSE's to run on newer hardware, but I don't think they go back to 2.2. You would have to contact the z/VSE development group directly to ask. I understand that they require that you commit to installing a supported VSE within 6 months(?) before they will give them to you. Tony Thigpen -Original Message - From: Yosua, Sara Sent: 08/30/2010 04:20 PM Although it is obviously not supported, does anyone know of any technical reason why a back level VSE/ESA 2.2 guest would not IPL and run under z/VM 6.1 on a z/10 ? Thank you for any feedback. Sara E Yosua
Re: CMS Pipelines for Windows
Hi. Thank you very much! My design is based around the concept of a sort of 'client-server' approach. In my little version of Pipelines; the StageManager provides th e central 'server' system that services input and output requests from the various stages. The StageManager does not 'know' about stages and it does not coordinate them; it simply (obviously with other support stuff) reads and writes records when it is asked to. Each stage is responsible for parsing its argument, allocating any data structures that it may need during its runtime phase .. and then at dispatch time .. its a free-for-all. But because the ReadRecord(), PeekRecord() etc functions all call into the StageManager; it simply lock s and releases stages as and when they call the appropriate function. There is no commit level stuff .. or anything like that .. and there is n o 'central brain' which coordinates what can run and when.. it runs by the way the stages interconnect. Again .. thanks for the support! Regards. James Laing.
Re: VSWITCH defined VSE TCP/IP fails
Frank, Would you be willing to share the steps you used to create the VSWITCH? Thanks, Billy On 30 Aug 2010 at 8:11, Frank M. Ramaekers wrote: Thanks, that helpsthe difference between an upCOUPLEd and a COUPLEd VSWITCH: UnCOUPLEd: AR 0015 MAC: 02-00-01-00-00-0E LAN: * NoneMFS: 8992 COUPLEd (and not yet initialized): AR 0015 MAC: 02-00-01-00-00-0E VSWITCH: SYSTEM VSWAILT ...and initialized: * cp q v nic aa0 details AR 0015 Adapter 0AA0.P00 Type: QDIO Name: UNASSIGNED Devices: 3 AR 0015 MAC: 02-00-01-00-00-0E VSWITCH: SYSTEM VSWAILT AR 0015 RX Packets: 49 Discarded: 0 Errors: 0 AR 0015 TX Packets: 42 Discarded: 0 Errors: 0 AR 0015 RX Bytes: 2450 TX Bytes: 2884 AR 0015 Connection Name: Session Established AR 0015 Device: 0AA0 Unit: 000 Role: CTL- READ AR 0015 Device: 0AA1 Unit: 001 Role: CTL- WRITE AR 0015 Device: 0AA2 Unit: 002 Role: DATAvPort: 0065 Index: 0065 AR 0015 Options: IPv4 AR 0015 Unicast IP Addresses: AR 0015 10.1.20.2MAC: 02-00-01-00-00- 0E AR 0015 1I40I READY Thanks Alan! Frank M. Ramaekers Jr. -Original Message- From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Alan Altmark Sent: Friday, August 27, 2010 3:33 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: VSWITCH defined VSE TCP/IP fails On Friday, 08/27/2010 at 04:28 EDT, Frank M. Ramaekers framaek...@ailife.com wrote: * cp q v nic aa0 details AR 0015 Adapter 0AA0.P00 Type: QDIOName: UNASSIGNED Devices: 3 AR 0015 MAC: 02-00-01-00-00-0ELAN: * None And there you have it. The adapter is not COUPLED, as indicated by the * None. An uncoupled NIC is the equivalent of an unplugged ethernet cable. Alan Altmark z/VM Development IBM Endicott _ This message contains information which is privileged and confidential and is solely for the use of the intended recipient. If you are not the intended recipient, be aware that any review, disclosure, copying, distribution, or use of the contents of this message is strictly prohibited. If you have received this in error, please destroy it immediately and notify us at privacy...@ailife.com.
Electronic Delivery - DDR or DVD?
In SHOPZ, for Electronic Delivery, is it necessary to order DDR to get a DVD image for upload (ftping) to VM? I installed 5.4 last October from an Electronic Delivery using Chapters 6 and 7 of the IBM Guide For Automated Installation and Service by ftping a DVD image up to VM. It went very smoothly. I am now installing 6.1 and trying to do the same thing again. But for Electronic Delivery, SHOPZ requires ordering DDR , not DVD. When we ftped it down to a laptop and unzipped it, we found a DVD image as well as other files. Am I doing something wrong or is this how it is supposed to work? I
Re: Electronic Delivery - DDR or DVD?
On Tuesday, 08/31/2010 at 09:00 EDT, George Henke/NYLIC george_he...@newyorklife.com wrote: In SHOPZ, for Electronic Delivery, is it necessary to order DDR to get a DVD image for upload (ftping) to VM? I installed 5.4 last October from an Electronic Delivery using Chapters 6 and 7 of the IBM Guide For Automated Installation and Service by ftping a DVD image up to VM. It went very smoothly. I am now installing 6.1 and trying to do the same thing again. But for Electronic Delivery, SHOPZ requires ordering DDR , not DVD. When we ftped it down to a laptop and unzipped it, we found a DVD image as well as other files. Am I doing something wrong or is this how it is supposed to work? You order the DVD version of the product, not the DDR, and select a tape format (which is ignored, but required). Why do you say that Shopz requires the DDR? I just set up a Shopz order (short of actually shipping it), and it didn't whine about needing the DDR. If you navigate to How to buy on the z/VM Home Page, you find a couple of Ordering tips links. Alan Altmark z/VM Development IBM Endicott
Re: CMS Pipelines for Windows
I see what you mean .. but how about a central 'service unit' that handle s all the input and output. The stages don't need to know anything about ea ch other .. they just request records and write records and that's it. A stage cannot be expected to 'know' about what it's input and output str eams are connected to; it's a worker bee. In my version (limited as it is) eac h stage is nothing more than a DLL that gets loaded by the StageManager, ki cked off and it starts requesting records. The StageManager only services requ ests as and when it is asked to. By providing a set of interface functions tha t (in the StageManager) cause locking/unlocking; all of the internal pipeli ne complexity is hidden from the stage designer. Let me know what you think. James.
Re: Electronic Delivery - DDR or DVD?
I have done as you said and here are the instructions. I have bolded the text in question. The instructions call for selecting DDR. Then the instructions at the bottom for installing from FTP Server, Chapter 7, Step 3 of Guide For Automated Installation and Service, call for using the downloaded DVD image. Apparently, we are to download DDR to upload DVD. IBM Systems System z z/VM How specify Internet Delivery for your z/VM order on ShopzSeries Effective January 25, 2008, the z/VM base operating system and base options are available for Internet delivery for orders placed using ShopzSeries in countries where it is available. We know many of our customers have requested Internet delivery and IBM is pleased to offer it to you. Thank you for your continued interest in z/VM. In addition to shipment on tape cartridges and DVD, z/VM is available for download from the Internet through ShopzSeries. Tips for ordering Internet delivery of z/VM via ShopzSeries In ShopzSeries, a black diamond () symbol indicates that electronic delivery is available for your z/VM product selection, even though you are shown only the two choices -- DDR or DVD. On a ski trail, black diamond signs mark the difficult/advanced ski trails. Ironic as it may seem, IBM is not using the black diamond symbol to indicate a degree of difficulty in ordering electronic delivery of z/VM. Use the tips below to help you know which pulldown selections you need, and which buttons to click on various screens. Once you are signed into ShopzSeries to create a new order: Select z/VM for the Operating Environment and select Products for Package Category Select the Hardware System where you plan to use this order On the Shop for Products screen, select Base Product for Group and also choose your language and filter. Do NOT click on Continue, instead click SHOW CATALOG ! When you see the catalog list, select DDR and then select Internet Continue if you need to select new licenses, do so. To specify delivery options, choose Internet on the Preferred Media pull-down and click on Go to be able to indicate any special instructions, and then click Continue. On the Review and Submit page, you have an opportunity to review and change your order before submitting it. Once you have submitted and confirmed your order, the next screen shows you a list of your orders and their status. The internet download can be performed using the instructions that are in the post-order email or by clicking on the Internet Download link on the order status page. For your convenience and planning, you can review the instructions for z/VM V5.4. See also: - How to Buy page - SDO page Installing z/VM V5.4.0 Installation instructions can be found in the Guide for Automated Installation and Service, GC24-6099, Part 2, z/VM System Image DVD Installation. Select the instructions in Part 2 that match the type of installation you are performing (first or second level, installing from DVDs, FTP server or VM minidisk (second level only)). The Guide for Automated Installation and Service and the Program Directory for z/VM and related products are available online at the following website: http://www.vm.ibm.com/library/ IBM, Alan Altmark alan_altm...@us.ibm.com Sent by: The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU 08/31/2010 09:35 AM Please respond to The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU To IBMVM@LISTSERV.UARK.EDU cc Subject Re: Electronic Delivery - DDR or DVD? On Tuesday, 08/31/2010 at 09:00 EDT, George Henke/NYLIC george_he...@newyorklife.com wrote: In SHOPZ, for Electronic Delivery, is it necessary to order DDR to get a DVD image for upload (ftping) to VM? I installed 5.4 last October from an Electronic Delivery using Chapters 6 and 7 of the IBM Guide For Automated Installation and Service by ftping a DVD image up to VM. It went very smoothly. I am now installing 6.1 and trying to do the same thing again. But for Electronic Delivery, SHOPZ requires ordering DDR , not DVD. When we ftped it down to a laptop and unzipped it, we found a DVD image as well as other files. Am I doing something wrong or is this how it is supposed to work? You order the DVD version of the product, not the DDR, and select a tape format (which is ignored, but required). Why do you say that Shopz requires the DDR? I just set up a Shopz order (short of actually shipping it), and it didn't whine about needing the DDR. If you navigate to How to buy on the z/VM Home Page, you find a couple of Ordering tips links. Alan Altmark z/VM Development IBM Endicott
Re: VSWITCH defined VSE TCP/IP fails
No problem. Originally, I had on z/VSE machine with 3 addresses used for TCP/IP. I wished to move this to a layer-3 VSWITCH for redundancy purposes. (Much of the following was derived from the IBM Redbook Linux on IBM eserver zSeries and S/390: VSWITCH and VLAN Features of z/VM 4.4) 1) Define the VSWITCH a. define vswitch vswitchname rdev ccuu1 ccuu2 ccuu3 b. -and- add the same statement to 'SYSTEM CONFIG' file (Remember ccuu1 ccuu2 ccuu3 represent a set of 3 address to be used) 2) Granting access to the VSWITCH a. set vswitch vswitchname grant userid b. -and- add Modify VSwitch vswitchname GRAnt userid to 'SYSTEM CONFIG' c. - or - add the set vswitch command in the AUTOLOG1 startup 3) Defining the simulated NICs a. for userid cmd define nic ccuu4 qdio b. -and- add to the directory for userid: NICDEF ccuu4 TYPE QDIO DEVICES 3 (a above can be skipped, but the userid would have to be logged off then on) 4) Attaching the simulated NIC with couple ccuu4 to system vswitchname (This will need to be performed each time the virtual machine is logged on.) (Don't think I missed anything) Frank M. Ramaekers Jr. From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Billy Bingham Sent: Tuesday, August 31, 2010 7:51 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: VSWITCH defined VSE TCP/IP fails Frank, Would you be willing to share the steps you used to create the VSWITCH? Thanks, Billy On 30 Aug 2010 at 8:11, Frank M. Ramaekers wrote: Thanks, that helpsthe difference between an upCOUPLEd and a COUPLEd VSWITCH: UnCOUPLEd: AR 0015 MAC: 02-00-01-00-00-0E LAN: * NoneMFS: 8992 COUPLEd (and not yet initialized): AR 0015 MAC: 02-00-01-00-00-0E VSWITCH: SYSTEM VSWAILT ...and initialized: * cp q v nic aa0 details AR 0015 Adapter 0AA0.P00 Type: QDIO Name: UNASSIGNED Devices: 3 AR 0015 MAC: 02-00-01-00-00-0E VSWITCH: SYSTEM VSWAILT AR 0015 RX Packets: 49 Discarded: 0 Errors: 0 AR 0015 TX Packets: 42 Discarded: 0 Errors: 0 AR 0015 RX Bytes: 2450 TX Bytes: 2884 AR 0015 Connection Name: Session Established AR 0015 Device: 0AA0 Unit: 000 Role: CTL- READ AR 0015 Device: 0AA1 Unit: 001 Role: CTL- WRITE AR 0015 Device: 0AA2 Unit: 002 Role: DATAvPort: 0065 Index: 0065 AR 0015 Options: IPv4 AR 0015 Unicast IP Addresses: AR 0015 10.1.20.2MAC: 02-00-01-00-00- 0E AR 0015 1I40I READY Thanks Alan! Frank M. Ramaekers Jr. -Original Message- From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Alan Altmark Sent: Friday, August 27, 2010 3:33 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: VSWITCH defined VSE TCP/IP fails On Friday, 08/27/2010 at 04:28 EDT, Frank M. Ramaekers framaek...@ailife.com wrote: * cp q v nic aa0 details AR 0015 Adapter 0AA0.P00 Type: QDIOName: UNASSIGNED Devices: 3 AR 0015 MAC: 02-00-01-00-00-0ELAN: * None And there you have it. The adapter is not COUPLED, as indicated by the * None. An uncoupled NIC is the equivalent of an unplugged ethernet cable. Alan Altmark z/VM Development IBM Endicott _ This message contains information which is privileged and confidential and is solely for the use of the intended recipient. If you are not the intended recipient, be aware that any review, disclosure, copying, distribution, or use of the contents of this message is strictly prohibited. If you have received this in error, please destroy it immediately and notify us at privacy...@ailife.com. _ This message contains information which is privileged and confidential and is solely for the use of the intended recipient. If you are not the intended recipient, be aware that any review, disclosure, copying, distribution, or use of the contents of this message is strictly prohibited. If you have received this in error, please destroy it immediately and notify us at privacy...@ailife.com.
Re: VSWITCH defined VSE TCP/IP fails
A couple of things On the DEFINE VSWITCH you only need to specify the 1st address of the triplet. On the NICDEF add LAN SYSTEM switchNameand it will be coupled automatically when you logon. example NICDEF 061C TYPE QDIO DEVICES 3 LAN SYSTEM VSWTCH3 OR SPECIAL 061C QDIO 3 SYSTEM VSWTCH3 On Tue, Aug 31, 2010 at 10:04 AM, Frank M. Ramaekers framaek...@ailife.comwrote: No problem. Originally, I had on z/VSE machine with 3 addresses used for TCP/IP. I wished to move this to a layer-3 VSWITCH for redundancy purposes. (Much of the following was derived from the IBM Redbook “Linux on IBM eserver zSeries and S/390: VSWITCH and VLAN Features of z/VM 4.4”) 1) Define the VSWITCH *a. **define vswitch vswitchname rdev ccuu1 ccuu2 ccuu3* b. –and- add the same statement to ‘SYSTEM CONFIG’ file (Remember ccuu1 ccuu2 ccuu3 represent a set of 3 address to be used) 2) Granting access to the VSWITCH *a. **set vswitch vswitchname grant userid* b. –and- add *Modify VSwitch vswitchname GRAnt userid* to ‘SYSTEM CONFIG’ c. – or – add the *set vswitch* command in the AUTOLOG1 startup 3) Defining the simulated NICs a. *for userid cmd define nic ccuu4 qdio* b. –and- add to the directory for *userid*: NICDEF *ccuu4* TYPE QDIO DEVICES 3 (a above can be skipped, but the userid would have to be logged off then on) 4) Attaching the simulated NIC with *couple ccuu4 to system vswitchname *(This will need to be performed each time the virtual machine is logged on.) (Don’t think I missed anything) Frank M. Ramaekers Jr. -- *From:* The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] *On Behalf Of *Billy Bingham *Sent:* Tuesday, August 31, 2010 7:51 AM *To:* IBMVM@LISTSERV.UARK.EDU *Subject:* Re: VSWITCH defined VSE TCP/IP fails Frank, Would you be willing to share the steps you used to create the VSWITCH? Thanks, Billy On 30 Aug 2010 at 8:11, Frank M. Ramaekers wrote: Thanks, that helpsthe difference between an upCOUPLEd and a COUPLEd VSWITCH: UnCOUPLEd: AR 0015 MAC: 02-00-01-00-00-0E LAN: * NoneMFS: 8992 COUPLEd (and not yet initialized): AR 0015 MAC: 02-00-01-00-00-0E VSWITCH: SYSTEM VSWAILT ...and initialized: * cp q v nic aa0 details AR 0015 Adapter 0AA0.P00 Type: QDIO Name: UNASSIGNED Devices: 3 AR 0015 MAC: 02-00-01-00-00-0E VSWITCH: SYSTEM VSWAILT AR 0015 RX Packets: 49 Discarded: 0 Errors: 0 AR 0015 TX Packets: 42 Discarded: 0 Errors: 0 AR 0015 RX Bytes: 2450 TX Bytes: 2884 AR 0015 Connection Name: Session Established AR 0015 Device: 0AA0 Unit: 000 Role: CTL- READ AR 0015 Device: 0AA1 Unit: 001 Role: CTL- WRITE AR 0015 Device: 0AA2 Unit: 002 Role: DATAvPort: 0065 Index: 0065 AR 0015 Options: IPv4 AR 0015 Unicast IP Addresses: AR 0015 10.1.20.2MAC: 02-00-01-00-00- 0E AR 0015 1I40I READY Thanks Alan! Frank M. Ramaekers Jr. -Original Message- From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Alan Altmark Sent: Friday, August 27, 2010 3:33 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: VSWITCH defined VSE TCP/IP fails On Friday, 08/27/2010 at 04:28 EDT, Frank M. Ramaekers framaek...@ailife.com wrote: * cp q v nic aa0 details AR 0015 Adapter 0AA0.P00 Type: QDIOName: UNASSIGNED Devices: 3 AR 0015 MAC: 02-00-01-00-00-0ELAN: * None And there you have it. The adapter is not COUPLED, as indicated by the * None. An uncoupled NIC is the equivalent of an unplugged ethernet cable. Alan Altmark z/VM Development IBM Endicott _ This message contains information which is privileged and confidential and is solely for the use of the intended recipient. If you are not the intended recipient, be aware that any review, disclosure, copying, distribution, or use of the contents of this message is strictly prohibited. If you have received this in error, please destroy it immediately and notify us at privacy...@ailife.com. _ This message contains information which is privileged and confidential and is solely for the use of the intended recipient. If you are not the intended recipient, be aware that any review, disclosure, copying, distribution, or use of the contents of this message is strictly prohibited. If you have received this in error, please destroy it immediately and notify us
Re: VSWITCH defined VSE TCP/IP fails
1) Yes, but you can have up to 3 triplets (9 address total) 2) Didn't know about the LAN SYSTEM switchname Frank M. Ramaekers Jr. From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Mark Pace Sent: Tuesday, August 31, 2010 9:11 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: VSWITCH defined VSE TCP/IP fails A couple of things On the DEFINE VSWITCH you only need to specify the 1st address of the triplet. On the NICDEF add LAN SYSTEM switchNameand it will be coupled automatically when you logon. example NICDEF 061C TYPE QDIO DEVICES 3 LAN SYSTEM VSWTCH3 OR SPECIAL 061C QDIO 3 SYSTEM VSWTCH3 On Tue, Aug 31, 2010 at 10:04 AM, Frank M. Ramaekers framaek...@ailife.com wrote: No problem. Originally, I had on z/VSE machine with 3 addresses used for TCP/IP. I wished to move this to a layer-3 VSWITCH for redundancy purposes. (Much of the following was derived from the IBM Redbook Linux on IBM eserver zSeries and S/390: VSWITCH and VLAN Features of z/VM 4.4) 1) Define the VSWITCH a. define vswitch vswitchname rdev ccuu1 ccuu2 ccuu3 b. -and- add the same statement to 'SYSTEM CONFIG' file (Remember ccuu1 ccuu2 ccuu3 represent a set of 3 address to be used) 2) Granting access to the VSWITCH a. set vswitch vswitchname grant userid b. -and- add Modify VSwitch vswitchname GRAnt userid to 'SYSTEM CONFIG' c. - or - add the set vswitch command in the AUTOLOG1 startup 3) Defining the simulated NICs a. for userid cmd define nic ccuu4 qdio b. -and- add to the directory for userid: NICDEF ccuu4 TYPE QDIO DEVICES 3 (a above can be skipped, but the userid would have to be logged off then on) 4) Attaching the simulated NIC with couple ccuu4 to system vswitchname (This will need to be performed each time the virtual machine is logged on.) (Don't think I missed anything) Frank M. Ramaekers Jr. From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Billy Bingham Sent: Tuesday, August 31, 2010 7:51 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: VSWITCH defined VSE TCP/IP fails Frank, Would you be willing to share the steps you used to create the VSWITCH? Thanks, Billy On 30 Aug 2010 at 8:11, Frank M. Ramaekers wrote: Thanks, that helpsthe difference between an upCOUPLEd and a COUPLEd VSWITCH: UnCOUPLEd: AR 0015 MAC: 02-00-01-00-00-0E LAN: * NoneMFS: 8992 COUPLEd (and not yet initialized): AR 0015 MAC: 02-00-01-00-00-0E VSWITCH: SYSTEM VSWAILT ...and initialized: * cp q v nic aa0 details AR 0015 Adapter 0AA0.P00 Type: QDIO Name: UNASSIGNED Devices: 3 AR 0015 MAC: 02-00-01-00-00-0E VSWITCH: SYSTEM VSWAILT AR 0015 RX Packets: 49 Discarded: 0 Errors: 0 AR 0015 TX Packets: 42 Discarded: 0 Errors: 0 AR 0015 RX Bytes: 2450 TX Bytes: 2884 AR 0015 Connection Name: Session Established AR 0015 Device: 0AA0 Unit: 000 Role: CTL- READ AR 0015 Device: 0AA1 Unit: 001 Role: CTL- WRITE AR 0015 Device: 0AA2 Unit: 002 Role: DATAvPort: 0065 Index: 0065 AR 0015 Options: IPv4 AR 0015 Unicast IP Addresses: AR 0015 10.1.20.2MAC: 02-00-01-00-00- 0E AR 0015 1I40I READY Thanks Alan! Frank M. Ramaekers Jr. -Original Message- From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Alan Altmark Sent: Friday, August 27, 2010 3:33 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: VSWITCH defined VSE TCP/IP fails On Friday, 08/27/2010 at 04:28 EDT, Frank M. Ramaekers framaek...@ailife.com wrote: * cp q v nic aa0 details AR 0015 Adapter 0AA0.P00 Type: QDIOName: UNASSIGNED Devices: 3 AR 0015 MAC: 02-00-01-00-00-0ELAN: * None And there you have it. The adapter is not COUPLED, as indicated by the * None. An uncoupled NIC is the equivalent of an unplugged ethernet cable. Alan Altmark z/VM Development IBM Endicott _ This message contains information which is privileged and confidential and is solely for the use of the intended recipient. If you are not the intended recipient, be aware that any review, disclosure, copying, distribution, or use of the contents of this message is strictly prohibited. If you have received this in error, please destroy it immediately and notify us at privacy...@ailife.com.
Re: VSWITCH defined VSE TCP/IP fails
What makes this a Layer-3 VSWITCH vs a Layer-2? Thanks, Billy On 31 Aug 2010 at 9:04, Frank M. Ramaekers wrote: No problem. Originally, I had on z/VSE machine with 3 addresses used for TCP/IP. I wished to move this to a layer-3 VSWITCH for redundancy purposes. (Much of the following was derived from the IBM Redbook Linux on IBM eserver zSeries and S/390: VSWITCH and VLAN Features of z/VM 4.4) 1)Define the VSWITCH a.define vswitch vswitchname rdev ccuu1 ccuu2 ccuu3 b.-and- add the same statement to `SYSTEM CONFIG´file (Remember ccuu1 ccuu2 ccuu3 represent a set of 3 address to be used) 2)Granting access to the VSWITCH a.set vswitch vswitchname grant userid b.-and- add Modify VSwitch vswitchnameGRAnt userid to `SYSTEM CONFIG´ c.- or - add the set vswitch command in the AUTOLOG1 startup 3)Defining the simulated NICs a.for userid cmd define nic ccuu4 qdio b.-and- add to the directory for userid: NICDEF ccuu4 TYPE QDIO DEVICES 3 (a above can be skipped, but the userid would have to be logged off then on) 4)Attaching the simulated NIC with couple ccuu4 to system vswitchname (This will need to be performed each time the virtual machine is logged on.) (Don´t think I missed anything) Frank M. Ramaekers Jr. From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Billy Bingham Sent: Tuesday, August 31, 2010 7:51 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: VSWITCH defined VSE TCP/IP fails Frank, Would you be willing to share the steps you used to create the VSWITCH? Thanks, Billy On 30 Aug 2010 at 8:11, Frank M. Ramaekers wrote: Thanks, that helpsthe difference between an upCOUPLEd and a COUPLEd VSWITCH: UnCOUPLEd: AR 0015 MAC: 02-00-01-00-00-0E LAN: * NoneMFS: 8992 COUPLEd (and not yet initialized): AR 0015 MAC: 02-00-01-00-00-0E VSWITCH: SYSTEM VSWAILT ...and initialized: * cp q v nic aa0 details AR 0015 Adapter 0AA0.P00 Type: QDIO Name: UNASSIGNED Devices: 3 AR 0015 MAC: 02-00-01-00-00-0E VSWITCH: SYSTEM VSWAILT AR 0015 RX Packets: 49 Discarded: 0 Errors: 0 AR 0015 TX Packets: 42 Discarded: 0 Errors: 0 AR 0015 RX Bytes: 2450 TX Bytes: 2884 AR 0015 Connection Name: Session Established AR 0015 Device: 0AA0 Unit: 000 Role: CTL- READ AR 0015 Device: 0AA1 Unit: 001 Role: CTL- WRITE AR 0015 Device: 0AA2 Unit: 002 Role: DATAvPort: 0065 Index: 0065 AR 0015 Options: IPv4 AR 0015 Unicast IP Addresses: AR 0015 10.1.20.2MAC: 02-00-01-00-00- 0E AR 0015 1I40I READY Thanks Alan! Frank M. Ramaekers Jr. -Original Message- From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Alan Altmark Sent: Friday, August 27, 2010 3:33 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: VSWITCH defined VSE TCP/IP fails On Friday, 08/27/2010 at 04:28 EDT, Frank M. Ramaekers framaek...@ailife.com wrote: * cp q v nic aa0 details AR 0015 Adapter 0AA0.P00 Type: QDIOName: UNASSIGNED Devices: 3 AR 0015 MAC: 02-00-01-00-00-0ELAN: * None And there you have it. The adapter is not COUPLED, as indicated by the * None. An uncoupled NIC is the equivalent of an unplugged ethernet cable. Alan Altmark z/VM Development IBM Endicott _ This message contains information which is privileged and confidential and is solely for the use of the intended recipient. If you are not the intended recipient, be aware that any review, disclosure, copying, distribution, or use of the contents of this message is strictly prohibited. If you have received this in error, please destroy it immediately and notify us at privacy...@ailife.com. _ This message contains information which is privileged and confidential and is solely for the use of the intended recipient. If you are not the intended recipient, be aware that any review, disclosure, copying, distribution, or use of the contents of this message is strictly prohibited. If you have received this in error, please destroy it immediately and notify us at privacy...@ailife.com.
Re: VSWITCH defined VSE TCP/IP fails
The stack has to have this capability. AFAIK, only Linux can do this. Frank M. Ramaekers Jr. From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Billy Bingham Sent: Tuesday, August 31, 2010 9:32 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: VSWITCH defined VSE TCP/IP fails What makes this a Layer-3 VSWITCH vs a Layer-2? Thanks, Billy On 31 Aug 2010 at 9:04, Frank M. Ramaekers wrote: No problem. Originally, I had on z/VSE machine with 3 addresses used for TCP/IP. I wished to move this to a layer-3 VSWITCH for redundancy purposes. (Much of the following was derived from the IBM Redbook Linux on IBM eserver zSeries and S/390: VSWITCH and VLAN Features of z/VM 4.4) 1)Define the VSWITCH a.define vswitch vswitchname rdev ccuu1 ccuu2 ccuu3 b.-and- add the same statement to 'SYSTEM CONFIG'file (Remember ccuu1 ccuu2 ccuu3 represent a set of 3 address to be used) 2)Granting access to the VSWITCH a.set vswitch vswitchname grant userid b.-and- add Modify VSwitch vswitchnameGRAnt userid to 'SYSTEM CONFIG' c.- or - add the set vswitch command in the AUTOLOG1 startup 3)Defining the simulated NICs a.for userid cmd define nic ccuu4 qdio b.-and- add to the directory for userid: NICDEF ccuu4 TYPE QDIO DEVICES 3 (a above can be skipped, but the userid would have to be logged off then on) 4)Attaching the simulated NIC with couple ccuu4 to system vswitchname (This will need to be performed each time the virtual machine is logged on.) (Don't think I missed anything) Frank M. Ramaekers Jr. From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Billy Bingham Sent: Tuesday, August 31, 2010 7:51 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: VSWITCH defined VSE TCP/IP fails Frank, Would you be willing to share the steps you used to create the VSWITCH? Thanks, Billy On 30 Aug 2010 at 8:11, Frank M. Ramaekers wrote: Thanks, that helpsthe difference between an upCOUPLEd and a COUPLEd VSWITCH: UnCOUPLEd: AR 0015 MAC: 02-00-01-00-00-0E LAN: * NoneMFS: 8992 COUPLEd (and not yet initialized): AR 0015 MAC: 02-00-01-00-00-0E VSWITCH: SYSTEM VSWAILT ...and initialized: * cp q v nic aa0 details AR 0015 Adapter 0AA0.P00 Type: QDIO Name: UNASSIGNED Devices: 3 AR 0015 MAC: 02-00-01-00-00-0E VSWITCH: SYSTEM VSWAILT AR 0015 RX Packets: 49 Discarded: 0 Errors: 0 AR 0015 TX Packets: 42 Discarded: 0 Errors: 0 AR 0015 RX Bytes: 2450 TX Bytes: 2884 AR 0015 Connection Name: Session Established AR 0015 Device: 0AA0 Unit: 000 Role: CTL- READ AR 0015 Device: 0AA1 Unit: 001 Role: CTL- WRITE AR 0015 Device: 0AA2 Unit: 002 Role: DATAvPort: 0065 Index: 0065 AR 0015 Options: IPv4 AR 0015 Unicast IP Addresses: AR 0015 10.1.20.2MAC: 02-00-01-00-00- 0E AR 0015 1I40I READY Thanks Alan! Frank M. Ramaekers Jr. -Original Message- From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Alan Altmark Sent: Friday, August 27, 2010 3:33 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: VSWITCH defined VSE TCP/IP fails On Friday, 08/27/2010 at 04:28 EDT, Frank M. Ramaekers framaek...@ailife.com wrote: * cp q v nic aa0 details AR 0015 Adapter 0AA0.P00 Type: QDIOName: UNASSIGNED Devices: 3 AR 0015 MAC: 02-00-01-00-00-0ELAN: * None And there you have it. The adapter is not COUPLED, as indicated by the * None. An uncoupled NIC is the equivalent of an unplugged ethernet cable. Alan Altmark z/VM Development IBM Endicott _ This message contains information which is privileged and confidential and is solely for the use of the intended recipient. If you are not the intended recipient, be aware that any review, disclosure, copying, distribution, or use of the contents of this message is strictly prohibited. If you have received this in error, please destroy it immediately and notify us at privacy...@ailife.com. _ This message contains information which is privileged and confidential and is solely for the use of the intended recipient. If you are not the intended recipient, be aware
Re: VSWITCH defined VSE TCP/IP fails
Learned something today - I didn't realize there could be 2 backup triplets. Sorry for raising the SNR! ;-) On Tue, Aug 31, 2010 at 10:22 AM, Alan Altmark alan_altm...@us.ibm.comwrote: On Tuesday, 08/31/2010 at 10:11 EDT, Mark Pace pacemainl...@gmail.com wrote: A couple of things On the DEFINE VSWITCH you only need to specify the 1st address of the triplet. That's not a triplet. It's a specification of a primary and two backup OSA triplets. E.g. RDEV 1E00 1F00 2000. On the NICDEF add LAN SYSTEM switchNameand it will be coupled automatically when you logon. example NICDEF 061C TYPE QDIO DEVICES 3 LAN SYSTEM VSWTCH3 OR SPECIAL 061C QDIO 3 SYSTEM VSWTCH3 Please use NICDEF instead of SPECIAL. Alan Altmark z/VM Development IBM Endicott -- Mark D Pace Senior Systems Engineer Mainline Information Systems
Re: VSWITCH defined VSE TCP/IP fails
On Tuesday, 08/31/2010 at 10:32 EDT, Billy Bingham billy.bingham...@suddenlink.net wrote: What makes this a Layer-3 VSWITCH vs a Layer-2? If the VSWITCH is defined with the ETHERNET option, it is layer 2. If you let it default to (or specify) the IP option, it is layer 3. Only z/OS is limited to layer 3. Everyone else (with current software) can use layer 2. Alan Altmark z/VM Development IBM Endicott
Re: VSWITCH defined VSE TCP/IP fails
When did VSE pick up layer 2 support? On Tue, Aug 31, 2010 at 10:52 AM, Alan Altmark alan_altm...@us.ibm.comwrote: On Tuesday, 08/31/2010 at 10:32 EDT, Billy Bingham billy.bingham...@suddenlink.net wrote: What makes this a Layer-3 VSWITCH vs a Layer-2? If the VSWITCH is defined with the ETHERNET option, it is layer 2. If you let it default to (or specify) the IP option, it is layer 3. Only z/OS is limited to layer 3. Everyone else (with current software) can use layer 2. Alan Altmark z/VM Development IBM Endicott -- Mark D Pace Senior Systems Engineer Mainline Information Systems
Re: VSWITCH defined VSE TCP/IP fails
DEFINE VSWITCH VSWTCH1 RDEV 0600 CONTR * *ETH*-* Layer 2 * Define VSWITCH VSWTCH3 RDEV 0604 CONTR ** IP* -*Layer 3* On Tue, Aug 31, 2010 at 10:31 AM, Billy Bingham billy.bingham...@suddenlink.net wrote: What makes this a Layer-3 VSWITCH vs a Layer-2? Thanks, Billy On 31 Aug 2010 at 9:04, Frank M. Ramaekers wrote: No problem. Originally, I had on z/VSE machine with 3 addresses used for TCP/IP. I wished to move this to a layer-3 VSWITCH for redundancy purposes. (Much of the following was derived from the IBM Redbook “Linux on IBM eserver zSeries and S/390: VSWITCH and VLAN Features of z/VM 4.4”) 1)Define the VSWITCH a.define vswitch vswitchname rdev ccuu1 ccuu2 ccuu3 b.–and- add the same statement to ‘SYSTEM CONFIG’file (Remember ccuu1 ccuu2 ccuu3 represent a set of 3 address to be used) 2)Granting access to the VSWITCH a.set vswitch vswitchname grant userid b.–and- add Modify VSwitch vswitchnameGRAnt userid to ‘SYSTEM CONFIG’ c.– or – add the set vswitch command in the AUTOLOG1 startup 3)Defining the simulated NICs a.for userid cmd define nic ccuu4 qdio b.–and- add to the directory for userid: NICDEF ccuu4 TYPE QDIO DEVICES 3 (a above can be skipped, but the userid would have to be logged off then on) 4)Attaching the simulated NIC with couple ccuu4 to system vswitchname (This will need to be performed each time the virtual machine is logged on.) (Don’t think I missed anything) Frank M. Ramaekers Jr. From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Billy Bingham Sent: Tuesday, August 31, 2010 7:51 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: VSWITCH defined VSE TCP/IP fails Frank, Would you be willing to share the steps you used to create the VSWITCH? Thanks, Billy On 30 Aug 2010 at 8:11, Frank M. Ramaekers wrote: Thanks, that helpsthe difference between an upCOUPLEd and a COUPLEd VSWITCH: UnCOUPLEd: AR 0015 MAC: 02-00-01-00-00-0E LAN: * NoneMFS: 8992 COUPLEd (and not yet initialized): AR 0015 MAC: 02-00-01-00-00-0E VSWITCH: SYSTEM VSWAILT ...and initialized: * cp q v nic aa0 details AR 0015 Adapter 0AA0.P00 Type: QDIO Name: UNASSIGNED Devices: 3 AR 0015 MAC: 02-00-01-00-00-0E VSWITCH: SYSTEM VSWAILT AR 0015 RX Packets: 49 Discarded: 0 Errors: 0 AR 0015 TX Packets: 42 Discarded: 0 Errors: 0 AR 0015 RX Bytes: 2450 TX Bytes: 2884 AR 0015 Connection Name: Session Established AR 0015 Device: 0AA0 Unit: 000 Role: CTL- READ AR 0015 Device: 0AA1 Unit: 001 Role: CTL- WRITE AR 0015 Device: 0AA2 Unit: 002 Role: DATAvPort: 0065 Index: 0065 AR 0015 Options: IPv4 AR 0015 Unicast IP Addresses: AR 0015 10.1.20.2MAC: 02-00-01-00-00- 0E AR 0015 1I40I READY Thanks Alan! Frank M. Ramaekers Jr. -Original Message- From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Alan Altmark Sent: Friday, August 27, 2010 3:33 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: VSWITCH defined VSE TCP/IP fails On Friday, 08/27/2010 at 04:28 EDT, Frank M. Ramaekers framaek...@ailife.com wrote: * cp q v nic aa0 details AR 0015 Adapter 0AA0.P00 Type: QDIOName: UNASSIGNED Devices: 3 AR 0015 MAC: 02-00-01-00-00-0ELAN: * None And there you have it. The adapter is not COUPLED, as indicated by the * None. An uncoupled NIC is the equivalent of an unplugged ethernet cable. Alan Altmark z/VM Development IBM Endicott _ This message contains information which is privileged and confidential and is solely for the use of the intended recipient. If you are not the intended recipient, be aware that any review, disclosure, copying, distribution, or use of the contents of this message is strictly prohibited. If you have received this in error, please destroy it immediately and notify us at privacy...@ailife.com. _ This message contains information which is privileged and confidential and is solely for the use of the intended recipient. If you are not the intended recipient, be aware that any review, disclosure, copying, distribution, or use of the contents of this message is strictly prohibited. If you have received this in error, please destroy it immediately and notify us at privacy...@ailife.com. -- Mark D Pace Senior
Re: Electronic Delivery - DDR or DVD?
On Tuesday, 08/31/2010 at 09:54 EDT, George Henke/NYLIC george_he...@newyorklife.com wrote: I have done as you said and here are the instructions. I have bolded the text in question. The instructions call for selecting DDR. Then the instructions at the bottom for installing from FTP Server, Chapter 7, Step 3 of Guide For Automated Installation and Service, call for using the downloaded DVD image. Apparently, we are to download DDR to upload DVD. Ah, now I understand (I think). Big Picture: There are three possible ways to get z/VM: 1. On DVD by ordering z/VM System Image DVD on 3590 or 3592. (Huh?) Don't worry - you won't receive a tape, just a DVD. 2. Electronically, by ordering z/VM 3390 System DDR using Internet delivery. But don't be fooled by the name! It is actually a softcopy of the DVD contents (not an iso file). 3. On tape by ordering z/VM 3390 System DDR on 3590 or 3592. Aha! You actually get what you seem to have ordered. For reasons that are both embarrassing and inexplicable, we do not yet have the ability to have a single z/VM product (e.g. z/VM V6.1) available in four different media types (DVD, 3590, 3592, Softcopy). Progress is occurring, but it's slow. If you want to install from FTP using, you order the DDR with electronic delivery and follow the special instructions included with the order. Those instructions have you load the softcopy files into your FTP server. You can also create a DVD from them. Your completed Shopz order contains links to instructions on how to do that. (I worry that people don't see them.) If you'd like to see them: http://www.vm.ibm.com/install/vm54inst.pdf http://www.vm.ibm.com/install/vm61inst.pdf Most people create a DVD so that they have a bootable system recovery disc just in case. We are making efforts to improve the Planning sections of the Automated Installation book and the post-order instructions so that the above will be more obvious, with explicit references between the two. Alan Altmark z/VM Development IBM Endicott
Re: Electronic Delivery - DDR or DVD?
tyvm, Alan, it explains everything. Alan Altmark alan_altm...@us.ibm.com Sent by: The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU 08/31/2010 04:33 PM Please respond to The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU To IBMVM@LISTSERV.UARK.EDU cc Subject Re: Electronic Delivery - DDR or DVD? On Tuesday, 08/31/2010 at 09:54 EDT, George Henke/NYLIC george_he...@newyorklife.com wrote: I have done as you said and here are the instructions. I have bolded the text in question. The instructions call for selecting DDR. Then the instructions at the bottom for installing from FTP Server, Chapter 7, Step 3 of Guide For Automated Installation and Service, call for using the downloaded DVD image. Apparently, we are to download DDR to upload DVD. Ah, now I understand (I think). Big Picture: There are three possible ways to get z/VM: 1. On DVD by ordering z/VM System Image DVD on 3590 or 3592. (Huh?) Don't worry - you won't receive a tape, just a DVD. 2. Electronically, by ordering z/VM 3390 System DDR using Internet delivery. But don't be fooled by the name! It is actually a softcopy of the DVD contents (not an iso file). 3. On tape by ordering z/VM 3390 System DDR on 3590 or 3592. Aha! You actually get what you seem to have ordered. For reasons that are both embarrassing and inexplicable, we do not yet have the ability to have a single z/VM product (e.g. z/VM V6.1) available in four different media types (DVD, 3590, 3592, Softcopy). Progress is occurring, but it's slow. If you want to install from FTP using, you order the DDR with electronic delivery and follow the special instructions included with the order. Those instructions have you load the softcopy files into your FTP server. You can also create a DVD from them. Your completed Shopz order contains links to instructions on how to do that. (I worry that people don't see them.) If you'd like to see them: http://www.vm.ibm.com/install/vm54inst.pdf http://www.vm.ibm.com/install/vm61inst.pdf Most people create a DVD so that they have a bootable system recovery disc just in case. We are making efforts to improve the Planning sections of the Automated Installation book and the post-order instructions so that the above will be more obvious, with explicit references between the two. Alan Altmark z/VM Development IBM Endicott
