There is a great difference between OdsOpen and Navigator.ConnectDataStore...
OdsOpen "", "STORENAME", 0, 0
matches
dim store : set store = navigator.ConnectDataFinder(STORENAME)
OdsOpen "AOP5", "<corba typ=""sessionior"">IOR_STRING</corba>", 0, 0
matches
dim store : set store = navigator.ConnectDataStoreByParameter("AOP5", "<corba typ=""sessionior"">IOR_STRING</corba>")
And here the difference. When the variable store gets out of scope the ASAM ODS Corba session is closed. This would also happen if you terminate your
OdsOpen with the OdsClose that should match it. Else the session will stay open till the server times it out.
In your case this means the session with your IOR no longer exists after script has finished.
What would work around?
- You would have to create a global variable in a user command and assign the open to it. The global scope will stay open till you call close or assign nothing.
- You open the store in Navigator which will keep it open till you close it. (navigator.Display.OpenDataStoreByParameter)
There is an additional difference.
- OdsOpen will establish one connection to the server for each Open you call. Have a look at File->ASAMDataService and watch all your open stores holding client and server resources
- navigator.???? will not open a new server connection if the parameter string is equal. So if you want to open it twice append some xml <abc>1</abc> ...
Either way the best way to work like you do it is openeing the store in Navigator GUI. Second best is the global parameter but this one is harder to set up.
Most imports or ASAM scripts that I know work with a single open ....... and a close when script is finished.
Hope this helps
Andreas
