You don't need to set DSTIME parameter in the secondary class.

However, OBJ.DSTIME and SynchronizeCube does not see changes in objects of secondary class.

That is the case mentioned as

The changed record is not in the extent of the base class used by the cube.

in documentation (http://docs.intersystems.com/latest/csp/docbook/DocBook.UI.Page.cls?KEY=...)

For example, let's say that you have cube Person based on Sample.Person class.

And that class Sample.Person has property Job that references persistent class Sample.Company.

If you just modify object of Sample.Company as follows:

set p = ##class(Sample.Company).%OpenId(100)
set p.Name = "New Company Name"
write p.%Save()

Then this change will not be seen by SynchronizeCube and you'll need to update cube manually:
http://docs.intersystems.com/latest/csp/docbook/DocBook.UI.Page.cls?KEY=...

Adding DSTIME parameter to the Sample.Company does not help as original cube Person is not based on this class.

Hi Ponnumani.

You cannot run class itself in Caché. You can run some classmethod of this class.

For example from terminal you can run classmethod 'PrintPersons' of class Sample.Person as follows:

USER>zn "samples"

SAMPLES>do ##class(Sample.Person).PrintPersons()

Name: Klein,Agnes E.
Name: Willeke,Imelda R.
Name: Vanzetti,Rhonda Y.
...

I encourage you to read "Caché Programming Orientation Guide".
http://docs.intersystems.com/latest/csp/docbook/DocBook.UI.Page.cls?KEY=...

Particularly it contains information on how you can use terminal to test your programs:
http://docs.intersystems.com/latest/csp/docbook/DocBook.UI.Page.cls?KEY=...