how to run dynamic sdo like constructObject..

What do you want to do with the SDO?

If you are tryng to use it to create data, you can do the following:

/* Define temp-table for update of timesheet table */
DEFINE TEMP-TABLE ttXXXXXRowObjUpd NO-UNDO
{pp/obj/xxxxxfullo.i}
{src/adm2/rupdflds.i}.

CREATE ttXXXXXRowObjUpd.

ASSIGN
ttXXXXXRowObjUpd.RowMod = "A":U
ttXXXXXRowObjUpd.RowNum = 100001.

ASSIGN
   ttXXXXXRowObjUpd.field = ...

RUN updateTableViaSDO IN gshGenManager (
INPUT "":U,
INPUT "

Regards

Thomas

What exactly do you want to do?

Try this:

hRepositoryManager = DYNAMIC-FUNCTION ("getManagerHandle", "RepositoryManager") .
RUN startDataObject IN hRepositoryManager ("yourfullo",
                                           OUTPUT hSDO).

thanks mike..

this procedure also run initializeObject or we explicitly initialize? 

You're welcome.

I believe the fact, that launchContainer is part of the session manager and startDataObject is part of the repository manager will always remain a secret to those that were in charge at that time.

I don't expect it to do so (but a message in initializeObject would test - or the source code of the RY manager).

It certainly would be disturbing if it would do so if you need to set properties like the partition name, rowsToBatch, OpenQueryOnInitialize ect.

mikefe wrote:
You're welcome.
I believe the fact, that launchContainer is part of the session manager and startDataObject is part of the repository manager will always remain a secret to those that were in charge at that time.

I can't profess to being in charge of anything, but since I am the person responsible for startDataObject(), I'll try to remember/explain why it's in the Repos Mgr. I'm fairly sure it has to do with the fact that the procedure directly accesses the (client-side object and class) cache temp-tables for performance reasons. No doubt, there are alternative ways of doing this that might be preferable, but that's what we decided to do at the time.

Also consolidation of the invocation/launching APIs into the Repos Mgr would probably also have been a bright thing to do (launchContainer was in the Session Manager from Day One, for reasons unknown to me).

-- peter

kartikvbn wrote:
this procedure also run initializeObject or we explicitly initialize?  

Short answer is that you need to DIY.

You can inspect the source yourself: it's installed in $DLC\src\dynamics\ry\app\ryrepmngrp.i

-- peter