What is the component divided rule for Zos source code?
Jia Jia Li (805●8●157●192)
| asked Jul 23 '13, 10:54 p.m.
edited Jul 24 '13, 11:50 p.m. by Kevin Doyle (604●2●5)
Hi, does anyone has the zos RTC source control implement experience, and do you have any suggestion to divide the zos source code and parameter files into component?
|
One answer
There are several driving factor for selecting to populate components and divide into components. This is a very good thing to componentize.
The component is the artifact of the SCM that is baselined, so you would expect to populate a component with resources that go together and need to be versioned together. Also, components are part of streams. It is possible to have the same components in different streams (at the same level of configuration or not). If you plan to create several development streams, one per team for an area, then you will probably need to share some resources (copybooks defined by an application that are used by another) between these streams. These shared resources would go in a component provided by a team and used by another in their stream. |
Your answer
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.