It's all about the answers!

Ask a question

In RTC EE Build definition, Can the resource prefix have variable names that could be substituted at run time to form the DSN prefix name ?

Ravikanth Chavali (401724) | asked Sep 23 '15, 5:02 p.m.
edited Sep 23 '15, 5:04 p.m.

Currently using RTC v5.0.2, Clarification on the build definitions, specifically zOS Dependency Build - Rational Build Agent.

Can the Resource prefix under "Jazz Source Control" be variables that could be substituted at the build request time ? Similar to Load directory.


Use case:- We are having to create build definitions for each sub appl pneumonic since it takes literals.

Wish Goal:- Use variables that could be substituted based on the context within which the zFile lives (partial or full names of - zComponent, zComponent Project, zFolder)

Or any other alternative ?

Thank you,

Ravikanth Chavali

2 answers

permanent link
Lu Yuliang (16) | answered Sep 24 '15, 2:27 a.m.
Hi Ravikanth - Resource Prefix is not supported to use variables. However if compiling to get dual modules into different PDS is your use case, you could try conditional translators available since 5.0.1, see for details. 

permanent link
Alex Akilov (1211724) | answered Sep 30 '15, 12:51 p.m.
edited Sep 30 '15, 12:52 p.m.

If your ENVNAME maps to DEV, INT or PROD, would it make sense to reverse your qualifiers to HLQ.RTC.$ENVNAME.$APPLNAME?  If possible, then you can simply have build definitions for each environment that have the corresponding prefix HLQ.RTC.$ENVNAME but the $APPLNAME will instead be prepended to the value in the data set definition that's associated to your zFolders.  So if you have a zFolder called COBOL with COBOL also being the value defined in the data set definition associated with that zFolder, you would define application specific zFolders with a data set definition that contains the name $APPLNAME.COBOL

Ravikanth Chavali commented Sep 30 '15, 1:41 p.m. | edited Sep 30 '15, 1:44 p.m.

 That's true; But the way I see it is, that just shits the problem to a different side. Instead of having multiple build definitions, we will end up having multiple dataset definitions for each type(src-cob, pli, ezt, asm, jcl, proc, parm, etc.) of zFolder for each application (~20) , and also make sure to do the mapping/association correct.

Your answer

Register or to post your answer.