HD21044: ABSTRACT: OF

APAR status

• Closed as Permanent restriction.

Error description

• Env WindowsXP+SP1
  CATIA V5R11+SP6
  Smarteam V5R11+SP6
  .
  Problem description
  ===================
  CATIA ignores the CGRs which are carried from
  Smarteam, BUT recreateS
  its owned CGRs in CATIA Local cache folder.
  .
  .
  A material 61602487.444A is sent to you for
  investigation. It contains
  - V5R11CATIA_SMARTEAM_INTEGRATION.ppt
  - CGR1.bmp
  - CGR2.bmp
  - CGR3.bmp
  - CGR4.bmp
  .
  Scenario
  ========
  1. Start up CATIA,
  2. /tools/option/Product Structure (cache
  management).
  3. In the path to the local cache
  enter in the name of Smarteam working directory
  (pls see picture CGR2.bmp)
  4. exit CATIA and start again
  5. Within CATIA, connnect to SMARTEAM
  6. FILE+NEW a CATIA Product
  7. Insert two 2 new Parts into this Product. Create
  geometry for these
  two parts (e.g a simple pad)
  8. Activate the Product and select "SmarTeam |
  Save".
  => All .cgrs will be created in the working directory
  of SMARTEAM
  9. Checkin the whole assembly
  10. Query for the Product in SMARTEAM and
  select "File Operation | Open"
  in its context-menu
  11. All the objects will be loaded in visualization
  mode
  BUT the .cgr files will be re-created ALL OVER
  AGAIN.
  12. Now using windows explorer, try to look at the
  where the newly cgrs
  are created.
  13. As shown in picture CGR1.bmp
  Under the "declared Cache folder", it recreates a
  folder structure
  of \cgr\#2\"CATIA model working path"
  14. The above scenario can be reproduced WITH
  and WITHOUT the following
  Environment Variables
  - CATIA_SMARTEAM_CACHE
  - SMARTEAM_WITH_CACHE
  15. The reason why we're using the above
  Variables is because it is
  explicitly stated on
  a. V5R11GA Program Directory "What's New in
  V5R11 - SMARTEAM -
  CATIA Integration" section, under the title "Cache
  Management";
  and
  b. V5R11 SmartClass CD (pls see the
  V5R11CATIA_SMARTEAM_INTEGRATION.ppt which
  is an extraction from
  a doc in SmartClass CD)
  that we should use them
  16. But it turns out that no matter we use the
  Variables or not, the
  problem still persists.
  .
  Two important observations
  ==========================
  1. CATIA ignores SmarTeam generated CGRs and
  recreate its owned CGRs in
  CATIA cache (CGR) folder all over again.
  No matter how we set the CATIA Local cache path,
  it doesn't match
  with the SmarTeam working folder.
  (CATIA V5 always adds an extra folder e.g.
  \cgr\#2 before "CATIA
  model working path". Not sure if it induces any
  conflict on the
  mapping of the folder name??)
  .
  2. We also find that
  SmarTeam CGR file naming is ..cgr in
  SmarTeam work folder e.g. C:\Documents and
  Settings\
  Administrator.CONCENTRIC\My
  Documents\SmarTeam\work
  (pls see CGR3.bmp)
  But in CATIA, CGR file naming is
  ..cgr in CATIA cache folder.
  (pls see CGR4.bmp)
  .
  The Impact
  ==========
  The fact is that SMARTEAM has already created all
  the cgrs and saved
  them after checkin in its vault. And So when
  customer next time
  FILE+OPEN the CATProduct to have a view,
  SMARTEAM will bring along the
  original CATIA files with the corresponding cgrs
  from the the vault to
  the working directory. But in reality, CATIA does
  not use any of those
  already-made cgrs which are saved in the work
  directory of SMARTEAM.
  Instead, CATIA just recreate ALL OVER AGIAN
  NEW cgr files in its local
  cache directory. This is really being seen as
  completely unnecessary.
  Such act is redundant and consumes a lot of
  computing time and simply
  affect V5/Smarteam performance.
  .
  It is against the objective of cache management
  being used on Smarteam,
  which is written on online documentation
  "With the cache mode activated, any user can open
  a SMARTEAM stored
  CATProduct in visualization mode without loading
  the geometry (CATPart
  files).
  1. If User 1 Checks-In a CATPart file, the
  associated cgr files go into
  the vault.
  2. If the same or another user opens a CATProduct
  file referencing the
  CATPart files, the associated cgr is used (in
  visualization mode)
  instead of the CATPart file. This enables you to
  work on large
  assemblies. "
  ..
  Customer being an important Fabrication &
  Assembly V5/Smarteam user in
  here Australia is very concerning about the
  utilization of CGR in his
  site, as he has many huge assemblies which are
  needed to be handled in
  a daily manner. The CGR implementation has
  direct effect on the
  performance of his design task.
  [BCJ]
  .
  

Local fix

Problem summary

