(r4) DeploymentzOSConfigurationUtility < Deployment

Engineering Lifecycle Management Wiki - Deployment

Community information and contribution guidelines

~~EditAttach~~Printable

TWiki > Deployment Web > DeploymentConfiguringAndTuning > DeploymentzOSConfigurationUtility

Revision 4 - 2014-06-10 - 03:30:45 - Main.dohertl

<div id="header-title" style="padding: 10px 15px; border-width:1px; border-style:solid; border-color:#FFD28C; background-image: url(<nop>https://jazz.net/wiki/pub/Deployment/WebPreferences/TLASE.jpg); background-size: cover; font-size:120%">
---+!! <img src="https://jazz.net/wiki/pub/Deployment/WebPreferences/todo.png" alt="todo.png" width="50" height="50" align="right"> UNDER CONSTRUCTION: CLM z/OS configuration utility
%DKGRAY% Authors: Main.LiamDoherty <br>
Build basis: Rational Team Concert - Enterprise Extensions v5.0.1
%ENDCOLOR%</div></sticky>

<!-- Page contents top of page on right hand side in box -->
<sticky><div style="float:right; border-width:1px; border-style:solid; border-color:#DFDFDF; background-color:#F6F6F6; margin:0 0 15px 15px; padding: 0 15px 0 15px;">
%TOC{title="Page contents"}%
</div></sticky>

<sticky><div style="margin:15px;"></sticky>

The Collaborative Lifecycle management (CLM) Configuration Utility is an ISPF based utility to aid in the configuration of all the components of CLM on the z/OS platform. As there are many optional configuration components to CLM, such as where the server is installed, what application server to use, what data base, etc, it can be a unclear what to install. The configuration utility allows the user to select the components they wish to install and from there it creates a work flow based list of items to action, that perform the configuration. The work flow is presented in a logical order of items to be actioned. Users can add additional configuration items or even create completely new configurations. 

---++ Installation

