I thought the OSA needed to be configured and OSASF looked like the best way to do it. I didn't know it would work without any configuration. I guess another reason was for disaster recovery. We had difficulties at our last DR test because we had to use an OSA and we had no experience with it. I figured if I had the configuration in VM I could just load it to the OSA at the DR site. Would that work? How do others do it? As far as QDIO vs Non-QDIO, I'm just running with had I have. It was Non-QDIO so I figured I'd keep it that way & avoid an IOCP gen. We are z/VM 5.4 & z/VSE 4.1 so I hope we're current enough to use QDIO but I'll check. So how does the OSA know what's expected of it? Just by the IOCP definitions? Right now when I "Q 1460-146F" I get 1460, 1461, & 146F FREE. 1462-146E are offline??? I can't find where they're Varied Off so how do they get that way? Any ideas?
Again, thanks for any and all help and sorry for all the questions but this isn't very clear (at least to me it's not). Bob -----Original Message----- From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Mike At HammockTree Sent: Thursday, July 02, 2009 10:47 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: First OSA config. The first question, Bob, is "Why are you using OSASF at all??" OSASF is not needed/used by the ICC port of the OSA. If you change your definition of the other port (PCHPID 110) to OSD and run in QDIO mode you won't need OSASF. You can have zVM and multiple guests all use/share that port witth no OSASF. zVM could have ports 1460-1461, guest 1 could have 1462-1463, guest 3 could have 1464-1465, etc.... Of course you will have to change your zvm and guest TCP/IP definitions to use QDIO mode, but that is generally very simple and this avoids the complications of OSASF. Of course, the zVM folks here will also probably point out that you could just define a VSWITCH and connecct the port to that and then connect the zVM IP stack and all the guersts to that VSWITCH. This all does assume that your guests will support QDIO mode. Old systems may present a problem. Mike ----- Original Message ----- From: "Frankovich, Bob" <bfrankov...@scspa.com> To: <IBMVM@LISTSERV.UARK.EDU> Sent: Thursday, July 02, 2009 9:35 AM Subject: First OSA config. I'm trying to figure out how to configure the OSA card on our z9 box. I'v= e never worked with OSA's before so I have more questions than answers. AN= Y help will be appreciated. The initial OSA config was done by a business = partner. These are the IOCP def's : CHPID PATH=(10),TYPE=OSE,PCHID=110,PART=PROD CHPID PATH=(11),TYPE=OSC,PCHID=111,PART=PROD ************************************************ CNTLUNIT PATH=(10),UNIT=OSA,CUNUMBR=1460 IODEVICE ADDRESS=(1460,15),UNIT=OSA,UNITADD=00,CUNUMBR=1460 IODEVICE ADDRESS=(146F,1),UNIT=OSAD,UNITADD=FE,CUNUMBR=1460 * CNTLUNIT CUNUMBR=E020,PATH=(11),UNIT=OSC IODEVICE ADDRESS=(E020,08),CUNUMBR=(E020),UNIT=3270 We are using E020 & E021 for our VM & Prod VSE consoles. I've been trying to set up the CMS Users OSASF, OSAMAINT, & OSADMIN1 = 2 & 3 using the OSA Implemntation redbook & the OSA Customer guide. I have= not done anything with user 4OSASF40, should I? I've gone thru chapter 4 (Setting up OSA/SF on z/VM) and I'm pretty sure I have everything defined= as it says to. We're running z/VM 5.4 When I logon to OSADMIN1 and enter IOACMD, I get the menu back but when I= select option 4 to get the config, I get : CMALLC_PRODUCT_SPECIFIC_ERROR: CMSIUCV CONNECT completed with return cod= e 1011 The only explanation I've found to this message says I don't have TASF = installed ??? Obviously I'm not doing something right! All ideas will be appreciated = Email secured by SCSPA-CheckPoint Firewall The contents of this e-mail are confidential to the ordinary user of the e-mail address to which it was addressed and may also be privileged. If you are not the addressee of this e-mail you should not copy, forward, disclose or otherwise use it or any part of it in any form whatsoever. If you have received this e-mail in error, please notify us by telephone or e-mail the sender by replying to this message, and then delete this e-mail and other copies of it from your computer system. We reserve the right to monitor all e-mail communications through our network. The contents of this e-mail are confidential to the ordinary user of the e-mail address to which it was addressed and may also be privileged. If you are not the addressee of this e-mail you should not copy, forward, disclose or otherwise use it or any part of it in any form whatsoever. If you have received this e-mail in error, please notify us by telephone or e-mail the sender by replying to this message, and then delete this e-mail and other copies of it from your computer system. We reserve the right to monitor all e-mail communications through our network.
