Tried some different scenarios in SCM. Turns out both the origin and
termination requires alarms for SCM to pick up the properties.
If I specify only a element property in either as the origin or
termination the SCM job doesn't pic them up.
In this example I have set a alarm property called "hostname" for the
origin and a element property called "neighbour" for the termination
The debug result gives the following: "Pass 1: sourceid = Element1,
targetid = null".
Verifying by debug that there is actually a property called neighbour,
with a value.

Using the same configuration but with alarms providing both origin and
termination works fine.
There seems to be a problem for the SCM to pic up element properties
while generating the dependencies.



skliber's Profile:
View this thread: