Scott, Three years ago when we were rolling out our sysplex across three lpars I believe we ran into a problem if all of our CONSOLxx members were not in sync. So since I'm only changing the one CONSOLxx member on the sandbox I do not want to create a problem on the other lpars when we IPL them on Sunday. So why not add them to the other lpars, right? Because that we cause change control paperwork to complete this task. So I'm really trying to find a proven short cut.
Rogers -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Scott Rowe Sent: Thursday, March 05, 2009 1:41 PM To: [email protected] Subject: Re: Adding new console for OSA-ICC I don't understand what either sysplex, CONSOLxx, or CNGRP have to do with NIP consoles. BTW, if you have a console in CONSOLxx when you IPL, sysplex willknow about the console, but I don't understand whay you are concerned with that. >>> "Laine, Rogers" <[email protected]> 3/5/2009 2:10 PM >>> Kevin, thanks for your reply. Were you testing under a sysplex? Rogers -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Neubert, Kevin Sent: Thursday, March 05, 2009 1:02 PM To: [email protected] Subject: Re: Adding new console for OSA-ICC If your NIP console list contains your old and new device addresses and you have not deleted the old equipment, etc. you are good to go for your testing. I did not experience any issues running mixed 2074/OSA-ICC consoles for conversion to OSA-ICC in the manner you describe. I don't feel backing out your sandbox changes is necessary. Good luck. Regards, Kevin -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Laine, Rogers Sent: Thursday, March 05, 2009 7:05 AM To: [email protected] Subject: Adding new console for OSA-ICC When we added the OSA-ICC to our IODF we also defined new NIP consoles for all three LPARS. I would like to test one of these console on our sandbox lpar using ICC. This is what I think needs to be done. 1. Define the new console for sandbox lpar to CONSOLxx parm and NOT to the CNGRPxx parm. I'm thinking that if it is not in the CNGRP member it will not be broadcast across the sysplex. 2. IPL the sandbox lpar to introduce the new NIP console. This IPL will be done using one of the existing NIP consoles. 3. Add the new console to the sessions configuration on the ICC. 4. See if I can connect to the new console using Extra. If this works continue with next step. 5. IPL again but use this new NIP console instead of the existing one used above in step 2. Since this is being done on my sandbox lpar I do not want it to impact my other two production lpars. We will be IPLing the other two lpars on Sunday morning and do not want to cause any problems because of my testing. So can I leave this new console defined to the sandbox for Sunday's IPL or should I remove it from CONSOLxx and IPL again? TIA, Rogers ************************************************ This E-Mail transmission (and/or the documents accompanying it) may contain information belonging to the sender which is confidential, privileged and/or exempt from disclosure under applicable law. The information is intended only for the use of the individual(s) or entity named above. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution or the taking of any action in reliance on the contents of this information is strictly prohibited. If you have received this E-Mail transmission in error, please immediately notify us by return E-Mail or telephone to arrange for return of its contents including any documents. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html CONFIDENTIALITY/EMAIL NOTICE: The material in this transmission contains confidential and privileged information intended only for the addressee. If you are not the intended recipient, please be advised that you have received this material in error and that any forwarding, copying, printing, distribution, use or disclosure of the material is strictly prohibited. If you have received this material in error, please (i) do not read it, (ii) reply to the sender that you received the message in error, and (iii) erase or destroy the material. Emails are not secure and can be intercepted, amended, lost or destroyed, or contain viruses. You are deemed to have accepted these risks if you communicate with us by email. Thank you. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html ************************************************ This E-Mail transmission (and/or the documents accompanying it) may contain information belonging to the sender which is confidential, privileged and/or exempt from disclosure under applicable law. The information is intended only for the use of the individual(s) or entity named above. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution or the taking of any action in reliance on the contents of this information is strictly prohibited. If you have received this E-Mail transmission in error, please immediately notify us by return E-Mail or telephone to arrange for return of its contents including any documents. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
