3.2. BEAMST Command Sets

BEAMST data is grouped into command sets according to the requirements of each type of code check. Each command set consists of a header command for the code check, the commands applicable to the check and an END command to terminate the set. It is permissible to run several different code checks by appending the command sets in a single BEAMST datafile. It should be noted however that if plot files are to be saved then command sets should not be appended.

The structure of a typical BEAMST datafile for multiple check types is shown below:

The header command for each command set consists of a keyword defining the design code, a second keyword (or sub-header) defining the particular requirements from the code and in some instances further keywords defining editions, amendments and check classes.

The preliminary data is the first block of the BEAMST data. It defines the memory size to be used, the project name, structure and component names, file names and options to be used. It also defines which files are to be saved for further processing.

The preliminary data must contain at least a JOB, STRUCTURE, ANSYS, and END command for Mechanical APDL analyses. Other commands should be used as appropriate.

The BEAMST command sets are summarized in the table below. The commands relevant to each command set are summarized in the tables that follow, the reference for each is also given in the table below.


Release 18.2 - © ANSYS, Inc. All rights reserved.