HD49724: SET PERMISSIONS BY VB SCRIPT NOT RECOGNIZED FOR CATIA FILES U SING WINDOWS MAPPED DRIVES

APAR status

• Closed as Permanent restriction.

Error description

• Set permissions by VB Script not recognized for
  CATIA files using Windows mapped drives.
  .
  A Setup preparations
  1. Create two directory: H:\AutoSave\R14Catia\Utv
  and
  H:\AutoSave\R14Catia\Prod
  2. Share H:\AutoSave\R14Catia\Utv as "Read
  Write"
  3. Share H:\AutoSave\R14Catia\Prod as "Read
  Only"
  4. Map H:\AutoSave\R14Catia\Utv to Y:
  5. Map H:\AutoSave\R14Catia\Prod to Z:
  6. Change "Search Order" in Catia to only
  use "Other folders"
  7. Configure "Other folders" first to Utv and then to
  Prod
  Note. Do not use the "Read Only" attribute, only
  permission by group and
  users.
  .
  B Prepare Catia data
  1. Create a new product (top level assembly)
  2. Under that product create a new product (middle
  level assembly)
  3. Under that product create a new product (lower
  level assembly)
  4. Create a new part into the lower level assembly
  5. Save all products and the part to Y: (Your Utv
  directory)
  6. Close all documents and open the lower level
  assembly
  7. Create a copy of the part
  8. Save and close the product
  9. If you open the top product you will see this
  in "Save Management": All files have "Read Write"
  Access.
  .
  A1. Simulate the problem
  1. Move all documents except the top product to Z:
  (Prod directory)
  Move files from H:\AutoSave\R14Catia\Utv to
  H:\AutoSave\R14Catia\Prod
  and not Y: to Z:
  2. Open the top level assembly in Y: (Your Utv
  diretory)
  3. Save it by the CATScript or a VB program, see
  "AutoSaveCurrent.CATScript" below
  4. After the CATScript you see this
  Problem : In the "Save Management" you can see
  that all files in Z: are "Read Write" but that is not
  true.
  This is a very big problem, to day we have 1000 of
  files in directory's like this.
  Notes
  1. Open the middle level assembly (product2) from
  Z:
  2. Save width File->Save and you get this
  message.
  3. The "Save Management" will show that all files
  have "Read Write" Access.
  .
  To change low level products without change above
  products are used a lot when the change not
  interfere with the function or by other reason.
  Which above products who needs to be changed
  are decided by the user or by a change meeting.
  The problem seems to start after upgrade to Catia
  V5R10, before this we had a similar problem in R3
  but could be solved outside Catia. (In R6 and R7
  we had no problem?).
  The automation property Doc.ReadOnly is now
  always return false but not in previous releases.
  It looks like Catia can't recognize that the products
  are protected by the file system permission, be
  course it works if I use the read only
  attribute. See A2 test below.
  .
  A2. Read-only attribute test
  By this test I will show that it had not been a
  problem if Catia had recognize the files in Z:
  as "Read Only".
  1. Set file attribute to "Read Only" to all files in Z:
  (Prod)
  Use file property in H:\AutoSave\R14Catia\Prod to
  set the attribut.
  2. Open the top level assembly in Y: (Your Utv
  diretory)
  3. Save it by the CATScript or a VB program, see
  "AutoSaveCurrent.CATScript" attached file.
  Note NO error, but this is not a solution of the
  problem
  4. Close and reopen the top product in Y:
  you will see in "Save Management": files in Z:
  have "Read Only" Access and files in Y: have "Read
  Write" Access .
  .
  Problem:
  Catia donﾨt realize files from a read-only directory
  as a read-only file.
  Here files from Z: should be read-only, because of
  the settings on that shared folder.
  .
  

Local fix

Problem summary

