Is it possible to link files so that they are kept in line ?

I believe the right time to check this is at "deliver" time.
You'd have to write your own pre-operation process extension for this
(since there is no built-in functionality for this). So I think there
are two questions here:

- Jazz SCM team: How hard is it to write the pre-op trigger that
enumerates the list of files modified in a file set? Would it be
reasonable to file a request to expose an SCM primitive that does this?

- Gerardo: Assuming you have the code that will enumerate the files
changed by the deliver, how could that code determine whether a file of
this kind has been modified, and if so, what are the files that are
"linked" together in this way? Do they have some standard naming
conventions?

Cheers,
Geoff


gerardo_brenner wrote:

for example, in a development project we have a cobol, assembler, pl1
and c copybooks describing the same data area.
Is it possible to link them together so that one cannot be changed
without changing the other 3 ?

Hi Geoff,

we do have naming conventions and probably file name would be good enough for now,( we need it for programs in java and c/c++ which perform the same function ), but I was thinking more along the lines of specifying the links in the file properties, for example in the Jazz Source Control, Check-in-Policies where we could be able to specify an array of "links" or related files. This approach would be more flexible than just file names, as you could link, for example, header files to several c programs regardless of their names.

I believe the right time to check this is at "deliver" time.
You'd have to write your own pre-operation process extension for this
(since there is no built-in functionality for this). So I think there
are two questions here:

- Jazz SCM team: How hard is it to write the pre-op trigger that
enumerates the list of files modified in a file set? Would it be
reasonable to file a request to expose an SCM primitive that does this?

- Gerardo: Assuming you have the code that will enumerate the files
changed by the deliver, how could that code determine whether a file of
this kind has been modified, and if so, what are the files that are
"linked" together in this way? Do they have some standard naming
conventions?

Cheers,
Geoff


gerardo_brenner wrote:

for example, in a development project we have a cobol, assembler, pl1
and c copybooks describing the same data area.
Is it possible to link them together so that one cannot be changed
without changing the other 3 ?

There is no functionality to link files that way in Team Concert today
(but you could of course submit an enhancement request).

Cheers,
Geoff

gerardo_brenner wrote:

Hi Geoff,

we do have naming conventions and probably file name would be good
enough for now,( we need it for programs in java and c/c++ which
perform the same function ), but I was thinking more along the lines
of specifying the links in the file properties, for example in the
Jazz Source Control, Check-in-Policies where we could be able to
specify an array of "links" or related files. This approach
would be more flexible than just file names, as you could link, for
example, header files to several c programs regardless of their
names.

gmclemmwrote:
I believe the right time to check this is at "deliver"
time.
You'd have to write your own pre-operation process extension for
this
(since there is no built-in functionality for this). So I think
there
are two questions here:

- Jazz SCM team: How hard is it to write the pre-op trigger that
enumerates the list of files modified in a file set? Would it be
reasonable to file a request to expose an SCM primitive that does
this?
- Gerardo: Assuming you have the code that will enumerate the files

changed by the deliver, how could that code determine whether a file
of
this kind has been modified, and if so, what are the files that are

"linked" together in this way? Do they have some standard
naming
conventions?

Cheers,
Geoff


gerardo_brenner wrote:
for example, in a development project we have a cobol, assembler,
pl1
and c copybooks describing the same data area.
Is it possible to link them together so that one cannot be changed
without changing the other 3 ?