Stats

  • Replies 2
  • Subscribers 17
  • Views 6242
  • Members are here 0
More Content

axlRunBatchDBProgram to run a report in 17.4

HJerry

Hi all,

We are using the following syntax, in 17.2, to create different reports and it works fine.

sprintf(cmd, "report -v sum \"%s\" summary.rpt", axlGetDrawingName() )
axlRunBatchDBProgram("summary report" cmd ?noLogview t ?noExitMsgs t)

When I try the same code in 17.4 it does no recognize axlGetDrawingName() as the for the design name.

I also tried axlCurrentDesign() and that did not work in 17.4, either.

Any ideas would be appreciated.

Thanks,

Jerry

  • DavidJHutchins

    I am running allegro 17.4 S020 Windows SPB 64-bit Edition

    I don't have any issues with core commands not working correctly:

    \i (01:10:48) skill axlGetDrawingName()
    (01:10:48) "D:/SPB_Data/xxxx/Eagle_Fountain/eagle_fountain_sfp_dp_lp_110821c.brd"
    \i (01:11:07) skill axlCurrentDesign()
    (01:11:07) "eagle_fountain_sfp_dp_lp_110821c"
    \i (01:11:58) skill
    \i (01:12:22) skill 'sprintf(cmd, "report -v sum `\"%s`\" summary.rpt", axlGetDrawingName() )'
    (01:12:22) "report -v sum \"D:/SPB_Data/xxxx/Eagle_Fountain/eagle_fountain_sfp_dp_lp_110821c.brd\" summary.rpt"

    however the axlRunBatchDBProgram command doesn't appear to have the correct syntax:

    \i (01:12:49) skill 'axlRunBatchDBProgram("summary report" cmd ?noLogview t ?noExitMsgs t)'
    \e (01:12:49) Batch command line string missing "%s" placeholder for design name; command line must be formatted properly.
    \i (01:13:00) fillin confirm
    (01:13:00) -1

  • HJerry

    I found the issue. In 17.4 you need to escape the %s with a % when doing a sprintf. So:

    sprintf(cmd, "report -v sum \"%%s\" summary.rpt" axlGetDrawingName())

    axlRunBatchDBProgram("summary report" cmd ?noLogview t ?noExitMsgs t)

    Thanks,

    Jerry

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.