Linux#

The Linux distributions can be downloaded from www.zset-software.com. There may be more than one incremental release available for download. Under normal circumstances, the latest version should be chosen. For distributions recorded on CD-ROM, please contact your Z-set distributor.

The distribution supports multiple incremental releases installed in the same shared location, facilitating easy version switching. The program can also be run directly from a CD-ROM, allowing old version results to be re-run as-is.

This installation procedure applies to all Z-set versions released after version Z9.0.

Download Z-set distribution archive file (e.g. z915_Linux_64.tar.gz) in folder MyPath (e.g. usr/local/ for example) containing the Z-set distribution. This will create a MyPath\Z9.1 folder containing the Z-set distribution. While creating the folder for Z-set installation, ensure that its name has NO blank spaces.
Once all the executable files are installed the user can set the environment variables. The user can either set the environment variable in his .cshrc or .bashrc file (depending on the shell script used) or can set it directly typing the following commands in terminal:
- for sh or bash shells:
```
export Z7PATH=MyPath/Z9.1
. $Z7PATH/lib/Z7_profile
```
- for csh or tcsh shells:
```
setenv Z7PATH MyPath/Z9.1
source $Z7PATH/lib/Z7_cshrc
```
At this point you should be able to test the executable files. Run for example:
```
Zrun -H
Zmaster
```

Initiate a license file request: the floating and centralized license management is available with many powerful features. The “classical” Zebulon node-locked licensing is also available.

Node-locked license: To get a license, launch the command:

Zserver -id

and send via email the obtained information to support@zset-software.com.

The user has two choices for the location where the encoded license key obtained from Z-set support team can be placed:

The standard path $Z7PATH/lib .
User defined path: this choice is preferable to avoid moving the license file each time when you download a new version of Z-set. With this choice, a system variable Z7LICENSE has to be set, pointing to the complete file path of the license file.

When executing the Z-set programs, the system will initially look for the license file specified by the environment variable Z7LICENSE, and then in the directory $Z7PATH/lib/*.zlic.

If there are problems with the license, one can test it with the following command:

Zrun -test_license

By default this command checks out the fem module license. Other license tokens can be checked out by giving the package name after the test switch such as

Zrun -test_license zbbhpc

for Z-mat HPC. Here is the list of available license tokens:

fem	Finite element module
m	Zmesh module
G	Graphical interface Zmaster
o	Zopt module (optimization)
S	Zsim module (simulation)
pp	Post-Processing
zbbhpc	Z-mat HPC
PP	Parallel processing
glue	glue subdomains’ results files after a parallel computation

Floating license: Starting from Z8.3.5 version the floating license system does not require license file on all client machines. In order to be issued a license, the license server should be used to get host information. Kindly open a command prompt, launch the command Zserver -id, and send that data in its entirety to support@zset-software.com.

Using this Hostname and Hostid Transvalor S.A. will issue a license for the floating license server. Now if the client machines want an access to the license file they will have to specify the Z7LICENSE path as a hostname or IP address, followed by the server port number:
- IP address:
```
Z7LICENSE xxx.xxx.x.xx:yyyy
```
  where xxx.xxx.x.xx is the IP address, and yyyy is the port number.
- Hostname:
```
Z7LICENSE Hostname:yyyy
```
By default, the license file is encoded using the port number 3490. If this port is not available or cannot be opened for listening, please notify our team so that the license file can be encoded accordingly. To ensure that other machines on the network can recognize the Hostname of your license server, it must be accessible through DNS or other name resolution methods. In some network configurations, combining the Hostname with a DNS suffix may be necessary to create a fully qualified domain name (FQDN). The Hostname resolution can be tested by attempting to ping the the IP address or the Hostname using the command
```
ping xxx.xxx.x.xx
```
or
```
ping Hostname
```
Please feel free to call your Z-set distributor if there are any difficulties.

The license file will be sent by e-mail and should be stored to any place on the license server machine. Next the license server must be started, for which we suggest the following command (c-shell syntax):
```
Zserver &
```
A more complete command can be used (see Zserver)
```
Zserver -p /path/to/license/file -l /path/to/log/file.log &
```
This command can be placed in one of the system rc scripts so that the license server will be started each time the system restarts. The connection with the server can be verified with the command:
```
Zrun -test_license
```
This command defaults to checking out the fem module. Other license tokens can be selected by giving the package name after the switch:
```
Zrun -test_license zbbhpc
```

Documentation and Test Files The documentation set is always supplied in the directory $Z7PATH/HANDBOOK in the form of indexed PDF files. All available manuals can be listed with the following command:
```
Zman -h
```
A large number of input files and example problems are shipped with the software in the TESTS directory. We do recommend that these tests be used together with User Manuals because they provide an excellent base for creating input files. Also these files are frequently referenced from the technical support.
Run a Z-mat problem from the test directory. If you are using a Z-mat platform with another solver (Abaqus, Ansys, Marc, Samcef, Morfeo, Aster, Adventure cluster, LS-Dyna, …)
1. For Z-mat with ABAQUS make sure that the environment variables are set and type the following:
```
cd $Z7PATH/TESTS/Z-mat/umat_v61/
Zmat -fg doghri
Zrun -pp doghri.pst
Zodb doghri.odb
```
1. For Z-mat with ANSYS make sure that the environment variables are set and type the following:
```
cd $Z7PATH/TESTS/Zansys/INP
Zansys doghri_ansys
Zrun -pp doghri_ansys.pst
Zmaster doghri_ansys.rst
```
Setup for User projects With every distribution there is a “template” user project from which one can get the latest appropriate building setup. This can be found at $Z7PATH/User-project . Normally, if all the above steps have been filled out, and the user has the appropriate C++ compiler, the user project can be compiled right away.
```
cd $Z7PATH/User-project
Zsetup
Zmake
```
Whenever a file is added or removed from the source directories, execute Zsetup to regenerate the makefiles. If compilation issues arise, it might be necessary to adjust the compiler switches for your site. Additionally, detailed instructions on testing user plugins and more can be found in the readme file within $Z7PATH/User-project.

Zebulon and Z-mat commands will search for user plugins (shared libraries .so) in the following paths, in this order:
- $Z7PATH/PUBLIC/lib-$Z7MACHINE
- $ZEBU_PATH
- Current working directory ./
$ZEBU_PATH is a user-defined environment variable that specifies the directory where user plugins are located. Users can also create symbolic links to these shared libraries in the simulations directory (or in $Z7PATH/PUBLIC/lib-$Z7MACHINE) to avoid the need to copy .so files after each modification.
Note

While the previous methods of loading plugins are still supported, it is currently recommended to make an entry in the user ~/.zsetrc file such as:
```
Solver.PluginPath /home/work/project1:/home/users/shared_projects
```
Note

The user must set up the proper environment variables before running external FE solver jobs, such as ABAQUS or ANSYS. These environment variables link Z-mat with the respective software. For instructions on setting up the proper environment variables, please refer to the respective script sections.