HD84532: STCAI: Script fails to get CATIA object

APAR status

• Closed as Permanent restriction.

Error description

• STCAI: Script fails to get CATIA object
  .
  CATIA SmarTeam integration problem reproduced
  on SmDemo
  .
  Scenario:
  1. Start the Script Maintenance tool
  2. Hook the attached script file for CATIA V5 object
  class / Life Cycle Stage 1[Before].
  3. Start CATIA and create a new CATPart
  4. Connect to SmarTeam and launch SmarTeam
  Editor.
  5. Save the CATPart in SmarTeam
  6. Start the check-in operation using
  SmarTeam/Life Cycle/Check In menu on CATIA.
  7. Leave the CheckIn window opened for about 5
  minutes
  8. Click Ok button on the CheckIn window
  Problem: The script fails to get the CATIA session
  (error message: OLE Automation object does not
  exist).
  Problem can be reproduced with MS Word (and an
  ActiveX exe). But the time-out is about 25 minutes.
  

Local fix

Problem summary

• STCAI: Script fails to get CATIA object
  .
  CATIA SmarTeam integration problem reproduced
  on SmDemo
  .
  Scenario:
  1. Start the Script Maintenance tool
  2. Hook the attached script file for CATIA V5 object
  class / Life Cycle Stage 1[Before].
  3. Start CATIA and create a new CATPart
  4. Connect to SmarTeam and launch SmarTeam
  Editor.
  5. Save the CATPart in SmarTeam
  6. Start the check-in operation using
  SmarTeam/Life Cycle/Check In menu on CATIA.
  7. Leave the CheckIn window opened for about 5
  minutes
  8. Click Ok button on the CheckIn window
  Problem: The script fails to get the CATIA session
  (error message: OLE Automation object does not
  exist).
  Problem can be reproduced with MS Word (and an
  ActiveX exe). But the time-out is about 25 minutes.
  

Problem conclusion

• THIS PROBLEM IS PERMANENT RESTRICTION IN CATIA
  Additional Closure Information:
  Incident Diagnosis:
  When a script is hooked on a SmarTeam event and called after
  5 minutes waiting, the GetObject (, "CATIA.Application")
  instruction fails.
  Reason:
  This is a restriction due to the infrastructure of the CATIA
  code and to Microsoft. During lifecycle operations, SmarTeam
  and CATIA communicate through Windows COM API. This scenario
  is a limitation of using the Windows COM technology.
  Detailed Explanations:
  1. When CheckIn window is kept opened, CATIA calls the
  SmarTeam CheckIn operation (through Microsoft COM API) but it
  stays inactive and waits for SmarTeam answer. During this
  time, for CATIA, the windows message stack is getting bigger
  and bigger. (because it calls the SmarTeam CheckIn operation
  for at least 5 minutes)
  2. When click on CheckIn button, SmarTeam calls back CATIA
  (because of the script) using the COM API: GetObject
  3. The GetObject call fails because on CATIA side, the
  windows message stack is full and has reached the maximum
  authorized. So, the GetObject can't be managed.
  Correct Application:
  Do not wait 5 minutes before clicking on the OK button when
  LifeCycle window is opened
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

Applicable component levels