View previous topic :: :: View next topic
|
Author |
Message |
Sam_nura
New User
Joined: 04 Dec 2008 Posts: 46 Location: Bangalore
|
|
|
|
Hi,
I am doing the installation of z/os. As of my knowledge we can install the z/os by using anyone of the following methods,
--> ServerPac
--> Custom-Built Product Delivery Option (CBPDO)
--> SystemPac
Also we can install the Z/OS without using an installation package like sharing system libraries or cloning an already-installed z/OS.
http://publib.boulder.ibm.com/infocenter/zos/v1r9/index.jsp?topic=/com.ibm.zos.r9.e0zb100/izwouad.htm
Can any one suggest me which method will be a prober one? What is the difference in installing Z/OS without installation package? Thanks in advance. |
|
Back to top |
|
 |
|
|
Robert Sample
Global Moderator
Joined: 06 Jun 2008 Posts: 8280 Location: Dubuque, Iowa, USA
|
|
|
|
Google is your friend. I searched for cbpdo versus serverpac and found the first hit has:
Quote: |
CBPDO (Custom-Built Product Delivery Option) is an entitled software delivery package consisting of uninstalled products and unintegrated service. There is no dialog program to help you install, as there is with ServerPac. Following the instructions in the publication z/OS Program Directory, you must use SMP/E to install the individual z/OS elements and features, and their service, before you can IPL. This is extremely installation specific and requires building of many job streams.
ServerPac is an entitled software delivery package consisting of products and service for which IBM has performed the SMP/E installation steps and some of the post-SMP/E installation steps. To install the package on your system and complete the installation of the software it includes, you use the CustomPac Installation Dialog. The CustomPac Installation Dialog generates tailored installation jobs and saves detailed definitions of volume, catalog, and data set configurations, which can be tailored, saved, and merged to install subsequent ServerPacs. |
The cloning method is typically used to copy a sandbox LPAR to a production environment; it's not generally used to install a new copy of z/OS. Only use CBPDO if you're very familiar with the installation process and like writing JCL. If IBM is willing to help you out with ServerPac, why not let them? |
|
Back to top |
|
 |
Sam_nura
New User
Joined: 04 Dec 2008 Posts: 46 Location: Bangalore
|
|
|
|
Hi Robert,
we already having one Lpar (driving system) which is having all features of Z/OS. Now preparing the new Production environment. so the cloning method is a correct way to make the new environment? |
|
Back to top |
|
 |
Robert Sample
Global Moderator
Joined: 06 Jun 2008 Posts: 8280 Location: Dubuque, Iowa, USA
|
|
|
|
Is there an LPAR already established so you're just copying the operating system to the other LPAR? If so, then cloning is the easiest way of copying -- but remember cloning includes the Unix System Services root along with the sysres packs, jes packs, and what other packs your system resides on.
If you don't already have the second LPAR set up, then cloning is the LAST thing you want to do. You have to work out the details of the hardware accessing both LPARs before proceeding. |
|
Back to top |
|
 |
Sam_nura
New User
Joined: 04 Dec 2008 Posts: 46 Location: Bangalore
|
|
|
|
OK.. but the cloning would not be affect the future up gradation right... |
|
Back to top |
|
 |
Bill Dennis
Active Member
Joined: 17 Aug 2007 Posts: 562 Location: Iowa, USA
|
|
|
|
Future upgrades would be applied to the driving system and then you clone again. |
|
Back to top |
|
 |
Sam_nura
New User
Joined: 04 Dec 2008 Posts: 46 Location: Bangalore
|
|
|
|
Thanks Dennis... But we cant directly apply the PTFs and those stuff in the cloned system right. For example if i go for migration from 1.7 to 1.9 we needs to apply some toleration PTFs |
|
Back to top |
|
 |
Robert Sample
Global Moderator
Joined: 06 Jun 2008 Posts: 8280 Location: Dubuque, Iowa, USA
|
|
|
|
You need two LPARs defined -- your sandbox (testing) system and your production system. You apply the toleration PTFs to the testing system, then do the upgrade, then clone to your production LPAR when your application testers agree the new operating system is ready for their production work. You are then ready to apply the toleration PTFs to your testing system for the next operating system upgrade. You can keep the testing system up for experimentation or deactivate it until you need it again -- probably depending on how the LPAR weights are assigned and how badly production needs the cycles. |
|
Back to top |
|
 |
Sam_nura
New User
Joined: 04 Dec 2008 Posts: 46 Location: Bangalore
|
|
|
|
Thanks Robert...
I think this will be best method to use the new products instance of directly installing into the production system without any testing. |
|
Back to top |
|
 |
Robert Sample
Global Moderator
Joined: 06 Jun 2008 Posts: 8280 Location: Dubuque, Iowa, USA
|
|
|
|
I strongly concur. It is rare, but IBM has introduced serious problems while creating fixes -- so applying changes directly to production is a risky business; 99% of the time it'll work fine but that 1% you'll have to IPL to recover, and you'd better have a good pre-fix backup in that case! |
|
Back to top |
|
 |
|