Pro/Intralink Scripting Issue

[bbailey]

Hi All,

I am working on a Pro/Intralink script that uses the
Application.launchProE method to launch Pro bound to a given Workspace.
The intent is that a Pro/TOOLKIT app will be invoke to accomplish some
tasks, then control will return to the script.

The issue I am having is that the Application.launchProE method returns
control to the script immediately, not waiting for Pro at all.

I have tried launching Pro in it's own shell, using the start /w command,
but that fails as well. Does anyone have a method for stating Pro/E in a
batch file and causing the batch file to wait until Pro has returned?

Thanks,

Ben

This thread is inactive and closed by the PTC Community Management Team. If you would like to provide a reply and re-open this thread, please notify the moderator and reference the thread. You may also use "Start a topic" button to ask a new question. Please be sure to include what version of the PTC product you are using so another community member knowledgeable about your version may be able to assist.

[gchampoux]

We had a similar problem.

To my knowledge, there is no way to force an Intralink script to wait for Pro/E to finish.

Our workaround: Our batch file launches Intralink with one script to do some tasks.

The batch file then launches Pro/E (not from the Intralink script)and then another Intralink session to wrap up.

Gerry

[bbailey]

Thanks Gerry!

I have about come to the same conclusion. Unfortunately, my script is
interactive. My current investigation paths are (1) Launch Pro/E and
invoke a trail file. Ilink WILL wait for that. Will have to play some
games to get the TOOLKIT going. The advantage is that Ilink handles all
the connection issues. (2) Use JAVA methods to invoke an Asynchronous
TOOLKIT app and wait for that. I don't have a whole lot of experience
with Asynchronous mode, plus I would need to handle all the connection
issues myself.

I'll post a summary once I wrangle this Beastie to the ground.

Ben

[FV]

Hi all,

Ben,

If you are running Windows XP or above, you could add the following construct to the startup batch file:

:LOCK_LBL

rem sleep 5

tasklist /FI "IMAGENAME eq xtop.exe" | findstr /i "xtop"

if %ERRORLEVEL%neq 0 goto :CONT_LBL

goto LOCK_LBL

:CONT_LBL

...

I don't remember where 'sleep' command or equivalent on Windows machine was located...

The same idea works from toolkit app: spawn a process, watch for xtop.exe process in 'while' loop, continiue after theprocess termination.

Another approach isto access a trail file from toolkit app and watch for themagic '!End of Trail File' string.

HIH.

FV.

In Reply to Ben Bailey:

Thanks Gerry!

I have about come to the same conclusion. Unfortunately, my script is
interactive. My current investigation paths are (1) Launch Pro/E and
invoke a trail file. Ilink WILL wait for that. Will have to play some
games to get the TOOLKIT going. The advantage is that Ilink handles all
the connection issues. (2) Use JAVA methods to invoke an Asynchronous
TOOLKIT app and wait for that. I don't have a whole lot of experience
with Asynchronous mode, plus I would need to handle all the connection
issues myself.

I'll post a summary once I wrangle this Beastie to the ground.

Ben