Best Tips & Kept Secrets of RTC -EE and RDz By Olivier Gauneau and Nicolas Dangeville

Please Note:

2

• IBM’s statements regarding its plans, directions, and intent are subject to change or withdrawal without notice at IBM’s sole discretion.

• Information regarding potential future products is intended to outline our general product direction and it should not be relied on in

making a purchasing decision. • The information mentioned regarding potential future products is not a commitment, promise, or legal obligation to deliver any

material, code or functionality. Information about potential future products may not be incorporated into any contract. • The development, release, and timing of any future features or functionality described for our products remains at our sole discretion. • Performance is based on measurements and projections using standard IBM benchmarks in a controlled environment. The actual

throughput or performance that any user will experience will vary depending upon many factors, including considerations such as the amount of multiprogramming in the user’s job stream, the I/O configuration, the storage configuration, and the workload processed. Therefore, no assurance can be given that an individual user will achieve results similar to those stated here.

Interim fixes for RTC Fix central

Interim Fixes on Fix Central

4

• Interim fixes are available since CLM v4.0.7 and can be downloaded from Fix Central Web site: • http://www-01.ibm.com/support/docview.wss?uid=swg27043083 • http://www-933.ibm.com/support/fixcentral/ Note: The latest ifix of each release is also available on jazz.net on the download page

RTC Installation on z/OS Configuration Utility & IVP

Configuration Utility

6

• Since RTC v5.0.1, the Configuration Utility helps you configure the different CLM components on z/OS through an ISPF-based interface and automatically generated workitems.

Specify the installation location

Select the components of the

product you want to configure

For example with Rational Build Agent: review all of the default settings and change them, if necessary.

Generate the workitems

Run the workflow items

Installation verification process (IVP) for z/OS

7

The Rational® solution for Collaborative Lifecycle Management installation verification process (IVP) verifies information about settings that you configured during installation on z/OS

The installation verification process (IVP) provides information about the settings of the following installation configurations: • General installation • Rational Team Concert ISPF client • Rational Build Agent • ISPF gateway. The IVP checks for things that might cause problems with the listed settings, if they are not set up correctly, such as: • RACF® permissions on data sets • RACF on general resource profiles • UNIX Systems Services (USS) permissions on files and directories • Space restrictions on configuration and work directories • ISPF gateway set up • APF authorizations • Necessary PARMLIB members are correctly updated. .

RTC Migration From v4 to v5, from v5 to v6, or from v4 to v6

Migration from v4 to v6

9

General Migration tips If you have EE content, part of the migration will be done when running the upgrade scripts, and the rest of the migration will be done at the first start of the server. This minimizes the downtime of the server. In v6, a significant migration of the build map is performed, that can take some time. You can select in which order you will process

the build maps: by ordering the project areas being processed or the build definitions. Check the documentation <reference to add> In v5, there is also a build map migration of a different nature. Migrate from v4 to v6 Upgrading from version 4 to any release of version 6 is a two-step process. You must first upgrade your server to the latest fix pack of the version 5 release, then upgrade to version 6. We recommend that you use 5.02 latest ifix as the v5 intermediate version. If you plan to migrate directly from v4 to v6, coming from 4.05 or later and if you target RTC 6.01 ifix1, you can avoid to start the server when you reach 5.02: all the migrations steps will be performed when you start the 6.01 server. After you have reached your target version and the server has finished to perform the migration steps, you can plan to run 2 optional steps. These steps can be performed a couple of days after the actual migration: repotools-ccm -createVersionIDs : you run it when the server is running. This will create version ids for all the history of the source file

in the SCM repotools-ccm -reindex all. This will recreate the Jena indexes and significantly reduce their size, making the next indexing and

requests much faster. http://www-01.ibm.com/support/knowledgecenter/SSYMRC_6.0.1/com.ibm.jazz.install.doc/topics/c_two_step_upgrade.html?lang=en

RTC Performance

RTC on z/OS

11

• zIIP/zAAP: • when running any of the following components on z/OS it is highly recommended to have a zAAP or run zAAP on zIIP: Rational

Team Concert Build System toolkit, Rational Build Agent, Rational Team Concert ISPF daemon, CLM Server (or any of the capabilities). When using DB2 for z/OS as the database it is highly recommended to have a zIIP to allow the offloading of the JDBC processing. See https://jazz.net/wiki/bin/view/Deployment/CLMSystemRequirements50

• Benchmarking on z/OS • Using zIIP/zAAP with RTC 5.0: https://jazz.net/wiki/bin/view/Deployment/RationalTeamConcertForZOSzIIP • Comparison by version till 6.0.1:

https://jazz.net/wiki/bin/view/Deployment/RationalTeamConcertForZOSPerformanceComparisonBetweenReleases • Disable Monitor the last contact time to reduce the CPU consumption on the build machine

RTC Source Code Data indexes Background • Source code data is collected by scanning the files in a stream • Streams share the same configuration at some key states of their life • When the files are the same, it’s pointless to rescan. Not rescanning saves processing time & space in the Jena indices RTC is able to share Source Code data between streams when 2 (or more) streams share the same configuration of component(s) • This happens when you duplicate a stream • This happens when you add/replace a component from a stream to a stream

