Re: the hessling editor and regina rexx
I have REXX-Regina_3.4(MT) 5.00 30 Dec 2007 in SLES11 SP1. Think I had to compile it, but not sure. It works, but we don't really use it, so I can't say everything works. ___ Tore Agblad Volvo Information Technology Infrastructure Mainframe Design Development, Linux servers Dept 4352 DA1S SE-405 08, Gothenburg Sweden Telephone: +46-31-3233569 E-mail: tore.agb...@volvo.com http://www.volvo.com/volvoit/global/en-gb/ -Original Message- From: Linux on 390 Port [mailto:linux-...@vm.marist.edu] On Behalf Of Smith, Ann (ISD, IT) Sent: den 22 oktober 2010 00:27 To: LINUX-390@VM.MARIST.EDU Subject: the hessling editor and regina rexx Anyone know what the latest version of 'the' is that is available and what versions of regina it is compatible with? I see the33Bw32 on sourceforge . The date is March 2008. Was looking for the that can be run with SLES10 SP3 and later. Ann Smith Mainframe Systems Support -zVM and zLinux Support Integrated Technology Delivery IBM Global Service Integrated Operations At The Hartford Work phone: 860-547-6110 Pager: 800-204-6367 Email: mailto:ann.sm...@thehartford.com This communication, including attachments, is for the exclusive use of addressee and may contain proprietary, confidential and/or privileged information. If you are not the intended recipient, any use, copying, disclosure, dissemination or distribution is strictly prohibited. If you are not the intended recipient, please notify the sender immediately by return e-mail, delete this communication and destroy all copies. -- 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: mon_fsstatd - filesystem monitor records
We use putfiles to write the records, the filename/filetype contains the date and recordID. This is part of a larger pipeline that contains some logic to enable us to comunicatie with the MONWRITE machine. '\ STARMON MONDCSS SHARED',/* connect to MONITOR*/ '| specs 9.8 1.8', /* Get TOD clock */ ' 5 c2x 10 7.2 c2x nw 1-* nw', /* Translate D R */ '| a: lookup 10-16 1-7 details', /* Only selected records */ '| dateconv 1.8 todabs rexxj timeout', /* Convert tot to julian */ '| specs w1 1 /_/ next /00/ next', /* Build filename : 10271_00 */ '/D/ nw w3 next', /* Build filetype : D0A */ '/R/ next w4 next',/* Build filetype :R0002 */ '/D/ nw', /* Build filemode : D*/ 'w5-* next', /* Remaining data*/ '| putfiles append grouped', /* write files */ '\ moncolct param x',/* Parameter file*/ '| a:' The param file contains the records we want to write to disk such as 0A 0002. If you want files for every hour replace the /00/ with 7.2 . Regards, Berry. -Original Message- From: Linux on 390 Port [mailto:linux-...@vm.marist.edu] On Behalf Of Scott Rohling Sent: vrijdag 22 oktober 2010 1:45 To: LINUX-390@VM.MARIST.EDU Subject: Re: mon_fsstatd - filesystem monitor records One thing - I don't seem to actually see the output file on disk until I stop the PIPE.. is there a way to run pipe starmon and have it output records to disk as they are received?When I LINK to the disk from another userid - I don't see a file at all until I 'hx' out of the pipe. Scott Rohling On Thu, Oct 21, 2010 at 1:13 PM, Berry van Sleeuwen berry.vansleeu...@xs4all.nl wrote: The most easiest: PIPE STARMON | monwrite file a, that way you will write one record to disk for each record in CP MONITOR. In this case you won't have to figure out how to parse the records or to process them afterwards with MONVIEW. Just connect a test CMS machine to MONITOR if you can't use MONWRITE for this. Regards, Berry. Op 21-10-10 21:04, Scott Rohling schreef: Hi Berry - Thanks very much for your reply - you're right - I was being too simplistic in plumbing the MONWRITE data. I used MONVIEW and quickly did an XLATE A2E against the output - I can now see dasda1, etc in the output. So I obviously need to parse the MONWRITE data correctly. I'll poke around the MONVIEW stuff to figure it out. Thanks again! Scott Rohling On Thu, Oct 21, 2010 at 12:28 PM, Berry van Sleeuwen berry.vansleeu...@xs4all.nl wrote: Hi scott, We do see records for every mounted filesystem. Both on SLES10 SP2 and SLES11 SP1. Indeed, have option APPLMON for the guest and start mon_fsstatd. Actually we have APPLDATA, mon_fsstatd and mon_procd running. We run two machines on the CP MONITOR running custom plumbing. The first only writes selected recordtypes to disk (such as Dom. 10 Rec. 2). The second CMS machine monitors the filesystem records and creates incidents based on certain thresholds on filesystem usage. We don't run the IBM MONWRITE. First of all we'd like to write only those records we are interested in. And second, MONWRITE writes the file into fixed 4096 records instead of one record for each monitor record. Do you know for sure your plumbing does indeed get the records the correct way? Have you tried the MONVIEW package from the IBM VM packages? Regards, Berry. Op 21-10-10 17:16, Scott Rohling schreef: I am trying to use the mon_fsstatd driver (s390-tools) to generate monitor records with Linux fileystem stats. The guest has OPTION APPLMON and ability to write monitor records. Records 'do' seem to be generated - but it seems like it's only for a single filesystem (/dev/dasdd1, which happens to be the last listed if you do a df -h). According to the device drivers manual -- a record should be generated for each physical mounted filesystem. I'm only seeing one. As an aside - I am viewing the records on z/VM by linking to MONWRITE 191 and using some creative PIPEing to translate the ascii fields to ebcdic, etc... Basically getting all records with 'LNXAPPL' in ascii and parsing them. So pretty sure I'm not missing records that are being written for APPLDATA ... Has anyone else used this driver and gotten different/better results? (I'm running this on RHEL54 under z/VM 5.4) Scott Rohling -- 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
CAVMEN Meeting on Thursday, October 28, 2010
The fourth quarter meeting of the Chicago Area VM (and Linux) Enthusiasts will be held on Thursday, October 28, 2010. We are scheduled to meet in room M2 off the cafeteria, it is right next to room M3 where we frequently meet. NOTE: We have a very full agenda for this meeting, and we will be starting promptly at 9:00AM. All of the road construction in the Hewitt area has been completed. There should be no unusual traffic delay. -- Meeting Location: This quarter's meeting will be held at the Hewitt Associates 'East Campus' located at 100 Half Day Road, in Lincolnshire, IL. We will meet in Conference Room 100-M2, in Building 100, just off the cafeteria. If you have not attended a meeting at this location before, or you are not familiar with the area, http://cavmen.home.comcast.net/hewittb99.htmlClick here for additional information on directions, maps, lodging and dining. -- Attendance: We would like to request a count of expected attendees by the Monday before the meeting, so that we may plan appropriately for arranging the facilities, and for refreshments and lunch, should one of the vendors wish to provide them. If you are planning to attend, PLEASE send an E-Mail by that date to mailto:cav...@comcast.netcav...@comcast.net with a subject line of Meeting Attendance. This is meant to be a facilities planning aid and should not be interpreted as a registration requirement. If you suddenly become available at the last minute, please feel free to attend even if you have not responded. Thank you in advance for your cooperation in this matter. -- Meeting Agenda: 9:00 AM z/VM Platform Update This session will provide you with the latest greatest information about z/VM. We will discuss the recently announced updates to z/VM V5.4 and z/VM 6.1, including support for the IBM zEnterprise System, as well as the Statements of Direction for Single-System Image and Live Guest Relocation. The speaker will be John Franciscovich of the IBM Corporation. 10:05 AMCoffee Break 10:15 AMz/VM Single System Image and Guest Mobility Preview IBM has issued a Statement of Direction describing its intent to permit multiple z/VM Systems to collaborate in a Single System Image cluster, and to allow a running guest to be moved from one member of a cluster to another with Live Guest Relocation. This presentation provides a preview of these enhancements. The speaker will be John Franciscovich of the IBM Corporation. 11:30 PMLunch Break 12:30 PMAdministration and Vendor Announcements 12:45 PMLinux on z Update The speaker will present a brief update of recent developments in the Linux under z/VM area. The speaker will be Paul Augustyniak of the IBM Corporation. 1:00 PM CSL-WAVE - Linux / z/VM Virtual Server Management CSL-WAVE, is very unique in the sense that it provides complete freedom to our users to operate z/VM-based virtual server farms while eliminating the need for the Linux sys-admins to develop a z/VM skill set. CSL-WAVE abstracts the z/VM resources and knowhow via its intuitive GUI and architecture to the point that CSL-WAVE users do not need to resort to the z/VM system programming dept for help for any of their day-to-day infrastructure management nor for even more advanced activities such as storage or network management. All within the scope and permissions that are dictated by the site-level CSL-WAVE administration function (Usually the z/VM system programmer). The product handles all aspects of the virtual server farm: Virtual server management, provisioning, storage managed at the server and z/VM instance level, Network (GLANs and VSwitches), even script management across the virtual server farm. The speaker will be Sharon Chen, Founder and CEO of CSL-International. 2:15 PM Coffee Break 2:30 PM What's new from IBM for automating operations on z/VM and Linux on System z As the Linux on System z environment continues to grow, the need for software and solutions to manage this environment also grows. IBM continues to enhance a set of software solutions to assist customers with automated operations, system management, and storage management. This session will focus on automated operations and what's new in Operations Manager for z/VM V1.4, announced and available in September 2010. Live demos will be included. The speaker will be Tracy Dean of the IBM Corporation. 3:30 PM Coffee Break and Prize Drawing 3:45 PM What's new from IBM for tape management on z/VM As the Linux on System z environment continues to grow, the need for software and solutions to manage this environment also grows. IBM continues to enhance a set of software solutions to assist customers with automated operations, system management, and storage management. This session will focus on tape management and what's new in Tape Manager for z/VM V1.3, announced and available in September 2010. The speaker will
Re: mon_fsstatd - filesystem monitor records
You can use 'diskslow' to write the records, but that might not be a good idea for all of the monitor data unless you are only writing the records you want and filtering out the rest. The other thing you should do is set up a delay stage and issue a FINIS every so often (10 secs, 30 secs, whatever you need.) Such as: '? literal +30', '| dup *', '| delay', '| spec /FINIS * * A/ 1', '| command' On Thu, Oct 21, 2010 at 7:45 PM, Scott Rohling scott.rohl...@gmail.com wrote: One thing - I don't seem to actually see the output file on disk until I stop the PIPE.. is there a way to run pipe starmon and have it output records to disk as they are received? When I LINK to the disk from another userid - I don't see a file at all until I 'hx' out of the pipe. Scott Rohling -- Bruce Hayden z/VM and Linux on System z ATS IBM, Endicott, NY -- 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/
zVM updated, VLAN dead
Hi Folks! I have a very strange problem on a client here. We had a zVM 5.4 running flawlessly, with vswitch and vlan tagging. Yesterday we updated zVM to 6.1. Even this being a big change, it was the only change we did. We had a gateway machine, lnxadm, with a eth0 coupled to a vswitch (VADM) on VLAN 812. If we try to ping the gateway, we get an Destination Host Unreachable. We have other linuxes on the same environmente, and we can ssh to any of them, without any problem. This is our environment: CP Q NIC DET Adapter 0700.P00 Type: QDIO Name: UNASSIGNED Devices: 3 MAC: 02-00-00-00-00-04 VSWITCH: SYSTEM VADM RX Packets: 5 Discarded: 0 Errors: 0 TX Packets: 39 Discarded: 18 Errors: 0 RX Bytes: 320 TX Bytes: 2226 Connection Name: HALLOLE State: Session Established Device: 0700 Unit: 000 Role: CTL-READ Device: 0701 Unit: 001 Role: CTL-WRITE Device: 0702 Unit: 002 Role: DATA vPort: 0081 Index: 0081 VLAN: 0812 Options: Ethernet Broadcast Unicast MAC Addresses: 02-00-00-00-00-04 Multicast MAC Addresses: 01-00-5E-00-00-01 33-33-00-00-00-01 33-33-FF-00-00-04 ifconfig eth0 eth0 Link encap:Ethernet HWaddr 02:00:00:00:00:04 inet addr:10.9.49.15 Bcast:10.9.49.255 Mask:255.255.255.0 inet6 addr: fe80::ff:fe00:4/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1492 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:57 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 b) TX bytes:3258 (3.1 KiB) cat /etc/sysconfig/network-scripts/ifcfg-eth0 # IBM QETH DEVICE=eth0 ARP=yes OPTIONS=layer2=1 BOOTPROTO=none IPADDR=10.9.49.15 NETMASK=255.255.255.0 NETTYPE=qeth ONBOOT=yes SUBCHANNELS=0.0.0700,0.0.0701,0.0.0702 TYPE=Ethernet USERCTL=no IPV6INIT=no PEERDNS=yes CP Q LAN VADM DET VSWITCH SYSTEM VADM Type: VSWITCH Connected: 14 Maxconn: INFINITE PERSISTENT RESTRICTEDETHERNET Accounting: OFF VLAN Aware Default VLAN: 0812Default Porttype: Trunk GVRP: Enabled Native VLAN: 0001VLAN Counters: OFF MAC address: 02-00-00-00-00-01 State: Ready IPTimeout: 5 QueueStorage: 8 Isolation Status: OFF RDEV: 8003.P00 VDEV: 8003 Controller: DTCVSW1 RDEV: 8006.P00 VDEV: 8006 Controller: DTCVSW2 BACKUP Adapter Connections: Adapter Owner: LNXADM NIC: 0700.P00 Name: UNASSIGNED Porttype: Trunk RX Packets: 5 Discarded: 0 Errors: 0 TX Packets: 39 Discarded: 18 Errors: 0 RX Bytes: 320 TX Bytes: 2226 Device: 0702 Unit: 002 Role: DATA vPort: 0081 Index: 0081 VLAN: 0812 Options: Ethernet Broadcast Unicast MAC Addresses: 02-00-00-00-00-04 Multicast MAC Addresses: 01-00-5E-00-00-01 33-33-00-00-00-01 33-33-FF-00-00-04 CP Q VSWITCH VADM DET VSWITCH SYSTEM VADM Type: VSWITCH Connected: 14 Maxconn: INFINITE PERSISTENT RESTRICTEDETHERNET Accounting: OFF VLAN Aware Default VLAN: 0812Default Porttype: Trunk GVRP: Enabled Native VLAN: 0001VLAN Counters: OFF MAC address: 02-00-00-00-00-01 State: Ready IPTimeout: 5 QueueStorage: 8 Isolation Status: OFF RDEV: 8003.P00 VDEV: 8003 Controller: DTCVSW1 VSWITCH Connection: RX Packets: 1058558Discarded: 2642 Errors: 0 TX Packets: 830546 Discarded: 0 Errors: 0 RX Bytes: 477088169TX Bytes: 264909169 Device: 8003 Unit: 000 Role: DATA vPort: 0001 Index: 0001 Unicast IP Addresses: 10.9.49.1MAC: 00-04-23-AD-42-1A Remote RDEV: 8006.P00 VDEV: 8006 Controller: DTCVSW2 BACKUP Adapter Connections: Adapter Owner: LNXADM NIC: 0700.P00 Name: UNASSIGNED Porttype: Trunk RX Packets: 5 Discarded: 0 Errors: 0 TX Packets: 39 Discarded: 18 Errors: 0 RX Bytes: 320 TX Bytes: 2226 Device: 0702 Unit: 002 Role: DATA vPort: 0081 Index: 0081 VLAN: 0812 Options: Ethernet Broadcast Unicast MAC Addresses: 02-00-00-00-00-04 Multicast MAC Addresses: 01-00-5E-00-00-01 33-33-00-00-00-01 33-33-FF-00-00-04 CP Q VSWITCH VADM ACC VSWITCH SYSTEM VADM Type: VSWITCH Connected: 14 Maxconn: INFINITE PERSISTENT RESTRICTEDETHERNET Accounting: OFF VLAN Aware Default VLAN: 0812Default Porttype: Trunk GVRP: Enabled Native VLAN: 0001VLAN Counters: OFF MAC address: 02-00-00-00-00-01 State: Ready IPTimeout: 5 QueueStorage: 8 Isolation Status: OFF Authorized userids: LNXADM Porttype: Trunk VLAN: 0812
2010-10-22 Linux on System z kernel 2.6.36 related updates on developerWorks
Please refer to http://www.ibm.com/developerworks/linux/linux390/whatsnew.html for several updates to the 'Development stream': * description of upstream kernel 2.6.36 features that were contributed by Linux on System z development * kernel 2.6.36 patch for kernel message catalog * s390-tools 1.11.0 delivers new functionality and bugfixes * updated documentation -- Device Drivers, Features, and Commands -- Using the Dump Tools -- Kernel Messages as well as updated Restrictions and Technical Details * end of message Mit freundlichen Grüßen / Kind regards Gerhard Hiller Systems Software Management IBM Systems Technology Group, Systems Software Development Phone: +49-7031-16-4388 IBM Deutschland Fax: +49-7031-16-3545 Schoenaicher Str. 220 E-Mail: ghil...@de.ibm.com 71032 Boeblingen Germany IBM Deutschland Research Development GmbH / Vorsitzender des Aufsichtsrats: Martin Jetter Geschäftsführung: Dirk Wittkopp Sitz der Gesellschaft: Böblingen / Registergericht: Amtsgericht Stuttgart, HRB 243294 image/gifimage/gifimage/gifimage/gifimage/gifimage/gifimage/gif
Re: zVM updated, VLAN dead
Did you grant access for LNXADM to the VSWITCH, VADM? You can grant access to the user by logging into MAINT and issuing SET VSWITCH VADM GRANT LNXADM. Thang 2455 South Road (Embedded Phamimage moved to file: pic56110.gif) Phone:(845) 433-7567Poughkeepsie, NY 12601 e-mail: thang.p...@us.ibm.com From: Mauro Souza thoriu...@gmail.com To: LINUX-390@vm.marist.edu Date: 10/22/2010 09:02 AM Subject:zVM updated, VLAN dead Sent by:Linux on 390 Port LINUX-390@vm.marist.edu Hi Folks! I have a very strange problem on a client here. We had a zVM 5.4 running flawlessly, with vswitch and vlan tagging. Yesterday we updated zVM to 6.1. Even this being a big change, it was the only change we did. We had a gateway machine, lnxadm, with a eth0 coupled to a vswitch (VADM) on VLAN 812. If we try to ping the gateway, we get an Destination Host Unreachable. We have other linuxes on the same environmente, and we can ssh to any of them, without any problem. This is our environment: CP Q NIC DET Adapter 0700.P00 Type: QDIO Name: UNASSIGNED Devices: 3 MAC: 02-00-00-00-00-04 VSWITCH: SYSTEM VADM RX Packets: 5 Discarded: 0 Errors: 0 TX Packets: 39 Discarded: 18 Errors: 0 RX Bytes: 320 TX Bytes: 2226 Connection Name: HALLOLE State: Session Established Device: 0700 Unit: 000 Role: CTL-READ Device: 0701 Unit: 001 Role: CTL-WRITE Device: 0702 Unit: 002 Role: DATA vPort: 0081 Index: 0081 VLAN: 0812 Options: Ethernet Broadcast Unicast MAC Addresses: 02-00-00-00-00-04 Multicast MAC Addresses: 01-00-5E-00-00-01 33-33-00-00-00-01 33-33-FF-00-00-04 ifconfig eth0 eth0 Link encap:Ethernet HWaddr 02:00:00:00:00:04 inet addr:10.9.49.15 Bcast:10.9.49.255 Mask:255.255.255.0 inet6 addr: fe80::ff:fe00:4/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1492 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:57 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 b) TX bytes:3258 (3.1 KiB) cat /etc/sysconfig/network-scripts/ifcfg-eth0 # IBM QETH DEVICE=eth0 ARP=yes OPTIONS=layer2=1 BOOTPROTO=none IPADDR=10.9.49.15 NETMASK=255.255.255.0 NETTYPE=qeth ONBOOT=yes SUBCHANNELS=0.0.0700,0.0.0701,0.0.0702 TYPE=Ethernet USERCTL=no IPV6INIT=no PEERDNS=yes CP Q LAN VADM DET VSWITCH SYSTEM VADM Type: VSWITCH Connected: 14 Maxconn: INFINITE PERSISTENT RESTRICTEDETHERNET Accounting: OFF VLAN Aware Default VLAN: 0812Default Porttype: Trunk GVRP: Enabled Native VLAN: 0001VLAN Counters: OFF MAC address: 02-00-00-00-00-01 State: Ready IPTimeout: 5 QueueStorage: 8 Isolation Status: OFF RDEV: 8003.P00 VDEV: 8003 Controller: DTCVSW1 RDEV: 8006.P00 VDEV: 8006 Controller: DTCVSW2 BACKUP Adapter Connections: Adapter Owner: LNXADM NIC: 0700.P00 Name: UNASSIGNED Porttype: Trunk RX Packets: 5 Discarded: 0 Errors: 0 TX Packets: 39 Discarded: 18 Errors: 0 RX Bytes: 320 TX Bytes: 2226 Device: 0702 Unit: 002 Role: DATA vPort: 0081 Index: 0081 VLAN: 0812 Options: Ethernet Broadcast Unicast MAC Addresses: 02-00-00-00-00-04 Multicast MAC Addresses: 01-00-5E-00-00-01 33-33-00-00-00-01 33-33-FF-00-00-04 CP Q VSWITCH VADM DET VSWITCH SYSTEM VADM Type: VSWITCH Connected: 14 Maxconn: INFINITE PERSISTENT RESTRICTEDETHERNET Accounting: OFF VLAN Aware Default VLAN: 0812Default Porttype: Trunk GVRP: Enabled Native VLAN: 0001VLAN Counters: OFF MAC address: 02-00-00-00-00-01 State: Ready IPTimeout: 5 QueueStorage: 8 Isolation Status: OFF RDEV: 8003.P00 VDEV: 8003 Controller: DTCVSW1 VSWITCH Connection: RX Packets: 1058558Discarded: 2642 Errors: 0 TX Packets: 830546 Discarded: 0 Errors: 0 RX Bytes: 477088169TX Bytes: 264909169 Device: 8003 Unit: 000 Role: DATA vPort: 0001 Index: 0001 Unicast IP Addresses: 10.9.49.1MAC: 00-04-23-AD-42-1A Remote RDEV: 8006.P00 VDEV: 8006 Controller: DTCVSW2 BACKUP Adapter Connections: Adapter Owner: LNXADM NIC: 0700.P00 Name: UNASSIGNED Porttype: Trunk RX Packets: 5 Discarded: 0 Errors: 0 TX Packets: 39 Discarded: 18
Re: zVM updated, VLAN dead
Did your SYSTEM CONFIG remain exactly the same? Did you do MODIFY VSWITCH in SYSTEM CONFIG to grant access? Did AUTOLOG1/2 remain exactly the same - did you perhaps issue SET VSWITCH GRANT there? Scott Rohling On Fri, Oct 22, 2010 at 6:59 AM, Mauro Souza thoriu...@gmail.com wrote: Hi Folks! I have a very strange problem on a client here. We had a zVM 5.4 running flawlessly, with vswitch and vlan tagging. Yesterday we updated zVM to 6.1. Even this being a big change, it was the only change we did. We had a gateway machine, lnxadm, with a eth0 coupled to a vswitch (VADM) on VLAN 812. If we try to ping the gateway, we get an Destination Host Unreachable. We have other linuxes on the same environmente, and we can ssh to any of them, without any problem. This is our environment: CP Q NIC DET Adapter 0700.P00 Type: QDIO Name: UNASSIGNED Devices: 3 MAC: 02-00-00-00-00-04 VSWITCH: SYSTEM VADM RX Packets: 5 Discarded: 0 Errors: 0 TX Packets: 39 Discarded: 18 Errors: 0 RX Bytes: 320 TX Bytes: 2226 Connection Name: HALLOLE State: Session Established Device: 0700 Unit: 000 Role: CTL-READ Device: 0701 Unit: 001 Role: CTL-WRITE Device: 0702 Unit: 002 Role: DATA vPort: 0081 Index: 0081 VLAN: 0812 Options: Ethernet Broadcast Unicast MAC Addresses: 02-00-00-00-00-04 Multicast MAC Addresses: 01-00-5E-00-00-01 33-33-00-00-00-01 33-33-FF-00-00-04 ifconfig eth0 eth0 Link encap:Ethernet HWaddr 02:00:00:00:00:04 inet addr:10.9.49.15 Bcast:10.9.49.255 Mask:255.255.255.0 inet6 addr: fe80::ff:fe00:4/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1492 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:57 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 b) TX bytes:3258 (3.1 KiB) cat /etc/sysconfig/network-scripts/ifcfg-eth0 # IBM QETH DEVICE=eth0 ARP=yes OPTIONS=layer2=1 BOOTPROTO=none IPADDR=10.9.49.15 NETMASK=255.255.255.0 NETTYPE=qeth ONBOOT=yes SUBCHANNELS=0.0.0700,0.0.0701,0.0.0702 TYPE=Ethernet USERCTL=no IPV6INIT=no PEERDNS=yes CP Q LAN VADM DET VSWITCH SYSTEM VADM Type: VSWITCH Connected: 14 Maxconn: INFINITE PERSISTENT RESTRICTEDETHERNET Accounting: OFF VLAN Aware Default VLAN: 0812Default Porttype: Trunk GVRP: Enabled Native VLAN: 0001VLAN Counters: OFF MAC address: 02-00-00-00-00-01 State: Ready IPTimeout: 5 QueueStorage: 8 Isolation Status: OFF RDEV: 8003.P00 VDEV: 8003 Controller: DTCVSW1 RDEV: 8006.P00 VDEV: 8006 Controller: DTCVSW2 BACKUP Adapter Connections: Adapter Owner: LNXADM NIC: 0700.P00 Name: UNASSIGNED Porttype: Trunk RX Packets: 5 Discarded: 0 Errors: 0 TX Packets: 39 Discarded: 18 Errors: 0 RX Bytes: 320 TX Bytes: 2226 Device: 0702 Unit: 002 Role: DATA vPort: 0081 Index: 0081 VLAN: 0812 Options: Ethernet Broadcast Unicast MAC Addresses: 02-00-00-00-00-04 Multicast MAC Addresses: 01-00-5E-00-00-01 33-33-00-00-00-01 33-33-FF-00-00-04 CP Q VSWITCH VADM DET VSWITCH SYSTEM VADM Type: VSWITCH Connected: 14 Maxconn: INFINITE PERSISTENT RESTRICTEDETHERNET Accounting: OFF VLAN Aware Default VLAN: 0812Default Porttype: Trunk GVRP: Enabled Native VLAN: 0001VLAN Counters: OFF MAC address: 02-00-00-00-00-01 State: Ready IPTimeout: 5 QueueStorage: 8 Isolation Status: OFF RDEV: 8003.P00 VDEV: 8003 Controller: DTCVSW1 VSWITCH Connection: RX Packets: 1058558Discarded: 2642 Errors: 0 TX Packets: 830546 Discarded: 0 Errors: 0 RX Bytes: 477088169TX Bytes: 264909169 Device: 8003 Unit: 000 Role: DATA vPort: 0001 Index: 0001 Unicast IP Addresses: 10.9.49.1MAC: 00-04-23-AD-42-1A Remote RDEV: 8006.P00 VDEV: 8006 Controller: DTCVSW2 BACKUP Adapter Connections: Adapter Owner: LNXADM NIC: 0700.P00 Name: UNASSIGNED Porttype: Trunk RX Packets: 5 Discarded: 0 Errors: 0 TX Packets: 39 Discarded: 18 Errors: 0 RX Bytes: 320 TX Bytes: 2226 Device: 0702 Unit: 002 Role: DATA vPort: 0081 Index: 0081 VLAN: 0812 Options: Ethernet Broadcast Unicast MAC Addresses: 02-00-00-00-00-04 Multicast MAC Addresses: 01-00-5E-00-00-01 33-33-00-00-00-01 33-33-FF-00-00-04 CP Q VSWITCH VADM ACC VSWITCH SYSTEM VADM Type: VSWITCH Connected: 14 Maxconn: INFINITE PERSISTENT RESTRICTEDETHERNET
Re: the hessling editor and regina rexx
From my SLES11-SP1 sles001:~ rpm -aq the the-3.1-359.1 sles001:~ rpm -qa regina regina-3.4-0.1.44 On Fri, Oct 22, 2010 at 2:23 AM, Agblad Tore tore.agb...@volvo.com wrote: I have REXX-Regina_3.4(MT) 5.00 30 Dec 2007 in SLES11 SP1. Think I had to compile it, but not sure. It works, but we don't really use it, so I can't say everything works. ___ Tore Agblad Volvo Information Technology Infrastructure Mainframe Design Development, Linux servers Dept 4352 DA1S SE-405 08, Gothenburg Sweden Telephone: +46-31-3233569 E-mail: tore.agb...@volvo.com http://www.volvo.com/volvoit/global/en-gb/ -Original Message- From: Linux on 390 Port [mailto:linux-...@vm.marist.edu] On Behalf Of Smith, Ann (ISD, IT) Sent: den 22 oktober 2010 00:27 To: LINUX-390@VM.MARIST.EDU Subject: the hessling editor and regina rexx Anyone know what the latest version of 'the' is that is available and what versions of regina it is compatible with? I see the33Bw32 on sourceforge . The date is March 2008. Was looking for the that can be run with SLES10 SP3 and later. Ann Smith Mainframe Systems Support -zVM and zLinux Support Integrated Technology Delivery IBM Global Service Integrated Operations At The Hartford Work phone: 860-547-6110 Pager: 800-204-6367 Email: mailto:ann.sm...@thehartford.com This communication, including attachments, is for the exclusive use of addressee and may contain proprietary, confidential and/or privileged information. If you are not the intended recipient, any use, copying, disclosure, dissemination or distribution is strictly prohibited. If you are not the intended recipient, please notify the sender immediately by return e-mail, delete this communication and destroy all copies. -- 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/ -- Mark D Pace Senior Systems Engineer Mainline Information Systems -- 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: zVM updated, VLAN dead
Yes, we copied the PROFILE EXEC from autolog1 to the new zvm, copied our system config definitions, and all other machines have connectivity. The only different setting is VLAN ID, our lnxadm is using vlan 812 and other machines uses vlan 809, 810, etc... Mauro http://mauro.limeiratem.com - registered Linux User: 294521 Scripture is both history, and a love letter from God. On Fri, Oct 22, 2010 at 11:15 AM, Scott Rohling scott.rohl...@gmail.comwrote: Did your SYSTEM CONFIG remain exactly the same? Did you do MODIFY VSWITCH in SYSTEM CONFIG to grant access? Did AUTOLOG1/2 remain exactly the same - did you perhaps issue SET VSWITCH GRANT there? Scott Rohling On Fri, Oct 22, 2010 at 6:59 AM, Mauro Souza thoriu...@gmail.com wrote: Hi Folks! I have a very strange problem on a client here. We had a zVM 5.4 running flawlessly, with vswitch and vlan tagging. Yesterday we updated zVM to 6.1. Even this being a big change, it was the only change we did. We had a gateway machine, lnxadm, with a eth0 coupled to a vswitch (VADM) on VLAN 812. If we try to ping the gateway, we get an Destination Host Unreachable. We have other linuxes on the same environmente, and we can ssh to any of them, without any problem. This is our environment: CP Q NIC DET Adapter 0700.P00 Type: QDIO Name: UNASSIGNED Devices: 3 MAC: 02-00-00-00-00-04 VSWITCH: SYSTEM VADM RX Packets: 5 Discarded: 0 Errors: 0 TX Packets: 39 Discarded: 18 Errors: 0 RX Bytes: 320 TX Bytes: 2226 Connection Name: HALLOLE State: Session Established Device: 0700 Unit: 000 Role: CTL-READ Device: 0701 Unit: 001 Role: CTL-WRITE Device: 0702 Unit: 002 Role: DATA vPort: 0081 Index: 0081 VLAN: 0812 Options: Ethernet Broadcast Unicast MAC Addresses: 02-00-00-00-00-04 Multicast MAC Addresses: 01-00-5E-00-00-01 33-33-00-00-00-01 33-33-FF-00-00-04 ifconfig eth0 eth0 Link encap:Ethernet HWaddr 02:00:00:00:00:04 inet addr:10.9.49.15 Bcast:10.9.49.255 Mask:255.255.255.0 inet6 addr: fe80::ff:fe00:4/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1492 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:57 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 b) TX bytes:3258 (3.1 KiB) cat /etc/sysconfig/network-scripts/ifcfg-eth0 # IBM QETH DEVICE=eth0 ARP=yes OPTIONS=layer2=1 BOOTPROTO=none IPADDR=10.9.49.15 NETMASK=255.255.255.0 NETTYPE=qeth ONBOOT=yes SUBCHANNELS=0.0.0700,0.0.0701,0.0.0702 TYPE=Ethernet USERCTL=no IPV6INIT=no PEERDNS=yes CP Q LAN VADM DET VSWITCH SYSTEM VADM Type: VSWITCH Connected: 14 Maxconn: INFINITE PERSISTENT RESTRICTEDETHERNET Accounting: OFF VLAN Aware Default VLAN: 0812Default Porttype: Trunk GVRP: Enabled Native VLAN: 0001VLAN Counters: OFF MAC address: 02-00-00-00-00-01 State: Ready IPTimeout: 5 QueueStorage: 8 Isolation Status: OFF RDEV: 8003.P00 VDEV: 8003 Controller: DTCVSW1 RDEV: 8006.P00 VDEV: 8006 Controller: DTCVSW2 BACKUP Adapter Connections: Adapter Owner: LNXADM NIC: 0700.P00 Name: UNASSIGNED Porttype: Trunk RX Packets: 5 Discarded: 0 Errors: 0 TX Packets: 39 Discarded: 18 Errors: 0 RX Bytes: 320 TX Bytes: 2226 Device: 0702 Unit: 002 Role: DATA vPort: 0081 Index: 0081 VLAN: 0812 Options: Ethernet Broadcast Unicast MAC Addresses: 02-00-00-00-00-04 Multicast MAC Addresses: 01-00-5E-00-00-01 33-33-00-00-00-01 33-33-FF-00-00-04 CP Q VSWITCH VADM DET VSWITCH SYSTEM VADM Type: VSWITCH Connected: 14 Maxconn: INFINITE PERSISTENT RESTRICTEDETHERNET Accounting: OFF VLAN Aware Default VLAN: 0812Default Porttype: Trunk GVRP: Enabled Native VLAN: 0001VLAN Counters: OFF MAC address: 02-00-00-00-00-01 State: Ready IPTimeout: 5 QueueStorage: 8 Isolation Status: OFF RDEV: 8003.P00 VDEV: 8003 Controller: DTCVSW1 VSWITCH Connection: RX Packets: 1058558Discarded: 2642 Errors: 0 TX Packets: 830546 Discarded: 0 Errors: 0 RX Bytes: 477088169TX Bytes: 264909169 Device: 8003 Unit: 000 Role: DATA vPort: 0001 Index: 0001 Unicast IP Addresses: 10.9.49.1MAC: 00-04-23-AD-42-1A Remote RDEV: 8006.P00 VDEV: 8006 Controller: DTCVSW2 BACKUP Adapter Connections: Adapter Owner: LNXADM NIC: 0700.P00 Name: UNASSIGNED Porttype: Trunk RX Packets: 5
Re: the hessling editor and regina rexx
The latest release of THE is 3.3. The latest release of Regina is 3.5. As it happens, I built Regina and THE for NORD Linux. These are ready-to-run, not in RPM nor Deb format. They are package hierarchies on CD and they should fly on *any* distro immediately as-is. You can, of course, copy the content from the CD to your own disk. Or you can mount the CD image and point to it. You can even put these packages into a common storage place ... shared disk, NFS, SAMBA, perhaps even SAN. Find the CD at http://www.casita.net/pub/nord/CD1-s390.iso.gz (It actually contains both i386 and s390 builds. Sorry ... that makes it twice as big.) The hardest thing you have to do to use this directly is create a /usr/opt directory for relocation sym-linkery. Oh ... and you have to sym-link libregina.so in a place where the dynamic loader will find it. Small beans. The recipe is ... mkdir -m 1777 -p /usr/opt # which can itself be sym-linked to /var ln -s /where/you/mounted/regina-3.3/s390 /usr/opt/regina-3.4 ln -s regina.3.4 /usr/opt/regina ln -s /where/you/mounted/the-3.2/s390 /usr/opt/the-3.2 ln -s the-3.2 /usr/opt/the ln -s /usr/opt/regina/lib/libregina.so /usr/local/lib/. Unfortunately, as you can see, this THE and Regina are each one release back, 3.2 and 3.4 respectively. Not sure how I missed updating them. This reminds me that I should publish the current status of NORD Linux. Been meaning to do that since before a certain job change. -- R; On Thu, Oct 21, 2010 at 18:27, Smith, Ann (ISD, IT) ann.sm...@thehartford.com wrote: Anyone know what the latest version of 'the' is that is available and what versions of regina it is compatible with? I see the33Bw32 on sourceforge . The date is March 2008. Was looking for the that can be run with SLES10 SP3 and later. Ann Smith Mainframe Systems Support -zVM and zLinux Support Integrated Technology Delivery IBM Global Service Integrated Operations At The Hartford Work phone: 860-547-6110 Pager: 800-204-6367 Email: mailto:ann.sm...@thehartford.com This communication, including attachments, is for the exclusive use of addressee and may contain proprietary, confidential and/or privileged information. If you are not the intended recipient, any use, copying, disclosure, dissemination or distribution is strictly prohibited. If you are not the intended recipient, please notify the sender immediately by return e-mail, delete this communication and destroy all copies. -- 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: zVM updated, VLAN dead
Authorized userids: LNXADM Porttype: Trunk VLAN: 0812 Did you really mean to attach this Linux guest with a virtual trunk port? Or did you really intend to attach it with an access port to vlan 812? If you attach it to a virtual trunk port, you have to load the 802.1q module to handle the vlan tags which z/VM will send. And if it is only authorized to 1 vlan, there doesn't seem to be any point to use a virtual trunk port. You didn't show your DEF VSWITCH statement, but the output shows that you have the default port type for vnics as trunk: VLAN Aware Default VLAN: 0812Default Porttype: Trunk GVRP: Enabled Native VLAN: 0001VLAN Counters: OFF You probably thought that you needed to specify PORTTYPE TRUNK because you are attached to a trunk port on the real switch. That isn't what this operand does. So, either remove PORTTYPE TRUNK from the vswitch defination (it defaults to PORTTYPE ACCESS) or change the NICDEF to porttype access. I'd recommend removing the PORTTYPE from the VSWITCH defination. On Fri, Oct 22, 2010 at 8:59 AM, Mauro Souza thoriu...@gmail.com wrote: Hi Folks! snip CP Q VSWITCH VADM ACC VSWITCH SYSTEM VADM Type: VSWITCH Connected: 14 Maxconn: INFINITE PERSISTENT RESTRICTED ETHERNET Accounting: OFF VLAN Aware Default VLAN: 0812 Default Porttype: Trunk GVRP: Enabled Native VLAN: 0001 VLAN Counters: OFF MAC address: 02-00-00-00-00-01 State: Ready IPTimeout: 5 QueueStorage: 8 Isolation Status: OFF Authorized userids: LNXADM Porttype: Trunk VLAN: 0812 Mauro http://mauro.limeiratem.com - registered Linux User: 294521 Scripture is both history, and a love letter from God. -- 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/ -- Bruce Hayden z/VM and Linux on System z ATS IBM, Endicott, NY -- 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: mon_fsstatd - filesystem monitor records
Thanks, Berry and Bruce! The FINIS * * A with the delay looks like the simplest way to get the file closed so I can read it from another user... I'm essentially filtering for the LNXAPPL records for the Linux monitoring records. I'm particularly interested in the mon_fsstatd records, but the others may be useful as well.. Scott Rohling On Fri, Oct 22, 2010 at 6:17 AM, Bruce Hayden bjhay...@gmail.com wrote: You can use 'diskslow' to write the records, but that might not be a good idea for all of the monitor data unless you are only writing the records you want and filtering out the rest. The other thing you should do is set up a delay stage and issue a FINIS every so often (10 secs, 30 secs, whatever you need.) Such as: '? literal +30', '| dup *', '| delay', '| spec /FINIS * * A/ 1', '| command' On Thu, Oct 21, 2010 at 7:45 PM, Scott Rohling scott.rohl...@gmail.com wrote: One thing - I don't seem to actually see the output file on disk until I stop the PIPE.. is there a way to run pipe starmon and have it output records to disk as they are received?When I LINK to the disk from another userid - I don't see a file at all until I 'hx' out of the pipe. Scott Rohling -- Bruce Hayden z/VM and Linux on System z ATS IBM, Endicott, NY -- 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: zVM updated, VLAN dead
We granted access to the LNXADM on another vlan (808). Got another IP, from lnxdb (killed to avoid ip conflict), put the ip on LNXADM, no success. Changed PORT TYPE to ACCESS, back to VLAN 812, logoff/logon LNXADM, no success... Shutdown on zVM, loaded the partition with zvm540, and everything is running fine. What seens VERY odd to me is that all configuration on zvm610 and zvm540 are EXACTLY the same, and zvm610 doesn't work. And as today is Friday, and I am flying back home in a couple hours, we will stay on zvm610 until I research more on this. Thanks guys! Mauro http://mauro.limeiratem.com - registered Linux User: 294521 Scripture is both history, and a love letter from God. On Fri, Oct 22, 2010 at 12:16 PM, Bruce Hayden bjhay...@gmail.com wrote: Authorized userids: LNXADM Porttype: Trunk VLAN: 0812 Did you really mean to attach this Linux guest with a virtual trunk port? Or did you really intend to attach it with an access port to vlan 812? If you attach it to a virtual trunk port, you have to load the 802.1q module to handle the vlan tags which z/VM will send. And if it is only authorized to 1 vlan, there doesn't seem to be any point to use a virtual trunk port. You didn't show your DEF VSWITCH statement, but the output shows that you have the default port type for vnics as trunk: VLAN Aware Default VLAN: 0812Default Porttype: Trunk GVRP: Enabled Native VLAN: 0001VLAN Counters: OFF You probably thought that you needed to specify PORTTYPE TRUNK because you are attached to a trunk port on the real switch. That isn't what this operand does. So, either remove PORTTYPE TRUNK from the vswitch defination (it defaults to PORTTYPE ACCESS) or change the NICDEF to porttype access. I'd recommend removing the PORTTYPE from the VSWITCH defination. On Fri, Oct 22, 2010 at 8:59 AM, Mauro Souza thoriu...@gmail.com wrote: Hi Folks! snip CP Q VSWITCH VADM ACC VSWITCH SYSTEM VADM Type: VSWITCH Connected: 14 Maxconn: INFINITE PERSISTENT RESTRICTEDETHERNET Accounting: OFF VLAN Aware Default VLAN: 0812Default Porttype: Trunk GVRP: Enabled Native VLAN: 0001VLAN Counters: OFF MAC address: 02-00-00-00-00-01 State: Ready IPTimeout: 5 QueueStorage: 8 Isolation Status: OFF Authorized userids: LNXADM Porttype: Trunk VLAN: 0812 Mauro http://mauro.limeiratem.com - registered Linux User: 294521 Scripture is both history, and a love letter from God. -- 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/ -- Bruce Hayden z/VM and Linux on System z ATS IBM, Endicott, NY -- 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: zVM updated, VLAN dead
It would be helpful to have the output of Q CPLEVEL and Q VMLAN from both levels. Maybe 6.1 has a key fix or fixes that you don't have on 5.4, and that why it works differently. On Fri, Oct 22, 2010 at 11:40 AM, Mauro Souza thoriu...@gmail.com wrote: We granted access to the LNXADM on another vlan (808). Got another IP, from lnxdb (killed to avoid ip conflict), put the ip on LNXADM, no success. Changed PORT TYPE to ACCESS, back to VLAN 812, logoff/logon LNXADM, no success... Shutdown on zVM, loaded the partition with zvm540, and everything is running fine. What seens VERY odd to me is that all configuration on zvm610 and zvm540 are EXACTLY the same, and zvm610 doesn't work. And as today is Friday, and I am flying back home in a couple hours, we will stay on zvm610 until I research more on this. Thanks guys! Mauro http://mauro.limeiratem.com - registered Linux User: 294521 Scripture is both history, and a love letter from God. -- Bruce Hayden z/VM and Linux on System z ATS IBM, Endicott, NY -- 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: zVM updated, VLAN dead
Just a guess, maybe you don't have VM64604 on your 540 system? And it is probably integrated in 610. That one could change the native vlan without any sound. I was hit by that one when I applied it. Best regards, Pieter Harder pieter.har...@brabantwater.nl tel +31-73-6837133 / +31-6-47272537 -Oorspronkelijk bericht- Van: Linux on 390 Port [mailto:linux-...@vm.marist.edu] Namens Bruce Hayden Verzonden: vrijdag 22 oktober 2010 17:46 Aan: LINUX-390@VM.MARIST.EDU Onderwerp: Re: zVM updated, VLAN dead It would be helpful to have the output of Q CPLEVEL and Q VMLAN from both levels. Maybe 6.1 has a key fix or fixes that you don't have on 5.4, and that why it works differently. On Fri, Oct 22, 2010 at 11:40 AM, Mauro Souza thoriu...@gmail.com wrote: We granted access to the LNXADM on another vlan (808). Got another IP, from lnxdb (killed to avoid ip conflict), put the ip on LNXADM, no success. Changed PORT TYPE to ACCESS, back to VLAN 812, logoff/logon LNXADM, no success... Shutdown on zVM, loaded the partition with zvm540, and everything is running fine. What seens VERY odd to me is that all configuration on zvm610 and zvm540 are EXACTLY the same, and zvm610 doesn't work. And as today is Friday, and I am flying back home in a couple hours, we will stay on zvm610 until I research more on this. Thanks guys! Mauro http://mauro.limeiratem.com - registered Linux User: 294521 Scripture is both history, and a love letter from God. -- Bruce Hayden z/VM and Linux on System z ATS IBM, Endicott, NY -- 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/ Brabant Water N.V. Postbus 1068 5200 BC 's-Hertogenbosch http://www.brabantwater.nl Handelsregister: 16005077 -- 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: zVM updated, VLAN dead
Hi people, Here are the data: On ZVM610 q vmlan VMLAN maintenance level: Latest Service: VM64604 VMLAN MAC address assignment: MACADDR Prefix: 02 MACIDRANGE SYSTEM: 01-FF USER: 00-00 VMLAN default accounting status: SYSTEM Accounting: OFF USER Accounting: OFF VMLAN general activity: PERSISTENT Limit: INFINITE Current: 2 TRANSIENT Limit: INFINITE Current: 0 q cplevel z/VM Version 6 Release 1.0, service level 1002 (64-bit) Generated at 10/21/10 13:31:23 UTC IPL at 10/22/10 00:28:00 UTC On ZVM540 CP Q VMLAN VMLAN maintenance level: Latest Service: VM64471 VMLAN MAC address assignment: MACADDR Prefix: 02 MACIDRANGE SYSTEM: 01-FF USER: 00-00 VMLAN default accounting status: SYSTEM Accounting: OFF USER Accounting: OFF VMLAN general activity: PERSISTENT Limit: INFINITE Current: 2 TRANSIENT Limit: INFINITE Current: 0 CP Q CPLEVEL z/VM Version 5 Release 4.0, service level 0902 (64-bit) Generated at 06/05/09 18:43:17 UTC IPL at 10/22/10 14:57:33 UTC Really, we have VM64604 on VM610 and not on VM540. I am reading about this change, but we won't have time to change today. Bu thanks a lot for the help! Mauro http://mauro.limeiratem.com - registered Linux User: 294521 Scripture is both history, and a love letter from God. On Fri, Oct 22, 2010 at 1:51 PM, Harder, Pieter pieter.har...@brabantwater.nl wrote: Just a guess, maybe you don't have VM64604 on your 540 system? And it is probably integrated in 610. That one could change the native vlan without any sound. I was hit by that one when I applied it. Best regards, Pieter Harder pieter.har...@brabantwater.nl tel +31-73-6837133 / +31-6-47272537 -Oorspronkelijk bericht- Van: Linux on 390 Port [mailto:linux-...@vm.marist.edu] Namens Bruce Hayden Verzonden: vrijdag 22 oktober 2010 17:46 Aan: LINUX-390@VM.MARIST.EDU Onderwerp: Re: zVM updated, VLAN dead It would be helpful to have the output of Q CPLEVEL and Q VMLAN from both levels. Maybe 6.1 has a key fix or fixes that you don't have on 5.4, and that why it works differently. On Fri, Oct 22, 2010 at 11:40 AM, Mauro Souza thoriu...@gmail.com wrote: We granted access to the LNXADM on another vlan (808). Got another IP, from lnxdb (killed to avoid ip conflict), put the ip on LNXADM, no success. Changed PORT TYPE to ACCESS, back to VLAN 812, logoff/logon LNXADM, no success... Shutdown on zVM, loaded the partition with zvm540, and everything is running fine. What seens VERY odd to me is that all configuration on zvm610 and zvm540 are EXACTLY the same, and zvm610 doesn't work. And as today is Friday, and I am flying back home in a couple hours, we will stay on zvm610 until I research more on this. Thanks guys! Mauro http://mauro.limeiratem.com - registered Linux User: 294521 Scripture is both history, and a love letter from God. -- Bruce Hayden z/VM and Linux on System z ATS IBM, Endicott, NY -- 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/ Brabant Water N.V. Postbus 1068 5200 BC 's-Hertogenbosch http://www.brabantwater.nl Handelsregister: 16005077 -- 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: zVM updated, VLAN dead
On Friday, 10/22/2010 at 11:41 EDT, Mauro Souza thoriu...@gmail.com wrote: We granted access to the LNXADM on another vlan (808). Got another IP, from lnxdb (killed to avoid ip conflict), put the ip on LNXADM, no success. Changed PORT TYPE to ACCESS, back to VLAN 812, logoff/logon LNXADM, no success... Shutdown on zVM, loaded the partition with zvm540, and everything is running fine. What seens VERY odd to me is that all configuration on zvm610 and zvm540 are EXACTLY the same, and zvm610 doesn't work. And as today is Friday, and I am flying back home in a couple hours, we will stay on zvm610 until I research more on this. You need to do a QUERY VSWITCH DETAILS and compare line-by-line to look for any differences, ensuring that you do things in the same order. If QUERYs are the same and the same order was followed, then open a PMR. Alan Altmark's Best Practice for VLAN-aware VSWITCHes: 1. Do not specify PORTTYPE on the DEFINE VSWITCH. [I would like to see the option go away on DEFINE/MODIFY.] If you want a guest to be VLAN aware, specify PO 2. Ensure NATIVE matches the switch native VLAN ID 3. DEFINE VSWITCH ... VLAN , where is a switch administrator-defined private VLAN that is used only to detect guests that have not been properly assigned to a VLAN. 4. Specify VLAN option for all SET VSWITCH GRANTs. If you let it default, you will get the the default (bad) VLAN specified in #3. Alan Altmark z/VM and Linux on System z Consultant IBM System Lab Services and Training ibm.com/systems/services/labservices office: 607.429.3323 alan_altm...@us.ibm.com IBM Endicott -- 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: zVM updated, VLAN dead
Did I notice that the linux definition had layer2=1 and that the Q VSWITCH did not say ETHERNET? Sam Bass -- 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/
Stupid C compiler question
I want to start learning C programming. When I go into yast and search for a compiler I see these lines. What is the differnce between these 2? │gcc43│The GNU C Compiler and Support Files │gcc │The system GNU C Compiler -- Mark D Pace Senior Systems Engineer Mainline Information Systems -- 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: Stupid C compiler question
-Original Message- From: Linux on 390 Port [mailto:linux-...@vm.marist.edu] On Behalf Of Mark Pace Sent: Friday, October 22, 2010 1:55 PM To: LINUX-390@VM.MARIST.EDU Subject: Stupid C compiler question I want to start learning C programming. When I go into yast and search for a compiler I see these lines. What is the differnce between these 2? │gcc43│The GNU C Compiler and Support Files │gcc │The system GNU C Compiler -- Mark D Pace Senior Systems Engineer Mainline Information Systems gcc43 is GCC version 4.3 gcc is the current version of GCC (4.4.4 on my Fedora Linux/Intel). -- John McKown Systems Engineer IV IT Administrative Services Group HealthMarketsR 9151 Boulevard 26 N. Richland Hills TX 76010 (817) 255-3225 phone (817)-691-6183 cell john.mck...@healthmarkets.com www.HealthMarkets.com Confidentiality Notice: This e-mail message may contain confidential or proprietary information. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. HealthMarketsR is the brand name for products underwritten and issued by the insurance subsidiaries of HealthMarkets, Inc. -The Chesapeake Life Insurance CompanyR, Mid-West National Life Insurance Company of TennesseeSM and The MEGA Life and Health Insurance Company.SM -- 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: Stupid C compiler question
Both show as version 4.3 on my system. SLES SP-1 If I select gcc then yast also auto-magically selects gcc43. If I select gcc43 it does not also select gcc. 2010/10/22 McKown, John john.mck...@healthmarkets.com -Original Message- From: Linux on 390 Port [mailto:linux-...@vm.marist.edu] On Behalf Of Mark Pace Sent: Friday, October 22, 2010 1:55 PM To: LINUX-390@VM.MARIST.EDU Subject: Stupid C compiler question I want to start learning C programming. When I go into yast and search for a compiler I see these lines. What is the differnce between these 2? │gcc43│The GNU C Compiler and Support Files │gcc │The system GNU C Compiler -- Mark D Pace Senior Systems Engineer Mainline Information Systems gcc43 is GCC version 4.3 gcc is the current version of GCC (4.4.4 on my Fedora Linux/Intel). -- John McKown Systems Engineer IV IT Administrative Services Group HealthMarketsR 9151 Boulevard 26 N. Richland Hills TX 76010 (817) 255-3225 phone (817)-691-6183 cell john.mck...@healthmarkets.com www.HealthMarkets.com Confidentiality Notice: This e-mail message may contain confidential or proprietary information. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. HealthMarketsR is the brand name for products underwritten and issued by the insurance subsidiaries of HealthMarkets, Inc. -The Chesapeake Life Insurance CompanyR, Mid-West National Life Insurance Company of TennesseeSM and The MEGA Life and Health Insurance Company.SM -- 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/ -- Mark D Pace Senior Systems Engineer Mainline Information Systems -- 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: Stupid C compiler question
On 10/22/2010 at 02:54 PM, Mark Pace pacemainl...@gmail.com wrote: I want to start learning C programming. When I go into yast and search for a compiler I see these lines. What is the differnce between these 2? *gcc43*The GNU C Compiler and Support Files *gcc *The system GNU C Compiler If you look inside the RPMs, you'll see that the gcc package contains _only_ symbolic links: lrwxrwxrwx1 rootroot7 Feb 21 2009 /usr/bin/cc - gcc-4.3 lrwxrwxrwx1 rootroot7 Feb 21 2009 /usr/bin/gcc - gcc-4.3 lrwxrwxrwx1 rootroot8 Feb 21 2009 /usr/bin/gcov - gcov-4.3 lrwxrwxrwx1 rootroot 12 Feb 21 2009 /usr/share/man/man1/cc.1.gz - gcc-4.3.1.gz lrwxrwxrwx1 rootroot 12 Feb 21 2009 /usr/share/man/man1/gcc.1.gz - gcc-4.3.1.gz lrwxrwxrwx1 rootroot 13 Feb 21 2009 /usr/share/man/man1/gcov.1.gz - gcov-4.3.1.gz The gcc43 package contains all the real binaries, libraries, and man pages to which these symlinks point. I'm guessing (since I didn't participate in the packaging) that this would allow you to have multiple versions of GCC installed, but the default one you get if you just invoke gcc or cc will be determined by the gcc package. 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: Stupid C compiler question
Thank you both for the explanations. Have a great weekend. On Fri, Oct 22, 2010 at 3:31 PM, Mark Post mp...@novell.com wrote: On 10/22/2010 at 02:54 PM, Mark Pace pacemainl...@gmail.com wrote: I want to start learning C programming. When I go into yast and search for a compiler I see these lines. What is the differnce between these 2? *gcc43*The GNU C Compiler and Support Files *gcc *The system GNU C Compiler If you look inside the RPMs, you'll see that the gcc package contains _only_ symbolic links: lrwxrwxrwx1 rootroot7 Feb 21 2009 /usr/bin/cc - gcc-4.3 lrwxrwxrwx1 rootroot7 Feb 21 2009 /usr/bin/gcc - gcc-4.3 lrwxrwxrwx1 rootroot8 Feb 21 2009 /usr/bin/gcov - gcov-4.3 lrwxrwxrwx1 rootroot 12 Feb 21 2009 /usr/share/man/man1/cc.1.gz - gcc-4.3.1.gz lrwxrwxrwx1 rootroot 12 Feb 21 2009 /usr/share/man/man1/gcc.1.gz - gcc-4.3.1.gz lrwxrwxrwx1 rootroot 13 Feb 21 2009 /usr/share/man/man1/gcov.1.gz - gcov-4.3.1.gz The gcc43 package contains all the real binaries, libraries, and man pages to which these symlinks point. I'm guessing (since I didn't participate in the packaging) that this would allow you to have multiple versions of GCC installed, but the default one you get if you just invoke gcc or cc will be determined by the gcc package. 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/ -- Mark D Pace Senior Systems Engineer Mainline Information Systems -- 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/
