Alyce, > E007 ATTACHED TO CLIENT 0340
> Why doesn't it like my E000 and/or e007 response? Because you attached your REAL device E007-E009 as VIRTUAL device addresses 0340-0342. Using consistent virtual addresses on each server is a *GOOD THING*. This permits you to have fewer changes between SLES guests. You just attach different REAL devices to the guests as the same VIRTUAL addresses. Linux only sees the same virtual device addresses, so the Linux configuration is the same for pretty much everything except the IP address and Hostname. That way you take that same Golden Image, copy it to the next virtual guest server, only have to change the IP address and Hostname, and add whatever middleware it needs. The virtual OSA addresses are the same. But you'd be far better off spending a little time researching VIRTUAL SWITCHes and using them instead of real OSA addresses. Mike Walter Hewitt Associates Any opinions expressed herein are mine alone and do not necessarily represent the opinions or policies of Hewitt Associates. "Austin, Alyce (CIV)" <[EMAIL PROTECTED]> Sent by: "The IBM z/VM Operating System" <[email protected]> 09/26/2008 04:38 PM Please respond to "The IBM z/VM Operating System" <[email protected]> To [email protected] cc Subject Re: SLES10 Client Hello, >From my Client userid, I type SLES to bring up the full-service server for SLES10: This is what I get: Why is it looking for the CDs when I have a starter system implemented? sles NO FILES PURGED RDR FILE 0027 SENT FROM CLIENT PUN WAS 0027 RECS 090K CPY 001 A NOHOLD NOKEEP RDR FILE 0028 SENT FROM CLIENT PUN WAS 0028 RECS 0001 CPY 001 A NOHOLD NOKEEP RDR FILE 0029 SENT FROM CLIENT PUN WAS 0029 RECS 107K CPY 001 A NOHOLD NOKEE Searching for info file... *** Could not find the SUSE Linux Enterprise Server 10 Installation CD. Activating manual setup program. >>> Linuxrc v2.0.79 (Kernel 2.6.16.60-0.21-default) <<< Please select the type of your network device. 1) OSA-2 or OSA Express 2) Hipersockets -------------------- 3) Channel To Channel (CTC) 4) ESCON 5) Inter-User Communication Vehicle (IUCV) > 1 Please choose the CCW bus interface. 1) QDIO 2) LCS > 1 1) QDIO 2) LCS Please choose the physical medium. 1) Ethernet 2) Token Ring > 1 0.0.0340 1731/01 0.0.0341 1731/01 0.0.0342 1731/01 evice address for read channel [e003]> e007 *** This is not a valid CCW address. Please select the type of your network device. 1) OSA-2 or OSA Express 2) Hipersockets -------------------- Why doesn't it like my E000 and/or e007 response? When I do a q osa, this is what I see on my system: q osa OSA E003 ATTACHED TO TCPIP E003 DEVTYPE OSA CHPID 00 OSD OSA E004 ATTACHED TO TCPIP E004 DEVTYPE OSA CHPID 00 OSD OSA E005 ATTACHED TO TCPIP E005 DEVTYPE OSA CHPID 00 OSD OSA E007 ATTACHED TO CLIENT 0340 DEVTYPE OSA CHPID 00 OSD OSA E008 ATTACHED TO CLIENT 0341 DEVTYPE OSA CHPID 00 OSD OSA E009 ATTACHED TO CLIENT 0342 DEVTYPE OSA CHPID 00 OSD Any help will be appreciated, Thanks, Alyce -----Original Message----- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of David Boyes Sent: Thursday, September 25, 2008 11:39 AM To: [email protected] Subject: Re: SLES10 Client > > Do I need a secondary user defined It's not required, but it is a good idea to have somewhere central for all the console logs on your system to go by default, rather than have them scattered all over the spool. If you want to silence the message, change the CONLOG on the CONSOLE statement in the directory entry to any valid userid on your system, or remove it if you want the console logs to end up in CLIENT's rdr. > > do I need both > > CPU statements? No. Most guests seem to feel healthier and more responsive if you have more than one logical CPU, but it's not required or desirable in some cases. Do note that there are some applications that don't build properly in a UP system, so we put the extra statement in to try to catch that. As Rich said, it's an example. Tailor it as you see fit. 19F and the disks you plan to use to put the Linux system on are the important bits. The rest is "as you like it". The information contained in this e-mail and any accompanying documents may contain information that is confidential or otherwise protected from disclosure. If you are not the intended recipient of this message, or if this message has been addressed to you in error, please immediately alert the sender by reply e-mail and then delete this message, including any attachments. Any dissemination, distribution or other use of the contents of this message by anyone other than the intended recipient is strictly prohibited. All messages sent to and from this e-mail address may be monitored as permitted by applicable law and regulations to ensure compliance with our internal policies and to protect our business. E-mails are not secure and cannot be guaranteed to be error free as they can be intercepted, amended, lost or destroyed, or contain viruses. You are deemed to have accepted these risks if you communicate with us by e-mail.