-share <URL of the stream>

Sharing is transparent • Except that update SCD is very fast ! Indexes don’t necessarily stay shared • They « diverge » when structural changes in files occur. • The new scan request dialog has a mechanism to re-share what's

common between two streams

Build on z/OS optimization: Java shared classes

13

• Configure -Xshareclasses for the build agent so that the JVM will load the classes from its cache rather than the jar files. • The cache is also shared across Java processes. • https://www-

01.ibm.com/support/knowledgecenter/SSYKE2_7.0.0/com.ibm.java.zos.70.doc/diag/appendixes/cmdline/Xshareclasses.html • The following example will create a cache file

/tmp/blz_javasharedresources/javasharedresources/C240D2A64_memory_BLZ601_G11 with id BLZ601 and a maximum size of 20 Mb. All Java processes using this same cache name will read classes from this same file.

Build on z/OS optimization:

14

• Using Ant tasks like logPublisher or artifactFilePublisher can consume some CPU because they reconnect to the server and upload a file to the build result. It is therefore recommended to use them once at the end of the build rather than for example after each compile in an external shell or REXX script launching a new JVM with Ant.

http://www-01.ibm.com/support/knowledgecenter/SSYMRC_6.0.1/com.ibm.team.build.doc/topics/r_ant-tasks.html?lang=en • In 6.0.1, a new property com.ibm.team.build.ant.reuseLoginOptionhas been added for Build Ant tasks. If this property is set to true, all

tasks reuse this connection as long as they connect to same repository with same user ID. • In 6.02, logPublisher implements a new batch mechanism. Logs will only be uploaded by set of x files (default is 40). Also, the task

shares the repository connection with the rest of the build, which makes it much faster. • Disable ENV/SET entries in build log (new in v6.0) using properties _SUPPRESS_ENV_OUTPUT. Your log will be less verbose ! • https://jazz.net/jazz/web/projects/Rational%20Team%20Concert#action=com.ibm.team.workitem.viewWorkItem&id=350252 • For Team build, never publish build maps (they will be listed in the build report).

Build on z/OS optimization: WLM

15

You can differentiate WLM classes assigned to the build agent or to the build processes by creating classification rules of: • type AI to match with _BPX_ACCT_DATA property • type TN to match with _BPX_JOBNAME property

Build on z/OS optimization: WLM

16

export _BPX_ACCT_DATA=BLZD export _BPX_JOBNAME=BLZO601

• Modify startba.sh to export _BPX_ACCT_DATA or _BPX_JOBNAME with the WLM classification values matching rules AI or TN for the build agent daemon class. For example:

• Modify your build definition or build engine to add properties BPX_ACCT_DATA or _BPX_JOBNAME with the WLM classification

values matching rules AI or TN for the build process class.

Build on z/OS optimization: WLM

17

• After having installed and refreshed the WLM configuration (with for example command vary wlm,policy=MVSBLD09,refresh), the build tasks should show the configured WLM service class: STCLO for the build agent daemon and STCMD for the build process.

Understanding the version ID in history

Understanding the version ID in history

19

• https://jazz.net/forum/questions/212150/understanding-the-version-id-in-history?utm_campaign=forum&utm_medium=email&utm_source=forum-new-answer&utm_content=forum-question

This is a simple example but contains a lot of info

Version 8: there was a “resolve with mine”. The check-in history of 16 explains why we are missing versions:

Understanding the version ID in history

20

Again, a resolve with mine was done on version 15 and a new check-in with 16

RDz user build Limitation and Build properties

RDz user build: some limitations

22

• User build supports only COBOL and PL/I, see http://www-

01.ibm.com/support/knowledgecenter/SSQ2R2_9.5.1/com.ibm.rational.rtc.rdz.doc/topics/rdzrtcz_int_user_build.html?lang=en • User build does not support instream DD, see the request for enhancement at https://www.ibm.com/developerworks/rfe/execute?use_case=viewRfe&CR_ID=72619

RDz user build: managing build properties

23

• Since RDz v9.5.1, it is possible to add specific properties to a user build or to override RTC ones, see https://www.ibm.com/developerworks/rfe/execute?use_case=viewRfe&CR_ID=62420

• For example with a translator using a TSO command like where MyProperty is defined on the build definition: EXEC 'GAUNEA2.PMRS.REXX(TSTCOMP)' '${MyProperty} ${requestUUID} ${buildResultUUID} ${personalBuild}

${team.enterprise.scm.fetchDestination} @{source.member.name} ${buildDefinitionId}'

RDz user build: managing RTC build properties

24

• ${requestUUID} is not applicable to a RDz user build and can therefore not be substituted. Since 9.5.1, it is possible to override it in RDz:

• RDz user build property mechanism can also be extended through a custom plugin, see the extension point at http://www-01.ibm.com/support/knowledgecenter/SSQ2R2_9.5.1/com.ibm.rational.rtc.rdz.doc/topics/pde_schema_com-ibm-teamz-zide-

