Interpret InductEx® process status and printed diagnostic codes

Separate process status from the printed number

Record the operating-system process result, the supervisor state and any printed diagnostic number separately. The manual’s numbered list describes messages printed in the log; it is not a universal table of shell exit values.

On the checked Windows 8.0.2 CLI, a missing main IXI and an unknown option each return process status 2 before extraction. That does not mean controlled diagnostic (2), which the manual associates with a port-label file. Engine failures tested here return process status 1, with further detail in their current logs.

Status 0 means the process ended through its normal path; it does not establish that the requested calculation, study or numerical acceptance succeeded. The legacy SWEEP example returns 0 with a warning and no extracted elements. An external watchdog also records its own timeout state independently of a numeric process exit.

Use the exercised failures as bounded examples

These are exercised outcomes for exact teaching inputs, not a promise that every related failure reaches the same code path. The missing process/netlist wording can say Cannot create file while describing a read attempt; check the stage and actual path before changing permissions.

Find the first failure and verify recovery

The complete downloadable teaching runner is shared with the scripting guide. Its missing-netlist case leaves a partial sol.txt and a failed receipt; the corrected fresh generation reproduces the original detailed result. It rejects warnings, unsupported SWEEP, failed processes and timeout states.

1. Keep the exact executable/version, process/supervisor outcome, printed diagnostic text, complete saved inputs and current run log.
2. Read the earliest current error. A missing solver result may follow an earlier failure to load a dependency, launch the solver, construct the model or create its output.
3. Use a printed controlled number with the documented reference below. Follow the actual file paths named by the selected runtime: older engine-specific filenames in the reference may differ from current artifacts.
4. Correct the cause in a separate working copy and use a new result directory. Require a fresh successful receipt and the intended current numerical data, not merely disappearance of the previous error or existence of sol.txt.

Look up every active documented diagnostic

The following 68 entries cover the active numbered descriptions in the maintained Exit Codes source. Treat unexercised rows as source-qualified reference information; their current emission path and release applicability still need verification. Do not use this list to reinterpret a shell result such as 2.

Legacy format/feature descriptions are retained within their reference scope. The virtual-cut row is deliberately phrased as a span/intersection check because the legacy wording needs clarification. No product/source manual was edited and no broad numerical or release acceptance is inferred.

Use the lookup to narrow the table, then select the number to open its stable row link. Show all diagnostics restores the complete reference. Every entry remains readable when JavaScript is unavailable; the linked number is also included in the Markdown answer and numbered-reference JSON index.

Check the result

The original failure is resolved in a fresh run, with correct input/output identity, requested quantities/units and independent numerical acceptance. Process status, controlled message number, solver verdict, artifact publication and physical accuracy remain distinct.

If the problem remains

Prepare a minimal complete reproducer and relevant first-error context for private support. Review logs and process files before sharing; omit licence contents, holder information and private fabrication data. Do not manufacture licence denials or change system permissions to guess at a diagnostic.