• ABSTRACT:    OF
  Env WindowsXP+SP1
  CATIA V5R11+SP6
  Smarteam V5R11+SP6
  .
  Problem description
  ===================
  CATIA ignores the CGRs which are carried from
  Smarteam, BUT recreateS
  its owned CGRs in CATIA Local cache folder.
  .
  .
  A material 61602487.444A is sent to you for
  investigation. It contains
  - V5R11CATIA_SMARTEAM_INTEGRATION.ppt
  - CGR1.bmp
  - CGR2.bmp
  - CGR3.bmp
  - CGR4.bmp
  .
  Scenario
  ========
  1. Start up CATIA,
  2. /tools/option/Product Structure (cache
  management).
  3. In the path to the local cache
  enter in the name of Smarteam working directory
  (pls see picture CGR2.bmp)
  4. exit CATIA and start again
  5. Within CATIA, connnect to SMARTEAM
  6. FILE+NEW a CATIA Product
  7. Insert two 2 new Parts into this Product. Create
  geometry for these
  two parts (e.g a simple pad)
  8. Activate the Product and select "SmarTeam |
  Save".
  => All .cgrs will be created in the working directory
  of SMARTEAM
  9. Checkin the whole assembly
  10. Query for the Product in SMARTEAM and
  select "File Operation | Open"
  in its context-menu
  11. All the objects will be loaded in visualization
  mode
  BUT the .cgr files will be re-created ALL OVER
  AGAIN.
  12. Now using windows explorer, try to look at the
  where the newly cgrs
  are created.
  13. As shown in picture CGR1.bmp
  Under the "declared Cache folder", it recreates a
  folder structure
  of \cgr\#2\"CATIA model working path"
  14. The above scenario can be reproduced WITH
  and WITHOUT the following
  Environment Variables
  - CATIA_SMARTEAM_CACHE
  - SMARTEAM_WITH_CACHE
  15. The reason why we're using the above
  Variables is because it is
  explicitly stated on
  a. V5R11GA Program Directory "What's New in
  V5R11 - SMARTEAM -
  CATIA Integration" section, under the title "Cache
  Management";
  and
  b. V5R11 SmartClass CD (pls see the
  V5R11CATIA_SMARTEAM_INTEGRATION.ppt which
  is an extraction from
  a doc in SmartClass CD)
  that we should use them
  16. But it turns out that no matter we use the
  Variables or not, the
  problem still persists.
  .
  Two important observations
  ==========================
  1. CATIA ignores SmarTeam generated CGRs and
  recreate its owned CGRs in
  CATIA cache (CGR) folder all over again.
  No matter how we set the CATIA Local cache path,
  it doesn't match
  with the SmarTeam working folder.
  (CATIA V5 always adds an extra folder e.g.
  \cgr\#2 before "CATIA
  model working path". Not sure if it induces any
  conflict on the
  mapping of the folder name??)
  .
  2. We also find that
  SmarTeam CGR file naming is ..cgr in
  SmarTeam work folder e.g. C:\Documents and
  Settings\
  Administrator.CONCENTRIC\My
  Documents\SmarTeam\work
  (pls see CGR3.bmp)
  But in CATIA, CGR file naming is
  ..cgr in CATIA cache folder.
  (pls see CGR4.bmp)
  .
  The Impact
  ==========
  The fact is that SMARTEAM has already created all
  the cgrs and saved
  them after checkin in its vault. And So when
  customer next time
  FILE+OPEN the CATProduct to have a view,
  SMARTEAM will bring along the
  original CATIA files with the corresponding cgrs
  from the the vault to
  the working directory. But in reality, CATIA does
  not use any of those
  already-made cgrs which are saved in the work
  directory of SMARTEAM.
  Instead, CATIA just recreate ALL OVER AGIAN
  NEW cgr files in its local
  cache directory. This is really being seen as
  completely unnecessary.
  Such act is redundant and consumes a lot of
  computing time and simply
  affect V5/Smarteam performance.
  .
  It is against the objective of cache management
  being used on Smarteam,
  which is written on online documentation
  "With the cache mode activated, any user can open
  a SMARTEAM stored
  CATProduct in visualization mode without loading
  the geometry (CATPart
  files).
  1. If User 1 Checks-In a CATPart file, the
  associated cgr files go into
  the vault.
  2. If the same or another user opens a CATProduct
  file referencing the
  CATPart files, the associated cgr is used (in
  visualization mode)
  instead of the CATPart file. This enables you to
  work on large
  assemblies. "
  ..
  Customer being an important Fabrication &
  Assembly V5/Smarteam user in
  here Australia is very concerning about the
  utilization of CGR in his
  site, as he has many huge assemblies which are
  needed to be handled in
  a daily manner. The CGR implementation has
  direct effect on the
  performance of his design task.
   BCJ
  .
  

Problem conclusion

• THIS PROBLEM IS PERMANENT RESTRICTION IN
  SMARTEAM Integration
  The described behaviour is the supported one.
  The environment variables enable are not any
  more supported (V5R11 documentation was not up
  to date).
  Although cgr are duplicated, they are correctly
  used in CATIA and updated only when necessary.
  There are two kind of cgrs used with
  SMARTEAMIntegration:
  - cgr for STEAM viewer. THey are created when
  performing save in CATIA.
  - cgr for CATPart. they are created when opening
  the CATPart in CATIA as all CATIA cgrs
  It's not possible to have only one cgr for this two
  applications.
  .
  

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