MSC Nastran Utilities Guide

MSC Nastran 2020

Service Pack 1

Utilities Guide
Corporate Europe, Middle East, Africa
MSC Software Corporation MSC Software GmbH
4675 MacArthur Court, Suite 900 Am Moosfeld 13
Newport Beach, CA 92660 81829 Munich, Germany
Telephone: (714) 540-8900 Telephone: (49) 89 431 98 70
Toll Free Number: 1 855 672 7638 Email: [email protected]
Email: [email protected]

Japan Asia-Pacific
MSC Software Japan Ltd. MSC Software (S) Pte. Ltd.
Shinjuku First West 8F 100 Beach Road
23-7 Nishi Shinjuku #16-05 Shaw Tower
1-Chome, Shinjuku-Ku Singapore 189702
Tokyo 160-0023, JAPAN Telephone: 65-6272-0082
Telephone: (81) (3)-6911-1200 Email: [email protected]
Email: [email protected]

Worldwide Web
www.mscsoftware.com

Support
http://www.mscsoftware.com/Contents/Services/Technical-Support/Contact-Technical-Support.aspx

Disclaimer
MSC Software Corporation reserves the right to make changes in specifications and other information contained in this document
without prior notice.
The concepts, methods, and examples presented in this text are for illustrative and educational purposes only, and are not
intended to be exhaustive or to apply to any particular engineering problem or design. MSC Software Corporation assumes no
liability or responsibility to any person or company for direct or indirect damages resulting from the use of any information contained
herein.
User Documentation: Copyright 2020 MSC Software Corporation. Printed in U.S.A. All Rights Reserved.
This notice shall be marked on any reproduction of this documentation, in whole or in part. Any reproduction or distribution of this
document, in whole or in part, without the prior written consent of MSC Software Corporation is prohibited.
This software may contain certain third-party software that is protected by copyright and licensed from MSC Software suppliers.
Additional terms and conditions and/or notices may apply for certain third party software. Such additional third party software terms
and conditions and/or notices may be set forth in documentation and/or at http://www.mscsoftware.com/thirdpartysoftware (or successor
website designated by MSC from time to time).
PCGLSS 8.0, Copyright © 1992-2016, Computational Applications and System Integration Inc. All rights reserved. PCGLSS 8.0 is
licensed from Computational Applications and System Integration Inc.
MSC, Dytran, Marc, MSC Nastran, Patran, the MSC Software corporate logo, e-Xstream, Digimat, and Simulating Reality are
trademarks or registered trademarks of the MSC Software Corporation and/or its subsidiaries in the United States and/or other
countries. Hexagon and the Hexagon logo are trademarks or registered trademarks of Hexagon AB and/or its subsidiaries.
NASTRAN is a registered trademark of NASA. FLEXlm and FlexNet Publisher are trademarks or registered trademarks of Flexera
Software. All other trademarks are the property of their respective owners.
Use, duplicate, or disclosure by the U.S. Government is subjected to restrictions as set forth in FAR 12.212 (Commercial Computer
Software) and DFARS 227.7202 (Commercial Computer Software and Commercial Computer Software Documentation), as
applicable.
U.S. Patent 9,361,413
July 24, 2020
NA:V2020:Z:Z:Z:DC-UTIL-PDF
Documentation Feedback
At MSC Software, we strive to produce the highest quality documentation and welcome your feedback.
If you have comments or suggestions about our documentation, write to us at: documentation-
[email protected].
Please include the following information with your feedback:
 Document name
 Release/Version number
 Chapter/Section name
 Topic title (for Online Help)
 Brief description of the content (for example, incomplete/incorrect information, grammatical
errors, information that requires clarification or more details and so on).
 Your suggestions for correcting/improving documentation
You may also provide your feedback about MSC Software documentation by taking a short 5-minute
survey at: http://msc-documentation.questionpro.com.

Note: The above mentioned e-mail address is only for providing documentation specific
feedback. If you have any technical problems, issues, or queries, please contact Technical
Support.
 Contents
MSC Nastran 2020 Utilities Guide

Contents

Preface
List of MSC Nastran Books . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Technical Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Training and Internet Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

1 Using the Utility Programs

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
Key for Readers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
Definitions Used in this document. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
ABQ2NAS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Abaqus translator command. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Supported entities and the map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
Important known limitations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
An Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
ESTIMATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
F04REPRT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
MSCACT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
MSCPLOTPS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
MSGCMP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
MultiOpt . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
NEUTRL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
OP4UTIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
PLOTPS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
RCOUT2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Building the Utilities Delivered in Source Form . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
MSC Fatigue Utilities for Nastran Embedded Fatigue. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

Main Index
 6 MSC Nastran 2020 Utilities Guide

2 Building and Using the Sample Programs

Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Building and Using BEAMSERV . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Building and Using DDLPRT. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Building and Using DDLQRY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Building and Using DEMO1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Building and Using DEMO2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Building and Using DR3SERV . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Building and Using MATTST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Building and Using SMPLR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
Building and Using a Spline Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
Spline Server Source Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Building and Using TABTST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Beam Server Source Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
DRESP3 Server Source Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
MSC.Access Source Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

Main Index
 MSC Nastran Implicit Nonlinear (SOL 600) User’s GuideMSC Nastran 2019 Feature Pack
1 Utilities Guide
Preface

Preface


List of MSC Nastran Books

Technical Support

Training and Internet Resources

Main Index
 8 MSC Nastran 2020 Utilities Guide

List of MSC Nastran Books

A list of some of the MSC Nastran documents is as follows:

Installation and Release Guides

 Installation and Operations Guide
 Release Guide
Reference Guides
 Quick Reference Guide
 DMAP Programmer’s Guide
 Reference Guide
 Utilities Guide
Demonstration Guides
 Linear Analysis
 Implicit Nonlinear (SOL 400)
 Explicit Nonlinear (SOL 700)
User’s Guides
 Getting Started
 Linear Static Analysis
 Dynamic Analysis
 Embedded Fatigue
 Embedded Vibration Fatigue
 Thermal Analysis
 Superelements and Modules
 Design Sensitivity and Optimization
 Rotordynamics
 Implicit Nonlinear (SOL 400)
 Explicit Nonlinear (SOL 700)
 Aeroelastic Analysis
 User Defined Services
 Non Linear (SOL 400)
 High Performance Computing
 DEMATD

Main Index
 MSC Nastran 2020 Utilities Guide 9
Preface

You may find any of these documents from MSC Software at:
http://simcompanion.mscsoftware.com/infocenter/index?page=home

