Workaround: An IBM i Build Specification build does not rebuild objects based on dependency changes

Summary

In some cases, after you upgrade to Rational Team Concert 4.0 or 4.0.1, your IBM i Build Specification build only processes those members you have directly modified, along with their resulting objects.

More Information

Problem

Before version 4.0, source members of IBM i Build Specification builds did not need an associated language definition. The source code data collection service automatically scanned those source members using default scanners. With version 4.0, the source code data collection service only scans source members to which you have explicitly assigned a language definition, or those you can associate with a default language definition.

Workarounds

Create a default language definition for each source member extension and associate it with a scanner. If you can apply a scanner to multiple file extensions, you can create one single language definition and add those file extensions to it; for example, if you have RPG ILE members, you can create a language definition with a file extension like this: “rpgle”. In the Language Definition editor, on the Scanners tab, add the IBM i default scanner, which determines the right scanner to use based on the member extension. In this case, you do not need to create a translator, and you can leave the list of translators empty.

Related Information

The following links point to related information:


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.
Feedback
Was this information helpful? Yes No 1 person rated this as helpful.