Community PCB Design & IC Packaging (Allegro X) Allegro X Scripting - Skill axlDBCheck being obsoleted

Stats

More Content

axlDBCheck being obsoleted

HJerry

Hi all,

One of our programs runs axlDBCheck and I see it is being obsoleted. The warning says to look at running dbdoctor from skill code but I can't find anything in the skill documentation. 

Has anyone found anything about this in the skill docs? If so, where abouts?

Thanks,

Jerry

  • 0

    Hi HJerry,

    I've seen reports of this message but I'm not able to reproduce it. Can you tell me what version of which tool you're using and which HF are you in?

    Also, the SKILL documentation recommends to use another command instead of axlDBCheck (even though I didn't see any warnings of it being obsolete there). The command that is recommended is axlRunBatchDBProgram. Here's an example of how to use it: 

        axlRunBatchDBProgram("dbdoctor", "dbdoctor <options> %s" ?logfile "mydbdoctor" ?reloadDB t)


    And here's the documentation for this command: 

    axlRunBatchDBProgram

    axlRunBatchDBProgram(
t_prog
t_cmdFmt
[?logfile t_logfile] [?startMsg t_startMsg] [?reloadDB t/nil] [?noUnload t/nil] [?silent t/nil] [?noProgress t/nil] [?warnProgram t/nil] ) ⇒ t/x_error

    Description

    Spawns batch jobs that require an open database via an abstract model. When the job completes, it prints a message and optionally reloads (?reloadDB) the database if successful. If the database is saved from the current active database, it uses a temporary name to avoid overwriting the database on disk.

    The following options are always required (UIBatchSpawn):

    t_prog

    Name of the program to run.

    t_cmdFmt

    Command string.

    The following options are optional.

    t_logFile

    Name of log file that the program creates. Registers this with the log file viewlog facility if the program ends in an error. If no log file is required, do not set this option. If no extension is given, adds .log as the extension.

    startMsg

    Enables a start message to display when the program starts. Defaults to the program name. If you override by providing this string, the message begins with “Starting...”

    reloadDB

    If you set this to t, the database reloads after a successful run of the program. If the batch program does not save the database (for example, reports) then there is no reason to reload database. dbids are refreshed.

    noUnload

    If you set this to t, you don’t save the database to disk. You use this for a program that creates a new database or doesn’t require an Allegro PCB Editor database. Default is nil.

    silent

    If you set this to t, no messages are displayed. Use when the user does not need to know that a program is spawned. Default is nil.

    noProgress

    If t, the progress meter does not display. Default is nil.

    noLogview

    When set, it prevents display if log file on program exit.

    noWarnOnExit

    When set, suppresses some exit warning messages.

    warnProgram

    Program supports warning status (returns 0, if success; 1, if warnings; and 2, if errors).

    noExitMsgs

    When set, suppresses messages about program success or failure.

  • 0 in reply to JuanCR

    To be a bit more clear, axlDBCheck returns (x_errors x_warnings)/nil and is what the program looks for.  Using batch, I believe, will only create the log file.

    I can open the log file and get the information that way, but was trying to avoid it.

    Thanks again.

    Hi Juan,

    Thanks for the reply.

    I am working on 17.4(S037)

    I am familiar with axlRunBatchDBProgram. From the warning I was thinking there may be a different way.

    This is the warning I get when running the program:

    W- *WARNING* (axlDBCheck): This interface is obsolete and will be removed in a future release.
    W- See documentation for tips on running batch dbdoctor program from SKILL code.

    Thanks again,

    Jerry

  • 0 in reply to HJerry

    I compared the doc files for this command between 17.4 and 23.1, below is the only addition:

    'attributes   Check all attribute-owner relationships

    I just ran this command in allegro 23.1 S002 and did not see any warning, below is the jrl file contents:

    \i (00:00:43) skill 'axlDBCheck(`'all)'
    \t (00:00:43) Checking db records
    \t (00:00:43) checking for orphans...
    \t (00:00:43) Checked 4 percent
    \t (00:00:43) Checked 8 percent
    \t (00:00:43) Checked 13 percent
    \t (00:00:43) Checked 17 percent
    \t (00:00:43) Checked 22 percent
    \t (00:00:43) Checked 26 percent
    \t (00:00:43) Checked 31 percent
    \t (00:00:43) Checked 35 percent
    \t (00:00:43) Checked 40 percent
    \t (00:00:43) Checked 44 percent
    \t (00:00:43) Checked 49 percent
    \t (00:00:43) Checked 53 percent
    \t (00:00:43) Checked 58 percent
    \t (00:00:43) Checked 62 percent
    \t (00:00:43) Checked 67 percent
    \t (00:00:43) Checked 71 percent
    \t (00:00:43) Checked 76 percent
    \t (00:00:43) Checked 80 percent
    \t (00:00:43) Checked 85 percent
    \t (00:00:43) Checked 89 percent
    \t (00:00:43) Checked 94 percent
    \t (00:00:43) Checked 98 percent
    \t (00:00:43) Checked 100 percent
    \w (00:00:44) Run batch DRC to correctly regenerate DRC errs.

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.