• Skip to main content
  • Skip to search
  • Skip to footer
Cadence Home
  • This search text may be transcribed, used, stored, or accessed by our third-party service providers per our Cookie Policy and Privacy Policy.

  1. Community Forums
  2. Allegro X Scripting - TCL
  3. Fail to open DSN with TCL due to both "dot" and "space"...

Stats

  • State Not Answered
  • Replies 2
  • Subscribers 14
  • Views 132
  • Members are here 0
More Content

Fail to open DSN with TCL due to both "dot" and "space" in the file name

Gelzone
Gelzone 4 days ago

I try both Menu "File::Open::Design" and MenuCommand "57601" to open my file with tcl but fail.

The file name is "<project folder>/test_M.2 test1.DSN" and the error message shows something like "<project folder>/test_M.2 not found".

And I try to remove the "dot" (keep the "space"), the command can open the DSN file successfully.
Another experiment that keeping "dot" but remove "space" also works well.

So I think this file not found issue will occur when both "dot" and "space" exist in the file name.

  • Cancel
  • Sign in to reply
  • JCTEYSSIER0
    0 JCTEYSSIER0 4 days ago

    Space is a field separator at operating system level.

    A lot of problem occur if usinf this caracter in pathname or name.

    My advice is to use ONLY:

    a to z

    0 to 9

    underscore (_)

    dash (-)

    and no other caracters.

    By the way, be aware of file pathname length, operating system like windows handhle badly verry long name (in the past, file pathname were not or badly handheld is more than 255)

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Verify Answer
    • Cancel
  • Gelzone
    0 Gelzone 4 days ago in reply to JCTEYSSIER0

    JCTEYSSIER0 

    Thanks for reply.

    The DSN name is following my company's rule so I think it's not that easy to change the format. And the DSN name will affect the netlist content, so I ain't gonna to change it to a temp name.

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Verify Answer
    • Cancel
Cadence Guidelines

Community Guidelines

The Cadence Design Communities support Cadence users and technologists interacting to exchange ideas, news, technical information, and best practices to solve problems and get the most from Cadence technology. The community is open to everyone, and to provide the most value, we require participants to follow our Community Guidelines that facilitate a quality exchange of ideas and information. By accessing, contributing, using or downloading any materials from the site, you agree to be bound by the full Community Guidelines.

© 2026 Cadence Design Systems, Inc. All Rights Reserved.

  • Terms of Use
  • Privacy
  • Cookie Policy
  • US Trademarks
  • Do Not Sell or Share My Personal Information