ui-userBuildProperty_preview.html?lang=en

RDz user build: managing RTC build properties

25

• In RDz user build v9.5.1, the generated JCL is: • RDz user build v9.1.1 performs a single pass variable substitution and will not be able to resolve ${buildRequesterUserId}. • Also some RTC properties are not supported like ${buildResultUUID} ${personalBuild} and the generated JCL would be:

//SYSTSIN DD * ISPSTART CMD(EXEC 'GAUNEA2.PMRS.REXX(TSTCOMP)' 'Value1 ${requestUUID- } ${buildResultUUID} ${personalBuild} /u/GAUNEA2/rtc HELLO2 MybuildWithVariables') //*

//SYSTSIN DD * ISPSTART CMD(EXEC 'GAUNEA2.PMRS.REXX(TSTCOMP)' 'Value1 req1 5691110A- FALSE /u/GAUNEA2/rtc HELLO2 MybuildWithVariables') //*

Notices and Disclaimers

26

Copyright © 2016 by International Business Machines Corporation (IBM). No part of this document may be reproduced or transmitted in any form without written permission from IBM.

U.S. Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM.

Information in these presentations (including information relating to products that have not yet been announced by IBM) has been reviewed for accuracy as of the date of initial publication and could include unintentional technical or typographical errors. IBM shall have no responsibility to update this information. THIS DOCUMENT IS DISTRIBUTED "AS IS" WITHOUT ANY WARRANTY, EITHER EXPRESS OR IMPLIED. IN NO EVENT SHALL IBM BE LIABLE FOR ANY DAMAGE ARISING FROM THE USE OF THIS INFORMATION, INCLUDING BUT NOT LIMITED TO, LOSS OF DATA, BUSINESS INTERRUPTION, LOSS OF PROFIT OR LOSS OF OPPORTUNITY. IBM products and services are warranted according to the terms and conditions of the agreements under which they are provided.

Any statements regarding IBM's future direction, intent or product plans are subject to change or withdrawal without notice.

Performance data contained herein was generally obtained in a controlled, isolated environments. Customer examples are presented as illustrations of how those customers have used IBM products and the results they may have achieved. Actual performance, cost, savings or other results in other operating environments may vary.

References in this document to IBM products, programs, or services does not imply that IBM intends to make such products, programs or services available in all countries in which IBM operates or does business.

Workshops, sessions and associated materials may have been prepared by independent session speakers, and do not necessarily reflect the views of IBM. All materials and discussions are provided for informational purposes only, and are neither intended to, nor shall constitute legal or other guidance or advice to any individual participant or their specific situation.

It is the customer’s responsibility to insure its own compliance with legal requirements and to obtain advice of competent legal counsel as to the identification and interpretation of any relevant laws and regulatory requirements that may affect the customer’s business and any actions the customer may need to take to comply with such laws. IBM does not provide legal advice or represent or warrant that its services or products will ensure that the customer is in compliance with any law

Notices and Disclaimers Con’t.

27

Information concerning non-IBM products was obtained from the suppliers of those products, their published announcements or other publicly available sources. IBM has not tested those products in connection with this publication and cannot confirm the accuracy of performance, compatibility or any other claims related to non-IBM products. Questions on the capabilities of non-IBM products should be addressed to the suppliers of those products. IBM does not warrant the quality of any third-party products, or the ability of any such third-party products to interoperate with IBM’s products. IBM EXPRESSLY DISCLAIMS ALL WARRANTIES, EXPRESSED OR IMPLIED, INCLUDING BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.

The provision of the information contained h erein is not intended to, and does not, grant any right or license under any IBM patents, copyrights, trademarks or other intellectual property right.

IBM, the IBM logo, ibm.com, Aspera®, Bluemix, Blueworks Live, CICS, Clearcase, Cognos®, DOORS®, Emptoris®, Enterprise Document Management System™, FASP®, FileNet®, Global Business Services ®, Global Technology Services ®, IBM ExperienceOne™, IBM SmartCloud®, IBM Social Business®, Information on Demand, ILOG, Maximo®, MQIntegrator®, MQSeries®, Netcool®, OMEGAMON, OpenPower, PureAnalytics™, PureApplication®, pureCluster™, PureCoverage®, PureData®, PureExperience®, PureFlex®, pureQuery®, pureScale®, PureSystems®, QRadar®, Rational®, Rhapsody®, Smarter Commerce®, SoDA, SPSS, Sterling Commerce®, StoredIQ, Tealeaf®, Tivoli®, Trusteer®, Unica®, urban{code}®, Watson, WebSphere®, Worklight®, X-Force® and System z® Z/OS, are trademarks of International Business Machines Corporation, registered in many jurisdictions worldwide. Other product and service names might be trademarks of IBM or other companies. A current list of IBM trademarks is available on the Web at "Copyright and trademark information" at: www.ibm.com/legal/copytrade.shtml.

Thank You Your Feedback is Important!

Access the InterConnect 2016 Conference Attendee Portal to complete your session surveys from your

smartphone, laptop or conference kiosk.