• Set permissions by VB Script not recognized for CATIA files   u
  sing Windows mapped drives
  Set permissions by VB Script not recognized for
  CATIA files using Windows mapped drives.
  .
  A Setup preparations
  1. Create two directory: H:\AutoSave\R14Catia\Utv
  and
  H:\AutoSave\R14Catia\Prod
  2. Share H:\AutoSave\R14Catia\Utv as "Read
  Write"
  3. Share H:\AutoSave\R14Catia\Prod as "Read
  Only"
  4. Map H:\AutoSave\R14Catia\Utv to Y:
  5. Map H:\AutoSave\R14Catia\Prod to Z:
  6. Change "Search Order" in Catia to only
  use "Other folders"
  7. Configure "Other folders" first to Utv and then to
  Prod
  Note. Do not use the "Read Only" attribute, only
  permission by group and
  users.
  .
  B Prepare Catia data
  1. Create a new product (top level assembly)
  2. Under that product create a new product (middle
  level assembly)
  3. Under that product create a new product (lower
  level assembly)
  4. Create a new part into the lower level assembly
  5. Save all products and the part to Y: (Your Utv
  directory)
  6. Close all documents and open the lower level
  assembly
  7. Create a copy of the part
  8. Save and close the product
  9. If you open the top product you will see this
  in "Save Management": All files have "Read Write"
  Access.
  .
  A1. Simulate the problem
  1. Move all documents except the top product to Z:
  (Prod directory)
  Move files from H:\AutoSave\R14Catia\Utv to
  H:\AutoSave\R14Catia\Prod
  and not Y: to Z:
  2. Open the top level assembly in Y: (Your Utv
  diretory)
  3. Save it by the CATScript or a VB program, see
  "AutoSaveCurrent.CATScript" below
  4. After the CATScript you see this
  Problem : In the "Save Management" you can see
  that all files in Z: are "Read Write" but that is not
  true.
  This is a very big problem, to day we have 1000 of
  files in directory's like this.
  Notes
  1. Open the middle level assembly (product2) from
  Z:
  2. Save width File->Save and you get this
  message.
  3. The "Save Management" will show that all files
  have "Read Write" Access.
  .
  To change low level products without change above
  products are used a lot when the change not
  interfere with the function or by other reason.
  Which above products who needs to be changed
  are decided by the user or by a change meeting.
  The problem seems to start after upgrade to Catia
  V5R10, before this we had a similar problem in R3
  but could be solved outside Catia. (In R6 and R7
  we had no problem?).
  The automation property Doc.ReadOnly is now
  always return false but not in previous releases.
  It looks like Catia can't recognize that the products
  are protected by the file system permission, be
  course it works if I use the read only
  attribute. See A2 test below.
  .
  A2. Read-only attribute test
  By this test I will show that it had not been a
  problem if Catia had recognize the files in Z:
  as "Read Only".
  1. Set file attribute to "Read Only" to all files in Z:
  (Prod)
  Use file property in H:\AutoSave\R14Catia\Prod to
  set the attribut.
  2. Open the top level assembly in Y: (Your Utv
  diretory)
  3. Save it by the CATScript or a VB program, see
  "AutoSaveCurrent.CATScript" attached file.
  Note NO error, but this is not a solution of the
  problem
  4. Close and reopen the top product in Y:
  you will see in "Save Management": files in Z:
  have "Read Only" Access and files in Y: have "Read
  Write" Access .
  .
  Problem:
  Catia don t realize files from a read-only directory
  as a read-only file.
  Here files from Z: should be read-only, because of
  the settings on that shared folder.
  .
  

Problem conclusion

• THIS PROBLEM IS PERMANENT RESTRICTION IN
  CATIA
  Incident Diagnosis
  The rights of the file are not bound to the sharing
  mode of their parent folder, if it is mapped as an
  external disk. Neither the RO attributes nore the acl
  are impacted, thus each kernel call to retrieve
  these information will return the same state from
  the mapped disk in RO, or from localy on the
  machine with a RW folder.
  The export mode of the shared is an other notion.
  .
  If one looks at the file's properties through
  explorer the files will not be displayed as read only
  by windows.
  It is only when trying to write on it that applications
  will discover the RO state.
  .
  Restriction Explanation
  It has been decided by design to rely only the
  information provided by the attribute RO for the
  read only state of files :
  1- for compatibility issues between windows file
  Systems NTFS FAT
  2 - for interoperability issues between Unix and
  Windows with NFS servers
  3 - for performances issues. The only other way to
  insure that the file is really read only as a
  conjonction of its own rights and the export mode
  of the filesystem, is to open it with the desired
  access rights. This protocol is both costly and
  dangerous ( risk of letting opened files, numbers of
  files opened ...)
  Thus it is not possible to see the RO state before
  trying the write ( as MS applications)
  By-Pass
  none
  .
  

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