Sample advisor: preventing multi-module change sets

It has been a while since my last post. It hasn’t been because of lack of ideas, rather time, although the blog has been bugging me in the back of my mind for attention for quite some time. So here we go … for this come back I have picked an always interesting topic, to force some rules in your SCM.

I wanted to talk about one aspect of managing change sets in Rational Team Concert. Tools like RTC and Rational Developer for z Systems come in hand with the cultural and practices changes in the umbrella of Enterprise Modernization, but let’s face it, there are certain challenges that come into play in discussions with customers quite commonly and will take some time to leave … if ever (languages used and platform peculiarities play their part as well).

Continue reading

Manually inspecting your RTC generated package for z/OS

I guess any user of Rational Team Concert Enterprise Extensions is familiar with the packaging feature (see Packaging and deploying with Enterprise Extensions otherwise). This packaging feature, based on the location specified in its definition, stores the  package it generates for a later deployment. The package can additionally be added to the packaging result Downloads tab with the following flag:


While the package result provides a great insight of what has been packaged in the “Package Summary” tab and the “Package Summary Work Item” that creates; what if I want to manually inspect the contents of the package? Continue reading

Unique Files Names SCM Advisor

In (specially) mainframe development environment, there are situations in which duplicate element names can be problematic. And from time to time I get helping customers migrate to Rational Team Concert, I find them asking of a way of ensuring this source elements names uniqueness in SCM can be enforced. In this post I am going to show an advisor for such enforcement, and talk about some restrictions to the approach.

Continue reading

Custom Services Configuration Properties – naming collision issues

I have recently been working on writing a custom service to automate some computed information retrieval from an RTC Server. That service I wanted it to have a configuration property that could be set/modified using the Advanced Properties page (https://<yourServerURI>/ccm/admin). In that process I faced a “dummy” issue that made me waste some precious time, so I wanted to share here my experience.

This post is meant to be a really short one, with the idea of providing a tip based on my experience.

Note: if this a kind of custom element you may need in your deployment but you don’t know where to start, I advice you to firstly take a look at Hello Jazz — How to write a simple Jazz component at

Continue reading

Work Item cross-stream deliveries and promotion – a sample precondition

Work Item based Promotion allows you to move your changes related to a certain work item in your streams hierarchy. At the same time, Rational Team Concert allows a great flexibility to “move” your changes between work items, so developers can report their work or decide which changes better represent their tasks work. However, when it comes to work items promotion, there are times where this flexibility can lead you to undesired scenarios.

Continue reading