
Products: Abaqus/Standard Abaqus/Explicit

Abaqus uses the FORTRAN unit numbers outlined in the table below. Unless noted otherwise, you should not try to write to these FORTRAN units from user subroutines.
For Abaqus/Standard, you should specify unit numbers 15–18 or unit numbers greater than 100 .
For Abaqus/Explicit, specify units 16–18 or unit numbers greater than 100 ending in 5 to 9, e.g. 105, 268, etc. You cannot write to the.sta file.

| Code | Unit Number | Description |
|---|---|---|
| Abaqus/Standard | 1 | Internal database |
| 2 | Solver file | |
| 6 | Printed output (.dat) file (You can write output to this file.) | |
| 7 | Message (.msg) file (You can write output to this file.) | |
| 8 | Results (.fil) file | |
| 10 | Internal database | |
| 12 | Restart (.res) file | |
| 19–30 | Internal databases (scratch files). Unit numbers 21 and 22 are always written to disk. | |
| 73 | Text file containing meshed beam cross-section properties (.bsp) |
| Code | Unit Number | Description |
|---|---|---|
| Abaqus/Explicit | 6 | Printed output (.log) . |
| 12 | Restart (.res) file | |
| 13 | Old restart (.res) file, if applicable | |
| 15 | Analysis Preprocessor (.dat or .pre) file | |
| 23 | Communications (.023) file | |
| 60 | Global package (.pac) file | |
| 61 | Global state (.abq) file | |
| 62 | Temporary file | |
| 63 | Global selected results (.sel) file | |
| 64 | Message (.msg) file | |
| 65 | Output database (.odb) file | |
| 67 | Old package (.pac) file, if import from Abaqus/Explicit | |
| 68 | Old state (.abq) file, if import from Abaqus/Explicit | |
| 69 | Internal database; temporary file | |
| If domain-parallel | 70 | Local package (.pac.1) file for CPU #1 |
| 71 | Local state (.abq.1) file for CPU #1 | |
| 73 | Local selected results (.sel.1) file for CPU #1 | |
| 80 | Local package (.pac.2) file for CPU #2 | |
| 81 | Local state (.abq.2) file for CPU #2 | |
| 83 | Local selected results (.sel.2) file for CPU #2 | |
| ... | Add three files, incrementing units by 10, for each additional CPU |