Topic
7 replies Latest Post - ‏2014-07-17T08:47:01Z by anthonyk
Norricorp
Norricorp
77 Posts
ACCEPTED ANSWER

Pinned topic 256 char file + path name limit on windows for merging?

‏2008-09-12T08:12:35Z |
If a merge is done on windows where the pathname is greater than 256 chars in a dynamic view, has anyone seen this fail?

I have seen problems when you do a graphical update on a snapshot view when the path is greater than 256 but doing a command line update gets round that problem.

I have not seen problems with the 256 limit in a dynamic view but am being told it happens. Possibly I have not seen it because snapshot paths are longer due to the extra directories for view root and therefore never had a dynamic view with a 256 path length.
Updated on 2008-09-14T17:54:46Z at 2008-09-14T17:54:46Z by SystemAdmin
  • SystemAdmin
    SystemAdmin
    47293 Posts
    ACCEPTED ANSWER

    Re: 256 char file + path name limit on windows for merging?

    ‏2008-09-12T08:50:44Z  in response to Norricorp
    Yes, unfortunately it does fail.

    For one-off tasks you can alleviate this problem a little bit by mapping one "long" directory to a single drive letter, using the "subst" command, i.e.:

    subst T: "Z:\something\something else\etc"

    will map the "long" path on Z: to T:. However, this is quite a kludge and I don't really know how you could make it work efficiently with everyday tasks.

    Regards,

    Kristijan
    • SystemAdmin
      SystemAdmin
      47293 Posts
      ACCEPTED ANSWER

      RE: [cciug] Re: 256 char file + path name limit on windows for merging?

      ‏2008-09-12T16:45:25Z  in response to SystemAdmin
      The long-term solution is to design your branching strategy to keep it
      as flat as possible.
      This may or may not include a nomenclature process which enforces
      shorter view and branch names, but
      in the end flatter trees are essential.

      We avoid deriving projects from each other, rather we merge them back to
      main to create a BASELINE for
      the next project.

      ric

      -----Original Message-----
      From: cciug-bounces@lists.ca.ibm.com
      mailto:cciug-bounces@lists.ca.ibm.com On Behalf Of Rational ClearCase
      Sent: Friday, September 12, 2008 1:51 AM
      To: cciug@lists.ca.ibm.com
      Subject: cciug Re: 256 char file + path name limit on windows for
      merging?

      Yes, unfortunately it does fail.

      For one-off tasks you can alleviate this problem a little bit by mapping
      one "long" directory to a single drive letter, using the "subst"
      command, i.e.:

      subst T: "Z:\something\something else\etc"

      will map the "long" path on Z: to T:. However, this is quite a kludge
      and I don't really know how you could make it work efficiently with
      everyday tasks.

      Regards,

      Kristijan

      _______________________________________________
      cciug mailing list
      cciug@lists.ca.ibm.com
      Unsubscribe:cciug-leave@lists.ca.ibm.com
  • SystemAdmin
    SystemAdmin
    47293 Posts
    ACCEPTED ANSWER

    Re: 256 char file + path name limit on windows for merging?

    ‏2008-09-12T14:13:49Z  in response to Norricorp
    The 256 (approx) limit is a Windows imposed one. We only solved it her by reducing the package length of our java packages.

    Best Regards,
    Graham Turnbull
  • SystemAdmin
    SystemAdmin
    47293 Posts
    ACCEPTED ANSWER

    RE: [cciug] 256 char file + path name limit on windows for merging?

    ‏2008-09-12T14:18:24Z  in response to Norricorp
    OK, kiddies, DON'T do this at home.
    If the total pathname length gets longer than 255, Windows gets upset.
    Here's a definitive answer...

    nm = 'a'
    do i = 1 to 300
    'cmd /c rename c:\'nm nm'a' -- Add one char to dir name.
    nm = nm || 'a'
    'type c:\'nm'\filename.txt > nul:' -- See if new, longer, dirname
    still works.
    if rc = 0 then worked = 'yes'
    else worked = 'no'
    say "dirname is" nm~length "chars long; type worked:" worked"."
    end

    I tried to use all windows cmd prompt commands.
    The dir contained a file called "filename.txt".

    Towards the end, we have:
    ...
    dirname is 242 chars long; type worked: yes.
    dirname is 243 chars long; type worked: yes.
    The system cannot find the path specified.
    dirname is 244 chars long; type worked: no.

    So, when the dir name (244 chars) plus filename (12 chars) hits 256
    chars (exclusive of drive letter), the file can't be opened.
    This is just on the C:\ folder (no ClearCase to consider).
    Windows XP Pro, SP 2.

    BTW, the reason NOT to try this at home is removing the too-long dir
    requires a trick:
    Dir /x
    Shows the short, 8.3 version of the file name.
    Then use that name:
    Rename AAAAAA~1 a
    Matthew Miner

    > -----Original Message-----
    > From: cciug-bounces@lists.ca.ibm.com
    > mailto:cciug-bounces@lists.ca.ibm.com On Behalf Of Rational
    > ClearCase
    > Sent: Friday, September 12, 2008 4:13 AM
    > To: cciug@lists.ca.ibm.com
    > Subject: cciug 256 char file + path name limit on windows
    > for merging?
    >
    > If a merge is done on windows where the pathname is greater
    > than 256 chars in a dynamic view, has anyone seen this fail?
    >
    >
    >
    > I have seen problems when you do a graphical update on a
    > snapshot view when the path is greater than 256 but doing a
    > command line update gets round that problem.
    >
    >
    >
    > I have not seen problems with the 256 limit in a dynamic view
    > but am being told it happens. Possibly I have not seen it
    > because snapshot paths are longer due to the extra
    > directories for view root and therefore never had a dynamic
    > view with a 256 path length.
    >
    "Misys" is the trade name for Misys plc (registered in England and Wales). Registration Number: 01360027. Registered office: One Kingdom Street, London W2 6BL, United Kingdom. For a list of Misys group operating companies please go to http://www.misys.com/html/about_us/group_operating_companies/. This email and any attachments have been scanned for known viruses using multiple scanners.
    This email message is intended for the named recipient only. It may be privileged and/or confidential. If you are not the named recipient of this email please notify us immediately and do not copy it or use it for any purpose, nor disclose its contents to any other person. This email does not constitute the commencement of legal relations between you and Misys plc. Please refer to the executed contract between you and the relevant member of the Misys group for the identity of the contracting party with which you are dealing.

    _______________________________________________
    cciug mailing list
    cciug@lists.ca.ibm.com
    Unsubscribe:cciug-leave@lists.ca.ibm.com
  • anthonyk
    anthonyk
    2 Posts
    ACCEPTED ANSWER

    Re: 256 char file + path name limit on windows for merging?

    ‏2014-07-17T08:47:01Z  in response to Norricorp
    Hello,
     
     
    I used Long Path Tool software that simply worked for me for Long Path files.
     
    Thank you....