The installation of the CLM Configuration utility is performed by the SMP/E installation of FMID HRCC501 which is the Common Components FMID. For information see the [[https://pic.dhe.ibm.com/infocenter/clmhelp/v5r0/topic/com.ibm.jazz.install.doc/topics/r_rtcz_smpe_installation.html/][SMP/E installation process]] topic.

---++ Starting and running the CLM Configuration Utility on z/OS®
The Colaborative Lifecycle Management™ Configuration Utility libraries are created as part of the SMP/E installation. When you run the REXX procedure for starting the Configuration Utility, the libraries are dynamically added to your TSO/ISPF session. The libraries are assigned only when needed using LIBDEF and ALTLIB services. This method ensures that existing TSO/ISPF logon procedures do not need to be changed.

The components of the ISPF client dialog are delivered in these libraries:

   $ _hlq_.SBLZEXEC: REXX EXECs
   $ _hlq_.SBLZLOAD: Load modules
   $ _hlq_.SBLZMxxx: ISPF messages
   $ _hlq_.SBLZPxxx: ISPF panels
   $ _hlq_.SBLZSLIB: ISPF skkeletons
   $ _hlq_.SBLZSAMP: Work flow XML

where xxx identifies the national language. For example, SBLZPENU is the ISPF panel library for U.S. English.

---+++ Starting the Configuration Utility

Start the Configuration Utility dialog using the BLZCINIT REXX executable code. You can run the executable code from the TSO command processor panel:

    On the TSO command processor panel, enter EX '<hlq>.SBLZEXEC(BLZCINIT)''<hlq> <userhlq> <language>'

The ISPF client command =BLZCINIT= accepts three parameters:

   $ *HLQ*: (Optional.)The data set name high level qualifiers for the Configuration Utility data sets. If this is not specified the HLQ used to start =BLZCINIT= will be used as the default.
   $ *USERHLQ*: (Optional.)The data set name high level qualifiers for the Configuration Utility data sets created by the Configuration Utility process. If this is not specified the default is BLZ.#CUST. 
   $ *Language*: (Optional.) Identifies the national language. Currently, the Configuration Utility only supports the following languages:

   $     ENU: U.S. English, which is the default if Language is omitted
   $     ENP: U.S. English Uppercase
   $     JPN: Japanese

It should be noted that if the 2nd or 3rd invocation parameters need to be specified then the 1st parameter must also be specified. 

For example invoke this exec with the following command        
                                                   
=ex 'BLZ.V501.SBLZEXEC(BLZCINIT)' 'BLZ.V501 BLZ.CONFIG ENU'=
                                                   
The resulting data set used are:   
                
BLZ.V501.SBLZPENU (etc System data sets)                
BLZ.CONFIG.CLMnnn.* (configuration data sets)       

---++ Navigating through the Configuration utility

When the Configuration Utility is started, either for the first time or on subsequent invocation the following information is presented to the user:

<verbatim>
Rational CLM V5.0.1 utility initialization     
HLQ for install datasets = BLZ.V501            
HLQ for user datasets = BLZ.CONFIG
</verbatim>             

This information tells the user the version of the Configuration Utility, the product libraray high level qualifier used, and the high level qualifier of the configuration data sets. 

---+++ New configuration

On the initial invocation, or when a new configuration is requested, the Initial options menu is presented. This screen allows the user to enter the location of :

   * The HLQ of the installed product data sets. On initial invocation this defaults to the HLQ used to start the Configuration Utility
   * The location of the BLZPASTK module. It is possible this has been moved to a secure library that is APF authorized already.
   * The product installation directory in the Hierarchical File System, by default this is */usr/lpp/jazz/v5.0*.
   * The location of Java. The Configuration Utility will use the Java version found in the users path, if one exists.
   * The directory to be used for CLM configuration files, by default */etc/jazz50*.
   * The directory to be used  for work files, log files and temporary files, by default this is */u/jazz50*.
   * The location of the iconv executable, by default */bin/iconv*.

   * CLM Configuration utility - Options Menu: <br />
     <img src="%ATTACHURLPATH%/Options_Menu.jpg" alt="Options_Menu.jpg" width="544" height="431" />

The user should change any of the option that need to be changed. You will not be able to leave this screen until a valid location has been specified for the product HLQ, product location and Java  location. An error screen listing all of the errors will be displayed:

   * CLM Configuration utility - Options Errors: <br />
     <img src="%ATTACHURLPATH%/Options_Errors.jpg" alt="Options_Errors.jpg" width="529" height="287" />

Once all the valid information is entered the Java version will be displayed. The user can now press *PF3* to proceed to the configuration panels. 

   * CLM Configuration utility - Options Menu Java Version: <br />
     <img src="%ATTACHURLPATH%/Options_Menu_Java_Version.jpg" alt="Options_Menu_Java_Version.jpg" width="554" height="37" />

---+++ Entering customization information via the customization panels

Once the user has entered the valid information on the Options menu they will be presented with the main customization menu. This is the menu that drives the selection and customization of the required and optional components to be installed for CLM. The list presented in the Main Customization Menu shows all of the available options:

   * CLM Configuration utility - Customization Main Menu: <br />
     <img src="%ATTACHURLPATH%/Customization_Main_Menu.jpg" alt="Customization_Main_Menu.jpg" width="538" height="414" />

The user can chose which parts of the product they want to install. For example if they are running the server off z/OS then they do not need to install any of the *Optional z/OS server customization* or any of the *Optional RTC application customization*. If they are only using the Build Agent to build z/OS applications, but do not intend to use the ISPF Client theen they will only need to revieew and configure the following options:

<verbatim>
1  General settings (*)
2  ISPF Gateway (*)    
3  Rational Build Agent 
</verbatim>

The ==(***)== next to an option indicates if that option has been selected to be configured. The *General Settings* and *ISPF Gateway* are required customizations so are marked with a ==(***)==. For any of the optional customizations the user need to select the option, and then in the subsequent screen mark that they wish this optional component to be customized. Taking the above scenario of just installing the Rational Build Agent the user would enter option *3* and press *Enter* and then be presented with the Rational Build Agent Customization panel. They need to enter a *Y* at the specified place to indicate that this component will be included in the customization. In addition all of the default settings should be reviewd and changed if required. 

   * CLM Configuration utility - Rational Build Agent Customization: <br />
     <img src="%ATTACHURLPATH%/Rational_Build_Agent_Customization.jpg" alt="Rational_Build_Agent_Customization.jpg" width="557" height="351" />

The user should select all the components they wish to include in the configuration amd verify the settings in each on. For more information on each of the different settings consult the Help panels by pressing *PF1*. In addition more information can be found in the installing section in the CLM online guide. It should be noted that additional configurations can be made later, after a configuration work flow has been generated, by selecting and changing teh configuration. This scenario will be discussed in more detail later. 

---+++ Generating the configuration work flow

Once all of the required components have been selected and the settings checked the work flow for this particular configuration can be generated. On the main configuration panel select the *G* option to generate the configuration jobs. 

   * CLM Configuration utility - Generate Configuration: <br />
     <img src="%ATTACHURLPATH%/Generate_Configuration.jpg" alt="Generate_Configuration.jpg" width="517" height="40" />



---+++++!! Related topics: [[DeploymentWebHome][Deployment web home]], [[DeploymentWebHome][Deployment web home]]

---+++++!! External links:          

   * [[https://www.ibm.com][IBM]]

<sticky></div></sticky>


   * CLM Configuration utility - Generate Configuration: <br />
     <img src="%ATTACHURLPATH%/Generate_Configuration.jpg" alt="Generate_Configuration.jpg" width="517" height="40" />

Attachments

Topic attachments
I	Attachment	Action	Size	Date	Who	Comment
jpg	Customization_Main_Menu.jpg	manage	43.5 K	2014-06-10 - 02:33	UnknownUser	CLM Configuration utility - Customization Main Menu
jpg	Generate_Configuration.jpg	manage	5.5 K	2014-06-10 - 03:29	UnknownUser	CLM Configuration utility - Generate Configuration
jpg	Options_Errors.jpg	manage	29.2 K	2014-06-10 - 02:15	UnknownUser	CLM Configuration Utility - Options Errors
jpg	Options_Menu.jpg	manage	55.4 K	2014-06-10 - 02:10	UnknownUser	CLM Configuration utility - Options Menu
jpg	Options_Menu_Java_Version.jpg	manage	6.6 K	2014-06-10 - 02:29	UnknownUser	CLM Configuration utility - Options Menu Java Version
jpg	Rational_Build_Agent_Customization.jpg	manage	55.6 K	2014-06-10 - 03:07	UnknownUser	CLM Configuration utility - Rational Build Agent Customization

Copyright © by IBM and non-IBM contributing authors. All material on this collaboration platform is the property of the contributing authors.
Contributions are governed by our Terms of Use. Please read the following disclaimer.
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.