• 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 PCB Editor
  3. Running bat files using axlRunBatchDBProgram

Stats

  • Replies 5
  • Subscribers 158
  • Views 15149
  • Members are here 0
More Content

Running bat files using axlRunBatchDBProgram

archive
archive over 18 years ago

A while back, Frank gave us a hint that bat files could be run within axlRunBatchDBProgram. This works well (thanks Frank) and is a graceful alternative to system commands. However, I have problems with directing output to files within my batch files. ie. I might want to include this line in my batch file: dir *.* > c:\temp\files.txt The files.txt file is not created. Does anyone have a good workaround or know why this doesn't work? Cheers, Dave


Originally posted in cdnusers.org by Dave Elder
  • Sign in to reply
  • Cancel
  • archive
    archive over 18 years ago

    Hi Dave,

    Not sure how you start your command, but you might want to try this.

    start cmd /seperate mybat.bat

    This will open a new DOS command prompt, which is idenpendent of the axlRunDBBatchProcess. Like opening a link in a new Window in IE.

    Just the bat file may not work. I think SKILL is launching your command as a new child process and I remember that DOS doesn't like this with bat files because it has to invoke the command prompt first.

    So the following might work too

    cmd.exe mybat.bat

    I am not sure what benefit you gain compared to using the system command in SKILL?

    If that doesn't work, you could write yourself a small wrapper in java. I think I have one somewhere.

    Andy ;-)


    Originally posted in cdnusers.org by andyk
    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Cancel
  • archive
    archive over 18 years ago

    Thanks Andy, I'll check out your ideas. Mye batch file runs OK but the redirect doesn't create a file.
    Why I don't like system calls: The system command opens a DOS window, albeit briefly, on the workstation. With multiple calls, this can be quite distracting to the user. Cheers, Dave


    Originally posted in cdnusers.org by Dave Elder
    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Cancel
  • Grungy Remnant
    Grungy Remnant over 16 years ago

    HI.  Did anyone ever have a solution for this?  I too am trying to avoid the system command to avoid the pop-ups. Although I don't need to run a bat file.   An example is the following CVS command:

    command prompt:   cvs watched >cvslog     this works and redirects the output to the cvslog file

     

    skill:     system("cvs watched >cvslog")     this also works as expected, including the

    redirect, but you get the cmd popup briefly

     

    axlSkill:  axlRunBatchDBProgram("cvs" "cvs watched >cvslog")  The cvs command works but the redirect does not work.  The same thing will happen using a bat file.  Adding cmd.exe in the bat file doesn't help either.  (ie. cmd.exe cvs watched >cvslog )

     

    So are redirects just not possible with axlRunBatchDBProgram or am I missing something?

     

    Thanks for any info!!

     CJB

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Cancel
  • wolfwang
    wolfwang over 16 years ago

    a good study skill website URL:   www.2ndevelop.com

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Cancel
  • Silver John
    Silver John over 14 years ago

     Hi, Dave, Grungy Remnant.

    I have similar problem (shell( "hg branch > ../hg.tmp").

    Are you found solution?

    Also question: what difference between system() and shell(), without regard for returning value?

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • 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.

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

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