Re: Rexx Alternate library
Here's my VMARC. Be sure to look at my fixed version of EAGACTAL EXEC. The original version had 2 problems and bad RAS: - it ran with the default ADDRESS CMS, what is not good for RAS reasons, I changed it to ADDRESS COMMAND. I had to uppercase one letter in an option of one COPYFILE command. - it could display a nasty errormsg: DMSNXD616W EAGRTPRC does not exist. This alarms the end-user, but would not indicate a problem. This is fixed by running with ADDRESS COMMAND. - the verification procedure failed always: it tried to COPYFILE the compiled verification execs from the wrong place. 2007/8/13, Tracy Dean [EMAIL PROTECTED]: On Fri, 10 Aug 2007 16:04:34 +0300, Kris Buelens [EMAIL PROTECTED] wrote: ... Question: is someone from the VM lab listening and able to get a repaire d version of the alternate library on http://www-306.ibm.com/software/awdtools/rexx/rexxzseries/altlibrary.htm l ... We're looking into it (including providing the package in VMARC format.) Thanks, Tracy Dean, IBM -- Kris Buelens, IBM Belgium, VM customer support
Re: Access to 191 MDISK when running IFCONFIG
There is an MDISKPW option on IFCONFIG. Or, you could add OPTION LNKNOPASS to TCPIP's direntory entry (or install an ESM like RACF to make passwords obsolete). 2007/8/13, Fred Schmidt [EMAIL PROTECTED]: ifconfig -tcp tcpip2 osab2 down DTCIFC2654E TCPIP2 is unable to link to your 191 minidisk which is DTCIFC2654E currently accessed as file mode A Is there a cleaner way of giving this access than changing the user's password in USER DIRECT for MDISK 191 to ALL or updating TCPIP's PROFILE EXEC to VMLINK to the 191 minidisk of all users allowed to run the IFCONFIG commands? Regards, Fred Schmidt Department of Corporate and Information Services (DCIS) Data Centre Services (DCS) Northern Territory Government, Australia -- Kris Buelens, IBM Belgium, VM customer support
Re: TCP/IP problem with hypersockets
David, Thank you for your advice which solved the TCPIP startup problem. It is now possible to telnet a Linux virtual machine (at 192.168.1.2) from another virtual machine. What does not work yet, is the connection from Windows. (We do not use Linux on the workstations.) After the Windows command route add 192.168.1.0 mask 255.255.255.0 192.168.0.4, it is impossible to ping 192.168.1.2. Pinging 192.168.1.1 works (there is a virtual lan 192.168.1 on the harware router). But I suppose that these Windows problems are not in the scope of this list. Thanks again. Best regards, Antoon Vekeman Software Product Research Software Solutions for DB2 http://www.sprdb2.com B-2288 Bouwel Belgium On Fri, 10 Aug 2007 18:13:53 -0400, David Boyes wrote: You are using the VM TCP stack as a layer 3 router. That means that you must have different subnets for the LCS and hipersocket interfaces (either by splitting the 192.168.0 network with the netmask, or by using a different subnet of the 192.168 space for the hipersocket link. The easy way is to set the hipersocket interface to 192.168.1.1, number all your linux guests as 192.168.1.x with a default gw of 192.168.1.1. The last step is to make sure that the other devices on your network that need to reach machines on the hipersocket LAN have a routing entry for 192.168.1.0/255.255.255.0 via 192.168.0.4 as the gateway. For Linux, that would look like: route add net 192.168.1.0 netmask 255.255.255.0 gw 192.168.0.4 Windows should be something similar.
Debian SSL Server Enabler
Does the Sinenomine Debian SSL Server Enabler 2.1 work with Z/VM 5.3 and support FTP client and server secure connections? Jim Hughes 603-271-5586 There's no sense in being precise when you don't even know what you're talking about. John von Neumann
Re: TCP/IP problem with hypersockets
Alan, I separated the networks for LCS and hypersockets. This solved the problem and the QDIO link can now be accessed from another virtual machine (not from outside the network). Removing PORTNAME on the QDIO DEVICE statement resulted in a TCP/IP error message and prevented startup of the link. This may be a TCP/IP release issue: we are still on TCP/IP 4.3. (For PWD members it is no longer easy to remain up-to-date since the VM ADCDs were dropped. Not so for z/OS ...) Thank you for your advice. Best regards, Antoon Vekeman Software Product Research Software Solutions for DB2 http://www.sprdb2.com B-2288 Bouwel Belgium On Sat, 11 Aug 2007 11:36:20 -0700, Alan Altmark wrote: On Friday, 08/10/2007 at 05:48 EDT, Antoon Vekeman [EMAIL PROTECTED] wrote: DTCPRS007E Error encountered in reading PROFILE TCPIP *: DTCPAR123I Line 67: Gateway not directly accessible in GATEWAY command 00057 HOME 00058 192.168.0.3 ETH_VM431 00059 192.168.0.10 QDIO1 00060 ; 00061 GATEWAY 00062 ; Network First Link MTU Subnet S 00063 ; Address Hop Name Size Mask V 00064 ; 00065 192.168.0 = ETH_VM431 1492 0 00066 192.168.0 = QDIO1 1500 255.255.255.0 0 00067 DEFAULTNET 192.168.0.4 ETH_VM431 1492 0 You have two interfaces defined with the same subnet (192.168.0/24) that are connected to different networks. It ain't gonna work. The message is probably because you don't have EQUALCOSTMULTIPATH in the AssortedParms, and the first GATEWAY entry was replaced by the second one, excluding ETH_VM431. You MUST put the Guest LAN and the LCS device in separate networks. Also, remove the PORTNAME specification for the QDIO device. It isn't required and its presence will, someday in the unforseen future, come back to bite you. Alan Altmark z/VM Development IBM Endicott
VMware gives IBM credit for VM
VMware Predicts Death To Operating Systems Mendel Rosenblum envisions a world run by virtualization appliances where software makers wouldn't need a bulky or complex OS. He said in his keynote at LinuxWorld conference: The hypervisor is the system program that provides the virtual machine environment. The term came from the IBM mainframe world. IBM was the first to introduce the concept of a virtual machine. I give IBM credit for inventing this, but they also in some sense killed it (by turning toward operating systems), Rosenblum said. http://update.informationweek.com/cgi-bin4/DM/y/mBBn80HnWTA0G4n0FRPI0FQ /Fran Hensler at Slippery Rock University of Pennsylvania USA for 44 years [EMAIL PROTECTED] +1.724.738.2153 Yes, Virginia, there is a Slippery Rock
Re: TCPIP config changes in z/VM 5.2
Berry, This issue was addressed in APAR PK42210 Regards, Miguel Delapaz z/VM TCP/IP Development Now I noticed the default was presented as a default gateway (flags UGS) in the old VM and the new one is a host (flags UGHS). Other than that I think the netstat gate output is the same in both systems. Any ideas on how to fix this? TIA, Berry.
TCPIP config changes in z/VM 5.2
Hello List, Last Friday we migrated one of our VM systems. This VM is one of four tha t use static routing only. Now I have found that the IP configuration rules have been changed in z/VM 5.2. So I changed the HOME and GATEWAY statements in the configuration file. Unfortunatly I haven't been able to get it fully functional. I can ping my gateway and even the nameserver bu t I can't ping the servers I need to access. The old z/VM 4.4 configuration: HOME 10.81.32.11 CTCLVM42 10.81.32.11 CTCLVM43 10.81.32.11 CTCLVM45 10.81.32.11 OSAETH2 10.81.32.01 OSAETH0 GATEWAY ; (IP) Network FirstLink Max. Packet Subnet Subnet ; Address Hop Name Size (MTU) MaskValue ; --- --- --- --- ; 10.81.32.13 =CTCLVM42 1500 HOST 10.81.32.15 =CTCLVM45 1500 HOST 10.81.32.17 =CTCLVM43 1500 HOST 10=OSAETH2 1500 0.255.255.0 0.81.32. 0 DEFAULTNET10.81.32.253 OSAETH2 1500 0 A NETSTAT GATE will present me with: Default 10.81.32.253 UGS 1500 noneOSAETH2 10.0.0.0direct US 1500 0.255.255.0 0.81.32.0 OSAETH2 10.81.32.13 direct UHS 1500 HOST CTCLVM42 10.81.32.15 direct UHS 1500 HOST CTCLVM45 10.81.32.17 direct UHS 1500 HOST CTCLVM43 Now the new VM (actually a diffent node but the same idea): HOME 10.81.32.17 CTCLVM32 10.81.32.17 CTCLVM34 10.81.32.17 CTCLVM35 10.81.32.17 255.255.255.0 OSAETH2 10.81.32.07 OSAETH0 GATEWAY 10.81.32.11 HOST =CTCLVM34 1500 10.81.32.13 HOST =CTCLVM32 1500 10.81.32.15 HOST =CTCLVM35 1500 DEFAULTNET10.81.32.253 OSAETH2 1500 A NETSTAT GATE will show: Subnet Address Subnet Mask FirstHopFlgs PktSz Metric Link -- --- - -- -- Default HOST 10.81.32.253UGHS 1500 none OSAETH 2 10.81.32.0 255.255.255.0directUT 1500 none OSAETH 2 10.81.32.11 HOST directUHS 1500 none CTCLVM 34 10.81.32.13 HOST directUHS 1500 none CTCLVM 32 10.81.32.15 HOST directUHS 1500 none CTCLVM 35 When I check the connections I try: PING 10.81.32.11 (this will ping through a CTC connection) PING 10.81.32.253 (this is the gateway) PING 10.1.1.25 (this is our nameserver as specified in the TCPIP DATA) PING 10.1.1.73 (this is a NT server but can't be pinged in the new VM). When I try to ping the server by its name (PING HNYM-CDT1) the name get's resolved and the ping will try to reach 10.1.1.73, but no success. Now I noticed the default was presented as a default gateway (flags UGS) in the old VM and the new one is a host (flags UGHS). Other than that I think the netstat gate output is the same in both systems. Any ideas on how to fix this? TIA, Berry.
Re: Live Virtual Class, Aug 14 - Virtualization Basics (10am NY time)
Thanks Rob, I tried again just now. I was able to register. Regards, ..Roland Rob van der Heij [EMAIL PROTECTED] wrote: On 8/12/07, Roland P. Chung wrote: It does not matter any more It is full when I tried to register on Friday afternoon... Ummm Try again. There may have been a glitch since it picked up a new registration just now. Rob -- Rob van der Heij Velocity Software, Inc http://velocitysoftware.com/
Re: TCP/IP problem with hypersockets
After the Windows command route add 192.168.1.0 mask 255.255.255.0 192.168.0.4, it is impossible to ping 192.168.1.2. Pinging 192.168.1.1 works (there is a virtual lan 192.168.1 on the harware router). That's your problem. IP addresses must be unique. If 192.168.1.x is in use elsewhere, then you need to use a different range for your Linux guests and modify the route command appropriately. Try renumbering the Linux guests to 192.168.2.x or some unused number.
Re: Debian SSL Server Enabler
Does the Sinenomine Debian SSL Server Enabler 2.1 work with Z/VM 5.3 and support FTP client and server secure connections? The current version does work on 5.3, but is based on the 5.2 SSL code and thus has the limitations of the 5.2 code. We're looking at doing a 5.3 version of the SSL Enabler, but it's behind some other paying work that has to take precedence. We also are looking at using CentOS, which might address some of the supported version issues. We'd also consider doing a SuSE version if Novell feels generous with permission to distribute appliance virtual machines based on SLES without charge.
Re: TCP/IP problem with hypersockets
On Monday, 08/13/2007 at 09:59 EDT, Software Product Research [EMAIL PROTECTED] wrote: For PWD members it is no longer easy to remain up-to-date since the VM ADCDs were dropped. Not so for z/OS ... Look at the z/VM 5.2 Developer's Startup for Linux within the PWD program. And you should contact PWD to let them know that you need z/VM ADCDs. Alan Altmark z/VM Development IBM Endicott
Re: Access to 191 MDISK when running IFCONFIG
On Monday, 08/13/2007 at 12:06 EDT, Fred Schmidt [EMAIL PROTECTED] wrote: ifconfig -tcp tcpip2 osab2 down DTCIFC2654E TCPIP2 is unable to link to your 191 minidisk which is DTCIFC2654E currently accessed as file mode A Is there a cleaner way of giving this access than changing the user's password in USER DIRECT for MDISK 191 to ALL or updating TCPIP's PROFILE EXEC to VMLINK to the 191 minidisk of all users allowed to run the IFCONFIG commands? If your security policy allows it, you can give TCPIP the LNKNOPAS option in the directory. Elimination of disk passwords is just one of the benefits of installing a security product like RACF. Alan Altmark z/VM Development IBM Endicott
Re: question to guest lan type qdio and zos 1.5
On Monday, 08/13/2007 at 08:08 EDT, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: the rsu level of the zvm 5.3 is 0701. This systems runs on a t-server. But I think that this cannot be an issue because everything is virtually built by zvm so the hardware shouldn't be an issue or could it make sense to test the same scenario on a real z-machine. Is it possible that zos needs an additional option in user direct. Currently there are the same options than on a vse 2.7 which works fine with the virtual qdio. What I know definitely is that this zos has formerly worked with a real osa qdio in an lpar on a 9672. So I would say there shouldn't be missing ptfs on the zos side. The only reference I find to your error is when the VM directory entry for the z/OS guest has the RMCHINFO option. Yours does not. I'd still open a PMR with CommServer. They are the only ones who know exactly what they are looking for. They can, in turn, call VM Development to resolve the issue. Alan Altmark z/VM Development IBM Endicott
[no subject]
Hello, I notice that PERFSVM A DISK fills up rather quickly. Does it automatically role-over when it gets to a certain percentage? If not, what is the best way to clean it up? Which files are OK to delete and still keep it running? Thanks for your help, Alyce
