Our organization has recently upgraded from Abaqus 2020HF9 to Abaqus 2024HF7. As a result, users now have ODB files generated from multiple Abaqus versions, and we are working towards making our internal tools compatible across these versions.
As part of this, we are considering the following approach:
- Dynamically execute the
abaqus odbreportbatch command. - Identify which Abaqus version is able to open a given ODB.
- Based on that, determine the appropriate Abaqus executable path for further processing.
However, we have a few concerns regarding the use of the odbreport command:
- Does executing
abaqus odbreportconsume an Abaqus license token? - If it does consume a license, how long does it typically take for the license to be released after execution?
- Is its behavior similar to
abaqus python, which does not consume a license?
Since this command may need to be executed multiple times to identify the compatible version for different ODBs, understanding its licensing impact is critical for our implementation.