Technical Support
For technical support phone numbers and contact information, please visit:
http://www.mscsoftware.com/Contents/Services/Technical-Support/Contact-Technical-Support.aspx
Support Center (http://simcompanion.mscsoftware.com)

The SimCompanion link above gives you access to the wealth of resources for MSC Software products. Here
you will find product and support contact information, product documentations, knowledge base articles,
product error list, knowledge base articles and SimAcademy Webinars. It is a searchable database which
allows you to find articles relevant to your inquiry. Valid MSC customer entitlement and login is required to
access the database and documents. It is a single sign-on that gives you access to product documentation for
complete list of products from MSC Software, allows you to manage your support cases, and participate in
our discussion forums.

Training and Internet Resources

MSC Software (www.mscsoftware.com)

MSC Software corporate site with information on the latest events, products and services for the
CAD/CAE/CAM marketplace.
http://simcompanion.mscsoftware.com

The SimCompanion link above gives you access to the wealth of resources for MSC Software products. Here
you will find product and support contact information, product documentations, knowledge base articles,
product error list, knowledge base articles and SimAcademy Webinars. It is a searchable database which
allows you to find articles relevant to your inquiry. Valid MSC customer entitlement and login is required to
access the database and documents. It is a single sign-on that gives you access to product documentation for
complete list of products from MSC Software, allows you to manage your support cases, and participate in
our discussion forums.
http://www.mscsoftware.com/msc-training

The MSC Training link above will point you to schedule and description of MSC Seminars. Following
courses are recommended for beginning MSC Nastran users.
NAS101A - Linear Static and Normal Modes Analysis using MSC Nastran

This course serves as an introduction to finite element analysis. It includes discussion of basic features
available in MSC Nastran for solving structural engineering problems. In this course, all finite element
models will be created and edited using a text editor, not a graphical pre-processor. Proper data structure of
the MSC Nastran input file is covered. At the conclusion of seminar, the student will be familiar with
fundamental usage of MSC Nastran.

Main Index
 10 MSC Nastran 2020 Utilities Guide

NAS101B - Advanced Linear Analysis using MSC Nastran

This course is a continuation of NAS101A - Linear Static and Normal Modes Analysis using MSC Nastran.
In this class, you will learn: Theory of buckling analysis and how to perform a buckling analysis About rigid
elements - MPC, RBAR,RBE2, and RBE3 Modeling with interface element CINTC and connectors
Lamination theory and composite materials MSC Nastran composite theory Failure theories Linear contact
and permanent glued contact Different model checks Modeling tips and tricks
NAS120 - Linear Static Analysis using MSC Nastran and Patran

This seminar introduces basic finite element analysis techniques for linear static, normal modes, and buckling
analysis of structures using MSC Nastran and Patran. MSC Nastran data structure, the element library,
modeling practices, model validation, and guidelines for efficient solutions are discussed and illustrated with
examples and workshops. Patran will be an integral part of the examples and workshops and will be used to
generate and verify illustrative MSC Nastran models, manage analysis submission requests, and visualize
results. This seminar provides the foundation required for intermediate and advanced MSC Nastran
applications.

Main Index
 Chapter 1: Using the Utility Programs
MSC Nastran 2020 Utilities Guide

1 Using the Utility Programs


Overview

ABQ2NAS

ESTIMATE

F04REPRT

MSCACT

MSCPLOTPS

MSGCMP

MultiOpt

NEUTRL
 OP4UTIL

PLOTPS

RCOUT2

Building the Utilities Delivered in Source Form

MSC Fatigue Utilities for Nastran Embedded Fatigue

Main Index
 2 MSC Nastran 2020 Utilities Guide
Overview

Overview

Key for Readers

The IOG uses certain stylistic conventions to denote user action, to emphasize particular aspects of a
MSC Nastran run, or to signal other differences within the text.

Italics Represent user-specified variables.

Example: The system RC file is install_dir/conf/nast20200rc.
Courier font Indicates system input or output.
Example: $ install_dir/bin/msc20200
Quote marks Distinguish words or phrases such as lowercase keywords, commands, variables,
Dbsets or file suffixes from regular text.
Example: If “out” is not specified, MSC Nastran saves the output files using
the basename of the input data file as a prefix.

Definitions Used in this document

The IOG uses certain definitions to denote installation directories, and product versions of MSC Nastran.

install_dir The full path to the directory used in the installation

Example: The system RC file is install_dir/conf/nast20200rc.
prod_ver The Product and Version of MSC Nastran
Example: For MSC Nastran 2020

prod_ver=nast20200
ver_num The version number. For MSC Nastran 2020, this is 20200.
util_ver The version number used for building utilities.
Example: For MSC Nastran 2020

util_ver=msc20200
msc_arch The architecture of the platform.
Example: win64i8 for Windows 64 i8 version
Example: linux64i8 for Linux 64 i8 version

Main Index
 CHAPTER 1 3
Using the Utility Programs

This chapter describes how to use the various MSC Nastran utility programs. The utility programs are part
of the standard MSC Nastran delivery.

Table 1-1 Utility Program Functions

Utility Function
ABQ2NAS Abaqus to Nastran translator
ESTIMATE Estimates system requirements of an MSC Nastran job and suggests performance
improvements.
F04REPRT Perl script to summarize or compare .f04 files.
MSCACT Accumulates and summarizes MSC Nastran accounting data.
MSGCMP Compiles the message catalog.
MultiOpt MultiOpt supports Multiple Model Optimization (MMO) and Global
Optimization (GO).
NEUTRL Converts MSC Nastran plot files to PostScript or neutral format.
MSCPLOTPS MSCPLOTPS is very similar to PLOTPS in that it reads plotting commands from
a single MSC Nastran binary- or neutral-format plot file. The primary difference is
that MSCPLOTPS automatically determines the format of the input file.
OP4UTIL OP4UTIL may be used to validate, copy or reformat binary files created using the
MSC Nastran OUTPUT4 module.
PLOTPS PLOTPS reads plotting commands from a single MSC Nastran binary- or
neutral-format plot file and produces a file that can be printed on a PostScript
device.
RCOUT2 Converts neutral-format OUTPUT2 files to binary format.

Sections ABQ2NAS, 3 through RCOUT2, 38 describe each utility (in alphabetical order), and present applicable
keywords and examples. Building the Utilities Delivered in Source Form, 38 contains instructions on how to build
the source code utilities.
 The utilities trans, receive, xmonast, and xnastran are no longer supported. If those utilities are
needed, please see MSC Nastran 2014.

ABQ2NAS

Abaqus translator command

MSC Nastran has a utility to convert Abaqus input files to MSC Nastran input files, the translator is a
standard executable with name abq2nas.
The format of the “abq2nas” command is:
util_ver abq2nas an_abaqus.inp an_nastran.dat <command line options>

Main Index
 4 MSC Nastran 2020 Utilities Guide
ABQ2NAS

The command will translate “an_abaqus.inp” to a MSC Nastran input file with name of “an_nastran.dat”.
Here abq2nas is the utility executable. The translation processing information including warnings and errors
will be written to a log file with name “an_nastran.abq2nas” file.
There are a few command line options, three are direct text inputs for step, case control and bulk data
sections. Below are examples of the command line options:
abq2nas aa.inp bb.bdf CASE=“NLOPRM NLDBG=NRDBG”
abq2nas aa.inp bb.bdf STEP=“AUTOSPC(RESIDUAL,PUNCH)=YES”
abq2nas aa.inp bb.bdf BULK=“NLMOPTS,LRGS,1;,,SPROPMAP,2
abq2nas aa.inp bb.bdf tosurf=yes or no(default)
if tosurf is yes, *SURFACE keywords for contact to MSC Nastran BCSURF entries if type is ELEMENT or
BCGRID entries if type is NODE.
Multiple lines can be expressed by using semicolons “;”, it is user’s responsibility to provide a correct MSC
Nastran entry, the translator just takes it as is.
Another two options are mergecontact and tosurf. mergecontact=yes/no controls contact merging, which
will be explained later.
abq2nas aa.inp bb.bdf mergecontact=yes
tosurf=yes/no controls if translate *SURFACE keywords for contact to MSC Nastran BCSURF or BCGRID
entries.
abq2nas aa.inp bb.bdf tosurf=yes
if tosurf is yes, *SURFACE keywords for contact to MSC Nastran BCSURF entries if type is ELEMENT or
BCGRID entries if type is NODE.

Supported entities and the map

Below are the supported entities and the map of Abaqus to MSC Nastran.
Notice here “activate hyperelements formulation” is achieved by adding the card below into the MSC Nastran
file:
NLMOPTS LRGSTRN 2

Abaqus MSC Nastran

Element
Element
Plane Strain
CPE3 CTRIA3, PLPANE, PSHLN2
CPE3H CTRIA3, PLPANE, PSHLN2
CPE4 CQUAD4, PLPLANE + PSHLN2
CPE4H CQUAD4, PLPLANE + PSHLN2, activate hyperelasticity formulation
CPE4I CQUAD4, PLPLANE + PSHLN2

Main Index
 CHAPTER 1 5
Using the Utility Programs

Abaqus MSC Nastran

Element
CPE4IH CQUAD4, PLPLANE + PSHLN2, activate hyperelasticity formulation
CPE4R CQUAD4, PLPLANE + PSHLN2
CPE4RH CQUAD4, PLPLANE + PSHLN2, activate hyperelasticity formulation
CPE6 CTRIA6, PLPLANE + PSHLN2
CPE6H CTRIA6, PLPLANE + PSHLN2, activate hyperelasticity formulation
CPE6M CTRIA6, PLPLANE + PSHLN2
CPE6MH CTRIA6, PLPLANE + PSHLN2, activate hyperelasticity formulation
CPE8 CQUAD8, PLPLANE + PSHLN2
CPE8H CQUAD8, PLPLANE + PSHLN2, activate hyperelasticity formulation
CPE8R CQUAD8, PLPLANE + PSHLN2
CPE8RH CQUAD8, PLPLANE + PSHLN2, activate hyperelasticity formulation
Plane Stress
CPS3 CTRIA3, PLPLANE + PSHLN2
CPS4 CQUAD4, PLPLANE + PSHLN2
CPS4I CTRIA3, PLPLANE + PSHLN2
CPS4R CTRIA3, PLPLANE + PSHLN2
CPS6 CTRIA6, PLPLANE + PSHLN2
CPS6M CTRIA6, PLPLANE + PSHLN2
CPS8 CQUAD8, PLPLANE + PSHLN2
CPS8R CQUAD8, PLPLANE + PSHLN2
Generalized Plane Strain
CPEG3 CTRIA3, PLPLANE + PSHLN2
CPEG3H CTRIA3, PLPLANE + PSHLN2
CPEG4 CQUAD4, PLPLANE + PSHLN2
CPEG4H CQUAD4, PLPLANE + PSHLN2, activate hyperelasticity formulation
CPEG4I CQUAD4, PLPLANE + PSHLN2
CPEG4IH CQUAD4, PLPLANE + PSHLN2, activate hyperelasticity formulation
CPEG4R CQUAD4, PLPLANE + PSHLN2
CPEG4RH CQUAD4, PLPLANE + PSHLN2, activate hyperelasticity formulation
CPEG6 CTRIA6, PLPLANE + PSHLN2
CPEG6H CTRIA6, PLPLANE + PSHLN2, activate hyperelasticity formulation

Main Index
 6 MSC Nastran 2020 Utilities Guide
ABQ2NAS

Abaqus MSC Nastran

Element
CPEG6M CTRIA6, PLPLANE + PSHLN2
CPEG6MH CTRIA6, PLPLANE + PSHLN2, activate hyperelasticity formulation
CPEG8 CQUAD, PLPLANE + PSHLN2
CPEG8H CQUAD, PLPLANE + PSHLN2, activate hyperelasticity formulation
CPEG8R CQUAD, PLPLANE + PSHLN2
CPEG8RH CQUAD, PLPLANE + PSHLN2, activate hyperelasticity formulation
Axisymmetric, Stress/displacement elements without twist
CAX3 CTRIAX, PLPLANE + PSHLN2
CAX3H CTRIAX, PLPLANE + PSHLN2, activate hyperelasticity formulation
CAX4 CQUADX, PLPLANE + PSHLN2
CAX4H CQUADX, PLPLANE + PSHLN2, activate hyperelasticity formulation
CAX4I CQUADX, PLPLANE + PSHLN2
CAX4IH CQUADX, PLPLANE + PSHLN2, activate hyperelasticity formulation
CAX4R CTRIAX, PLPLANE + PSHLN2
CAX4RH CQUADX, PLPLANE + PSHLN2, activate hyperelasticity formulation
CAX6 CTRIAX, PLPLANE + PSHLN2
CAX6H CTRIAX, PLPLANE + PSHLN2, activate hyperelasticity formulation
CAX6M CTRIAX, PLPLANE + PSHLN2
CAX8 CQUADX, PLPLANE + PSHLN2
CAX8H CQUADX, PLPLANE + PSHLN2, activate hyperelasticity formulation
CAX8R CQUADX, PLPLANE + PSHLN2
CAX8RH CQUADX, PLPLANE + PSHLN2, activate hyperelasticity formulation
Axisymmetric, Stress/displacement elements with twist
CGAX3 CTRIAX, PLPLANE + PSHLN2
CGAX3H CTRIAX, PLPLANE + PSHLN2, activate hyperelasticity formulation
CGAX4 CQUADX, PLPLANE + PSHLN2
CGAX4H CQUADX, PLPLANE + PSHLN2, activate hyperelasticity formulation
CGAX4R CQUADX, PLPLANE + PSHLN2
CGAX4RH CQUADX, PLPLANE + PSHLN2, activate hyperelasticity formulation
CGAX6 CTRIAX, PLPLANE + PSHLN2
CGAX6H CQUADX, PLPLANE + PSHLN2, activate hyperelasticity formulation
CGAX6M CTRIAX, PLPLANE + PSHLN2

Main Index
 CHAPTER 1 7
Using the Utility Programs

Abaqus MSC Nastran

Element
CGAX6MH CTRIAX, PLPLANE + PSHLN2, activate hyperelasticity formulation
CGAX8 CTRIAX, PLPLANE + PSHLN2
CGAX8H CQUADX, PLPLANE + PSHLN2
CGAX8R CQUADX, PLPLANE + PSHLN2, activate hyperelasticity formulation
CGAX8RH CQUADX, PLPLANE + PSHLN2
3D Stress/displacement elements
C3D4 CTETRA, PSOLID + PSLDN1
C3D4H CTETRA, PSOLID + PSLDN1
C3D6 CPENTA, PSOLID + PSLDN1
C3D6H CPENTA, PSOLID + PSLDN1, activate hyperelasticity formulation
C3D8 CHEXA, PSOLID + PSLDN1
C3D8H CHEXA, PSOLID + PSLDN1, activate hyperelasticity formulation
C3D8I CHEXA, PSOLID + PSLDN1
C3D8IH CHEXA, PSOLID + PSLDN1, activate hyperelasticity formulation
C3D8R CHEXA, PSOLID + PSLDN1
C3D8RH CHEXA, PSOLID + PSLDN1, activate hyperelasticity formulation
C3D10 CTETRA, PSOLID + PSLDN1
C3D10H CTETRA, PSOLID + PSLDN1, activate hyperelasticity formulation
C3D10I CTETRA, PSOLID + PSLDN1
C3D10M CTETRA, PSOLID + PSLDN1
C3D10MH CTETRA, PSOLID + PSLDN1, activate hyperelasticity formulation
C3D15 CPENTA, PSOLID + PSLDN1
C3D15H CPENTA, PSOLID + PSLDN1, activate hyperelasticity formulation
C3D20 CHEXA, PSOLID + PSLDN1
C3D20H CHEXA, PSOLID + PSLDN1, activate hyperelasticity formulation
C3D20R CHEXA, PSOLID + PSLDN1
C3D20RH CHEXA, PSOLID + PSLDN1, activate hyperelasticity formulation
Membrane
M3D3 CTRIA3, PSHELL
M3D4 CQUAD4, PSHELL
M3D4R CQUAD4, PSHELL

Main Index
 8 MSC Nastran 2020 Utilities Guide
ABQ2NAS

Abaqus MSC Nastran

Element
M3D6 CTRIA6, PSHELL
M3D8 CQUAD8, PSHELL
M3D8R CQUAD8, PSHELL
M3D9 CQUAD8, PSHELL
M3D9R CQUAD8, PSHELL
2D truss
T2D2 CROD, PROD
T2D2H CROD, PROD/PRODN1
T2D3 CROD, PROD
T2D3H CROD, PROD/PRODN1
3D truss
T3D2 CROD, PROD
T3D2H CROD, PROD
T3D3 CROD, PROD
T3D3H CROD, PROD
Beam in plane
B21 CBEAM, PBEAM/PBEAML
B21H NA, but write out the same one as B21 with a warning
B22 CBEAM3, PBEAM/PBEAML
B22H NA, but write out the same one as B22 with a warning
B23 NA, but write out the same one as B21 with a warning
B23H NA, but write out the same one as B21 with a warning
Beam in 3D space
B31 CBEAM, PBEAM/PBEAML
B31H NA, but write out the same one as B31 with a warning
B32 CBEAM3, PBEAM/PBEAML
B32H NA, but write out the same one as B32 with a warning
B33 NA, but write out the same one as B31 with a warning
B33H NA, but write out the same one as B31 with a warning
Conventional shells
STRI3 CTRIA3, PSHELL

Main Index
 CHAPTER 1 9
Using the Utility Programs

Abaqus MSC Nastran

Element
S3 CTRIA3, PSHELL
S3R CTRIA3, PSHELL + PSHLN1
S3RS CTRIA3, PSHELL + PSHLN1
STRI65 CTRIA3, PSHELL
S4 CQUAD4, PSHELL
S4R CQUAD4, PSHELL + PSHLN1
S4RS CQUAD4/PSHELL + PSHLN1
S4RSW CQUAD4/PSHELL + PSHLN1
S4R5 CQUAD4/PSHELL + PSHLN1
S8R CQUAD8/PSHELL + PSHLN1
S8R5 CQUAD8/PSHELL + PSHLN1
Continuum shell(Solid shell)
SC8R CHEXA, PCOMPLS
Spring
SPRINGA CBUSH, PBUSH + PBUSHT
SPRING1 CELAS1, PELAS + PELAST
SPRING2 CBUSH, PBUSH + PBUSHT
Dashpot
DASHPOT1 CBUSH, PBUSH + PBUSHT
DASHPOT2 CBUSH, PBUSH + PBUSHT
DASHPOTG CBUSH, PBUSH + PBUSHT
Flexible joint
JOINTC CBUSH, PBUSH + PBUSHT
Distributing coupling
DCOUP2D RBE2/RBE3
DCOUP3D RBE2/RBE3
Gasket
GK3D8 CHEXA, PSOLID, MATG
GK3D8N CHEXA, PSOLID, MATG
Other geometry entities
*NGEN GRID

Main Index
 10 MSC Nastran 2020 Utilities Guide
ABQ2NAS

Abaqus MSC Nastran

Element
*NFILL GRID
*NCOPY GRID
*ELGEN Elements
*ASSEMBLY/*INSTAN offset ids of GRID and elements, *ELSET or *NSET with option
CE/*PART INSTANCE=part_name is available also
*SYSTEM CORD2R and write the cord2r id to CP field of related GRID
*ORENTATION CORD2R and write the cord2r id to CBUSH, COMN1, 2D elements,
shell elements and PSOLID
*TRANSFORM CORD2R and write the cord2r id to CD field of related GRID
Properties
*SOLID SECTION PSOLID
*SHELL SECTION PSHELL/PCOMP/PCOMPL/PCOMPLS
*BEAM SECTION PBEAM/PBEAML
*BEAM GENERAL PBEAML
SECTION
*GASKET SECTION MATG
Materials
*ELASTIC MAT1/MAT8/MATORT/MAT9
*DENSITY
*PLASTIC MATEP
*HYPERELASTIC MATHE
*VISCOELASTIC MATVE
*CREEP MATVP
Contact
*SURFACE BCBODY1,BSURF, BCNURB2, BCPATCH depending on *RIGID
BODY
*RIGID BODY BCNURB2 for analytical curves, a BCPACH for 3D model when the
elements used by a *SURFACE
*CONTACT PAIR BCONNECT
*SURFACE BCONPRP
INERACTION
*TIE Glue contact (BCONNECT)
Loads Boundaries

Main Index
 CHAPTER 1 11
Using the Utility Programs

Abaqus MSC Nastran

Element
*CLOAD FORCE/MOMENT
*TEMPERATUE TEMP
*INTIAL TEMP and TEMPERATURE(INIT) in case control
CONDITION
TYPE=TEMPERATUE
*DLOAD PLOAD4/PLOAD1
GRAV
RFORCE
PLOADX
*DSLOAD PLOAD4 for shell and solid, PLOAD1for beam elements
PLOADX
MPC, Coupling, etc
? *Kinematic Coupling RBE2
*Distributing Coupling RBE3
*Coupling + *Kinematic RBE2
*Coupling + *Distributing RBE3
*MPC Beam type RBAR
*Pre-tension BOLT
*Equation MPC
Analysis procedure
*STATIC, Perturbation ANALYSIS=STATIC
*STATIC, no perturbation ANALYSIS=NLSTATIC
*Frequency ANALYSIS=MODES

In the contact area, there is a strict limitation in MSC Nastran: one element can only be used by one contact
body. The translator is highly likely going to make an element belong to multiple bodies. To overcome this
issue, merging contact bodies that share common elements into one body is required. The command line
option mergecontact=yes/no controls this. the default is yes, no is only for debugging purposes.

Important known limitations

The following input syntax is not supported. This is not necessarily a complete list:
*AMPLITUDE
*BULK VISCOSITY
*CONTACT

Main Index
 12 MSC Nastran 2020 Utilities Guide
ABQ2NAS

*CONTACT INCLUSION
*CONTACT PAIR is not completely supported
*CONTACT PROPERTY ASSIGNMENT
*CYCLIC HARDENING
*DISTRIBUTION
*DLOAD - several parameters including PY are not supported
*DRUCKER PRAGER
*DRUCKER PRAGER HARDENING
*DSLOAD – several parameters including EDLD and BX are not
supported
*DYNAMIC
*FRAME SECTION, also B33 element is not supported
*HYPERELASTIC – parameter MODULI AND POLYNOMIAL
*INITIAL CONDITIONS type HARDENING
*INITIAL CONDITIONS type STRESS
*MOHR COULOMB
*MOHR COULOMB HARDENING
*MPC – type C BIQUAD and QUADRATIC are not supported
*NCOPY
*PLASTIC, DEPENDENCIES
*RBE - only 1D analytical surfaces and 2D R3D4, R3D3 elements can
be translated
*REBAR LAYER
*STEADY STATE DYNAMICS
*STEP – parameter UNSYMM
*SUBMODEL
*SURFACE BEHAVIOR
*SWELLING
*VISCO
BEH4 and BEH8 are not supported.
Generalized plane strain elements are translated into equivalent plane strain elements.

An Example
Here is an example based on chapter 4 of the MSC Nastran Demonstration Problems Manual (nug4), please
refer to this chapter for detailed information.
Download the Abaqus input file here:
http://www.mscsoftware.com/doc/nastran/mdug/input_files/abaqus_trans/nug_04_abaqus.zip
Use this command to translate it to a MSC Nastran file
msc20200 abq2nas nug_04_abaqus.inp nug_04_abaqus.bdf
Below is a side by side illustration to show how the data is translated. The left side shows contents of the
Abaqus input file and right side shows that of generated MSC Nastran input file.

Main Index
 CHAPTER 1 13
Using the Utility Programs

…. ….

*NODE BEGIN BULK

1, 250., 0. $ translated from keyword line 4

2, 249.846, 3.92388 GRID 1 250. 0.0 0.0

….. GRID 2 249.846 3.92388 0.0

…..

*ELEMENT, TYPE=C3D8R, ELSET=A3D_1_0_0 $ translated from type C3D8R, near line 3604

1, 41, 42, 81, 40, 900, 905, CHEXA 1 1 41 42 81 40 900 905

1100, 895 1100 895

2, 900, 905, 1100, 895, 901, 906, CHEXA 2 1 900 905 1100 895 901 906

1101, 896 1101 896

3, 901, 906, 1101, 896, 902, 907, 1102, 897

….

Main Index
 14 MSC Nastran 2020 Utilities Guide
ABQ2NAS

*SOLID SECTION, ELSET=A3D_1_0_0, MATERIAL=MAT1_1_0 $ translated from *SOLID SECTION near line 8874, element type is C3D8R

1., PSOLID 1 1

*SOLID SECTION, ELSET=A3D_2_0_0, MATERIAL=MAT1_2_0 $ translated from *SOLID SECTION near line 8879, element type is C3D8R

1., PSOLID 2 2

*MATERIAL, NAME=MAT1_1_0 $ Translated from a *MATERIAL near line 8884

*DENSITY MAT1 1 210000. 0.3 1.

1., …

*ELASTIC, TYPE=ISO

210000., 0.3

….

** Contact_1

** $ contact body from line 8904 , element face ids are ignored

*SURFACE, TYPE=ELEMENT, NAME=M_CONTACT_1_0 BCBODY1 1 3D DEFORM 1

2306, S6 BSURF 1 2306 2307 2310 2311….

2307, S6 $ translated from *CONTACT PAIR near line 9143

2310, S BCONECT 101 1 2 1

*CONTACT PAIR, INTERACTION=CONTACT_1_0, SMALL $ Translated from the *SURFACE INTERACTION near line 9145

S_CONTACT_1_0, M_CONTACT_1_0 BCONPRP 1 FRIC 0.1

*SURFACE INTERACTION, NAME=CONTACT_1_0 BCPARA 0 FTYPE 6

*FRICTION, SLIP TOLERANCE=0.02 BCTABL1 10000 101

0.1, BCTABL1 0 101

…. ….

*STEP, NC=10, NLGEOM $ from *STEP NLGEOM option

3-D Loaded Pin with Friction …. PARAM LGDISP 1

*STATIC $ translated from the *STEP near line 9152 and the *STATIC near line 9156

0.1, 1. NLSTEP 1 1.

ADAPT 0.1 10 10

…..

$ lbc from keyword line 9173:*BOUNDARY, OP=NEW

*BOUNDARY, OP=NEW SPC1 3 2 700

700, 2,, 0. SPC1 3 2 701

701, 2,, 0. ……

……. $ lbc from keyword line 10201:*CLOAD, OP=NEW

*CLOAD, OP=NEW FORCE 5 1004 1. 50000. 0.0 0.0

FORCE_1_0, 1, 50000

Notice that MSC Nastran 2020 does not give the same results as nug4 for the translated MSC Nastran input
file, you will need to make the changes below to obtain the same results:
$ translated from *CONTACT PAIR near line 9143

Main Index
 CHAPTER 1 15
Using the Utility Programs

BCONECT 101 1 2 1 ®(change to) BCONECT, 101, 3, 1, 2, 1

And add below line:
BCONPRG, 3, , ICOORD, 1, ISEARCH, 1
The modified file is included in the download zip file with name nug_04_abaqus_modified.dat.

ESTIMATE
ESTIMATE may be used to estimate the memory and disk requirements for MSC Nastran jobs and make
suggestions on improving the performance of these jobs. ESTIMATE will read the input data file and
estimate the job’s memory and disk requirements. The ESTIMATE program is most accurate in predicting
the requirements of static analyses that do not have excessive output requests. The memory requirements for
normal modes analyses using the Lanczos method are reasonably accurate; however, the disk requirements
are dependent upon the number of modes, this is a value that ESTIMATE cannot determine. Memory and
disk requirements for other solutions are less accurate.
The basic format of the “estimate” command is

util_ver estimate input_file [keywords]

where input_file is the name of the data file. If the file type of the input data file is “.dat”, it may be omitted
from the command line.
ESTIMATE processes keywords using the following precedence to resolve conflicts when keywords are
duplicated (with 1 representing the highest precedence):
1. The Bulk Data file.
2. The command line.
3. The nastran INI and RC files (if “nastrc=yes” is specified).
4. data-file-directory/.estimaterc on LINUX, or data-file-directory\estimate.rcf on Windows, where
data-file-directory is the directory containing the input data file.
5. $HOME/.estimaterc on LINUX, or %HOMEDRIVE%%HOMEPATH%\estimate.rcf file on
Windows.
6. estimate.ini in the directory containing the ESTIMATE executable.
Please be aware that the Bulk Data file can only contain statements that are accepted by MSC Nastran. The
following keywords will be recognized by ESTIMATE when they appear in the Bulk Data file on NASTRAN
statements:

buffpool, buffsize, real

Note: "buffsize=estimate" is NOT accepted on a NASTRAN statement.

Main Index
 16 MSC Nastran 2020 Utilities Guide
ESTIMATE

The following Case Control statements will be recognized by ESTIMATE when they appear in the bulk data
file:

adapt, method, mpc, sp

Note: If these statements appear multiple times, e.g., in subcases, only the first occurrence of each
case control statement will be recognized.

Similarly, the nastran INI and RC files can only accept keywords that are accepted by the nastran command.
The following nastran command keywords will be recognized by ESTIMATE when they appear in nastran
RC files if and only if "nastrc=yes" is also set:

bpool, buffsize, memory, real, realdelta, smemory, version

The full set of ESTIMATE utility keywords can ONLY appear on the ESTIMATE command line or in the
ESTIMATE RC files, e.g., ".estimaterc" on LINUX and "estimate.rcf" on Windows.

Keywords
adapt adapt=number Default: None
Selects an ADAPT set for adaptivity jobs if an ADAPT Case Control command is
not present or multiple ADAPT Case Control commands are present in the data file.
By default, ESTIMATE will choose the first ADAPT found.
bpool bpool=value Default: 150 (all others)
Same as MSC Nastran keyword, see bpool, 185. This keyword cannot appear in an
ESTIMATE RC file if “nastrc=yes” is specified.
buffsize buffsize=number Default: 8193
Same as MSC Nastran keyword, see buffsize, 186. This keyword cannot appear in an
ESTIMATE RC file if “nastrc=yes” is specified.
dballco dballco=value Default: 1
Allows you to scale DBALL estimates. This scale factor is applied before the
"dballmin" value, that provides a lower bound for DBALL estimates.
Example: util_ver estimate example dballco=2
This will double the DBALL disk estimate and then apply the "dballmin" lower
bound.
Example: util_ver estimate example dballco=0.5
This will halve the DBALL disk estimate. An estimate less than than the lower
bound specified by "dballmin" will be set to the lower bound.
dballmin dballmin=value Default: 1mb

Main Index
 CHAPTER 1 17
Using the Utility Programs

Allows you to define the lower bound for all DBALL estimates. This bound is
applied after the "dballco" value, that multiplies the actual estimate by a
"conservatism" factor.
Example: util_ver estimate example dballmin=2mb
This will set the minimum DBALL disk estimate to 2 MB.
dskco dskco=value Default: 1
Allows you to define a factor to scale total disk estimates. This scale factor is applied
before the "dskmin" value, that provides a lower bound for total disk estimates.
Example: util_ver estimate example dskco=2
This doubles the total disk estimate and then applies the "dskmin" lower bound.
Example: util_ver estimate example dskco=0.5
This will halve the total disk estimate. An estimate less than the lower bound
specified by "dskmin" will be set to the lower bound.
dskmin dskmin=value Default: 1mb
Allows you to define the lower bound for all total disk estimates. This bound is
applied after the "dskco" value, that multiplies the actual estimate by a
"conservatism" factor.
Example: util_ver estimate example dskmin=2mb
This will set the minimum total disk estimate to 2 MB.
enable The “enable” keyword can be used to explicitly enable rules. This may be useful to
enable a rule that was automatically suppressed when a value was assigned. For
example, the following command will now calculate the estimated memory
requirements for a job even though a value for memory was specified on the
command line:
Example: util_ver estimate example memory=5mb
enable=10
estimatedof estimatedof=yes,no Default: No
Indicates if the number of degrees of freedom are to be estimated. By default,
ESTIMATE will count the DOF. This process takes time, but it is generally more
accurate. Specifying “estimatedof=no” will result in a less accurate, but faster,
estimate of the DOF. The presence of any MESH entries in the Bulk Data will force
“estimatedof=yes”.
memco memco=number Default: 1.0
Allows you to specify a constant factor that is either more or less conservative than
the default.
Example: util_ver estimate example memco=2
This setting will double the memory estimate.
memmin memmin=value Default: 16mb

Main Index
 18 MSC Nastran 2020 Utilities Guide
ESTIMATE

Allows you to define the lower bound for all memory estimates. This bound is
applied after the "memco" value, that multiplies the actual estimate by a
"conservatism" factor.
Example: util_ver estimate example memmin=8mb
This will set the minimum memory estimate to 8 MB.
memory memory=size Default: 16mb
Same as MSC Nastran keyword, see memory, 202. This keyword cannot appear in
an ESTIMATE RC file if “nastrc=yes” is specified.
method method=number Default: None
Selects a METHOD for dynamics jobs if a METHOD Case Control command is
not present or multiple METHOD Case Control commands are present in the data
file. By default, ESTIMATE will choose the first METHOD found.

mode mode=keyword Default: suggest

Selects the program operating mode. Specifying “mode=estimate” will result in
memory and disk estimates only. Specifying “mode=suggest”, the default, will
estimate memory and disk requirements for the current job configuration, suggest
modifications to improve the performance, and provide estimates for the memory
and disk requirements of the suggested configuration. Specifying “mode=modify”
does all that “mode=suggest” does plus actually make the suggested changes to your
data file. See “out” to specify the new data file’s name and information on organizing
your input file.

Note: If “mode=modify” is specified, and ESTIMATE detects errors in the input file or encounters
valid Bulk Data that is not understood by ESTIMATE, the program will revert to
“mode=suggest”.

Example: util_ver estimate example

mode=estimate
The memory and disk requirements for the current job are displayed.
Example: util_ver estimate example
The memory and disk requirements for the current job, suggestions for improving
performance, and memory and disk requirements for the suggested configuration are
displayed.

Main Index
 CHAPTER 1 19
Using the Utility Programs

Example: util_ver estimate example

mode=modify
The memory and disk requirements for the current job, suggestions for improving
performance, and estimates of memory and disk requirements for the suggested
configuration are displayed. If, and only if, modifications to “example.dat” are
suggested, the original input file is versioned (given indices) and the revised data file
is written to “example.dat”.

mpc mpc=number Default: None

Selects an MPC if an MPC Case Control command is not present or multiple MPC
Case Control commands are present in the data file. By default, ESTIMATE will
choose the first MPC found.
nastrc nastrc=yes,no Default: Yes
The “nastrc” keyword allows you to select the type of RC file processing invoked by
the ESTIMATE utility. Setting “nastrc=yes”, the default, will process the standard
MSC Nastran RC files before the standard ESTIMATE RC files, i.e.,
$HOME/.estimaterc and “data-file-directory/.estimaterc” on LINUX, and
%HOMEDRIVE%%HOMEPATH\estimate.rcf and
“data-file-directory/estimate.rcf” on Windows, are processed. Setting “nastrc=no”
will only process the standard ESTIMATE RC files.
out out=pathname Default: input filename
Specifies the name of the output file if “mode=modify” is specified and
modifications of the data file are actually required. By default, the original file is
versioned (given indices) and the revised data file is written to the original input file’s
name. See Using Filenames and Logical Symbols, 60
Example: util_ver estimate example
mode=modify
If modifications to “example.dat” are suggested, the original input file is versioned
(given indices) and the revised data file is written to “example.dat”.
Example: util_ver estimate example
mode=modify \
out=modified
The revised data file is written to “modified”.

Main Index
 20 MSC Nastran 2020 Utilities Guide
ESTIMATE

Note: In order to minimize the amount of data duplicated between the original input file and the
modified file, MSC recommends that the Bulk Data that is not subject to modification by
ESTIMATE (i.e., all Bulk Data except PARAM and EIGRL entries) be placed in an
INCLUDE file.

An example of the recommended input file organization is:

NASTRAN statements
FMS statements
Executive
CEND
Case Control
BEGIN BULK
PARAM,...
$
EIGRL,...
$
INCLUDE file.bulk
$
ENDDATA

pause pause=keyword Default: No

Pause ESTIMATE before exiting to wait for the “Enter” or “Return” key to be
pressed. This can be useful when ESTIMATE is embedded within another program.
The values are “fatal”, “information”, “warning”, “yes”, and “no”. Setting “pause=yes”
will unconditionally wait; “pause=fatal” will only wait if a fatal message has been
issued by ESTIMATE; “pause=information” and “pause=warning” will similarly wait
only if an information or warning message has been issued. The default is
“pause=no”, i.e., do not wait when ESTIMATE ends.
real real=value Default: See text.
Same as MSC Nastran keyword, see real, 215. This keyword cannot appear in an
ESTIMATE RC file if “nastrc=yes” is specified.
realdelta realdelta=value Default: See text.
Same as MSC Nastran keyword, see realdelta, 215. This keyword cannot appear in an
ESTIMATE RC file if “nastrc=yes” is specified.

report report=keyword Default: Normal

Specifies the program’s report format. The “report=normal” format is intended to be
read by you. The “report=keyword” format is intended to be read by a program.
scr300co scr300co=value Default: 1
Allows you to define a factor to scale SCR300 estimates. This scale factor is applied
before the "scr300min" value, that provides a lower bound for SCR300 estimates.

Main Index
 CHAPTER 1 21
Using the Utility Programs

Example: util_ver estimate example

scr300co=2
This will double the SCR300 disk estimate and then apply the "scr300min" lower
bound.
Example: util_ver estimate example
scr300co=0.5
This will halve the SCR300 disk estimate. An estimate less than the lower bound
specified by "scr300min" will be set to the lower bound.
scr300min scr300min=value Default: 1mb
Allows you to define the lower bound for all SCR300 estimates. This bound is
applied after the "scr300co" value, that multiplies the actual estimate by a
"conservatism" factor.
Example: util_ver estimate example
scr300min=2mb
This will set the minimum SCR300 disk estimate to 2 MB.
scratchco scratchco=value Default: 1
Allows the user to define a factor to scale SCRATCH estimates. This scale factor is
applied before the "scratchmin" value, that provides a lower bound for SCRATCH
estimates.
Example: util_ver estimate example
scratchco=2
This will double the SCRATCH disk estimate and then apply the "scratchmin"
lower bound.
Example: util_ver estimate example
scratchco=0.5
This will halve the SCRATCH disk estimate. An estimate less than the lower bound
specified by "scratchmin" will be set to the lower bound.
scratchmin scratchmin=value Default: 1mb
Allows you to define the lower bound for all SCRATCH estimates. This bound is
applied after the "scratchco" value, that multiplies the actual estimate by a
"conservatism" factor.
Example: util_ver estimate example
scratchmin=2mb
This will set the minimum SCRATCH disk estimate to 2 MB.
smemory smemory=size Default: 100 (all others)
Same as MSC Nastran keyword, see smemory, 221. This keyword cannot appear in an
ESTIMATE RC file if “nastrc=yes” is specified.
spc spc=number Default: None

Main Index
 22 MSC Nastran 2020 Utilities Guide
ESTIMATE

Selects an SPC if an SPC Case Control command is not present or multiple SPC
Case Control commands are present in the data file. By default, ESTIMATE will
choose the first SPC found.
suppress suppress=list Default: None
Specifies rules that are to be suppressed when “mode=suggest” or “mode=modify” is
specified. See Rules, 22 for the list of rules. If no value is specified, i.e., “suppress=”,
then any rules previously suppressed are enabled. Multiple rules can be suppressed
by using the keyword multiple times or by specifying a comma-separated list.
Example: util_ver estimate example
suppress=1
Suppress rule 1, the rule controlling BUFFSIZE.
Examples: util_ver estimate example
suppress=1,6
util_ver estimate example
suppress=1 suppress=6
util_ver estimate example
suppress=2 suppress= \
suppress=1,6
Suppress rules 1 and 6.
verbose verbose=yes,no Default: No
Specifies the amount of information to be displayed. Specifying “verbose=yes” will
generate a much larger amount of output. The additional information includes a
more detailed summary of the input file, the parameters used in estimating the
memory and disk requirements, and the estimates for the original file, even when
“mode=suggest” or “mode=modify” is specified.
version version=string Default: 2006
Specifies the version of MSC Nastran for which the estimates are to be targeted. The
version will affect the estimated memory requirements and the actions of various
rules, see Rules, 22. This keyword cannot appear in an ESTIMATE RC file if
“nastrc=yes” is specified.
wordsize wordsize=number Default: 64
Specifies the word size of the estimate’s target computer. By default, ESTIMATE’s
calculations will be appropriate the current computer. This keyword may be used to
specify estimates for a computer with a different word size. A comma-separated list
of values may be specified when estimates and suggestions for multiple machines are
desired. If “mode=modify” was specified, the modification are based on the last word
size specified.

Rules
ESTIMATE has a fixed rule base that it uses to make suggestions for improvement. Any of the rules may be
suppressed with the “suppress” keyword. The current rules are:

Main Index
 CHAPTER 1 23
Using the Utility Programs

1. Set recommended BUFFSIZE.

BUFFSIZE=8193 DOF  100000
BUFFSIZE=16385 100000  DOF  400000
BUFFSIZE=32769 DOF  400000

2. Use default BPOOL.

BPOOL=150

3. Suppress symmetric decomposition if not enough memory for sparse.

SYSTEM(166)=0
4. Make all open core available to modules.
Delete HICORE.
5. Select the sparse solver.
Delete SPARSE
Delete USPARE density  12.0
SPARSE=1
density  12.0
USPARSE=0

6. Force default rank size.

Delete SYSTEM(198)
Delete SYSTEM(205)
7. Do not sequence.
PARAM,NEWSEQ,-1 version  69.0

8. Use default Lanczos parameters.

EIGRL,...,V1=““
EIGRL,...,MAXSET=15
9. Use default SMEMORY.
INIT SCRATCH (MEM=100) wordsize = 32
INIT SCRATCH (MEM=0) wordsize = 64

10. Use estimated memory size.

memory=estimated-memory

Main Index
 24 MSC Nastran 2020 Utilities Guide
F04REPRT

11. Use default RAM.

INIT MASTER (RAM=30000)
12. Real.
Delete REAL.
13. Do not use Supermodule.
Delete PARAM,SM,YES.
14. Do not use Parallel Lanczos.
Delete NUMSEG.

Examples
The ESTIMATE program can be used in several ways. The default mode will make suggestions on improving
the performance of MSC Nastran and estimate the resource requirements of the job assuming the suggested
parameters.

util_ver estimate example

To get an estimate of the job using the current parameters, use the command:

util_ver estimate example mode=estimate other_estimate_keywords

To have a new input file generated with the suggested changes, use the command:

util_ver estimate example mode=modify other_estimate_keywords

To run MSC Nastran with the memory estimated by ESTIMATE, use:

util_ver nastran example memory=estimate other_nastran_keywords

F04REPRT
The F04REPRT utility is a Perl script that will summarize and/or compare .f04 files. The utility can
determine the CPU time consumed by various MSC Nastran modules, i.e., as a DIAG 49 replacement, or
compare the relative performance of one or more jobs under various configurations.

Note: You must have Perl installed on your system to use this utility. Perl is available from numerous
sources, including the URL
http://www.perl.com
This is not an MSC Software Corporation site and MSC has no control over the site’s content.
MSC cannot guarantee the accuracy of the information on this site and will not be liable for
any misleading or incorrect information obtained from this site.

Main Index
 CHAPTER 1 25
Using the Utility Programs

The basic format of the F04REPRT command is

util_ver f04reprt.pl -s [options] pathname [pathname ...]

or

util_ver f04reprt.pl -d [options] old1 new1 [oldn newn...]

where “-s” selects the summary mode, “-d” selects the comparison mode, options are zero or more of the
options listed below, pathname is a pathname, and oldi and newi are pathnames. If a pathname is a directory,
all .f04 files in the directory are summarized/compared.

Note: Alternatively, you can run F04REPRT with the command

perl install-dir/prod_ver/util/f04reprt.pl arguments ...
on LINUX, or
perl install-dir\prod_ver\util\f04reprt.pl arguments ...
on Windows if perl is in your PATH. LINUX users can also use the command
install-dir/prod_ver/util/f04reprt.pl arguments ...
if your Perl executable is /usr/local/bin/perl, or the “shbang” line was updated to the
appropriate path.

Running F04REPRT without any arguments will display a help message explaining the utility’s options.

Main Index
 26 MSC Nastran 2020 Utilities Guide
F04REPRT

Options
-c -c Default: No
Indicates module times are to be accumulated in a single entry, rather than separate
entries for each module occurrence
-d -d Default: None
Requests a comparison (difference) between each pair of oldi and newi pathnames
specified on the command line. If only one pair of pathnames are specified, the “-d”
is optional.
-e Specifies that module elapsed times are to be used for ordering entries instead of
CPU times.
-f -f c Default: Space
Specifies a field separator character to separate field in the comparison report. This
character may be inclosed in either single or double quotes to protect it from the
command shell.
-m -m number Default: 0.05
Specifies the minimum CPU time threshold for comparisons or summaries. CPU
times less than this threshold will be ignored.
-o -o file-type Default: None
Specifies an output file-type. If specified, each comparison or summary report will
be written to a separate file in the current working directory with the name
basename.ext where basename is the base name of the pathname or oldi.
If not specified, output will be written to stdout with each report separated by a form
feed “Ctrl-L” character.
-r -r number Default: 5
Specifies the delta percentage used for “FASTER” and “SLOWER” comments in
comparison (-d) output.
Any old versus new comparisons that exceed this delta from 100%,eg.,
 delta  95%  or  delta  105%  , will print the appropriate comment.
-s -s Default: None
Requests a summary report for each pathname specified on the command line. If
only one pathname is specified, the “-s” is optional.
-x -x file-type Default: f04
Specifies an alternate input file type.

Main Index
 CHAPTER 1 27
Using the Utility Programs

Examples
util_ver f04reprt.pl example

If “./example” on LINUX, or “.\example” on Windows, is a subdirectory of the current directory,

F04REPRT will write a summary report to stdout for every .f04 file in the directory. Otherwise, if
“./example.f04” on LINUX, or “.\example.f04”, on Windows is a file, a summary report of the one file is
written to stdout.

util_ver f04reprt.pl old new

If “old” and “new” are subdirectories of the current working directory, F04REPRT will generate lists of the
.f04 files in each directory. Comparisons will be made between each pair of files with the same name in the
two directories. Non-.f04 files and unpaired .f04 files, i.e., .f04 files that exist in either “old” or “new” but
not both, will be ignored. Otherwise, if “old.f04” and “new.f04” are files, then a comparison of these two files
will be displayed.

MSCACT
MSCACT may be used to generate usage reports from the accounting files generated by MSC Nastran when
the “acct=yes” keyword is used. The basic format of the “mscact” command is

util_ver mscact [keywords] acc-file [acc-file ...]

where acc-file are the names of the accounting file(s) to be summarized.

Note: The keywords only affect files listed after the keyword.

Keywords
perfile perfile=yes,no Default: No
Specifies the summary is to be printed on a per file basis. If “perfile=yes” is specified,
a summary of each file will be individually printed. By default, the summary will
include all files.
sortby sortby=keyword Default: Name
Sort the report as specified by the keyword. The keywords are:

Keyword Sort Order

count Sort by third report column.

Main Index
 28 MSC Nastran 2020 Utilities Guide
MSCACT

cpu Sort by second report column.

name Sort by first report column.
none Do not sort report; report is ordered as found
in data file.

Setting “sortby=none” produces a report very similar to the previous versions of this
utility.

summary summary=keyword Default: None

Selects the type of summary. If “summary=none” is specified, the total CPU for all
entries will be displayed. Otherwise, one of the following summary types may be
selected:

Keyword Type of Summary

acdata By acdata
acid By account ID (acid)
date By execution date
jid By job name
product By product name
sol By SOL
user By user name
version By product name and version

Examples
All of the following examples assume your current working directory is the MSC Nastran accounting
directory, i.e., install_dir/acct on LINUX and install_dir\acct on Windows.
To summarize accounting data across all files:

util_ver mscact file1 file2

file1 file2:
Total: cpu-sec count

where filei are the filenames, cpu-sec is the total CPU seconds across all files, and count is the number of entries
accumulated across all files.
To summarize accounting data from individual files:

Main Index
 CHAPTER 1 29
Using the Utility Programs

util_ver mscact perfile=yes file1 file2

file1:
Total:cpu-sec count
file2:
Total:cpu-sec count

where filei is the name of each file, cpu-sec is the total number of CPU seconds, and count is the number of
entries in each file.
To summarize accounting data in individual files by user:

util_ver mscact summary=user perfile=yes file1 file2

file1:
user1:cpu-sec1 count1
user2:cpu-sec2 count2
...
Total:cpu-sec count
file2:
user1:cpu-sec1 count1
user2:cpu-sec2 count2
...
Total:cpu-sec count

where filei are the filenames of each file, useri are the names, cpu-seci are the total CPU seconds for each user,
counti are the number of entries accumulated for each user, cpu-sec is the number of total CPU seconds, and
count is the number of entries in each file.

Accounting File Format

A separate file is created for each month of each year and is named

install_dir/acct/mscyymm.acc

on LINUX and

install_dir\acct\mscyymm.acc

on Windows where yy are the last two digits of the year and mm is the month (01 to 12). Each month’s file
is independent of every other file.
The accounting file begins with three header records followed by detail records, one detail record for each
MSC Nastran job run during the given month and year. Comments, indicated by a hash mark “#” as the first
character of the line, may be placed anywhere in the file after the header records.
Detail records (any non-comment line after the third line) include the following data:
1. The day the job was started (i.e., Sun., Mon., Tue., Wed., Thu., Fri., or Sat.).

Main Index
 30 MSC Nastran 2020 Utilities Guide
MSCPLOTPS

2. The month the job was started (i.e., Jan., Feb., Mar., Apr., May, Jun., Jul., Aug., Sep., Oct., Nov.,
or Dec.).
3. The date of the month the job was started (i.e., 01 through 31).
4. The time the job was started (i.e., hh:mm:ss, where hh is 00 through 23, mm is 00 through 59, and
ss is 00 through 59).
5. The time zone (i.e., the “TZ” environment variable).
6. The year the job was started (four digits).
7. The name of the user running the job.
8. The job’s output filename.
9. The analysis application, e.g., MSC Nastran.
10. The version of the application (e.g., 2019.1).
11. The SOL used by the job (e.g., 101, 120).
12. The total CPU time, in seconds, of the job (from the .f04 file).
13. The cumulative CPU time, in seconds, of all detail records up to and including this record.
14. The cumulative CPU time, in minutes, of all detail records up to and including this record.
15. The account ID as specified by the nastran command’s “acid” keyword.
16. The account data as specified by the nastran command’s “acdata” keyword.

Note: The cumulative times (fields 13 and 14) are for historical purposes only. These values are
ignored.

MSCPLOTPS
MSCPLOTPS is very similar to PLOTPS in that it reads plotting commands from a single MSC Nastran
binary- or neutral-format plot file and produces a file that can be printed on a PostScript device. The primary
difference is that MSCPLOTPS automatically determines the format of the input file, i.e., whether it is a
binary- or a neutral-format plot file, and supports plot files generated on any platform and in any processing
mode. Otherwise, the processing capabilities of the two programs are the same. Except as noted below, the
use of MSCPLOTPS is the same as the use of PLOTPS. Please see PLOTPS, 35 and replace the word plotps
with mscplotps. The basic format of the “mscplotps” command is:
util_ver mscplotps input_plot_file [keywords]
where input_plot_file is the name of the plot file generated by MSC Nastran or NEUTRL. A neutral-format
plot file can be read from stdin by specifying “-” as the filename. If the extension of the input file is “.plt” or
“.neu”, the extension may be omitted from tine input_plot_file specification.

Main Index
 CHAPTER 1 31
Using the Utility Programs

All keywords are the same as for PLOTPS except that the “format” keyword is optional. If it is specified, the
specified type will be checked against the actual type, a warning message issued if the types do not match,
and the “format” specification ignored.

Note: MSCPLOTPS command is only used on LINUX systems.

MSGCMP
MSGCMP compiles a text message file and generates a binary message catalog. The basic format of the
command is
util_ver msgcmp text_file [message_catalog]
where text_file is the name of an existing text message file or is “-” to read from stdin, and message_catalog is
the optional name of the message catalog that will be written. The type of the text file must be “.txt”. If a
message catalog is not named, the message catalog will be written in the local directory as “text_file.msg”. The
message catalog can be tested using the “msgcat” keyword (p. 205).
The utility can also regenerate a text file from an existing message catalog using the command
util_ver msgcmp message_catalog.msg [text_file]
where message_catalog.msg is the name of an existing message catalog and text_file is the optional name of a
text file that will be written. The type of the message catalog must be “.msg” and must be entered on the
command line. If a text file is not named, the text file is written to stdout.
The text source file for the standard message catalog is
install_dir/prod_ver/util/analysis.txt
on LINUX and
install_dir\prod_ver\util\analysis.txt
on Windows. The standard message catalog is
install_dir/prod_ver/arch/analysis.msg
on LINUX and
install_dir\prod_ver\arch\analysis.msg
on Windows.

Examples
The following command will compile the message catalog from a text file named “myfile.txt”
util_ver msgcmp myfile
The message catalog will be named “myfile.msg”. This catalog may be used with the nastran command
util_ver nastran myjob msgcat=myfile.msg other_nastran_keywords

Main Index
 32 MSC Nastran 2020 Utilities Guide
MultiOpt

Note: Message catalogs are machine dependent. “Binary File Compatibility” identifies the systems
that are binary compatible; binary compatible systems can use multiple copies of the same
message file.

MultiOpt
MSC Nastran utility MultiOpt supports Multiple Model Optimization (MMO) and Global Optimization
(GO). MMO combines two or more related optimization tasks into a single combined optimization task.
GO is a practical procedure to find an approximate global optimal solution with reasonable computing cost.
The way to invoke MultiOpt is using a command line of the following form:
MSC20200 MultiOpt mygofile.xml (or mymmofile.xml)
Additional guidance on the use of the MultiOpt utility can be found in MultiOpt-Global Optimization and Multi
Model Optimization (Ch. 9) in the Design Sensitivity and Optimization User’s Guide.

NEUTRL
NEUTRL converts a binary-format plot file into a neutral-format plot file. The basic format of the “neutrl”
command is

util_ver msgcmp myfile

where binary_plot_file is the name of a binary plot file. If the file type of the plot file is “.plt”, it may be
omitted from the command line.

Keywords
dump dump=yes,no Default: no
This option enables a raw print of each plot command to be made before it is
processed. This print is used for debugging purposes only.
output output=pathname Default: binary_plot_file.neu
This option specifies the name of the neutral-format file. If “out=—” is specified, the
neutral plot file is written to stdout. By default, the output file is the name of the
input file with the new type “.neu”.
verbose verbose=yes,no Default: yes Output is a disk file.

no Output is stdout.
This option specifies whether processing messages are to be written.

Main Index
 CHAPTER 1 33
Using the Utility Programs

Examples
To execute the program, enter the following command:
util_ver neutrl example1
The name of the output file is
example1.neu

OP4UTIL
OP4UTIL may be used to validate, copy or reformat binary files created using the MSC Nastran OUTPUT4
module. It may also be used to “dump” the contents of any binary format file. The basic format of the
"op4util" command is:
util_ver op4util <options> <file names>

This program is used as follows:

To generate a usage/help message:
util_ver op4util
util_ver op4util -h[elp]
util_ver op4util -?

To copy a file:
util_ver op4util -c[opy] [-v[erbose]] <from_fname> <to_fname>

To dump a file or files:

util_ver op4util -d[ump] [-v[erbose]] <fname_1> [... <fname_n>]

To query a file or files to determine their format:

util_ver op4util -q[uery] [-v[erbose]] <fname_1> [... <fname_n>]

To validate (test) a file or files, i.e., to check their validity as OUTPUT4 files:
util_ver op4util -t[est] [-v[erbose]] [-m nnn] <fname_1> [... <fname_n>]

Main Index
 34 MSC Nastran 2020 Utilities Guide
OP4UTIL

Keywords
-? Requests that usage information be written to stdout. This is the same as the
-h option.
-c[opy] Requests the copy option. This option copies the file specified by <from_fname>
to the file specified by <to_fname>, overwriting any existing file and creating a
new file if it does not exist. This option does not validate <from_fname> or
change its format in any way.
-d[ump] Requests the file dump option. This option lists the contents of each file, including
record number and record length information, in both hexadecimal and character
formats. Just as will the -query option, it checks each of the files specified by
<fname_1> to <fname_n> to see if it is a valid binary file and reports its
endian. The file need not be a valid OUTPUT4 file.
-h[elp] Requests that usage information be written to stdout.
-m nnn This parameter is only required when the -test, -xchange or <endian_opt> options
fail because of memory allocation errors. The nnn value is the size of the memory
to be used, in MB, and must be in the range 1 to 2047. The blank between the -m
and the nnn value is optional.
-q[uery] Requests the file query option. This option checks each of the files specified by
<fname_1> to <fname_n> to see if it is a valid binary file and reports its endian.
It does not test the actual file data to see if the file is a valid OUTPUT4 file.
-t[est] Requests the file validate (test) option. This option reads each of the file specified
by <fname_1> to <fname_n>, checking for a valid binary format file
containing matrices in the proper OUTPUT4 format.
-v[erbose] Requests "verbose" output. Normally, the -copy, -test, -xchange, and
<endian_opt> options do not generate any output and the -query and -test
options only write out a single line about each of the files they process. In verbose
mode, program headers and detailed file descriptions are generated, and the -test,
-xchange and <endian_opt> options will list the matrices in the files along with
their format and size.

If more than one processing option is specified, the last one specified is the one that will be in effect.
The default options (if one of -c, -h, -q, -t, -x, -? or -b, -l or one of their synonyms are not specified) are

-h If there are no file name options

-q If one or more than two file name options are specified
-x If exactly two file name options are specified.

Error messages such as those describing invalid command options are written to stderr.

Main Index
 CHAPTER 1 35
Using the Utility Programs

Examples:
1. Copy file infile_1.op4 to test_file.op4:
util_ver op4util -c infile_1.op4 test_file.op4
2. Copy file input_file.op4 to win_file.op4, forcing win_file.op4 to have Windows
(little-endian) format. Also, generate verbose messages about the conversion process:
util_ver op4util -wind -v input_file.op4 win_file.op4
3. Dump files input_file.op4 and input_file.op2, generating verbose messages about the
file formats:
util_ver op4util -dump-v input_file.op4 input_file.op2

PLOTPS
PLOTPS reads plotting commands from a single MSC Nastran binary- or neutral-format plot file and
produces a file that can be printed on a PostScript device. The basic format of the “plotps” command is

util_ver plotps input_plot_file [keywords]

where input_plot_file is the name of the plot file generated by MSC Nastran or NEUTRL. A neutral-format
plot file can be read from stdin by specifying “-” as the filename. The plot file type “.plt” does not have to be
specified on the command line.

Keywords
begin begin=number Default: 1
end end=number Default: 999999
Plots a selected range of plot frames.
color color=yes,no Default: No
Enables or disables color pens. Setting “color=no”, the default, will assign a solid
line to pen 1 and various dashed lines to pens 2, 3, and 4. Setting “color=yes” will
assign black to pen 1, red to pen 2, green to pen 3, and blue to pen 4. All text and
axes will always be written with a solid black pen.
cscale cscale=number Default: 1.0
Specifies a scale factor for all characters and special symbols on the plot. By default,
characters and special symbols are 9 points (about 0.125 inch). The scale value, if
specified, is also applied to characters and special symbols.
The “cscale” value is critical to the correct imaging of the plot if
“optimizestrings=yes” was specified. In general, you must specify the same “cscale”
value as was specified in the original MSC Nastran job that generated the PLT file.
dump dump=yes,no Default: No
Enables a raw print of each plot command before it is processed. This print is used
for debugging purposes only.

Main Index
 36 MSC Nastran 2020 Utilities Guide
PLOTPS

format format=keyword Default: Binary

Specifies the input file format. If the file type of the input file is “.neu” or the plot
file is read from stdin, then “format=neutral is assumed.
height height=number Default: 10.0 inches
Specifies the printable page height. The actual page is assumed to be 1 inch larger.
optimizestrings optimizestrings=yes,no Default: Yes
Indicates the string optimization feature is to be enabled. This feature can result
in a substantial reduction in plot file size, printer memory requirements, and print
speed.
If “optimizestrings=no” is set, PLOTPS will draw each character individually, at
the expense of PS file size and the memory and time needed by your PostScript
printer to image the file.
output output=pathname Default: plot-file.ps
Specifies the name of the PostScript output file. If a neutral-format plot file is read
from stdin, the default output filename is “plotps.ps”. If “out=—” is specified, the
PostScript output is written to stdout. By default, the output file is named the
name of the input file with the new type “.ps”.
rotate rotate=keyword Default: Automatic
Controls the orientation of the generated image. If “rotate=automatic” is specified,
the program orients the image so that the long direction of the image is aligned
with the long direction of the page. If “rotate=no” is specified, the image is
generated with the horizontal axis aligned with the bottom edge of the page. If
“rotate=yes” is specified, the image is generated with the horizontal axis aligned
with the right edge of the page.
scale scale=number Default: 1.0
Specifies a scale factor for all elements of the plot.

Note: The program will not attempt to print a multipage image if this option is used to enlarge the
image beyond the size of the available page.

verbose verbose=yes,no Default: Yes Output is a disk file

No Output is stdout.
Specifies whether processing messages are to be written.
width width=number Default: 7.5 inches
Specifies the printable page width. The actual page is assumed to be 1 inch larger.

Main Index
 CHAPTER 1 37
Using the Utility Programs

Note: The begin, end, dump, format and output keywords are not allowed for PostScript plot
generation in MSC Nastran. That is, these keywords may not be specified on the SYS=
describer or in the SYFIELD keyword for the PLOT logical name.

Examples
To translate a binary-format plot file named example1.plt into PostScript, use

util_ver plotps example1

The name of the output file is

example1.ps

To translate a neutral-format plot file named example2.neu into PostScript, use

util_ver plotps example2.neu

The name of the output file is

example2.ps

Using the String Optimization Feature

When the string optimization feature functions correctly, you can realize a substantial reduction in the size
of the PostScript file and a commensurate reduction in the memory and time needed by your PostScript
printer to image the file. However, there are some cases where the feature does not function correctly, and
generates an incorrect plot image.
The “cscale” value used in the MSC Nastran job that generated the PLT file is critical to the correct operation
of the “optimizestrings” feature. In general, you need to specify the same value in the PLOTPS run. There
are some cases, however, where the value should be left at the default, i.e., 1.0. You can determine this by
imaging and printing the first frame of the PLT file with the following two commands:

util_ver plotps plt-file end=1 out=value.ps cscale=cscale-value

util_ver plotps plt-file end=1 out=default.ps

where plt-file is the MSC Nastran PLT file and cscale-value is the CSCALE value used in the MSC Nastran
job that generated the file. A visual comparison of the two PostScript images will identify the correct setting.
In general, it will be the first command, i.e., the one that set the CSCALE value to the MSC Nastran job’s
value.

Main Index
 38 MSC Nastran 2020 Utilities Guide
RCOUT2

RCOUT2
RCOUT2 is used to convert a neutral-format OUTPUT2 file generated by MSC Nastran into a
binary-format OUTPUT2 file. Since MSC Nastran can read and write binary-format and neutral-format
OUTPUT2 files, this utility is generally used to construct a binary OUTPUT2 file for a third-party program
that can only read a binary OUTPUT2 file. The basic format of the “rcout2” command is

util_ver rcout2 neutral_output2_file [keywords]

Keywords
output output=pathname Default: neutral_file.op2
This option specifies the name of the binary OUTPUT2 file. By default, the output
file is the name of the input file with the new type “.op2".

Examples
To execute the program, enter the following command:

util_ver rcout2 example

The name of the output file is

example.op2

Building the Utilities Delivered in Source Form

Several of the utilities (i.e., PLOTPS, NEUTRL, RCOUT2, and MSCACT) are delivered in source and
executable form. The source code allows these utilities to be customized or built for other platforms. A script
and makefile are provided to build and install these utilities. The script determines the architecture of current
platform and invokes the make utility to perform the actual compilation, link, and installation.
The utility program source files are located in

install_dir/prod_ver/util

on LINUX and

install_dir\prod_ver\util

on Windows. This directory is an optional component of the MSC Nastran installation. This directory
includes the following files:

Main Index
 CHAPTER 1 39
Using the Utility Programs

Table 1-2 Utility Program Source Files

File Description
acnaspat.pl
ld.F Source for RCOUT2 Utility Routines.
libfmsc.F Source for FORTRAN Utility Library Routines.
makefile Makefile to Build Source Utility Programs.
mattst.F Source for Sample OUTPUT4 File Reader TABTST (see Building and Using TABTST,
53).
mscact.c Source for MSC Accounting Programs.
neutrl.F Source for NEUTRL Utility.
ngtarg.F Source for Command Line Utilities.
plotps.F Source for PLOTPS Utility.
rcout2.F Source for RCOUT2 Utility.
tabtst.F Source for Sample OUTPUT2 File Reader MATTST (see Building and Using MATTST,
49).
util Script to Build Source Utility Programs.

Three steps are required to build and install the source utilities. Make sure that you are in the utility program
source directory, i.e., install_dir/prod_ver/util on LINUX and install_dir\prod_ver\util on Windows.
1. The first step compiles and links all of the source utility programs. Enter the command

util_ver util build

If only one utility is to be built, use the name of the utility (i.e., “mscact,” “neutrl,” “plotps,” or
“rcout2") instead of “build”. For example,

util_ver util plotps

will only build the PLOTPS utility.

2. After the programs are generated in the current directory, you can install the executable programs into
the architecture directory for your computer (i.e., install_dir/prod_ver/arch on LINUX and
install_dir\prod_ver\arch on Windows). Enter the command

util_ver util install

3. The third step deletes all object files and temporary files created by the “make” process. Enter the
command

Main Index
 40 MSC Nastran 2020 Utilities Guide
MSC Fatigue Utilities for Nastran Embedded Fatigue

util_ver util clean

The building and installation process can be repeated if you want to build the utilities for other computer
architectures at your site.
To build the utilities on another computer that does not have MSC Nastran installed, copy the complete
utilities directory to the other computer. Since the util_ver command will not be available, you must run the
util script directly. Before you do, however, set the environment variable MSC_ARCH to the name of a
supported architecture as shown in Table 3-1. The “install” option cannot be used.

MSC Fatigue Utilities for Nastran Embedded Fatigue

The utilities created for MSC Fatigue are now included in MSC Nastran. These utilities may be used to
process fatigue data (such as DAC files). Refer to the MSC Fatigue User's Guide for specific details about
these utilities.
The utilities were built on an IA32 system.
On Windows, these utilities do not work as specified if MSC_BASE has a space in the path.
On Linux, to run these utilities, the following i386 RPMs will be required to be installed on your system:
libXp-1.0.0-8.1.el5.i386.rpm
libXmu-1.0.2-5.i386.rpm
openmotif-2.3.1-2.el5.i386.rpm
Several environmental variables are needed to run these utilities. The following example is a template to run
the "ptime" utility on linux:
#! /bin/sh
#
MSC_BASE=/opt/MSC_NASTRAN
MSC_VERSD=20200/msc20200
MSC_ARCH=linux64
#
# Ncode libs
export
LD_LIBRARY_PATH=${MSC_BASE}/${MSC_VERSD}/${MSC_ARCH}/NEF_utils/b
in:${MSC_BASE}/${MSC_VERSD}/${MSC_ARCH}/NEF_utils/syslib/intel:
MSC_BASE}/${MSC_VERSD}/${MSC_ARCH}
export npath=${MSC_BASE}/${MSC_VERSD}/${MSC_ARCH}/NEF_utils
#
export p3fpath=$npath
export PATH=$PATH:$npath/bin
#
echo $PATH
$npath/bin/ptime
Please see Utilities (App. C) in the for more details.

Main Index
 Chapter 2: Building and Using the Sample Programs
MSC Nastran 2020 Utilities Guide

2 Building and Using the

Sample Programs


Overview
 Building and Using BEAMSERV

Building and Using DDLPRT

Building and Using DDLQRY

Building and Using DEMO1

Building and Using DEMO2

Building and Using DR3SERV

Building and Using MATTST

Building and Using SMPLR

Building and Using a Spline Server
 Building and Using TABTST
 Beam Server Source Files

DRESP3 Server Source Files

MSC.Access Source Files

Main Index
 42 MSC Nastran 2020 Utilities Guide
Overview

Overview
This chapter describes how to build and use the various MSC Nastran sample programs. The sample
programs are grouped by function as follows:

Program Function
BEAMSERV Implements user-defined bar and beam elements for MSC Nastran.
DDLPPRT Reads and displays XDB results database files. These sample programs are part of
DDLQRY MSC.Access and demonstrate how to use the database library routines.

DEMO1
DEMO2
SMPLR
DR3SERV* Implements user-defined responses for MSC Nastran.
MATTST** Reads and displays OUTPUT2 and OUTPUT4 files.
TABTST**
SPXSRVA* Implements user-defined splines for MSC Nastran

Descriptions on building and using the sample programs follow in alphabetical order. If SCONS is being
used to build a standalone program, it can be installed as part of the MSC SDK.
*When building with SCons on linux, the 32 bit versions of libz and xml2 need to be installed.
**When building on windows, please issue the following first to initialize compilers:
set Fx=”C:\Program Files (x86)\
IntelSWTools\compilers_and_libraries_2017.5.267\windows\bin\ipsxe-comp-
vars.bat”
call %Fx% intel64 vs2017

Building and Using BEAMSERV

BEAMSERV implements a user-defined beam element for MSC Nastran.

Note: The sample beam server source code is only provided as a simple example illustrating basic
concepts. It is not intended to be a complete or usable program.

Unlike the other sample programs, a beam server is not a stand alone program that runs from the command
line. Instead, the beam server is started and controlled by MSC Nastran. In the current implementation,
communications between MSC Nastran and the beam server are accomplished through pipes, with MSC
Nastran reading and writing BEAMSERV’s stdout and stdin units, respectively.

Main Index
 CHAPTER 2 43
Building and Using the Sample Programs

Note: 1. The MSC Nastran job invoking the beam server and the beam server itself may run on
different computers but they have to be network mounted.
2. Your program may not read from stdin (FORTRAN logical unit 5) nor write to stdout
(FORTRAN logical unit 6).
3. The beam server cannot write to the .f06, .f04, or .log files of the MSC Nastran job that
started the beam server.
4. Debugging must be accomplished by writing to a disk file, or connecting to the running
beam server executable with a debugger (this may not be available on all systems, and
debug compiler options should be used).

Building BEAMSERV
The BEAMSERV program source files are located in the directory

install_dir/prod_ver/nast/beamlib/src/beamserv

on LINUX and

install_dir\prod_ver\nast\beamlib\src\beamserv

on Windows (see Beam Server Source Files, 55).

To build the program, change the working directory to the beamlib directory and enter the command:

scons opt=yes beamserv

It will create beamserv on LINUX or beamserv.exe on Windows and store it in the

$APPS_LOCAL/arch/bin/ directory. To learn more about the build environment, please consult the MSC
Software Development Kit User’s Guide.
Alternatively, you may copy the entire beamlib directory to another location, change the working directory
to ~new_path/beamlib/ and issue the command:

scons opt=yes beamserv

Using BEAMSERV
MSC Nastran is made aware of the beam server by the “gmconn” keyword and an external evaluator
connection file. Entries in the connection file for piped communications are formatted as follows:

evaluatorname,pipe,pathname

Main Index
 44 MSC Nastran 2020 Utilities Guide
Building and Using DDLPRT

where evaluatorname is the evaluator name defined on the CONNECT FMS statement and pathname is the
pathname of the beam server executable.

Note: The evaluator name on the CONNECT FMS statements and in the external evaluator
connection file must match exactly, including character case. To use a mixed or lower case
group name, the name on the CONNECT FMS statement must be in quote marks; the name
in the external evaluator connection file is never quoted.

To use the sample beam server and data file, create the file “samp_eval” with the following line:

LOCBMLS,pipe,pathname

where pathname is the pathname of the beam server built above, e.g.,
$APPS_LOCAL/arch/bin/beamserv on LINUX or $APPS_LOCAL\arch\bin\beamserv.exe on
Windows.
MSC Nastran is then run using the following command:

prod_ver nastran sample gmconn=samp_eval

Building and Using DDLPRT

DDLPRT illustrates the mass retrieval of data from the MSC.Access Data Definition Language (DDL)
database.

Building DDLPRT
The DDLPRT program source code is in the file “ddlprt.F” (see MSC.Access Source Files, 56). To build the
program, change the working directory to the access directory and type the command:

SCONS opt=yes ddlprt

If you do not have write access to the source directory, install_dir/prod_ver/access on LINUX and
install_dir\prod_ver\access on Windows, copy the entire directory to another location, change the working
directory to the new location, and issue the SCONS command.

Using DDLPRT
DDLPRT is run with the “ddlprt” command. The format of the “ddlprt” command is

util_ver ddlprt [ddl_xdb_file] [keywords]

If the DDL XDB file is not specified, the program uses the default MSC.Access DDL file,
install_dir/prod_ver/arch/dbc.xdb on LINUX and install_dir\prod_ver\arch\dbc.xdb on Windows. The
optional keywords are:

Main Index
 CHAPTER 2 45
Building and Using the Sample Programs

print=print_file Default: ddl_xdb_file.prt

This keyword specifies the name of the print file documenting
the format of every MSC.Access relation. By default, the print
file uses the basename of the input DDL XDB file with the new
file type “.prt”. Note, the size of this file is approximately one
megabyte.
toc=table_of_contents_file Default: ddl_xdb_file.toc
This keyword specifies the name of the print file’s table of
contents. By default, the toc file uses the basename of the input
XDB file with the new file type “.toc”.

To execute the program, enter the command:

util_ver ddlprt

The program displays the filename, version, and compilation date of the DDL file as well as the names of the
print and table of contents files. Once these files are generated, the program exits. The print and table of
contents files may then be printed once DDLPRT has completed.

Building and Using DDLQRY

DDLQRY illustrates the interactive retrieval of data from the MSC.Access Data Definition Language (DDL)
database.

Building DDLQRY
The DDLQRY program source code is in the file “ddlqry.F” (see MSC.Access Source Files, 56). To build the
program, change the working directory to the access directory and type the command:

SCONS opt=yes ddlqry

If you do not have write access to the source directory, install_dir/prod_ver/access on LINUX or
install_dir\prod_ver\access on Windows, copy the entire directory to another location, change the working
directory to the new location, and issue the SCONS command.

Using DDLQRY
DDLQRY is run with the “ddlqry” command. The format of the “ddlqry” command is

util_ver ddlqry [ddl_xdb_file]

If a file is not specified, the program uses the default MSC.Access DDL file,
install_dir/prod_ver/arch/dbc.xdb on LINUX and install_dir\prod_ver\arch\dbc.xdb on Windows.

Main Index
 46 MSC Nastran 2020 Utilities Guide
Building and Using DEMO1

The program displays the filename, version, and compilation date of the DDL file and prompts you for the
name of a DDL object:

Enter Object Name (null to quit)

After you enter the name of each object, the format of the object is displayed. The program repeats the
prompt until a blank line is entered.

Building and Using DEMO1

DEMO1 prints information about a results database (XDB) file produced by MSC Nastran.

Note: The sample program source code is only provided as a simple example illustrating basic
concepts. It is not intended to be a complete or usable program.

Building DEMO1
The DEMO1 program source code is in the file “demo1.F” (see MSC.Access Source Files, 56). To build the
program, change the working directory to the access directory and type the command:

scons opt=yes demo1

If you do not have write access to the source directory, install_dir/prod_ver/access on LINUX or
install_dir\prod_ver\access on Windows, copy the entire directory to another location, change the working
directory to the new location, and issue the SCONS command.

Using DEMO1
DEMO1 is run using the “demo1” command. The installed version of the program is run with the command:

util_ver demo1

You are prompted for the input graphics database filename.

Enter the database path name:

Running MSC Nastran with a101x.dat (in install_dir/prod_ver/access) produces a101x.xdb that may be used
as input to this program.

Building and Using DEMO2

DEMO2 prints information about a results database (XDB) file produced by MSC Nastran.

Main Index
 CHAPTER 2 47
Building and Using the Sample Programs

Note: The sample program source code is only provided as a simple example illustrating basic
concepts. It is not intended to be a complete or usable program.

Building DEMO2
The DEMO2 program source code is in the file “demo2.F” (see MSC.Access Source Files, 56). To build the
program, change the working directory to the access directory and type the command:

scons opt=yes demo2

If you do not have write access to the source directory, install_dir/prod_ver/access on LINUX or
install_dir\prod_ver\access on Windows, copy the entire directory to another location, change the working
directory to the new location, and issue the SCONS command.

Using DEMO2
DEMO2 is run using the “demo2” command. The installed version of the program is run with the
command:

util_ver demo2

You are prompted for the input graphics database filename.

Enter the database path name:

Running MSC Nastran with a61x.dat (in install_dir/prod_ver/access) produces a101x.xdb that may be used
as input to this program.

Building and Using DR3SERV

DR3SERV implements user-defined responses for MSC Nastran.

Note: The sample DRESP3 server source code is only provided as a simple example illustrating basic
concepts. It is not intended to be a complete or usable program.

Unlike the other sample programs, a DRESP3 server is not a stand alone program that runs from the
command line. Instead, the DRESP3 server is started and controlled by MSC Nastran. In the current
implementation, communications between MSC Nastran and the DRESP3 server are accomplished through
pipes, with MSC Nastran reading and writing DR3SERV’s stdout and stdin units, respectively.

Main Index
 48 MSC Nastran 2020 Utilities Guide
Building and Using DR3SERV

Note: 1. The MSC Nastran job invoking the DRESP3 server and the DRESP3 server itself may
run on different computers but they have to be network mounted.
2. Your program may not read from stdin (FORTRAN logical unit 5) nor write to stdout
(FORTRAN logical unit 6).
3. The DRESP3 server cannot write to the .f06, .f04, or .log files of the MSC Nastran job
that started the DRESP3 server.
4. Debugging must be accomplished by writing to a disk file, or connecting to the running
dresp3 server executable with a debugger (this may not be available on all systems, and
debug compiler options should be used).

Building DR3SERV
The DR3SERV program source files are located in the directory

install_dir/prod_ver/nast/dr3/src/dr3serv

on LINUX and

install_dir\prod_ver\dr3srv

on Windows (see DRESP3 Server Source Files, 55).

To build the program, change the working directory to the dr3 directory and enter the command:

scons opt=yes dr3serv

where dr3serv is the target program. This command will create program, dr3serv on LINUX or dr3serv.exe
on Windows and store it in the $APPS_LOCAL/arch/bin/ directory. To learn more about the build
environment, please consult the MSC Software Development Kit User’s Guide.
Alternatively, you may copy the entire dr3 directory to another location, change the working directory to
~new_path/dr3 and issue the command:
scons opt=yes dr3serv
To build another server program, say dr3serva, change the working directory to dr3 directory and enter the
same build command with a new target name:
scons opt=yes dr3serva

Using DR3SERV
MSC Nastran is made aware of the DRESP3 server by the “gmconn” keyword and an external evaluator
connection file. Entries in the connection file for piped communications are formatted as follows:

evaluatorname,pipe,pathname

Main Index
 CHAPTER 2 49
Building and Using the Sample Programs

where evaluatorname is the evaluator name defined on the CONNECT FMS statement and pathname is the
pathname of the DRESP3 server executable.

Note: The evaluator name on the CONNECT FMS statements and in the external evaluator
connection file must match exactly, including character case. To use a mixed or lower case
group name, the name on the CONNECT FMS statement must be in quote marks; the name
in the external evaluator connection file is never quoted.

To use the sample DRESP3 server and data file, create the file “samp_eval” with the following line:

myrsp,pipe,pathname

where pathname is the pathname of the DRESP3 server built above, e.g., of the DRESP3 server built above,
e.g., $APPS_LOCAL/arch/bin/dr3serv on LINUX or $APPS_LOCAL\arch\bin\dr3serv.exe on
Windows.
MSC Nastran is then run using the following command:

util_ver nastran sample gmconn=samp_eval

Building and Using MATTST

MATTST reads a binary format OUTPUT4 matrix.

Note: The sample program source code is only provided as a simple example illustrating basic
concepts. It is not intended to be a complete or usable program.

Building MATTST
The MATTST program source code is in the file “mattst.F” (see Building the Utilities Delivered in Source Form, 38).
To build the program, change the working directory to the util directory and type the command:

util_ver util mattst

If you do not have write access to the source directory, install_dir/prod_ver/util on LINUX or
install_dir\prod_ver\util on Windows, copy the entire directory to another location, change the working
directory to the new location, and issue the command:

util_ver ./util mattst

on LINUX, or

util_ver .\util mattst

Main Index
 50 MSC Nastran 2020 Utilities Guide
Building and Using SMPLR

on Windows. Note, the directory specification is required in this circumstance.

Using MATTST
MATTST is run with the “mattst” command. The installed version of the program is run with the command:

util_ver mattst

You are prompted for the number of matrices.

Please enter the number of matrices:

You are prompted for the input filename.

Please enter the INPT4 FILENAME:

You are prompted for the output binary filename.

Please enter the output binary filename:

You are prompted for the output text filename.

Please enter the output text filename:

Running the MSC Nastran job “DEMODIR:um54.dat” produces a file, “um54.f11”, that may be used as
input to this program.

Building and Using SMPLR

SMPLR reads a results database (XDB) file produced by MSC Nastran.

Note: The sample program source code is only provided as a simple example illustrating basic
concepts. It is not intended to be a complete or usable program.

Building SMPLR
The SMPLR program source code is in the file “smplr.F” (see MSC.Access Source Files, 56). To build the
program, change the working directory to the access directory and type the command:

scons opt=yes smplr

If you do not have write access to the source directory, install_dir/prod_ver/access on LINUX or
install_dir\prod_ver\access on Windows, copy the entire directory to another location, change the working
directory to the new location, and issue the SCONS command.

Main Index
 CHAPTER 2 51
Building and Using the Sample Programs

Using SMPLR
SMPLR is run using the “smplr” command. The installed version of the program is run with the command:

util_ver smplr

You are prompted for the input filename.

Enter the database name to process:

Running MSC Nastran with a101x.dat (see MSC.Access Source Files, 56) produces a101x.xdb that may be used
as input to this program.

Building and Using a Spline Server

A spline server implements user-defined spline methods for MSC Nastran.

Note: The sample spline server source code is only provided as a simple example illustrating basic
concepts. It is not intended to be a complete or usable program.

Unlike the other sample programs, a spline server is not a stand-alone program that runs from the command
line. Instead, the spline server is started and controlled by MSC Nastran. In the current implementation,
communications between MSC Nastran and the spline server are accomplished through pipes, with MSC
Nastran reading and writing the spline server’s stdout and stdin units, respectively.

Note: 1. The MSC Nastran job invoking the spline server and the spline server itself may run
on different computers but they have to be network mounted.

2. Your program may not read from stdin (FORTRAN logical unit 5) nor write to stdout
(FORTRAN logical unit 6).

3. The spline server cannot write to the .f06, .f04, or .log files of the MSC Nastran job
that started the spline server.

4. Debugging must be accomplished by writing to a disk file, or connecting to the running

spline server executable with a debugger (this may not be available on all systems, and
debug compiler options should be used).

Building SPXSERVA
The spxserva program source files are located in the directory
install_dir/prod_ver/nast/spline_server/src/spxsrva

Main Index
 52 MSC Nastran 2020 Utilities Guide
Building and Using a Spline Server

on LINUX and
install_dir\prod_ver\nast\spline_server\src\spxsrva

on Windows (see Spline Server Source Files).

To build the program, change the working directory to the spline_server directory and enter the command:
scons opt=yes spxserva

where spxsrva is the targeted program. This command will create program, spxsrva on LINUX or spxsrva.exe
on Windows and store it in the $APPS_LOCAL/arch/bin/ directory. To learn more about the build
environment, please consult the MSC Software Development Kit User’s Guide.
Alternatively, you may copy the entire spline_server directory to another location, change the working
directory to ~new_path/spline_server and issue the command:
scons opt=yes spxsrva

Using the Spline Server

MSC Nastran is made aware of the spline server by the “gmconn” keyword and an external evaluator
connection file. Entries in the connection file for piped communications are formatted as follows:
evaluatorname,pipe,pathname

where evaluatorname is the evaluator name defined on the CONNECT FMS statement and pathname is the
path name of the spline server executable.

Note: The evaluator name on the CONNECT FMS statements and in the external evaluator
connection file must match exactly, including character case. To use a mixed or lower case
group name, the name on the CONNECT FMS statement must be in quote marks; the name
in the external evaluator connection file is never quoted.

To use the sample spline server and data file, create the file “samp_eval” with the following line:
EXTSPLN,pipe,pathname

where pathname is the path name of the spline server built above, e.g., my/path/to/spxserva or ./spxserva on
LINUX and my\path\to\spxserva or .\spxserva on Windows.
MSC Nastran is then run using the following command:
util_ver nastran sample gmconn=samp_eval for MSC Nastran

Main Index
 CHAPTER 2 53
Building and Using the Sample Programs

Spline Server Source Files

The spline server program source files are located in the spline server source directory, i.e.,
install_dir/prod_ver/nast/spline_server/src/spxsrva on LINUX and
install_dir\prod_ver\nast\spline_server\src\spxsrva on Windows. This directory is an optional component of
the MSC Nastran installation.
There are source files for two example spline servers: spxserva and spxservb. The spxserva program is
implemented entirely in the C programming language. The spxservb program uses a mix of the C and
Fortran programming languages.
Table 2-1 lists files contained in the SPXSERVA directory

Table 2-1 Spline Server spxserva Sample Program Source Files

File Description
SConscript File that is used by scons to guide the build
sxmsg.c Sample source for the spline server.
sxsevda.c Sample source for the spline server.

Table 2-2 lists files contained in the SPXSERVB directory

Table 2-2 Spline Server spxservb Sample Program Source Files

File Description
SConscript File that is used by scons to guide the build
mkgmat.F Sample source for the spline server.
spxaport.h Sample source for the spline server.
sxmsg.c Sample source for the spline server.
sxsevdb.c Sample source for the spline server.
sxsevdb.h Sample source for the spline server.
spxaport.h Sample source for the spline server.

Building and Using TABTST

TABTST reads a binary format OUTPUT2 file (do not confuse this program with RCOUT2, described in
RCOUT2, 38).

Main Index
 54 MSC Nastran 2020 Utilities Guide
Building and Using TABTST

Note: The sample program source code is only provided as a simple example illustrating basic
concepts. It is not intended to be a complete or usable program.

Building TABTST
The TABTST program source code is in the file “tabtst.F” (see Building the Utilities Delivered in Source Form, 38).
To build the program, change the working directory to the util directory and type the command:

util_ver util tabtst

If you do not have write access to the source directory, install_dir/prod_ver/util on LINUX or
install_dir\prod_ver\util on Windows, copy the entire directory to another location, change the working
directory to the new location, and issue the command:

util_ver ./util tabtst

on LINUX, or

util_ver .\util tabtst

on Windows.

Note: The directory specification is required in this circumstance.

Using TABTST
TABTST is run with the “tabtst” command. The installed version of the program is run with the command:

util_ver tabtst

You are prompted for the input filename.

Please type the INPUT2 filename:

You are prompted for the output filename.

Please type the output filename:

Running the MSC Nastran job “TPLDIR/basic:tabtsta.dat” produces a file, “tabtsta.f11”, that may be used
as input to this program.

Main Index
 CHAPTER 2 55
Building and Using the Sample Programs

Beam Server Source Files

The beam server program source files are located in the beam server source directory, i.e.,
install_dir/prod_ver/nast/beamlib/src/beamserv on LINUX and
install_dir\prod_ver\nast\beamlib\src\beamserv on Windows. This directory is an optional
component of the MSC Nastran installation.
Table 2-3 lists files contained in this directory. The Arbitrary Beam Cross-Section (ABCS) (Ch. 4) in the MSC
Nastran Linear Static Analysis User’s Guide can replace this Beam Server.

Table 2-3 Beam Server Sample Program Source Files

File Description
SConscript File used by SCons to guide the build
brtuc.F Sample source for the beam server
brtug.F Sample source for the beam server
brtui.F Sample source for the beam server
brtup.F Sample source for the beam server
bsbrc.F Sample source for the beam server
bsbrg.F Sample source for the beam server
bsbri.F Sample source for the beam server
bsbrp.F Sample source for the beam server
bsgrq.F Sample source for the beam server
bsmsg.F Sample source for the beam server
bsbrt.F Sample source for the beam server
bscon.F Sample source for the beam server
mevbr.F Sample source for the beam server
msbrc.F Sample source for the beam server
msbrg.F Sample source for the beam server
msbri.F Sample source for the beam server

DRESP3 Server Source Files

The DRESP3 server program source files are located in the DRESP3 server source directory, i.e.,
install_dir/prod_ver/nast/dr3/src/dr3erv on LINUX and
install_dir\prod_ver\nast\dr3\src\dr3serv on Windows. This directory is an optional
component of the MSC Nastran installation.
Table 2-4 lists files contained in this directory

Main Index
 56 MSC Nastran 2020 Utilities Guide
MSC.Access Source Files

Table 2-4 DRESP3 Server Sample Program Source Files

File Description
SConscript File used by SCons to guide the build.
r3sgrt.F Sample source for the DRESP3 server.
r3svald.F Sample source for the DRESP3 server.
r3svals.F Sample source for the DRESP3 server.

Each server requires a separate source directory. In this delivery, 18 server directories are installed for 18
sample problems. For example, the source files, SConscript, r3sgrta.F, r3svalda.F and r3svalsa.F for server
dr3erva are stored in ~install_dir/prod_ver/nast/dr3/src/dr3serva directory.

MSC.Access Source Files

The MSC.Access sample source files are located in the MSC.Access source directory
install_dir/prod_ver/access on LINUX and install_dir\prod_ver\access on Windows. This directory is an
optional component of the MSC Nastran installation. The src directory contains one subdirectory for each
the six sample programs, listed in Table 2-5 through Table 2-10.

Table 2-5 Access Program ddladd Source Files

File Description
SConscript File that is used by scons to guide the build
ddladd.F Main source file for program ddladd
ld2001.F Subroutine source file for program ddladd
ld2004.F Subroutine source file for program ddladd
ld66.F Subroutine source file for program ddladd
ld67.F Subroutine source file for program ddladd
ld675.F Subroutine source file for program ddladd
ld68.F Subroutine source file for program ddladd
ld681.F Subroutine source file for program ddladd
ld69.F Subroutine source file for program ddladd
ld70.F Subroutine source file for program ddladd
ld705.F Subroutine source file for program ddladd
ld706.F Subroutine source file for program ddladd
ld707.F Subroutine source file for program ddladd

Main Index
 CHAPTER 2 57
Building and Using the Sample Programs

Table 2-6 Access Program ddlprt Source Files

File Description
SConscript File that is used by scons to guide the build
ddlprt.F Demonstration database dictionary print program

Table 2-7 Access Program ddlqry Source Files

File Description
SConscript File that is used by scons to guide the build
ddlqry.F Demonstration database dictionary query program

Table 2-8 Access Program demo1 Source Files

File Description
SConscript File that is used by scons to guide the build
demo1.F Source for sample MSC Nastran database reader.

Table 2-9 Access Program demo2 Source Files

File Description
SConscript File that is used by scons to guide the build
demo2.F Source for sample MSC Nastran database reader.

Table 2-10 Access Program smplr Source Files

File Description
SConscript File that is used by scons to guide the build
smplr.F Source for sample MSC Nastran database reader.

Main Index
 58 MSC Nastran 2020 Utilities Guide
MSC.Access Source Files

Main Index