IBM Support

HD67336: RENAME VIA MACRO THE PRODUCT INSTANCE NAME IS INCOMPLETE

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as Permanent restriction.

Error description

  • ABSTRACT:-
    Rename via Macro the Product Instance Name is
    incomplete via  CATScript , but complete using the
    same code via Visual Basic CATVBA.
    .
    SCENARIO:-
    1. Load the "Bug_Demo_assembly.CATProduct" on
    R17 level.
    2. Create in the Assembly Design workbench a
    symmertry with the plane
    'bg_02_01' located in geo body 'Spiegelebenen' in
    the part
    F16740000040313000000_003_bez_axis_cl_130.CA
    TPart and the Product
    F16740000040313000201_002_cl_fx_innenteil.CATP
    roduct , In  finishing the Assembly Symmetry
    Wizzard use the Mirror, new component on all level
    Option on the top node.
    3. Run the VBA Macro. Click on OK at all messages
    4. Check the tree. All Instances are renamed
    5. Close the window and do step 1 and 2 again
    6. Now use the CATScript macro and check the
    tree
    .
    PROBLEM:- Not all instances are renamed. Both
    macro have the  same code.
    .
    EXPECTED RESULT:-Both CATVBA and CATScript
    should work properly.
    .
    

Local fix

Problem summary

  • Rename via Macro the Product Instance Name is incomplete
    via  CATScript , but complete using the same code via Visual
    Basic
    ABSTRACT:-
    Rename via Macro the Product Instance Name is
    incomplete via  CATScript , but complete using the
    same code via Visual Basic CATVBA.
    .
    SCENARIO:-
    1. Load the "Bug_Demo_assembly.CATProduct" on
    R17 level.
    2. Create in the Assembly Design workbench a
    symmertry with the plane
    'bg_02_01' located in geo body 'Spiegelebenen' in
    the part
    F16740000040313000000_003_bez_axis_cl_130.CA
    TPart and the Product
    F16740000040313000201_002_cl_fx_innenteil.CATP
    roduct , In  finishing the Assembly Symmetry
    Wizzard use the Mirror, new component on all level
    Option on the top node.
    3. Run the VBA Macro. Click on OK at all messages
    4. Check the tree. All Instances are renamed
    5. Close the window and do step 1 and 2 again
    6. Now use the CATScript macro and check the
    tree
    .
    PROBLEM:- Not all instances are renamed. Both
    macro have the  same code.
    .
    EXPECTED RESULT:-Both CATVBA and CATScript
    should work properly.
    .
    

Problem conclusion

  • THIS PROBLEM IS PERMANENT
    RESTRICTION IN
    CATIA.
    .
    Restriction Explanation
    the same code is processed with the two
    scripts
    but for
    "B80168055378100000000_001_sym_of_ap
    02_absti
    mmplatte.1"
    the inputs are differents.
    In CATVBA , .Name is called to change
    instance
    name in
    "B80168055378100000000_001_sym_of_ap
    02_absti
    mmplatte. 1" with a blank between . and 1.
    Since
    this instance name is not already
    used .Name
    method change the instance.
    In CATSript, the input is
    B80168055378100000000_001_sym_of_ap0
    2_absti
    mmplatte.1"
    without the blank. This instance name is
    already
    use.
    .
    By-Pass
    Instance name should be unique in a
    assembly.
    CATScript has to be changed to avoid
    instance
    conflict.
    .
    

Temporary fix

Comments

APAR Information

  • APAR number

    HD67336

  • Reported component name

    CATIA V5 NT>XP

  • Reported component ID

    569151000

  • Reported release

    517

  • Status

    CLOSED PRS

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2007-09-11

  • Closed date

    2007-11-30

  • Last modified date

    2007-11-30

  • 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

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSVJ2K","label":"CATIA"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"517","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
30 November 2007