Making User-Defined Executables and Subroutines

This option is used to create a user-supplied postprocessing program. The value of the option specifies the name of the executable created by this procedure. It is also used as the default source file name.

If no option is given on the command line, you will be prompted for this value.

This option is used to create user subroutine object files and shared libraries. The value of the option specifies the name of the user subroutine source file to be compiled and linked. The resulting object and shared library files are placed in the directory given by the command line directory option. If the directory option is not used, the files are placed in the current working directory.

The object file or files created have a suffix indicating if the user subroutine is for Abaqus/Standard or Abaqus/Explicit. The Abaqus/Standard object file suffix is —std. Abaqus/Explicit has single and double precision object files; the object file suffixes are —xpl and —xplD. The Abaqus/Standard user subroutine shared library that is created is called standardU, and the Abaqus/Explicit shared libraries are called explicitU and explicitU-D. If the directory option is used and it contains object files with the appropriate suffix for the shared library that is being created, those files are linked to the shared library.

This option is valid only when used in conjunction with the job option. It is used to specify the name of the source or object file containing your program if it is different from job-name. If a file extension is not provided, the option value with a Fortran source file extension is sought. If a file by this name is not found, the option value with an object file extension is sought.

This option is valid only when used in conjunction with the library option. It is used to specify the absolute path of the destination of the user subroutine object and shared library files that will be created by the procedure. It is also used to specify the location of additional object files that are to be linked to the shared library or libraries being created. If the option is omitted, the files created by the procedure are placed in the current working directory.

This option is valid only when used in conjunction with the job option. It is used to specify the type of object file, either Fortran, C, or C++, given by the job or user option.

This option is valid only when used in conjunction with the library option. It is used to create Abaqus user subroutines in individual dynamic link libraries or shared objects. These libraries contain any utility routines included in the user subroutine. The library naming conventions are user_subroutine_name_usub.dll and user_subroutine_name_usub.so.

To direct Abaqus to use these user subroutines during input file execution, you must specify the uniquelibs option in the abaqus execution procedure (see Abaqus/Standard and Abaqus/Explicit Execution).

The use of global data between user subroutines via common blocks usage in Fortran routines is not allowed. If encountered, Abaqus issues a warning during the build process. To ensure the sharing of global data transfer among user subroutines, you must declare DLLExport and DLLImport statements accordingly.